Re: PUBLIC CHALLENGE: (was RE: devfs again, (was RE: USB deviceallocation) )

david parsons (orc@pell.portland.or.us)
9 Oct 1999 02:43:47 -0700


In article <linux.kernel.Pine.GSO.4.10.9910090219390.14121-100000@weyl.math.psu.edu>,
Alexander Viro <viro@math.psu.edu> wrote:

>On 8 Oct 1999, david parsons wrote:

>> The sticky bit hasn't always been there, and when I was at university
>> 20 years ago we had a bunch of machines running BSD 2.7 with /tmp
>> being 777.
>
>Umhm... Remember the fun with rm /tmp/12345.s; cp my_code.s /tmp/12345.s;

Not on a single-user machine it isn't.

You're forgetting that this is Unix, and a Unix kernel is a marvelously
adaptable thing. I'm not talking about taking a dos+devfs kernel and
putting it onto a publicly accessable multiuser Posix box, but taking
the kernel and putting a custom userland on it for an installer, a
firewall, a (hypothetical) Linux+WINE upgrade to Windows, or a single
disk toy to annoy the purists.

>> plus fat takes a little less room than ext2fs on a floppy, so that
>> plus devfs may be enough so I can shoehorn the bloated elephant that
>> will be 2.6 onto my install floppy and still have enough room to fit
>> the installer and pcmcia utilities.
>
>BTW, do you realize that 2.0.28 is very likely to have racey FAT?

Devfs doesn't exist for 2.0.28. I'm talking about 2.6, because
if the feature freeze is in, devfs won't be going into 2.4 and
I'll be waiting for 2.6 to rev Mastodon's kernel from 2.0.28.
I've already done all the kludges to get the gory details out
of the kernel for 2.0.28.

____
david parsons \bi/ unless you're warning me that the ms-dos filesystem
\/ is going away in 2.6

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/