[K12OSN] hotplug issue

norbert bear2bar at netscape.net
Sun Dec 5 14:40:18 UTC 2004


eharrison at mail.mesd.k12.or.us wrote:

> On Sat, 4 Dec 2004, norbert wrote:
>
>>>>> Are you referring to this?
>>>>> http://pxes.sourceforge.net
>>>>
>>>>
>>>
>>>> Yes that's the CD I'm using however I'm using K12ltsp on the server..
>>>
>>>
>>>
>>> If you are using pxes, client-side problems probably need to be
>>> reported to the pxes folks.
>>>
>>> PXES *replaces* the K12LTSP client boot process, having K12LTSP on
>>> the server doesn't really matter in this case.
>>>
>>> Hopefully that makes sense ;-)
>>>
>
>
>> The problem is specific ot 4.2 since the CD work fine with both 4.0.1 
>> & 4.1.1 therefore I must conclude that something has changed on the 
>> server side ???? But as I mentionned in my last email I'm getting the 
>> same problem with a boot floppy also.....
>>
>> .....and that doesn't make sense :-D
>
>
> In LTSP/K12LSTP, the client uses BOOTP/PXE to download a kernel and
> an initial ram disk. The initial ram disk contains software to NFS
> mount the server and to execute the LTSP software via NFS. The X
> server the client runs, for example, is located on the NFS share.
>
> PXES is self-contained, the boot image contains all of the software
> needed, including the X server. NFS is not used at all (and since
> the LTSP software is *only* on NFS, PXES never uses the LTSP software).
>
> When you boot via floppy, are you using a LTSP or a PXES image?
> If you are getting hotplug errors, it must be PXES since LTSP does
> not include hotplug...
>
> Could you post your /etc/dhcpd.conf? That'll help us figure out exactly
> what software is running.
>
> -Eric
>
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>

Hi Eric,

Thanks for the explaination, here is the dhcpd.conf file...

# Sample configuration file for ISCD dhcpd
#
# Don't forget to set run_dhcpd=1 in /etc/init.d/dhcpd
# once you adjusted this file and copied it to /etc/dhcpd.conf.
#

default-lease-time            21600;
max-lease-time                21600;
ddns-update-style none;
allow booting;
allow bootp;

option subnet-mask            255.255.255.0;
option broadcast-address      192.168.0.255;
option routers                192.168.0.252;
option domain-name-servers    192.168.0.252;
option domain-name            "ltsp";
option root-path              "192.168.0.252:/opt/ltsp/i386";
option option-128 code 128 = string;
option option-129 code 129 = text;

shared-network WORKSTATIONS {
  subnet 192.168.0.0 netmask 255.255.255.0 {
     range dynamic-bootp 192.168.0.200 192.168.0.250;
     use-host-decl-names       on;
     option log-servers        192.168.0.252;

     # trick from Peter Rundle <peter.rundle at au.interpath.net>
     if substring (option vendor-class-identifier, 0, 9) = "PXEClient"
     {
        filename      "/lts/pxe/pxelinux.bin";
          # NOTE: kernels are specified in /tftpboot/lts/pxe/pxelinux.cfg/
     }
     else
     {
        filename    "/lts/vmlinuz.ltsp";
     }
  }
}

# example configurations for specifying specific kernels to specific clients
#group    {
#    use-host-decl-names       on;
#    option log-servers        192.168.0.252;

