Hi all, thinking about the current state of CRUX-ARM, I had some ideas that I'll try to explain as best I can. When we started this project we had a few devices and they also lacked the ability to boot from a medium (e.g. SD card) and to install CRUX on a different medium (such as an SSD). There were days when we had to use a flash card and the installation process was limited to unzip our file release (rootfs) in the root partition. Now we have some efikamx smarttop/smartbook devices (thanks to Genesi CEO) that have an SSD inside and allow to use a bootable either from an SD card, or perhaps a USB-CDROM, USB stick, etc. That is why I think we've reached the point where we can think of using an installer as is done in CRUX. I propose some ideas: - Use a initrd or initramfs image with a similar init script like the one in system/iso.git (CRUX), which should search for and mount the crux media - Use a 'setup' script to perform the installation on the user selected media. a) the script could be written in 'dialog' like upstream CRUX, but we must add 'dialog' to our initrd/initramfs b) for now we can live with a simple shell script Anyways we must add(*) 'pkgadd' to our initrd/initramfs (*) is not posible to just decompress the rootfs like we did in the past, so people should be able to select individual packages - Use a directory structure similar to upstream where we could find a directory called crux/ which contains: - a dir per collection of packages (core, opt, xorg) - the kernel directory for sources - tools, etc. - Also we could think in use an external tool to customize installer images with the number of packages we want, etc. I have some other ideas (taken from my own modifications to the original installer of CRUX) but I believe that for now we could at least to implement a basic installer. Naturally there are many things that could have explained in more detail, but I'd rather get a first impression of your ideas. What do you think? -- Jose V Beneyto | http://sepen.mine.nu