From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: grub-setup inflexibility
Date: Thu, 16 Sep 2010 01:00:04 +0200 [thread overview]
Message-ID: <4C914FF4.1050500@gmail.com> (raw)
In-Reply-To: <cone.1284576904.92667.30634.1000@toolshiner.phx1.kidfixit.com>
[-- Attachment #1: Type: text/plain, Size: 2506 bytes --]
On 09/15/2010 08:55 PM, Joey Korkames wrote:
> Colin Watson writes:
>
>> On Xen (I'm told), it's possible to assign disk images in the host to
>> things that are named rather like partitions in the guest (e.g.
>> /dev/sda1), but that don't have an associated disk (e.g. /dev/sda);
>> indeed, the latter device is nonexistent. This confuses
>> grub_util_biosdisk_get_grub_dev.
>>
>> There's really no other situation in which I think it's terribly
>> plausible that you might have /dev/sda1 but not /dev/sda, so it seems to
>> me that in this case we can reasonably treat the apparent "partition" as
>> a disk in its own right.
>>
>
> Can we make some of these 'decisions' switchable on the command line?
> I perform a lot of block device redirections (Xen, iSCSI, nbd, etc) or
> work from live cd's (where / is merely rootfs+unionfs with no disk,
> but /boot is a mounted disk), and grub-setup raises fatal objections
> that I would like to override when _I_ know what devnodes the
> bootblocks and the filesystems belong on.
>
It looks like you confused grub-setup (called from grub-install) with
grub-mkconfig (called from update-grub). Former accesses only to
/boot/grub and it needs to know about /boot/grub in order to configure
image correctly.
grub-mkconfig on the other hand probes for root but you don't have to
use it. If you prefer the old way of doing things you can simply remove
grub-mkconfig and write grub.cfg yourself.
> Some of this probe logic is starting to delve into sysadmin logic,
> which can be terribly obtuse and site-specific. I really don't think
> the install code should be _solely_ implemented in compiled languages
> - it should be possible to install grub2 boot blocks in
> alternative/scriptable ways like it was with grub1 (dd
> if=/boot/grub/stage1 of=/dev/foo bs=446 count=1 conv=notrunc).
> That also lets you install pre-assembled grub cores from
> non-grub2-supported platforms, which is useful for no-physical-access
> OS conversion.
>
> This is somewhat like the "where is stage1" complaints the list has
> been getting, but I'd like to see this minor inflexibility resolved in
> the awesome grub2 framework vs. just asking to keep bugfixing ancient
> grub1.
>
> thanks for reading
> -joey
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2010-09-15 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 17:33 [PATCH] Handle partition devices without corresponding disk devices Colin Watson
2010-09-15 18:55 ` grub-setup inflexibility Joey Korkames
2010-09-15 23:00 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-09-16 2:02 ` Joey Korkames
2010-09-16 7:40 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-11-18 2:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4C914FF4.1050500@gmail.com \
--to=phcoder@gmail.com \
--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.