WetGeek Today, the first time I issued the mount -a command after modifying /etc/fstab, the mount points were apparently created automatically, because there were no errors listing the mount points that needed to be created.
This just gets weirder and weirder. Yesterday I installed siduction on a Latitude laptop, and when I got around to modifying /etc/fstab that time, the missing mount points were not created automatically. It was the same as always ... the first mount -a generated a list of the mount points that needed to be created. Then using that as a reminder, I created them with mkdir commands.
I suspect that they were not created automatically on the VM, either, but I was positive I hadn't done it manually. I have no idea what could have happened.
The nala/dpkg problem occurred when i installed siduction on the laptop and updated it. I registered on forum.siduction.org and left a bug report with a screen capture to show how it looked. I chatted with an admin there who said he'd seen the same thing happen twice during testing, but couldn't reproduce it afterwards. Today he filed an official bug report in their system.
For me, it happens only during an update/upgrade, and not when doing that with apt. When just installing software I needed today using nala, dpkg worked fine. The siduction admin, called "Devil," didn't mention what he was doing when he saw the error happen twice.
My opinion of siduction hasn't changed at all after installing it on hardware. I spent some more time with it today, finishing its configuration (calendars in Thunderbird, tab stacks in Vivaldi, etc.), such that it's now an exact match for my main laptop. Or as close to that as possible for a machine that's running a different distro and newer software versions. On hardware, siduction is a joy to use. It would make an excellent #2 distro for anyone interested in such a thing. It's so much like using Solus it's scary.
