Search Results for 'linux live kit'

[Forum Admin rokytnji]

Have not looked at the script yet to see if it makes any systemd calls.

https://github.com/Tomas-M/linux-live

From the build script

# BIOS / MBR booting
cp -r bootfiles/* $BOOT
KER=$(basename $(readlink -f $VMLINUZ))
cat bootfiles/syslinux.cfg | sed -r -e "s:/boot/:/$LIVEKITNAME/boot/:" -e "s:vmlinuz:$KER:" > $BOOT/syslinux.cfg
cat bootfiles/syslinux.cfg | sed -r "s:/boot/:/$LIVEKITNAME/boot/:" > $BOOT/syslinux.cfg
cat bootfiles/bootinst.bat | sed -r "s:/boot/:/$LIVEKITNAME/boot/:" | sed -r "s:\\\\boot\\\\:\\\\$LIVEKITNAME\\\\boot\\\\:" > $BOOT/bootinst.bat
cp $VMLINUZ $BOOT/ || exit

• This reply was modified 1 year, 3 months ago by rokytnji.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

Found this today
https://www.linux-live.org/

Linux Live Kit
is a set of shell scripts which allows you to create your own Live Linux from an already installed Linux distribution. The Live system you create will be bootable from CD-ROM or USB Flash Drive

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Anonymous]

xref: MX Linux forum topic: Forking and maintaining GTK 2 library and applications

.
> I prefer GTK 2 applications as they have a classic look to them, are much lighter, and their themes look better.

I share your sentiment.

> GTK2 [..] many of those packages are now unmaintained

unmaintained == forcibly deprecated, by the Gnome project and the Debian Gnome Team
(Jeremy Bicha, and the team, is (y)our nemesis ~~ an opponent or rival which we cannot best or overcome)

unmaintained ~= cherished, “warts and all”.
No showstopper bugs, so no expectation of need to “maintain” it. If it ain’t broke don’t fix (deprecate) it…

> GTK 3 is too heavy and…

…and editing or creating gtk3 themes is quite a chore. Many, if not most gtk3 themefiles need to be “compiled”.

> I would make it a personal project to repackage applications that can still be compiled against GTK 2, and maybe take the time to learn the GTK toolkit in order to backport it.

For personal use, I’ve preserved several gtk2 applications ~~ compiling ’em and their (now absent from debian stable repo) dependent libraries on the newer O/S version. It’s quite a chore, for any given application there are typically a LOT of dependent library packages (many of which have also been nixed from debian). backforward porting cannot be fully achieved (the app will run, but gLib or another component will spammily spew deprecation warnings. To skirt namespace collision (gtk3 libs bearing same-name), one would need to compile-and-rename various chained, low level, library packages (e.g. ,myglib2) and search/replace all affected references throughout the application source code. Alternatively, we (you, me) may be able to utilize LD_PRELOAD and AppImage packaging to continue delivering select gtk2 applications.

Also, bear in mind that many of our (well, true for mine at least) cherished “good old applications” are pygtk (python 2 + gtk 2)
which necessitates curation and maintenance of a plethora packages which provide various python2 libraries.

> There have also been packages recompiled for GTK 2 on the AUR

Really “recompiled”, or just preserved to (still) build against gtk2, or against a non-current version of gLib?
If you share some links, I will take a look.

> a fork based off of the GTK 2 code called STLWRT [..] to compile both GTK 2 and GTK 3 apps into consistently looking like GTK 2.

Smells like a fool’s errand considering that there’s nosuchthing as *one* “gtk3”. Breaking changes//deprecations exist across the 20+ various gtk 3.xx versions

Is it antiX’s plan to keep supporting GTK 2 in its repos and offer GTK 2 apps indefinitely?

Clearly the answer is NO.
Most if not all of the antiX -authored (scripted, not compiled) utilities have already been rewritten; the newer versions use python3 + gtk3; the compiled antiX/MX apps rely on Qt.

[Moderator Brian Masinick]

@linuxdaddy: I had forgotten about where you are; thanks for reminding us.

I’m guessing that you are in one of the higher elevations as opposed to a low valley; otherwise I am surprised you received 3-5″ of snow.

About an hour away from us in North Carolina, they had high winds that brought in MUCH LOWER temperatures and a dusting of white on a few peaks, but that’s it.

We briefly got down to 32 one day ago but we’re back up to 57 this afternoon; clearly nowhere near snow maintaining temperatures!

I also noticed your pet. I definitely remember Olive the kitty but I forget this one’s name. Looks like he (she) is having a good time!

--
Brian Masinick

[Moderator Brian Masinick]

Regarding the telemetry, yeah, the default, and the way the World Wide Web was created from the very beginning, made information very accessible, but yes, the complete and absolute security of what you’re doing, where you’ve been, etc. has always been in question from the very beginning.

I was aware of much of this information before the “famous” (or infamous, depending on your opinion) major, significant release of Windows 95, which, for better or worse, truly helped the masses for the first time gain access to the kind of computing information I’ve had access to since at least the early eighties, as far as the broadest reaches of the Internet, and longer than that, as far as industry-wide technology and information.

I remember when Microsoft made a marketing contract with the owners of the Rolling Stones tune, “Start Me Up!”. Very successful marketing campaign. That technology caused me to purchase my own personal computer for the first time, and it came with Windows for Workgroups 3.11, and I purchased a Windows 95 kit and a book about Slackware – “Linux: Configuration and Installation (Mis Press Slackware Series) by Eric Foster-Johnson, Patrick Volkerding, and Kevin Reichard.”

It was this book that got me actively into Linux, though I had been following it in literature for a few years. After that, my next door neighbor, also interested in Linux from a telephony perspective (he and a partner built a company and made their in house phone system based on a small business phone network based on Linux). He introduced me to a USA Linux Users Group called the USALUG. A friend there got me interested in Debian and some of it’s derivatives, and for me, the rest is history.

To this day I find Slackware to be pretty efficient, but I prefer Debian style packaging, so I use Debian-based distributions primarily, including both systemd and non systemd variants.

Back to telemetry and information compromise, in all of my years of using on line technology, purchasing products online and using computers, I’ve only been intruded upon twice, neither of which affected my long term safety. The first was my own local grocery store that got compromised; I changed my credit cards, etc. The second was a foreign scam that ALMOST caught me; I smelled a RAT, contacted a friend of mine at the local police department, gave them the information, and they cooperated with federal and international parties and eventually caught the specific perpetrators. In neither case did I personally suffer financial loss.

I am not afraid of my browsing or buying habits being challenged, other than the possibility of tracking my travel; however, now that I live in a well-protected senior living community, I needn’t be afraid of that either; the likelihood of personal property being stolen or compromised is minimal.

I share this long, drawn out story, including the stuff about Windows, Slackware, Debian, and Linux because I’ve used this stuff as long as most people here and longer than 99% of the world’s population. I purchased 100% of my holiday presents online, back before we had today’s security measures in place and whether someone knows a lot about me or not, I’ve not been physically or financially harmed by any of it, though a few have attempted to harm me; the only ones who succeeded in causing me financial harm were people I misjudged, not someone who took anything over the Internet from me.

Can telemetry data be used? Yeah, even the early founders discussed this. Java, with all of its capabilities, was also examined for trade-offs between effectively networking and connecting data versus opening potential holes. IBM, out of the oldest computing companies, once had the most secure systems because they were the LEAST open – their systems and networks did NOT connect to the world wide Internet until well after Microsoft, UNIX, and Linux systems (plus Digital Equipment Corporation, with their DECnet, before the TCP/IP Internet effectively wiped them out).

Data is available. It CAN be captured, but it’s not particularly easy to grab, and it’s harder to specifically identify to a particular user. The bad guys go after big hauls, usually of easy, “low hanging fruit” with poor security, or with payloads that make hard work yield millions, even billions, for a successful “heist”. Someone COULD potentially find, get, steal, “whatever” something from me. The effort to do it would almost certainly cost FAR MORE than the amount they could possibly gain from attempting to acquire any of my assets; they’re non-zero, but they’re not that much! Most of us are probably in a similar place; why worry? The bad guys can get much more, both in intelligence, information, and financial assets by looking elsewhere!

--
Brian Masinick

[Member ModdIt]

Hi anticapitalista, sorry but this is already somewhat out of controll.
Parents are involved as they pointed out the problem which I did not know about.

Checked again user machine and mine have as below, the install came from official channnel.
Further to that two other separate official installs all same.

My weight at debian is less than a feather, I have reported bugs without an answer in the past.

This reflects on directly antiX, I think they will not give a damn.

# Partner Distribution Configuration File
# Author: Dan Mills <thunder@mozilla.com>

[Global]
id=antiXLinux
version=21
about=Updates will come through package manager
about.en-US=Updates will come through package manager

[Preferences]

# Disable the bundled pocket extension
extensions.pocket.enabled=false

# Privacy: enable tracking protection, disable third-party cookies
network.cookie.cookieBehavior=1
privacy.trackingprotection.enabled=true
privacy.trackingprotection.introCount=20

# Telemetry: report everything, no prompting.
toolkit.telemetry.enabled=true
browser.crashReports.unsubmittedCheck.autoSubmit=true
datareporting.policy.dataSubmissionPolicyBypassNotification=true

# Disable first-run annoyances.
browser.rights.3.shown=true
browser.startup.homepage_override.mstone=”ignore”

[LocalizablePreferences]
browser.startup.homepage=”https://www.antixforum.com/&#8221;

# If a directory for the locale the browser is running in doesn’t
# exist, Firefox will automatically try the ‘default’ locale, as defined
# by the distribution.searchplugins.defaultLocale preference.

# Bookmarks

# There are two “toplevel” sections, BookmarksToolbar and BookmarksMenu.
# These can reference other sections via the “folder” type item. These
# folder sections must be named “BookmarksFolder-<id>”.

# Each section contains a list of numbered item settings, where each
# item represents a bookmark, livemark, separator, folder, or the default
# bookmarks in that container (if any). The default type is bookmark.

[BookmarksToolbar]
item.1.title=antiX Forum
item.1.link=https://www.antixforum.com/
item.1.description=
item.2.title=antiX Website
item.2.link=https://antixlinux.com/
item.2.description=

[BookmarksMenu]
item.1.type=folder
item.1.title=anticapitalista!
item.1.folderId=1
item.2.type=folder
item.2.title=antiX Linux
item.2.folderId=2

[BookmarksFolder-1]
item.1.title=anti-fascist
item.1.link=http://www.antiracismfascism.org/
item.2.title=Democracy Now!
item.2.link=http://www.democracynow.org/
item.3.title=CounterPunch
item.3.link=http://www.counterpunch.org/
item.4.title=New Left Review
item.4.link=http://newleftreview.org/
item.5.title=Monthly Review
item.5.link=http://monthlyreview.org/
item.6.title=Marxists Internet Archive
item.6.link=http://www.marxists.org/
item.7.title=The Noam Chomsky Website
item.7.link=http://www.chomsky.info/
item.8.title=Radical Philosophy
item.8.link=http://www.radicalphilosophy.com/
item.9.title=Jacobin
item.9.link=https://jacobinmag.com/
item.10.title=Catalyst
item.10.link=https://catalyst-journal.com/

[BookmarksFolder-2]
item.1.title=antiX-forum
item.1.link=https://www.antixforum.com/
item.2.title=antiX Website
item.2.link=https://antixlinux.com/
item.3.title=antiX-videos
item.3.link=https://www.youtube.com/user/runwiththedolphin?feature=watch
item.4.title=old antiX-forum
item.4.link=https://www.tapatalk.com/groups/antix/
item.5.title=antiX-FAQ
item.5.link=file:/usr/share/antiX/FAQ/index.html
item.6.title=antiX wiki
item.6.link=https://antixlinuxfan.miraheze.org/wiki/Main_Page
item.7.title=antiX-equivalents
item.7.link=file:/usr/share/antiX/equivalents.html

[Forum Admin anticapitalista]

You should report this to Debian since that is where we get the package from.

This is what antiX has in /usr/share/firefox-esr/distribution/distribution.ini.

# Partner Distribution Configuration File
# Author: Dan Mills <thunder@mozilla.com>

# id: short string unique to this distribution
# about: a short descriptive (ui-visible) string for this
# distribution
# version: version of the extra distribution pieces (not the version
# of Firefox)
# bookmarks.initialized.pref: (optional) name of a boolean pref used to determine if bookmarks should be created on startup. This option should not be used except to upgrade from previous customized distributions that did not use the distribution.ini method

[Global]
id=antiXLinux
version=19
about=Updates will come through package manager
about.en-US=Updates will come through package manager
#bookmarks.initialized.pref=cck.testpartner.initialized

[Preferences]
mozilla.partner.id="
app.distributor=
app.distributor.channel=
app.update.url.manual="The Oracle recommends using synaptic for updates."
browser.search.distributionID=
app.update.enabled=false
browser.search.searchEnginesURL="https://www.startpage.com"
browser.search.defaultenginename="Startpage"
extensions.update.enabled=true
intl.locale.matchOS=true
browser.shell.checkDefaultBrowser=false
browser.newtabpage.enhanced=false
media.mediasource.enabled=true
media.mediasource.webm.enabled=true
media.fragmented-mp4.ffmpeg.enabled=true
media.fragmented-mp4.gmp.enabled=false
media.fragmented-mp4.exposed=true

[LocalizablePreferences]
browser.startup.homepage="https://www.antixforum.com/"

# If a directory for the locale the browser is running in doesn't
# exist, Firefox will automatically try the 'default' locale, as defined
# by the distribution.searchplugins.defaultLocale preference.

# Bookmarks

# There are two "toplevel" sections, BookmarksToolbar and BookmarksMenu.
# These can reference other sections via the "folder" type item. These
# folder sections must be named "BookmarksFolder-<id>".

# Each section contains a list of numbered item settings, where each
# item represents a bookmark, livemark, separator, folder, or the default
# bookmarks in that container (if any). The default type is bookmark.

[BookmarksToolbar]
item.1.title=antiX Forum
item.1.link=https://www.antixforum.com/
item.1.description=
item.2.title=antiX Website
item.2.link=https://antixlinux.com/
item.2.description=

[BookmarksMenu]
item.1.type=folder
item.1.title=anticapitalista!
item.1.folderId=1
item.2.type=folder
item.2.title=antiX Linux
item.2.folderId=2

[BookmarksFolder-1]
item.1.title=anti-fascist
item.1.link=http://www.antiracismfascism.org/
item.2.title=Democracy Now!
item.2.link=http://www.democracynow.org/
item.3.title=CounterPunch
item.3.link=http://www.counterpunch.org/
item.4.title=New Left Review
item.4.link=http://newleftreview.org/
item.5.title=Monthly Review
item.5.link=http://monthlyreview.org/
item.6.title=Marxists Internet Archive
item.6.link=http://www.marxists.org/
item.7.title=The Noam Chomsky Website
item.7.link=http://www.chomsky.info/
item.8.title=Radical Philosophy
item.8.link=http://www.radicalphilosophy.com/

[BookmarksFolder-2]
item.1.title=antiX-forum
item.1.link=https://www.antixforum.com/
item.2.title=antiX Website
item.2.link=https://antixlinux.com/
item.3.title=antiX-videos
item.3.link=https://www.youtube.com/user/runwiththedolphin?feature=watch
item.4.title=old antiX-forum
item.4.link=https://www.tapatalk.com/groups/antix/ 
item.5.title=antiX-FAQ
item.5.link=file:/usr/share/antiX/FAQ/index.html
item.6.title=antiX-equivalents
item.6.link=file:/usr/share/antiX/equivalents.html

No mention of
toolkit.telemetry.enabled=true
browser.crashReports.unsubmittedCheck.autoSubmit=true
datareporting.policy.dataSubmissionPolicyBypassNotification=true

• This reply was modified 1 year, 4 months ago by anticapitalista.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member PPC]

I’ve seen some reviews on Zorin- this kind of distros that are similar to the currently User Interface that most people are used to (windows 10) are not, in my opinion, “bad”- they serve a usefull porpose- give people, willing to try Linux, a more familiar ambient, do dimish the shock of the change.
change is not bad- I love some wierd UI’s- I even tested a MacOs like UI in antiX, just to see if it “clicked” to me- it did not- I’m set in my ways, I’m used to a toolbar on the bottom, a menu icon on the left, quick launch icons, system tray, and a clock. So I tweak a little the default icewm- change the theme, add a search icon and skippy xd to the toolbar, and it has most of the funcionality an user of a modern computer expects and then some more… but there’s a lot that people expect that icewm simply can’t deliver.
Just because I needed to keep my mind busy I began to experiment with tint2 toolbar, and then jgmenu – I was never into using toolbars and menus that did not with the WM, I considered that “bloat” (used too much system resources)- but I found a way of using my setup- that may put any Windows 10 at ease- in even lower system resources that the default rox-icewm desktop- I was not exacly trying to emulate W10, just using the good UI ideas it offered- and also ended up with something that was very usefull to me- a way to adjust to being forced to use Windows 10!- I can now switch between antiX and W10 without ever thinking “Damn wrong OS! I have to do this in another way!”.
Zorin and similar distros take the idea of providing a familiar interface to an extreme, but I can’t blame them- they are comfortable for newbies.
Well the fact that they have everything and the kitchen sink installed- hum- I’m a middle ground myself- I don’t like having loads of tools, specially tools that are heavy and that I won’t probably ever use, in my system… But I can see the value of having almost every single piece of software available- mainly because not everyone has broadband available to install GIMP or LibreOffice, etc…

I would not mind if antiX had an “ultra-complete” ISO with GIMP, L.A.M.P., Firefox, thunderbird, java, wine and steam, etc, etc, preinstalled- I would not use it, but it could be gold for someone that has no access to the internet (or has no reliable broadband or has a slow connection)- example- students that can download the iso in school, and then install and use it at home, where they do not have internet…

I did the following searches on this young at heart forum, for libudev-zero, mdev, smdev, nldev, mdevd and found nothing, not a single mention, so here is the story:

Can we live without udevd?

Let’s recapitaluta how wide this struggle has been, to not depend on IBM for your open and free software to work.

On the logind front, consolekit2 is not dead, this is old propaganda, especially with all its development from its BSD fork, consolekit2 is alive and well. But you can live well and prosper (as Spok said) without any logind. I have for quite a while. Then there was the silly myth that wayland can not work without systemd/elogind. Myth busted, the guy that made seatd broke that myth right in the myth manufacturer’s face, and once people started considering using wayland without elogind, they also found out it works perfectly fine even without seatd (if compiled as such). That deep of a myth. It is like saying you need a fishing pole to go on a date…. folklore. Also you don’t need X for wayland/wlroots/sway … it works. I still don’t like it, but whether it works is a different story.

And dbus, that decorative snitch, monitoring and communicating your every click and keystroke? It even monitors and snitches on root’s activities. So to whom is this piece of crap in service of? I’ve lived without it for years now. So more folklore spread around by the IBM parakeets.

But we are stuck with a big IBM chunk, we are not out of the hole yet, we love what IBM does for us (like junkies love the pusher) from the second we hit enter on the bootloader screen. udev hooks running and rerunning and eternally running till everything is shutdown and gone to sleep.

IS (not are) there an alternative?

Years ago somebody decided they’ve had enough with udev and wrote smdev. As simple and lean as it can possibly be, with the ability to be enriched by hw modules for anyone that desired more than a simple x86 machine booting, having classic input/output abilities, reading/mounting disks, and a few simple additional hw. It worked, it is simple (suckless) and the great story is that it runs once and ends, doesn’t need to be daemonized (thank anticapitalista for that – if you have to thank anyone – because it takes a few seconds for each run). But as hw get more fancy and multiple in necessity, it wasn’t enough for people to adopt. So it remained.

Then comes this other solution, an intermediary, which can utilize any mdev provider, simulate the ability to be triggered by a change in hw, run the mdev (of choice!), and provide new definitions for hw adder/removed. This project was called nldev, a middle man.

Then skarnet begins work, not yet finished, to provide a true and complete udev alternative, still less than 1/3 of the code of (udev/eudev/libeudev), and it does work if you study the subject in depth and can configure it right. A nice template of a .conf file to uncomment all its abilities that are utilized, would have been nice, but skarnet wants you to do your own research and make your own choices, just like s6 s6-rc, etc. No ground food and chewed ready for swallowing from skarnet, they like to see you in tears before you make their sw work. Their server has been running for a ?decade? with it, with reboots only taking place in leap years, and if there is no pandemic.

BUT!!!

Why aren’t users and distro devs running to adopt such solutions? 1 reason! X is having problems with them, in most cases you can’t get the keyboard and mouse to work properly. That’s a big one … for most people, let’s be realistic. “Some” people don’t need X, they do all their work on console, their greps and cuts and sed and vis, is all they need, and lynx for a fancy browser to relax from coding.
Why is X so peculiar about the specific mdev? Because it was written with the single piece of available to them and looks for its coding.

Pop goes the myth of X would only work with IBM’s udev.

libudev-zero

A very young and promising project, getting about 5-6 upgrades just this past week alone, although it worked 10 days ago when I fist tried it.
On the early trials I replaced libeudev with libudev-zero, booted with eudev, then shut down the daemon, then started X. Cursor, cursor theme, keyboard, all working great. Then tried to substitute eudev with one of the alternatives, I admit I don’t have yet the knowledge and patience to configure mdevd right (Sorry mr.Bercot) but smdev worked, run manually once, and then libudev-zero takes over. As soon as smdev runs and throws 30 pages of nasty looking output on your screen, the screen readjusts (just like in udevd activity), net interfaces become available, and all is well.

Hmm… not so fast slick, how is your kernel image created with smdev?

That begun being tough, mkinitcpio run aground without eudev/udev available, possibly with the libudev-zero in place of libeudev. Here comes the “middleman” that makes any mdev availability work, nldev. You substitute nldev for udev in mkinitcpio.conf and the image is created properly, nldev is configured to run smdev during the boot hooks, and you get a nice console login: with any parts of e/udev removed from the system.
And of course X started normally and my favorite terminal provided a shell.

Not so fast slick! Now that you got linux-lts image booting without udev, what else is there missing?

Ok, Ok, Ok, … (Joe Pesci voice in lethal weapon X) … some things must not work because they were compiled with udev’s existence, which eudev does wonders for substituting because …. IT IS THE SAME CODE!!! Like what, you might ask. lsusb for example, still works but throws some garbage up on top for not being able to get the udev version. The output is still the same as with eudev. /dev/disk/ is empty, but blkid works fine (it doesn’t depend on udev). All mounting/unmounting/ssh/sshfs all work. How about Gparted, does it work? NO! Why? Because it is compiled based on the specific udevd and unless it gets the version number it exits with an error. If you can bypass this, or if you and the coder of libudev-zero figure out a way to fake this functionality, I don’t think there is an issue.

Yet, again, not so fast slick!!! You are tripping over yourself.

libeudev
├─device-mapper
├─eudev
├─libgudev
├─libusb
├─lvm2
├─usbutils
└─util-linux
eudev
├─colord
└─dhcpcd

This is a list of what I have found up to now, that are very base/core parts of almost any linux distro. that depend and ARE built based on udev, and some may work fine, but internally they think that udev is there. So idially they must be rebuilt with the alternative in presence, in my case smdev, nldev, libudev-zero.
This is a little harder to do than I thought, but my abilities are limited. So it is not to say it can’t be done, I’m just passing the torch here for those that understand the importance of doing so and are willing to try it in a test installation.
I can assist with details anyone willing to give it a try, I have a runit script that works with mldev, and a 66/s6 script for not so clear solution for boot@-66, and more.

Just to see the light in the tunnel though, it is rewarding and new land will not be discovered unless we all do a little more pushing of the fence we are trapped in.

Because they want us fenced in and dependent to control us. It is our single mission in life to bring those fences down, because on our land we can build autonomy, on their land we will always be slaves. We will not make this mistake again, to allow our land to be purchased for individual use. Am I losing it? No, anticapitalista knows what I am talking about.

A las barricadas!

anti-X - Adélie - obarun - systemd Free Space

[Member melodie]

Xecure wrote:

Search the antiX forums first.

I didn’t search the forum, because it has beeen a _random discovery_ while trying several light GNU/Linux distributions in order to attempt to revive a very old laptop. (18 years old, but very nice looking on the outside).
I had discovered Devuan which I didn’t know of, as well as their snapshot tool, and tried to figure how to have the poweroff reboot etc. working with lightdm instead of slim. Both antiX and Devuan use no systemd with elogind and so on, so I figured I might try the same method on antiX.

Now what you are saying makes me think, I’ll try your way, no additional package else than pm-utils, well at least I’ll try removing both “libpolkit-gobject-elogind-1-0” and “libpolkit-backend-elogind-1-0” (devuan8 packages) and see what happends. I keep both as deb packages in a directory just in case.

But : shouldn’t them packages in the antiX distribution sources be the same version so that installing one will not create a conflict preventing the other to be installed? Shouldn’t it be an issue that should be addressed? (I am not sure how, obviously… )

I enclose a screenshot of Synaptic in antiX 64bits, with emphasis on the two packages and *the versions mis-matching* offered as a *possible update*.

Also : openbox is a window manager with some advanced features, not a desktop manager nor an environment manager so it relies not on itself to manage the desktop, but on the components which are installed along with it. LightDM meaning Light Desktop Manager, the session will require a few things to be working properly as for a full fledged Desktop Environment such as LXDE for instance, but with just some of its components the system will be even lighter.
Now you might argue that antiX is already light, whatever desktop you choose, which is right, but it’s too large to fit in some of the very old laptops when booted as live, once the squashfs is decompressed it fills all the RAM and the boot process hangs.

Also antiX and its Snapshot program is a great tool to have to make your own version. The users targeted for the versions I rebuild are *end users* with *limited needs*, so I make the ISOS as small and simple to use as possible and the users can have it evolved later as they see fit (of course they can ask for help to do that if necessary). You can have a go with the latest 32bits available, here : http://downloads.linuxvillage.org

As soon as a similar 64bits will be ready, I’ll try to write full descriptions with a few screenshots.

Thanks for your help.

• This reply was modified 1 year, 12 months ago by melodie.
• This reply was modified 1 year, 12 months ago by melodie.

Attachments:

1. 

   VirtualBox_antiX-base-64bits.png
   

[Member andyprough]

Nice to see Olive kitty make her return. Do you take requests linuxdaddy? I think Olive kitty playing in a patch of green grass this spring would make for a very nice wallpaper.

Anonymous wrote:

Here are a few more.
first photo is a cat-faced spider, which is a member of the Orb Weaver spider family.
cat-faced spider

the other two photos are of my Olive kitty.
(original text in English)

Attachments:

1. 

   olivekittymanuallens.jpg
   

[Member ModdIt]

@Robin. Thanks for checking, in the first post JohanS stated that he was able to read the card on same device with Bodhi Linux.
Unfortunately (maybe fortunately for me) I do not have a fitting card to do any tests with my hardware.
As you are seeing same kind of problem it looks like a kernel bug or regression is present in antiX.

@ JohanS To be more certain now it would be good if you could rescue your data to another storage device for
safety.
To rule out linux seeing some kind of file corruption, if you can please check again if Bodhi can read the card,
if yes which kernel is in use there. uname -r will give you the answer.
please do checks robin suggested and post.
Then try other available kernels in antiX, you can do that running live, Remaster, restart and see if you can read
the card.

Fixing frustrating issues like this one is important both for users and the distro, if this is widespread as it seems likely
linux as a whole.
@Robin be nice if you could check if this this issue is present on Bullseye.

What we need to know is which kernel version works with affected cards and devices, if possible where they stopped working, the
more precise the info the better. Maybe yoshi@mx linux can give some further insights regarding patch he applied after kernel
org posts.

Although there is a known kernel issue:
As plenty of faked SD cards are in circulation, often bought at reputable stores.
Perhaps checking cards with f3 – Fight Flash Fraud toolset might be a good idea. This toolkit can only be used on an empty card
as it reads writes and confirms data, now routine for me before using usb sticks or sd cards. f3 is available in repos.

• This reply was modified 2 years, 1 month ago by ModdIt.
• This reply was modified 2 years, 1 month ago by ModdIt.

[Member lafricain]

$ apt list --upgradable 
En train de lister... Fait
add-desktop-antix/buster 0.3.25 all [pouvant être mis à jour depuis : 0.3.22]
add-key-antix/buster 0.4.4 all [pouvant être mis à jour depuis : 0.4.3]
advert-block-antix/buster 0.2.26 all [pouvant être mis à jour depuis : 0.2.25]
antix-archive-keyring/buster 20019.3.14 all [pouvant être mis à jour depuis : 20019.3.13]
antix-goodies/buster 0.8.4.2 all [pouvant être mis à jour depuis : 0.7.18]
antix-installer/buster 1.3.5 i386 [pouvant être mis à jour depuis : 1.3.3]
antix-libs/buster 0.8.7 all [pouvant être mis à jour depuis : 0.8.3]
antix-user/buster 0.1.13 i386 [pouvant être mis à jour depuis : 0.1.10]
antix-viewer/buster 0.1.8 i386 [pouvant être mis à jour depuis : 0.1.4]
app-select-antix/buster 1.0.3 all [pouvant être mis à jour depuis : 0.1.2]
apt-notifier/buster 18.04.12 all [pouvant être mis à jour depuis : 18.04.11]
apt-transport-https/stable,stable 1.8.2.2 all [pouvant être mis à jour depuis : 1.8.2.1]
apt-utils/stable,stable 1.8.2.2 i386 [pouvant être mis à jour depuis : 1.8.2.1]
apt/stable,stable 1.8.2.2 i386 [pouvant être mis à jour depuis : 1.8.2.1]
automount-antix/buster 0.1.21 all [pouvant être mis à jour depuis : 0.1.20]
base-files/stable 10.3+deb10u8 i386 [pouvant être mis à jour depuis : 10.3+deb10u6]
bind9-host/stable 1:9.11.5.P4+dfsg-5.1+deb10u3 i386 [pouvant être mis à jour depuis : 1:9.11.5.P4+dfsg-5.1+deb10u2]
bootrepair-antix/buster 17.18 i386 [pouvant être mis à jour depuis : 17.16]
ca-certificates/stable-updates,stable 20200601~deb10u2 all [pouvant être mis à jour depuis : 20200601~deb10u1]
chroot-rescue/buster 0.1.13 all [pouvant être mis à jour depuis : 0.1.12]
cli-aptix/buster 0.2.26 all [pouvant être mis à jour depuis : 0.2.25]
cli-installer-antix/buster 4.12 all [pouvant être mis à jour depuis : 4.8]
cli-shell-utils/buster 0.3.35 all [pouvant être mis à jour depuis : 0.3.33]
codecs-antix/buster 17.7 i386 [pouvant être mis à jour depuis : 17.5]
connectshares-antix/buster 0.3.2 i386 [pouvant être mis à jour depuis : 0.3.1]
connman-vpn/stable 1.36-2.1~deb10u1 i386 [pouvant être mis à jour depuis : 1.36-2.0antix2]
connman/stable 1.36-2.1~deb10u1 i386 [pouvant être mis à jour depuis : 1.36-2.0antix2]
console-grid-gui/buster 0.2.29 all [pouvant être mis à jour depuis : 0.2.28]
control-centre-antix/buster 0.7.25 all [pouvant être mis à jour depuis : 0.7.24]
cups-ppdc/stable 2.2.10-6+deb10u4 i386 [pouvant être mis à jour depuis : 2.2.10-6+deb10u3]
ddm-mx/buster 19.11.02+antix3 all [pouvant être mis à jour depuis : 19.11.02+antix2]
desktop-defaults-base-antix/buster 0.6.13 all [pouvant être mis à jour depuis : 0.6.12]
desktop-defaults-core-antix/buster 0.6.8 all [pouvant être mis à jour depuis : 0.6.7]
desktop-defaults-fluxbox-antix/buster 0.4.16 all [pouvant être mis à jour depuis : 0.4.15]
desktop-defaults-icewm-antix/buster 0.4.22 all [pouvant être mis à jour depuis : 0.4.20]
desktop-defaults-jwm-antix/buster 0.6.4 all [pouvant être mis à jour depuis : 0.6.3]
desktop-defaults-rox-antix/buster 0.6.2 all [pouvant être mis à jour depuis : 0.5.16]
desktop-defaults-spacefm-antix/buster 0.3.8 all [pouvant être mis à jour depuis : 0.3.7]
desktop-session-antix/buster 0.5.22 all [pouvant être mis à jour depuis : 0.5.21]
distro-info-data/stable 0.41+deb10u3 all [pouvant être mis à jour depuis : 0.41+deb10u2]
ds-mouse-antix/buster 0.2.5 all [pouvant être mis à jour depuis : 0.2.3]
elogind/buster 246.9.1-1.0antix1 i386 [pouvant être mis à jour depuis : 243.7-1.0antix1]
eudev/buster 246:3.2.9.1.0antix3 i386 [pouvant être mis à jour depuis : 232:3.2.9.1]
faq-docs-antix/buster 0.6.2 all [pouvant être mis à jour depuis : 0.6.1]
feh/buster 3.6.3-1.0antix1 i386 [pouvant être mis à jour depuis : 3.5-1.0antix1]
file/stable 1:5.35-4+deb10u2 i386 [pouvant être mis à jour depuis : 1:5.35-4+deb10u1]
fonts-opensymbol/buster-backports 2:102.11+LibO7.0.4~rc2-1~bpo10+2 all [pouvant être mis à jour depuis : 2:102.11+LibO7.0.2-2~bpo10+1]
formatusb/buster 0.1.6 i386 [pouvant être mis à jour depuis : 0.1.5]
gdebi-core/buster 0.9.5.7+nmu4.antix1 all [pouvant être mis à jour depuis : 0.9.5.7+nmu3.antix2]
gdebi/buster 0.9.5.7+nmu4.antix1 all [pouvant être mis à jour depuis : 0.9.5.7+nmu3.antix2]
gir1.2-polkit-1.0/buster 0.105-29+antix1 i386 [pouvant être mis à jour depuis : 0.105-26+antix1]
gparted-common/buster 1.2.0-1.0antix1 all [pouvant être mis à jour depuis : 1.0.0-0.antix1]
gparted/buster 1.2.0-1.0antix1 i386 [pouvant être mis à jour depuis : 1.0.0-0.antix1]
grub-common/stable 2.02+dfsg1-20+deb10u4 i386 [pouvant être mis à jour depuis : 2.02+dfsg1-20+deb10u2]
grub-efi-ia32-bin/stable 2.02+dfsg1-20+deb10u4 i386 [pouvant être mis à jour depuis : 2.02+dfsg1-20+deb10u2]
grub-pc-bin/stable 2.02+dfsg1-20+deb10u4 i386 [pouvant être mis à jour depuis : 2.02+dfsg1-20+deb10u2]
grub-pc/stable 2.02+dfsg1-20+deb10u4 i386 [pouvant être mis à jour depuis : 2.02+dfsg1-20+deb10u2]
grub2-common/stable 2.02+dfsg1-20+deb10u4 i386 [pouvant être mis à jour depuis : 2.02+dfsg1-20+deb10u2]
herbstluftwm/buster 0.9.2-1.0antix1 i386 [pouvant être mis à jour depuis : 0.8.3-3.0antix1]
icewm-common/buster 2.2.1-1.0antix1 i386 [pouvant être mis à jour depuis : 1.8.3-1.0antix1]
icewm-icons-papirus-antix/buster 0.1.2 all [pouvant être mis à jour depuis : 0.1.1]
icewm/buster 2.2.1-1.0antix1 i386 [pouvant être mis à jour depuis : 1.8.3-1.0antix1]
intel-microcode/stable 3.20201118.1~deb10u1 i386 [pouvant être mis à jour depuis : 3.20200616.1~deb10u1]
inxi-gui-antix/buster 0.3.12 all [pouvant être mis à jour depuis : 0.3.11]
iproute2/stable 4.20.0-2+deb10u1 i386 [pouvant être mis à jour depuis : 4.20.0-2]
iso-snapshot-antix/buster 0.3.24 i386 [pouvant être mis à jour depuis : 0.3.19]
iso-template-antix/buster 19.18 all [pouvant être mis à jour depuis : 19.13]
jwm/buster 2.3.7-5.0antix1 i386 [pouvant être mis à jour depuis : 2.3.7-2]
libapt-inst2.0/stable,stable 1.8.2.2 i386 [pouvant être mis à jour depuis : 1.8.2.1]
libapt-pkg5.0/stable,stable 1.8.2.2 i386 [pouvant être mis à jour depuis : 1.8.2.1]
libbind9-161/stable 1:9.11.5.P4+dfsg-5.1+deb10u3 i386 [pouvant être mis à jour depuis : 1:9.11.5.P4+dfsg-5.1+deb10u2]
libbrotli1/stable,stable 1.0.7-2+deb10u1 i386 [pouvant être mis à jour depuis : 1.0.7-2]
libcairo-gobject2/stable 1.16.0-4+deb10u1 i386 [pouvant être mis à jour depuis : 1.16.0-4]
libcairo2/stable 1.16.0-4+deb10u1 i386 [pouvant être mis à jour depuis : 1.16.0-4]
libck-connector0/buster 1.2.2-1~antix2 i386 [pouvant être mis à jour depuis : 1.2.1-8~antix1]
libdns-export1104/stable 1:9.11.5.P4+dfsg-5.1+deb10u3 i386 [pouvant être mis à jour depuis : 1:9.11.5.P4+dfsg-5.1+deb10u2]
libdns1104/stable 1:9.11.5.P4+dfsg-5.1+deb10u3 i386 [pouvant être mis à jour depuis : 1:9.11.5.P4+dfsg-5.1+deb10u2]
libefiboot1/stable 37-2+deb10u1 i386 [pouvant être mis à jour depuis : 37-2]
libefivar1/stable 37-2+deb10u1 i386 [pouvant être mis à jour depuis : 37-2]
libelogind0/buster 246.9.1-1.0antix1 i386 [pouvant être mis à jour depuis : 243.7-1.0antix1]
libeudev-dev/buster 246:3.2.9.1.0antix3 i386 [pouvant être mis à jour depuis : 232:3.2.9.1]
libeudev1/buster 246:3.2.9.1.0antix3 i386 [pouvant être mis à jour depuis : 232:3.2.9.1]
libexif12/stable,stable 0.6.21-5.1+deb10u5 i386 [pouvant être mis à jour depuis : 0.6.21-5.1+deb10u4]
libfreetype6/stable,stable 2.9.1-3+deb10u2 i386 [pouvant être mis à jour depuis : 2.9.1-3+deb10u1]
libgnutls30/stable 3.6.7-4+deb10u6 i386 [pouvant être mis à jour depuis : 3.6.7-4+deb10u5]
libgssapi-krb5-2/stable,stable 1.17-3+deb10u1 i386 [pouvant être mis à jour depuis : 1.17-3]
libimobiledevice6/stable 1.2.1~git20181030.92c5462-2+deb10u1 i386 [pouvant être mis à jour depuis : 1.2.1~git20181030.92c5462-2]
libisc-export1100/stable 1:9.11.5.P4+dfsg-5.1+deb10u3 i386 [pouvant être mis à jour depuis : 1:9.11.5.P4+dfsg-5.1+deb10u2]
libisc1100/stable 1:9.11.5.P4+dfsg-5.1+deb10u3 i386 [pouvant être mis à jour depuis : 1:9.11.5.P4+dfsg-5.1+deb10u2]
libisccc161/stable 1:9.11.5.P4+dfsg-5.1+deb10u3 i386 [pouvant être mis à jour depuis : 1:9.11.5.P4+dfsg-5.1+deb10u2]
libisccfg163/stable 1:9.11.5.P4+dfsg-5.1+deb10u3 i386 [pouvant être mis à jour depuis : 1:9.11.5.P4+dfsg-5.1+deb10u2]
libjpeg62-turbo/stable 1:1.5.2-2+deb10u1 i386 [pouvant être mis à jour depuis : 1:1.5.2-2+b1]
libk5crypto3/stable,stable 1.17-3+deb10u1 i386 [pouvant être mis à jour depuis : 1.17-3]
libkrb5-3/stable,stable 1.17-3+deb10u1 i386 [pouvant être mis à jour depuis : 1.17-3]
libkrb5support0/stable,stable 1.17-3+deb10u1 i386 [pouvant être mis à jour depuis : 1.17-3]
libldap-2.4-2/stable 2.4.47+dfsg-3+deb10u6 i386 [pouvant être mis à jour depuis : 2.4.47+dfsg-3+deb10u2]
libldap-common/stable 2.4.47+dfsg-3+deb10u6 all [pouvant être mis à jour depuis : 2.4.47+dfsg-3+deb10u2]
liblwres161/stable 1:9.11.5.P4+dfsg-5.1+deb10u3 i386 [pouvant être mis à jour depuis : 1:9.11.5.P4+dfsg-5.1+deb10u2]
libmagic-mgc/stable 1:5.35-4+deb10u2 i386 [pouvant être mis à jour depuis : 1:5.35-4+deb10u1]
libmagic1/stable 1:5.35-4+deb10u2 i386 [pouvant être mis à jour depuis : 1:5.35-4+deb10u1]
libmariadb3/stable 1:10.3.27-0+deb10u1 i386 [pouvant être mis à jour depuis : 1:10.3.23-0+deb10u1]
libnss-myhostname/stable 241-7~deb10u6 i386 [pouvant être mis à jour depuis : 241-7~deb10u4]
libp11-kit0/stable,stable 0.23.15-2+deb10u1 i386 [pouvant être mis à jour depuis : 0.23.15-2]
libpam-elogind/buster 246.9.1-1.0antix1 i386 [pouvant être mis à jour depuis : 243.7-1.0antix1]
libpolkit-agent-1-0/buster 0.105-29+antix1 i386 [pouvant être mis à jour depuis : 0.105-26+antix1]
libpolkit-gobject-1-0/buster 0.105-29+antix1 all [pouvant être mis à jour depuis : 0.105-26+antix1]
libpolkit-gobject-elogind-1-0/buster 0.105-29+antix1 i386 [pouvant être mis à jour depuis : 0.105-26+antix1]
libproxy1v5/stable,stable 0.4.15-5+deb10u1 i386 [pouvant être mis à jour depuis : 0.4.15-5]
libreoffice-style-colibre/buster-backports 1:7.0.4~rc2-1~bpo10+2 all [pouvant être mis à jour depuis : 1:7.0.2-2~bpo10+1]
libsnmp-base/stable 5.7.3+dfsg-5+deb10u2 all [pouvant être mis à jour depuis : 5.7.3+dfsg-5+deb10u1]
libsnmp30/stable 5.7.3+dfsg-5+deb10u2 i386 [pouvant être mis à jour depuis : 5.7.3+dfsg-5+deb10u1]
libsqlite3-0/stable 3.27.2-3+deb10u1 i386 [pouvant être mis à jour depuis : 3.27.2-3]
libssl1.1/stable 1.1.1d-0+deb10u5 i386 [pouvant être mis à jour depuis : 1.1.1d-0+deb10u3]
libtiff5/stable 4.1.0+git191117-2~deb10u2 i386 [pouvant être mis à jour depuis : 4.1.0+git191117-2~deb10u1]
libuno-cppu3/buster-backports 1:7.0.4~rc2-1~bpo10+2 i386 [pouvant être mis à jour depuis : 1:7.0.2-2~bpo10+1]
libuno-cppuhelpergcc3-3/buster-backports 1:7.0.4~rc2-1~bpo10+2 i386 [pouvant être mis à jour depuis : 1:7.0.2-2~bpo10+1]
libuno-purpenvhelpergcc3-3/buster-backports 1:7.0.4~rc2-1~bpo10+2 i386 [pouvant être mis à jour depuis : 1:7.0.2-2~bpo10+1]
libuno-sal3/buster-backports 1:7.0.4~rc2-1~bpo10+2 i386 [pouvant être mis à jour depuis : 1:7.0.2-2~bpo10+1]
libuno-salhelpergcc3-3/buster-backports 1:7.0.4~rc2-1~bpo10+2 i386 [pouvant être mis à jour depuis : 1:7.0.2-2~bpo10+1]
libxml2/stable 2.9.4+dfsg1-7+deb10u1 i386 [pouvant être mis à jour depuis : 2.9.4+dfsg1-7+b3]
libzstd1/stable 1.3.8+dfsg-3+deb10u2 i386 [pouvant être mis à jour depuis : 1.3.8+dfsg-3]
live-usb-maker-gui-antix/buster 0.2.18 i386 [pouvant être mis à jour depuis : 0.2.14]
live-usb-maker/buster 0.4.8 all [pouvant être mis à jour depuis : 0.4.6]
mariadb-common/stable 1:10.3.27-0+deb10u1 all [pouvant être mis à jour depuis : 1:10.3.23-0+deb10u1]
mountbox-antix/buster 0.1.14 all [pouvant être mis à jour depuis : 0.1.12]
nano/buster 5.6.1-0.antix1 i386 [pouvant être mis à jour depuis : 5.3.0-1.0antix1]
ncdu/buster 1.15.1-1.0antix1 i386 [pouvant être mis à jour depuis : 1.13-1+b1]
network-assistant/buster 0.1.6 i386 [pouvant être mis à jour depuis : 0.1.4]
openssl/stable 1.1.1d-0+deb10u5 i386 [pouvant être mis à jour depuis : 1.1.1d-0+deb10u3]
packageinstaller-pkglist/buster 0.3.27 all [pouvant être mis à jour depuis : 0.3.23]
packageinstaller/buster 0.2.7 i386 [pouvant être mis à jour depuis : 0.2.4]
papirus-mini-antix/buster 0.1.3 all [pouvant être mis à jour depuis : 0.1.1]
policykit-1/buster 0.105-29+antix1 i386 [pouvant être mis à jour depuis : 0.105-26+antix1]
python-apt-common/stable,stable 1.8.4.3 all [pouvant être mis à jour depuis : 1.8.4.1]
python-lxml/stable,stable 4.3.2-1+deb10u2 i386 [pouvant être mis à jour depuis : 4.3.2-1]
python3-apt/stable,stable 1.8.4.3 i386 [pouvant être mis à jour depuis : 1.8.4.1]
python3-lxml/stable,stable 4.3.2-1+deb10u2 i386 [pouvant être mis à jour depuis : 4.3.2-1]
remaster-antix/buster 0.7.22 all [pouvant être mis à jour depuis : 0.7.21]
repo-list/buster 0.1.22 all [pouvant être mis à jour depuis : 0.1.20]
repo-manager/buster 0.2.4.2 i386 [pouvant être mis à jour depuis : 0.2.4.1]
rox-filer/buster 1:2.11-5.0antix2 i386 [pouvant être mis à jour depuis : 1:2.11-1.2]
runit-helper/buster 2.10.1+antix1 all [pouvant être mis à jour depuis : 2.8.6]
screenshot-antix/buster 0.2.7 all [pouvant être mis à jour depuis : 0.2.5]
set-dpi-antix/buster 0.1.18 all [pouvant être mis à jour depuis : 0.1.16]
slim-themes-extras-antix/buster 0.1.5 all [pouvant être mis à jour depuis : 0.1.4]
sudo/stable,stable 1.8.27-1+deb10u3 i386 [pouvant être mis à jour depuis : 1.8.27-1+deb10u2]
synaptic/buster 0.90.2+antix1 i386 [pouvant être mis à jour depuis : 0.90+antix3]
tmux/buster 3.1c-1.0antix1 i386 [pouvant être mis à jour depuis : 3.1b-1.0antix1]
tomb/buster 2.9+dfsg1-1.0antix1 i386 [pouvant être mis à jour depuis : 2.7+dfsg2-1]
tzdata/stable-updates,stable 2021a-0+deb10u1 all [pouvant être mis à jour depuis : 2020a-0+deb10u1]
uno-libs-private/buster-backports 1:7.0.4~rc2-1~bpo10+2 i386 [pouvant être mis à jour depuis : 1:7.0.2-2~bpo10+1]
unzip/stable 6.0-23+deb10u2 i386 [pouvant être mis à jour depuis : 6.0-23+deb10u1]
ure/buster-backports 1:7.0.4~rc2-1~bpo10+2 i386 [pouvant être mis à jour depuis : 1:7.0.2-2~bpo10+1]
virtualbox-guest-dkms/buster 6.1.18-dfsg-2~mx19+1 all [pouvant être mis à jour depuis : 6.1.14-dfsg-2~mx19+1]
virtualbox-guest-utils/buster 6.1.18-dfsg-2~mx19+1 i386 [pouvant être mis à jour depuis : 6.1.14-dfsg-2~mx19+1]
virtualbox-guest-x11/buster 6.1.18-dfsg-2~mx19+1 i386 [pouvant être mis à jour depuis : 6.1.14-dfsg-2~mx19+1]
wallpaper-antix/buster 0.5.5 all [pouvant être mis à jour depuis : 0.5.4]
xfburn/buster 0.6.2-1.0antix1 i386 [pouvant être mis à jour depuis : 0.5.5-2]
xserver-common/stable,stable 2:1.20.4-1+deb10u2 all [pouvant être mis à jour depuis : 2:1.20.4-1+deb10u1]
xserver-xorg-core/stable,stable 2:1.20.4-1+deb10u2 i386 [pouvant être mis à jour depuis : 2:1.20.4-1+deb10u1]
youtube-dl/buster 2021.01.16-1.0antix1 all [pouvant être mis à jour depuis : 2020.09.14-1.0antix2]

And inxi:

$ inxi -Fxz
System:
  Host: unika Kernel: 4.9.235-antix.1-486-smp i686 bits: 32 compiler: gcc 
  v: 8.3.0 Desktop: IceWM 1.8.3 
  Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Desktop System: VIA product: KT400-8235 v: N/A serial: <filter> 
  Mobo: N/A model: KT400-8235 serial: <filter> BIOS: Phoenix v: 6.00 PG 
  date: 10/08/2003 
CPU:
  Topology: Single Core model: AMD Athlon XP 3000+ bits: 32 type: UP 
  arch: K7 Palomino+ L2 cache: 512 KiB 
  flags: pae sse bogomips: 4368 
  Speed: 2184 MHz min/max: N/A Core speed (MHz): 1: 2184 
Graphics:
  Device-1: AMD RV280 [Radeon 9200 SE] vendor: PC Partner Limited 
  driver: radeon v: kernel bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.4 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1280x1024~60Hz 
  OpenGL: renderer: Mesa DRI R200 (RV280 5964) x86/MMX+/3DNow!+/SSE DRI2 
  v: 1.3 Mesa 18.3.6 direct render: Yes 
Audio:
  Device-1: VIA VT8233/A/8235/8237 AC97 Audio vendor: Chaintech 
  driver: snd_via82xx v: kernel bus ID: 00:11.5 
  Sound Server: ALSA v: k4.9.235-antix.1-486-smp 
Network:
  Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter 
  driver: 8139too v: 0.9.28 port: ac00 bus ID: 00:0c.0 
  IF: eth0 state: unknown speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 232.89 GiB used: 4.20 GiB (1.8%) 
  ID-1: /dev/sda vendor: Western Digital model: WD2500BEVT-22A23T0 
  size: 232.89 GiB 
Partition:
  ID-1: / size: 226.23 GiB used: 4.20 GiB (1.9%) fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Info:
  Processes: 149 Uptime: 1m Memory: 1000.6 MiB used: 109.0 MiB (10.9%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.36 

[Member andyprough]

The Surf browser seems to be everything that epiphany-browser tries to be, in terms of minimal footprint but still delivering good rendering and video. I built and installed it on my modern laptop and it uses just about 200mb ram to play the video on the home page of antixlinux.com, so about 1100mb less than epiphany-browser.
https://surf.suckless.org/

Pretty easy to make and install, maybe it would build on a non-SSE2 system.

Update: I did a little more reading. According to the Debian 10.1 release notes, non-SSE2 compatibility was built into webkit2gtk by September 2019. Since Surf browser uses webkit2gtk, Surf should work OK on older non-SSE2 computers. https://www.debian.org/News/2019/20190907

[Anonymous]

But the point is that this problem is probably with more than one package, and it will get more common with newer packages.

Let’s park the “probably”.
The devuan project Devuan currently maintains only 118 packages.
https://gitea.devuan.dev/devuan?page=8
I say “only” because
1) this total is less than when previously checked (back a few years when updating the nosystemd.org wiki)
2) many casual users falsely believe Devuan has “rescued” a huge number of systemd-tainted packages

.
Of those 118 packages, 60 are related to devuan infrastructure or are otherwise unuseful uninteresting to anyone running a desktop, non-devuan, system:
linux-raspi
linux-sunxi
devuan-baseconf
pkgsel
unattended-upgrades
devuan-keyring
www.devuan.org (web docs packagename)
documentation (was devuan-doc)
infrastructure_doc
installer-iso
gitea.devuan.dev (web assets)
clearlooks-phenix-lightpurpy-theme
clearlooks-phenix-darkpurpy-theme
clearlooks-phenix-purpy-theme
darkpurpy-icon-theme
clearlooks-phenix-cinnabar-theme
cinnabar-icon-theme
devuan-lintian-profile
choose-mirror
choose-init
live-build
openstack-devuan-images
pdns-recursor
debootstrap
base-files
apt-setup
net-tools
reportbug
rootskel-gtk
anna
base-installer
lsb
ltsp
ltspfs
ldm
pcsc-lite
ansible-role-nginx
jenkins-debian-glue
releasebot
jessie-support
cryptsetup-modified-functions
desktop-base
389-ds-base
tellpackage
debian-installer
gitea-spammerblock
sacc
dak
tasksel
sanity
britney2
main-menu
popularity-contest
distro-info-data
devuan-sanity
debian-config-override
amprolla3
pinthread
rrqnet

.
Another 30 or so packages are unappealing (same/older versions, or lesser functionality) compared to packages available via antiX repo or MX Linux repo:
refractasnapshot-base
refractasnapshot-gui
refractainstaller-gui
refractainstaller-base
xfce4-session
xfce4-systemload-plugin
xfce4-settings
xfce4-panel
plymouth
lightdm
dbus
policykit-1
cowdancer
xlennart
rsyslog
bash-completion
firejail
util-linux
valgrind
procps
apt
gpsd
colord
consolekit2 (deprecated, unneeded in antiX 19)
udev (unneeded in antiX 19)
libvirt
sysvinit
gdisk
cups
slim
apulse
elogind
eudev

Having discounted the above, only a short “shortlist” remains. Notes-to-self from my recent check show the following as the only noteworthy packages “of possible interest”:

dnscrypt-proxy
fontsnaps (for xfce-4)
gvfs
init-system-helpers
iwd
meson
net-tools
network-manager
openvpn
packagekit
pulseaudio
python3-fusepy
seatd (nascent project, elogind alternative)
setnet
sshguard
surf2
tomcat9
udisks2
upower
vdev
wicd
lxc-templates
cgroupfs-mount
cgmanager