Re: disk vs partition numbering
On Wednesday 13 December 2006 09:59, adrian15 wrote: > For them their first hard disk (Who is going to have a zero-hard disk in > the real world. It has no sense) is C:, but you could name it 1. > And when they partition their hard disk they suppose that the first cut > it is the 1 not the 0. And you could name it 0. This is in computing world... but if you go to a building you go to the ground floor or to the 1st floor but you not do go to the 0th floor! > About your arguments... mine are: Grub2 users are not unix OS or its > sysadmins but Windows ones. Grub2 should address to this kind of users > in my opinnion. Hmm... I don't agree that most users are Windows users. AFAIK, most Windows users stick to the default selector (ntldr), and does not try to see how GRUB works at all. When I talked about Windows users I was talking about Windows users that do not stick the Windows but the ones that migrates, and thus dual boot with Gnu/Linux. But you are comparing apples with oranges here. What Windows does is to count only partitions for hard disks and count only disk for floppy disks and CD/DVD drives. C: is not a disk. It is a partition that Windows can recognize as a primary partition. D: is a second partition, regardless of whether it is in the same disk as C: or in next disk, or in next next disk. So you cannot compare GRUB's scheme with Windows' simply. Yes. You're right. So.. please compare the building floors scheme (what everyone understands) with hard disks and partitions. Personally, I think it is really unfortunate that the way of Windows is of no use. Really no use. If Windows were not that crap, everybody else could follow the same way, and everybody would be quite happy. I am of the same opinnion. :) I suppose the MS-DOS original developer (that one that Bill bought the OS with little money) thought that letters were less scary for identifying devices. Okuji adrian15 ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: disk vs partition numbering
adrian15 <[EMAIL PROTECTED]> writes: >> On Wednesday 13 December 2006 09:59, adrian15 wrote: >>> > For them their first hard disk (Who is going to have a zero-hard disk in >>> > the real world. It has no sense) is C:, but you could name it 1. >>> > And when they partition their hard disk they suppose that the first cut >>> > it is the 1 not the 0. >> >> And you could name it 0. > > This is in computing world... but if you go to a building you go to > the ground floor or to the 1st floor but you not do go to the 0th > floor! Another thing about computing world is that not everything is logical, you don't have to deal with bits and bytes only, but also with people. Many operating systems start counting disks with 1. You could argue other operating systems do other things and you will be right. But a decision has to be taken, which is what Okuji did. [...] >> But you are comparing apples with oranges here. What Windows does is >> to count only partitions for hard disks and count only disk for >> floppy disks and CD/DVD drives. C: is not a disk. It is a partition >> that Windows can recognize as a primary partition. D: is a second >> partition, regardless of whether it is in the same disk as C: or in >> next disk, or in next next disk. So you cannot compare GRUB's scheme >> with Windows' simply. > > Yes. You're right. So.. please compare the building floors scheme > (what everyone understands) with hard disks and partitions. It has nothing to do with floors, but it does have something to do with counting. No one starts counting with 0. Except when you count partitions, of course. ;-) -- Marco ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Conditionally building `grub-emu'
Thomas Schwinge <[EMAIL PROTECTED]> writes: Hi Thomas, > On request / suggestion / whatever ;-) of Marco I created the following > patch. Thanks a lot for doing this! [...] > The only remaining problem --- which only happens if building without > having `grub-emu' enabled --- is the following one: [...] Is this fixed already by what Okuji proposed (and possibly committed)? -- Marco ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU
bibo,mao wrote:
>> menuentry "MacOSX" {
>> set root=(hd0,2)
>> chainloader /System/Library/CoreServices/boot.efi
>> }
>>
>> menuentry "GNU/Linux" {
>> set root=(hd0,5)
>> linux /boot/vmlinuz root=/dev/sda5
>> }
>>
> There is no initrd option in your menu, I do not know whether it can
> successfully boot up without initrd option with grub2. you can enter
> into rescue mode(command-line mode), and enter commands like this:
> $linux /boot/vmlinuz root=/dev/sda5
> $initrd /boot/xxx
> $boot
>
> And what is your linux kernel version?
2.6.18.5.
initrd is in my case in fact not needed; I compiled ata_piix and ext3
drivers, and everything inbetween directly into the kernel, so if
correctly loaded, it should be able to access /dev/sda5 and retrieve
/sbin/init from the hard disk; then everything else comes from there as
well.
Currently I am a little puzzled, as grub2 loads and executes MacOS-X
boot.efi correctly, but if trying linux, then linux stops somewhere.
As next, if burning the same kernel image as a bootable syslinux-CD,
linux gets loaded and executed as one would expect.
With the "nv" driver even X11 runs in full 1920x1200 resolution on
iMac-T7400 excellently (nvidia proprietary driver builds, starts and
runs without complaints, but shows "black pixels" only :-).
Maybe MacOS if booting from CD sets up some faked BIOS environment so
Linux and X11 are in believing it is usual IBM-PC-hardware, but if
booting with grub2 this is not the case and then linux fails?
Momentarily I am not convinced it is a grub2 issue.
Greetings,
Eeri Kask
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
Re: disk vs partition numbering
Marco Gerards wrote: with counting. No one starts counting with 0. Except when you count partitions, of course. ;-) what about arrays in C/C++ ? Damon Register ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: disk vs partition numbering
Dne 13 Prosinec 2006, 22:00, Yoshinori K. Okuji napsal(a): > On Wednesday 13 December 2006 09:14, James Lockie wrote: > >> I take that back, software should work without having to read the >> manual, grub legacy was NOT like that for me. > > Exactly. It is ideal that one can use software without reading a manual > appropriately. The reality is different, but we should make effort to get > closer to this goal. > >> Maybe grub should use the way of designating a disk/partition in the >> same way as what OS it is running on? Yes, being different for each OS. >> :-) >> > > Unfortunately, this would cause strange behaviors. For example, suppose > that you have installed GRUB into a floppy or CD-R. When you bring it to > another computer, how should GRUB behave? Mimic the operating system on > which GRUB was installed? Mimic the operating system the user is trying to > boot? If you have multiple operating systems installed, which one??? > > Okuji The only think grub may (should?) mimic is bios. IBM-PC compatible bios has no 'visible' numbering. I would choose 0-based, (subtracting 0x80 is better for me than 0x81), but I'm not a beginner. Another thing is, that we can add possibility to change naming scheme by some module. Then, at the beginning of config file will be something like 'renamedevices --linuxstyle', and then we can use (hda,1). -- Tomas Ebenlendr http://drak.ucw.cz/ebik ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: EFI-dualbooting OSX and Linux on iMac with T7400-CPU
Eeri Kask wrote:
bibo,mao wrote:
>> menuentry "MacOSX" {
>> set root=(hd0,2)
>> chainloader /System/Library/CoreServices/boot.efi
>> }
>>
>> menuentry "GNU/Linux" {
>> set root=(hd0,5)
>> linux /boot/vmlinuz root=/dev/sda5
>> }
>>
> There is no initrd option in your menu, I do not know whether it can
> successfully boot up without initrd option with grub2. you can enter
> into rescue mode(command-line mode), and enter commands like this:
> $linux /boot/vmlinuz root=/dev/sda5
> $initrd /boot/xxx
> $boot
>
> And what is your linux kernel version?
2.6.18.5.
There exists one bug in Linux kernel only EFI bios relative at
http://marc.theaimsgroup.com/?l=linux-kernel&m=116157536316034&w=2
I do not know whether 2.6.18.5 incorporates this bug.
initrd is in my case in fact not needed; I compiled ata_piix and ext3
drivers, and everything inbetween directly into the kernel, so if
correctly loaded, it should be able to access /dev/sda5 and retrieve
/sbin/init from the hard disk; then everything else comes from there as
well.
Currently I am a little puzzled, as grub2 loads and executes MacOS-X
boot.efi correctly, but if trying linux, then linux stops somewhere.
As next, if burning the same kernel image as a bootable syslinux-CD,
linux gets loaded and executed as one would expect.
With the "nv" driver even X11 runs in full 1920x1200 resolution on
iMac-T7400 excellently (nvidia proprietary driver builds, starts and
runs without complaints, but shows "black pixels" only :-).
Maybe MacOS if booting from CD sets up some faked BIOS environment so
Linux and X11 are in believing it is usual IBM-PC-hardware, but if
booting with grub2 this is not the case and then linux fails?
I am not familiar with Mac machine, In general there exists two types of
bios. One is EFI bios, the other is legacy pc bios. I doubt that
syslinux-CD boots from legacy pc bios but not EFI bios. You can enter
"dmesg" command to find memory map information to judge which bios kernel
boots from.
thanks
bibo, mao
Momentarily I am not convinced it is a grub2 issue.
Greetings,
Eeri Kask
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
