Hi,
Randall Craig wrote:
> I am not sure what the chipset is on that board. Do a lspci -vv
> and you will get the chipset information. But I imagine it uses the
> SiS 900 ethernet code.
>
> Linuxbios see: http://www.linuxbios.org has been successfully used
> on its cousin ECS K7SEM. But I hav
Suhardi,
That's the chip I use.
Jim.
On Mon, 11 Mar 2002, Suhardi Hamid wrote:
> Dear sirs,
> I wish to know what are the eprom/flash rom chips compatible with
> 3c905B-TX NM. I have tried SST 29EE512 (90-4C-PH) and it's working fine.
> However, the chip is hardly found in local stores here. I
Dear sirs,
I wish to know what are the eprom/flash rom chips compatible with
3c905B-TX NM. I have tried SST 29EE512 (90-4C-PH) and it's working fine.
However, the chip is hardly found in local stores here. I'll be glad if
anyone could suggest me other chips that I can try on. Thank you.
_
Julius,
That's great news. I've kind of noticed that people
haven't been complaining about this as much lately.
Jim.
On Sun, 10 Mar 2002, Julius Szelagiewicz wrote:
> Jim,
> this was a problem in rh71, it went away with 72. i ue k120s 2.0
> and the gdm - no problems. julius
>
> On Sun
Jim,
this was a problem in rh71, it went away with 72. i ue k120s 2.0
and the gdm - no problems. julius
On Sun, 10 Mar 2002 [EMAIL PROTECTED] wrote:
> Zak,
>
> If only it were that easy :)
>
> As I understand it, it is really a function of the display manager
> to kill any running tasks
I am not sure what the chipset is on that board. Do a lspci -vv
and you will get the chipset information. But I imagine it uses the
SiS 900 ethernet code.
Linuxbios see: http://www.linuxbios.org has been successfully used
on its cousin ECS K7SEM. But I have not tried using ltsp on it.
Cheers,
Well everything is very cool at the moment. I am running ltsp 3.0, SuSE
7.0. With thin clients based on the MES-N NLX Asus box.
I have rewritten my data collection code from using named pipes to
sockets. This is a *very* nice solution for a manufacturing floor, or
POS systems. My Microtouch t
* Rainer_Standke <[EMAIL PROTECTED]> [10.03.02 23:28]:
> does it matter to switch the ltsp-workstation off after finished work or
> must it been shut down?
You should logout and terminate all your processes, but then you can
just switch off the workstation.
__
On Sunday 10 March 2002 23:28, Rainer_Standke wrote:
> Hi,
> does it matter to switch the ltsp-workstation off after finished work or
> must it been shut down?
>
The way I understand it, it is always better to do a logout.
Jo
_
Hi,
does it matter to switch the ltsp-workstation off after finished work or
must it been shut down?
Gruss
Rainer
--
[EMAIL PROTECTED]
http://www.swoos.de/
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
Michel,
Probably, you do need to configure X for the workstation,
look in LTSROOT/lts.conf
Cicero
On Saturday 10 March 2001 16:58, you wrote:
> Following my first post on this subject /var/log/messages reported the
> following:
>
> syslogd started: busybox v0.60.1 (2001.09.28-01:12+)
> devf
Zak,
If only it were that easy :)
As I understand it, it is really a function of the display manager
to kill any running tasks if a user dissappears. Really outside
the scope of the LTSP. Although I agree that it is important
for us.
It seems that GDM is the display manager that causes the mo
Hi all
OK, that's not quite an accurate description, but when users simply
switch off their terminals, their processes don't seem to die along with
them. Searching the ltsp-discuss archives yielded a few options for
dealing with these orphaned processes, but they all seem to be slightly
dodgy in
Following my first post on this subject /var/log/messages reported the
following:
syslogd started: busybox v0.60.1 (2001.09.28-01:12+)
devfsd[108]: Caught SIGHUP
devfsd[108]: read config file: "/etc/devfsd.conf"
init: entering runlevel: 2
init: switching to runlevel: 5
init: no more processes
Sitat Conrad Lawes <[EMAIL PROTECTED]>:
> There is no way to use rdesktop without using KDE or GNOME. However,
> I believe that you can configure KDE to autolaunch rdesktop at
> startup. Check the ltsp contribution area and the ltsp mail
> archives. I believe someone has already done this.
Wh
I succeded to start dhcp and the the workstation is coming up
to: Starting syslogd
and hang at this point.
My set up configuration is exactly as provided by LTSP.ORG
The workstation is a Shuttle FV24 computer
the processor is a Celeron 900 Mhz
Memory 256 meg SDRAM
the following accessories are
On Sunday 10 March 2002 17:23, Conrad Lawes wrote:
> There is no way to use rdesktop without using KDE or GNOME. However, I
> believe that you can configure KDE to autolaunch rdesktop at startup.
> Check the ltsp contribution area and the ltsp mail archives. I believe
> someone has already done
Cicero Mota wrote:
> Hi,
> I did install remote apps for my ltsp workstation, but the
> time to launch looks too big: simple
> $ rsh xxx.xxx.xxx.xxx ls
> takes more than 11s
> Does anybody know why is it so slow?
> Can it be better
Cicero,
a few things for you to check:
1. Are you using ipchains
Conrad Lawes wrote:
> Jo <[EMAIL PROTECTED]> wrote:
>>I managed to connect an LTSP client to a Win2k terminal server
>> using rdesktop (www.rdesktop.org). Is it possible to have the
>> LTSP terminal connect to the W2k terminal server immediately?
>
> There is no way to use rdesktop without using
There is no way to use rdesktop without using KDE or GNOME. However, I believe that
you can configure KDE to autolaunch rdesktop at startup. Check the ltsp contribution
area and the ltsp mail archives. I believe someone has already done this.
Jo <[EMAIL PROTECTED]> (by way of Jo <[EMAIL PROT
It is usually impossible and risky to flash a BIOS integrated boot ROM using a utility
from a third party. Normally only the PC or motherboard manufacturer can supply the
flash utility to update or replace your BIOS.
I suspect that your BIOS-integrated boot ROM uses the PXE network boot protoc
Ernst,
I've got LTSP 3.0 running on SuSE 7.3
Tip (1) : To start DHCP when the server boots you have to change
a parameter through Yast (1!!) :
== Start Yast
== Choose
== Choose
== Hit F4 to search for a specific parameter
== Type START_D and hit
== Make sure START_DHCPD is selected
== Hit F
On Sun, Mar 10, 2002 at 02:20:27PM +0100, Ernst Klein wrote:
> I think dhcpd is not running. Starting it manually:
>
> # dhcpd &
>
> Internet Software Consortium DHCP Server V3.0rc12
> Copyright 1995-2001 Internet Software Consortium.
> All rights reserved.
> For info, please visit http://www.is
Hello,
look at the dhcpd message. it cant find the /etc/dhcpd.conf. you wrote
that you edited the /etc/dhcp.conf.
(ist vielleicht nur ein tip-fehler)
good luck,
bastian
On Sun, 2002-03-10 at 14:20, Ernst Klein wrote:
> Hello,
>
> I`m installing a new server based on SuSE7.3 and ltsp 3.0
>
Which is the correct Etherboot Image for the Onboard LAN on the ECS K7S5A
Motherboard?
Has anyone successfully flashed a boot rom onto the BIOS?
--
Crayne's law: All computers wait at the same speed.
_
Ltsp-discuss mailing list
Hello,
I`m installing a new server based on SuSE7.3 and ltsp 3.0
In the past I used SuSE 7.1 and ltsp 2.07 with bootp and it worked
great.
I installed successful the following tgz-packages:
ltsp_core-3.0.0.tgz (with changes in the file suse-7.3.sh ,which were
discussed here some weeks ago)
lts
On Fri, 2002-03-08 at 18:35, Jason A. Pattie wrote:
> Berend De Schouwer wrote:
>
> >>>*** A possible solution may be to create a VPN(IPSEC) betweeen the client
> >>>and the server. Allow the home directory to be mounted only through the
> >>>VPN.
> >>>
> >>A very good solution and one that is no
27 matches
Mail list logo