Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Alistair Lambie" <alambie@wellington.sgi.com>
To: Mike Shaver <shaver@neon.ingenia.ca>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: init=/bin/sh and serial devices
Date: Wed, 9 Apr 1997 14:31:16 +0000	[thread overview]
Message-ID: <9704091431.ZM9866@windy.wellington.sgi.com> (raw)
In-Reply-To: "Alistair Lambie" <alambie> "Re: init=/bin/sh and serial devices" (Apr  9,  2:30pm)

On Apr 9,  2:30pm, Alistair Lambie wrote:
> Subject: Re: init=/bin/sh and serial devices
> BTW, if you use the init package it will take care of all this stuff...you
> should be able to just lay it over the top of the root package on your nfs
> disk.
>

You will need to edit inittab for the serial devices...it's set up for the vc's
on a 'headed' Indy.


> Cheers, Alistair
>
> On Apr 9,  2:23pm, Alistair Lambie wrote:
> > Subject: Re: init=/bin/sh and serial devices
> > On Apr 9,  2:12pm, Mike Shaver wrote:
> > > Subject: init=/bin/sh and serial devices
> > > Wierd stuff here.
> > > We've got it mountinng the NFS partition and running /bin/sh, but we
> > > can't type anything to it at that point.
> > > It's kinda weird, because we see the `#' prompt, but stuff I type to
> > > it isn't registering.
> > >
> > > stdin in /dev/cua1, FWIW.
> > >
> >
> > Try 'init=/bin/sh </dev/cua1 >/dev/cua1'.  I seem to remember you need
that.
> > Sorry all this seems to be coming piece meal, but it's been a long time
since
> I
> > have run it up, and you kind of forget some of the details till you are
> > reminded!
> >
> > Cheers, Alistair
> >
> > --
> > Alistair Lambie
> 				    alambie@wellington.sgi.com
> > Silicon Graphics New Zealand				  SGI
Voicemail: 56791
> > Level 5, Walsh Wrightson Tower,				    Ph:
> +64-4-802 1455
> > 94-96 Dixon St, Wellington, NZ			  	   Fax:
> +64-4-802 1459
> >-- End of excerpt from Alistair Lambie
>
>
>
> --
> Alistair Lambie
				    alambie@wellington.sgi.com
> Silicon Graphics New Zealand				  SGI Voicemail: 56791
> Level 5, Walsh Wrightson Tower,				    Ph:
+64-4-802 1455
> 94-96 Dixon St, Wellington, NZ			  	   Fax:
+64-4-802 1459
>-- End of excerpt from Alistair Lambie



-- 
Alistair Lambie					    alambie@wellington.sgi.com
Silicon Graphics New Zealand				  SGI Voicemail: 56791
Level 5, Walsh Wrightson Tower,				    Ph: +64-4-802 1455
94-96 Dixon St, Wellington, NZ			  	   Fax: +64-4-802 1459

  parent reply	other threads:[~1997-04-09  2:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-09  2:09 init=/bin/sh and serial devices Mike Shaver
1997-04-09 14:22 ` Alistair Lambie
     [not found]   ` <alambie>
1997-04-09 14:29     ` Alistair Lambie
1997-04-09 14:31     ` Alistair Lambie [this message]
1997-04-09 14:24 ` Alistair Lambie
1997-04-09  4:29   ` Alex deVries
1997-04-09 18:46     ` Ariel Faigon
1997-04-09 18:46       ` Ariel Faigon
1997-04-09  7:06   ` Martin Knoblauch
1997-04-09 18:31     ` William J. Earl
1997-04-09 18:40       ` Ariel Faigon
1997-04-09 18:40         ` Ariel Faigon
1997-04-09 19:30     ` Alistair Lambie
1997-04-14  8:17     ` David S. Miller
1997-04-14 18:05       ` William J. Earl
1997-04-15  2:09         ` David S. Miller
1997-04-18 22:35           ` Alistair Lambie
1997-04-18 22:35             ` Alistair Lambie

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=9704091431.ZM9866@windy.wellington.sgi.com \
    --to=alambie@wellington.sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=shaver@neon.ingenia.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