On Sun, Oct 21, 2012 at 09:22:39PM +0200, Daniel Brockmann wrote:
> I set up a LTSP server for the first time and it works so far: I can log on, I
> can change lts.conf settings and see the change after rebooting.

What distro? What version of LTSP? On recent versions, "ltsp-info" should be 
able to tell you this information.

 
> But one thing would not work on my thin client (Winestra 4210): I cannot 
> access
> the local CF-card-driven IDE hard drive. USB thumbdrives work well so far. The
> CF/IDE HDD was formated with two FAT 16 partitions using a live Ubuntu system 
> -
> so it's proven that it is working at all, at least.
> 
> Here's the lts.conf :
 
> # Enables access to locally connected storage devices
> MODULE_01 = "ide_generic"
...
> MODULE_07 = "sd_mod"
> LOCALDEV = true
> HOTPLUG = y
> LOCAL_STORAGE = y
> ALLOW_UNKNOWN_USB = y
> LOCAL_DEVICE_01 = /dev/hda:hda
...
> LOCAL_DEVICE_08 = /dev/sdd:sdd

You shouldn't need any of these variables defined in lts.conf for any recent 
(5.x) version of LTSP.

Try using "ltsp-localapps xterm", which should bring up an xterm running on 
your actual thin client hardware, and then check if your devices are visible 
using lsmod, dmesg, etc.

Alternately, you can get a passwordless root shell by setting SCREEN_02=shell 
and SCREEN_07=ldm in lts.conf, and then pressing ctrl-alt-f2 and ctrl-alt-f7 
should switch between them, respectively.

These instructions presume you're running a version of LTSP released in the 
last 6 years or so, i.e. 5+. :)


live well,
  vagrant

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to