On 2013/02/21 04:26, Tom H wrote:
On Wed, Feb 20, 2013 at 8:57 AM, Pat Riehecky <[email protected]> wrote:
On 02/19/2013 10:14 AM, Graham Allan wrote:
On Mon, Feb 18, 2013 at 07:33:37PM -0700, Orion Poplawski wrote:
On 02/18/2013 02:01 PM, Ken Teh wrote:
During a kickstart install, how are drives mapped? I notice that sata0
is not always sda. This is especially true when there are very large
drives in the mix.
The sd* letters are simply handed out in order of enumeration and,
as you noted, is not deterministic. If you need that, use the
/dev/disk/by-{id,label,path,uuid} labels.
For this reason we use a script during the kickstart %pre section which
attempts to examine the available drives and determine which is the
appropriate one to install on (also waits for confirmation if an
unexpected partition table is found).
Any chance you can share that script? It sounds interesting!
You can use "list-hardrives" in "%pre" and parse its output.
If you want to see what its output looks like, you can install
anaconda - although the actual anaconda executable, IIRC, is
"list-hardrives-<something>".
# /usr/lib/anaconda/list-harddrives-stub
sda 476940.023438
sr0 64.361328125
{^_^}
