Re: so where is our press-release about MacOS X ?

You're right, there's no need to pick fights. But I'm just pointing out that there's no reason FreeBSD should work particularly hard to create the appearance of an alliance with Apple, when all they've done is use the source of some kernel components and a number of utilities for a commercial prod

Re: so where is our press-release about MacOS X ?

In message , Dan Feldman wr ites: >under the moniker "Public Source," after refusing to comply with Open >Source Foundation rules for using the Open Source trademark. OS X ships >with such industry-standard sofware as the Z shell and the Apache W

Re: so where is our press-release about MacOS X ?

FOR IMMEDIATE RELEASE - 1 Apr 2000 SEATTLE - The FreeBSD Project, Inc. officially welcomed today the introduction of Apple Computer's Mac OS X. The next-generation operating system uses the TCP/IP stack of an obsolete version of FreeBSD's flagship product, and is otherwise completely unrelated.

ata driver problems with CTX laptop

I have a CTX EzBook 800 series on which I have used FreeBSD version 2.2.8 since that version was current. At the time I had to use some of the PAO stuff to get the pcmcia enet to work, but everything else seemed to work fine. I just bought a new disk, and figured i'd install 4.2. The at

Re: so where is our press-release about MacOS X ?

As a part-time journalist, I receive a fair number of press releases. Most get tossed, unopened, in an effort to simplify my life. When I do open a release, it all too frequently contains news of some VP of paper clips who has gotten promoted to Senior VP of office supplies. I have considered wri

Re: Displaying options for current NFS mounts

On Sat, 24 Mar 2001, Dima Dorfman wrote: > I tried to export this stuff in struct statfs, but ran into a problem: > I'd need the complete definitions of _args in , but I > can't include, e.g., because the latter includes the > former ()! mount.h used to know too much about all sorts of filesyst

Re: so where is our press-release about MacOS X ?

At 8:36 AM +0100 3/24/01, Poul-Henning Kamp wrote: >Shouldn't the FreeBSD project issue a press release welcoming >Apple's MacOS X ? For what it's worth, the Red Herring article on MacOS 10, at: http://www.redherring.com/index.asp?layout=story&channel=2002&doc_id=1380018338 Mentions that:

Re: Displaying options for current NFS mounts

On Sat, 24 Mar 2001, Dima Dorfman wrote: > Implementing the above functionality in mount(8) isn't actually that > hard. We would need to export the filesystem-specific _args > structures (e.g., nfs_args, ffs_args) to the userland. If we do that, > mount(8) will be able to display all kinds of i

Re: Intel driver doc's Take 2.

On Sat, Mar 24, 2001 at 03:11:54PM -0500, Dennis wrote: > Most drivers are written without full docs. Feh. *EVERY* wpaul written Ethernet driver was written _with_ having the full docs. wpaul will not write a driver otherwise. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux

Re: tuning a VERY heavily (30.0) loaded server

On Tue, Mar 20, 2001 at 09:50:51AM -0800, Matt Dillon wrote: > One thing that comes to mind is that you can smarthost your outgoing > email to another host so the queues don't build up. This should > greatly reduce mail load. In fact, I would recommend offloading email > entirely

Re: Intel driver doc's Take 2.

On 24 Mar 2001, at 19:59, Dennis wrote: > the only thing more annoying the 2 people having a discussion is a third > person telling them to stop. Feel free not to read any more messages in > this thread. Feel free to read the list charter. You two are in a pissing contest unreleated to this

Re: Intel driver doc's Take 2.

Yes, I agree. We should delete the rest of this thread. On Sat, 24 Mar 2001, Dennis wrote: > At 04:07 PM 03/24/2001, Dan Langille wrote: > >On 24 Mar 2001, at 16:12, Dennis wrote: > > > > > And why does all of your email have that stupid attachment? Whats the > > > matter, cant figure out how

Re: Intel driver doc's Take 2.

At 04:07 PM 03/24/2001, Dan Langille wrote: >On 24 Mar 2001, at 16:12, Dennis wrote: > > > And why does all of your email have that stupid attachment? Whats the > > matter, cant figure out how to use an open-source mailer? :-) > >It's called a PGP signature. > >Could you two kids please take this

Re: Intel driver doc's Take 2.

