John, There are no problems using CentOS. There may be some issues with autoconf on FC9. FC8 worked fine. A 32bit host system works better than a 64bit host (for the build environment).
2.5 kernel? Those were the beta ones before 2.6 came out! Dang that's old. Everything is accurate with Chris's instructions until the end. See more notes inline... <snip> >> C} cd .. >> D} make >> >> This resumes the building of your astlinux... >> >> Once done you will have a directory called astlinux-trunk-xxxx this is where >> your new images are located. >> >> Not being sure which image you are running but assuming you are running on >> the newer runnix structure, loading up a new version couldn't be simpler... >> in my case my systems are not FULL production systems.. I am using the Neo >> Light (CV860a) boards for testing. And have a semi production system in my >> home. >> >> To load a new image you can power down, pull the flashcard out and drop it >> in your windows PC if you like... >> The 'os' directory will contain your images.. look at your existing >> astlinux-trunk-xxxx.run.conf file and simply change the version number in >> that file if you like. This way it will boot and run exactly the same as >> before... No need to pull the CF card! Simply issue this command: mount -o remount,rw /oldroot/cdrom Then use scp to copy the new files into the /oldroot/cdrom/os directory. Note: Do NOT delete your current images. Reboot first then remove the old files. Multiple astlinux-XXX.run, astlinux-XXX.run.conf, astlinux-XXX.run.sha1 files can remain in the 'os' directory. The newest one is used unless a 'ver' file exists which can be used to specify the version to use. (the format for the ver file is astlinux-XXX). Also with versions after 1895, you can specify astkd=auto and asturw=auto. If you used genkd and genunion to create your file systems, the correct file system labels will exist and be automatically detected. You can test this by typing: findfs LABEL=ASTKD findfs LABEL=ASTURW >> Then copy your new astlinux-trunk-xxxx.run file and its associated .sha1 >> file from your developer to the os dir on the flash, and finally copy the >> initrd.img file over to the os dir as well... now either rename the old >> files to something like astxxxxinactive and astxxxxinactivesha1 and >> initrdinactive with no . and nothing after.. they will stay there but not >> hurt anything.. or you can move them off entirely if you like... See above... This is really why we like the new system and why it's taken so long to get a release ready. It's much easier to upgrade and manage remote upgrades. No need to pull the CF card each time an update is needed. Darrick ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
