Re: [suse-linux-uk-schools] Small Project Starter Suggestions
On Tuesday 23 Oct 2001 19:20, Glenn Cameron wrote:
I've got an old server and some machines not in use that could be useful for data-logging and internet access in a science lab. The machines don't have CD-ROMs so I'm thinking I either end up sticking a cd-rom in each machine to build it, or get the workstations to act as dumb terminals connect to the server - I have a 100mb switch and the machines have Intel pro cards in so should be acceptable speed. Any pointers on a good way to go forward, what to read and where to start?
I don't 100% understand what you want to do with them. If it's just simple 'net access, and perhaps word processing/whatever, I'd do an install over
"Chris Howells" <chrish@gmx.co.uk> wrote: the
network, and just use them as standalone machines, although of course going over the LAN for 'net access.
OK, was wondering whether to go for a thin client structure but I guess we'd need to beef up the server quite a lot to make that viable. So I guess what I'd just like some pointers/advice on is how best to get started. Presumably install SuSE on the server, probably can manage that easy enough, but the issue then is how to set-up the workstations in a sensible way, in terms of installing the OS and the configuration. Is it a case of booting from a floppy and installing by nfs presumably, and then configuring each one individually or is there a better way to manage it all? Sorry, if this all sounds a bit dim to everyone but although I use linux every day for e-mail and web services, I just don't have the experience on the desktop level so just need some pointers. -- Glenn Cameron King Henry VIII School, Coventry
----- Original Message -----
OK, was wondering whether to go for a thin client structure but I guess
we'd
need to beef up the server quite a lot to make that viable. So I guess what I'd just like some pointers/advice on is how best to get started. Presumably install SuSE on the server, probably can manage that easy enough, but the issue then is how to set-up the workstations in a sensible way, in terms of installing the OS and the configuration. Is it a case of booting from a floppy and installing by nfs presumably, and then configuring each one individually or is there a better way to manage it all? Sorry, if this all sounds a bit dim to everyone but although I use linux every day for e-mail and web services, I just don't have the experience on the desktop level so just need some pointers.
Ho Hum. I'll probably need my mouth washed for this. Look at KickStart. OK I know its R*d H*t, but have a look at http://www.linuxdoc.org/HOWTO/KickStart-HOWTO.html This e-mail is intended for the addressee shown. It contains information that is confidential and protected from disclosure. Any review, dissemination or use of this transmission or its contents by persons or unauthorized employees of the intended organisations is strictly prohibited. The contents of this email do not necessarily represent the views or policies of East Norfolk Sixth Form College, it's employees or students.
What sort of hardware spec are your client machines - esp RAM and processor? Do you need to run X on them? Basic data-logging should be no problem on any machine able to run a kernel (upwards from 386 with 8M), but I assume that when you say internet access you mean a graphical browser under X? Do you want office type software? Staroffice needs a lot of RAM, so does KDE. Unless you decide to go totally thin-client, the best way to install CD-less PC's is to use a minimal boot floppy and install across the LAN from a CD/DVD mounted on the server. If your clients are a reasonable spec RAM-wise at least, you could for a server based install running local apps rather than full thin-client. ____________________________________ Giles Nunn - Network Manager Carms Schools ICT Development Centre Tel: +44 01239 710662 Fax: 710985 ____________________________________ On Tue, 23 Oct 2001, Glenn Cameron wrote:
On Tuesday 23 Oct 2001 19:20, Glenn Cameron wrote:
I've got an old server and some machines not in use that could be useful for data-logging and internet access in a science lab. The machines don't have CD-ROMs so I'm thinking I either end up sticking a cd-rom in each machine to build it, or get the workstations to act as dumb terminals connect to the server - I have a 100mb switch and the machines have Intel pro cards in so should be acceptable speed. Any pointers on a good way to go forward, what to read and where to start?
I don't 100% understand what you want to do with them. If it's just simple 'net access, and perhaps word processing/whatever, I'd do an install over
"Chris Howells" <chrish@gmx.co.uk> wrote: the
network, and just use them as standalone machines, although of course going over the LAN for 'net access.
OK, was wondering whether to go for a thin client structure but I guess we'd need to beef up the server quite a lot to make that viable. So I guess what I'd just like some pointers/advice on is how best to get started. Presumably install SuSE on the server, probably can manage that easy enough, but the issue then is how to set-up the workstations in a sensible way, in terms of installing the OS and the configuration. Is it a case of booting from a floppy and installing by nfs presumably, and then configuring each one individually or is there a better way to manage it all? Sorry, if this all sounds a bit dim to everyone but although I use linux every day for e-mail and web services, I just don't have the experience on the desktop level so just need some pointers.
-- Glenn Cameron King Henry VIII School, Coventry
-- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com
On Tue, 23 Oct 2001, Glenn Cameron wrote:
"Chris Howells" <chrish@gmx.co.uk> wrote:
On Tuesday 23 Oct 2001 19:20, Glenn Cameron wrote:
I've got an old server and some machines not in use that could be useful for data-logging and internet access in a science lab. The machines don't have CD-ROMs so I'm thinking I either end up sticking a cd-rom in each machine to build it, or get the workstations to act as dumb terminals connect to the server - I have a 100mb switch and the machines have Intel pro cards in so should be acceptable speed. Any pointers on a good way to go forward, what to read and where to start?
OK, was wondering whether to go for a thin client structure but I guess we'd need to beef up the server quite a lot to make that viable. So I guess what I'd just like some pointers/advice on is how best to get started.
Don't guess! Get some figures of CPU load, etc. from your existing systems and/or other users. You might be pleasantly surprised.
Presumably install SuSE on the server, probably can manage that easy enough, but the issue then is how to set-up the workstations in a sensible way, in terms of installing the OS and the configuration. Is it a case of booting from a floppy and installing by nfs presumably, and then configuring each one individually or is there a better way to manage it all?
SystemImager is very good at building and maintaining lots of identical machines -- IMHO it solves a lot more of the problem than KickStart. See: http://systemimager.org/ Bob G
participants (4)
-
Giles Nunn -
Glenn Cameron -
manager -
Robert J Gautier