Lanman,
When the users log in via a LTSP workstation, they are logging
into the server. they've got the full resources of the
server at their disposal.
It's the workstation itself that can only see /opt/ltsp/i386.
If you want to restrict the users to a certain subdirectory,
you might look at u
Dear LTSP List; Having just joined this list, I find myself
in need of some basic info. I'm running LTSP 3.0 on a
Mandrake 9.0 server. As with any typical install, LTSP is
installed in the "/opt/ltsp/i386" folder. Using Webmin,
I've created users for LTSP, and pointed their home folders
to "/opt/lt
I have been having difficulty in using ssh to contact the clients, and I believe
it is because of a faulty NIS installation. I've solved several (thousand)
errors which were mostly my fault, and now am down to what I believe is the
final error. Upon running ssh to a client, I get the response:
[
I've just done something very similar - replaced RedHat 8 on my LTSP 3
server with Fedora Core 1 and LTSP 4. Getting X working was the usual
nightmare of 'which of the 27 config files have I forgotten this time?'
but it's all working now.
I too noticed that I couldn't telnet from a ws to the serve
Am Sonntag, 28. Dezember 2003 19:40 schrieb Clodoaldo Pinto Neto:
> (I'm not good enough with Linux) I had to do a reinstall. This time
> the most current distro I had at hand was Fedora Core 1. So I
> installed it and as I was doing it all fresh why not try the new
> LTSP 4.0?
If you want to use
Hello,
I was running LTSP in a Mandrake 9.1 server and 3 workstations. Local
application [EMAIL PROTECTED] It was working fine until 2 days ago when the server
motherboard died. Causa mortis: stuffed capacitors.
Since I could not make the installed system work with another board (I'm not
good eno
