Hi
I am sending a mail to access to the list.
I cant make head of tails to the new V2.0 beta0 code. Its very broken,
compiles and runs well. Cant see why it mkconfig makes a grub.cfg.new
and no grub.cfg
Want to get involved in the code and thought rather than we going
through file after file i
Please tell me how to take part in development of grub2.
Thanks!
___
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
On 27.02.2012 09:29, Tu.Jianfeng wrote:
Please tell me how to take part in development of grub2.
lists.gnu.org/mailman/listinfo/grub-devel
Start with reading source and developper manual.
What are your areas of interest?
Thanks!
___
Grub-devel maili
On 01.03.2012 08:37, Chris C wrote:
Hi
I am sending a mail to access to the list.
Subscription is here: lists.gnu.org/mailman/listinfo/grub-devel
I cant make head of tails to the new V2.0 beta0 code. Its very broken,
Just "very broken" is utterly unconstructive. You need to be more
specific
I tried to find all relevant docs and read what I've found (e.g.
grub-dev.texi), so please excuse me if this questions has been already
answered somewhere.
I would like to change and submit code for GRUB and from what i see
right now indentation of the code doesn't seem to follow any rules. Most
o
On 01.03.2012 13:09, Andreas Vogel wrote:
I tried to find all relevant docs and read what I've found (e.g.
grub-dev.texi), so please excuse me if this questions has been already
answered somewhere.
I would like to change and submit code for GRUB and from what i see
right now indentation of the c
Thanks for clarification and the pointer to GCS.
Just for reference: the appropriate indentation setting for VIM is
set tabstop=8 softtabstop=2 shiftwidth=2 noexpandtab
so that indentation is 2 spaces and each bunch of 8 spaces will be
converted into a TAB char.
Andreas
Am 01.03.2012 13:
The attached patch fixes the following warnings when building GRUB on
NetBSD (and probably other BSDs):
util/getroot.c: In function 'grub_make_system_path_relative_to_its_root':
util/getroot.c:2711:2: error: label 'parsedir' defined but not used
util/getroot.c: At top level:
util/getroot.c:1084:1
On Tue, Feb 28, 2012 at 11:39:32AM -0500, Lennart Sorensen wrote:
> I should do another powerpc build of trunk to make sure we got all the
> warnings now.
gcc-4.4 -DHAVE_CONFIG_H -I. -I../../../grub-core -I.. -Wall -W
-I../../../include -I../include -DGRUB_MACHINE_EMU=1
-DGRUB_MACHINE=POWERPC_
On Thu, Mar 01, 2012 at 01:37:10PM -0500, Lennart Sorensen wrote:
> gcc-4.4 -DHAVE_CONFIG_H -I. -I../../../grub-core -I.. -Wall -W
> -I../../../include -I../include -DGRUB_MACHINE_EMU=1
> -DGRUB_MACHINE=POWERPC_EMU -DGRUB_TARGET_CPU_POWERPC=1 -m32
> -DGRUB_FILE=\"normal/charset.c\" -I. -I../..
On Thu, Mar 01, 2012 at 02:15:17PM -0500, Lennart Sorensen wrote:
> Would using this instead work:
>
> for (i = k - 1; i >= 0 && (unsigned) i > line_start - 1;
>
> After all if i already had to be >=0 then casting it to unsigned has no
> harm, whereas casting line_start to signed could potentiall
root@rceng03new:~# /usr/sbin/grub-probe --device /dev/md1 --target=partmap
/usr/sbin/grub-probe: error: disk `mduuid/dc00bd3a0e9491bb0b66fa8b9246c2e8' not
found.
That seems wrong.
So does:
root@rceng03new:~# /usr/sbin/grub-probe --device /dev/md0 --target=partmap
/usr/sbin/grub-probe: error: Co
On Thu, Mar 01, 2012 at 02:47:58PM -0500, Lennart Sorensen wrote:
> root@rceng03new:~# /usr/sbin/grub-probe --device /dev/md1 --target=partmap
> /usr/sbin/grub-probe: error: disk `mduuid/dc00bd3a0e9491bb0b66fa8b9246c2e8'
> not found.
>
> That seems wrong.
>
> So does:
>
> root@rceng03new:~# /us
On 01.03.2012 20:47, Lennart Sorensen wrote:
root@rceng03new:~# /usr/sbin/grub-probe --device /dev/md1 --target=partmap
/usr/sbin/grub-probe: error: disk `mduuid/dc00bd3a0e9491bb0b66fa8b9246c2e8' not
found.
Is the uuid correct?
That seems wrong.
So does:
root@rceng03new:~# /usr/sbin/grub-pro
On Thu, Mar 01, 2012 at 09:07:34PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
> On 01.03.2012 20:47, Lennart Sorensen wrote:
> >root@rceng03new:~# /usr/sbin/grub-probe --device /dev/md1 --target=partmap
> >/usr/sbin/grub-probe: error: disk `mduuid/dc00bd3a0e9491bb0b66fa8b9246c2e8'
> >not
On Thu, Mar 01, 2012 at 03:15:52PM -0500, Lennart Sorensen wrote:
> Should grub-probe be suggesting checking your device.map if it doesn't
> exist and doesn't need it? That's confusing.
If I use grub-probe from grub 1.99 I get:
root@rceng03new:~/grub2-1.99# ./build/grub-ieee1275/grub-probe --tar
16 matches
Mail list logo