| 1 |
On 2020-03-19 00:12, Ian Zimmerman wrote: |
| 2 |
> On 2020-03-18 22:57, n952162 wrote: |
| 3 |
> |
| 4 |
>> Well, some new recognitions ... |
| 5 |
>> |
| 6 |
>> It turns out that those /dev/disk subdirectories don't necessarily have |
| 7 |
>> all the disk devices represented: |
| 8 |
>> |
| 9 |
>> 1. by-id/ |
| 10 |
>> 2. by-partuuid/ |
| 11 |
>> 3. by-path/ |
| 12 |
>> 4. by-uuid/ |
| 13 |
> There is also by-label, which you can reference from fstab like |
| 14 |
> |
| 15 |
> LABEL=foobar /home ext4 defaults ... |
| 16 |
> |
| 17 |
> If predictability and readability is the goal, I think using labels is |
| 18 |
> the best option, because you have complete control over them, unlike the |
| 19 |
> device IDs. For example: |
| 20 |
> |
| 21 |
> LABEL=my-machine-home-part /home ext4 defaults ... |
| 22 |
> |
| 23 |
> This doesn't solve your underlying timing problem, of course. Just apropos. |
| 24 |
> |
| 25 |
I had by-label/ in the back of my mind, thinking that was always |
| 26 |
available as a fall-back, but then forgot about it because it's /not |
| 27 |
there/! That list above I got with ls(1). |
| 28 |
|
| 29 |
I wonder if whatever process it is that builds /dev/disk (/udev/?) is |
| 30 |
getting aborted, because I can't imagine a reason that |
| 31 |
/dev/disk/by-uuid/* -> /dev/sda* shouldn't be there. |
Archives