ltsp-update-image -> 2nd dhcp

Steve Jackson sjxn at bigpond.net.au
Mon Feb 4 08:44:51 GMT 2008


I might be completely wrong, but it seems to me that the second DHCP call
will take place automatically as ifup is called as a result of the udev
rules in /opt/ltsp/i386/etc/udev/rules.d/85-ifupdown.rules. You may be able
to modify the rule concerned to call a script that does the same job as
ifup, by manually calling ifconfig and the dhclient with the port number
set. This is pure speculation on my part, I haven't tried this!

Steve



On 04/02/2008, Anton Kaser <antonkaser at gmx.net> wrote:
>
> Hi,
>
> on Wednesday, den 30.01.2008, 11:59 +0100 wrote Oliver Grawert:
> > hi,
> > On Mi, 2008-01-30 at 11:12 +0100, Anton Kaser wrote:
> > > -sudo chroot /opt/ltsp/i386 update-initramfs -u
> > did you update teh kernel package in the chroot at some point ? could
> it
> > be that update-initramfs updates teh wrong version ?
> > you can try to force the version with -k for that command, chek teh
> > version matches whats linked to as vmlinuz in the tftp dir ...
> >
>
> I checked that. 2.6.22-14 is in tftp and is created.
> vmlinuz is this version but the date is from October.
> initrd.img is todays date
>
> > also are you sure it fails at the first dhcp call and not at the
> second
> > (which happens after / was mounted and isnt related to initramfs but
> > dhclient)
>
> You are absolutely right with the 2nd dhcp - thats where i am stuck for
> month!!
> Where can I change the dhclient behaviour?
> Under Feisty it was the -p 1068 Option in the nfs-script. Then I had to
> run mkelf-linux and created
> nbi.img-2.6.22-14-386, vmlinuz-2.6.22-14-386 and
> initrd.img-2.6.22-14-386 ( with Feisty kernel numbers)
>
> Now it seems only initrd.img-2.6.22-14-386 is changed:
>
> root at edubuntu:/var/lib/tftpboot/ltsp/i386# ls -l
> -rw-r--r-- 1 root root   75391 2007-10-15 03:35 config-2.6.22-14-386
> lrwxrwxrwx 1 root root      24 2008-01-30 16:06 initrd.img ->
> initrd.img-2.6.22-14-386
> -rw-r--r-- 1 root root 4420981 2008-01-30 16:05 initrd.img-2.6.22-14-386
> lrwxrwxrwx 1 root root      21 2008-01-30 16:06 nbi.img ->
> nbi.img-2.6.22-14-386
> -r--r--r-- 1 root root 6114946 2007-12-12 22:06 nbi.img-2.6.22-14-386
> -rw-r--r-- 1 root root   13552 2007-12-21 14:05 pxelinux.0
> drwxr-xr-x 2 root root    4096 2007-12-12 22:06 pxelinux.cfg
> lrwxrwxrwx 1 root root      21 2008-01-30 16:06 vmlinuz ->
> vmlinuz-2.6.22-14-386
> -rw-r--r-- 1 root root 1696312 2007-10-15 03:35 vmlinuz-2.6.22-14-386
>
> Booting up to the second dhcp-request works fine.
>
> How does the client get a ip at the 2nd step????????
>
> thanks toni
>
> ps
>
> a part of the dhcp.conf. - maybe this gives any clou:
>
> option option-128 code 128 = string;
> option option-129 code 129 = text;
>
> subnet 192.168.2.0 netmask 255.255.255.0 {
>   range 192.168.2.80 192.168.2.99;
>   option domain-name "kaser.local";
>   option domain-name-servers 192.168.2.1;
>   option broadcast-address 192.168.2.255;
>   option routers 192.168.2.10;
>   option subnet-mask 255.255.255.0;
>   option option-128 e4:45:74:68:00:00;
>   option option-129 "DPORT=1067";
>   next-server 192.168.2.10;
>
>   if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
>     filename "/ltsp/i386/pxelinux.0";
>   }
>   else{
>     filename "/ltsp/i386/nbi.img";
>   }
>   option root-path "192.168.2.10:/opt/ltsp/i386";
>
>
> --
> edubuntu-users mailing list
> edubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/edubuntu-users/attachments/20080204/7a30b8d4/attachment.htm 


More information about the edubuntu-users mailing list