En réponse à OKUJI Yoshinori [EMAIL PROTECTED]:
Ok, I came back to Japan yesterday. I will be busy for a while,
because of house-moving and some desk works, but I'll try to read and
reply e-mail about GRUB accumulated in my mailbox from now on... Give
more time to me.
[BTW, why are
Geachte heer/mevrouw
Hartelijk welkom bij Teledirekt Nederland SoftwareNieuws.
Teledirekt Nederland is het grootste postorderbedrijf in
Nederland op het gebied van software.
Wilt u extra productinformatie of een goed advies?
Bel dan GRATIS de Teledirekt Verkoopadvieslijn: 0800 - 237 66 44.
Als u
I have discovered that this was the issue with a system that I had
previously reported that GRUB would Oops the kernel on - this is the
reason. Using the --no-mem-option flag to the 'kernel' command at the
grub prompt causes this problem to go away.
Derrik Pates | Sysadmin, Douglas School
-BEGIN PGP SIGNED MESSAGE-
On Wednesday, 1. August 2001 17:39, you wrote:
I have discovered that this was the issue with a system that I had
previously reported that GRUB would Oops the kernel on - this is the
reason. Using the --no-mem-option flag to the 'kernel' command at the
Mario Klebsch writes:
MK Since linux does not require the mem= parameter anymore, will the
MK option be reversed some time in the future (renamed to
MK -mem-option)?
Better yet, is there a way for Grub to detect a newer version of
linux, and set the default based on that?
--
Gordon
I have tried this on my desktop at home, and had a friend try it with a
Sony Vaio laptop - this is still the case as of GRUB 0.90. It just hangs,
never shuts down the system at all, even though it's obviously supposed
to. (I've looked at the APM shutdown code and the Linux kernel's APM
shutdown
