Re: misprint in cvs(1) man page

On Sat, Jul 19, 2014 at 06:41:35AM +, ?? ?? wrote: > On Sat, Jul 19, 2014 at 07:01:57AM +0059, Jason McIntyre wrote: > > On Sat, Jul 19, 2014 at 05:26:41AM +, ?? ?? wrote: > > > There is misprint in cvs(1) man page for import command: > > > > > > 'Yo

Re: misprint in cvs(1) man page

On Sat, Jul 19, 2014 at 07:01:57AM +0059, Jason McIntyre wrote: > On Sat, Jul 19, 2014 at 05:26:41AM +, ?? ?? wrote: > > There is misprint in cvs(1) man page for import command: > > > > 'You can use this command both for initial creation of a repository, and > > for wholesa

Re: misprint in cvs(1) man page

On Sat, Jul 19, 2014 at 05:26:41AM +, ?? ?? wrote: > There is misprint in cvs(1) man page for import command: > > 'You can use this command both for initial creation of a repository, and > for wholesale updates to the module _form_ the outside source' > > must be: > > 'Yo

misprint in cvs(1) man page

There is misprint in cvs(1) man page for import command: 'You can use this command both for initial creation of a repository, and for wholesale updates to the module _form_ the outside source' must be: 'You can use this command both for initial creation of a repository, and for wholesale updates

tcpdump(8) not printing llc data for ieee80211

Sometimes tcpdump(8) does not print llc & higher layer data when using -y IEEE802_11 or IEEE802_11_RADIO. Index: print-802_11.c === RCS file: /cvs/src/usr.sbin/tcpdump/print-802_11.c,v retrieving revision 1.13 diff -u -p -r1.13 print-

Re: lynx: disable old protocols

ftp -o - http://ftp.openbsd.org/pub/OpenBSD/snapshots/ftplist | some script, or maybe your eyes and pick one. On Fri, Jul 18, 2014 at 4:29 PM, Ville Valkonen wrote: > On 17 July 2014 00:10, Stuart Henderson wrote: >> On 2014/07/16 16:00, Jean-Philippe Ouellet wrote: >>> Oh come on... It's not li

Re: lynx: disable old protocols

On 17 July 2014 00:10, Stuart Henderson wrote: > On 2014/07/16 16:00, Jean-Philippe Ouellet wrote: >> Oh come on... It's not like the URLs are some giant uuid-based madness >> or something. All the mirrors have the same simple layout. If you install >> lots of boxes regularly, it doesn't take long

Re: [DIFF] sftp-server.8, sshd_config.5 after syslog_r change

Unfortunately, no. The ssh manual pages are also used by the -portable effort. We do not bother documenting these divergences; there is little harm. Actually you could submit a new diff which suggest that logging "might" need a /dev/log setup. If written carefully to cover both kinds of systems

[DIFF] sftp-server.8, sshd_config.5 after syslog_r change

Hi, is this correct to reflect syslog_r(3) change? I tested chrooted internal-sftp without /dev/log in the chroot and it was logging fine. j. Index: sftp-server.8 === RCS file: /cvs/src/usr.bin/ssh/sftp-server.8,v retrieving revisi

Re: [patch] sys/dev/ic/mfi.c

> Hi, > > I think is a bug in sys/dev/ic/mfi.c noticed during > "PATCH: further kernel malloc -> mallocarray" review[1] > > I see the mallocarray() patch seems to have been applied. > Want to make sure if this is in fact a bug, that it is > not overlooked. > > Ignore if this is noise. That diff

Re: "Only what you need"

>Something that has been in my eye for a while; how about those users and >groups? > >$ cat /etc/passwd|wc -l > 56 >$ cat /etc/group |wc -l > 75 > >Maybe one group for write access to /var, one for /etc, etc? Or we could run them all as root.

"Only what you need"

Hi, Something that has been in my eye for a while; how about those users and groups? $ cat /etc/passwd|wc -l 56 $ cat /etc/group |wc -l 75 Maybe one group for write access to /var, one for /etc, etc? //Gustav -- This e-mail is confidential and may not be shared with anyone other

Re: LibreSSL and GOST crypto

> I have been pointed that I did not formulate the question clearly. > Would you prefer to have a static ENGINE thing built into the LibreSSL, > providing 100% API compatibility with original ccgost implementation, > or it would be better to have a cleaner well-integrated cryptosuite? As already r

call for bwi(4) testing

This diff for bwi(4) needs testing, both on systems where it works and on systems where it spews these error messages to the console: bwi0: intr fatal TX/RX (0) error 0x1000 bwi0: intr fatal TX/RX (1) error 0x1000 The point of this diff is to make the above errors go away. But I need

Re: man.cgi: clean exit when absent or empty manpath.conf

Salut Sebastien, Sébastien Marie wrote on Fri, Jul 18, 2014 at 08:50:17AM +0200: > Starting to play with man.cgi (src/usr.bin/mandoc/cgi.c), Thank you for testing. > it seems that man.cgi will segfault if configuration file > is absent or empty. > > Here a patch that display error message and