OK - I started this so I'll throw in another couple of (euro) cents worth. . . . . .
I've moved from CF to DOM - For all those who are thinking about buying a IDE->CF send me your DOM orders off-list ;-) I moved to 0.4.0 painlessly by "flashing" the DOM from the ISO CD and then simply swapping out with the new DOM. Of course I use a kd! If astopt has been dropped/included as std. then it would be nice to partition the whole DOM (c.f. std. *nix install) rather than just flash the current img size. It makes upgrading easier because they are getting bigger all the time ;-) I'm not sure if the dom's are fat16 - anyway I'd prefer a ufs. What would be nice is a little script that takes all the values from the rc.conf on the kd and inserts them into the /stat/etc version writing the result to /mnt/kd/rc.conf.040 (eg) BTW: The script should read each variable in the /stat/etc/rc.conf even if they are commented. This is easy because there's only one "#". I like to put values into variables that I might use, but I leave them commented out. It would be a shame to loose them. If I think of anything else I'll let you all know. -Graham S. Jarvis- ----- Original Message ----- From: "Kristian Kielhofner" <[EMAIL PROTECTED]> To: "Discussion of AstLinux - Asterisk on Compact Flash" <[EMAIL PROTECTED]> Sent: Friday, May 12, 2006 8:59 PM Subject: Re: [Astlinux-users] 0.4.0 astup > Tom Lynn wrote: > > Darick, > > I'm actually quite calm. Thank you for your concern. > > > > I'm waiting for 30-60 days to see what happens with .4 before I > > attempt an installation. Already though, people are assuming things > > like astup will work, while in reality, they're downgrading to .3 if > > they attempt it. > > > > I'll keep an open mind about the upgrade, but do realize that it's > > more pain that was expected. > > > > Tom, > > That is a very good point. However, astup is already fixed (for people > that already have 0.4). > > I am not happy about changing images. However, I am working on > something today (I have a basic version done) that should make you feel > much better. It will GUARANTEE smooth upgrades till... > > Here is how it works: > > - Your CF stays formatted as FAT16 as it is out of the box > > - You install the AstLinux Loader onto the CF (still FAT16 - it is based > on SYSLINUX) > > - You drop a raw AstLinux-ssdsd.img on the disk (in the FAT16 partition, > not on the disk itself) > > - Insert the CF/CD/USB etc and the AstLinux loader will automatically > find the most recent AstLinux image and boot it. > > Eventually I will work in SHA1 checksuming and other more advanced > features. I already have this running now, I just need to work out some > kinks with the keydisk, etc. > > To upgrade AstLinux, all you have to do is download a new .img on your > CF/USB/etc. The loader will detect the new image and boot it > automatically. If you want to boot a specific .img (version, etc) from > the CF, you can pass astimg= on the boot command line (or edit the > syslinux.cfg) file manually. Meanwhile, the .img is still bootable with > GRUB should you not feel comfortable with the whole new loader. > > I am still working on some of the subtle details, but I am getting > there. Input appreciated! > > -- > Kristian Kielhofner > _______________________________________________ > Astlinux-users mailing list > [email protected] > http://lists.kriscompanies.com/mailman/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to [EMAIL > PROTECTED] _______________________________________________ Astlinux-users mailing list [email protected] http://lists.kriscompanies.com/mailman/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
