I'm posting in the MX modified because I upgraded my boys modified MX-14, to MX-16 I using a snapshot made earlier today with all updates etc installed, plus a handful of tools to assist his schooling. Being lazy, I chose not to back up data and reformat his 64GB SSD, instead I moved a few folders containing his school work to another location in /home, deleted the remainder of his user account and performed the install instructing it to keep /home, so the drive retained its original formatting
My surprise came when I enabled on the firewall on the new install and tried to set exclusions for samba, GUFW failed to make any rules and reported the error listed above, so I proceeded to check with ls -ld / and sure enough, it was exactly as the message said
Code: Select all
$ ls -ld / drwxrwxrwx 19 root root
I rebooted his NUC with my Live-USB, mounted his / partition and its name was listed under media/ using the partitions UUID, so I was able to check and sure enough, it was drwxrwxrwx when mounted. I chmodded the device listed with the UUID to drwxr-xr-x, rebooted normally and low and behold, the rules I tried unsuccessfully to add to GUFW were in place and working, Re-checking with ls -ld / confirmed the permissions were set right.
I don't believe this is a normal scenario, though this does beg the question, should our installer check the drives permissions and correct them if they are found to be in error during install when a choice is made to retain /home ????? Thoughts anyone?
Quirk #2 was discovered after I installed a different snapshot created yesterday to another machine and set the user to log in automatically. Upon first boot, instead of arriving at a desktop, I was left with a blank screen. I switched to VT1 and issued the reboot command, only to be met at next boot by the same thing. This time, I used Crtl + Alt + Esc to kill X and was presented with a login screen containing the login username from the machine I used to create the snapshot.
To me, this one begs a little more digging because I think I may have stumbled upon a bug and I wonder if others can reproduce it.
The process is simple, make a general snapshot, then boot and install said snapshot to a VM or another machine. Ensure you use a different user name to that which was used when creating the snapshot and set the user to autologin. Secondly, make sure you do not select the option to copy over live desktop changes. If, like me, you're faced with a black screen and not much else, kill X with the 3 finger salute and see if you're presented with the username from the originating machine.