public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Zachary Kline <kline.zachary@gmail.com>
To: speakup@braille.uwo.ca
Subject: grub2 impressions
Date: Fri, 27 Nov 2009 16:14:00 -0800	[thread overview]
Message-ID: <20091128001400.GA4428@blackbird> (raw)

Hi All,
I've just decided to take the plunge and switch my dual boot ArchLinux
system from using grub-legacy to grub2.  My initial impressions are
below, for what it's worth.  I should note here that I've never felt it
necesary to have grub beep at the boot menu or any other such feature.
I just set an infinite timeout and go.
Superficially, menu.lst has gone, replaced by grub.cfg.  The syntax of
device specifications has been made a bit irregular.  Disks are still
numbered at 0, partitions are numbered at 1.  One wonders if the
developers plan on regularizing the disk numbers at some point?  So,
for instance, /dev/sda1 is (hd0,1) and sda5 is (hd0,5).
That aside, the command syntax is different.  You'll be using set a lot,
to change variables like your timeout or the default menu entry.  "set
timeout=0", for instance.  Menu entries are defined by blocks enclosed
in braces, instead of the title keyword.
menuentry "Arch Linux" {
set root=(hd0,5)
linux /boot/vmlinuz26 root=/dev/sda5 ro
initrd /boot/kernel26.img
}
This is the entry I use to boot ArchLinux over here.  I still need to
figure out how to get that to use uuids, but for now this certainly does
the job.
The documentation provided with my ArchLinux package of 1.97.1 is
incomplete.  There's a skeleton info menu with a few introductory nodes
already filled in, but it leaves a lot to be desired.  Nevertheless,
there's a sample configuration file included (at least in my package).
Overall, I'm happy I switched.  I'm sure the system will be going
through some pollishing before it's officially bug free (TM), butoverall
I like being on the leading edge when it comes to these things.  I
quibble with the developers to an extent over minor cosmetic issues, but
that's neither here nor there.  I hope this helps anyone who might want
to give this a try.
All the best,
Zack.

             reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Zachary Kline [this message]
 ` John G. Heim
   ` Zachary Kline
     ` Jason White
       ` Steve Holmes
       ` John G. Heim
 ` Kirk Reiser

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=20091128001400.GA4428@blackbird \
    --to=kline.zachary@gmail.com \
    --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).