, September 20, 2001 5:40 PM
Subject: Wishlist (it's a must)
Hi!
Please remove all unnecessary clear screens from the
code. Especially the cls() which gets called when stage2 is entered.
It prevents experts and others from seeing error messages!
So they cant
-BEGIN PGP SIGNED MESSAGE-
On Sunday, 23. September 2001 01:52, you wrote:
So why not add some error code return values and passing so that the
boot process halts or stalls to give you time to read the error
message. Absent any error codes, clear screen and continue?
This would work
Ok, I think now is the time when I should comment on this issue.
First of all, I agree that GRUB shouldn't erase anything on the screen
unnecessarily. IIRC, this is not the first time that the issue rose in
this mailing list. The reason that we didn't fix the problem at that
time was just that
-BEGIN PGP SIGNED MESSAGE-
On Saturday, 22. September 2001 03:21, Robert Siemer wrote:
Automatically calling cls() prevents me from seeing output. Error
messages and other.
...
Who on this list really suppresses e.g. kernel output??
I did so in a project a year ago. I removed lots
Mario Klebsch [EMAIL PROTECTED] writes:
So, my vote is for removing the cls() calls and leting the menu clear
the screen. Howebver, I am not sure what to do in case there are error
messages and the user wants a menu. Perhaps a 'hotkey' could be used to
suppress the menu.
The earlier
From: Gordon Matzigkeit [EMAIL PROTECTED]
Mario Klebsch [EMAIL PROTECTED] writes:
So, my vote is for removing the cls() calls and leting the menu clear
the screen. Howebver, I am not sure what to do in case there are error
messages and the user wants a menu. Perhaps a 'hotkey' could be
: Saturday, September 22, 2001 4:39 PM
Subject: Re: Wishlist (it's a must)
From: Gordon Matzigkeit [EMAIL PROTECTED]
Mario Klebsch [EMAIL PROTECTED] writes:
So, my vote is for removing the cls() calls and leting the menu clear
the screen. Howebver, I am not sure what to do in case
Subject: Wishlist (it's a must)
Hi!
Please remove all unnecessary clear screens from the
code. Especially the cls() which gets called when stage2 is entered.
It prevents experts and others from seeing error messages!
So they cant report bugs or debug very well!
Regards
a compile
time option.
bill r
- Original Message -
From: Christoph Plattner [EMAIL PROTECTED]
To: sese granola [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Robert Siemer [EMAIL PROTECTED]
Sent: Friday, September 21, 2001 4:29 PM
Subject: Re: Wishlist (it's a must)
Menu.lst is executed much
From: sese granola [EMAIL PROTECTED]
Ok, let me rephrase then. There are definitely times when I want
lots of output for debugging but generally I want no output beyond
the primary task of loading an os.
I hate to choose one or the other and would hope some way
to provide for both
Hi!
Please remove all unnecessary clear screens from the
code. Especially the cls() which gets called when stage2 is entered.
It prevents experts and others from seeing error messages!
So they cant report bugs or debug very well!
Regards,
Robert
PS: Likewise it also
I would rather see an option used via menu.lst for this behavior.
- Original Message -
From: Robert Siemer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 20, 2001 5:40 PM
Subject: Wishlist (it's a must)
Hi!
Please remove all unnecessary clear screens from
:40 PM
Subject: Wishlist (it's a must)
Hi!
Please remove all unnecessary clear screens from the
code. Especially the cls() which gets called when stage2 is entered.
It prevents experts and others from seeing error messages!
So they cant report bugs or debug very well
Please remove all unnecessary clear screens from the
code. Especially the cls() which gets called when stage2 is
entered.
It prevents experts and others from seeing error messages!
So they cant report bugs or debug very well!
From: sese granola [EMAIL PROTECTED]
I would rather see
14 matches
Mail list logo