#    host ws001 {
#        hardware ethernet     00:E0:06:E8:00:84;
#        fixed-address         192.168.0.1;
#        filename              "/lts/vmlinuz.ltsp";
#        option option-128 e4:45:74:68:00:00;
#        option option-129 "NIC=3c509";
#    }
#    host ws002 {
#        hardware ethernet     00:D0:09:30:6A:1C;
#        fixed-address         192.168.0.2;
#        filename              "/lts/vmlinuz.ltsp";
#        option option-128 e4:45:74:68:00:00;
#        option option-129 "NIC=ne";
#    }
#    host ws003 {
#        hardware ethernet     00:D0:09:30:28:B2;
#        fixed-address         192.168.0.3;
#        # kernels are specified in /tftpboot/lts/boot/pxe/pxelinux.cfg/
#        filename              "/lts/boot/pxe/pxelinux.0";
#    }
#}  
group {
    use-host-decl-names       on;
    option log-servers        192.168.0.252;

    host hp2200 {
        hardware ethernet     00:01:e6:99:3b:22;
        fixed-address         192.168.0.253;
    }

    host ws001 {
        hardware ethernet     00:60:08:68:4c:d9;
        fixed-address         192.168.0.1;
        filename              "/lts/vmlinuz.ltsp";

    }
    host ws002 {
        hardware ethernet     00:10:4b:2a:b7:36;
        fixed-address         192.168.0.2;
        filename              "/lts/vmlinuz.ltsp";
    }
    host ws003 {
        hardware ethernet     00:10:4b:93:ca:21;
        fixed-address         192.168.0.3;
        filename              "/lts/vmlinuz.ltsp";
    }
    host ws004 {
        hardware ethernet     00:60:97:D0:2E:D7;
        fixed-address         192.168.0.4;
        filename              "/lts/vmlinuz.ltsp";
    }

    host ws005 {
        hardware ethernet     00:10:4b:23:18:86;
        fixed-address         192.168.0.5;
        filename              "/lts/vmlinuz.ltsp";
    }
    host ws006 {
        hardware ethernet     00:60:97:93:fc:74;
        fixed-address         192.168.0.6;
        filename              "/lts/vmlinuz.ltsp";
    }
   host ws007 {
        hardware ethernet     00:60:97:36:ff:91;
        fixed-address         192.168.0.7;
        filename              "/lts/vmlinuz.ltsp";
    }
   host ws008 {
        hardware ethernet     00:60:08:CF:0D:F5;
        fixed-address         192.168.0.8;
        filename              "/lts/vmlinuz.ltsp";
    }

    host ws009 {
        hardware ethernet     00:60:08:16:bd:89;
        fixed-address         192.168.0.09;
        filename              "/lts/vmlinuz.ltsp";

    }
    host ws010 {
        hardware ethernet     00:10:5A:E4:CC:33;
        fixed-address         192.168.0.10;
        filename              "/lts/vmlinuz.ltsp";
    }
    host ws011 {
        hardware ethernet     00:10:4b:94:4C:BC;
        fixed-address         192.168.0.11;
        filename              "/lts/vmlinuz.ltsp";
    }
    host ws012 {
        hardware ethernet     00:60:08:99:e5:4e;
        fixed-address         192.168.0.12;
        filename              "/lts/vmlinuz.ltsp";
    }

    host ws013 {
        hardware ethernet     00:c0:f0:4c:b3:20;
        fixed-address         192.168.0.13;
        filename              "/lts/vmlinuz.ltsp";
    }
    host ws014 {
        hardware ethernet     00:60:97:e0:da:72;
        fixed-address         192.168.0.14;
        filename              "/lts/vmlinuz.ltsp";
    }
    host ws015 {
        hardware ethernet     00:60:97:07:b5:39;
        fixed-address         192.168.0.15;
        filename              "/lts/vmlinuz.ltsp";
    }
    host ws016 {
        hardware ethernet     00:50:DA:1A:70:0C;
        fixed-address         192.168.0.16;
        filename              "/lts/vmlinuz.ltsp";
    }
    host ws017 {
          hardware ethernet     00:60:08:17:1F:96;
        fixed-address         192.168.0.17;
        filename              "/lts/vmlinuz.ltsp";
    }
    host ws018 {
    hardware ethernet     00:60:08:16:bd:6e;
        fixed-address         192.168.0.18;
        filename              "/lts/vmlinuz.ltsp";
    }
    host ws019 {
        hardware ethernet     00:50:04:13:c1:b4 ;
        fixed-address         192.168.0.19;
        filename              "/lts/vmlinuz.ltsp";
    }
    host ws020 {
        hardware ethernet     00:50:FC:72:46:56;
        fixed-address         192.168.0.20;
        filename              "/lts/vmlinuz.ltsp";
    }
}

Hope that this will lead to an answer....


thks
norbert




More information about the K12OSN mailing list