Re: [Ltsp-discuss] ubuntu 12.04 ltsp-pnp nbd problem

2012-06-14 Thread Alkis Georgopoulos
Στις 13/06/2012 11:27 πμ, ο/η Peter D Knight έγραψε: client boots into initramfs dmesg shows unable to read squash super block added this to /etc/inetd.conf 2000stream tcpnowait nobody /usr/sbin/tcpd /usr/sbin/nbdrootd /opt/ltsp/images/i386.img Remove it, in 12.04 nbd-server is

Re: [Ltsp-discuss] ubuntu 12.04 ltsp-pnp nbd problem

2012-06-14 Thread Peter D Knight
Thanks Jan nbd server is runing fine. Removed the line from inetd.conf I wanted to try and mount the image root@peter:/etc/nbd-server/conf.d# nbd-client 127.0.0.1 2000 /dev/nbd0 Negotiation: ..size = 240MB bs=1024, sz=251707392 bytes So /dev/nbd0 is fine on the server What file type is it mount

[Ltsp-discuss] ubuntu 12.04 ltsp-pnp nbd problem

2012-06-13 Thread Peter D Knight
client boots into initramfs dmesg shows unable to read squash super block added this to /etc/inetd.conf 2000stream tcpnowait nobody /usr/sbin/tcpd /usr/sbin/nbdrootd /opt/ltsp/images/i386.img nbd-serve/ltsp_i386.conf looks good [/opt/ltsp/i386] exportname = /opt/ltsp/images/i386.img

Re: [Ltsp-discuss] ubuntu 12.04 ltsp-pnp nbd problem

2012-06-13 Thread Jan Middelkoop
Hi Peter, As of 12.04, LTSP in Ubuntu no longer uses /etc/inetd.conf for serving NBD mounts. I'd suggest removing that line. Also interesting that your /etc/nbd-server/conf.d/ltsp_i386.conf is different than mine. For me the section is called [ltsp_i386] and for you it's [/opt/ltsp/i386].

Re: [Ltsp-discuss] ubuntu 12.04 ltsp-pnp nbd problem

2012-06-13 Thread Alkis Georgopoulos
Στις 13/06/2012 11:52 πμ, ο/η Jan Middelkoop έγραψε: Also interesting that your /etc/nbd-server/conf.d/ltsp_i386.conf is different than mine. For me the section is called [ltsp_i386] and for you it's [/opt/ltsp/i386]. I wonder why that is. I added that part in upstream LTSP after 12.04 was

Re: [Ltsp-discuss] ubuntu 12.04 ltsp-pnp nbd problem

2012-06-13 Thread Peter D Knight
More info root@peter:/home/pdk# mount -t squashfs /dev/nbd0 /ltsp mount: block device /dev/nbd0 is write-protected, mounting read-only mount: /dev/nbd0: can't read superblock This maybe the problem How to solve it Peter On Wed, Jun 13, 2012 at 10:52 AM, Jan Middelkoop j...@recreatie-zorg.nlwrote: