[SOLVED] How to identify Slackware Current? (Feature Request)

marav · 01-08-2022, 04:46 PM

Quote:

Originally Posted by iluvatar1

Hmm yeah, I did not want to suggest what fields to use, but now that you cited the docs, maybe VARIANT or VARIANT_ID would be useful tags ...
According to the link I already posted (https://docs.slackware.com/howtos:mi...ckware_version), there is no currently a way to distinguish among current versions.

I'm not sure Pat will recompile aaa_base with each update

iluvatar1 · 01-08-2022, 05:05 PM

Quote:

Originally Posted by marav

I'm not sure Pat will recompile aaa_base with each update

You are right, this is just a suggestion and surely is not the ideal. Maybe my case is just a singular point so not worth to be taken into account. Thanks for showing the possible implication of changing /etc/os-release with each date.

Petri Kaukasoina · 01-09-2022, 03:46 AM

Quote:

Originally Posted by iluvatar1

Is there a way to know the actual time stamp of the current version one is using?

If you use slackpkg, would this help?

Code:

head -1 /var/lib/slackpkg/ChangeLog.txt

chrisretusn · 01-09-2022, 04:41 AM

Quote:

Originally Posted by Petri Kaukasoina

If you use slackpkg, would this help?

Code:

head -1 /var/lib/slackpkg/ChangeLog.txt

Beat me to it.

bormant · 01-09-2022, 09:19 AM

Keep in mind this ChangeLog.txt for last
# slackpkg update

And without upgrade-all after update may be wrong (more fresh).

kjhambrick · 01-09-2022, 09:56 AM

All --

I like the way CentOS places the anaconda-ks.cfg file in /root/

Code:

[root@nuc10i7 ~]# ls -la /root/anaconda-ks.cfg

-rw-------. 1 root root 1482 Jan  8 10:31 /root/anaconda-ks.cfg

It tells me exactly when that particular system was installed ( this one was installed yesterday morning ).

I always copy the slackware tree from the USB Device that I used for my install to my local File System after installing so that I can keep my local repo up-to-date via rsync and move as few files over the internet as possible.

This is how I create /root/slackware-initial-install.txt

Code:

[ ! -d /mnt/usb ] && mkdir /mnt/usb

mount /dev/sdx /mnt/usb                  # watch out !  change for YOUR usb drive  !

# change slackware-current-64/ChangeLog.txt to slackware-current ( ? ) for 32-bit installs 

head -1 /mnt/usb/slackware-current-64/ChangeLog.txt > /root/slackware-initial-install.txt

# this step is optional ; I use it when I forget to run head ... immediately 

touch -r /var/log/packages/aaa_base-15.0-x86_64-1 /root/slackware-initial-install.txt

umount /mnt/usb

Now I have a file like this on my system:

Code:

# ls -la ~/slackware-initial-install.txt

-rw-r--r-- 1 root root 29 Nov  7 04:35 /root/slackware-initial-install.txt

# cat ~/slackware-initial-install.txt
Sat Nov  6 20:24:12 UTC 2021

This works for me because I don't use any Package Managers other than installpkg, ugradepkg and removepkg

HTH

-- kjh

iluvatar1 · 01-09-2022, 02:45 PM

Thanks for the tips. Yes, using slackpkg works until I do a simple slackpkg update and then the date in slackpkg Changelog is not related with the system installation (unless I also update the system).
I will explore the idea from @kjhambrick, maybe I can do that at the very installation or first boot in my packer setups. Thanks!