public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: grub chainloader
Date: Wed, 18 Jul 2007 17:06:57 +0100	[thread overview]
Message-ID: <4A3B8A4F-1B2E-4892-BC7F-5764A206DF8D@stellar.eclipse.co.uk> (raw)
In-Reply-To: <200707181700.32834.alan@linuxholdings.co.za>


On 18 Jul 2007, at 16:00, Alan McKinnon wrote:
>> ...
>> 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.
>
> ... 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.

Um... surely the config file (um... grub.conf, right?) is _just_ a file.

It's not a Linux file, it's not a GRUB file, it's just a text file,  
which can be edited by any operating system that can write to the  
partition.

I have in the past considered putting grub.conf on a FAT32 partition  
- I'm not 101% sure that'd work but I've never tried because I never  
actually saw the usefulness.

> 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 ...

You clearly have more experience than I do with teaching novices  
about Linux.

You might ask them to consider - as a teaching aid - the Windows XP  
boot.ini file (I believe this is retired in Vista).

Boot.ini can be edited in Windows' Notepad in much the same way  
grub.conf can be edited with vi or nano. Very few Windows users will  
have any experience of doing more than removing an extra line (where  
the system was dual-booting to a previous installation of Millennium  
Edition, for instance) or reducing the countdown time before  
automatically booting the default entry, but if your students are  
bright then they will be aware of the boot.ini and will have done  
that much.

Stroller.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-07-18 16:13 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
2007-07-18 16:06             ` Stroller [this message]
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=4A3B8A4F-1B2E-4892-BC7F-5764A206DF8D@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --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