diskless feature in fedora?
Kaspars Melkis
liste2 at isolis.lv
Fri Jan 16 10:25:04 UTC 2004
2004-01-15 at 17:49, Lewi rakstīja:
> thank you, I have tried it, but still not working :(
> would u like write some manual
>
> my step is, please correct me
>
> I have 1 server fedora OS with gigabit ethernet on board from Asus P4800,
> and diskless client with Compaq Deskpro 6000 with tlan ethernet that using etherboot for network booting
> (how do I know if cards is support PXE???)
>
> 1. copy fedora OS( / ) in server to /a/root with default kernel, mkdir /a/snapshot
Where you using "rsync -a -e ssh 172.16.15.2:/ /a/root" ?
It is not clear what have you done. What I did was to put hd into
diskless client machine, installing Fedora OS on it, updating,
configuring and tweaking it, starting sshd and then copying it to server
with rsync. At least, it was what docs said to do.
> 2. running redhat-config-nfs export /a/root /a/snapshot, starting portmap, nfs
> checking with:
> # rpcinfo -p
> # exportfs
> # cat /etc/exports
> /a/root/ *(rw,sync,no_root_squash)
> /a/snapshot/ *(rw,sync,no_root_squash)
>
> add line to /etc/hosts.allow
> portmap:ALL
>
> 3. running redhat-config-netboot->diskless->create with name for example: diskless
> 4. create a snapshot in redhat-config-netboot with name for example: 172.16.15.2
> 5. create dhcpd.conf that contain file for boot (created by mknbi later)
> ________________________________
> not authoritative;
> ddns-update-style none;
> ignore client-updates;
> allow booting;
> allow bootp;
>
> subnet 172.16.15.0 netmask 255.255.255.0 {
> option routers 172.16.15.1;
> option subnet-mask 255.255.255.0;
>
> option domain-name "mitindo.com";
> option domain-name-servers 172.16.15.1;
>
> range dynamic-bootp 172.16.15.128 172.16.15.150;
> default-lease-time 21600;
> max-lease-time 43200;
>
> # we want the nameserver to appear at a fixed address
> host ichtus {
> hardware ethernet 00:80:5f:2a:05:2e;
> fixed-address 172.16.15.2;
> next-server 172.16.15.1;
> if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
> filename "/thunder.zpxe";
> } else if substring (option vendor-class-identifier, 0, 9) = "Etherboot" {
> filename "/vmlinuz.nbi";
> }
> }
> }
> _______________________________________
>
> 6. starting dhcpd, tftpd
> 7. download floppy image for booting in client in http://www.rom-o-matic.com (for mine is eb-5.2.2-thunder.zdsk)
> # cat eb-5.2.2-thunder.zdsk > /dev/fd0
>
> 8. enter /tftpboot/linux-install/diskless
> what's next????
> where do I get /dev/ram0? rdev from vmlinuz or initrd??
etherboot will load initrd from nbi image into /dev/ram0.
> 9. mv vmlinuz.nbi /tftpboot/
correct.
> what I'm doing so long is:
>
> #mknbi-linux --rootdir=172.16.15.1:/a/root --ip=172.16.15.2:172.16.15.1:172.16.15.1:ichtus:eth0 --append=nfsroot=172.16.15.1:/mnt/lvmroot/root vmlinuz initrd.img > vmlinuz.nbi
After you create snapshot with redhat-configure-netboot you will find a
files /tftpboot/linux-install/pxelinux.cfg/ with name in hex numbers
(client ip address). This is your cheatlist for parameters to create for
nbi image.
In your case it would be more like,
/usr/bin/mknbi-linux --append "noauto root=/dev/ram0 init=disklessrc
NFSROOT=172.16.15.1:/a ramdisk_size=10000 ETHERNET=eth0" vmlinuz
initrd.img > vmlinuz.nbi
You should understand that the initial root dir is ram drive, not nfs,
and "init=disklessrc" is important because it will mount nfs and
snapshot directories. Check your NFSROOT again.
Also there was some confusion with mknbi-linux binary. I found another
version of mknbi-linux in /usr/local/bin that generated images I was
unable to boot. Then I installed redhat original mknbi with "yum install
mknbi" which installed mknbi-linux in /usr/bin, that's why I write full
pathname. I don't know what's the differences. All I know that rpm
version works and the other does not.
I hope it helps.
Kaspars Melkis
http://www.isolis.lv
#mknbi-linux --rootdir=172.16.15.1:/a/root
--ip=172.16.15.2:172.16.15.1:172.16.15.1:ichtus:eth0
--append=nfsroot=172.16.15.1:/mnt/lvmroot/root vmlinuz initrd.img >
vmlinuz.nbi
>
> above I try with recompiled kernel that having
> IP kernel auto configuration in Networking options, then
> network device tlan,
> file system->network file system->nfs file system->root nfs
> compiled as built in kernel
>
> but having problem for mounting nfs root, the error messages is
> nfs server .... not responding
> nfs server .... still retrying
> nfs server .....OK
>
> so the booting running so slow
>
>
>
> On Wed, Jan 14, 2004 at 05:59:48PM +0200, Kaspars Melkis wrote:
> > Use the append feature when generating etherboot image and then it will
> > work.
> >
> > I used the following command, but you can adjust it for your
> > configuration:
> >
> > /usr/bin/mknbi-linux --append "noauto root=/dev/ram0 init=disklessrc
> > NFSROOT=192.168.0.43:/mnt/storage/diskless/fc1 ramdisk_size=10000
> > ETHERNET=eth0 SNAPSHOT=maya" \
> > vmlinuz initrd.img > kernel
> >
> > Cheers,
> >
> > Kaspars
> >
> > 2004-01-14 at 11:52, Lewi rakst??ja:
> > > I want to asking about redhat-config-netboot,
> > > I have read diskless environment manual,
> > >
> > > my conclusion is, fedora without install any other packages like k12ltsp can't serve like netboot server
> > > I look at kernel configuration default NFS_ROOT don't set
> > >
> > > system root for diskless workstation, just I copied from host installation fedora
> > > so maybe I will d/w ltsp 4.0 or k12ltsp 4.0
> > >
> > > or my conclusion is wrong???
> > >
> > >
> > > --
> > > ichtus
> > > ------
> > > Lewi Supranata .K
> > > ICQ: 50643061
> > > IPLUG Team
> > > Homepage : http://mbone.petra.ac.id/u/ichtus
> > > GnuPG Public Key : http://mbone.petra.ac.id/u/ichtus/ichtus-keys2
> > >
> >
> >
> > --
> > fedora-list mailing list
> > fedora-list at redhat.com
> > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>
> --
> ichtus
> ------
> Lewi Supranata .K
> ICQ: 50643061
> IPLUG Team
> Homepage : http://mbone.petra.ac.id/u/ichtus
> GnuPG Public Key : http://mbone.petra.ac.id/u/ichtus/ichtus-keys2
>
More information about the fedora-list
mailing list