- This topic has 41 replies, 5 voices, and was last updated Oct 17-4:09 pm by boruch.
-
Posts
-
anticapitalista
Now, can you post inxi -v8 as requested.
When did you ever request that? Anyway, I’m not sure that I can right now, or whether it would do any good – that machine is now running another OS and will be busy for a few days acting as a temporary server for another project. Does it really matter? Do you have a specific question, or are you just asking in a shot-in-the-dark “checklist” way?
Forget it.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
caprea
Good news, tried another usb-stick and this worked perfectly.
Dont know why and what.
The non functional stick was made with live-usb-maker-gui on an installation with testing-repos.
The functional was also made with live-usb-maker-gui on stable repos.
Maybe its just the stick itself.
The OP didn’t mention how he made his live-usb.anticapitalista
Thanks for the feedback caprea.
If you still have the non-functioning one, here are some new installer debs.
Maybe these work. You need antix-installer and installer-data-antix debs.Probably also best to use the latest libcmd that dolphin linked to.
https://download.tuxfamily.org/antix/Testing/
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
boruch
The OP didn’t mention how he made his live-usb.
I used the command-line:
dd ... of=/dev/sdb ...- This reply was modified 4 years, 7 months ago by boruch.
caprea
Not sure what that was,some kind of a lot of smoke for nothing. The debs from above didn’t help.But to start over from scratch, creating the live-usb once again, helped.
Also with dd-command. Everything works now.
The errors must have been due to the way I created the stick.Confusingly, someone else had exactly the same errors.I just now tried a second install of antix 17.2, using the same usb stick (ie. I didn’t re-image anything) but on a different machine, and the install *DID* succeed.
So, my guess is my reported problems may have to do with some combination of clicks that both I and @caprea made when beginning the install.
One possible vector would be the pressing of the ‘cancel’ button on the installer’s first screen, which I reported did not actually cancel, but instead opened another window allowing one to continue the install or to really cancel.
A second possible vector would be the set of dialogs asking one to set the keyboard layout. Those dialogs had some navigation quirks, and repeated themselves, and also initiated an update-initramfs operation and who knows what else.
Meanwhile, here are some more initial feedback issues (as before, if you want me to report them elsewhere, let me know where, and I’ll be happy to):
23) apropos not working by default – the solution is to run ‘mandb’, which should normally have been done by apt or by cron. I see that there does exist a man-db script in /etc/cron.daily, so this issue would only be noticed by users who attempt to use apropos before the first time cron.daily scripts are run. I’m not sure how other distros handle this.
24) This new install is now on a laptop, so I quickly realized that the lid functions and the screen blank / lock functions aren’t functioning, and there isn’t a helpful app for configuring them. What is the recommended accepted ‘antix magic’ method? A quick web search returned what is now bad advice from a very old and archived antix forum.
24.1) The acpi-support package is an unexpected version that includes many scripts specific to particular manufacturers’ hardware, and much more convoluted than on my other working non-systemd (devuan) laptop.
24.2) Selecting logout from the icewm menu, and then suspend does not lock the screen upon resume.
24.3) Selecting logout from the icewm menu, and then lock screen does function (don’t know yet if it will timeout and suspend), but the unlock screen has a blank white wallpaper, and I suspect the intended behaviour is to use the default antix wallpaper (DC metro Shady Grove?)
25) This issue is really a question about the AntiX repository architecture – what is/are the antix upstream(s)? For the install, I selected ‘antix testing’, and I see that my sources.list includes debian ftp repositories. Is antix a direct debian derivative? I thought it was based on MX, which in turn was based on devuan? Is debian testing really the recommended source for versions of packages that haven’t yet made it into antix? Or should another source be used (eg. MX, devuan)? This is potentially important because debian sometimes unique / extensive / weird patching and configuring of packages.
26) torrent application – The gui menu uses transmission, but the command-line control center uses rtorrent, so a user wanting to use both interfaces will need two sets of configs and have to deal with complications in sharing torrents between rtorrent and transmission. However, transmission itself has an ncurses interface, called transmission-remote-cli, so if antix uses that for the command-line control center, there is total sharing and compatibility between it and the gui menu. Under the hood, the setup is a bit more complex, because one needs to install packages transmission-daemon and transmission-remote-cli, start the daemon, and then connect to it from either the command line or gui, but the setup is usually automated as a startup service…
27) multiple simultaneous gui sessions – how does antix expect one to ‘switch users’, ie. interrupt a user’s gui session and switch to other user(s) gui session(s), and back, without logging out of any?
- This reply was modified 4 years, 7 months ago by boruch.
28) The xlockmore package, used by antix by default for locking the screen, isn’t by default installed properly, which explains why it behaves the way it does.
28.1) It’s first point of failure is finding a correct font. It is configured to use a version of Helvetica, which is not by default installed (run xlock from the command line to see the exact error message). This can be circumvented by using the command line option ‘-font fixed’.
28.2) The second point of failure is accessing what the xlock documentation refers to as ‘modes’, but which you and I would call ‘plug-ins’ or ‘extensions’. The default configuration is to randomly cycle among available modes, but none are included, so it falls back to displaying a blank screen, and since no colors were specified (command line options -background and -foreground) the display is black on white.
28.3) At the very least, the ‘image’ mode should have been included. This would allow one or a list of images to be displayed as the background. They need to specified using the command line option ‘-bitmap’ and seem to have to be in either xbm, xpf, or ras format.
28.4) It would be helpful to know from where antix pulled its version of the package. It doesn’t seem to have come from debian and is significantly older than the package developer’s current stable version (5.31 vs 5.56).
greyowl
25) This issue is really a question about the AntiX repository architecture – what is/are the antix upstream(s)? For the install, I selected ‘antix testing’, and I see that my sources.list includes debian ftp repositories. Is antix a direct debian derivative? I thought it was based on MX, which in turn was based on devuan? Is debian testing really the recommended source for versions of packages that haven’t yet made it into antix? Or should another source be used (eg. MX, devuan)? This is potentially important because debian sometimes unique / extensive / weird patching and configuring of packages.
I believe that antiX is a direct debian derivative and MX is based on antiX. Neither of them is based on Devuan.
Dell Latitude D620 laptop with antiX 22 (64 bit)
@greyowl : Thanks for the response. It was getting mighty lonely here this past week. For the benefit of the distribution’s core-developers, I should say that it’s not very confidence-inspiring to potential users who are are deciding whether to adopt a distribution that such a long time passes before any kind of even partial response is forthcoming. If they feel their time and effort is better spent elsewhere, so be it.
anticapitalista
28 – install xlockmore-gl if you want graphics.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
@anticapitalista : Thanks – I’ll look into it.
@anticapitalista: I’m now installing the package and even before using it I can report two more issues / bug reports / packaging errors.
29) The install insists on installing several wayland packages, even though the I never installed wayland, and am using X11 !, This is a pretty fresh install with not much if anything installed on top the default. Is the default install corrupted with wayland stuff? It won’t *hurt* anything, but it would add useless cruft and space, and also add to any apt update overhead.
30) The apt install process was dominated by a very long interval in which a zillion (I counted) locales were being created / updated ! But why? Like I said, this is being reported for an almost virgin install, so st the default install pushing all those locales? This is important because not only is it useless cruft that takes up a lot of space on disk, but it also adds a lot of extra time whenever apt wants to perform an update that affects locales.
- You must be logged in to reply to this topic.
