Well, I've flushed iptables (see below) and it's still searching for
dhcp. I'll try again after reboot but
iptables does not appear to be the problem.
Adam Bogacki,
[EMAIL PROTECTED]
Tux:~# iptables -A INPUT -i eth1 -j ACCEPT
Tux:~# iptables -A OUTPUT -o eth1 -j ACCEPT
Tux:~# iptables-save
# Gene
Thanks Jim.
RE. "You should set eth1 as a trusted interface so it doesn't do any
filtering".
iptables -A INPUT -i eth1 -j ACCEPT
iptables -A OUTPUT -o eth1 -j ACCEPT
iptables-save
[I've sent the output]
..but an attempt to boot ws001 was not successful.
tail -f /var/log/messages ..gave me
Me too!!
Oscar
.
.
.
.
.
i am trying to build ltsp from scratch using lbe.
i got the following error when compiling bison:
<...>
../intl/libintl.a(loadmsgcat.o)(.text+0x0): first defined here
/uml/lbe/i386-linux-crosscomp/lib/gcc-lib/i386-linux/3.2.3/../../../../i386-
linux/bin/ld: Warning: size
Evan Hisey wrote:
Hello all-
For any one interested I ahve just finished a first draft of a howto
for the LBE. It is sketchy in places, like the complete list of what
all the variables do an which are required in the package.def. But I
think it should be able to get some one up and running with it
Hi everybody,
currently i'm using ltsp-3.x in my office with appr. 60 (thin)clients
connected to it. as the load on the server is getting higher and higher
and almost reaches a critical level, i'm thinking of moving of the most
resource consuming applications (such as mozilla-firefox & thunderbi
Is the calculation applied to concurrent users? Or we can go by number
of clients?
Thanks
Jim McQuillan wrote:
Oxiel,
You will definately want more ram. Ram is probably the single most
important thing in a large multi-user system.
Start your ram calculations based on the following formula:
256
