Re: Intel Etherexpress support?

2000-10-31 Thread Peter van Dijk
On Tue, Oct 31, 2000 at 10:57:11AM +0100, Gerhard Sittig wrote: > On Tue, Oct 31, 2000 at 00:08 +0100, Peter van Dijk wrote: > > > > Without looking at any of your code, I would kindly like to ask > > you not to look at the Linux driver for eexpress too much - > > i

Re: Intel Etherexpress support?

2000-10-30 Thread Peter van Dijk
On Thu, Oct 26, 2000 at 12:58:28AM -0400, Matthew N. Dodd wrote: > On Tue, 24 Oct 2000, Glendon Gross wrote: > > Is it possible to use the old Intel EtherExpress-16 cards with FreeBSD? > > The driver was broken a while back and I'm right in the middle of trying > to fix it. I've actually given u

Re: Junior Kernel Hacker Task: M_ZERO

2000-10-22 Thread Peter van Dijk
On Sun, Oct 22, 2000 at 06:23:57PM -0400, Peter Dufault wrote: [snip] > I guess I'm suggesting a clarification on when you want to set this flag. > If I want to be sure I get my zeroed out stuff real soon should I use > still use bzero? No. What he means is that this 'zeroing process' will happen

Re: port tree clean?

2000-10-09 Thread Peter van Dijk
On Tue, Oct 10, 2000 at 02:52:37AM +0800, Donny Lee wrote: > > Hi there, > > is port tree back for cvsup? Yes. Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds

2000-10-09 Thread Peter van Dijk
On Mon, Oct 09, 2000 at 12:37:30AM +, attila! wrote: > -BEGIN PGP SIGNED MESSAGE- > > on Sun, 8 Oct 2000 11:46:47 +0200, Peter van Dijk <[EMAIL PROTECTED]> said: > > > Actually, mailwrapper (I don't know about this mailcap thing, > > I'm o

Re: POSTFIX-- Wietse: tweak and go! --pkg & port: both duds

2000-10-08 Thread Peter van Dijk
On Sun, Oct 08, 2000 at 07:02:12AM +, attila! wrote: [snip] > > (o) CAUTION: 'make world' reinstalls 'sendmail' even when > > NO_SENDMAIL=YES # do not build sendmail and related programs > > is included in '/etc/make.conf'; 'make world' may not > compile sendmail, but

Re: #include in

2000-10-02 Thread Peter van Dijk
On Mon, Oct 02, 2000 at 10:10:39AM -0700, Jordan Hubbard wrote: > > >This breaks several other ports (like BitchX). > > > > I think this breaks all IRC's which are cloned from the same origin :-) > > I'm still looking for the downside to this. ;-) 'HEY!' ;P Greetz, Peter -- dataloss networks

Re: superduperopen(3) (was: Fdescfs updates--coming to a devfs near you!)

2000-09-17 Thread Peter van Dijk
On Sat, Sep 16, 2000 at 10:04:47AM +0200, Gerhard Sittig wrote: > > > How much sense does it make to think about implementing tee and > select methods this way? Like "open file1 and file2 and write to > both of them whatever I give to you" and "give me data coming in > from whatever file is in

Re: Fdescfs updates--coming to a devfs near you!

2000-09-14 Thread Peter van Dijk
On Thu, Sep 14, 2000 at 02:37:06PM +0200, Poul-Henning Kamp wrote: [snip] > The majority of these programs could be handled by adding knowledge > of "-" as a magic filename to fopen(3). > > At the same time I would really love if we implemented "|.*" to mean > "do an popen(3)" instead. Heh, and

Re: FIFOs & select: what about our implementation?

2000-09-05 Thread Peter van Dijk
On Wed, Sep 06, 2000 at 12:44:33AM +0400, Andrey A. Chernov wrote: [snip] > > Please consider that we talk not about reads but about select. 'Select' is > used to indicate that data is available while 'read' used to read it, they > are two different things and behaviour of one thing not related t

Re: FIFOs & select: what about our implementation?

2000-09-05 Thread Peter van Dijk
On Tue, Sep 05, 2000 at 07:50:56PM +0400, Andrey A. Chernov wrote: > Consider this comment comes from screen(1): > > /* > * Define this if your system exits select() immediatly if a pipe is > * opened read-only and no writer has opened it. > */ > #define BROKEN_PIPE 1 > > We have broken(?) pi