Hi,
The diff below updates libXpm to version 3.5.13. Tests and oks
welcome.
Apply in $XSRCDIR/lib/libXpm and then rebuild xenocara following
release(8).
Index: ChangeLog
===
RCS file: /cvs/OpenBSD/xenocara/lib/libXpm/ChangeLog,v
ret
On Sat, Dec 28, 2019 at 07:48:45PM -0500, Bryan Steele wrote:
> With FreeDB announcing[0] that the service will be shutting down as of
> March 31st of 2020, and the only other alternative (MusicBrainz) already
> having shutdown their freedb/cddb gateway in favour of their own API
> early this year,
On Sat, Dec 28, 2019 at 07:46:46PM -0600, Patrick Dohman wrote:
>
> > On Dec 28, 2019, at 6:11 AM, Stefan Sperling wrote:
> >
> > Access points at 36c3 use low transmit power on purpose, and often fall
> > below
> > the RSSI threshold which trigger background scans. At some locations (e.g.
> >
Hi,
The patch below update xauth to version 1.1. Testing and oks welcome
Index: ChangeLog
===
RCS file: /cvs/OpenBSD/xenocara/app/xauth/ChangeLog,v
retrieving revision 1.9
diff -u -p -u -r1.9 ChangeLog
--- ChangeLog 19 Feb 2017 17:
Hi again,
the patch below update xhost to version 1.0.8. testing and oks
welcome.
Index: ChangeLog
===
RCS file: /cvs/OpenBSD/xenocara/app/xhost/ChangeLog,v
retrieving revision 1.6
diff -u -p -u -r1.6 ChangeLog
--- ChangeLog 10 May
When switching APs we queue a deauth frame to the old AP, which
should be the last frame queued to hardware before we switch.
To send the deauth frame ieee80211_send_mgmt() gets called.
ieee80211_send_mgmt() calls if_start(), a driver-specific function
which usually loops over the outgoing managem
> On Dec 29, 2019, at 6:50 AM, Stefan Sperling wrote:
>
> I don't understand your question.
> What is a "handover" and what does soft vs. hard mean?
I apologize for the confusion.
A 80211 handover refers to a AP "switch"
* After a background scan, we have now switched APs.
* Pretend we were
On Sun, Dec 29, 2019 at 08:54:35AM -0600, Patrick Dohman wrote:
>
>
> > On Dec 29, 2019, at 6:50 AM, Stefan Sperling wrote:
> >
> > I don't understand your question.
> > What is a "handover" and what does soft vs. hard mean?
>
> I apologize for the confusion.
> A 80211 handover refers to a AP
Marc Espie wrote in <20191229101350.ga17...@nausicaa.home>:
|On Sat, Dec 28, 2019 at 07:48:45PM -0500, Bryan Steele wrote:
|> With FreeDB announcing[0] that the service will be shutting down as of
|> March 31st of 2020, and the only other alternative (MusicBrainz) already
|> having shutdown the
On Sun, Dec 29, 2019 at 07:40:01AM +0100, Klemens Nanni wrote:
> On Sun, Dec 29, 2019 at 03:30:15AM +0100, Klemens Nanni wrote:
> > > link->target isn't the right place to put this, for one thing it's only
> > > 16 bits
> > > and the wwn is 64 bits, and it's used throughout the driver to look up
On Mon, Dec 30, 2019 at 06:54:02AM +1000, Jonathan Matthew wrote:
> I'd prefer this:
>
> pagelen = min(hdr.page_length * 4, sizeof(vpg));
>
> just to avoid trashing the stack if the page grows in newer firmware versions.
Sure, I'll commit with min() and a small comment for that, thanks.
OBP defaults to booting from disk and network in that order.
With multiple disks attached, only the first disk is tried.
OBP mostly if not always also defaults to automatic boot, meaning
domains start trying boot devices once the firmware is done rather than
dropping into the {0} ok prompt.
This
Hi,
Is the purpose of smr_grace_wait() to round robin the curproc through
all CPUs, to make sure all CPUs have passed the quiescent state? Is
this line of thinking correct or flawed?
I was preparing a diff and wanted to know if it is safe to disable the
SMR kthread by commenting it out for testing
Those are briefly mentioned for the specific softraid case in
boot_sparc64(8) but I want better offline documentation.
Technically `boot-device' accepts the empty string as well but all that
OBP does is
{0} ok setenv boot-device ''
boot-device = ''
{0} ok boot
Now that `ldomctl console ...' is implemented there is actually no need
to print the device any longer, it is an implementation detail that
should be hidden just like it is the case with vmctl.
That also makes it fit nicely on serial consoles again.
$ doas ldomctl status primary
p
On Sun, Dec 29, 2019 at 05:23:43PM -0600, Amit Kulkarni wrote:
> I was preparing a diff and wanted to know if it is safe to disable the
> SMR kthread by commenting it out for testing purposes on amd64. Just a
> simple yes/no would do!
no
16 matches
Mail list logo