On Tue, Jul 05, 2011 at 09:36:28PM +0200, Frank Lienhard wrote:
> So here is what I did:
> I installed the ltsp-server-standalone package from the Lenny repos. used
> the 'ltsp-build-client' command, which finished with a success
> message
> I edited /etc/dhcp3/dhcpd.conf and /etc/ltsp/dhcpd.conf a
Στις 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
Thanks, Alkis. I'm looking forward to trying these fixes.
db
2011/7/6 Άλκης Γεωργόπουλος :
> On Wed, Jul 6, 2011 at 7:44 PM, David Burgess wrote:
>> 2. The CPU frequency scaling governor is set to Performance by
>> default. The /etc/init.d/ondemand file exists in the chroot, but the
>> governor
On Wed, Jul 6, 2011 at 7:44 PM, David Burgess wrote:
> 2. The CPU frequency scaling governor is set to Performance by
> default. The /etc/init.d/ondemand file exists in the chroot, but the
> governor does not change, even after the 60-second sleep period and
> I'm not sure why.
Ubuntu/LTSP disabl
Ubuntu 10.10 amd64 (fat) client and server
1. I installed hplip in my chroot, trying to mimic a full Ubuntu
desktop installation that was in use on my client. When I launch
System>Administration>Printing on my booted fat client, the Printing
app opens with the title "Printing - 192.168.85.16", whi
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
>
> Try running this on the server as root:
> ltsp-update-sshkeys
>
What confuses me is, that according to:
https://help.ubuntu.com/community/HowToCookEdubuntu/Chapters/LTSPManagement
the command should return messages about creating new ssh-keys, which in
my case isn't the case.
and I figure
> 1) You don't understand LTSP
>
No correct that way. More correct is: I was unable get my question right.
And I got one thing wrong: the consoles F1-F6 are running locally on the
Terminal, which leads me to the wrong conclusion about the source of the
problem ("no home dir for user ")
> 2) Y
>
> LTSP is complex and tricky. If I were offering advice I'd say install a
> recent UBUNTU and configure ltsp. That is easy to follow the recipe.
>
>
Oh yes that will help keeping the users and configurations ;-)
--
Hi Jordan,
thank you for answer :-)
2011/7/5 Jordan Erickson :
> This is just a shot in the dark, but if you have remote syslog setup in
> lts.conf, disable it - I've had that issue before after a couple/few
> systems are booting, others will time out.
I don't have enabled rsyslog in my lts.con
On 06/07/2011, at 1:49 PM, ltsp-discuss-requ...@lists.sourceforge.net wrote:
> Alkis Georgopoulos wrote:
>> 05-07-2011, ? ???, ??? ??? 21:36 +0200, ?/? Frank Lienhard
>> ??:
>>
>>> My client boots (with a kernel image from rom-o-matic), I get a login
>>> screen.
>>> But no user is
>> No, I have to confirm to add the machine to the knownhosts and to give
>> the passwd for the user
>>
>
> If you have to confirm that, then
> 1) I wonder why ltsp-update-sshkeys that highvoltage proposed didn't
> work for you.
I followed the hints from Alkis several times:
2b) If you see
>
> If you have to confirm that, then
> 1) I wonder why ltsp-update-sshkeys that highvoltage proposed didn't
> work for you.
here is my sshd_config from the server (only lines without #):
(maybe here are some left over modifications from other things I did..)
-snip---
Port
16 matches
Mail list logo
