Re: Determining if GRUB is the bootloader in use on a system

2001-08-08 Thread OKUJI Yoshinori
IMO, you shouldn't use a BPB as an identifier, because the user can modify it arbitrarily. Instead, what do you think about just searching the string GRUB from a boot record? GRUB will have the string even for the future, and I don't think LILO will have the string itself (except when the user

Re: grub command works, but GRUB boot loader hangs

2001-08-08 Thread Ben Liblit
Okuji Yoshinori wrote: Debugging is, IMO, a general process OK, OK, you've shamed me into it. I have added a number of debugging print statements to GRUB's stage2. I have only one machine at this location, and the problems only appear when using GRUB as a boot loader, so my compile-test cycle

Re: Determining if GRUB is the bootloader in use on a system

2001-08-08 Thread Pixel
Jeremy Katz [EMAIL PROTECTED] writes: [...] missing the easy way to check and tell if GRUB is being used as the boot loader? well, we're using: offset magic offset magic [ 'grub', 0, \xEBG, 0x17d, stage1 \0 ], [ 'grub', 0, \xEBH, 0x17e, stage1 \0 ], [ 'grub', 0,

Re: grub command works, but GRUB boot loader hangs

2001-08-08 Thread Yoshinori K. Okuji
From: Ben Liblit [EMAIL PROTECTED] Subject: Re: grub command works, but GRUB boot loader hangs Date: Wed, 08 Aug 2001 03:22:33 -0700 get_diskinfo() calls get_diskinfo_standard(1, ...), which immediately returns error code 96. I find the 96 noteworthy, because this same call returns error

Re: [PATCH] Ensure serial device exists prior to use

2001-08-08 Thread Yoshinori K. Okuji
From: Jeremy Katz [EMAIL PROTECTED] Subject: [PATCH] Ensure serial device exists prior to use Date: Wed, 8 Aug 2001 02:00:49 -0400 We shouldn't try to use the serial terminal if the user hasn't properly configured it yet. This patch (against current CVS) makes it so ensures that we have set

quick grub question

2001-08-08 Thread Robert Ross
Hello, A friend and I are installing linux on a flash device, and currently we're using GRUB. One of the reasons we chose not to use LILO was that by default it writes to the device on every boot; these flash devices are only good for so many writes. We went looking through the FAQ and other

How to tell grub is installed

2001-08-08 Thread Parrish M Myers
Hello, I don't mean to be a bother, but... Does anyone know a simple way to detect weither grub is installed in the MBR (as oposed to lilo)? Will 'dd if=/' work for this. I don't want to change any of the info, just non-destructivly test which boot loader resides in the MBR. Thanks Parrish

Small problem...

2001-08-08 Thread Stephane Dalton
Hi guys, I've got a quick one for you. I'm trying to boot off a compact flash device connected to an IDE to CF adapter (Compact flash is very similar to IDE) the device behave normally when mounted under Linux and I can read and write to it without problem. BUT when I'm trying to boot out of

Re: [Bug-grub] DAC960 raid controller

2001-08-08 Thread Jason Thomas
your right, I just looked over the make_rd script again and see my mistake. But I think this patch (or the correct one) would be useless without other modifications to grub. On Thu, Aug 09, 2001 at 03:19:33AM +0900, Yoshinori K. Okuji wrote: From: Jason Thomas [EMAIL PROTECTED] Subject: Re:

Re: How to tell grub is installed

2001-08-08 Thread Yoshinori K. Okuji
See the archive of this mailing list. That kind of issue was discussed yesterday... Okuji ___ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub

Re: [Bug-grub] DAC960 raid controller

2001-08-08 Thread Yoshinori K. Okuji
From: Jason Thomas [EMAIL PROTECTED] Subject: Re: [Bug-grub] DAC960 raid controller Date: Thu, 9 Aug 2001 10:13:33 +1000 your right, I just looked over the make_rd script again and see my mistake. But I think this patch (or the correct one) would be useless without other modifications to

Re: [Bug-grub] DAC960 raid controller

2001-08-08 Thread Jason Thomas
well not sure exactly, but a debian user reported a bug trying to setup with one of these. I don't have one but tried to duplicate the problem using a fake device, and grub didn't like it. I created the device and set my root partition to mount from it and rebooted and then tried to do a grub