grub-0.5.96.1 grub-install problems with /dev/fd0

2000-10-23 Thread Dirk Herrmann
Hello GRUB developers, nice work so far, and very good documentation also! However, I have had the following problems: * The sed commands in line 79 and 81 go across two lines, but these lines are not ended with `\` * giving '(fd0)' as the argument does not work. Again, the above lines

Re: grub 0.5.96.1 bugfix for grub-install.in

2000-10-23 Thread OKUJI Yoshinori
From: "Markus F.X.J. Oberhumer" [EMAIL PROTECTED] Subject: grub 0.5.96.1 bugfix for grub-install.in Date: Mon, 23 Oct 2000 16:23:45 +0200 (CEST) This is the ChangeLog entry for patch attached below: 2000-10-23 Markus F.X.J. Oberhumer [EMAIL PROTECTED] * util/grub-install.in

Re: grub-0.5.96.1 grub-install problems with /dev/fd0

2000-10-23 Thread OKUJI Yoshinori
From: Dirk Herrmann [EMAIL PROTECTED] Subject: grub-0.5.96.1 grub-install problems with /dev/fd0 Date: Mon, 23 Oct 2000 15:55:46 +0200 (MEST) * The sed commands in line 79 and 81 go across two lines, but these lines are not ended with `\` Sorry for the inconvenience. That was fixed after

Re: GRUB 0.5.97 doesn't handle kernel parameters

2000-10-23 Thread tschweikle
From: [EMAIL PROTECTED] Subject: Re: GRUB 0.5.97 doesn't handle kernel parameters Date: Wed, 18 Oct 2000 12:28:39 +0200 Does Grub 0.5.97 calculate the kernel size wrong? It reports a size 7 byte less than Grub 0.5.95. That's fine. That's just because of an alignment. BTW, I have no

trying 0.5.96.1

2000-10-23 Thread Jeff Sheinberg
Hi, I am reporting two issues with grub 0.5.96.1, specifically related to the grub shell, 1. When run in batch mode, the echoing of long lines is incorrect, this is probably related to the next issue. 2. When run in interactive mode, the command editing uses a truncate mode

Re: trying 0.5.96.1

2000-10-23 Thread OKUJI Yoshinori
Hi Jeff, From: Jeff Sheinberg [EMAIL PROTECTED] Subject: trying 0.5.96.1 Date: Mon, 23 Oct 2000 19:04:23 -0400 (EDT) 1. When run in batch mode, the echoing of long lines is incorrect, this is probably related to the next issue. I intentionally ignored this, as I was tired from