From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Support for search by disk id module
Date: Sat, 15 Apr 2017 14:18:48 +0300 [thread overview]
Message-ID: <579d86e5-328b-d6a4-be82-7a85d07c408d@gmail.com> (raw)
In-Reply-To: <7x2E7Enw9wkilxMD6FwVNb3TiLsX1pyyVtpr1RneBvfyNYokTJDktwHaa-8emGHsIkpLA2XsTxayMG5w05TDui1cY3TjQhc9os-_4kNbqc0=@protonmail.com>
15.04.2017 13:55, Mat628 пишет:
> Hi,
>
> I wanted to verify/clarify what would be an acceptable format for a disk id to be used as a search parameter for a module to return the associated device.
>
> Where on Linux, devices are mapped to a hardware specific path.
> For hard disks it is
>
> type-product_serial(-partition#)
>
There is no established standard and this changed over time. GRUB uses
platform firmware to access devices, so it can only use information
firmware exports. In general we have no way to query for this information.
> ata-ST42443343DR_6GE23Y09
> ata-ST42443343DR_6GE23Y09-part1
>
> But for a USB flash drive it is
>
> type-vendor_product_serial-(?physical id?)-(part#)
>
> usb-SanDisk_Ultra_4E53324345657878876543-0:0-part1
>
> where product = model name
>
> Would it be okay to shorten this for USB flash drive to
>
> type-product_serial-(part#) ?
>
> usb-Ultra_4E53324345657878876543-part1
>
> To help keep it to a minimal amount of characters the user would have to type. While ensuring the shortened version would not impact its reliability to return the correct device. Even the 'type' could be removed if that is okay with you?
>
> Best regards,
>
> Matt
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
next prev parent reply other threads:[~2017-04-15 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 10:55 Support for search by disk id module Mat628
2017-04-15 11:18 ` Andrei Borzenkov [this message]
2017-04-15 11:27 ` Mat628
2017-04-15 11:32 ` Vladimir 'phcoder' Serbinenko
2017-04-15 11:54 ` Mat628
2017-04-15 11:38 ` Andrei Borzenkov
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=579d86e5-328b-d6a4-be82-7a85d07c408d@gmail.com \
--to=arvidjaar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).