From: Nicolas Pitre <nico@CAM.ORG>
To: Nikhil Nair <nn201@cus.cam.ac.uk>
Cc: blinux-list@redhat.com, linux-access@ssv1.union.utah.edu
Subject: Re: Debian installation - interested?
Date: Wed, 27 Nov 1996 17:08:03 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.3.94.961127164817.19143A-100000@Ocean.CAM.ORG> (raw)
In-Reply-To: <Pine.LNX.3.95.961127192354.5187A-100000@amasis.trin.cam.ac.uk>
On Wed, 27 Nov 1996, Nikhil Nair wrote:
[...]
> So what I'd like to know from you all is: what do you think would be most
> useful? Presumably many people don't have DecTalks, but do many have
> second machines to use as serial terminals? If having a serial terminal
> installation procedure would be useful, should there be a choice of which
> com port to use? How should this be selected - would separate rootdisks
> be needed, or would a simple choice on the main keyboard (say pressing 1
> or 2) be OK?
What I think is best is to have a rootdisk wich starts a getty on both
COM1 and COM2. It is also best to have a dumb terminal installation
script (easier to track with a screen review software). It could be set
on a separate rootdisk or just make the serial port login active on an
already existing rootdisk... But since COM1 and COM2 are driven with a
getty, the terminal could then be attached to any of those two without
having to make a selection.
I think it's also possible to configure lilo to redirect its I/O to a comm
port (in 9600 bauds). A bootdisk could be set up with this so the
installation even from the boot time could be controlled and monitored
from an external terminal wich could be an extra PC with any kind of
access software.
It's even possible to get boot time messages on the serial port just by
defining a simbolic link like /dev/console --> /dev/ttyS0...
> Nikhil Nair
> Trinity College, Cambridge, England
> Tel.: +44 1223 368353
> Email: nn201@cus.cam.ac.uk
> nnair@debian.org
nico@cam.org
Nicolas Pitre
ing. stag.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Nikhil Nair
` Nicolas Pitre [this message]
` Graham Swallow
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=Pine.GSO.3.94.961127164817.19143A-100000@Ocean.CAM.ORG \
--to=nico@cam.org \
--cc=blinux-list@redhat.com \
--cc=linux-access@ssv1.union.utah.edu \
--cc=nn201@cus.cam.ac.uk \
/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).