symlink persist follow-up

[Grizzly]

Sunday, September 24, 2023  at 9:33, Ralf Mardorf via ubuntu-users wrote:
Re: symlink persist follow-up (at least in part)

>On Sat, 2023-09-23 at 23:24 +0100, Grizzly via ubuntu-users wrote:
>> fstab from Mantic 
>> UUID=c8264b8d-5caa-4515-b44b-a7c9c78f536a / ext4 errors=remount-ro,x-gvfs-show,x-gvfs-name=Jammy 0 1
>> fstab from Jammy
>> UUID=c8264b8d-5caa-4515-b44b-a7c9c78f536a / ext4 errors=remount-ro 0       1

>At least one entry for a root directory is wrong, since both are using
>the same UUID. It's probably the one for Mantic, since an gvfs option
>does name it Jammy.

>I'm not surprised that the correct root directory is mounted anyway,
>since the boot loader might point to the correct root directory and we 
>have systemd-fstab-generator and native systemd units that might mount
>devices that aren't listed in fstab.

>New to me is a fstab tainted with gvfs related options.

>I recommend as a first step to tidy up your install. IOW ensure that you
>either use systemd units only or fstab entries only and don't use
>anything else to mount.

Last time I went into fstab (from Mantic) I ended up not been able to boot, not 
been able to rebuild fstab from recovery console either, I had to boot Jammy 
then copy /etc/fstab edit (change UUID) it and paste to Mantic /etc/fstab 
(could be why they look close)

is there a "SAFE" way to (re)build / clean fstab ??

I have it working, drive is mounted, symlink is seen but wallpaper is still 
default Maze, until I change it manully, it doesn't stick past reboot though