All of lore.kernel.org
 help / color / mirror / Atom feed
From: adrian15 <adrian15@raulete.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Detection of boot devices by a linux kernel
Date: Fri, 15 Jun 2007 14:46:35 +0200	[thread overview]
Message-ID: <46728A2B.1080103@raulete.net> (raw)


	First question:
	=================
	
	Once a Kernel has booted can request the bios the different boot
devices and try to open them with a bios-disk driver or whatever the
name is?

	
	Current problems:
	====================	

	I do not know what's the live cd / non-live cd installer algorithm for
detecting which grub device corresponds to which linux device.
	There's a man in hardwareguys.com which gets some strange results. He
installing Linux in his 4th drive and as long as it is detected as
/dev/sdg then the linux assign it: hd6 . :)

http://forums.hardwareguys.com/ikonboard.cgi?act=ST;f=21;t=5731;&#top

	Probable solution:
	=====================
	If the answer for the first question is that NO here there is my
solution to problem.

	We should make a command that iterates all the hard disks boot devices
and looks for the uuid from the hard disks. Once it has done so it saves
the result into a variable.

	Then we can boot a kernel and pass this variable as a parametrer.

	Example:
	==========

	grub> set
	prefix=(cd)/boot/grub/
	root=(cd)
	grub> detectboot -s biosdevices
	grub> set
	root=(cd)
	biosdevices=hd0|ffkei|hd1|ereok|hd2|er455
	grub> linux /boot/knoppix-6.0-kernel root=/dev/ram grubdevices=$biosdevices
	grub> initrd /boot/knoppix-6.0-initrd
	grub> boot

	Then thanks to the "grubdevices=hd0|ffkei|hd1|ereok|hd2|er455" string
found in /proc/cmdline the knoppix boot scripts can check the uuid for
each detected hard disk and generate a valid devices.map file.

	Any comments on this?
	

	adrian15




                 reply	other threads:[~2007-06-15 13:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=46728A2B.1080103@raulete.net \
    --to=adrian15@raulete.net \
    --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.