Re: secondary nameserver in kickstart network option

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Anne,

On Wed, 24 Jan 2001, Anne POSSOZ wrote:

> Hello Mike,
>
> > Please look at:
> >  http://www.europe.redhat.com/documentation/rhl7/ref-guide-en/s1-kickstart2-commands.php3
> >
> > subsection: "%pre -- Pre-Installation Configuration Section"
>
> This is great. I didn't realize the %pre section was documented together
> with the command section, at the far end. And just with that example:
> %pre
> # add another nameserver
>      echo "nameserver 10.10.0.2" >> /etc/resolv.conf
>
> Thanks a lot.
no problem ....



>
> > Ok, if you want know more about this stuff, then make your questions.
> > We have tried it at our side with RH 6.2 and it works ;-).
>
> Just as a start, what is mknbi-linux? Maybe my ignorance...
OK this command MaKes a tagged Network Boot Image (mknbi ;-) from a linux
kernel and an initial ramdisk so you can give it a TFTP server to serv
with it and clients can boot a linux kernel over the network. OK, I have
worked at night to make our website to this stuff also available in
english. Look at:

 http://www.tu-chemnitz.de/urz/anwendungen/cluster/publish/RemoteInstall/index.php3?lang=en

Puuuuhhhh...:) ....  I hope they now explain some things.

>
> >   mknbi-linux $KSINSTROOT/ks-cd-img-6.2/misc/src/trees/boot/vmlinuz \
> >            $KSINSTROOT/ks-cd-img-6.2/misc/src/trees/initrd-network.img \
> >            --append="ks=nfs:192.168.250.253:$KSINSTROOT/ks-roots/ " \
> >            > linux-6.2.nbi.192.168.250.253
>
> Can you phrase what is the aim of this? I cannot figure out how
> all this work. I miss some points.
> By the way, there is no more misc/src/trees in redhat 7.0...
> I am just curious as we can get ideas from other.
Ok we don't have tested the redhat 7.0 distribution at any time. But I
think you can use the kernel and initial ramdisk from the images/pxeboot
path. Then the command should looks like

   mknbi-linux $KSINSTROOT/ks-cd-img-7.0/images/pxeboot/vmlinuz \
            $KSINSTROOT/ks-cd-img-7.0/images/pxeboot/initrd.img \
            --append="ks=nfs:192.168.250.253:$KSINSTROOT/ks-roots/ " \
            > linux-6.2.nbi.192.168.250.253

or if I readed the "RH reference guide" correctly and all (BOOTP/DHCP,
TFTP and NFS) is on the same machine then the command

   mknbi-linux $KSINSTROOT/ks-cd-img-7.0/images/pxeboot/vmlinuz \
            $KSINSTROOT/ks-cd-img-7.0/images/pxeboot/initrd.img \
            --append="ks" > linux-6.2.nbi.192.168.250.253

will do enough. But that was not tested by me :(.

best regards
  mike


-- 
----------------------------------------------------------------------
email:  Mike.Becher@xxxxxxxxxxxxxxxxxx http://www.tu-chemnitz.de/~mibe
mail:   TU Chemnitz, URZ, Str. d. Nationen 62, 09107 Chemnitz, Germany
phone:  (+49) (0)371/531-1725          fax: (+49) (0)371/531-1629
----------------------------------------------------------------------





[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux