Krishna Murphy wrote:
>> Alfred Nutile wrote:
>>> What if it only shows ws001 and not the :0? I am having some trouble
>>> getting KDM to recognize each terminal and apply per terminal log in
>>> settings as you mentioned on another site.
>>> Thought this may be why?
>>>
>>
>> if 'echo $DISPLAY'
> Alfred Nutile wrote:
>> What if it only shows ws001 and not the :0? I am having some trouble
>> getting KDM to recognize each terminal and apply per terminal log in
>> settings as you mentioned on another site.
>> Thought this may be why?
>>
>
> if 'echo $DISPLAY' is showing just 'ws001', withou
Alfred Nutile wrote:
> What if it only shows ws001 and not the :0? I am having some trouble
> getting KDM to recognize each terminal and apply per terminal log in
> settings as you mentioned on another site.
> Thought this may be why?
>
if 'echo $DISPLAY' is showing just 'ws001', without t
What if it only shows ws001 and not the :0? I am having some trouble
getting KDM to recognize each terminal and apply per terminal log in
settings as you mentioned on another site.
Thought this may be why?
Jim McQuillan wrote:
> Sounds like your DISPLAY environment variable isn't set correctly.
?
> Original Message
> Subject: Re: [Ltsp-discuss] Local Hardware
> From: Jim McQuillan <[EMAIL PROTECTED]>
> Date: Mon, June 26, 2006 1:40 pm
> To: [EMAIL PROTECTED]
> Cc: ltsp-discuss@lists.sourceforge.net
>
> [EMAIL PROTECTED] wrote:
> > I g
Do you have something different in your setup?
Jim McQuillan
[EMAIL PROTECTED]
>
>> Original Message ----
>> Subject: Re: [Ltsp-discuss] Local Hardware
>> From: Jim McQuillan <[EMAIL PROTECTED]>
>> Date: Mon, June 26, 2006 1:27 pm
>> To: [
I get nothing when I that on the client. Also should I be running the
lbus command on the server or client? Either way, I don't get anything
when I type echo $DISPLAY on my client's shell (which is screen_02).
> Original Message
> Subject: Re: [Ltsp-discuss
Sounds like your DISPLAY environment variable isn't set correctly.
at the shell prompt, type this:
echo $DISPLAY
see what that produces. It should be something like:
ws001:0.0
Jim McQuillan
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
> Ok, does anyone know why when I run:
>
> sh /et
Ok, does anyone know why when I run:
sh /etc/X11/xinit/xinitrc.d/lbus-start.sh
I get this:
Use of uninitialized value in substitution (s///) at /usr/sbin/lbussd
line 46.
Use of uninitialized value in concatenation (.) or string at
/usr/sbin/lbussd line 62.
Couldn't establish a connection to :92
From the command prompt, enter:
# modprobe ide-disk
This will give you /dev/hda.
Mount as normal.
Kent
> How do you get access to Local Hardware on an LTSP terminal like a Hard
> Drive?
>
> --
> Leigh Martell
>
> QUOTE OF THE WEEK:
> Experience is not what happens to you; it is what you
Leigh Martell wrote:
How do you get access to Local Hardware on an LTSP terminal like a Hard
Drive?
Short Answer:
Depends.
Long Answer:
The harddrives can be accessed (on the workstation) as /dev/hd* after
loading the right modules (ide-disk ??). That way, only local_apps (aka
programs running o
How do you get access to Local Hardware on an LTSP terminal like a Hard
Drive?
--
Leigh Martell
QUOTE OF THE WEEK:
Experience is not what happens to you; it is what you do with what happens
to you.
-- Aldous Huxley
---
This SF.
12 matches
Mail list logo
