There is a typo in grub-install that prevents the printing of a
diagnostic message. The patch below should explain it better.
RCS file: /cvs/grub/util/grub-install.in,v
retrieving revision 1.11
diff -u -b -B -c -r1.11 grub-install.in
cvs server: conflicting specifications of output style
*** gru
From: Michael Riepe <[EMAIL PROTECTED]>
Subject: Re: appropriate code for a GRUB-specific option
Date: Sat, 27 May 2000 14:55:59 +0200
> You could use the Vendor Class Identifier (code 60) and Vendor Specific
> Information (code 43) options with encapsulated vendor-specific options
> to create a
Hello from Gregg C Levine usually at Jedi Knght Computers
(This is is a resend to acknowledge my successful subscription to this list!
I was advised to send it, the first time, at the suggestion of the Boss's
Admin Assistant. Now it is because of the reason above.)
I am writing to advise you folks
Hello from Gregg C Levine usually at Jedi Knght Computers
I am writing to advise you folks of a successful boot using the boot img
stored with the other Grub files, at the Alpha store fileserver. This one I
used the DOS/Windows rawrite file/command to write it out to a blank floppy.
It behaved exa
Finally, I've added diskless support into GRUB, based on patches by
Christoph and Chip. I haven't tested it at all yet, though I've
checked the build process very carefully, so you shouldn't expect that
it will work well.
Okuji
Hello,
Currently I'm working on integrating diskless support into GRUB, so
that it will be able to be used in a diskless environment (PXE or
NBI). The support is quite trivial, as GRUB itself doesn't have to
provide the user any ROM images (because we use Etherboot, Netboot, or
a PXE ROM for
