Am Donnerstag, 26. Februar 2004 23:45 schrieb Charles Steinkuehler:
> I'm getting new network service soon (hopefully more bandwidth!), and
> will be taking the opportunity to migrate my personal firewall system
> from Dachstein CD to Bering.
>
> Not that there's anything wrong with the method of creating a Bering CD
> outlined in the users guide, but I'm wanting something a bit closer to
> Dachstein (ie: floppy-boot emulation for the bootable CD, instead of
> isolinux), as I find it easier to debug, and easier for others to modify.
>
> In the process of making a Bering CD "bootdisk" floppy, I had to crawl
> through the Bering /linuxrc script, and I noticed a few things I think
> could be improved:
>
> - There are a *LOT* of variable assignments of the form:
>
> VAR=sed 's/.*LRP=/\1/; s/ .*//1' /proc/cmdline`
>
> These would be a lot faster using the built-in shell substitution
> functions, although it would require two lines instead of one, ie:
>
> CMDLINE=`cat /proc/cmdline`
> ...
> VAR=${CMDLINE##*LRP=}
> VAR=${VAR%% *}
>
> I think the sed stuff came from Dachstein (and probably from LRP
> before that), but I know a lot more about shell scripting now than I did
> when I was starting on the *stein releases. :)
>
> - There is currently no mechanism for varying the size of the root, log,
> or temp ramdisk other than by directly editing the kernel command line
> provided by the bootloader (kind of hard when it's on a read-only CD).
> It looks to me like it should be possible to mount the boot= device (ie:
> a floppy) and read the ramdisk sizes from optional config files, as is
> currently done with LRP= and PKGPATH=, although it might be necessary to
> unmount the disk prior to the pivot_root, and re-mount it afterwords
> (some testing required).
>
> So...to get this on topic for leaf-devel, is there any interest in
> incorperating any of these /linuxrc chages in Bering? If so, I'll try
> to do a decent job of the modifications and provide them in a convinent
> form for public comment (is /linuxrc maybe in CVS somewhere?). If not,
> I'll probably just ignore the problem entirely, and make something that
> only works for me.
>
> Also, is there any interest in making a 1440K minimal floppy boot disk
> and a set of instructions available for the generation of a CD-ROM? I
> find this a *VERY* easy way to make CD images, as you can simply tell
> users to copy bootdisk.bin and whatever LRP packages they want to a
> directory, then run mkisofs with the appropriate command switches. Much
> less confusing than isolinux procedure outlined in the users guide, IMHO.
Charles;
your work on linuxrc will be welcome and we definitely will test improvements
in/for Bering-uClibc version.
In case you don't know, Bering-uClibc CD is build with bootdisk.ima and the
Dachstein CD approach instead isolinux.
There are also doc's for building such a CD in the Bering-uClibc User's Guide.
kp
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
