public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Erik Heil" <eheil@patmedia.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Fw: terminal servers
Date: Fri, 7 Nov 2003 17:13:09 -0500	[thread overview]
Message-ID: <017d01c3a57c$54724ad0$0201a8c0@eheil> (raw)


----- Original Message ----- 
From: "Luke Davis" <ldavis@shellworld.net>
To: "Erik Heil" <eheil@patmedia.net>; "Speakup is a screen review system for
Linux." <speakup@braille.uwo.ca>
Sent: Friday, November 07, 2003 5:00 PM
Subject: Re: terminal servers


> That's pretty much where I was about to go.
>
> The base system needs to be am image that can be dumped directly to each
> terminal.
> Everything other than that--/usr, /bin, /sbin, /home, and so on, can be
> NFS mounted.
>
> The matter of /etc and /var comes to mind.
>
> It might be good to have these NFS mounted as well, but resident on the
> server, and spesific to each terminal.  (with /etc.  You would only have
> to do it with parts of /var, I believe, such as /var/log, /var/lock,
> /var/run, etc..)
>
> Luke
>
>
>
> On Fri, 7 Nov 2003, Erik Heil wrote:
>
> > Hi, Alex.  What you would want to do is have all of the clients boot via
an
> > bootp server which you would configure on your server.  In order for
this to
> > be successful the client machines must have a PXE-capable NIC and the
system
> > BIOS must support booting via TCP/ip.  You would use NFS to export
/home,
> > /usr, etc. to the client machines so they would have access to any
shared
> > directories on the server you would want.  As far as making the machines
> > boot, you would create an image directory on the server that would
include
> > the kernel, etc. the machines would need.  I'll try and dig up some
how-to's
> > for you here, but this should get you pointed in the right place.
> > ----- Original Message -----
> > From: "Alex Snow" <alex_snow@gmx.net>
> > To: <speakup@braille.uwo.ca>
> > Sent: Friday, November 07, 2003 3:17 PM
> > Subject: terminal servers
> >
> >
> > > Hi all. I have a lot of crap hardware around here I can probably turn
> > > into some really low-end machines. I would like to use these machines
> > > mostly 486dx's and early pentiums as diskless terminals.
> > > I took a look at the ltsp but it doesn't seem like it will run on
> > > slackware. Does anyone know where I could look to get started on
setting
> > > up a terminal server and it's clients?
> > >
> > > --
> > > Who is General Failure and why is he reading my hard disk?
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >



                 reply	other threads:[~ UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='017d01c3a57c$54724ad0$0201a8c0@eheil' \
    --to=eheil@patmedia.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).