Re: [leaf-devel] New linuxrc mods ready for testing
Eric Spakman wrote: Hello Charles, Files like mount.boot, boot.fstype and /dev/boot are removed (which is great btw), but they are used in some of the lrcfg/lrpkg scripts AFAIK. So maybe some of these scripts needs some changes too. I don't think the Dachstein package backup scripts use these anymore (part of the upgrade to supporting multiple devices), so Bering shouldn't be either. I have verified I can properly backup packages, but I have not made an exhaustive search for anything that might reference the 'boot' files. There are some traces of boot.fstype and /dev/boot left in POSIXness.linuxrouter (both Dachstein-1.0.2 and Bering). I just looked at these, and the use of the boot= kernel command line setting, boot.fstype and /dev/boot are not real significant in POSIXNESS.linuxrouter. The boot= setting and boot.fstype are used as 'defaults' for populating the backdisk file when manually installing a package after the system has come up (note is is also possible to optionally specify a backup device when manually installing a package). The /dev/boot symlink and boot.fstype are used in the mount.boot procedure (uncalled by any other POSIXness or lrcfg script), and by the mount.back procedure (as a fallback if the newer backdisk file is not present). There are at least three ways to deal with this: 1) Remove the references to these files from POSIXNESS.linuxrouter, replacing them with references to the newer files (and likely get rid of the mount.boot procedure entirely). 2) Create the files in linuxrc, using the first PKGPATH= device (instead of the depricated boot= device). 3) Ignore the problem with manually adding packages once the system is up and running. :) Any preference? -- Charles Steinkuehler [EMAIL PROTECTED] --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] New linuxrc mods ready for testing
Eric Spakman wrote: Charles, snip There are at least three ways to deal with this: 1) Remove the references to these files from POSIXNESS.linuxrouter, replacing them with references to the newer files (and likely get rid of the mount.boot procedure entirely). 2) Create the files in linuxrc, using the first PKGPATH= device (instead of the depricated boot= device). 3) Ignore the problem with manually adding packages once the system is up and running. :) Any preference? My preference would be option 1, although option 3 also appeals to me :) :) OK, then it's not a linuxrc problem. Should I go ahead and make the mods to POSIXness? If so, are the Bering versions checked in to CVS anywhere (I've got the Dachstein versions in CVS). Are there any differences between the Bering and the Bering-uClibc versions of POSIXness? P.s. Any progression with the rewrite of linuxrc, need any help? It looks like the linuxrc rewrite is pretty much done. I've made a minor tweak or two since the version I posted (removed /bin/bash from initrd.lrp to prevent conflicts when adding a real bash shell, and removed the code that leaves the CD-ROM mounted and creates the /lib/modules symlink from linuxrc). The biggest help at this point would be for others to test the new linuxrc, make sure it works for them, and think about any other features that might need to be added to linuxrc or leaf.cfg. Further work that looks like it needs to get done, but isn't really directly related to just linuxrc: - Merge Dachstein and Bering modutils code. Bang commands from Dachstein are necessary (IMHO) for running cleanly off a CD-ROM, and I like the 'find' feature of the Bering modutils (as long as it's limited to searching only the current directory and below, rather than the whole root filesystem). Of course, the Bering development team might have a different view of this, and want to keep the current modutils. - Add the /bin/bash - /bin/ash symlink to root, or (optionally) create it in /linuxrc (or sometime prior to loading add-on packages, if package loading gets moved to init). - Determine a mechanism for loading packages at init time, rather than in /linuxrc. There are a lot of options here, including adding a couple new rcS.d scripts, creating an entirely new runlevel (maybe rcL.d?) that runs before rcS.d, etc. I'm not sure there's a universal solution to this problem...since LEAF is based on a ramdisk that is populated at boot time, there's a natural conflict between wanting to mount additional devices 'normally' (ie /etc/fstab or similar), and needing to have some directories mounted prior to package installation, since we're rebuilding the entire filesystem every time we boot. I think the package installation issue needs some discussion between the developers to determine what would work well, and the first two issues are minor enough to be ignored until one of the Bering branches switches to the new linuxrc code (I can work around these issues pretty easily for now, and convert to the 'real' Bering way of doing things once there's an official release). -- Charles Steinkuehler [EMAIL PROTECTED] --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] New linuxrc mods ready for testing
Charles At 06:11 16.03.2004 -0600, Charles Steinkuehler wrote: Eric Spakman wrote: Hello Charles, Files like mount.boot, boot.fstype and /dev/boot are removed (which is great btw), but they are used in some of the lrcfg/lrpkg scripts AFAIK. So maybe some of these scripts needs some changes too. I don't think the Dachstein package backup scripts use these anymore (part of the upgrade to supporting multiple devices), so Bering shouldn't be either. I have verified I can properly backup packages, but I have not made an exhaustive search for anything that might reference the 'boot' files. There are some traces of boot.fstype and /dev/boot left in POSIXness.linuxrouter (both Dachstein-1.0.2 and Bering). I just looked at these, and the use of the boot= kernel command line setting, boot.fstype and /dev/boot are not real significant in POSIXNESS.linuxrouter. The boot= setting and boot.fstype are used as 'defaults' for populating the backdisk file when manually installing a package after the system has come up (note is is also possible to optionally specify a backup device when manually installing a package). The /dev/boot symlink and boot.fstype are used in the mount.boot procedure (uncalled by any other POSIXness or lrcfg script), and by the mount.back procedure (as a fallback if the newer backdisk file is not present). There are at least three ways to deal with this: 1) Remove the references to these files from POSIXNESS.linuxrouter, replacing them with references to the newer files (and likely get rid of the mount.boot procedure entirely). 2) Create the files in linuxrc, using the first PKGPATH= device (instead of the depricated boot= device). Sounds reasonable, it certainly is better than boot= 3) Ignore the problem with manually adding packages once the system is up and running. :) or insert backuptype NONE if not specified at lrpkg -i I looked into linuxrc myself and found that it does not use lrpkg to install packages. It is not a big deal but to me this is not extremely consistent. 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: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] New linuxrc mods ready for testing
Erich Titl wrote: snip 3) Ignore the problem with manually adding packages once the system is up and running. :) or insert backuptype NONE if not specified at lrpkg -i I looked into linuxrc myself and found that it does not use lrpkg to install packages. It is not a big deal but to me this is not extremely consistent. linuxrc doesn't use lrpkg -i to install packages because at boot time the PKGPATH variable is used to install packages from potentially multiple places. The intent of lrpkg -i is to allow manual installation of a specific *.lrp package file once the system is running. While I could be convinced extending lrpkg to deal with the PKGPATH setting would be worthwhile, I think this would mainly be of benifit if package loading is broken into two (or more) steps, with only a limited number of core packages being installed by linuxrc, with the rest being installed by an /etc/init.d script. Also note that I don't believe the POSIXness scripts (lrpkg included) are available currently in the initial ramdisk, but are in root.lrp. -- Charles Steinkuehler [EMAIL PROTECTED] --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] New linuxrc mods ready for testing
At 10:29 16.03.2004 -0600, Charles Steinkuehler wrote: Erich Titl wrote: snip 3) Ignore the problem with manually adding packages once the system is up and running. :) or insert backuptype NONE if not specified at lrpkg -i I looked into linuxrc myself and found that it does not use lrpkg to install packages. It is not a big deal but to me this is not extremely consistent. linuxrc doesn't use lrpkg -i to install packages because at boot time the PKGPATH variable is used to install packages from potentially multiple places. It still iterates through all potential directories, this can be done with lrpkg just the same. The intent of lrpkg -i is to allow manual installation of a specific *.lrp package file once the system is running. While I could be convinced extending lrpkg to deal with the PKGPATH setting would be worthwhile, I think this would mainly be of benifit if package loading is broken into two (or more) steps, with only a limited number of core packages being installed by linuxrc, with the rest being installed by an /etc/init.d script. I don't think lrpkg needs to be touched (well, not for that reason) ... gunzip -c $mnt/$f.lrp /dev/null if [ $? -eq 0 ]; then echo -n $dev gunzip -c $mnt/$f.lrp | qt busybox tar -x might as well be lrpkg -i $mnt/$f #Update installed packages file [ $fnd -eq 0 ] echo $f$PFX/packages backdisk=$f=-t $t $dev fnd=1 else echo -n $dev(cpt!) fnd=1 fi ... Also note that I don't believe the POSIXness scripts (lrpkg included) are available currently in the initial ramdisk, but are in root.lrp. True, but then why. It certainly is not that big. 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: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] New linuxrc mods ready for testing
On Tue, 2004-03-16 at 07:36, Charles Steinkuehler wrote: The biggest help at this point would be for others to test the new linuxrc, make sure it works for them, and think about any other features that might need to be added to linuxrc or leaf.cfg. Charles, Did you look at David's apkg? I think it has many of the features you're looking at now. http://leaf-project.org/devel/ddouthitt/packages/apkg.lrp http://leaf-project.org/devel/ddouthitt/packages/apkg.lrp.txt -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] FYI: New package directory
On Tue, 2004-03-16 at 08:02, K.-P. Kirchdrfer wrote: Please read the instructions in the README you'll find in that repository first, it will be helpful to build the above web page in the current format automatically. K.-P., Greg Morgan is working on this task. phpWebSite package repository indexing module http://kissalice.sourceforge.net/phpmanual/output/c2152.html -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] FYI: New package directory
Am Dienstag, 16. Mrz 2004 18:16 schrieb Mike Noyes: On Tue, 2004-03-16 at 08:02, K.-P. Kirchdrfer wrote: Please read the instructions in the README you'll find in that repository first, it will be helpful to build the above web page in the current format automatically. K.-P., Greg Morgan is working on this task. good. For the moment we use genpage.pl. http://cvs.sourceforge.net/viewcvs.py/leaf/src/bering-uclibc/buildtool/tools/genpage.pl It's not a general solution, but helps a lot to build Bering-uClibc package page(s) kp --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] New Website
On Mon, 2004-03-08 at 14:51, Mike Noyes wrote: Everyone, The website upgrade is taking longer than I anticipated. I'm less than a quarter done. Even so, I hope to go live with the new site this weekend. Everyone, As you may have noticed, our new website isn't operational yet. Work is progressing slowly. I'll keep everyone informed of my progress, and post a message 24 hours prior to the upgrade. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] FYI: New package directory
As of today a new package directory for LEAF Bering-uClibc packages called testing is available. Packages in this directory could be build and contributed by someone outside the Bering-uClibc team, or build for users by request and untested due to lack of hardware etc.., and will be provided as-is. LEAF Users can find those packages at the end of the packages page for Bering-uClibc: http://leaf.sourceforge.net/mod.php?mod=userpagemenu=91017page_id=51 LEAF Developers can write/commit their packages compiled against uClibc version 0.9.20 to the cvs repository: leaf/bin/packages/uclibc-0.9/20/testing/ Please read the instructions in the README you'll find in that repository first, it will be helpful to build the above web page in the current format automatically. thx for your attention kp --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
