On Mon, Jun 30, 2014 at 07:31:45PM +0200, Gregor Best wrote:
> Hi people,
>
> the attached patch fixes two minor issues with the ifconfig(8) manpage.
>
> The first part makes the operation of the `delete' option without an
> argument a bit more obvious.
>
> The second is a simple fix for the ran
On Mon, Jun 30, 2014 at 2:47 PM, Ingo Schwarze wrote:
> so in a nutshell, mmap(2) was originally a BSD idea and first implemented
> in SunOS? And there is no doubt that *BSD always had MAP_ANON and never
> MAP_ANONYMOUS and that SunOS primarily defines MAP_ANON and MAP_ANONYMOUS
> only for "/* (s
I noticed a problem in one of my OpenBSD installation where tmux(1)
would lose its session socket after a few inactive days. Every time
that happened I quickly fixed it by sending a SIGUSR1 (as suggested by
the man page) to restore the socket session.
I also noted that would only happen on one mac
udv_attach() and uvn_attach() are called directly, not via any generic
dispatch table mechanism, so there's no point in specifying that they
accept "void *" instead of the underlying types they actually expect.
ok?
Index: share/man/man9/uvm.9
==
On Mon, Jun 30, 2014 at 11:53:04AM +0200, Otto Moerbeek wrote:
> This indeed solves some problems, but I have a test file on which it cores.
Patch relative to the original diff I posted.
diff -ru sort.new/fsort.c sort.new2/fsort.c
--- sort.new/fsort.cTue Jul 1 15:54:45 2014
+++ sort.new2/fs
On Sun, Jun 29, 2014 at 09:52:28PM -0700, Philip Guenther wrote:
> > > Here's a patch to do that.
> >
> > Just a comment in code (unused variables in urldecode).
> > Else it seems ok. And my use-case works.
>
> Dang it, I just noticed that I had sent an earlier version of my diff,
> which had pr
When pf is disabled (pfctl -d), pf_remove_queues() detaches hfsc from the
interface but the queues are not removed from pf_queues_active.
The next time pf rules are loaded, pf_commit_queues() calls pf_remove_queues()
and in turn hfsc_delqueue() for each queue in pf_queues_active. This fails
since
I've just switched on "out-of-order" packages, after much testing.
What this means:
new packages won't be compatible with older pkg_add. Most specifically,
the plist order may no longer match the packing-list.
-> if you see strange pkg_add errors, and your base system is not uptodate,
that's you