Hi, I am curious about the aproach taken but cannot easilly recognize it from the code. Could you (or the author) please explain what the aproach is? What is mounted from where, what is exported from where, which directories are read-only and which are writable? What is the meaning of nfs-root, ramfs-rsync, ramfs-http?
Is the approach only working for fedora? Why is the ramdisk built as cramfs? It is uncommon to use anything else than initramfs (simply buildable with cpio) since many years... If nothing speaks against initramfs, you should probably switch to that. Thanks & best regards, Erich On Dienstag 15 Juli 2008, [EMAIL PROTECTED] wrote: > Hi all, > > Ferrol has been working on the extension of SystemImager for a diskless > support. He did a pretty good job, the implementation being not intrusive. > > Please find a description of the modification, a patch for si_prepareclient > and a new Perl module for SystemImager that actually implements the diskless > support. It does not aim at being perfect but it is a small extension that > enables a basic diskless support, and we think the community may be > interested by such a capability. > > Is it something that could be included directly into SystemImager? > > Of course, if you have any questions or remarks, feel free to contact us. > > Thanks, > > Description of changes made: > ---------------------------- > > 1. The user needs only modify a configuration file. This file is > /etc/systemimager/diskless.conf. > > <ip> <path_to_kernel> <method_of_boot> > > The <method_of_boot> section can define three methods: > nfs-root, ramfs-rsync, ramfs-http. > > 2. /usr/sbin/si_prepareclient was modified in order to include a flag that can > be used to signify whether or not modifications should be done. > The proper call is: > > /usr/sbin/si_prepareclient --diskless > > It looks to see if that flag is there and then calls a function named > diskless(). This function makes use of a perl module, > /usr/lib/systemimager/perl/SystemImager/Diskless.pm, that contains > most of the code that was used in si_mkdiskless. > After the function, diskless(), returns si_prepareclient exits. This > can be changed, it was just seen as a possible annoyance to have some > parts of si_prepareclient to run if the user only wanted the diskless > portion to run. > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
