From: Luke Davis <ldavis@voicenet.com>
To: infynity@cyberhighway.net
Cc: John Covici <covici@ccs.covici.com>, blinux-list@redhat.com
Subject: Re: segmentation fault?? and fsck problems.
Date: Wed, 10 Jun 1998 15:22:42 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.3.96.980610152110.14835C-100000@unix01> (raw)
In-Reply-To: <Pine.LNX.3.95.980610055249.26166C-100000@draken.localnet>
I haven't followed this conversation very extencivly; but shouldn't it be
possible to redirect the entire console process, nomatter what, through
lilo's console redirect feature?
I'v heard of this feature, but have never managed to get it working.
As I said: I haven't followed this closely enough to know if this is what
is needed or not.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <357e4331.ccs@ccs.covici.com>
` L. C. Robinson
` Luke Davis [this message]
[not found] ` <+Fvf10r1Jg6U089yn@ccs.covici.com>
` John Covici
[not found] ` <h3uf10r1J8vU089yn@ccs.covici.com>
` John Covici
` L. C. Robinson
[not found] <357f91ed.ccs@ccs.covici.com>
` L. C. Robinson
[not found] ` <5MZg10r1JgCU089yn@ccs.covici.com>
` John Covici
` L. C. Robinson
segmentation fault?? John Covici
` segmentation fault?? and fsck problems L. C. Robinson
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.96.980610152110.14835C-100000@unix01 \
--to=ldavis@voicenet.com \
--cc=blinux-list@redhat.com \
--cc=covici@ccs.covici.com \
--cc=infynity@cyberhighway.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 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).