Alkis Georgopoulos wrote:
> Στις 06-07-2011, ημέρα Τετ, και ώρα 22:09 +0200, ο/η Frank Lienhard
> έγραψε:
>
>> Honestly: How to check?
>>
>
> >From SCREEN_08=shell on the client, run:
> grep nbd /proc/mounts
>
> If you see a line like
> /dev/nbd0 /rofs squashfs ro,relatime 0 0
> in the
Στις 06-07-2011, ημέρα Τετ, και ώρα 22:09 +0200, ο/η Frank Lienhard
έγραψε:
> Honestly: How to check?
>From SCREEN_08=shell on the client, run:
grep nbd /proc/mounts
If you see a line like
/dev/nbd0 /rofs squashfs ro,relatime 0 0
in there, then you're using NBD.
I'm not using Debian LTSP f
Alkis Georgopoulos wrote:
> Στις 06-07-2011, ημέρα Τετ, και ώρα 14:09 +0200, ο/η Frank Lienhard
> έγραψε:
>
>> ltsp-update-sshkeys
>> followed by
>> ltsp-update-image
>>
>> and TADA tha does the trick!
>>
>
> Debian serves the chroot with NFS by default.
> Ubuntu serves the chroot with NBD
Alkis Georgopoulos wrote:
> Στις 06-07-2011, ημέρα Τετ, και ώρα 14:09 +0200, ο/η Frank Lienhard
> έγραψε:
>
>> ltsp-update-sshkeys
>> followed by
>> ltsp-update-image
>>
>> and TADA tha does the trick!
>>
>
> Debian serves the chroot with NFS by default.
> Ubuntu serves the chroot with NBD
Στις 06-07-2011, ημέρα Τετ, και ώρα 14:09 +0200, ο/η Frank Lienhard
έγραψε:
> ltsp-update-sshkeys
> followed by
> ltsp-update-image
>
> and TADA tha does the trick!
Debian serves the chroot with NFS by default.
Ubuntu serves the chroot with NBD by default.
ltsp-update-image is only applicable to
Jonathan Carter (highvoltage) wrote:
> Hi Frank
>
> On 05/07/11 03:36 PM, Frank Lienhard wrote:
>
>> My client boots (with a kernel image from rom-o-matic), I get a login
>> screen.
>> But no user is able to log in.
>> I changed to text console (F1) on the thinclient and get an error
>> messag
On Fri, 31 Oct 2008 09:03:21 +0100
Verner Kjærsgaard <[EMAIL PROTECTED]> wrote:
> What/where would that (etc/rc.local) be on a SuSE11 box?
I don't think there is one. /etc/init.d/boot.local is the closest thing to it,
but it does its stuff first instead of last so it's not the same.
Someone who
Frank Cox skrev:
> On Thu, 30 Oct 2008 17:17:40 -0400
> bjc <[EMAIL PROTECTED]> wrote:
>
>> Others have mentioned this problem on this list and suggest
>> running two commands to fix the situation; ltsp-update-sshkeys followed by
>> ltsp-update-image -a i386. This works for me, but only until I
On Thu, 2008-10-30 at 17:16 -0700, Vagrant Cascadian wrote:
> On Thu, Oct 30, 2008 at 05:17:40PM -0400, bjc wrote:
> > Each time I reboot my ltsp-server, ldm refuses to log users into the
> > clients. I get the message "this workstation isn't authorized to connect
> > to server".
>
> is the server
On Thu, Oct 30, 2008 at 05:17:40PM -0400, bjc wrote:
> Each time I reboot my ltsp-server, ldm refuses to log users into the
> clients. I get the message "this workstation isn't authorized to connect
> to server".
is the server getting it's primary ip address via dhcp and getting a different
addres
On Thu, 30 Oct 2008 17:17:40 -0400
bjc <[EMAIL PROTECTED]> wrote:
> Others have mentioned this problem on this list and suggest
> running two commands to fix the situation; ltsp-update-sshkeys followed by
> ltsp-update-image -a i386. This works for me, but only until I reboot my
> server. The situ
Hi,
Each time I reboot my ltsp-server, ldm refuses to log users into the
clients. I get the message "this workstation isn't authorized to connect
to server".
Others have mentioned this problem on this list and suggest
running two commands to fix the situation; ltsp-update-sshkeys followed by
ltsp
12 matches
Mail list logo
