symlink persist follow-up

[Ralf Mardorf]

On Sat, 2023-09-23 at 07:24 +0100, Grizzly via ubuntu-users wrote:
> sometimes the Win7 disk is just not there (usually after a 
> few reboots)

What do you mean? The hardware is stolen from Bigfood and brought back
again and again? Even if Bigfood brought it back and reconnected it,
then it is not recognized or it is recognized but is not sdb1?

If the drive sometimes isn't recognized at all, then it might be that
hardware is broken. If the drive sometimes isn't sdb1 it means
absolutely nothing.

On some machines sda stays always sda and sdb stays always sdb and on
other machines it doesn't stay always the same, this is the reason for
me that on Thu, 2023-09-21 at 15:11 +0200 I mentioned:
>> Mount it by systemd or respectively by
>> /etc/fstab by UUID c8264b8d-5caa-4515-b44b-a7c9c78f536a
>> or by a label, don't use sdX.

> What "should" fstab for that drive look like?

On Thu, 2023-09-21 at 11:59 +0200, I provided an example:
>> LABEL=s3.a6400  /.a6400  ext4  defaults,noatime  0 2
   ^               ^        ^                       ^ ^            
   ^               ^        File system             ^ fsck order (0=no,1=for root,2=anything else)
   ^               Mount point                      always 0, since 1 is for an obsolete backup operation
   You can replace LABEL by UUID

The options should be "default" followed by changes to the default.
The defaults depend. If you don't know your system's defaults and/or
what options are available, then just add "default", don't add
"defaults,noatime". The options for root might be different, don't
change entries for root and swap, just add your entry.