From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: New user encountering problems
Date: Sat, 23 Sep 2000 11:58:36 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0009231155110.1013-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.21.0009231328030.12720-100000@jscp.yi.org>
I don't know why you might have had the troubles you mentioned Jacob. I
have two rethat systems myself and have never had any trouble with custom
kernels. I don't use make install to place them either.
After doing a make BzImage, I copy the new kernel to my /boot dir and
update lilo.conf manually. Personally I don't use the "standard" nameing
scheme. Partly because this only works if you have one kernel. I have
played arround and when doing stuff may try fiv or six different kernels
all with slightly different options in them. Instead, I use a date scheme.
My experiance has been that the kernel can be named anything. It can sit
anyplce on the disk that can be reached using the bios access to the disk.
--
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Seek simplicity -- and distrust it.
Alfred North Whitehead
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
Jerry Robinette
` Gorgotek Systems
` Kirk Wood
` Jacob Schmude
` Brent Harding
` Geoff Shang
` Brent Harding
` Jacob Schmude
` Kirk Wood [this message]
` Brent Harding
` Jacob Schmude
[not found] ` <Pine.LNX.4.21.0009231155110.1013-100000@localhost.localdom ain>
` Brent Harding
` Victor Tsaran
` Brent Harding
` Victor Tsaran
` Kerry Hoath
` Kirk Wood
` Victor Tsaran
` Distro discusion Kirk Wood
` Chris Nestrud
` Kirk Wood
` Gene Collins
` Victor Tsaran
` Jacob Schmude
` Brent Harding
` Victor Tsaran
` Brent Harding
` New user encountering problems Brent Harding
` HOWTOs (was Re: New user encountering problems) Jacob Schmude
` New user encountering problems Jacob Schmude
` William F. Acker WB2FLW +1-303-777-8123
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.0009231155110.1013-100000@localhost.localdomain \
--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).