Hi Erich:
scconf_bootinfo only returned two values, the kernel and the rootdev,
initrd and append were not outputed.
This is what my image's /etc/systemconfig/systemconfig.conf looks like:
# systemconfig.conf written by systeminstaller.
CONFIGBOOT = YES
CONFIGRD = YES
[BOOT]
ROOTDEV = /dev/hda6
BOOTDEV = /dev/hda
DEFAULTBOOT = 2.6.18-1.2798.fc6
[KERNEL0]
PATH = /boot/vmlinuz-2.6.18-1.2798.fc6
LABEL = 2.6.18-1.2798.fc6
It does not have info about append/initrd -- is yours different?
Thanks,
Bernard
On 3/21/07, Erich Focht <[EMAIL PROTECTED]> wrote:
> Hi Bernard,
>
> please copy the two attached scripts into your image to some place like
> /usr/bin. scconf_tool is a slightly modified version of what comes with
> systeminstaller-oscar. scconf_bootinfo gives you the info on the kernel,
> initrd, root device and append path.
>
> You'll need to do (in the autoinstall script):
>
> a=`chroot /a /usr/bin/scconf_bootinfo`
> kernel=`echo $a | cut -d" " -f1`
> dev=`echo $a | cut -d" " -f2`
> initrd=`echo $a | cut -d" " -f3`
> append=`echo $a | cut -d" " -f4-`
>
> ...
>
>
> If this works for you I will add the two scripts to systemconfigurator and
> remove scconf_tool from systeminstaller-oscar.
>
> Please be aware that the paths printed need to be prefixed with /a. There
> might be a problem when no absolute paths are used in the systemconfig.conf
> file or when the path is relative to the /boot directory. In that case you'll
> need to prefix the kernel and initrd paths with /boot first.
>
> Best regards,
> Erich
>
> On Wednesday 21 March 2007 16:41, Bernard Li wrote:
> > Hi Erich:
> >
> > On 3/21/07, Erich Focht <[EMAIL PROTECTED]> wrote:
> >
> > > you don't need to touch any SC component. You just need a tiny program
> > > that
> > > uses SC libs to read and interpret the systemconfig.conf of the image. In
> > > the
> > > latest systemconfigurator I added a handy tool for doing this. I think I
> > > can
> > > script you something passing you all you need in a few minutes.
> >
> > Great -- I will wait for it then :-)
> >
> > > By the way: why do you need to unmount /a? Can't you boot directly from
> > > the
> > > installed kernel and initrd? I'm afraid the space they take in the /ramfs
> > > will
> > > stay locked, won't it?
> >
> > If I do not umount /a, then when I kexec the new kernel, it will
> > complain that the disk is not umounted properly, etc.. I will need to
> > investigate whether it actually hangs onto the memory if I copy the
> > kernel/ramdisk to /tmp.
> >
> > 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
