> These are some specs are for a Linux X-terminal network. There will be 10
> diskless terminals and 1 network server. The network is for a computer lab
> in a school. Students will be trained in basic computer and internet skills.
> We'll run Redf hat 6.2 and StarOffice 5.2. A few students and teachers are
> expected to do a little programming, but not a whole lot. What do you guys think
> of the specs? Any comments are welcome.
> 
> Linux X-terminal workstation
> 
>    Processor  :       AMD K62-500, or Intel PIII-500, or similar processor.
>                               (minimum: Intel PII-450)
>    RAM                :       32MB

hmmm. this is quite dangerous because staroffice eats a lot of memory. it
must have a very high niceness value. hehehe. remember that diskless
workstations do not have the swap space a regular PC would have.
therefore, swapping must be prevented at all costs.

there is a swap over NFS patch somewhere. i used this for the
javastations. i will go through it for you if you like.

but, if you are just exporting the X display to the Xserver in the
workstation. i believe this is enough.

>    Hard disk  :       none

just make sure that the server (master node) of this setup will have a
fast hard disk subsystem. preferably U2W SCSI or UDMA66 or higher.

>    multimedia :       16-bit or 32-bit sound card*, multimedia speakers
>    video      :       4MB AGP video card (separate from motherboard)**
>    Network card       :       10/100 Ethernet card

if you can afford getting 100mbps card do so! i recommend the 3c905 series
and the Intel EEPro100 cards.

>    Monitor    :       15-inch SVGA
>    Peripherals        :       standard 101-key keyboard, 2-button serial mouse
>    ROM                :       custom boot ROM to connect temrinal to network

the Intel EEPro comes with something called PXE. you can install the PXE
daemon on the server eliminating the need for a bootrom. this reduces the
time it takes to install a diskless workstation. this makes the solution
totally: plug, play and forget.

>    Ports      :       printer port, 2 x serial ports, joystick, USB port
> 
> 
> Notes:
> *  Soundblaster compatible
> ** Preferably the video card should be separate; video built-in on the 
>    motherboard is NOT recommended.
> 
not just it is not recommended. it would eat part of your system RAM which
you must have a lot of!

> 
> Linux Network Server
> 
>    Processor  :       Intel Xeon-500, or Intel PIII-667

depending on your setup. do you execute apps off the server and export the
display to the Xserver of the workstation...or...do you run it off the
workstation.

for a big bad microprocessor, i have benchmarks that say the athlon rocks
intel anyday. for FPU performance a duron and a pIII of comparible clock
speed have very close performance values.

>    RAM                :       512MB
>    Hard disk  :       2 x SCSI 20GB or 1 x SCSI 36GB
>    CD ROM     :       52X CD ROM drive
>    Floppy     :       1.44MB floppy drive
>    video      :       4MB AGP video card**
>    Modem      :       US Robotics 56K external fax/modem
>    Network card       :       10/100  Ethernet card

match the card here with the workstation network interface cards.

>    Monitor    :       15 SVGA monitor
>    Peripherals        :       standard 101-key keyboard, two-button serial mouse
>    Ports      :       printer port, 2 x serial ports, joystick, USB
> 
>    
> Others
> 
>    LAN hub (16-port)

oooooooppppsssssssssssssssss! better rethink this. i believe a switch is
necessary. however, for the exporting Xdisplay method it may work.

>    printer (preferably laser)
> 

 
--------------------------------------
William Emmanuel S. Yu
Ateneo Cervini-Eliazo Networks (ACENT)
email  :  [EMAIL PROTECTED]
web    :  http://cersa.admu.edu.ph/
phone  :  63(2)4266001-5925/5904
 
Many people write memos to tell you they have nothing to say.
 

_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]

To subscribe to the Linux Newbies' List: send "subscribe" in the body to 
[EMAIL PROTECTED]

Reply via email to