A way to update versions elegantly?

[Member melodie]

Hello,
now both 32bits and 64bits versions of Bento antiX are ready to be spread among testers and a larger public, small, less than 700MB each, coming with Openbox in a easy to use and working out of the box manner. So I will soon write a full presentation with screenshots and all for both of them.

I have a question in my mind : is there a way to get the versions number and name evolve at same time as antiX does? I mean in a automated way?

I had noticed at the start of one of the last respins I did before hoping to the new, it was saying something such as “Welcome to antiX Keller 17.4.1…”

(I remove the splasht boot by default).

In the image above I am showing the files that revealed the name and number version in their content, which I have edited by hand (almost all of them). I would have tried a different approach if I had known that they belonged to a specific package, but I was unable to find such information (I tried “dpkg -S” as root against some of those files and it returned that they didn’t belong to any package).

Thanks for your know-how. And thanks for all your work!

• This topic was modified 1 year, 11 months ago by melodie.
• This topic was modified 1 year, 11 months ago by melodie.

[Member PPC]

Helpful

Up

0

::

melodie wrote:

is there a way to get the versions number and name evolve at same time as antiX does?

I’m under the impression that antiX always shows the version number of the original install, even after performing “full upgrades”, that’s by design to make troubleshooting easier (because upgraded versions are never really just like a fresh install).

PS:
I tested one of you bento versions a while back, and I remember it being very light on system resources…
But I’m a hardcore antiX user- I have it modded to suit all my needs, from my crappy old netbook to my multicore desktop- I always use the same interface and the same packages- on the netbook, my go to browser is antix’s very owm version of badwolf, ideal for compatible devices, with very slow system ressources and/or people that want a secure browser, but without the hassle os using tor browser.
I do love Openbox, but I stick with Fluxbox, just because it comes, out of the box, with antiX.
Your picture show a very cool desktop, in a retro sort of way, that could appeal to people that do like old style interfaces, but with all modern beneficts… (a terminal with a blue background does make me remember my old BSOD Windows days…)

P.

[Member Xecure]

Helpful

Up

0

::

See how MX Linux does it, and you can make a similar package for yourself.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Anonymous]

Helpful

Up

0

::

In previous antixforum topics, I’m certain we have discussed howto (what is necessary) to customize. The “automated way” detail was not discussed, just howto assign custom O/S and release name to replace antiX… and whatall needs to be changed, in multiple places (and within the initramfs content) so that the customization will survive across remaster and/or snapshot operations. Any automation would hinge on (stack upon) running a script which, on-demand, performed the customization steps.

From foggy memory, I recall worrying that there was a sticking point related to performing a snapshot from an already installed-to-disk system. Upon installation to disk, several “live” components are removed… and later, if a snapshot is performed, a “installed-to-live()” routine does retrieve a fresh, current version, copy of those live -related files. Nowadays, the snapshot tool has a feature (must edit config file to enable?) which will PAUSE after the work directory has been populated with files, so that you can (??? unpack initramfs content, customize, repack) before iso-snapshot proceeds to generating the ISO file.

I tried “dpkg -S” as root [..] and it returned that they didn’t belong to any package

Also from foggy memory: anticapitalista posted to mention “while snapshot is paused, just edit the working directory copies of lsb-release and os-release.” I’m unsure whether that carries over to the “pretty-name” file which winds up populated along with the dynamically-generated during livesession “initrd.out” file.

/live/config (aka “/etc/live/config”)

$ ls /etc/live/config
boot-device  cmdline2  distro     font        lang         proc-cmdline  virtualbox
cmdline      disabled  dmesg.out  initrd.out  pretty-name  tsplash

[Member melodie]

Helpful

Up

0

::

PPC wrote:

Your picture show a very cool desktop, in a retro sort of way, that could appeal to people that do like old style interfaces, but with all modern beneficts… (a terminal with a blue background does make me remember my old BSOD Windows days…)

P.

The Sakura terminal background was temporary. 🙂

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

Attachments:

1. 

   VirtualBox_bento-antiX-i486-23-mai_25_05_2021_01_06_03.png
   

2. 

   VirtualBox_bento-antiX-i486-23-mai_25_05_2021_01_06_20.png
   

[Author]

Posts