Re: Lead-up message 'Welcome to GRUB!' inverted text printed lowlevel via BIOS ?!?
On Sun, Feb 21, 2010 at 4:00 AM, Robo L wrote: > > Hi all, > > Firstly I would like to thank everyone for the reply and Your time. > > I would like to clarify the issue. > First I need to hide the very first Welcom message because I need to hide > GRUB for other users of MS Windows on my PC. I need it only for myself. I'm not entirely certain, but: (1) I think GRUB is licensed under GPLv3 or higher only (2) GPLv3 covers what were considered to be loopholes in GPLv2 (firmware enforced signature, software-as-a-service) therefore (3) Your use of GRUB (copying it into the boot record) requires you to provide your users with notice of their GPL rights to your version of GRUB. So one can hardly say that "another user on my PC not venture a guess that there is a GRUB" if you are required to tell them that GRUB is there and offer them the source code. > Richard: redirection is not good idea for me, becouse II need classical > console. I wrote a module with hidden password (secret process - no response > on console - silent) If match then redirect to boot linux. The nature of the > process is that another user on my PC not venture a guess that there is a > GRUB and secound linux OS! Security through obscurity is never a good idea and especially not when you have to give away the source code. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Lead-up message 'Welcome to GRUB!' inverted text printed lowlevel via BIOS ?!?
On Sun, Feb 21, 2010 at 08:56:15PM +0100, Robo L wrote:
> I found this function and make comment long ago
> After compilations welcome text not exist in binaries and GRUB still printed
> Welcome.
> Must be other function. I search in asm code, but still unsuccessfully.
No, that's the only place it comes from. If you're still seeing it,
then you haven't properly reinstalled the rebuilt version, somehow.
Perhaps you didn't run grub-install, or perhaps you ran it with the
wrong destination.
> btw: This function do not print Inverted.
It's called as follows:
grub_setcolorstate (GRUB_TERM_COLOR_HIGHLIGHT);
grub_printf ("Welcome to GRUB!\n\n");
grub_setcolorstate (GRUB_TERM_COLOR_STANDARD);
The grub_setcolorstate calls are what causes the message to be printed
in inverse video.
--
Colin Watson [cjwat...@ubuntu.com]
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Lead-up message 'Welcome to GRUB!' inverted text printed lowlevel via BIOS ?!?
Hi Colins, I found this function and make comment long ago After compilations welcome text not exist in binaries and GRUB still printed Welcome. Must be other function. I search in asm code, but still unsuccessfully. Rebuild or reedit binaries is like a last kick of dead :-) btw: This function do not print Inverted. Robo ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: [patch] search for partition using GPT GUID
On Sun, Feb 21, 2010 at 01:32:15PM +0100, Michal Suchanek wrote: > It has been explained that using the NTFS UUID is about equivalent of > using the volume label. If it is sufficient why are we using UUIDs at > all? We can use the much more readable labels everywhere and get rid > of those long and impractical UUIDs completely. Volume labels (in the general case; I don't know specifically about NTFS) are set by system administrators by hand. GRUB cannot assume that any filesystem has a volume label, or that they don't clash. (For example, Red Hat's installer used to have the unwise policy of setting labels to match the mount point; thus two Red Hat installations on the same machine would produce label collisions.) The appropriate policy for use of labels is to permit them to be used when requested by the system administrator, but not to use them by default. I posted an analysis of all the generic available methods for filesystem identification to debian-boot a while back: http://lists.debian.org/debian-boot/2008/12/msg00338.html -- Colin Watson [cjwat...@ubuntu.com] ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Lead-up message 'Welcome to GRUB!' inverted text printed lowlevel via BIOS ?!?
On Sun, Feb 21, 2010 at 11:00:57AM +0100, Robo L wrote: > As a second I would like to understand how it works with the printing, > because I spent much time reversed analysis and still I can not understand > who, where and when print the first inverted message "Welcome to GRUB!". grep should have found it ... it's in kern/main.c, in the grub_main function. > btw: for test I remove all Welcome message from binary (search for full > disk, MBR too) files and message is still printing :-) This is free software. Rebuild the source, don't edit the binary :-) -- Colin Watson [cjwat...@ubuntu.com] ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: [patch] search for partition using GPT GUID
2010/2/20 Vladimir 'φ-coder/phcoder' Serbinenko : > gbura...@gmail.com wrote: >> What about this patch? It is possible to integrate it, at least in the >> experimental branch? >> >> > I asked you for at least a usecase when it makes a difference but till > now I've read only about theoretical advantages. It has been explained that using the NTFS UUID is about equivalent of using the volume label. If it is sufficient why are we using UUIDs at all? We can use the much more readable labels everywhere and get rid of those long and impractical UUIDs completely. Thanks Michal ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: [RFC,resend] framebuffer rotation patch
2010/2/20 Vladimir 'φ-coder/phcoder' Serbinenko : > Michal Suchanek wrote: >> Hello, >> >> this is a framebuffer rotation patch rebased on top of current trunk. >> Between the trunk commits and the actual rotation there are a few >> fixes from my local branch most of which can be separated but the >> scroll fix conflicts with the rotation patch. >> >> This works for me (including terminal scrolling) in qemu and I >> compile-tested earlier version for efi as well. Only videotest and >> gfxterm was tested. >> >> Most of the suggestions I got in the previous discussion are >> incorporated in the new patch. >> > You have included some unrelated changes in your patch like useless > grub-mkrescue.in change. Yes, they are included as separate changesets, though. > What is the reason for get_max_viewport function? Why not just transform > mode_info? Because get_max_viewport is a user function. Transforming mode_info in every code using framebuffer would be error-prone, the users of the fb code should not need to invoke the transform functions. In the current users of get_max_viewport you can get away with get_veiwport (and throwing away the first two values) because all such uses happen just after graphics mode initialization and the current viewport is the maximum one. This might not be always the case in the future, though. Thanks Michal ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Lead-up message 'Welcome to GRUB!' inverted text printed lowlevel via BIOS ?!?
Hi all, Firstly I would like to thank everyone for the reply and Your time. I would like to clarify the issue. First I need to hide the very first Welcom message because I need to hide GRUB for other users of MS Windows on my PC. I need it only for myself. Richard: redirection is not good idea for me, becouse II need classical console. I wrote a module with hidden password (secret process - no response on console - silent) If match then redirect to boot linux. The nature of the process is that another user on my PC not venture a guess that there is a GRUB and secound linux OS! As a second I would like to understand how it works with the printing, because I spent much time reversed analysis and still I can not understand who, where and when print the first inverted message "Welcome to GRUB!". Who, where and how much bothers me more than the original problem. btw: for test I remove all Welcome message from binary (search for full disk, MBR too) files and message is still printing :-) Robo -- - E=mc2 ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
