From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: Lilo geo_comp_addr Error with 2.4.0
Date: Tue, 9 Jan 2001 07:40:27 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.21.0101090736020.24914-100000@ignatious> (raw)
In-Reply-To: <x77l44c1so.fsf@speech.braille.uwo.ca>
Janina,
One thing that comes to mind here for me. I know that slackware puts the
kernel image in the root directory with a softlink in the /boot
directory. This can cause confusion as far as I can see. What I have found
is that you can put the image in the /root directory (which I go ahead and
put on the first available partition) and skip the softlink altogether. I
name the kernel something that will help me remember when I compiled it
and any special features. I can find nothing sacred about vmlinuz other
then that it is the common name scheme. But I have seen the same (or a
similar) problem where someone continued following the slackware original
setup.
=======
Kirk Wood
Cpt.Kirk@1tree.net
Cluelessness
There are no stupid questions, but there are a lot of
inquisitive idiots
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Janina Sajka
` Kirk Reiser
` Janina Sajka
` Kirk Reiser
` Kirk Wood [this message]
` John Covici
` Kerry Hoath
` Kerry Hoath
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.LNX.4.21.0101090736020.24914-100000@ignatious \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).