Robin
Many thanks, skidoo for counterchecking the findings. I’ll give feedback to your comments as soon as possible.
Let me state for clarification:
All findings described above on this system are “as delivered” by antiX 19.3 full ISO, updated and upgraded using apt update and upgrade for all upgradable packages, with one exception: xserver-xorg-core, which is pinned to version xorg version 19 from (instead of 20 which was standard in antiX 19.3.) So some findings may not be representative for other users (who are not in need to use prorietary nvidia stuff) at all. Then this is a “live persistent all” system tentatively used until replacing hdd installl of 17.4.1 by 19.3 once it has proven to function as rock stable and doesn’t slow down system, which can always happen when switching to a next generation of an operating system.
It’s not a problem for me to fix most of the findings individually on this very notebook, but this list was meant to give an impression what a new user faces when using the standard tools antix features for all the tasks.
2)…
you will probably need to provide a verbose, step-by-step, “what I clicked, what I typed” walkthrough.
I’ll do that as soon as possible (need to free an USB stick before, you simply won’t never have enough of them at hand 🙂 and make some additional screenshots.
3)…
I didn’t use the command line options at all, since script complained about something missing in the arguments, couldn’d figure out what, even if ‘man’ claims you can mix the two methods. Will have to look deeper into the options of this script some day. For now I just wanted to use it to get a fresh fallback copy of the stick in case the recent kernel upgrade would fail. Could have done this using dd as well. But I decided to follow the path a new antiX user would probably take also.
from man:
or you can let a series of menus guide you
which I did. I’ll provide a step by step description what exactly I did and when and where for this also.
5)…
have to append that this happens only on actually “power down”. While on “reboot” the file system on Live USB stick seems to get unmounted properly (at least for some times now, I’ll observe this and report again). So maybe a short delay, added just before actually last power down command in this tool would fix this already? Seems the stick encounters an energy shortfall before it has a chance to get everything settled?
6)…
since I’m quite familiar with mounting and unmounting any kind of whatever using simply the standard mount command in terminal, this is not the point. This tool is meant to make this everyday routine task handy and efficient. For this it has to function correctly, then it is a nice shortcut. When working on a pc (other than programming) you usually won’t want to rummaging in the engine room just for plugging off an USB stick. So this tool has its clear right to exist. But it has to safely function under any conceivable circumstances. And you probably wouldn’t expect you’d need to chase for each popup window of a tool in another place on your screen. For sure, I absolutely agree people need to learn to do things manually, but given that somebody does know this already, he can use a tool for everyday usage. Most people prefer to use a pocket calculator instead of dividing four or five digit numbers with a pencil on a sheet of paper, even if they need to know how this works manually, before they start using this handy tool.
Since “unplugdrive” tool is a bash script I’ve looked into before already, I’ll take care of this myself and present the resulting modifications here on board before trying to upload them to git repo. Maybe they will meet the needs to get merged into antiX in order to fix all this.
The mentioned double mount happens right after first boot of a fresh Live-USB install from “full” ISO, without having touched any settings. So the default settings in antiX are probably the culprit. I immediately stopped this spook, but I still state: If the tool does claim it was safe to plug off your stick, this has to be true, irrespective how or who has mounted some additional partitions of it elsewhere before. No long palaver here, I can fix this bug easily in the script, making it safe.
7)…
Are any of the previously pre-installed ClawsMail plugins now absent?
Nope.
For comparison:
$ grep laws /usr/share/antiX/installed-packages.txt | cut -d ' ' -f 1
claws-mail
claws-mail-i18n
claws-mail-pdf-viewer:i386
claws-mail-pgpinline:i386
claws-mail-pgpmime:i386
claws-mail-tools
Only difference to antiX 17 was the imagemagick tool was removed from the preinstalled programs in the full antiX 19.3 ISO, but clawsmail does obviously expect it to be present.
8)…
remove the bootline parameters “quiet” and “splasht”
well, this was exactly how I fixed this indeed. (I’ve set it to “quiet” and “splash=v”, moreover added “mount=all” before saving all this with f8 option.) Wanted just to make aware of the strange behaviour of this affectionate clingy splash screen new users will face here when expecting simply to see the boot process instead after once having decided this question by pressing the offered key.
- This reply was modified 5 years, 5 months ago by Robin.
- This reply was modified 5 years, 5 months ago by Robin.
- This reply was modified 5 years, 5 months ago by Robin.
Windows is like a submarine. Open a window and serious problems will start.