From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: Slackware 8.0 partitioning tools.
Date: Sun, 16 Sep 2001 14:21:31 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0109161358450.24227-100000@ignatious> (raw)
In-Reply-To: <5.1.0.14.2.20010916094105.009e80f0@mail.tft-bbs.co.uk>
On Sun, 16 Sep 2001, Gordon Smith wrote:
> Hi. The layout of my system is a little strange, this was necessary. It is:
> Drive 1 = primary master
> CD-ROM = primary slave
> Drive 2 = ATA100 primary master
> Drive 3 = ATA100 Primary Slave
> Drive 4=ATA100 Secondary Master
> Drive 5 = ATA100 Secondary slave
And now we can solve a huge mystery. The following *should* represent the
drive letter vs the designation in linux:
1 - hda
cdrom - hdb
2 - hdf
3 - hdg
4 - hdh
5 - hdi
The first two are definately correct. But it is a certainty that your
drive 3 is *not* hdc. The reason SUSE is able to install is that it is not
making you specify the drive position. Suse was one of the first to
eliminate the need to understand a very easily misunderstood drive
designation.
Quite honestly, if you have a distribution installed, I would recomend
that you patch the kernel, compile and go on. I shied away from this task
for a long time. Then one day decided I had nothing better to do then
reinstall if I messed something up. The long and short is that it was
actually quite easy. In fact, it is so easy that I would recomend
everybody to compile their own kernel. Start with cutting out all the crap
in a stock kernel you don't use.
I have cut boot time significantly be eliminating the stuff in a stock
kernel that my machine doesn't use anyway. I cut it further by building in
things like network card support directly. Sure I made mistakes along the
way. I also found my own way of tracking what I have done. I discovered
that there is no need to name my kernel vmlinuz. I discovered that there
is no need to pout a softlink in the root directory to this. I discovered
that I can name my kernel to indicate the version number and date if I
choose.
You can find out a lot by playing here.
=======
Kirk Wood
Cpt.Kirk@1tree.net
The mind is like a parachute; it works much better when open.
If you're too open minded, your brains will fall out.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
Gordon Smith
` Gregory Nowak
` Gordon Smith
` Gregory Nowak
` Gordon Smith
` Kirk Wood
` Gordon Smith
` Saqib Shaikh
` Gordon Smith
` Gregory Nowak
` Frank Carmickle
` Gordon Smith
` Jacob Schmude
` Gordon Smith
` Frank Carmickle
[not found] ` <Pine.LNX.4.21.0109160640170.1418-100000@c1422183-a.ross1.p a.home.com>
` Gordon Smith
` Saqib Shaikh
` Gordon Smith
` Frank Carmickle
[not found] ` <Pine.LNX.4.21.0109160826040.1418-100000@c1422183-a.ross1.p a.home.com>
` Gordon Smith
` Gregory Nowak
` Frank Carmickle
[not found] ` <Pine.LNX.4.21.0109160726140.1418-100000@c1422183-a.ross1.p a.home.com>
` Gordon Smith
` Raul A. Gallegos
` Gregory Nowak
` Gordon Smith
` Kirk Wood [this message]
` Gordon Smith
` Jacob Schmude
` Gordon Smith
` Kirk Wood
` Saqib Shaikh
` Gordon Smith
` Saqib Shaikh
` Gordon Smith
Gregory Nowak
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.0109161358450.24227-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).