This topic contains 9 replies, has 7 voices, and was last updated by ile Dec 5-1:56 pm.
October 5, 2018 at 7:40 am #12365Forum Admin
antiX-17.2 (Helen Keller) released
This is primarily a point-release upgrade of antiX-17.1 (Heather Heyer) with a new L1TF/Foreshadow and Meltdown/Spectre patched kernel, various bugfixes, updated translations and some upgraded packages.
At the moment, iso files available from sourceforge
- This topic was modified 7 months, 3 weeks ago by anticapitalista.
Philosophers have interpreted the world in many ways; the point is to change it.October 5, 2018 at 8:08 am #12368Member
I am currently using antiX 17. See below:
$ inxi -S
Host: antix1 Kernel: 4.9.126-antix.1-486-smp i686 bits: 32 Desktop: IceWM 1.4.2
Distro: antiX-17_386-full Heather Heyer 24 October 2017
I would like to upgrade to 17.2 if it is not too complicated to do. Can it just be applied on top of antiX 17 or do I have to do a fresh install?
Please explain how to upgrade.
Dell Latitude D610 laptop (1.86 GHz, 2G RAM, 32 bit) - antiX 17October 5, 2018 at 8:34 am #12369Forum Admin
No fresh install needed.
You already have the latest kernel.
All you need to do is an
apt-get dist-upgradeand (if you want pulseaudio)
apt-get install pulseaudio pavucontrol
inxi will still show the version you started out with since we (the devs) thought it better to show what the user started with if/when seeking support.
- This reply was modified 7 months, 3 weeks ago by anticapitalista.
Philosophers have interpreted the world in many ways; the point is to change it.October 5, 2018 at 8:47 am #12371Forum Admin
Nope. No fresh install should be needed. My Chromebook is current as of yesterday with a dist-upgrade. When Anti uploads the 17.2 changes. I will get those also. Like you.
after I do a
sudo apt-get update
Let it finish
sudo apt-get dist-upgrade
Pretty simple. Easier than backing up everything and doing a reinstall. This chromebook is labled as AntiX 17. Because that is when I installed it.
But I am current so I am on 17.2
My Take is 17.2 isos are for new arrivals to the 17 iso. Without the need to do a massive upgrade online . Since I and you do ths gradually. We are cool.
Edit. Anti is quicker on the draw.
- This reply was modified 7 months, 3 weeks ago by rokytnji.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
Linux Registered User # 475019
How to Search for AntiX solutions to your problemsOctober 5, 2018 at 8:59 am #12373Member
This is easy.
Thanks for the help.
And, thanks for providing such a great linux distribution.
Dell Latitude D610 laptop (1.86 GHz, 2G RAM, 32 bit) - antiX 17October 6, 2018 at 5:45 am #12379Member
anticapitalista, Congratulations on another successful release — great to see antiX development still going strong — THANK YOU for all that you and your team do!
- (32-bit): IBM Thinkpad 600X (2000), IBM NetVista X41 (2002), IBM Thinkpad A31p (2003);
- (64-bit): Lenovo Thinkpads x61s (2008), x200 (2009), x301 (2009).October 6, 2018 at 7:37 pm #12381Member
I update every time I boot up. Today, I tried the dist-upgrade and there were no new apps available beyond the four I don’t want to update.
I assume that is normal?
stevesr0October 7, 2018 at 4:02 am #12382Member
Ho installato Antix-17.1 i386 base Heather Heyer 17 marzo 2018. Ho provato l’upgrade alla versione 17.2 seguendo le indicazioni fornite, ma, digitando inxi -S appare sempre la versione 17.1October 7, 2018 at 6:02 am #12383Forum Admin
A fully dist-upgraded antiX-17 and antiX-17.1 is the same as antiX-17.2 (provided you manually install the latest kernel and pulseaudio pavucontrol – needed for firefox to play audio ootb). inxi -S will still show your original install though.
Philosophers have interpreted the world in many ways; the point is to change it.December 5, 2018 at 1:56 pm #13913Member
Hello anticapitalista and everyone
fresh install 17.2 Helen Keller, thank you. on desktop previously “tubb” antiX16.
System: Host: onto2hk Kernel: 4.9.126-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: Fluxbox 1.3.5 dm: SLiM Distro: antiX-17.2_x64-full Helen Keller 4 October 2018 base: Debian GNU/Linux buster/sid Machine: Type: Desktop Mobo: ASUSTeK model: P5L8L-SE v: Rev 1.xx serial: <root required> BIOS: American Megatrends v: 0201 date: 10/09/2007 CPU: Topology: Single Core model: Intel Pentium 4 bits: 64 type: MT arch: Netburst Presler rev: 5 L2 cache: 2048 KiB bogomips: 13604 Speed: 3400 MHz min/max: N/A Core speeds (MHz): 1: 3400 2: 3400 Flags: acpi apic bts cid clflush cmov constant_tsc cx16 cx8 de ds_cpl dtes64 dts est fpu fxsr ht kaiser lahf_lm lm mca mce mmx monitor msr mtrr nopl nx pae pat pbe pdcm pebs pge pni pse pse36 sep ss sse sse2 syscall tm tm2 tsc vme xtpr Graphics: Device-1: Intel 82945G/GZ Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2772 Display: server: X.Org 1.20.3 driver: intel resolution: 1280x1024~60Hz OpenGL: renderer: Mesa DRI Intel 945G v: 1.4 Mesa 18.2.6 direct render: Yes Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: 2.3LK-NAPI port: e800 bus ID: 02:00.0 chip ID: 10ec:8168 Device-2: Realtek RTL8191SU 802.11n WLAN Adapter type: USB driver: r8712u bus ID: 1-3:2 chip ID: 0bda:8172 Drives: Local Storage: total: 153.39 GiB used: 5.13 GiB (3.3%) Sensors: Message: No sensors data was found. Is sensors configured? Info: Processes: 161 Uptime: 1h 34m Memory: 1.95 GiB used: 614.4 MiB (30.8%) Init: SysVinit v: N/A runlevel: 5 default: 5 Compilers: gcc: 8.2.0 alt: 6/8 Shell: bash v: 4.4.23 running in: lxterminal inxi: 3.0.25 herenot@onto2hk:~ $ sensors atk0110-acpi-0 Adapter: ACPI interface Vcore Voltage: +1.21 V (min = +0.85 V, max = +1.60 V) +3.3 Voltage: +3.33 V (min = +2.97 V, max = +3.63 V) +5 Voltage: +5.09 V (min = +4.50 V, max = +5.50 V) +12 Voltage: +12.04 V (min = +10.20 V, max = +13.80 V) CPU FAN Speed: 1088 RPM (min = 0 RPM, max = 7200 RPM) CHASSIS FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM) CPU Temperature: +42.5°C (high = +60.0°C, crit = +95.0°C) MB Temperature: +46.0°C (high = +45.0°C, crit = +95.0°C)
You must be logged in to reply to this topic.