At 04:19 PM 03/24/2001, Will Andrews wrote: >On Sat, Mar 24, 2001 at 04:12:34PM -0500, Dennis wrote: > > For your info, Bub, what makes the BSD license attractive is its usability > > by commercial vendors, so maybe you should go play in Linuxland because > > you are the one in the wrong camp, no

Re: Intel driver doc's Take 2.

Matthew Jacob wrote: > > 1 - Give a select group of people the docs under NDA > > 2 - If there are any specific features Intel wants avoided, get them to > > identify > > them up front. > > 3 - Let them write a driver that uses whatever features that are useful, wi th > > header fi

Re: Intel driver doc's Take 2.

On Sat, Mar 24, 2001 at 06:31:44PM +0100, Luigi Rizzo wrote: > 2) even if you have hardware with an "fxp" on board, adding a second >supported card is cheap and easy -- nothing like having to put >in a second video card; Many, many U1-form-factor systems have two fxp on-board NICs. No roo

make release

Hello there! I just read FAQ on making release and have one question. FAQ says I must be having full CVS source tree (or be able to access it via CVSROOT), but I'm behind modem connection. So I'm curious why it is not enough to have a cvsupped src-all/doc-all/ports-all collections? And is there a

Re: so where is our press-release about MacOS X ?

> >I don't think you can assume any such thing - I say go for it! :) > > Well, how soon we forget history :-) I have no idea what this means. > Right, I fully agree. Chart me up in the "kernel architecture" category > and lets find somebody else do the PR writing... Right. Can we see a show

Re: Displaying options for current NFS mounts

Gerald Pfeifer <[EMAIL PROTECTED]> writes: > What I'd like to see is `mount -v' printing > > vexpert:/files5 on /.amd_mnt/vexpert/files5 (nfs: v3, udp) > > instead of > > vexpert:/files5 on /.amd_mnt/vexpert/files5 (nfs) >

Patch to allow cvs diff to diff date ranges on a branch

This patch allows cvs diff to diff a date range on a branch. e.g.: cvs -d /home/ncvs diff -j RELENG_4:2/15/01 -j RELENG_4:3/06/01 I'm not quite sure what to do with it yet... I suppose submit it to the cvs maintainers since its in contrib. The patch is fairly straightfor

Re: Intel driver doc's Take 2.

On Sat, Mar 24, 2001 at 04:12:34PM -0500, Dennis wrote: > For your info, Bub, what makes the BSD license attractive is its usability > by commercial vendors, so maybe you should go play in Linuxland because > you are the one in the wrong camp, not me. the ability to take code, fix it > and inc

Re: Intel driver doc's Take 2.

On 24 Mar 2001, at 16:12, Dennis wrote: > And why does all of your email have that stupid attachment? Whats the > matter, cant figure out how to use an open-source mailer? :-) It's called a PGP signature. Could you two kids please take this pissing contest off -hackers? Thanks. -- Dan Langi

Re: Intel driver doc's Take 2.

At 03:12 PM 03/24/2001, Will Andrews wrote: >On Sat, Mar 24, 2001 at 03:11:54PM -0500, Dennis wrote: > > Most drivers are written without full docs. Intel supplied drivers for > > linux are available for both eepro100 and gigabit cards. The info is out > > there. Cobbling together the info to prod

Re: Intel driver doc's Take 2.

On Sat, Mar 24, 2001 at 03:11:54PM -0500, Dennis wrote: > Most drivers are written without full docs. Intel supplied drivers for > linux are available for both eepro100 and gigabit cards. The info is out > there. Cobbling together the info to produce a driver...THATS what open > source is all a

Re: Intel driver doc's Take 2.

At 02:45 PM 03/24/2001, [EMAIL PROTECTED] wrote: >On Sat, 24 Mar 2001, Richard Hodges wrote: > > > Thanks for the tip on the XL driver. Over the years, I have seen > > many questions about which driver/card was the best, and all the > > answers were pretty vague, or suggested that Intel had the e

Re: Intel driver doc's Take 2.

> > If the if_wx driver sucks, why not fix it rather than trying to coerce a > > mega-companies with a deep political structure to change is policies? But > > if youre not going to maintain it, dont do it at all. You cant stick it to > > users by deciding later that you dont want to support it an

Re: Intel driver doc's Take 2.

