On 16:36, Sun, 22 Dec 2019 <244clarendo...@gmail.com wrote:
>
>
>> The only remaining problem here might be that /dev/sda3 doesn't
>> reference the same drive on each dom0 boot process...
>>
>> So you'd have to write ... Alternatively you could ...
>
>
> Another option is to label the
> The only remaining problem here might be that /dev/sda3 doesn't
> reference the same drive on each dom0 boot process...
>
> So you'd have to write ... Alternatively you could ...
>
Another option is to label the filesystem, say with
tune2fs -L foo /dev/sda3
Then, instead of the
On 12/13/19 8:33 PM, billol...@gmail.com wrote:
No, it's been consistent for a few weeks now, so I'm not going to worry
about it. I did find another way to screw up, though. I attached the
drive persistently to my "untrusted" VM, and then put the mount in
/etc/fstab in the debian-10 template,
No, it's been consistent for a few weeks now, so I'm not going to worry
about it. I did find another way to screw up, though. I attached the
drive persistently to my "untrusted" VM, and then put the mount in
/etc/fstab in the debian-10 template, so it would persist also. That
worked fine
On 12/12/19 8:46 PM, billol...@gmail.com wrote:
Doh. I just noticed the "noauto" option. Sigh. Deleted it and it works
fine.
The only remaining problem here might be that /dev/sda3 doesn't
reference the same drive on each dom0 boot process...
So you'd have to write a udev rule for that.
