Hello. I'm back after long time of inactivity. I would like to expose my
idea:
Many of commercial OS have some weird conditions on where they are
installed (e.g. it must be installed on primary active partiotion, ...)
and what we can do is
1st possibility: function that transform primary<-> logi
So I have changed the partition numbering to 1-based. The strategy is that we
use 1-based only for the string representation of a device, while keeping
0-based internally. I think this is more intuitive for hacking. I assume that
I have modified all relevant parts, but I might have missed some p
On Mon, 2006-06-05 at 21:04 +0200, Yoshinori K. Okuji wrote:
> So I have changed the partition numbering to 1-based. The strategy is that we
> use 1-based only for the string representation of a device, while keeping
> 0-based internally. I think this is more intuitive for hacking. I assume that
Hi:I posted an issue loading the initrd file in a Xeon Platform, the problem was the following:>On Wednesday 31 May 2006 03:18, Jesús Velazquez wrote:>> We are trying to use Grub2 for booting RedHat Enterprise Linux 4 update 2
>> on Xeon Platforms. But, we found that the initrd file is not loaded
On Monday 05 June 2006 21:14, Hollis Blanchard wrote:
> On Mon, 2006-06-05 at 21:04 +0200, Yoshinori K. Okuji wrote:
> > So I have changed the partition numbering to 1-based. The strategy is
> > that we use 1-based only for the string representation of a device, while
> > keeping 0-based internally
On Monday 05 June 2006 21:44, Jesús Velazquez wrote:
> In the function grub_rescue_cmd_initrd (at file loader/i386/pc/linux.c),
> the following lines of code (lines 335-336)
>
> if (!linux_mem_size && linux_mem_size < addr_max)
> addr_max = linux_mem_size;
>
> Setup the addr_max to linux_mem_s
