On Tue, Aug 25, 2009 at 3:21 PM, Mark Rosenstand<rosenstand@gmail.com> wrote:
On Fri, 2009-08-21 at 15:25 +0200, Tilman Sauerbeck wrote:
Hi, the first release candidate of the upcoming CRUX 2.6 release is available now.
Preliminary release notes are available here: http://crux.nu/Main/ReleaseNotes2-6, the complete ChangeLog is available in gitweb: http://crux.nu/gitweb/?p=system/iso.git;a=blob_plain;f=ChangeLog;hb=2.6 and the ISO itself is available on our mirrors: http://crux.nu/Main/Download
Please report problems if you find them :)
Would it be possible to provide (USB-stickable) disk images instead of/in addition to the ISO images?
This would make it installable without using a USB CD-ROM on netbooks, mini-itx pc's and other devices. It's also way faster to boot than a CD which is great for recovery usage.
Additionally you don't get all those CD's that you never got around to label collecting dust and getting scratched all over your desktop.
Actually I think burning/booting ISO's is about the only usage my workstation CD-RW has these days with disk storage being dirty cheap.
Related to this topic of providing other installation media than CD-ROM's, would be the following: usage for installation in virtualized environments. For example when I've tried to install Crux for the first time I've used QEMU and everything worked seamlessly. But when I wanted to switch to a production environment and test it there it was a little bit more difficult. I wanted to install CRUX as the operating system into a Xen domU, and the problem was booting a domU from a CD-ROM... In the end I've successfully done that (but only after some hassle). So it would have been much more easy to just point the Xen configuration file to an CRUX installation disk image. (The same would be for installing CRUX unde UML (User Mode Linux), etc.) But these bootable disk-images could come into two flavours: * FAT file system with sys-linux on them that would just load the kernel and init-rd and boot them. The init-rd image should contain all the files needed for install (and thus would be quite big). (This would be easy to build and use in virtualized environment.) * because of the last problem Debian also puts another file on this disk, that would be picked up by the installer and thus lightens the init-rd. (This would be quite complicated both to build and setup in a virtualized environment.) * Ext2/3 (or whatever) file-system with GRUB / Lilo that would just run the whole system from this disk. This is just an bootable Linux system with needed files for installation. (Again easy to build an use.) I would vote for the third solution, as usually the kernel and init-rd is provided externally (outside of the disk image) in virtualized environments. Thanks, Ciprian.