On 2/7/07, Joe Ciccone <[EMAIL PROTECTED]> wrote: > Colin Dean wrote: > > Joe Ciccone wrote: > > > >> I suppose you _could_ but he entire intramfs is going to be compiled > >> into the kernel. That would make the kernel huge. I'm pretty sure that > >> SYSLINUX/ISOLINUX can boot off of USB as well. > >> > > > > What would be so bad about having such a huge kernel? It's all getting > > loaded into memory anyways, right? Or do I have misconception? > > > > > Nothing bad, just stating that it would enlarge the kernel. I prefer to > have small kernels, and that is just a personal preference. > > _______________________________________________ > Clfs-support mailing list > [email protected] > http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support > On 2/7/07, Joe Ciccone <[EMAIL PROTECTED]> wrote: > Colin Dean wrote: > > Joe Ciccone wrote: > > > >> I suppose you _could_ but he entire intramfs is going to be compiled > >> into the kernel. That would make the kernel huge. I'm pretty sure that > >> SYSLINUX/ISOLINUX can boot off of USB as well. > >> > > > > What would be so bad about having such a huge kernel? It's all getting > > loaded into memory anyways, right? Or do I have misconception? > > > > > Nothing bad, just stating that it would enlarge the kernel. I prefer to > have small kernels, and that is just a personal preference. > > _______________________________________________ > Clfs-support mailing list > [email protected] > http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support >
Hmm, is an initramfs even writable when it's loaded to memory, or is it static like an initrd? ... as for what you would need available to load a system into memory: 1) Kernel with tmpfs 2) busybox+uclibc (minimum pivot-root, mount, tar, gunzip) 3) Device nodes 4) Some means of detecting what filesystem to load the image from The steps your first bootscript would need to take: 1) Locate where the image is. I'm not certain what could be used to do that. 2) Mount that filesystem 3) Mount a tmpfs that is large enough to hold any tmp files, any configuration files, plus all of your system. 4) untar the system into place (I prefer the idea of tar, since it will let you manage the permissions ahead of time, with a lot less work) 5) pivot_root into the new system. 6) pass off control to the new system's bootscripts I'd delve more into this, but I'm having a few "issues" here with a couple of my systems ... I would go back to running a pure linux environment, but ATI drivers refuse to work for me :'-( ... -- Poison [BLX] Joshua M. Murphy _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
