Hi Alkis:

Thanks for your prompt reply.  I will indeed try the freenode link.   
However, here is the current situation:
1) The rootserver was already 192.168.0.1
2) and so was the nbdserver; it was exactly like your text!
3) For completeness sake, I retyped the bootmessages on the client for 
so far they did not roll away.  Here they are:
---------------------
.
.
.
Loading vmlinuz...............................
Loading initrd.img............................ready
[    5.821127] IO APIC resources could not be allocated.
Loading, please wait...
IP-Config: eth0 hardware address 00:50:ba:5e:79:4c mtu 1500 DHCP RARP
IP-Config: eth0 complete (from 192.168.0.1):
  address: 192.168.0.21        broadcast:    192.168.0.255    netmask: 
255.255.255.0
  gateway: 192.168.0.1        dns0     :  192.168.0.1        dns1   : 
0.0.0.0
  domain : example.com
  rootserver: 192.168.0.1  rootpath: /opt/ltsp/i386
  filename  : /ltsp/i386/nbi.img
Error: Connect: Connection refused
mount: mounting /rofs on /root/rofs failed: Invalid argument
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init
No init found. Try passing init= bootarg.

Busybox v1.10.2 ...etc...
(initramfs)
----------------------------------------------------

4)  Note: I observed that the 192.168.0.21 address matched the inet 
address on the client (ifconfig on BusyBox). It probably was internally 
configured.
5)  The key to the final solution may well be in the last two boot 
messages:   "No init found"  Do you have an idea about that?   I also 
perused all the log files on the server.  But, with my layman's 
knowledge, nothing specific jumped at me  -- - anyway that may have been 
the wrong place to look.   Would BusyBox be useful for troubleshooting?

Thanks again,
 Jack

Alkis Georgopoulos wrote:
> Hi Jack,
>
> no need for chatzilla, pointing your browser to
> http://webchat.freenode.net/?channels=ltsp gets you directly to the chat
> room (javascript-based). But as you said, you made great progress, so it
> might not be necessary. Now your tftp server and your dhcp3-server are
> (mostly?) working...
>
>   
>> IP-Config: eth0 complete (from 192.168.0.1) ... rootserver ...
>>     
>
> What is the rootserver ip in that exact line? It should be the same as
> your LTSP server, i.e. 192.168.0.1.
>
> If it is, then maybe your also changed the configuration file for your nbd 
> server. :(
> See how it's supposed to be:
>
> alk...@alkis:~$ grep nbd /etc/inetd.conf
> 9572                  stream  tcp     nowait  nobody /usr/sbin/tcpd 
> /usr/sbin/nbdswapd
> 2000               stream  tcp            nowait  nobody /usr/sbin/tcpd 
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
>
>

-- 
LTSP on top of Ubuntu 8.10 desktop does not boot
https://bugs.launchpad.net/bugs/316217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to