Re: [leaf-devel] /linuxrc testing - round 2

2004-05-05 Thread Charles Steinkuehler
Eric Spakman wrote:

Do you want to go ahead and make these changes and release a new tar.gz
file?
Attached you will find the updated tar.gz
Thanks to Eric, there's a new version of the updated linuxrc package 
available (posted on my website):
http://lrp.steinkuehler.net/files/kernels/misc-stuff/linuxrc-2004-05-05.tgz

IIRC, this fixes a few minor bugs, including:

- /dev/null in root.dev.mk (should be in root.blk.mk even though it's 
not a block device, as it's used early in the init scripts).

- A mistake in creating devlist and rdevlist that silent errors (umount 
and rmdir called with no arguments).  The errors appear in linuxrc.err 
if VERBOSE is enabled.

Eric:  Any other bugs addressed in this update?

--
Charles Steinkuehler
[EMAIL PROTECTED]


---
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson  Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] /linuxrc testing - round 2

2004-05-05 Thread Eric Spakman
 Thanks to Eric, there's a new version of the updated linuxrc package 
 available (posted on my website):
 http://lrp.steinkuehler.net/files/kernels/misc-stuff/linuxrc-2004-05-05.tgz
 
 IIRC, this fixes a few minor bugs, including:
 
 - /dev/null in root.dev.mk (should be in root.blk.mk even though it's 
 not a block device, as it's used early in the init scripts).
 
 - A mistake in creating devlist and rdevlist that silent errors (umount 
 and rmdir called with no arguments).  The errors appear in linuxrc.err 
 if VERBOSE is enabled.
 
 Eric:  Any other bugs addressed in this update?
 
No, these are the only bugs we found in linuxrc.

Eric Spakman


---
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson  Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] /linuxrc testing - round 2

2004-05-05 Thread Erich Titl
Charles

I looked at the new linuxrc, nice, modular, easier to maintain.

At 22:14 05.05.2004, Charles Steinkuehler wrote:

- /dev/null in root.dev.mk (should be in root.blk.mk even though it's not 
a block device, as it's used early in the init scripts).
Would this not, for consistency's sake, rather go to a root.chr.mk file.

cheers
Erich
THINK
Püntenstrasse 39
8143 Stallikon
mailto:[EMAIL PROTECTED]
PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16


---
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson  Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel


Re: [leaf-devel] /linuxrc testing - round 2

2004-05-05 Thread Charles Steinkuehler
Erich Titl wrote:

Charles

I looked at the new linuxrc, nice, modular, easier to maintain.

At 22:14 05.05.2004, Charles Steinkuehler wrote:

- /dev/null in root.dev.mk (should be in root.blk.mk even though it's not 
a block device, as it's used early in the init scripts).
Would this not, for consistency's sake, rather go to a root.chr.mk file.
Personally, I don't think so...

...if you're worried about a char device showing up in root.blk.mk, I'd 
either:

- Just add a comment in root.blk.mk stating something like /dev/null is 
here with all the block devices because it's used early in the boot 
sequence (and in this file!).

- If that's too much bloat or doesn't make you happy, you chould rename 
root.blk.mk something like root.bootdev.mk, root.init.mk or something 
else that coveys these devices are needed to boot-strap and find the 
leaf.cfg file

--
Charles Steinkuehler
[EMAIL PROTECTED]


---
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson  Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3

___
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel