> There is a difference in performance but not as much as I
> would have thought. The Graphics card has a lot to do with
> things. I suspect the NIC would change things as well if
> you could find a 100Mbit NIC for an ISA box.
You won't find a 100Mbit ISA NIC. If i recall c
This looks very promising. My only initial concern: how easy would it be
to run an OS other than Linux on the server? I've been using LTSP since
the 2.x days and it has always been fairly easy to make it work on the
OpenBSD server we have here. I'm guessing this concern would be similar
to inst
At one time i had [EMAIL PROTECTED] running on the LTSP clients. I had NFS swap
enabled, so the machines already had some writeable storage. Within the
NFS swap area, i created a directory for each system. So the path (from
the client's perspective) was something like /tmp/swapfiles/ws001
(wher
A few weeks ago someone linked to this page that displays a penguin with
a progress bar as the client boots, rather than the usual scrolling
messages: http://wiki.ltsp.org/twiki/bin/view/Ltsp/BootsplashPatch
Today i finally got around to trying it (on a DisklessWorkstations.com
Jammin 125). It
On my setup i have very restrictive firewall rules so that the server is
well protected. Then in my firewall rule set i list the clients and
give them full access to all TCP and UDP ports. I don't consider it an
optimal solution (better would be to only allow the specific ports that
are needed,
I have compiled IceWM and am playing with it, since based on feedback
from this list, it will do more of what i want than Blackbox. However,
i've noticed that simple things like loading IceWM or changing the
theme take a surprisingly long time (varies between 4 and 6 minutes!).
Previously when
I'm setting up LTSP 4.1 to be used as web terminals running Firefox.
Right now i'm using the Blackbox window manager, but i'm having trouble
figuring out a way to get Firefox to start maximized. Some of the
Googling i've done indicates that this is a window manager issue.
Blackbox does not allo
; set in your lts.conf file.
>
>Also, keep in mind the J-125 only has 32 or 64mb of ram, and the cpu
> is a whimply little 300mhz thing. The newer workstations are MUCH
> more powerful for this type of thing.
>
>Jim McQuillan
>[EMAIL PROTECTED]
>
>On Tue, 1 Feb 2005, D
will spit out WAY more info than you need, but give
> it a try, and see what it shows. usually, the last 100 or so lines
> will give a pretty good idea of what it was doing when it failed.
>
>Jim McQuillan
>[EMAIL PROTECTED]
>
>On Tue, 1 Feb 2005, Daniel Ramaley wrote
system. It took a while to get all the libraries, but 'ldd'
>and 'strace' are your friend, when figuring out the required libs and
>config files.
>
>Jim McQuillan
>[EMAIL PROTECTED]
>
>On Tue, 1 Feb 2005, Daniel Ramaley wrote:
>> Is there a canonical w
Is there a canonical way to do local applications with LTSP 4.1? With
LTSP 3 there were local_apps and local_netscape packages that made it
relatively easy. I see no equivalent packages as part of LTSP 4.1. I
want to get Firefox running as a local app. I've started working on it,
but Firefox re
This document describes how i made a web terminal with Linux Terminal
Server Project 2.09pre3 using OpenBSD as the server. If i can find time to
do so, i may use what i learned to modify the LTSP install scripts to
support OpenBSD. This document contains data customized to my situation,
such as th
I have a test network configured with LTSP 2.09pre3. The test network
consists of an LTSP client and two servers, one for DHCP and DNS, the other
for TFTP and NFS. I wanted 2 separate servers to mirror the production
configuration. Everything works wonderfully on the test network. When i
installed
I'm trying to get LTSP 2.09pre3 set up with local apps, but X always dies
with errors such as:
(WW) Warning, couln't open module XFree86
(II) UnloadModule: "XFree86"
(EE) Failed to load module "XFree86" (module does not exist, 0)
Below i've included my ltsp.conf and the full X error log
(/var/lo
14 matches
Mail list logo
