From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] cdrom access patch
Date: Fri, 14 Mar 2008 13:28:03 -0400 [thread overview]
Message-ID: <1205515683.2321.18.camel@dv> (raw)
In-Reply-To: <ca0f59980803132233l5d9f6b8em96e911bd7bca67b3@mail.gmail.com>
On Fri, 2008-03-14 at 13:33 +0800, Bean wrote:
> thanks a lot for your testing. if nobody objects, i would like to
> commit it soon.
It would be great if you posted the ChangeLog entry and explained the
reason for the patch. I checked the thread, but I don't see it.
Is it just going to affect access to the CD in the "no emulation" mode?
Or maybe you are trying to make CD-ROM accessible if booting from the
hard drive or another medium?
What is the problem you are trying to solve? And what's wrong with the
(cd0) name? I think it's more descriptive, and I don't care much if
some other device like LS-120 is going to get such name.
As for passing the boot driver data to multiboot kernels, I don't think
it's useful to pass data about emulated drives. Besides, it should be
easy to keep the BIOS number in memory for every drive, even if it's
called (cd0).
Compare how Linux is changing from naming CD-ROMs by the bus location
(/dev/hdc, /dev/hdd) to naming by functionality with sequential numbers
(/dev/scd0, /dev/scd1). Things like bus location should be transparent
to the user.
Better yet, all partitions should be identified by a unique ID, which is
what serious distros should be doing. Still, (cd0) is more reliable and
descriptive than (hd96) for casual use.
Please note that I'm not objecting against the patch, I'm just asking
for a better explanation to understand what the patch does and why.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-03-14 17:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 8:49 [PATCH] cdrom access patch Bean
2008-03-07 15:37 ` Vesa Jääskeläinen
2008-03-09 15:33 ` Bean
2008-03-10 15:53 ` Bean
2008-03-11 21:10 ` Christian Franke
2008-03-12 5:26 ` Bean
2008-03-12 6:52 ` Christian Franke
2008-03-13 22:59 ` Christian Franke
2008-03-14 5:33 ` Bean
2008-03-14 17:28 ` Pavel Roskin [this message]
2008-03-14 19:58 ` Bean
2008-03-14 20:56 ` Bean
2008-03-14 20:58 ` Vesa Jääskeläinen
2008-03-15 7:34 ` Bean
2008-03-15 8:49 ` Vesa Jääskeläinen
2008-03-15 10:54 ` Bean
2008-03-15 19:01 ` Christian Franke
2008-03-17 4:31 ` Pavel Roskin
2008-03-17 6:21 ` Bean
2008-03-19 22:09 ` Pavel Roskin
2008-03-20 6:06 ` Bean
2008-03-24 4:15 ` Bean
2008-03-14 23:20 ` Christian Franke
-- strict thread matches above, loose matches on Subject: below --
2008-03-06 23:58 Kalamatee
2008-03-08 20:16 Kalamatee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1205515683.2321.18.camel@dv \
--to=proski@gnu.org \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.