Darrick Hartman (lists) wrote: <snip> > > Tom, > > I uploaded a few new images a little while ago based on what's in trunk. > I've been using these images in production at several locations > without any issues. These are runnix based images. I need to clean up > the documentation on the www.astlinux.org page, but for now, you can > follow these steps. > > Go to my unofficial image site: > > http://www.djhsolutions.com/astlinux/ > > Download one of the two following files depending on your target device. > > For generic pc's with a monitor and keyboard attached: > > http://www.djhsolutions.com/astlinux/runnix.img.gz > Did that successfully after a couple of false starts!
<snip> > Next, you'll need the appropriate image files. I have these available > for generic pc's (geni586) and net5501 right now. I'll be uploading > images for VIA C3 based systems and net4801 in the morning. I'd > recommend using the svn 1586 images as they are the newest and contain > several updates including Asterisk 1.4.18. > > For example, if you were doing a generic PC, grab this file: > > http://www.djhsolutions.com/astlinux/astlinux-trunk-1586-geni586.tar.gz > > and optionally, the sha1 file to verify the download was successful. > Loaded that successfully as well. > You will need to edit the .conf > file to designate your key disk location and add an option for your > unionfs partition. On all new installs, I've been forgoing the key disk in > favor of only a unionfs partition. Followed the instructions here: http://www.astlinux.org/node/30 > With unionfs, you don't need to worry about putting the system into > read-write mode. Unionfs just does the right thing. There's a genunion > script which will set everything up for you. ( genunion /dev/partition ). Finally tumbled to that and it SEEMS to work > It even tells you how to modify the cmdline in the .conf file to > make sure everything works at boot. > That seems to have disappeared though I THINK I have it correct. > I'm working on a script that will move the contents of an existing key > disk to unionfs, but that's not done yet. > That seems to now work as advertised. Thanks much for that as well. > Hopefully this info is useful. > Now for my problem!! On boot a message flashes by: mounting /dev/loop1 on mnt/asturw failed invalid argument Changing the conf file so that this is in the boot line: asturw=/dev/hda3 astlive Seems to be the source of the error, yet all appears correct when hda3 is examined when booting from DSL Unable to mount either /dev/hda2 or /dev/hda3 when booting from the runnix configuration OK whats that indicate??? I THINK I have done everything as instructed, but once Astlinux is up none of the changes made are read on a reload. I can't even change the root password from the console and have it remembered. Sorry to be so think, but I must have missed something somewhere John Novack -- Dog is my co-pilot ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
