On Tue, Jan 21, 2014 at 03:52:23PM +1100, Rod Whitworth wrote:
> I had a short run-up of the first 5.5 i386 snap install and it
> looked pretty much as expected but a more recent one showed up and I
> grabbed it and loaded it onto my little Shuttle.
>
> The dmesg is below but I'll make some obser
I had a short run-up of the first 5.5 i386 snap install and it
looked pretty much as expected but a more recent one showed up and
I grabbed it and loaded it onto my little Shuttle.
The dmesg is below but I'll make some observations first.
Unlike the earlier snap the screen does not get entirel
Cleanup the abuse of x as the rn_addmask radix node. Since in most
cases x is just used as a temp variable. Main offender is rn_addmask()
which sets x once at the top uses it then late in the function and then
starts reuing it for various other stuff. While there fix some for loops
to while ones an
absolutely prevent forwarding carp or NFS/rpc using the shiny new
received-on any.
can only minimally test that here. need at least one carp and one
diskless test.
Index: rc
===
RCS file: /cvs/src/etc/rc,v
retrieving revision 1.420
j...@wxcvbn.org (Jérémie Courrèges-Anglas) writes:
> Hi,
>
> The reference FUSE implementation defines fuse_opt_parse's third
> argument as const. At least fuse-zip[1] needs this.
> follow.
Scratch that. 8)
[...]
--
jca | PGP: 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
(
> This is ugly. Better introduce an extent_alloc_with_descr() or
> extent_alloc_static() interface which is similar to extent_alloc(), but
> receives the extent descriptor as an added argument.
Fair enough; seems this is indeed a better interface as it doesn't
require the use of a "fixed" extent.
Hi,
The reference FUSE implementation defines fuse_opt_parse's third
argument as const. At least fuse-zip[1] needs this.
follow.
ok?
[1] https://code.google.com/p/fuse-zip/
Index: fuse_opt.c
===
RCS file: /cvs/src/lib/libfuse/fus
On Mon, Jan 20, 2014 at 12:38:37PM +0100, Martin Pieuchot wrote:
> Here's a diff that substitutes the crazy defines of rtsock.c plus some 0
> -> NULL conversion. There's no object change with it.
>
> ok?
OK claudio
makes rtsock.c not nicer but at least not worse.
> Index: net/rtsock.c
> =
> In order to make the sparc64 iommu code "mpsafe", I need to make sure
> the extent manager can be used in an mpsafe manner. The current code
> isn't really safe since the extent manager needs to allocate region
> descriptors whenever we do a bus_dmamap_load(). The diff below adds a
> function t
Hi,
Get rid of this routing message transition code before 5.5 release.
ok?
bluhm
Index: net/route.h
===
RCS file: /data/mirror/openbsd/cvs/src/sys/net/route.h,v
retrieving revision 1.83
diff -u -p -u -p -r1.83 route.h
--- net/rout
Hi Donovan,
Donovan Watteau wrote on Sat, Jan 11, 2014 at 04:18:59PM +0100:
> OpenBSD now provides an nginx.conf(5) manual page and I love this,
> thanks!
>
> But it ends with an EXAMPLES section which only deals with some
> horrible use of whitespace, which is "not recommended". I don't
> get
Greetings All,
About a week ago I warned you all that the OpenBSD project did not
have the funds to cover our bills for the past year (especially the
ability to handle the electricity) and that our funding sources were
not sustainable.
As most of you know the news of our predicament has been wide
Greetings All,
About a week ago I warned you all that the OpenBSD project did not
have the funds to cover our bills for the past year (especially the
ability to handle the electricity) and that our funding sources were
not sustainable.
As most of you know the news of our predicament has been wide
previously on this list Theo de Raadt contributed:
> >
> > If the tests are as good as this project claims them to be, the process
> > should take exactly one test cycle. If that's the case, then the test
> > regime suck big time. Logic brother. Logic.
>
> the OpenBSD project's purpose is not
Here's a diff that substitutes the crazy defines of rtsock.c plus some 0
-> NULL conversion. There's no object change with it.
ok?
Index: net/rtsock.c
===
RCS file: /home/ncvs/src/sys/net/rtsock.c,v
retrieving revision 1.134
diff -u
this diff adds "any" as a away to match any non-loopback interface.
primary use is probably sth like
block out on $someinf received-on any
which prevents anything to be forwarded to $someif, while still
allowing locally generated packets.
pass on any
also works, but is probably not all that use
Looking at ATI resume, I pushed Mark to explore using DVACT_WAKEUP instead,
because the code looks super hairy and might sleep...
The same applies to Intel.
Since there are many more people who rely on such machines, can we get
some test reports of this on all machines, for suspend/resume and
hib
Hi,
i'm interested in testing your diff, but i will not get to testing until
saturday.
Regards,
Fabian
18 matches
Mail list logo