RE: spam in commit-grub

2008-01-02 Thread Gregg C Levine
Hello! Who's the list-admin for commit-grub? I am thinking I can take that cover for a few weeks and see what happens. And what about resetting the list so that it requires a moderator to accept all posts, that way if something that is really junk does materialize we can throw it out. -- Gregg C L

Re: Conditional Statement in Grub 2

2008-01-02 Thread Gregg Levine
On Jan 2, 2008 8:11 PM, Antonio Dupont <[EMAIL PROTECTED]> wrote: > > > Hello, > > I apologize if this is the wrong list, but this is the list I have found > through my searches. Please tell me where to go if this is not the proper > place. > > I would like to have grub do a conditional statement

[PATCH] grub-probe && FreeBSD

2008-01-02 Thread Francis Gendreau
I finished to make grub-probe functionnal on FreeBSD system. I also added a few useful command-line options on the utility. 1) grub-probe support multiple output formats and targets. Optionnal patch. (util_grub-probe.c.diff) 2) Added support for resolution of mounted filesystem device.

Re: spam in commit-grub

2008-01-02 Thread Robert Millan
On Thu, Jan 03, 2008 at 01:55:37AM +0100, Robert Millan wrote: > I wouldn't like to run the risk of missing legitimate mail, specially in this > case that blocking spam is just a matter of restricting who can post to > commit-grub (like it happens on this list, which thankfuly is completely > spam-

Conditional Statement in Grub 2

