Re: Generating random.seed for network boot clients

2014-08-15 Thread Paul de Weerd
[moving from misc@ to tech@] On Fri, Aug 15, 2014 at 02:15:08PM +0200, Paul de Weerd wrote: | Yes, it is. Twice, in fact: | | Aug 15 14:13:39 tuna tftpd[14711]: 192.168.34.110: read request for '/etc/random.seed' | Aug 15 14:13:40 tuna tftpd[14711]: 192.168.34.110: read request for '/etc/rando

Re: [Patch] exec(3) Manual

2014-08-15 Thread Philip Guenther
On Wed, Jul 30, 2014 at 7:21 PM, Justus Baumgartner wrote: > On Sun, Jul 27, 2014 at 6:38 AM, Philip Guenther > wrote: > > ... > > > > That phrasing seems wrong: the environment pointer in execvpe() doesn't > > follow "the null pointer that terminates the list of arguments". > Something > > more

Re: jumbo support for bnx(4)

2014-08-15 Thread David Gwynne
ok i have a 5709 somewhere i can work on. dlg On 15 Aug 2014, at 9:50 am, Brad Smith wrote: > On 14/08/14 5:09 PM, Brad Smith wrote: >> On 13/08/14 6:42 AM, David Gwynne wrote: >>> ive had this for 2 years or so. updated to current again. >>> >>> its been tested on the following: >>> >>> bnx

diff -w vs files that don't end in a newline

2014-08-15 Thread Philip Guenther
In case someone is bored (heh) and looking for a user land bug to fix... Given this: printf '1\n2' >a printf '1\n2\n3' >b Compare the output of diff -u a b with the output of diff -uw a b The former gives this: --- a Fri Aug 15 14:08:26 2014 +++ b Fri Aug 15 14:08:25 2014 @@ -1,

Invalid structure spec for SIOCG80211ALLNODES

2014-08-15 Thread Vadim Zhukov
The SIOCG80211ALLNODES operate on struct ieee80211_nodereq_all, not on struct ieee80211_nodereq, right? If I understand things correctly, we were on a safe side because struct ieee80211_nodereq is larger than struct ieee80211_nodereq_all. Should this follow some bump? OK? -- WBR, Vadim Zhukov

improve ressl config setting

2014-08-15 Thread Ted Unangst
This diff is incomplete, but shows the direction I'm headed. The current config struct keeps a pointer to various strings (ca file, etc.). This causes (or will cause) two kinds of trouble. 1. error prone. it's reasonable to create a ca file path by snprintf into a stack buffer. when that buffer d

Re: building 12 hours ago ports tree trigger lil code problem

2014-08-15 Thread sven falempin
certainly an out of sync base. sorry for the noise On Fri, Aug 15, 2014 at 6:55 AM, sven falempin wrote: > Look in /usr/local/share/doc/pkg-readmes for extra documentation. > Can't use an undefined value as a HASH reference at > /usr/libdata/perl5/OpenBSD/Dependencies.pm line 387. > > > -- > >

building 12 hours ago ports tree trigger lil code problem

2014-08-15 Thread sven falempin
Look in /usr/local/share/doc/pkg-readmes for extra documentation. Can't use an undefined value as a HASH reference at /usr/libdata/perl5/OpenBSD/Dependencies.pm line 387. -- - () a

Re: ksh history bug

2014-08-15 Thread Jason McIntyre
On Fri, Aug 15, 2014 at 09:31:36AM +0200, Alexander Hall wrote: > > On Thu, Aug 14, 2014 at 12:10:58PM -0400, Jared Yanovich wrote: > > > + If first and last are both omitted, the previous 16 commands shall > > be listed or the previous single command shall be edited (based on the > > -l opt

Re: arp(8) output and expire timer

2014-08-15 Thread Henning Brauer
* Stuart Henderson [2014-08-15 10:29]: > On 2014/08/12 15:46, Martin Pieuchot wrote: > > I find arp(8) output really difficult to read, but more importantly it > > does not print the expire time of non permanent entries like ndp(8). > > > > So the diff below change arp(8)'s output to be more simi

Re: arp(8) output and expire timer

2014-08-15 Thread Stuart Henderson
On 2014/08/12 15:46, Martin Pieuchot wrote: > I find arp(8) output really difficult to read, but more importantly it > does not print the expire time of non permanent entries like ndp(8). > > So the diff below change arp(8)'s output to be more similar to ndp(8)'s > one. Personally I like the extr

Re: ksh history bug

2014-08-15 Thread Alexander Hall
> On Thu, Aug 14, 2014 at 12:10:58PM -0400, Jared Yanovich wrote: > + If first and last are both omitted, the previous 16 commands shall > be listed or the previous single command shall be edited (based on the > -l option). > > that kind of suggests that the "fc -l" producing those "previous