On Sat, 24 Mar 2001, Richard Hodges wrote: > Thanks for the tip on the XL driver. Over the years, I have seen > many questions about which driver/card was the best, and all the > answers were pretty vague, or suggested that Intel had the edge. Yes. It's currently my understanding that t

Re: AW: Best Gigabit ethernet for 4.x

On Sat, Mar 24, 2001 at 12:31:05 -0500, Dennis wrote: > At 05:04 PM 11/18/2000, Kenneth D. Merry wrote: > >On Sat, Nov 18, 2000 at 11:33:29 -0500, Dennis wrote: > > > At 04:28 PM 11/17/2000, Schmalzbauer, Harald wrote: > > > >I just heard that Intel doesn't supply documentation on ther chipset >

Re: Intel driver doc's Take 2.

On Sat, Mar 24, 2001 at 02:49:14PM -0500, Dennis wrote: > You use the term "our developers" as if you are some sort of closed cult. They have something in common, and it's not a cult. It's called being an "open source developer". > I have NEVER complained about Intel not releasing full informa

Re: so where is our press-release about MacOS X ?

In message <[EMAIL PROTECTED]>, Jordan Hubbard writes: >> I think you can assume that Jordan will veto me writing anything even >> remotely like a press-release for the project. I just thought it was >> a very good opportunity to beat the drum... > >I don't think you can assume any such thing - I

Patch to disallow the build of modules

Hi, Here is a patch to select the modules you want and don't want. The patch is for /usr/src/sys/modules/Makefile from RELENG_4. Then you have to put variables in make.conf (i'm writing the patch for defaults/make.conf) like this : NO_KMOD_FPU=true NO_KMOD_GNUFPU=true ... Thanks for any

Re: Intel driver doc's Take 2.

On Sat, 24 Mar 2001 [EMAIL PROTECTED] wrote: > On Sat, 24 Mar 2001, Richard Hodges wrote: > > > For many (most?) people that may be practical. But what about > > those of us with a 1RU system using fxp on the motherboard and > > NEED the single PCI slot for something else? I suspect that > > t

Re: Intel driver doc's Take 2.

At 01:33 PM 03/24/2001, [EMAIL PROTECTED] wrote: >On Sat, 24 Mar 2001, Luigi Rizzo wrote: > > > I have read the thread for a while, and i wonder: > > > > why in the world someone should go through the effort and > > responsibility of SIGNING THE NDA _and_ negotiating with Intel > > for getting per

Re: so where is our press-release about MacOS X ?

> I think you can assume that Jordan will veto me writing anything even > remotely like a press-release for the project. I just thought it was > a very good opportunity to beat the drum... I don't think you can assume any such thing - I say go for it! :) One of the things that makes the Linux c

Re: Intel driver doc's Take 2.

On Sat, 24 Mar 2001, Richard Hodges wrote: > For many (most?) people that may be practical. But what about > those of us with a 1RU system using fxp on the motherboard and > NEED the single PCI slot for something else? I suspect that > there are more of us than you might think. Richard,

Re: Intel driver doc's Take 2.

On Sat, 24 Mar 2001, Luigi Rizzo wrote: > I have read the thread for a while, and i wonder: > > why in the world someone should go through the effort and > responsibility of SIGNING THE NDA _and_ negotiating with Intel > for getting permissions to redistribute the code ? I made the ef

Re: tuning a VERY heavily (30.0) loaded s cerver

:Matt Dillon <[EMAIL PROTECTED]> writes: :> So you would be able to create approximately four 17GB swap partitions. :> If you reduce NSWAP to 2 you would be able to create approximately :> two 34GB swap partitions. If you reduce NSWAP to 1 you would be able :> to create approxima

Re: Intel driver doc's Take 2.

On Sat, 24 Mar 2001, Luigi Rizzo wrote: > I have read the thread for a while, and i wonder: > > why in the world someone should go through the effort and > responsibility of SIGNING THE NDA _and_ negotiating with Intel > for getting permissions to redistribute the code ? > > I do not see how th

Re: Intel driver doc's Take 2.

On Sat, 24 Mar 2001, Luigi Rizzo wrote: > I have read the thread for a while, and i wonder: > > why in the world someone should go through the effort and > responsibility of SIGNING THE NDA _and_ negotiating with Intel > for getting permissions to redistribute the code ? Because NDAs come as

