From: "orange-pc.ces.clemson.edu" <grant@grantgoodyear.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Build Doc Error
Date: 15 Jun 2002 10:06:28 -0400 [thread overview]
Message-ID: <1024149988.3753.45.camel@server.grantgoodyear.org> (raw)
In-Reply-To: <00b201c21440$2cfc9b50$7f542ed5@aap>
> Hmmm... I thought this was a distro for people who KNOW what they're doing
> ;-)
> Maybe, instead of creating such a symlink, there could be a short mention in
> the docs about the path to the files being relative to /boot.
> There are so many things newbies (of which I am one) have to learn the hard
> way that this one, in comparison, is very minor.
Why? I'm not sure what problem you're trying to solve. By having the
boot --> . symbolic link we have an elegant solution that works for
everybody, and doesn't hurt anybody. If the user has a separate /boot
partition and doesn't want to have grub point to (hd,x)/boot, then
that's fine. That user can even delete the symlink.
There was a time when we did not have that symbolic link. I know that
I got very tired of the subsequent "Hey, my computer won't boot." "Did
you use a separate /boot partition like it says in the docs?"
rounds that then occurred several times per week. So, Daniel Robbins
came up with a transparent solution that works for everybody.
Finally, I would like to clear up a common misconception. Gentoo Linux
is, indeed, "geared towards Linux power users". My personal opinion,
though, is that
it is unrealistic to expect even power users to understand
everything that goes into a Linux distribution, so saying that Gentoo
is "a distro for people who KNOW what they're doing" seems like
a bit much. (In fact, many people seem to come to Gentoo precisely
so that they can learn more about Linux without the drudgery required
with installing an LFS distro.) I prefer to say
that Gentoo Linux is a distro for people who want flexibility. Anything
we can do to make it easier for the user that does _not_ unduly impact
flexibility is something we should do, and most, if not all, of our
developers instinctively seem to understand that notion. Of course,
we don't always succeed, but we do try.
The opinions expressed above are, of course, my own. Daniel Robbins
and the other developers may not agree.
-g2boojum-
next prev parent reply other threads:[~2002-06-15 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 19:21 [gentoo-dev] Build Doc Error Hanford_Smith, Jason
2002-06-14 19:52 ` Doug Goldstein
2002-06-14 21:18 ` Colin Morey
2002-06-15 7:42 ` Mario Witt
2002-06-15 14:06 ` orange-pc.ces.clemson.edu [this message]
2002-06-16 10:05 ` Ryan Phillips
2002-06-15 5:02 ` orange-pc.ces.clemson.edu
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=1024149988.3753.45.camel@server.grantgoodyear.org \
--to=grant@grantgoodyear.org \
--cc=gentoo-dev@gentoo.org \
/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