kernel source tree and compiled goodies for 586 users are up now...
http://leaf.sourceforge.net/stinkingpig for the goods.
The tree is 2.2.18 based and the kernel is compiling to 413002 bytes.
Patches are:
initrd-archive_3.2_2.2.18.diff linux_brfw_2.2.17.diff
ip_masq_vpn-2.2.17.patch
well, I'm hung up on a execution order problem right now anyway, hopefully
will fix tonight and get something in the public tomorrow night.
--
Jack Coates
Monkeynoodle: It's what's for dinner!
On Sat, 17 Feb 2001, Mike Noyes wrote:
> At 11:10 PM 2/14/01 -0800, Jack Coates <[EMAIL PROTECTED]> w
what, having device files in the root? Seems good to me, or rather, I
don't see what's wrong with it. If you or the program have permissions and
access to mknod you can stick a device file anywhere in the filesystem I
suppose. Seems to me their location in the filesystem is more a matter of
conven
At 11:10 PM 2/14/01 -0800, Jack Coates <[EMAIL PROTECTED]> wrote:
>maybe -- I know very little about CVS and it may not be the best tool for
>providing a LEAF distribution (mixed script and binary files, symlinks, etc).
Jack,
I found this information on binary files and symlinks.
9. Handling bi
On 17 Feb 2001, at 6:49, Jack Coates wrote:
> I'd be inclined to stick to your existing system -- it seems sick
> and wrong to put device files in /tmp and I don't understand what
> they'd be doing there instead of /dev. There may well be a good
> reason (permissions? why not chmod the /dev entry
I'd be inclined to stick to your existing system -- it seems sick and
wrong to put device files in /tmp and I don't understand what they'd be
doing there instead of /dev. There may well be a good reason (permissions?
why not chmod the /dev entry?) but until one comes forward...
--
Jack Coates
Mo
