From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: New Debian Install - HELP!
Date: Sat, 11 Oct 2008 16:50:56 +0800 [thread overview]
Message-ID: <CD576A3D97D3440F8A2490D74A8FE2E4@bouncy> (raw)
In-Reply-To: <20081011084227.GA21623@pillow.holmesgrown.com>
Basically the reason grub won't do what you want right now is because you
are not used to it.
Lilo hard codes the boot locations of the kernel and initial ram disk into a
block list which breaks every time you rebuild an initrd or recompile or
move the kernel.
Grub can read file systems, and you can fix it when the boot loader
scrambles unlike lilo which just goes
lililililililililili
You can put lilo on and move to grub once you know how to make it go beep,
how to make it spit its output through a serial port etc if you so choose.
you probably wanted the options
speakup_synth=xxxxx debconf/priority=low
so it would ask you which boot loader to install; alternatively set the
priority to low on the main menu.
Regards, Kerry.
----- Original Message -----
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Saturday, October 11, 2008 4:42 PM
Subject: Re: New Debian Install - HELP!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Yeah, I got past that now. I did it by pressing down arrow once
followed by tab and then typed speakup.synth=spkout. That part
worked. I am having a hang-up right now as grub is the default loader
and after the install finished, I was forced to reboot. First of all,
I don't know how to interract with grub and over-ride kernel
parameters; but worse yet, my machine at the moment won't boot into
anything!!!. I have an existing windows partition on the first disk
and am I'm installing linux on the second disk. Apparently, grub did
not configure this properly. It's like windows is trying to boot
strait away and grub never comes up at all. I'm now sitting here
waiting to errase the entire linux partition so I can start over with
Debian and maybe I can get the thing to skip grub and install lilo
instead. I know lilo from my Slackware days and I know it is capable
of booting on one drive and dual booting for both windows and linux.
Plus I can make lilo talk at the beginning. Grub looks to o
convoluted to me as a first impression.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
Steve Holmes
` Erik Heil
` Tyler Littlefield
` Kitty Litter
` Samuel Thibault
` Can anyone explain how the syslinux menus work? Kitty Litter
` New Debian Install - HELP! Samuel Thibault
` Steve Holmes
` Alex Snow
` Steve Holmes
` Kerry Hoath [this message]
` Tony Baechler
` Steve Holmes
` Kerry Hoath
` Tony Baechler
` New Debian Install - HELP! grub or lilo Frank Carmickle
` New Debian Install - HELP! Gregory Nowak
` Steve Holmes
` Gregory Nowak
` Steve Holmes
` Alex Snow
` Steve Holmes
` Gregory Nowak
` Kerry Hoath
` Kerry Hoath
` Kitty Litter
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=CD576A3D97D3440F8A2490D74A8FE2E4@bouncy \
--to=kerry@gotss.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).