Well this is my configuration:
Main board:
Asus P4B
Two EIDE hard disk ( Quantum and Maxtor ):
- hda : Windows ( Primary master )
- hdc : Linux ( Secondary Master ) with the swap partition on hdc1 and
root filesystem on hdc2 . I have a Slack 8
I downloaded, compiled and installed Grub
On Saturday 26 January 2002 12:23 am, you wrote:
At Fri, 25 Jan 2002 17:05:17 +0100,
Han Holl wrote:
I can get this behaviour with grub by protecting all
entries but the default with 'lock', but this is rather
tedious and can easily lead to errors.
Why? How many entries do you have?
At Sat, 26 Jan 2002 15:21:18 +0100,
Han Holl wrote:
I distribute a new kernel occasionally, remove the oldest,
and must declare the newest default.
Our users must not be allowed to boot the wrong kernel
accidentally, but I want to keep those as backup.
This is all done by scripting, and I
On Saturday 26 January 2002 05:21 pm, Yoshinori K. Okuji wrote:
At Sat, 26 Jan 2002 15:21:18 +0100,
That's true in your case, as you chose the LILO way. Generally
speaking, however, GRUB is much more flexible. I think it always makes
things complex to obtain flexiblity (e.g. consider
I am using a RAID setup on /dev/hda with my root being /dev/hda2. I
installed grub on the system when the root was /dev/hdc2. After changing
everything in /boot/grub to refer to /ev/hda2 it still tries booting to
/dev/hdc2. I cannot understand why. Can you please help me?
Mark Collette
Hi,
I just saw a posting on FreshMeat. A guy was unable to boot
windows since converting his boot partition to being a
dynamic disk (he was actually using lilo, but not certain
grub would work either).
In case you're not familiar, the logical disk manager (LDM)
in windows 2000 XP, uses dynamic
On Sat, 26 Jan 2002, Mark Collette wrote:
I am using a RAID setup on /dev/hda with my root being /dev/hda2. I
installed grub on the system when the root was /dev/hdc2. After changing
everything in /boot/grub to refer to /ev/hda2 it still tries booting to
/dev/hdc2. I cannot understand why.
Here is a TODO list for 0.92. The order roughly follows the priority
list in my mind.
* Get rid of fsys_ext2fs.c, and add fsys_ext3fs.c which will support
both ext2 and ext3. This is what I'm doing now. I haven't realized
how to speed up lookups of a JBD log yet, though.
* Rewrite the
