[EMAIL PROTECTED] wrote:
>
> Marcus,
>
> Luckily, this is easy to fix.
>
> You need to increase the maximum number of filehandles
> and open inodes.
>
> And, you can do it while the system is running and it takes
> effect immediately.
>
> Try this:
>
> echo 24576 >/proc/sys/fs/file-max
> ec
Patrick,
I have the Cirrus GD5424 chip in a bunch of workstations. It took a while to
figure out and the best I could get from it was 8-bit color. We do use them
daily, and they are fine for star office, web browsing, e-mail, etc. but any
high color graphics look bad. You shouldn't have any tr
On Wednesday 20 February 2002 09:27, Nick Sklav scribbled:
> Hi Guys
>
> Is there a way to disable console blanking on the workstations by passing
> parameters.
Try putting "xset s off" in your xinitrc config file.
--
Neil Brideau,
As Will Rogers would have said, "There is no such things as a
Nick,
Maybe add 'setterm -blank 0' to the rc.local script.
I'm not sure if that will do it, while running X,
but it's worth a shot.
Jim McQuillan
[EMAIL PROTECTED]
On Wed, 20 Feb 2002, Nick Sklav wrote:
> Hi Guys
>
> Is there a way to disable console blanking on the workstations by passing
Indeed, the card seems to have a negative feedback on the web ;-( do you
think onw can override the onboard card with any other one (Matrox or
S3?) that I may have lying around, and for which XFree has got decent
drivers?
/Patrick
On Wed, 2002-02-20 at 23:07, Egan, Matt B. (Artco) wrote:
> You m
Hi,
I have an opportunity to acquire, for a decent price, the following
system to serve as a diskless station can someone tell me if it is worth
the money:
Unisys type CWD4002-ZE
486DX100
2 X SIMM skts to total 64mg ( I think they have 32 in @ present
On board NE2000 ( They work fine with 3C509
Hi Guys
Is there a way to disable console blanking on the workstations by passing parameters.
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-disc
> From: "Dyg It" <[EMAIL PROTECTED]>
> Date: Wed, 20 Feb 2002 09:15:54 -0600
>
> My network uses 192.168.1 addresses instead of the default
LTS default
> (192.168.0) with a subnet mask of 255.255.255.0.
> I have a linksys cable/dsl router which also acts as my
hub and dhcp server
> for my network.
> From: Martin <[EMAIL PROTECTED]>
> Date: Wed, 20 Feb 2002 10:28:31 -
>
> Made the change as suggested... it now goes to the correct
server... BUT despite only
> specifying the "Root Path" as below, the client tries to
mount /opt/ltsp/i386000.
> I've tried putting it in quotes and vario
Koursk,
Yes, you can run it with 8mb of ram, but you
will definately need to turn on NFS-SWAP.
And, it will be slow. But, at least it will run.
Jim McQuillan
[EMAIL PROTECTED]
On Wed, 20 Feb 2002, Koursk OOSeven wrote:
> Hi,
>
> What is the minimal hardware requirement concerning
> the wor
From: Koursk OOSeven <[EMAIL PROTECTED]>
> Is it possible to run ltsp on a 486 with 8MB of RAM
> (with GUI)?
I had it with 16MB but it was not that fast especially when starting
something beyond a terminal ;-)
8MB worked as well, but you should use NFS-Swapping!
Claas Rathje
Koursk,
If you take a look at http://www.LTSP.org/instructions-3.0.html,
you'll see that you also need option-128 setup in your dhcpd.conf file.
option-128 contains an Etherboot signature. Without that,
Etherboot will ignore any other options.
Jim McQuillan
[EMAIL PROTECTED]
On Wed, 20 Feb 2
From: Koursk OOSeven <[EMAIL PROTECTED]>
> #
> filename "/lts/vmlinuz-2.4.9-ltsp-5";
> option option-129 "NIC=3c509 IO=0x300";
> #
add the option-128 it is NEEDED!
option option-128 e4:45:74:68:00:00;
is the right one...
Claas Rathje
_
Hi,
What is the minimal hardware requirement concerning
the workstation?
Is it possible to run ltsp on a 486 with 8MB of RAM
(with GUI)?
Regards.
__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Musi
Hi,
NIC on ws001: 3c509
I receive the following error message:
Could not automatically detect the network card
...
ISA cards cannot be detected
...
/etc/dhcpd.conf
#
filename "/lts/vmlinuz-2.4.9-ltsp-5";
option option-129 "NIC=3c509 IO=0x300";
#
Server running RedHat 7.1, LTSP
I know it's a hack, but once the directory is mounted that is the last time it
is a referenced. Try making a symbolic link between /opt/ltsp/i386 and
/opt/ltsp/i386000 on the server
ie.
cd /opt/ltsp
ln -s i386 i386000
It should work. NFS mounts will follow symbolic links.
Darryl Bond
[EMAIL
rox.sourceforge.net
VERY functional, without the pretty colors.
Arthur H. Johnson II
The Linux Box
http://www.linuxbox.nu
[EMAIL PROTECTED]
--
Anyone who is capable of getting himself
made President should on no account
be allowed to do the job.
-- Douglas Adams,
"The Hitchhiker's Guide
Derek,
That is quite old.
I can't say for sure that the newer version of Etherboot
will work with that Dell, but it's worth a try.
The Etherboot guys have done some excellent work in the
area of PCI compatability and detection.
Jim.
On Wed, 20 Feb 2002, Derek Dresser wrote:
> Jim,
>
> The
Jim,
The chip is actually v1.4
Here is the relevant info off the chip
Lne100v4v1.4 100923
If you think that is the issue, I'll order a couple of newer card/chips for
the L500r's. These cards work fine in everything else I've tried. I'll
just use them in something else.
Thanks,
Derek
Derek,
What is the version number on the chip?
We are now shipping the cards with Etherboot 5.0.5, and there
has been lots of work done within Etherboot to work better
with various Bios implementations.
If the card has a sticker that says v1.6, then it is the
older version of the chip.
Let me
Jesse,
One big problem I see is that you don't have the 'filename' entry
in your dhcpd.conf file.
Take a look at http://www.LTSP.org/instructions-3.0.html
Down near the bottom of that doc is some examples of the entries
you need in dhcpd.conf.
Hope that helps,
Jim McQuillan
[EMAIL PROTECTED]
Dario,
Thanks for the suggestion, but it doesn't seem to be the cards. These are
cards that I purchased from www.disklessworkstations.com with boot proms
installed, and they work fine in other machines. It appears that for some
reason, those boxes don't realize that there is a boot prom avai
In your dhcp.conf file you need some more entries:
> Here's what I get wehn I try and boot a system...
> Me : 192.168.0.35 , Server 192.168.0.1 , Gateway 192.168.0.161
> Loading 192.168.0.1:/tftpboot/kernel
> here's my dhcpd.conf file :
>
> ### Example dhcpd.conf file for a Class C subnet 19
Hi,
I set my system up about a year ago and abandoned KDE due to lots of
"leftover" processes after people logged out (and some other issues
including an extremely long login that I couldn'g figure out). We use
ICEwm and commonly have over 300 logins per day (average 15-20 at a time)
without
We have the same problem here, I never got around to asking if it could be fixed.
We're just
living with the three zero's . I changed the name of the nfs directory to match what
the DHCP
clients ask for - in our case ltsp3000. Let me know if anyone figures this one out.
--- [EMAIL PROTECTED]
I'm having a problem with tftpd.. and am wondering what i can do to fix
things.. I have the problem after my workstations request an IP address from
my dhcp server..
Here's what I get wehn I try and boot a system...
.
MAC address = 00:50:04:9D:6B:E7
Connectors present : 10Base-T / 100Bas
Dyg It,
Even with static IP addresses, you still need to pass the
filename of the kernel to download and the directory
to mount as the root filesystem.
So, you're still going to be stuck with the Linksys router
not giving you all the info you need.
Jim.
On Wed, 20 Feb 2002, Dyg It wrote:
>
Thanks for the quick response, Jim!
Then let me ask you this...what about using static ip addresses, bypassing
dhcp all together. I didn't fully understand from the docs, but it appeared
that I should be able map ip addresses to mac addresses - if that's the
case, how would the LTS be configured g
A thin client is a small computer that is designed for network booting, not
a desktop that is missing a few pieces. Most of the ones I see are about
the size of a good Shakesphere book, with some even smaller! :) All
hardware is built in video/nic/auido/ports, with no harddrive and most don't
ha
Dyg It,
As much as you may WANT your linksys router to serve up dhcp, I just
don't think it is going to work.
As far as I know, there's no way within the Linksys to configure all
the stuff that an LTSP client needs. Things like root-path and
filename.
And, if you need to specify any kernel com
>Agreed. After my experiments in a 5 user environment with 1/2 gig of RAM,
>KDE has been found to be unsuitable for Terminal Server on my end. I may
>not be tuning my system in the right places thou.
>GNOME seems more apt for "simple" environments. We are testing running
>Ximian GNOME on it rig
Am 20 Feb 2002, um 10:39 Uhr schrieb Kohlmeier, Markus:
> Hi, does any thin client work with ltsp ?
>
> Thanks, Markus
>
Hi Markus,
what do you mean with "thin"?? Is there a way to be more "thin" than
you cold be with LTSP?
Or do you mean a special kind of hardware?
Andreas.
_
Agreed. After my experiments in a 5 user environment with 1/2 gig of RAM,
KDE has been found to be unsuitable for Terminal Server on my end. I may
not be tuning my system in the right places thou.
GNOME seems more apt for "simple" environments. We are testing running
Ximian GNOME on it right
Hi Derek,
I had similar problems with a couple of network cards. I solved it
enabling the "eprom socket" option with the utility disk usually shipped
with the NIC. Perhaps you have the same problem.
Good luck,
Dario.
El mié, 20-02-2002 a las 10:49, [EMAIL PROTECTED] escribió:
> Hello,
Abraham,
I had the same problems with a SiS6326 card in a machine I had (a
workstation, not a ltsp client) and I solved the problem adding the
following line in the device section of the video card:
Option "no_accel"
Perhaps you could try a custom XF86Config file with this and
[As a preface, I _have_ gone through the docs and searched the list archive
and tried numerous configurations - only to end up pulling my hair out]
My network uses 192.168.1 addresses instead of the default LTS default
(192.168.0) with a subnet mask of 255.255.255.0.
I have a linksys cable/dsl ro
Martin,
This very same thing happened to someone else back on Feb 5th.
I searched the mailing list archives, and unfortunately, it doesn't
look like they solved it either.
Jim McQuillan
[EMAIL PROTECTED]
On Wed, 20 Feb 2002, Martin wrote:
> Made the change as suggested... it now goes to the
Hello,
I have a couple of Dell Dimension L500r computers with bios revision A14
(most recent for this machine). I have a bootable PCI network card in
them, but they do not find it. I have disabled the floppy, hard drives,
etc. in the bios. There is no "network" option in the boot preference
And even when you get it working, it will invariably pull some other tricks later.
Lose the winders box and good fortune will return.
You have a linux box running ltsp. Let it be the dhcp server too. you will be much
happier on down the road.
Kinda like dealing with flaky hardware. I allow
Way too vague of a question. Of course some do not work. Which ones do you have in
mind.
Those that dont work now might be coerced if one has a real need for it.
On Wed, 20 Feb 2002 10:39:35 +0100
"Kohlmeier, Markus" <[EMAIL PROTECTED]> spewed into the bitstream:
~Hi, does any thin client w
Made the change as suggested... it now goes to the correct server... BUT despite
only specifying the "Root Path" as below, the client tries to mount /opt/ltsp/i386000.
I've tried putting it in quotes and various other things, but it always appends "000"
to the end! Has anyone else seen a
Title: Nachricht
Hi, does any thin
client work with ltsp ?
Thanks,
Markus
42 matches
Mail list logo
