Okay firstly this is for local-apps enabled workstations,
I was thinking down the line of, say you have RPMS you want to install for the
workstations it will be a lot easier to boot the workstation with a read-write
environment, run rpm on the workstation. this will then expand the rpm to the c
Frank Van Damme wrote:
> Durons on the client??? terrible waste of cpu power and money, what is the
> use for a thin client then?
> And ... he's talking about 500 clients. Are you often opening 2500 or more
> apps on a computer with 3 gigs of ram? I don't think so... He needs 8 gigs,
> preferabl
Janyne Kizer wrote:
> David Johnston wrote:
> > how do your local Star Office setups connect to the printer (directly to
> > the printer, via the server's spooler)? Do the remote users connect the
> > same way?
> Both are connecting to the print queue (the StarOffice queue is
> connected to the r
Ben,
Usually, the next step for me is to run tcpdump and watch the
packets fly.
I can help you look at it, if you want to come over to the
#ltsp IRC channel on irc.openprojects.net
Jim.
On Sun, 21 Apr 2002, Ben King wrote:
> ok... I do have the dhcpd.conf set to /lts/vmlinuz-2.4.9-ltsp-5 (un
ok... I do have the dhcpd.conf set to /lts/vmlinuz-2.4.9-ltsp-5 (under the
dir this is what I have). I have tried all of them. Also I get "udp 0
0 0.0.0.0:690.0.0.0:* " when I run netstat -an | grep ":69 ".
hosts.allow I have bootpd0.0.0.0in.tftpd192.168.1. portmap
192.168.
Quoting Frank Van Damme <[EMAIL PROTECTED]>:
> On Sunday 21 April 2002 03:00 am, you wrote:
> > Guys,
> >
> > A customer has come to me asking about the possibility of using Linux in
> a
> > new rollout. They are keen on using Linux on thin clients, and the best
> > solution seems to be LTSP.
> >
Here is the output from:
netstat -an| grep ":67"
udp0 0 0.0.0.0:67 0.0.0.0:*
> [EMAIL PROTECTED]
>
>
>
> On Sun, 21 Apr 2002, Denzil Kelly wrote:
>
> > I am running debian woody, and I am running ltsp
> 3.0.
> > I am having the follow problem. The client won't
> boo
Denzil,
You showed us a bunch of NFS stuff, but you aren't
getting that far.
Looking at your output from ifconfig -a, I see that
eth0 isn't up. I wonder if you have dhcpd configured
to listen on eth0 and not eth1.
Try this on the server:
netstat -an | grep ":67 "
and tell us what it say
Frank Van Damme wrote:
> On Sunday 21 April 2002 09:02 pm, Alex younts wrote:
>
>>My suggestion would go something like this:
>>Server: Dual Athlon 2000+ with 3GB of DDR RAM and SCSI hard drives with a
>> 1Gbps connection to your switch
>>Client: AMD Duron 600 with 32MB of RAM and
I am running debian woody, and I am running ltsp 3.0.
I am having the follow problem. The client won't boot.
I get this message:
Searching for server (DHCP)...
dhcpd is running on the server.
ifconfig -a gives:
dummy0Lin
On Sunday 21 April 2002 09:02 pm, Alex younts wrote:
> My suggestion would go something like this:
> Server: Dual Athlon 2000+ with 3GB of DDR RAM and SCSI hard drives with a
> 1Gbps connection to your switch
> Client: AMD Duron 600 with 32MB of RAM and a 100Mbps NIC
> Howev
My suggestion would go something like this:
Server: Dual Athlon 2000+ with 3GB of DDR RAM and SCSI hard drives with a
1Gbps connection to your switch
Client: AMD Duron 600 with 32MB of RAM and a 100Mbps NIC
However, depending on what how many things the users are doing, that
On Sunday 21 April 2002 03:00 am, you wrote:
> Guys,
>
> A customer has come to me asking about the possibility of using Linux in a
> new rollout. They are keen on using Linux on thin clients, and the best
> solution seems to be LTSP.
>
> Configuration will prob be something like KDE3, Open Office
Hi Craig,
I think consideration priority should probably be the server hardware, then
the network hardware, then the client hardware. Although my application is
no where near 500 clients, I would imagine that the priority is still the
same.
After first setting up LTSP with a handfull of workstati
Both are connecting to the print queue (the StarOffice queue is
connected to the regular Linux print queue).
David Johnston wrote:
>
> Janyne Kizer wrote:
> > My group has started to rollout RedHat 7.2 systems to several remote
> > sites. We are running StarOffice 5.2 on these systems and we ha
Hi Ilunga,
Although you do have an option root path specified, surf6 does not know
about it because the option is specified in the group declarationwhich
surf6 is not member of.
Try this instead:
not authoritative;
ddns-update-style none;
default-lease-time21600;
max-lease-
Jorgen,
Turn off ipchains, and see if it works.
My guess is that it will work.
Jim McQuillan
[EMAIL PROTECTED]
On Sun, 21 Apr 2002, Jørgen Pedersen wrote:
> -Hi, and thanks to Jim and David for suggestions
>
> In the meantime I have installed K12ltsp on a server in our testroom at
> work. D
Il giorno Sat, 20 Apr 2002, Frosted_Duck così ha scritto:
|From: Frosted_Duck <[EMAIL PROTECTED]>
|To: LTSP Discuss <[EMAIL PROTECTED]>
|Date: Sat, 20 Apr 2002 04:51:38 -0500
|Subject: [Ltsp-discuss] Client will not start
|
|I've gone threw the docs and can't seem to get anywhere... so please hel
Ben,
This is NOT a NFS or Portmapper problem. You aren't getting that
far yet.
Are you just getting dots forever ? It is normal to get several lines
of dots, but then the kernel should kick in and start producing lots
of messages.
Do you have a file called "vmlinuz.ltsp" in the /tftpboot/lts
-Hi, and thanks to Jim and David for suggestions
In the meantime I have installed K12ltsp on a server in our testroom at
work. Default installation, same procedure as I have tried at home. The
server at work: HP P2 500, 128Mb, Realtek 8139 - and client: IBM P2 amd
500, 128 Mb, realtek 8139..
I've gone threw the docs and can't seem to get anywhere... so please help...
let me start with a little info.. redhat 7.2, dhcp is working because the
client i has the ip that i gave it... the client is using www.rom-o-matic.com
for the bootdisk.. tftp is installed... but i'm not sure that its
21 matches
Mail list logo
