From: Alan McKinnon <alan@linuxholdings.co.za>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: grub chainloader
Date: Wed, 18 Jul 2007 17:00:32 +0200 [thread overview]
Message-ID: <200707181700.32834.alan@linuxholdings.co.za> (raw)
In-Reply-To: <AC336AF9-111A-48E6-BBDD-19C083083288@stellar.eclipse.co.uk>
On Wednesday 18 July 2007, Stroller wrote:
> On 18 Jul 2007, at 13:35, Etaoin Shrdlu wrote:
> > ...
> > You can get everything at once and in the same place using the
> > online docs:
> >
> > http://www.gnu.org/software/grub/manual/grub.html
>
> This manual is very excellent.
>
> I believe you can also get it in PDF format - I printed it out over 3
> years ago and still occasionally refer to it. How I miss my former
> employers' printer which would fold & stable paper to give A4 & A5
> booklets.
>
> The GRUB manual is as good as lots of books you'd pay $$$ for.
Yes, it is good documentation, in that everything is there - complete
docs are a rare thing these days. But few people that I've come across
thought to check the info pages and get it.
> >> And they are also written with the assumption that the reader
> >> understands the confines a boot loader has to work in.
>
> I don't know. I think the overview is pretty clear <http://
> www.gnu.org/software/grub/manual/grub.html#Overview>, and leads into
> the remainder of the documentation quite well.
Well there's at least two people who know how boot loaders work. But
it's not an easy concept to grasp for the average person. I get a feel
that you are not an average person so your impressions are not valid
for them. The big stumbling block is getting people to grasp that grub
is not an OS, it's not a linux app as linux is not in memory yet. And
yet, it can still read files and dirs that linux put there, and it's
config file read at run time is a linux file. It's enough to make the
average person's head spin (and does) - it can easily take two hours
for me to get a class full of reasonably bright Windows techies to
grasp why you use
kernel (hd0,0)/vmlinuz-<version> <options>
with a separate boot partition, and
kernel (hd0,0)/boot/vmlinuz-<version> <options>
when /boot is not a separate partition.
Then there's the bit about grub being able to load linux and
Multiboot-compliant kernels natively, but Windows and others must be
chainloaded...
None of this means that the grub docs are poor - it's just that
bootloaders are tricky beasts to grasp and the docs are correspondingly
hard to write so that Joe Average User gets it all first time through
--
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?
Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-07-18 15:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 22:50 [gentoo-user] grub chainloader Thufir
2007-07-17 23:12 ` [gentoo-user] " »Q«
2007-07-17 23:51 ` Thufir
2007-07-18 12:18 ` Alan McKinnon
2007-07-18 12:35 ` Etaoin Shrdlu
2007-07-18 14:20 ` Stroller
2007-07-18 15:00 ` Alan McKinnon [this message]
2007-07-18 16:06 ` Stroller
2007-07-18 17:32 ` Neil Bothwick
2007-07-19 7:44 ` Alan McKinnon
2007-07-19 0:31 ` Iain Buchanan
2007-07-18 13:30 ` Александър Л. Димитров
2007-07-18 19:35 ` Thufir
2007-07-19 0:25 ` Iain Buchanan
2007-07-19 0:51 ` Thufir
2007-07-19 11:36 ` Hans-Werner Hilse
2007-07-19 14:02 ` Iain Buchanan
2007-07-18 0:02 ` Iain Buchanan
2007-07-18 6:53 ` Mick
2007-07-18 15:36 ` Neil Bothwick
-- strict thread matches above, loose matches on Subject: below --
2007-07-19 7:14 burlingk
2007-07-19 6:25 ` Boyd Stephen Smith Jr.
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=200707181700.32834.alan@linuxholdings.co.za \
--to=alan@linuxholdings.co.za \
--cc=gentoo-user@lists.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