Hello Gregor, [...] GW> with the kernel works fine. But then LTSP tries to insmod 8139too.o, GW> successfully. After that following output appears: GW> eth0: RealTek RTL8139 Fast Ethernet at 0xc2807000, 00:c1:26:0b:1f:e8, IRQ 11 [...] GW> Mounting root filesystem: /opt/ltsp/i386 from: 192.168.0.254 GW> But nothing happens...
GW> Here are some definitions from my dhcpd.conf: GW> option subnet-mask 255.255.255.0; GW> option broadcast-address 192.168.0.255; GW> option routers 192.168.0.254; GW> option domain-name-servers 192.168.0.254; GW> option domain-name "ltsp-server"; GW> option root-path "192.168.0.254:/opt/ltsp/i386"; GW> OK, normally, in my local network, the fixed IP-address of my server is GW> 192.168.0.1... should I change the settings above? Is there any computer with that IP 192.168.0.254 ? Else it will hardly work... Of course in that case you need to change. [...] GW> I thought that my root-system isn't exported well, but there seems to be GW> everything OK (/etc/exports): GW> ## LTS-begin ## GW> # GW> # The lines between the 'LTS-begin' and the 'LTS-end' were added GW> # on: Son Dez 8 20:28:57 CET 2002 by the ltsp installation script. GW> # For more information, visit the ltsp homepage GW> # at http://www.ltsp.org GW> # GW> /opt/ltsp/i386 192.168.0.0/255.255.255.0(ro,no_root_squash) GW> /var/opt/ltsp/swapfiles 192.168.0.0/255.255.255.0(rw,no_root_squash) well, looks ok to me. GW> The root-directry /opt/ltsp/i386/root is empty. Is this the problem? But what GW> should be in there? Can anybody give some hints where the problem is now? AFAIK, that's unimportant. That directory should only contain the personal stuff and so for the user root, and as root will probably not login "locally" at the workstations (I mean, not in text-based console mode) and so he will not access that directory, it may (should) be empty. GW> Thanks! One comment: When we started implementing our "room 5" computer lab, we found out that one of the two nfs-servers delivered with debian 3 does not work well. Cannot remember wether it was user-space or kernel daemon as a co-worker treated that problem and told me afterwards, and no ssh-access during holidays :-( You could check this, but first go and look if it's a problem on the IP-Adress (which is quite probable here). Giving away a lot of coins, 0,02 Euro each, "merry & happy...", Anselm mailto:[EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
