From: Ishikawa <ishikawa@yk.rim.or.jp>
To: wb <dead_email@nospam.com>
Cc: Paul Blazejowski <paulb@blazebox.homeip.net>,
"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 01:10:21 +0900 [thread overview]
Message-ID: <3F2FD6ED.1005BB2C@yk.rim.or.jp> (raw)
In-Reply-To: 3F2F84D2.8000202@nospam.com
(Sorry this is not strictly related to SCSI, but I could not help it.)
Regarding the use of a program from uucp suite
for console output capture,
we can use C-Kermit as well.
> 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.
Or you can use C-Kermit.
See
http://www.columbia.edu/kermit/ckermit.html
for details. There are precompiled packages.
> ... [omission ] ...
> 5. Start uucp on the HOST:
>
> cu -l /dev/ttyS0 -s 9600
kermit
set line /dev/ttyS0
set speed 9600
connect
and you can issue other commands.
set [space] ?
will print all the available options at that point.
(You can log the interaction into a file by issueing
a command to kermit, too, but using script and then run kermit
inside the scripted session might be easier.)
(Generally speaking hitting ? somewhere on the kermit command line
prints usable options/setting/keywords, and so
you can learn the basics very quickly.)
You can set up a startup file that sets
the device name, speed, parity, data size, etc. and
so you don't have to type all the command every time.
While I agree cu might work well for one shot job,
running a full terminal emulator like C-Kermit
helps us in the long term.
Just thought to let you know a full-featured terminal
emulator is available under linux.
> John Donnelly AT HP DOT com
Is the succinct and to the point steps
part of a widely available document?
I wish I knew this a few years ago.
--
int main(void){int j=2003;/*(c)2003 cishikawa. */
char t[] ="<CI> @abcdefghijklmnopqrstuvwxyz.,\n\"";
char *i ="g>qtCIuqivb,gCwe\np@.ietCIuqi\"tqkvv is>dnamz";
while(*i)((j+=strchr(t,*i++)-(int)t),(j%=sizeof t-1),
(putchar(t[j])));return 0;}/* under GPL */
next prev parent reply other threads:[~2003-08-05 16:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 18:22 Badness in device_release at drivers/base/core.c:84 Diffie
2003-08-01 21:27 ` Greg KH
2003-08-02 5:40 ` Diffie
2003-08-01 21:44 ` Andrew Morton
2003-08-01 23:27 ` Mike Anderson
2003-08-02 5:57 ` Diffie
2003-08-02 5:53 ` Diffie
2003-08-03 1:55 ` Diffie
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 [this message]
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
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=3F2FD6ED.1005BB2C@yk.rim.or.jp \
--to=ishikawa@yk.rim.or.jp \
--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 \
--cc=paulb@blazebox.homeip.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.