From: Robertdkeys@aol.com (Robertdkeys@aol.com)
Subject: [TUHS] flaky webster or sigma WQESD4 and RQD11 controllers on KA650???
Date: Fri, 13 Dec 2002 11:52:14 EST [thread overview]
Message-ID: <161.1881237c.2b2b6a3e@aol.com> (raw)
I found out what the problem was.....(sheepishly
ducking...(:+\\...). At 3 in the morning I had
a typeo in the config file that the old eyeballs
did not catch. I had typed in the partitions
to allocate to root and swap, as opposed to just
the the disks. It compiled fine, but when run,
it paniced and dumped itself all over the floor.
So much for myopic eyes programming at 3 in the
morning.....
(:+{{.....
Bob
next reply other threads:[~2002-12-13 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 16:52 Robertdkeys [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-14 4:00 Robertdkeys
2002-12-14 2:30 John Holden
2002-12-14 1:21 Norman Wilson
2002-12-13 19:33 Carl Lowenstein
2002-12-13 7:29 Michael Sokolov
2002-12-13 5:50 Robertdkeys
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=161.1881237c.2b2b6a3e@aol.com \
--to=robertdkeys@aol.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 NNTP newsgroup(s).