Martin,
Are you certain that the workstation knows it's own hostname?
If the workstation doesn't know its hostname, then it won't be able to
read the specific sections from the lts.conf file.
Try setting: SCREEN_01 = shell
and boot the client. If you get a bash prompt, then type: hostnam
Hi - I'm a newbie to using ltsp.
I run SuSE 10.0 OSS on a Celeron-600 with 384MB RAM.
Recently I installed ltsp and have managed to get two workstations (both
P1-120MHz) up and running, but not very well.
One of them [assigned ws002 by DHCP] has Windows 98 installed on the
Hard Disk, and an
Hi,
I dug my fingers into a SUSE 10 LTSP server a colleague had set up, and
had some sweaty moments when all terminals only gave a TFTP boot timeout
after rebooting.
It turned out that I couldn't simply make 'reboot' from (Kterm) bash, as
I believe I could back on the SUSE 9.3 server, but had to
Hello,
Lately Ive been having a problem where gnome-vfs-daemon hangs for a user
and they effectively cannot use their user account. Even as root I seem
be completely unable to kill this process regardless of the signal, so I
am forced to reboot to fix a single user account which is major
inc
On 14/03/06, Werner Winter <[EMAIL PROTECTED]> wrote:
> Hello,
> I'm running a ltsp-server 3.0 and two nets: 192.168.0.0 and 192.168.2.0
> The terminals from the 0.0-net are booting without any problem. When I try
> to start the terminals from the 2.0-net they boot but stop on the grey
> screen wit
Hello Jim,
For those clients in the 192.168.2.x subnet, you'll need to set:
SERVER =
I did this already but it doesn't work :-(
--
Werner
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends
Werner,
For those clients in the 192.168.2.x subnet, you'll need to set:
SERVER =
in your lts.conf file. Make sure the 'ipaddr_of_server' is the address
from the 192.168.2.x subnet.
It already defaults to 192.168.0.254, but your clients in the other
subnet probably can't get to that
Hello,
I'm running a ltsp-server 3.0 and two nets: 192.168.0.0 and 192.168.2.0
The terminals from the 0.0-net are booting without any problem. When I try
to start the terminals from the 2.0-net they boot but stop on the grey
screen with the X. In /var/log/messages I get:
tserver kdm: server o
Hi All :)
I would like to know if it is possible to use nautilus instead of
Konqueror when i want to access to my USB drive on my ltsp client ?
Indeed, i know it is samba but it doesn't work. Maybe i do it wrong...
Plus in konqueror, i should refresh 2 times to access to the drive each
time i go i
Hi All :)
I would like to know if it is possible to use nautilus instead of
Konqueror when i want to access to my USB drive on my ltsp client ?
Indeed, i know it is samba but it doesn't work. Maybe i do it wrong...
Plus in konqueror, i should refresh 2 times to access to the drive each
time i go i
Am Montag, den 13.03.2006, 21:12 -0400 schrieb Timothy Legge:
> Andrew wrote:
> > My gigabit subnet has finally given up. I am getting the following
> > message repeated all the time:
> >
> > r8169: eth1: Reset RTL8169s PHY
> >
> > Does anyone know what I need to do?
>
> Try a complete power do
11 matches
Mail list logo
