public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Graham Swallow <gps@trix.dircon.co.uk>
To: blinux-list@redhat.com
Subject: Re: Debian installation - interested?
Date: Wed, 27 Nov 1996 23:52:09 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.3.91.961127233645.253C-100000@trix.dircon.co.uk> (raw)
In-Reply-To: <Pine.GSO.3.94.961127164817.19143A-100000@Ocean.CAM.ORG>

On Wed, 27 Nov 1996, Nicolas Pitre wrote:

> On Wed, 27 Nov 1996, Nikhil Nair wrote:
> > 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 don't suppose most people will have a mouse on COM1,
	but COM2 would normally be used for the extern modem
	or serial wire. LILO has low BAUD rate support,
	which means you have to mess about at 9600 BAUD
	which is plenty fast enough for screens, but as soon as you get
	pppd running, you'd switch to 11.5 K/S and
	get access to NFS files, telnet, multi-screens
	and your own system (or stay with a TTY emulator).

	As for the tty installation script, what about
		dpkg -i name1
		dpkg -i name2
	Slackware would be (something like)
		installpkg name1.tgz

	Before then sort out /etc/fstab manually,
	and run mke2fs manually. Then copy over your collection
	of /etc/hosts files (if they weren't the first thing you copied over).

	An alternative, is to install the minimum bases set that boots
	comportably, pack it into one tar file, arrange for it to
	appear on CDROM and wake up from there.

	The support you need to get the kernel boot messages onto
	the serial line is either new or pending. Good luck!

      Graham             gps@trix.dircon.co.uk
-- 
     --------------------------------------------------------------
     Linux Info Pages:  http://sunsite.unc.edu/pub/Linux/docs/Raven
     Raven Devel Site:  http://beyond.malmo.lth.se/~gps/Raven/
     Raven dial up:     http://trix.dircon.co.uk/ 
     Click here  -->    http://www.users.dircon.co.uk/~trix/
     --------------------------------------------------------------


      reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Nikhil Nair
 ` Nicolas Pitre
   ` Graham Swallow [this message]

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.LNX.3.91.961127233645.253C-100000@trix.dircon.co.uk \
    --to=gps@trix.dircon.co.uk \
    --cc=blinux-list@redhat.com \
    /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).