Re: Intel driver doc's Take 2.

I have read the thread for a while, and i wonder: why in the world someone should go through the effort and responsibility of SIGNING THE NDA _and_ negotiating with Intel for getting permissions to redistribute the code ? I do not see how this is doing any good to the project, given that 1) ther

Re: AW: Best Gigabit ethernet for 4.x

At 05:04 PM 11/18/2000, Kenneth D. Merry wrote: >On Sat, Nov 18, 2000 at 11:33:29 -0500, Dennis wrote: > > At 04:28 PM 11/17/2000, Schmalzbauer, Harald wrote: > > >I just heard that Intel doesn't supply documentation on ther chipset > and the > > >FreeBSD and Linux support is quiet bad. The Netge

Re: Intel driver doc's Take 2.

> 1 - Give a select group of people the docs under NDA > 2 - If there are any specific features Intel wants avoided, get them to > identify > them up front. > 3 - Let them write a driver that uses whatever features that are useful, with > header files that define the register bits etc

Re: so where is our press-release about MacOS X ?

In message <[EMAIL PROTECTED]>, Robe rt Watson writes: > >On Sat, 24 Mar 2001, Kris Kennaway wrote: > >> On Sat, Mar 24, 2001 at 08:36:30AM +0100, Poul-Henning Kamp wrote: >> > >> > Shouldn't the FreeBSD project issue a press release welcoming >> > Apple's MacOS X ? >> >> Good idea, write one :-

Re: so where is our press-release about MacOS X ?

On Sat, 24 Mar 2001, Kris Kennaway wrote: > On Sat, Mar 24, 2001 at 08:36:30AM +0100, Poul-Henning Kamp wrote: > > > > Shouldn't the FreeBSD project issue a press release welcoming > > Apple's MacOS X ? > > Good idea, write one :-) To be a really effective press release, it should be joint re

Re: tuning a VERY heavily (30.0) loaded s cerver

Matt Dillon <[EMAIL PROTECTED]> writes: > So you would be able to create approximately four 17GB swap partitions. > If you reduce NSWAP to 2 you would be able to create approximately > two 34GB swap partitions. If you reduce NSWAP to 1 you would be able > to create approximately o

Re: tuning a VERY heavily (30.0) loaded s cerver

On Fri, Mar 23, 2001 at 08:11:03PM +0100, Adrian Chadd wrote: > A while back I started running through the undocumented sysctls and > documenting them. I didn't get through all of them, and the main reason > I stopped was because there wasn't a nifty way to extract the sysctls > short of writing

Re: Intel driver doc's Take 2.

Peter Wemm wrote: > However, there are lots of things that would never go into a FreeBSD driver. > Things like the microcode interfaces for the wake-on-lan sequencer/filter, > etc. I´m trying for nearly a year now to get the docs from Intel for exactly this feature because i need it for a client

Re: udp checksum problem..

On Sat, Mar 24, 2001 at 05:10:04PM +0530, Madhavi Suram wrote: > > Hi > > I am modifying FreeBSD 4.1 kernel. I am hacking all UDP packets in > ip_input, changing some headers and finding the udp checksum > using in_pseudo() and setting the packet header csum_flags to > CSUM_UDP (I know this is

udp checksum problem..

Hi I am modifying FreeBSD 4.1 kernel. I am hacking all UDP packets in ip_input, changing some headers and finding the udp checksum using in_pseudo() and setting the packet header csum_flags to CSUM_UDP (I know this is a dirty way of doing it.. but, had to do it for efficiency reasons). When I t

Re: so where is our press-release about MacOS X ?

On Sat, Mar 24, 2001 at 08:36:30AM +0100, Poul-Henning Kamp wrote: > > Shouldn't the FreeBSD project issue a press release welcoming > Apple's MacOS X ? Good idea, write one :-) Kris PGP signature

Re: Fingerprint authentication?

On 0, David McNett <[EMAIL PROTECTED]> wrote: > On 23-Mar-2001, Michael Aronsen wrote: > > Has anyone been working on or know of any work being done on getting any > > fingerprint gadgets working in FreeBSD? > > This is mostly off-topic, but I wanted to take the opportunity to point > out an exc