Re: Adding -maxdepth and -mindepth options to find(1)

> Turns out the patch doesn't quite work as it stands... Something like > 'find . -name foo -maxdepth 1' won't work because the maxdepth code > will only be executed if the previous conditions match. (So 'find . > -maxdepth 1 -name foo' works fine.) I guess I'll have to find a way > around that

Re: Adding -maxdepth and -mindepth options to find(1)

Kris Kennaway wrote: > On Sat, 29 Apr 2000, Ben Smithurst wrote: > >> any other people who might want it? I've attached a patch to implement >> this, if I don't get any feedback I'll send-pr it instead, I thought I >> might get a few opinions here first. > > Good idea - haven't reviewed the pa

Re: Adding -maxdepth and -mindepth options to find(1)

On Sat, 29 Apr 2000, Ben Smithurst wrote: > any other people who might want it? I've attached a patch to implement > this, if I don't get any feedback I'll send-pr it instead, I thought I > might get a few opinions here first. Good idea - haven't reviewed the patch, though. Kris In God w

Re: Xircom cards

I cvsuped to 5.0-current and am trying the Xircom driver now. I want to provide as much information as needed. below is information on how I built my kernel and various configuration files. Upon insertion I get the below message. and although I can see the card with netstat -in as soon as I run

Re: IPv6 & Bridging don't work together

Nick, are you sure the problem does not depend upon having bridge_ipfw=1 ? I don't think there is anything else IPv4-specific in the bridging code, if it was we would also have problems with IPv4/IPX and other non-ip protocols. cheers luigi > Alas, > IPv6 does not appear to work

Re: Fwd: socket.h and _POSIX_SOURCE

On Sat, Apr 29, 2000 at 12:52:57PM +0200, Jeroen Ruigrok/Asmodai wrote: > -On [2425 20:08], Arun Sharma ([EMAIL PROTECTED]) wrote: > >Would it be fair to say this is a (POSIX non-compliance) bug in the > >header files ? > > As Bruce Evans was kind enough to reassure me: > > sys/socket.h is n

Re: Help me complete the FreeBSD specific zsh completions!

From: "Akinori -Aki- MUSHA" <[EMAIL PROTECTED]> Subject: Re: Help me complete the FreeBSD specific zsh completions! Date: Sat, 29 Apr 2000 17:14:31 +0900 knu> Here's an update patch for the shells/zsh-devel port: knu>http://people.freebsd.org/~knu/ports/zsh-devel.diff.gz knu> This updates the

IPv6 & Bridging don't work together

I have a filtering bridge that I am also trying to use as a 6to4 router. Alas, IPv6 does not appear to work correctly with the bridge. If I configure the interface on one side of the bridge, it is not ping6able by hosts on the other side. If I configure both sides with separate prefixes, then bot

printing problems in 3.4 when removing the sl pseudo-device

Hi, Anyone is aware of such a strange (?) behavior? When I am removing the sl pseudo-device from the kernel config file I am getting strange results printing files (at least .ps files like tiger.ps from gs examples). The printing is fine if I am putting the sl pseudo-device back in the kernel.

Re: Fwd: socket.h and _POSIX_SOURCE

-On [2425 20:08], Arun Sharma ([EMAIL PROTECTED]) wrote: >Would it be fair to say this is a (POSIX non-compliance) bug in the >header files ? As Bruce Evans was kind enough to reassure me: sys/socket.h is not a POSIX header. 'nuff said I guess. -- Jeroen Ruigrok vd Werven/Asmodaiasmod

Re: Help me complete the FreeBSD specific zsh completions!

Here's an update patch for the shells/zsh-devel port: http://people.freebsd.org/~knu/ports/zsh-devel.diff.gz This updates the port corresponding to zsh 3.1.7-pre-1. Use that version to work on developing compdefs. -- / /__ __