2008-01-02 Thread Antonio Dupont
Hello, I apologize if this is the wrong list, but this is the list I have found through my searches. Please tell me where to go if this is not the proper place. I would like to have grub do a conditional statement similar to this: if file_name on /dev/cdrom matches file_name on /dev/sda1 (US

Re: [PATCH] memtest86+ fix

2008-01-02 Thread Robert Millan
On Thu, Jan 03, 2008 at 12:46:15AM +0100, Yoshinori K. Okuji wrote: > On Wednesday 02 January 2008 18:05, Robert Millan wrote: > > This fixes boot for memtest86+ (and actually, Linux zImages since they were > > all affected). > > > > The problem was that the first code in grub_linux_boot_zimage cop

Re: [PATCH] allow user-configurable menucolor

2008-01-02 Thread Robert Millan
On Thu, Jan 03, 2008 at 12:42:01AM +0100, Yoshinori K. Okuji wrote: > On Tuesday 01 January 2008 13:47, Robert Millan wrote: > > This patch allows the following to work: > > > > set color_normal=cyan/blue > > set color_highlight=white/blue > > Although I am not a native speaker, I feel that th

Re: [PATCH] allow user-configurable menucolor

2008-01-02 Thread Robert Millan
On Thu, Jan 03, 2008 at 12:55:48AM +0100, Yoshinori K. Okuji wrote: > On Wednesday 02 January 2008 22:48, Robert Millan wrote: > > On Tue, Jan 01, 2008 at 06:38:06PM +0100, Robert Millan wrote: > > > `color' command is necessary to propagate user setting from environment > > > variables to the inte

Re: spam in commit-grub

2008-01-02 Thread Robert Millan
On Thu, Jan 03, 2008 at 12:20:59AM +0100, Yoshinori K. Okuji wrote: > On Monday 31 December 2007 15:26, Robert Millan wrote: > > There's spam in commit-grub. Could posting be restricted to mail > > originating from Savannah ? The envelope sender seems to always be > > of the form [EMAIL PROTECTED

Re: [PATCH] allow user-configurable menucolor

2008-01-02 Thread Yoshinori K. Okuji
On Wednesday 02 January 2008 22:48, Robert Millan wrote: > On Tue, Jan 01, 2008 at 06:38:06PM +0100, Robert Millan wrote: > > `color' command is necessary to propagate user setting from environment > > variables to the internal color of our current terminal. > > Vesa suggested (on IRC) to use write

Re: [PATCH] memtest86+ fix

2008-01-02 Thread Yoshinori K. Okuji
On Wednesday 02 January 2008 18:05, Robert Millan wrote: > This fixes boot for memtest86+ (and actually, Linux zImages since they were > all affected). > > The problem was that the first code in grub_linux_boot_zimage copied the > payload from 0x10 to 0x1. Since GRUB starts at 0x8200 and

Re: [PATCH] allow user-configurable menucolor

2008-01-02 Thread Yoshinori K. Okuji
On Tuesday 01 January 2008 13:47, Robert Millan wrote: > This patch allows the following to work: > > set color_normal=cyan/blue > set color_highlight=white/blue Although I am not a native speaker, I feel that they should be better called "normal_color" and "highlight_color". > which is equi

Re: spam in commit-grub

2008-01-02 Thread Yoshinori K. Okuji
On Monday 31 December 2007 15:26, Robert Millan wrote: > There's spam in commit-grub. Could posting be restricted to mail > originating from Savannah ? The envelope sender seems to always be > of the form [EMAIL PROTECTED] Which spam? I can't figure out what mail you meant. Maybe because I have

Re: Transparent decompression with file system filter

2008-01-02 Thread Yoshinori K. Okuji
On Monday 31 December 2007 17:59, Bean wrote: > Hi, > > Changes in this new patch: > > 1, change function name grub_file_open_raw to grub_file_ropen > 2, replace grub_file_open in command/blocklist.c and > util/i386/pc/grub-setup.c to grub_file_ropen. > > If nobody objects, i would like to commit t

Re: [non-finalised patch] reiserfs handling

2008-01-02 Thread Robert Millan
On Tue, Dec 25, 2007 at 12:51:35PM +0100, Yoshinori K. Okuji wrote: > On Sunday 14 October 2007 15:56, Vincent Pelletier wrote: > > Attached is my work on reiserfs handling. > > Has anybody tried his patch? If you have reiserfs, please test it and let me > know the result. I am willing to clean u

Re: [PATCH] allow user-configurable menucolor

2008-01-02 Thread Robert Millan
On Tue, Jan 01, 2008 at 06:38:06PM +0100, Robert Millan wrote: > > `color' command is necessary to propagate user setting from environment > variables to the internal color of our current terminal. Vesa suggested (on IRC) to use write hooks (grub_env_write_hook_t) in variables to avoid this. I t

Re: embedding filesystems in core image (Re: moving ata initialisation to a command)

2008-01-02 Thread Robert Millan
Hi, Marco, do you have any comments on this patch? You said you didn't like this approach, but it looks good to me, and to others as well. After having a look, do you still have any objection ? On Fri, Dec 21, 2007 at 09:54:31PM +0100, Robert Millan wrote: > diff -x '*.mk' -Nurp grub2/conf/i3

Re: embedding data in ELF (Re: moving ata initialisation to a command)

2008-01-02 Thread Pavel Roskin
On Wed, 2007-12-26 at 09:00 +0100, Robert Millan wrote: > On Thu, Dec 20, 2007 at 06:36:07PM +0100, Robert Millan wrote: > > > > I'd prefer to support embedding filesystems in core.img instead. This > > solves the problem for every situation instead of just PC boot media > > (e.g. LinuxBIOS ELF p

grub-fstest: debug tool for filesystem driver

2008-01-02 Thread Bean
Hi, I've written a new tool grub-fstest which can be useful in debuging filesystem drivers. To build grub-fstest, you must use option --enable-grub-fstest: ./configure --enable-grub-fstest Usage: fstest [OPTIONS] IMAGE_PATH COMMANDS IMAGE_PATH is the absolute path to an image file, COMMANDS is

[PATCH] memtest86+ fix

2008-01-02 Thread Robert Millan
This fixes boot for memtest86+ (and actually, Linux zImages since they were all affected). The problem was that the first code in grub_linux_boot_zimage copied the payload from 0x10 to 0x1. Since GRUB starts at 0x8200 and is typicaly more than 8 kiB in size, it'll most likely overwrite

Re: Testing on PowerMac G4

2008-01-02 Thread Robert Millan
On Wed, Jan 02, 2008 at 01:46:04AM -0500, Pavel Roskin wrote: > Quoting Robert Millan <[EMAIL PROTECTED]>: > > >>My guess is kernel.elf doesn't include the necessary code. It's about > >>60k long. > > Now I'm sure about that. Unfortunately, grub-mkimage produces images > that the OpenFirmware

Re: package for distribution

2008-01-02 Thread Robert Millan
Hi, On Wed, Jan 02, 2008 at 12:22:18AM -0500, Pavel Roskin wrote: > Hello! > > Quoting shirish <[EMAIL PROTECTED]>: > > > Hi all, > > I have been trying to see when GRUB2 is packaged so I could try > >it, use it & understand all or any differences. I am running Ubuntu > >Hardy Heron (unsta

Re: Treating .old Linux kernels

2008-01-02 Thread Pavel Roskin
Quoting Robert Millan <[EMAIL PROTECTED]>: I don't have a strong opinion on this, but I'd opt for trying harder. Skipping .old breaks compatibility with existing update-grub that is provided with Debian (and derivatives) for GRUB Legacy, which means there's a big userbase that has come to ex