SCIENTIFIC-LINUX-USERS Archives

February 2013

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Thu, 21 Feb 2013 14:41:19 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
On 2013/02/21 04:26, Tom H wrote:
> On Wed, Feb 20, 2013 at 8:57 AM, Pat Riehecky <[log in to unmask]> 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

{^_^}

ATOM RSS1 RSS2