From: Paul Blazejowski <paulb@blazebox.homeip.net>
To: wb <dead_email@nospam.com>
Cc: "Justin T. Gibbs" <gibbs@scsiguy.com>,
Patrick Mansfield <patmans@us.ibm.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Badness in device_release at drivers/base/core.c:84
Date: Wed, 06 Aug 2003 12:55:55 -0400 [thread overview]
Message-ID: <1060188955.887.3.camel@blaze.homeip.net> (raw)
In-Reply-To: <3F2F84D2.8000202@nospam.com>
[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]
On Tue, 2003-08-05 at 06:20, wb wrote:
> >
> > I'll look into serial console and try to set it up.Do i need extra
> > hardware or cables to run serial console? any poniters or setup
> > suggestions would be welcome as i never used serial consoles before.
> > Regards,
> >
> > Paul
> > -
>
> Your need a NULL modem serial cable available
> from any computer store.
>
> Install uucp - I use on the HOST :
>
> uucp-1.06.1-33.7.2.
>
> Also , LILO is broken on some machines and ignores
> serial input so make sure you use at least
>
> lilo-21.6-71
>
> On the TARGET
>
> 1. Connect the serial ports together ( COM1->COM1 ) with
> the serial cable .
>
> 2. Modify LILO to use serial line on the TARGET
> add to lilo.conf:
> append="console=ttyS0,9600n8 console=tty0 "
> serial=0,9600N8
>
> Run lilo
>
> 3. Add to /etc/inittab on the HOST
>
> S0:s12345:respawn:/sbin/agetty 9600 ttyS0
>
> 4. To see ALL THE CONSOLE MESSAGES during boot on the TARGET
>
> mv /dev/console /dev/console.org
> ln /dev/ttyS0 /dev/console
>
> 5. Start uucp on the HOST:
>
> cu -l /dev/ttyS0 -s 9600
>
> 6. Boot your target
>
> ///
>
> John Donnelly AT HP DOT com
>
John,
I appreciate your writing short and sweet howto :-).
I was able to get it going from FreeBSD 5.1 box with cu -l /dev/ttyd0
2&<1 > log to my Linux machine.
Thank you for helping.
Paul B.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-06 16:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030801182207.GA3759@blazebox.homeip.net>
2003-08-01 21:44 ` Badness in device_release at drivers/base/core.c:84 Andrew Morton
2003-08-01 23:27 ` Mike Anderson
[not found] ` <20030803015510.GB4696@blazebox.homeip.net>
2003-08-03 2:07 ` Andrew Morton
2003-08-03 21:47 ` Diffie
2003-08-03 21:52 ` Andrew Morton
2003-08-03 22:23 ` Diffie
2003-08-03 22:31 ` Diffie
2003-08-04 16:30 ` Patrick Mansfield
2003-08-04 17:48 ` Paul Blazejowski
2003-08-04 18:26 ` Paul Blazejowski
2003-08-04 18:57 ` Patrick Mansfield
2003-08-04 19:36 ` Justin T. Gibbs
2003-08-05 2:21 ` Paul Blazejowski
2003-08-05 10:20 ` wb
2003-08-05 16:10 ` Ishikawa
2003-08-06 16:58 ` Paul Blazejowski
2003-08-06 17:20 ` Chiaki
2003-08-13 2:03 ` Chiaki
2003-08-06 16:55 ` Paul Blazejowski [this message]
2003-08-05 7:18 ` Paul Blazejowski
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=1060188955.887.3.camel@blaze.homeip.net \
--to=paulb@blazebox.homeip.net \
--cc=akpm@osdl.org \
--cc=dead_email@nospam.com \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.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