On Wed, 7 Jun 2017 21:27:27 -0500
Amit Kulkarni wrote:
> On Thu, 8 Jun 2017 01:57:25 +0200
> Mike Belopuhov wrote:
>
> > On Wed, Jun 07, 2017 at 18:35 -0500, Amit Kulkarni wrote:
> > > Wow, please get this in!!!
> > >
> > > This fixes cvs update on
On Thu, 8 Jun 2017 01:57:25 +0200
Mike Belopuhov wrote:
> On Wed, Jun 07, 2017 at 18:35 -0500, Amit Kulkarni wrote:
> > Wow, please get this in!!!
> >
> > This fixes cvs update on hard disks, to go much much faster. When I am
> > updating the entire set of cvs trees: www,
On Thu, Jun 08, 2017 at 12:47:00AM +0200, Jan Klemkow wrote:
> This diff adds a missing routing message to the neighbor discovery code.
> The message informs the userland about new reachable IPv6 nodes on the
> network. The IPv6 network stack acts more like the IPv4 port by this
> diff. Now, the
On Wed, Jun 07, 2017 at 18:35 -0500, Amit Kulkarni wrote:
> Wow, please get this in!!!
>
> This fixes cvs update on hard disks, to go much much faster. When I am
> updating the entire set of cvs trees: www, src, xenocara, ports, I can
> still use firefox and have it perfectly usable. There's a
Wow, please get this in!!!
This fixes cvs update on hard disks, to go much much faster. When I am
updating the entire set of cvs trees: www, src, xenocara, ports, I can
still use firefox and have it perfectly usable. There's a night and
day improvement, before and after. Thanks for debugging and
Hi,
This diff adds a missing routing message to the neighbor discovery code.
The message informs the userland about new reachable IPv6 nodes on the
network. The IPv6 network stack acts more like the IPv4 port by this
diff. Now, the behavior is like arpcache() in netinet/if_ether.c on
line 653.
On Wed, Jun 07, 2017 at 01:17:10PM -0400, Ted Unangst wrote:
Klemens Nanni wrote:
Besides fixing a tautological 'v < 0' and using more descriptive/less
errorprone sizeof(target) this patch unifies strtoul(3) handling both
logically and cosmetically.
A great deal of these look like exactly the
On Wed, Jun 07, 2017 at 03:58:01PM +0200, Sven-Volker Nowarra wrote:
> Hi,
>
> I setup a PXE boot server, to load my different clients. Now I have 2 single
> EFI devices, which do not support PXE (both are Macminis). They prefer "EFI"
> files. Both are capable running 64bit software, but
Sven-Volker Nowarra wrote:
> Here the client stops, for sure there is no harddrive. Somehow the efiboot
> file does not provide the option to load the kernel via network, only hd0 or
> hd1 is offered. I looked up the files in
> /sys/arch/amd64/stand/efiboot/efiboot.c and the header files, but
bump because I forgot to CC florian@
On 26/05/17 18:11, Lucas Gabriel Vuotto wrote:
On 26/05/17 12:38, Florian Obser wrote:
On Fri, May 19, 2017 at 02:11:22PM -0300, Lucas Gabriel Vuotto wrote:
Previous patch shall be ignored, as it was an ugly hack. Below is a patch that
is simpler and
Hi,
I setup a PXE boot server, to load my different clients. Now I have 2 single
EFI devices, which do not support PXE (both are Macminis). They prefer "EFI"
files. Both are capable running 64bit software, but require 32bit EFI loaders.
So I added a line in my dhcpd.conf to supply
Hi,
I've discovered that short reads (nonzero b_resid) aren't
handled very well in our kernel and I've proposed a diff
like this to handle short reads of buffercache read-ahead
buffers:
diff --git sys/kern/vfs_bio.c sys/kern/vfs_bio.c
index 95bc80bc0e6..1cc1943d752 100644
--- sys/kern/vfs_bio.c
Klemens Nanni wrote:
> Besides fixing a tautological 'v < 0' and using more descriptive/less
> errorprone sizeof(target) this patch unifies strtoul(3) handling both
> logically and cosmetically.
A great deal of these look like exactly the situation strtonum was desinged to
cope with. this means
Michal Mazurek wrote:
> Yes, the function seems a bit inconsistent, in that "bcrypt" means "bcrypt,a"
> but NULL means "bcrypt,8". awolk@ points out that the function is used in
> just a few places - src and some ports patches, so we should be able to
> change it. Judging by the commit message the
Code like this should match the EXAMPLE in the strtoul manual page.
This shit happens everytime someone tries to take a shortcut,
sadly.
> Fix clang warning about tautological compare: an unsigned long can't
> be negative.
>
> ok? Or dlg@ can slip it in with his next ifconfig change.
>
>
Fix clang warning about tautological compare: an unsigned long can't
be negative.
ok? Or dlg@ can slip it in with his next ifconfig change.
Index: brconfig.c
===
RCS file: /cvs/src/sbin/ifconfig/brconfig.c,v
retrieving revision
On Wed, Jun 07, 2017 at 05:58:42PM +1000, David Gwynne wrote:
> On Wed, Jun 07, 2017 at 07:32:18AM +0100, Jason McIntyre wrote:
> > On Wed, Jun 07, 2017 at 02:51:42PM +1000, David Gwynne wrote:
> > > >
> > > > you are breaking the format of this page if you start to move specific
> > > >
On 06/06/17(Tue) 19:13, Miod Vallat wrote:
> This used to be necessary in the gcc 2.95 days. Nowadays nothing in base
> or X uses it.
ok mpi@
> Index: share/mk/bsd.own.mk
> ===
> RCS file: /OpenBSD/src/share/mk/bsd.own.mk,v
>
This might not be the fix we want in the long run, but it surely
prevents frustration when making a typo in the interface name.
As reported by Sebastien Marie and claudio@.
OK?
diff --git sys/net/pf_ioctl.c sys/net/pf_ioctl.c
index 43cccdb2efa..c563a439c45 100644
--- sys/net/pf_ioctl.c
+++
Hi,
This is a straightforward diff moving invariant chunks before
dequeue operation.
OK?
diff --git sys/dev/pci/if_vic.c sys/dev/pci/if_vic.c
index e34a1aa4f27..bc1e600d8bc 100644
--- sys/dev/pci/if_vic.c
+++ sys/dev/pci/if_vic.c
@@ -1049,43 +1049,35 @@ vic_start(struct ifnet *ifp)
On Sat, Jun 03, 2017 at 03:15:42PM +0200, Klemens Nanni wrote:
> =X actually works quite fine despite the mentioned condition:
>
> $ touch f; mkdir d
> $ chmod =X f d
> $ ls -ld f d
> d--x--x--x 2 kle wheel 512 Jun 3 15:11 d/
> -- 1 kle wheel0 Jun
On Wed, Jun 07, 2017 at 07:17:16PM +1000, David Gwynne wrote:
>
> tweaked diff
>
yes, looks good.
jmc
> Index: ifconfig.8
> ===
> RCS file: /cvs/src/sbin/ifconfig/ifconfig.8,v
> retrieving revision 1.282
> diff -u -p -r1.282
On Wed, Jun 07, 2017 at 10:01:41AM +0100, Jason McIntyre wrote:
> On Wed, Jun 07, 2017 at 05:58:42PM +1000, David Gwynne wrote:
> > >
> > > why not just add your one option to the vlan section, which is what it's
> > > relevant to, for now. if in the future you make it work in other areas,
> > >
On Tue, Jun 06, 2017 at 08:29:23PM +, Florian Obser wrote:
> On Tue, Jun 06, 2017 at 08:49:32PM +0200, Adam Wolk wrote:
> > On Tue, Jun 06, 2017 at 12:28:59PM -0600, Theo de Raadt wrote:
> > > > The only thing against using automatic rounds would be having them
> > > > guessed on a
> > > >
On Wed, Jun 07, 2017 at 05:58:42PM +1000, David Gwynne wrote:
> >
> > why not just add your one option to the vlan section, which is what it's
> > relevant to, for now. if in the future you make it work in other areas,
> > we can see whether it warrants a shuffle.
>
> well, vnetid and parent
On Wed, Jun 07, 2017 at 07:32:18AM +0100, Jason McIntyre wrote:
> On Wed, Jun 07, 2017 at 02:51:42PM +1000, David Gwynne wrote:
> > >
> > > you are breaking the format of this page if you start to move specific
> > > subsytems into the main body.
> > >
> > > that makes things less clear. for
On Wed, Jun 07, 2017 at 02:51:42PM +1000, David Gwynne wrote:
> >
> > you are breaking the format of this page if you start to move specific
> > subsytems into the main body.
> >
> > that makes things less clear. for example, can i use the parent-device
> > stuff on any type of interface or just
27 matches
Mail list logo