Hi Bernard, okay, I got it. Sounds good and I'll have a look at SC. You'll need some tiny code which uses the SC libs to get the info...
I'm forwarding this email to oscar-devel and DongInn, maybe DongInn can pass some info on kboot on his PS3. Best regards, Erich On Wednesday 21 March 2007 01:11, Bernard Li wrote: > Hi Erich: > > Actually this has nothing to do with PS3. PS3 uses kboot, which is a > bootloader based on kexec, however currently I am only interested in > integrating kexec with SystemImager. > > It is somewhat difficult to work on kboot for PS3 without the physical > hardware :-) > > The idea of integrating kexec with SystemImager is that after the > imaging process, you would umount /a and you would then run kexec to > boot the just imaged kernel (you need to copy the kernel and initrd to > /tmp first). > > The command is something like: > > kexec --append="root=/dev/hda6 ro" --initrd=/tmp/sc-initrd.img -t > bzImage --force /tmp/vmlinuz > > This would then boot up the just imaged kernel without reboot, and it > would even tell si_monitor that it has rebooted since it goes through > the entire process of booting up the kernel, doing init etc. > > So for now, you don't need to do anything in regards to > SystemConfigurator, unless you want to help me parse for the info > which I need ;-) (--append and --initrd options above). > > I hope that I am clear on this, please let me know if you have any > other questions. > > Cheers, > > Bernard > > On 3/20/07, Erich Focht <[EMAIL PROTECTED]> wrote: > > Hi Bernard, > > > > I heard of the work on integrating PS3s, and if you integrate a kexec based > > boot into systemimager, I guess I'll have to integrate a configurator module > > for it into systemconfigurator. Can you give me any details on the > > configuration files needed for kexec/kboot? How they look like, where they > > are, what program is used to install them or so? > > > > Thanks, > > best regards, > > Erich > > > > On Tuesday 20 March 2007 22:57, Bernard Li wrote: > > > Hi Erich: > > > > > > On 3/20/07, Erich Focht <[EMAIL PROTECTED]> wrote: > > > > > > > IMO it should work without SC, too. SC has some advantages in > > > > autodetecting > > > > and configuring modules.conf, but this is not mandatory and one could > > > > use > > > > other methods to do the post-config. I think you can take it out from > > > > the spec > > > > file's Requires: (guess this is what you want, right?). > > > > > > Actually no :-) > > > > > > I am integrating kexec with SystemImager, this will give the user a > > > new option where they do not need to reboot and it will start up the > > > imaged kernel automatically. I have tested this manually and it > > > works, the only issue I am facing is how to accurately retrieve the > > > append and initrd options to pass to kexec (--append and --initrd). > > > > > > For SystemImager, SystemConfigurator is the gatekeeper for these kind > > > of information, so I was thinking of using SystemConfigurator to > > > gather this info, but this is assuming that all users of SystemImager > > > will use SystemConfigurator so I would just like to confirm this. > > > > > > I will probably send an email to Sean Dague to see if he has any other > > > suggestions for me. > > > > > > I plan to add a new post-install action called "kexec", which will > > > automatically boot up the imaged kernel -- if you have any other > > > suggestions on how this should be implemented, please feel free to let > > > me know. > > > > > > Thanks, > > > > > > Bernard > > > > > > > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
