antiX-forum

Viewing 15 results - 1 through 15 (of 57 total)

1 2 … 4 →

Author

Search Results
March 5, 2023 at 11:58 pm #101267

In reply to: What are you “here” with today?
Forum Admin
rokytnji
Been busy with blown down fence. Lulus < my shop pit bull> lives in the house by day and barks all night in her large pen attached to the shop all night.. This is while I am priming the steel ketchen sink. Still have to sand it for paint job.

Body is stove up < country slang for sore bones and muscles > So I am in the easy chair on my chromebook using battery.
```
harry@antix1:~
$ acpi -b
Battery 0: Discharging, 90%, 10:03:29 remaining
harry@antix1:~
$ inxi -p
Partition:
  ID-1: / size: 13.36 GiB used: 6.56 GiB (49.2%) fs: ext4 dev: /dev/mmcblk1p2
  ID-2: /boot/efi size: 252 MiB used: 274 KiB (0.1%) fs: vfat
    dev: /dev/mmcblk1p1
  ID-3: /media/harry/sda1-usb-PNY_USB_2.0_FD_A size: 29.95 GiB
    used: 13.69 GiB (45.7%) fs: vfat dev: /dev/sda1
  ID-4: swap-1 size: 768 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/mmcblk1p3
harry@antix1:~
$ sudo ps_mem.py; inxi -Fxz
[sudo] password for harry: 
 Private  +   Shared  =  RAM used	Program

152.0 KiB +  36.5 KiB = 188.5 KiB	seatd
212.0 KiB +  29.5 KiB = 241.5 KiB	gpm
216.0 KiB +  60.5 KiB = 276.5 KiB	rpc.idmapd
232.0 KiB +  57.5 KiB = 289.5 KiB	init
264.0 KiB +  71.5 KiB = 335.5 KiB	rtkit-daemon
316.0 KiB +  69.5 KiB = 385.5 KiB	cron
412.0 KiB +  34.5 KiB = 446.5 KiB	acpid
340.0 KiB + 111.5 KiB = 451.5 KiB	dbus-launch
340.0 KiB + 149.5 KiB = 489.5 KiB	icewm-session
440.0 KiB + 109.5 KiB = 549.5 KiB	rpcbind
448.0 KiB + 118.5 KiB = 566.5 KiB	rpc.statd
376.0 KiB + 221.5 KiB = 597.5 KiB	udevil
176.0 KiB + 554.0 KiB = 730.0 KiB	saned (2)
644.0 KiB + 408.5 KiB =   1.0 MiB	devmon
720.0 KiB + 384.0 KiB =   1.1 MiB	dbus-daemon (2)
804.0 KiB + 427.5 KiB =   1.2 MiB	desktop-session
812.0 KiB + 482.0 KiB =   1.3 MiB	getty (6)
  1.3 MiB +  89.5 KiB =   1.4 MiB	sshd
  1.4 MiB + 336.5 KiB =   1.7 MiB	ntpd
  1.3 MiB + 399.5 KiB =   1.7 MiB	sudo
  1.6 MiB + 197.5 KiB =   1.8 MiB	connmand
  1.7 MiB + 472.5 KiB =   2.1 MiB	bash
  2.0 MiB + 263.5 KiB =   2.3 MiB	bluetoothd
  3.1 MiB +  22.5 KiB =   3.2 MiB	haveged
  2.9 MiB + 414.5 KiB =   3.3 MiB	udevd
  3.7 MiB + 356.5 KiB =   4.0 MiB	cupsd
  3.7 MiB +   1.0 MiB =   4.7 MiB	conky
  5.1 MiB + 544.5 KiB =   5.6 MiB	wpa_supplicant
  4.0 MiB +   3.7 MiB =   7.7 MiB	volumeicon
  6.3 MiB +   2.1 MiB =   8.3 MiB	icewm
 12.3 MiB + 740.5 KiB =  13.0 MiB	slimski
 10.0 MiB +   4.8 MiB =  14.9 MiB	roxterm
 25.7 MiB +   5.0 MiB =  30.7 MiB	Xorg
445.9 MiB +  98.3 MiB = 544.3 MiB	firefox-esr (8)
---------------------------------
                        660.6 MiB
=================================
System:
  Kernel: 5.10.153-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc
    v: 10.2.1 Desktop: IceWM v: 3.3.1 Distro: antiX-22_x64-full Grup Yorum 18
    October 2022 base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Laptop System: GOOGLE product: Candy v: 1.0
    serial: <superuser required>
  Mobo: GOOGLE model: Candy v: 1.0 serial: <superuser required>
    UEFI: coreboot v: MrChromebox-4.18.1 date: 10/27/2022
Battery:
  ID-1: BAT0 charge: 37.3 Wh (89.9%) condition: 41.5/44.5 Wh (93.4%)
    volts: 12.4 min: 11.4 model: Samsung DELL XK status: discharging
CPU:
  Info: dual core model: Intel Celeron N2840 bits: 64 type: MCP
    arch: Silvermont rev: 8 cache: L1: 112 KiB L2: 1024 KiB
  Speed (MHz): avg: 1669 high: 2500 min/max: 500/2582 cores: 1: 2500 2: 839
    bogomips: 8666
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display
    driver: i915 v: kernel arch: Gen-7 bus-ID: 00:02.0
  Device-2: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-3:4
  Display: server: X.Org v: 1.20.11 driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: i965 gpu: i915 resolution: 1366x768~60Hz
  API: OpenGL v: 4.2 Mesa 20.3.5 renderer: Mesa DRI Intel HD Graphics (BYT)
    direct-render: Yes
Audio:
  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
  Sound API: ALSA v: k5.10.153-antix.1-amd64-smp running: yes
  Sound Server-1: PulseAudio v: 14.2 running: no
Network:
  Device-1: Intel Wireless 7260 driver: iwlwifi v: kernel bus-ID: 01:00.0
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-4:6
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1
    lmp-v: 4.0
Drives:
  Local Storage: total: 44.65 GiB used: 20.26 GiB (45.4%)
  ID-1: /dev/mmcblk1 vendor: Hynix model: HAG2e size: 14.68 GiB
  ID-2: /dev/sda type: USB vendor: PNY model: USB 2.0 FD size: 29.97 GiB
Partition:
  ID-1: / size: 13.36 GiB used: 6.56 GiB (49.2%) fs: ext4 dev: /dev/mmcblk1p2
  ID-2: /boot/efi size: 252 MiB used: 274 KiB (0.1%) fs: vfat
    dev: /dev/mmcblk1p1
Swap:
  ID-1: swap-1 type: partition size: 768 MiB used: 0 KiB (0.0%)
    dev: /dev/mmcblk1p3
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 135 Uptime: 15m Memory: 3.75 GiB used: 1017.5 MiB (26.5%)
  Init: SysVinit runlevel: 5 Compilers: gcc: 10.2.1 Packages: 1644 Shell: Bash
  v: 5.1.4 inxi: 3.3.25
harry@antix1:~
```
The day the winds blew my fence down. Telephone pole posts sunk 5 feet down with cement. Snapped the poles at the base.
It was a biblical day as far wind speeds and time duration of them.
Not sure yet if I have the energy to handle this .
Fun and games in West Texas.

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
February 18, 2023 at 9:38 am #99927

In reply to: antiX-23-alpha1-runit-full (64bit) for testing
Member
Robin
Interim report antiX 23 (6.1.10-antix.1-amd64-smp kernel):

Works stable, have run it with an uptime of 7 days. No memory leakage, no crashes, no other issues.

Installed now in this alpha release mostly all what I have installed by default on antiX, and all of it works out of the box on antiX 23. No stability issues, no crashes. Many of the programs are noticibly improved:
```
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install samba scsitools lsscsi pwgen dnsdiag dnsutils firefox-esr-l10n-de gaupol gstreamer1.0-x gimp gimp-data gimp-data-extras gimp-gap gimp-gutenprint gimp-help-de gimp-plugin-registry gutenprint-doc gutenprint-locales libtiff-opengl libtiff-tools socat iotop-c pdfarranger wkhtmltopdf traceroute translate-shell tree hexchat-plugins hexchat-python3 gucharmap libreoffice-help-de libreoffice-l10n-de git git-doc imagemagick libmagickcore-6.q16-6-extra imagemagick-doc inkscape poedit thunderbird-l10n-de fonts-lyx simplescreenrecorder fonts-campania fonts-oflb-euterpe fonts-rufscript pdftk xournal fonts-ipafont-gothic fonts-ipafont-mincho fonts-indic freepats lilypond lilypond-fonts lilypond-data lilypond-doc-pdf-de frescobaldi fluid-soundfont-gm fluid-soundfont-gs fluidsynth qsynth rosegarden audacity libasound2-plugins meld ttf-mscorefonts-installer fonts-liberation playonlinux libdrumstick-rt-backends vmpk sfarkxtc musescore-general-soundfont-lossless musescore3 linguist-qt6 qt6-translations-l10n linux-show-player solaar whysynth ghostess jackd qjackctl a2jmidid meterbridge jack-capture ardour ardour-video-timeline mencoder kdenlive breeze-icon-theme frei0r-plugins hydrogen hydrogen-data hydrogen-doc hydrogen-drumkits hydrogen-drumkits-effects
```
Here the results:
- geany () /operation: perfect /translation to de: perfect
- poedit (3.2.2-1+b2) /operation: perfect /translation to de: perfect
- meld (3.22.0-2) /operation: perfect /translation to de: perfect
- xournal (1:0.4.8.2016-7+b1) /operation: perfect /translation to de: perfect
- virtualbox (7.0.6-155176~Debian~bullseye) (installer package from virtualbox-site) / hints: needs two packages from debian bullseye by now / operation: perfect /translation to de: perfect
- scsitools (0.12-4)/operation: perfect /translation to de: none (English only)
- samba (2:4.17.5+dfsg-2.0nosystemd1) /operation: perfect /translation to de: none (English only)
- firefox (102.7.0esr-1) /operation: perfect /translation to de: perfect
- claws-mail (4.1.1-2+b1) /operation: perfect /translation to de: perfect
- thunderbird (1:102.7.1-1) / operation: perfect /translation to de: perfect
- aCSTV (1.09) /operation: perfect /translation to de: not needed
- antiXscreenshot2 (1.08d) /operation: perfect /translation to de: perfect
- ardour (1:7.2.0+ds0-2) /operation: perfect /translation to de: 95%
- musescore3 (3.2.3+dfsg2-16) /operation: perfect /translation to de: perfect
- qsynth (0.9.9-1) /operation: perfect /translation to de: perfect
- fluidsynth (2.3.1-1) /operation: /translation to de: none (English only)
- VMPK (0.8.8-1) /operation: perfect /translation to de: perfect
- rosegarden (1:22.12.1-1) /operation: perfect /translation to de: perfect
- frescobaldi (3.2+ds1-2) /operation: perfect /translation to de: 80%
- qjackctl (0.9.9-1) /operation: perfect /translation to de: perfect
- jack (5+nmu1) /operation: perfect /translation to de: perfect
- gaupol (1.11-1) /operation: perfect /translation to de: 90%
- gimp (2.10.32-1+b3) /operation: perfect /translation to de: perfect
- Inkscape (1.2.2-2+b1) /operation:perfect /translation to de: perfect
The following packages drew in elogind again:
— fluidsynth (this one was present in a de-eloginded version on antiX 21/22 already)
— poedit
— kdenlive

When trying to purge libelogind0 these programs will get removed from system, which is a pity.

Windows is like a submarine. Open a window and serious problems will start.
January 26, 2023 at 9:02 pm #98333

In reply to: Can I make my custom locked-down computer more “open”?
Moderator
Brian Masinick
I’ve probably said this AT LEAST a HUNDRED times over the course of my career.

Whatever computer systems, operating systems or mobile devices people obtain is THEIR choice. I’m very grateful for Linux software.

I used to primarily a UNIVAC 1110 mainframe computer as a computer science undergraduate student in the 1970s, but I did have a few opportunities to use other options – a true real-time laboratory computer, a Digital Equipment PDP-8 minicomputer, and just before I graduated, a Heathkit H8 microcomputer. This taught me that there are many different types of systems. Also in high school I was able to access a county wide minicomputer with dial in access to a very simple environment with BASIC, just enough to get an initial interest in computer systems.

My first professional job was at a large corporation writing short tools to analyze corporate telephony data, initially long distance phone traffic and later the emergence of a variety of software and hardware that changed the way we communicate with phones and computers.

This work allowed me to get into the use of PCs, minicomputer systems and exploring emerging network technology and it also gave me a chance to get involved with UNIX systems.

A few years later this background allowed me to move to Digital Equipment Corporation. At the time the company as a whole wasn’t very interested in UNIX systems but one major group of customers were: AT&T and the recently divested Bell Operating companies, all of whom were major Digital customers!

Our Bell Accounts Systems Engineering team worked closely with these important customers and made sure that UNIX System V worked with our hardware. Every time we created new hardware we’d write UNIX drivers to support them. Millions of dollars were involved when all of the companies were considered.

Within a decade UNIX became an important operating system for any major computer systems manufacturing company. Our company built one of the early (though not the first) 64 bit UNIX operating system. In the early days of 64 bit systems we felt that ours was one of the most completely 64 bit versions available because the other options were ports of earlier 32 bit systems and ours was a complete rewrite to take full advantage of the 64 bit address space.

That’s all academic because the window was short lived. In the nineties Linux already existed. Once the Beowulf project began even inexpensive 64 bit systems could be transformed into massively scalable supercomputer systems so DEC’s window was very short. Hewlett Packard bought both Digital and Tandem, plus Compaq Computer and went head to head with IBM for leadership.

Naturally with inexpensive systems available to scale greatly, Dell and others also joined the party…

A few people at Digital were interested in Linux. A guy named Jon “maddog” Hall was one of them. Jon and I used to meet near a microwave where we’d pop up a bag of popcorn and talk about ULTRIX, UNIX System V and later Linux. Jon left Digital and was a founding member of Linux International. Both of us could clearly see that Linux done right could work on big systems, small systems and mobile systems (like smartphones) that Telco companies were salivating about, looking for a profitable way to move on from their dinosaur networks!

I moved on too. I found Y2K (Year 2000) was a good way to get a few short term contract positions. For me it was also a way to move to financial services firms who also were moving from UNIX to Linux systems.

That’s what I turned toward later in my career: testing and migration of software to new technology from legacy systems. Once I did that I conceded my place to younger, more nimble young engineers.

--
Brian Masinick
January 4, 2023 at 1:04 am #96719

In reply to: Pipewire without systemd
Member
stevesr0
Hi olsztyn (and any one else reading these posts <g>),

This post includes a first draft of what is installed on my system as a guide to what might work on other antiX systems. Especially for others with a Sid install running Openbox. The script and EXPORTline in my /home/.profile file that seems to be necessary is described in an earlier post in this thread. Comments, questions and critiques appreciated.

stevesr0

————————————————————————————————————————————-

A. Looking at the files you posted,

1. We are both using openbox as a window manager

2. In my installed system, the /home/stevesr0/.desktop-session/desktop-session.conf file doesn’t exist (don’t know why). In your live system (/home/demo), my understanding is that the /etc/skel file would be copied to /home/demo. So functionally, those are the relevant ones in both our systems.

3. Puzzled how you are able to autostart LXpanel with XDG_AUTOSTART when LOAD_XDG_AUTOSTART=false.

4. I left out the differences in our /etc/xdg/openbox/autostart files. See my file under C.

————————————————————————————————————–

B. A basic set of packages required for Pipewire:

pipewire (metapackage)
pipewire-bin
pipewire-pulse
pipewire-alsa
pipewire-tests
libpipewire-0.3-0
libpipewire-o.3-common
libpipewire-0.3-modules
libpipewire-0.3-dev (not sure if this is “basic”)
gstreamer1.0-pipewire
wireplumber
libwireplumber-0.4-0
libwireplumber-0.4-dev (not sure if this is “basic”)
libspa-0.2-dev
libspa-0.2-modules

Optional:
pavucontrol

—————————————————————

C. Configuration.

1. /etc/alsa/conf.d/50-pipewire.conf
```
# Add a specific named PipeWire pcm

defaults.pipewire.server "pipewire-0"
defaults.pipewire.node "-1"
defaults.pipewire.exclusive false
defaults.pipewire.role ""
defaults.pipewire.rate 0
defaults.pipewire.format ""
defaults.pipewire.channels 0
defaults.pipewire.period_bytes 0
defaults.pipewire.buffer_bytes 0

pcm.pipewire {
	@args [ SERVER NODE EXCLUSIVE ROLE RATE FORMAT CHANNELS PERIOD_BYTES BUFFER_BYTES ]
	@args.SERVER {
		type string
		default {
			@func refer
			name defaults.pipewire.server
		}
	}
	@args.NODE {
		type string
		default {
			@func refer
			name defaults.pipewire.node
		}
	}
	@args.EXCLUSIVE {
		type integer
		default {
			@func refer
			name defaults.pipewire.exclusive
		}
	}
	@args.ROLE {
		type string
		default {
			@func refer
			name defaults.pipewire.role
		}
	}
	@args.RATE {
		type integer
		default {
			@func refer
			name defaults.pipewire.rate
		}
	}
	@args.FORMAT {
		type string
		default {
			@func refer
			name defaults.pipewire.format
		}
	}
	@args.CHANNELS {
		type integer
		default {
			@func refer
			name defaults.pipewire.channels
		}
	}
	@args.PERIOD_BYTES {
		type integer
		default {
			@func refer
			name defaults.pipewire.period_bytes
		}
	}
	@args.BUFFER_BYTES {
		type integer
		default {
			@func refer
			name defaults.pipewire.buffer_bytes
		}
	}

	type pipewire
	server $SERVER
	playback_node $NODE
	capture_node $NODE
	exclusive $EXCLUSIVE
	role $ROLE
	rate $RATE
	format $FORMAT
	channels $CHANNELS
	period_bytes $PERIOD_BYTES
	buffer_bytes $BUFFER_BYTES
	hint {
		show on
		description "PipeWire Sound Server"
	}
}

ctl.pipewire {
        @args.SERVER {
                type string
                default {
                        @func refer
                        name defaults.pipewire.server
                }
        }
        type pipewire
        server $SERVER
}
```
——————————————————————–

2. /etc/alsa/conf.d/99-pipewire-defaults.conf
```
pcm.!default {
    type pipewire
    playback_node "-1"
    capture_node  "-1"
    hint {
        show on
        description "Default ALSA Output (currently PipeWire Media Server)"
    }
}

ctl.!default {
    type pipewire
}
```
——————————————————————-

3./etc/xdg/openbox/autostart
#
# These things are run when an Openbox X Session is started.
# You may place a similar script in $HOME/.config/openbox/autostart
# to run user-specific things.
#

# If you want to use GNOME config tools…
#
#if test -x /usr/lib/x86_64-linux-gnu/gnome-settings-daemon >/dev/null; then
# /usr/lib/x86_64-linux-gnu/gnome-settings-daemon &
#elif which gnome-settings-daemon >/dev/null 2>&1; then
# gnome-settings-daemon &
#fi

# If you want to use XFCE config tools…
#
#xfce-mcs-manager &

# Start PipeWire in background as media server
pipewire &
sleep 2

Start WirePlumber as media session manager for PipeWire
wireplumber &
#sleep 1

# Start pipewire-pulse to enable use of pavucontrol
pipewire-pulse &

# Start tint2 as the taskbar for the Openbox session
tint2 &

# add polkit-agent helper to enable starting items on obmenu
/usr/lib/policykit-1/polkit-agent-helper-1 &

# Start lxterminal for the session
lxterminal

———————————————————————–

D. Unmodified configuration files (I believe…).

/usr/share/pipewire/client-rt.conf
/usr/share/pipewire/client.conf
/usr/share/pipewire/jack.conf
/usr/share/pipewire/minimal.conf
/usr/share/pipewire/pipewire-avb.conf
/usr/share/pipewire/pipewire-pulse.conf
/usr/share/pipewire/pipewire.conf
December 6, 2022 at 1:10 am #94977

In reply to: Pipewire without systemd
Member
stevesr0
Note: Started a thread regarding polkit and consolekit re: substitute for systemd.

Advised on the Devuan forum that the “missing” polkit libraries weren’t being used beyond the equivalent of oldstable Debian and that in another nosystemd distro (Alpine Linux) that startd was able to support Pipewire.

Will continue thrashing through the wilderness…

Perhaps an antiX-22 Sid with Pipewire live usb will just work. I will try and report back.

stevesr0
December 4, 2022 at 11:01 pm #94905

In reply to: What are you “here” with today?
Member
seaken64
Hi Brian,

I’ve been doing the same, going thru several of my distros and updating/upgrading. Been working with some of my older kit the last few days so mostly working with antiX right now.

The machine I am on the forum with now is a laptop I bought myself from a local Circuit City and came with Windows XP SP2. After XP upgraded to SP3 it slowed to a crawl and became a real dog. I experimented with Linux and ended up installing antiX-16 after upgrading the ram to the max this machine could use, 480MB. (512 installed but the video subsystem takes some of the ram and leaves this machine with only 480MB). AntiX-16 gave this machine new life. I also re-installed XP SP2 and froze it at SP2. XP worked better again but now I had found antiX and XP got left behind.

I installed antiX-17, then antiX-19 Full and Core, running them all in a multi-boot grub setup.

Today I upgraded antiX-17, then both antiX-19 Full and Core. But since antiX-17 is about to lose support I decided to try to upgrade to antiX-22 32-bit Full. I wasn’t sure it would work on this old machine since it has an old VIA S3 graphics chip. But when I booted the Live USB it worked fine. The graphics were setup with the OpenChrome drivers automatically. The Kernel is 4.9.0-326. The WiFi was also supported OOTB. All I had to do was set it up with Ceni and my password for the LAN router. I was shocked that it works just as well as antiX-17 and antiX-19.

This has always been one of my favorite machines. It is larger than a Netbook but lighter and smaller than other laptops I had at the time. (I had one Dell Inspiron that was way too heavy to be a “laptop”). So, I ma happy this machine is working so well with antiX-22. Of course, with only 480MB RAM I can only do one thing at a time. But I am browsing with SeaMonkey and on the forum right now with this forum message. Pretty good for this single-core laptop from 2006.

Seaken64
```
 inxi -zv7
System:
  Kernel: 4.9.0-326-antix.1-486-smp arch: i686 bits: 32 compiler: gcc
    v: 10.2.1 Desktop: IceWM v: 3.2.2 dm: slimski v: 1.5.0
    Distro: antiX-22_386-full Grup Yorum 18 October 2022
    base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Portable System: Gateway product: MX3210 v: 73.03
    serial: <superuser required> Chassis: type: 8 serial: <superuser required>
  Mobo: Gateway model: N/A v: Rev1.73.03 serial: <superuser required>
    BIOS: Phoenix v: 73.03 date: 01/06/2006
Battery:
  ID-1: BAT0 charge: 20.9 Wh (99.1%) condition: 21.1/48.8 Wh (43.2%)
    volts: 12.6 min: 11.1 model: Gateway W32044L type: Unknown serial: <filter>
    status: charging
Memory:
  RAM: total: 429 MiB used: 283 MiB (66.0%)
  RAM Report:
    permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: single core model: Intel Celeron M bits: 32 arch: M Dothan rev: 8
    cache: 1024 KiB note: check
  Speed (MHz): 1397 min/max: N/A core: 1: 1397 bogomips: 2793
  Flags: acpi apic bts clflush cmov cx8 de dts fpu fxsr mca mce mmx msr
    mtrr pae pbe pge pse sep ss sse sse2 tm tsc vme
Graphics:
  Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro]
    vendor: Gateway driver: N/A bus-ID: 01:00.0 chip-ID: 1106:3344
    class-ID: 0300
  Display: server: X.Org v: 1.20.11 driver: X: loaded: openchrome
    unloaded: fbdev,modesetting,vesa gpu: N/A display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1280x768 s-dpi: 96 s-size: 338x203mm (13.31x7.99")
    s-diag: 394mm (15.52")
  Monitor-1: FP-1 res: 1280x768 hz: 60 size: N/A modes: N/A
  OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.5
    compat-v: 3.1 direct render: Yes
Audio:
  Device-1: VIA VT8233/A/8235/8237 AC97 Audio vendor: Gateway
    driver: snd_via82xx v: kernel bus-ID: 00:11.5 chip-ID: 1106:3059
    class-ID: 0401
  Sound Server-1: ALSA v: k4.9.0-326-antix.1-486-smp running: yes
Network:
  Device-1: Broadcom BCM4318 [AirForce One 54g] 802.11g Wireless LAN
    driver: b43-pci-bridge v: N/A bus-ID: 00:0e.0 chip-ID: 14e4:4318
    class-ID: 0280
  Device-2: VIA VT6102/VT6103 [Rhine-II] vendor: Gateway driver: via-rhine
    v: N/A port: 1800 bus-ID: 00:12.0 chip-ID: 1106:3065 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  IF-ID-1: wlan0 state: up mac: <filter>
  IP v4: <filter> type: dynamic scope: global broadcast: <filter>
  IP v6: <filter> scope: link
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 37.26 GiB used: 4.37 GiB (11.7%)
  ID-1: /dev/sda vendor: Hitachi model: HTS424040M9AT00 size: 37.26 GiB
    speed: <unknown> type: N/A serial: <filter> rev: A71A scheme: MBR
  Optical-1: /dev/sr0 vendor: TSSTcorp model: CDW/DVD TS-L462C rev: GA03
    dev-links: cdrom,cdrw,dvd
  Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw
    state: running
Partition:
  ID-1: / size: 7.68 GiB used: 4.33 GiB (56.4%) fs: ext4 dev: /dev/sda6
    label: rootantiX22 uuid: 948c89b0-b5a4-45cd-a83e-86e153c0609d
Swap:
  ID-1: swap-1 type: partition size: 896 MiB used: 40.9 MiB (4.6%)
    priority: -1 dev: /dev/sda5 label: N/A
    uuid: 5686fe9c-3557-4dba-8da4-9de196cbd48d
Unmounted:
  ID-1: /dev/sda1 size: 14.7 GiB fs: ntfs label: N/A uuid: B8CC161FF4974A14
  ID-2: /dev/sda2 size: 1 KiB fs: <superuser required> label: N/A uuid: N/A
  ID-3: /dev/sda3 size: 5.94 GiB fs: ext4 label: antiX-Frugal
    uuid: d1491443-0a8f-4633-ac5a-301bc3de196f
  ID-4: /dev/sda7 size: 7.84 GiB fs: ext4 label: rootantiX19
    uuid: 663c72e5-72d4-488e-a583-7f30e0b9b552
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 8 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 2-0:1 info: Full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
  Hub-3: 3-0:1 info: Full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
  Hub-4: 4-0:1 info: Full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
  Hub-5: 5-0:1 info: Full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
Sensors:
  System Temperatures: cpu: 63.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 132 Uptime: 1h 31m wakeups: 3 Init: SysVinit v: 2.96 runlevel: 5
  default: 5 Compilers: gcc: 10.2.1 alt: 10 Packages: apt: 1586 Shell: Bash
  v: 5.1.4 running-in: roxterm inxi: 3.3.19
```
November 18, 2022 at 2:05 am #93451

In reply to: Troubles with Broadcom WiFi BCM4318
Member
madibi
Dear aspire3023,
I experimented your issue in December 2021 when installing antiX on an Acer from 2007, and I found that the solution proposed in the top of the forum was optimal for me.
The same issue was detected in a lot of Debian derivatives such as Mx, Q4OS, Sparkly, etc and NOT on the *buntus => the issue lies in Debian and not in antiX.
The forum solution worked both on antiX 19 and in 21.
In some cases, with antiX 22, some problems with Connman are reported, and @Brian Masinick in the previous post pointed you to a solution.

As a 1st step: I’d search using a live with 21, to verify if the forum solution works.
Don’t forget to do : “sudo apt update” before following the 6 steps.
In this case you need another way to be connected to internet: in case your internet connection is done with another wifi dongle or an eth cable, you can immediately test if the forum solution is good for you.
In case your internet connection is done using your mobile phone, usb connection, unfortunately you should reboot your Acer in order to see if your b43 now works. In this case you should make your live try, using the root persistence.

As a 2nd step: now you know if your b43 is working or not, if it works now you can try on antiX 22 as now you will have located your problem.

Good luck 🙂
m

EDIT
A member of the forum named @lefti, pointed out another solution that you can find here:
https://www.antixforum.com/forums/topic/split-fix-broadcom-b43-problems-discussion/ ==> see feb the 1st
https://www.antixforum.com/forums/topic/split-linux-live-kit/page/2/ ==> see jan the 31st
- This reply was modified 5 months, 3 weeks ago by madibi.
November 6, 2022 at 5:42 pm #92517

In reply to: Hello All From UK – HP G60 3GiB RAM 2008
Member
banned
Hey All – thank you for all you well intentioned input – all of it is very useful to determine which options suit my simple requirements. For example Ft10-Trans is highly recommended so I followed the links kindly given to the gitlab readme and was horrified to see the screenshot of a Win10 looking Linux so full of clutter – the exact opposite of what I want. It came as no surprise to see confirmation of my guess as I zoomed in on the bottom right corner – see my screen clip below – to find CPUs at 50% with memory used 1142 MiB RAM. Yes folks, real figures OMG 🙂

https://gitlab.com/antix-contribs/ft10-transformation/-/raw/main/FT10-tilled-menu-with-visual-effects.jpg

As you can see with LXDE using HALF of that RAM, I have got Gimp open editing a logo, AbiWord open with document, printers, Web-Browser with second tab actually playing an embedded video. If you look at the live performance monitor it is showing CPU at 18% and Memory at 7% of the Dell’s 8GiB RAM = 560MiB. This is efficiency IMHO. Anyone can easily replicate this tiny experiment and post results 🙂

https://www.antixforum.com/wp-content/uploads/2022/11/minimax-RAMused-04.png

PCManFM has a Trash Can – also I have no need for calendar, clocks, cloud, debinstaller, maps, news, translate or weather to give my location and other personal data to! I can go to the best sites for the best info with a tap on my GrapheneOS phone or with one click browser bookmark within AntiX-22 LXDE. For example the Met Office gives out official weather warnings – so their forecast page is one of my browser bookmarks – light, simple and accurate!

You may understand when I recount the purchase of my used Dell Latitude E6420 i7 8GB RAM laptop from a small local shop. I said that I would buy it if they would install Linux alongside Win10. It came with Ubuntu 17 or 18 installed for me and after buying an ubuntu guide magazine I became used to the system. After six months Win10 had not been used at all so it got wiped – Hooray 🙂
This experience allowed me to rescue my love-hate HP G60 laptop running dreadful Vista Home Premium which had lost support and almost ground to a halt. Awful – yet after installing Trisquel v7 it was so fast and reliable I was over the moon 🙂 So much so I bought her a new battery and replaced the HDD with new SSD storage.

Just for the fun of it, against all advice, I installed Trisquel-mini LXDE onto the Dell and loaded every heavy app I could think of to try and break it – it ran faultlessly until v10 so then I installed Manjaro, then Endeavour amongst many, ending up with the very polished professional free version of Zorin OS Gnome mainly so that I could watch digital TV reliably whilst in our Mobile-Home RV. ZorinOS does freeze and lock up occasionally requiring you to crash out – power off.

Now that we have that tiny Roku Express thingy that converts any old TV, the old Dell is now an experimental laptop once again 🙂 as thanks to those AntiX-22 devs I now have a very stable HP G60 laptop as the daily kit along with GrapheneOS Pixel 3a phone. As you guys know a little tweaking and slimming will make the HP even better – I’m so happy right now – I can chill and play with the Dell at my leisure 🙂 (OAP 72) old age pensioner! Never liked ubuntu with Win10 only a faded distant memory or should I say; nightmare Vista OMG 🙂
Hey; I know you guys are WM pros and love those file managers. I have dealt with Roxy so I once again fired up zzzFM which looks like it was influenced by LXDE’s PCManFM with same shortcuts – cool, light and fast – but just tried to shift select a group of folders as I would normally, only to find that it just opens the first folder selected. Okay there may be a double click setting somewhere?…

ModdIt wrote:

PCmanFM seems unmaintained since last release February 19, 2021

…. so if it ain’t broke no need to fix it – PCManFM does everything efficiently straight out of the box 🙂 Why would I want anything else?
- This reply was modified 6 months ago by banned.
- This reply was modified 6 months ago by banned.
Attachments:
1. Ft10-High-CPUMem-01.jpg
2. minimax-RAMused-04-1.png
September 15, 2022 at 3:34 pm #89021

In reply to: AntiX on Asus eee PC
Member
olsztyn
rokytnji wrote:

Base iso is what I* ran eeepc on eeepc 701sd 4 gig drive back when I had a eeepc.

Indeed. I you try to traditionally install system then there is not much space you have to play with. Just 4GB. However if you install antiX as Live on it then it easily fits the Full version and more. That it because antiX Live all OS fits in one linuxfs file, which is compressed. The entire antiX Full version fits in under 3GB.
I have been routinely setting up antiX Full also on 4GB USB sticks, to have dedicated systems, such as one that currently runs full time in the kitchen to play my wife’s music service and browse Internet…
- This reply was modified 7 months, 3 weeks ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
July 9, 2022 at 2:51 pm #85835

Topic: Updated Debian 11: 11.4 released

in forum Other Distros
Moderator
Brian Masinick
I received an Email with the following update:

Updated Debian 11: 11.4 released

————————————————————————
The Debian Project https://www.debian.org/
Updated Debian 11: 11.4 released press@debian.org
July 9th, 2022 https://www.debian.org/News/2022/20220709
————————————————————————

The Debian project is pleased to announce the fourth update of its
stable distribution Debian 11 (codename “bullseye”). This point release
mainly adds corrections for security issues, along with a few
adjustments for serious problems. Security advisories have already been
published separately and are referenced where available.

Please note that the point release does not constitute a new version of
Debian 11 but only updates some of the packages included. There is no
need to throw away old “bullseye” media. After installation, packages
can be upgraded to the current versions using an up-to-date Debian
mirror.

Those who frequently install updates from security.debian.org won’t have
to update many packages, and most such updates are included in the point
release.

New installation images will be available soon at the regular locations.

Upgrading an existing installation to this revision can be achieved by
pointing the package management system at one of Debian’s many HTTP
mirrors. A comprehensive list of mirrors is available at:

https://www.debian.org/mirror/list

Miscellaneous Bugfixes
———————-

This stable update adds a few important corrections to the following
packages:

+—————————+—————————————–+
| Package | Reason |
+—————————+—————————————–+
| apache2 [1] | New upstream stable release; fix HTTP |
| | request smuggling issue [CVE-2022- |
| | 26377], out-of-bounds read issues |
| | [CVE-2022-28330 CVE-2022-28614 |
| | CVE-2022-28615], denial of service |
| | issues [CVE-2022-29404 CVE-2022-30522], |
| | possible out-of-bounds read issue |
| | [CVE-2022-30556], possible IP-based |
| | authentication bypass issue [CVE-2022- |
| | 31813] |
| | |
| base-files [2] | Update /etc/debian_version for the 11.4 |
| | point release |
| | |
| bash [3] | Fix 1-byte buffer overflow read, |
| | causing corrupted multibyte characters |
| | in command substitutions |
| | |
| clamav [4] | New upstream stable release; security |
| | fixes [CVE-2022-20770 CVE-2022-20771 |
| | CVE-2022-20785 CVE-2022-20792 CVE-2022- |
| | 20796] |
| | |
| clementine [5] | Add missing dependency on libqt5sql5- |
| | sqlite |
| | |
| composer [6] | Fix code injection issue [CVE-2022- |
| | 24828]; update GitHub token pattern |
| | |
| cyrus-imapd [7] | Ensure that all mailboxes have a |
| | “uniqueid” field, fixing upgrades to |
| | version 3.6 |
| | |
| dbus-broker [8] | Fix buffer overflow issue [CVE-2022- |
| | 31212] |
| | |
| debian-edu-config [9] | Accept mail from the local network sent |
| | to root@; only create |
| | Kerberos host and service principals if |
| | they don’t yet exist; ensure libsss- |
| | sudo is installed on Roaming |
| | Workstations; fix naming and visibility |
| | of print queues; support krb5i on |
| | Diskless Workstations; squid: prefer |
| | DNSv4 lookups over DNSv6 |
| | |
| debian-installer [10] | Rebuild against proposed-updates; |
| | increase Linux kernel ABI to 16; |
| | reinstate some armel netboot targets |
| | (openrd) |
| | |
| debian-installer-netboot- | Rebuild against proposed-updates; |
| images [11] | increase Linux kernel ABI to 16; |
| | reinstate some armel netboot targets |
| | (openrd) |
| | |
| distro-info-data [12] | Add Ubuntu 22.10, Kinetic Kudu |
| | |
| docker.io [13] | Order docker.service after |
| | containerd.service to fix shutdown of |
| | containers; explicitly pass the |
| | containerd socket path to dockerd to |
| | make sure it doesn’t start containerd |
| | on its own |
| | |
| dpkg [14] | dpkg-deb: Fix unexpected end of file |
| | conditions on .deb extract; libdpkg: Do |
| | not restrict source:* virtual fields to |
| | installed packages; |
| | Dpkg::Source::Package::V2: Always fix |
| | the permissions for upstream tarballs |
| | (regression from DSA-5147-1] |
| | |
| freetype [15] | Fix buffer overflow issue [CVE-2022- |
| | 27404]; fix crashes [CVE-2022-27405 |
| | CVE-2022-27406] |
| | |
| fribidi [16] | Fix buffer overflow issues [CVE-2022- |
| | 25308 CVE-2022-25309]; fix crash |
| | [CVE-2022-25310] |
| | |
| ganeti [17] | New upstream release; fix several |
| | upgrade issues; fix live migration with |
| | QEMU 4 and “security_model” of |
| | “user” or “pool” |
| | |
| geeqie [18] | Fix Ctrl click inside of a block |
| | selection |
| | |
| gnutls28 [19] | Fix SSSE3 SHA384 miscalculation; fix |
| | null pointer deference issue [CVE-2021- |
| | 4209] |
| | |
| golang-github- | Fix null pointer dereference caused by |
| russellhaering- | crafted XML signatures [CVE-2020-7711] |
| goxmldsig [20] | |
| | |
| grunt [21] | Fix path traversal issue [CVE-2022- |
| | 0436] |
| | |
| hdmi2usb-mode-switch [22] | udev: Add a suffix to /dev/video device |
| | nodes to disambiguate them; move udev |
| | rules to priority 70, to come after 60- |
| | persistent-v4l.rules |
| | |
| hexchat [23] | Add missing dependency on python3-cffi- |
| | backend |
| | |
| htmldoc [24] | Fix infinite loop [CVE-2022-24191], |
| | integer overflow issues [CVE-2022- |
| | 27114] and heap buffer overflow issue |
| | [CVE-2022-28085] |
| | |
| knot-resolver [25] | Fix possible assertion failure in NSEC3 |
| | edge-case [CVE-2021-40083] |
| | |
| libapache2-mod-auth- | New upstream stable release; fix open |
| openidc [26] | redirect issue [CVE-2021-39191]; fix |
| | crash on reload / restart |
| | |
| libintl-perl [27] | Really install gettext_xs.pm |
| | |
| libsdl2 [28] | Avoid out-of-bounds read while loading |
| | malformed BMP file [CVE-2021-33657], |
| | and during YUV to RGB conversion |
| | |
| libtgowt [29] | New upstream stable release, to support |
| | newer telegram-desktop |
| | |
| linux [30] | New upstream stable release; increase |
| | ABI to 16 |
| | |
| linux-signed-amd64 [31] | New upstream stable release; increase |
| | ABI to 16 |
| | |
| linux-signed-arm64 [32] | New upstream stable release; increase |
| | ABI to 16 |
| | |
| linux-signed-i386 [33] | New upstream stable release; increase |
| | ABI to 16 |
| | |
| logrotate [34] | Skip locking if state file is world- |
| | readable [CVE-2022-1348]; make |
| | configuration parsing stricter in order |
| | to avoid parsing foreign files such as |
| | core dumps |
| | |
| lxc [35] | Update default GPG key server, fixing |
| | creating of containers using the |
| | “download” template |
| | |
| minidlna [36] | Validate HTTP requests to protect |
| | against DNS rebinding attacks |
| | [CVE-2022-26505] |
| | |
| mutt [37] | Fix uudecode buffer overflow issue |
| | [CVE-2022-1328] |
| | |
| nano [38] | Several bug fixes, including fixes for |
| | crashes |
| | |
| needrestart [39] | Make cgroup detection for services and |
| | user sessions cgroup v2 aware |
| | |
| network-manager [40] | New upstream stable release |
| | |
| nginx [41] | Fix crash when libnginx-mod-http-lua is |
| | loaded and init_worker_by_lua* is used; |
| | mitigate application layer protocol |
| | content confusion attack in the Mail |
| | module [CVE-2021-3618] |
| | |
| node-ejs [42] | Fix server-side template injection |
| | issue [CVE-2022-29078] |
| | |
| node-eventsource [43] | Strip sensitive headers on redirect to |
| | different origin [CVE-2022-1650] |
| | |
| node-got [44] | Don’t allow redirection to Unix socket |
| | [CVE-2022-33987] |
| | |
| node-mermaid [45] | Fix cross-site scripting issues |
| | [CVE-2021-23648 CVE-2021-43861] |
| | |
| node-minimist [46] | Fix prototype pollution issue |
| | [CVE-2021-44906] |
| | |
| node-moment [47] | Fix path traversal issue [CVE-2022- |
| | 24785] |
| | |
| node-node-forge [48] | Fix signature verification issues |
| | [CVE-2022-24771 CVE-2022-24772 |
| | CVE-2022-24773] |
| | |
| node-raw-body [49] | Fix potential denial of service issue |
| | in node-express, by using node-iconv- |
| | lite rather than node-iconv |
| | |
| node-sqlite3 [50] | Fix denial of service issue [CVE-2022- |
| | 21227] |
| | |
| node-url-parse [51] | Fix authentication bypass issues |
| | [CVE-2022-0686 CVE-2022-0691] |
| | |
| nvidia-cuda-toolkit [52] | Use OpenJDK8 snapshots for amd64 and |
| | ppc64el; check usability of the java |
| | binary; nsight-compute: Move the |
| | ‘sections’ folder to a multiarch |
| | location; fix nvidia-openjdk-8-jre |
| | version ordering |
| | |
| nvidia-graphics- | New upstream release; switch to |
| drivers [53] | upstream 470 tree; fix denial of |
| | service issues [CVE-2022-21813 |
| | CVE-2022-21814]; fix out-of-bounds |
| | write issue [CVE-2022-28181], out-of- |
| | bounds read issue [CVE-2022-28183], |
| | denial of service issues [CVE-2022- |
| | 28184 CVE-2022-28191 CVE-2022-28192] |
| | |
| nvidia-graphics-drivers- | New upstream release; fix out-of-bound |
| legacy-390xx [54] | write issues [CVE-2022-28181 CVE-2022- |
| | 28185] |
| | |
| nvidia-graphics-drivers- | New upstream stable release |
| tesla-418 [55] | |
| | |
| nvidia-graphics-drivers- | New upstream stable release; fix out- |
| tesla-450 [56] | of-bounds write issues [CVE-2022-28181 |
| | CVE-2022-28185], denial of service |
| | issue [CVE-2022-28192] |
| | |
| nvidia-graphics-drivers- | New upstream stable release |
| tesla-460 [57] | |
| | |
| nvidia-graphics-drivers- | New package, switching Tesla support to |
| tesla-470 [58] | upstream 470 tree; fix out-of-bounds |
| | write issue [CVE-2022-28181], out-of- |
| | bounds read issue [CVE-2022-28183], |
| | denial of service issues [CVE-2022- |
| | 28184 CVE-2022-28191 CVE-2022-28192] |
| | |
| nvidia-persistenced [59] | New upstream release; switch to |
| | upstream 470 tree |
| | |
| nvidia-settings [60] | New upstream release; switch to |
| | upstream 470 tree |
| | |
| nvidia-settings- | New package, switching Tesla support to |
| tesla-470 [61] | upstream 470 tree |
| | |
| nvidia-xconfig [62] | New upstream release |
| | |
| openssh [63] | seccomp: add pselect6_time64 syscall on |
| | 32-bit architectures |
| | |
| orca [64] | Fix usage with webkitgtk 2.36 |
| | |
| php-guzzlehttp-psr7 [65] | Fix improper header parsing [CVE-2022- |
| | 24775] |
| | |
| phpmyadmin [66] | Fix some SQL queries generating a |
| | server error |
| | |
| postfix [67] | New upstream stable release; do not |
| | override user set default_transport in |
| | postinst; if-up.d: do not error out if |
| | postfix can’t send mail yet |
| | |
| procmail [68] | Fix null pointer dereference |
| | |
| python-scrapy [69] | Don’t send authentication data with all |
| | requests [CVE-2021-41125]; don’t expose |
| | cookies cross-domain when redirecting |
| | [CVE-2022-0577] |
| | |
| ruby-net-ssh [70] | Fix authentication against systems |
| | using OpenSSH 8.8 |
| | |
| runc [71] | Honour seccomp defaultErrnoRet; do not |
| | set inheritable capabilities [CVE-2022- |
| | 29162] |
| | |
| samba [72] | Fix winbind start failure when “allow |
| | trusted domains = no” is used; fix MIT |
| | Kerberos authentication; fix share |
| | escape issue via mkdir race condition |
| | [CVE-2021-43566]; fix possible serious |
| | data corruption issue due to Windows |
| | client cache poisoning; fix |
| | installation on non-systemd systems |
| | |
| tcpdump [73] | Update AppArmor profile to allow access |
| | to *.cap files, and handle numerical |
| | suffix in filenames added by -W |
| | |
| telegram-desktop [74] | New upstream stable release, restoring |
| | functionality |
| | |
| tigervnc [75] | Fix GNOME desktop start up when using |
| | tigervncserver@.service; fix colour |
| | display when vncviewer and X11 server |
| | use different endianness |
| | |
| twisted [76] | Fix information disclosure issue with |
| | cross-domain redirects [CVE-2022- |
| | 21712], denial of service issue during |
| | SSH handshakes [CVE-2022-21716], HTTP |
| | request smuggling issues [CVE-2022- |
| | 24801] |
| | |
| tzdata [77] | Update timezone data for Palestine; |
| | update leap second list |
| | |
| ublock-origin [78] | New upstream stable release |
| | |
| unrar-nonfree [79] | Fix directory traversal issue |
| | [CVE-2022-30333] |
| | |
| usb.ids [80] | New upstream release; update included |
| | data |
| | |
| wireless-regdb [81] | New upstream release; remove diversion |
| | added by the installer, ensuring that |
| | files from the package are used |
| | |
+—————————+—————————————–+

1: https://packages.debian.org/src:apache2
2: https://packages.debian.org/src:base-files
3: https://packages.debian.org/src:bash
4: https://packages.debian.org/src:clamav
5: https://packages.debian.org/src:clementine
6: https://packages.debian.org/src:composer
7: https://packages.debian.org/src:cyrus-imapd
8: https://packages.debian.org/src:dbus-broker
9: https://packages.debian.org/src:debian-edu-config
10: https://packages.debian.org/src:debian-installer
11: https://packages.debian.org/src:debian-installer-netboot-images
12: https://packages.debian.org/src:distro-info-data
13: https://packages.debian.org/src:docker.io
14: https://packages.debian.org/src:dpkg
15: https://packages.debian.org/src:freetype
16: https://packages.debian.org/src:fribidi
17: https://packages.debian.org/src:ganeti
18: https://packages.debian.org/src:geeqie
19: https://packages.debian.org/src:gnutls28
20: https://packages.debian.org/src:golang-github-russellhaering-goxmldsig
21: https://packages.debian.org/src:grunt
22: https://packages.debian.org/src:hdmi2usb-mode-switch
23: https://packages.debian.org/src:hexchat
24: https://packages.debian.org/src:htmldoc
25: https://packages.debian.org/src:knot-resolver
26: https://packages.debian.org/src:libapache2-mod-auth-openidc
27: https://packages.debian.org/src:libintl-perl
28: https://packages.debian.org/src:libsdl2
29: https://packages.debian.org/src:libtgowt
30: https://packages.debian.org/src:linux
31: https://packages.debian.org/src:linux-signed-amd64
32: https://packages.debian.org/src:linux-signed-arm64
33: https://packages.debian.org/src:linux-signed-i386
34: https://packages.debian.org/src:logrotate
35: https://packages.debian.org/src:lxc
36: https://packages.debian.org/src:minidlna
37: https://packages.debian.org/src:mutt
38: https://packages.debian.org/src:nano
39: https://packages.debian.org/src:needrestart
40: https://packages.debian.org/src:network-manager
41: https://packages.debian.org/src:nginx
42: https://packages.debian.org/src:node-ejs
43: https://packages.debian.org/src:node-eventsource
44: https://packages.debian.org/src:node-got
45: https://packages.debian.org/src:node-mermaid
46: https://packages.debian.org/src:node-minimist
47: https://packages.debian.org/src:node-moment
48: https://packages.debian.org/src:node-node-forge
49: https://packages.debian.org/src:node-raw-body
50: https://packages.debian.org/src:node-sqlite3
51: https://packages.debian.org/src:node-url-parse
52: https://packages.debian.org/src:nvidia-cuda-toolkit
53: https://packages.debian.org/src:nvidia-graphics-drivers
54: https://packages.debian.org/src:nvidia-graphics-drivers-legacy-390xx
55: https://packages.debian.org/src:nvidia-graphics-drivers-tesla-418
56: https://packages.debian.org/src:nvidia-graphics-drivers-tesla-450
57: https://packages.debian.org/src:nvidia-graphics-drivers-tesla-460
58: https://packages.debian.org/src:nvidia-graphics-drivers-tesla-470
59: https://packages.debian.org/src:nvidia-persistenced
60: https://packages.debian.org/src:nvidia-settings
61: https://packages.debian.org/src:nvidia-settings-tesla-470
62: https://packages.debian.org/src:nvidia-xconfig
63: https://packages.debian.org/src:openssh
64: https://packages.debian.org/src:orca
65: https://packages.debian.org/src:php-guzzlehttp-psr7
66: https://packages.debian.org/src:phpmyadmin
67: https://packages.debian.org/src:postfix
68: https://packages.debian.org/src:procmail
69: https://packages.debian.org/src:python-scrapy
70: https://packages.debian.org/src:ruby-net-ssh
71: https://packages.debian.org/src:runc
72: https://packages.debian.org/src:samba
73: https://packages.debian.org/src:tcpdump
74: https://packages.debian.org/src:telegram-desktop
75: https://packages.debian.org/src:tigervnc
76: https://packages.debian.org/src:twisted
77: https://packages.debian.org/src:tzdata
78: https://packages.debian.org/src:ublock-origin
79: https://packages.debian.org/src:unrar-nonfree
80: https://packages.debian.org/src:usb.ids
81: https://packages.debian.org/src:wireless-regdb

Security Updates
—————-

This revision adds the following security updates to the stable release.
The Security Team has already released an advisory for each of these
updates:

+—————-+————————–+
| Advisory ID | Package |
+—————-+————————–+
| DSA-4999 [82] | asterisk [83] |
| | |
| DSA-5026 [84] | firefox-esr [85] |
| | |
| DSA-5034 [86] | thunderbird [87] |
| | |
| DSA-5044 [88] | firefox-esr [89] |
| | |
| DSA-5045 [90] | thunderbird [91] |
| | |
| DSA-5069 [92] | firefox-esr [93] |
| | |
| DSA-5074 [94] | thunderbird [95] |
| | |
| DSA-5086 [96] | thunderbird [97] |
| | |
| DSA-5090 [98] | firefox-esr [99] |
| | |
| DSA-5094 [100] | thunderbird [101] |
| | |
| DSA-5097 [102] | firefox-esr [103] |
| | |
| DSA-5106 [104] | thunderbird [105] |
| | |
| DSA-5107 [106] | php-twig [107] |
| | |
| DSA-5108 [108] | tiff [109] |
| | |
| DSA-5110 [110] | chromium [111] |
| | |
| DSA-5111 [112] | zlib [113] |
| | |
| DSA-5112 [114] | chromium [115] |
| | |
| DSA-5113 [116] | firefox-esr [117] |
| | |
| DSA-5114 [118] | chromium [119] |
| | |
| DSA-5115 [120] | webkit2gtk [121] |
| | |
| DSA-5116 [122] | wpewebkit [123] |
| | |
| DSA-5117 [124] | xen [125] |
| | |
| DSA-5118 [126] | thunderbird [127] |
| | |
| DSA-5119 [128] | subversion [129] |
| | |
| DSA-5120 [130] | chromium [131] |
| | |
| DSA-5121 [132] | chromium [133] |
| | |
| DSA-5122 [134] | gzip [135] |
| | |
| DSA-5123 [136] | xz-utils [137] |
| | |
| DSA-5124 [138] | ffmpeg [139] |
| | |
| DSA-5125 [140] | chromium [141] |
| | |
| DSA-5127 [142] | linux-signed-amd64 [143] |
| | |
| DSA-5127 [144] | linux-signed-arm64 [145] |
| | |
| DSA-5127 [146] | linux-signed-i386 [147] |
| | |
| DSA-5127 [148] | linux [149] |
| | |
| DSA-5128 [150] | openjdk-17 [151] |
| | |
| DSA-5129 [152] | firefox-esr [153] |
| | |
| DSA-5130 [154] | dpdk [155] |
| | |
| DSA-5131 [156] | openjdk-11 [157] |
| | |
| DSA-5132 [158] | ecdsautils [159] |
| | |
| DSA-5133 [160] | qemu [161] |
| | |
| DSA-5134 [162] | chromium [163] |
| | |
| DSA-5136 [164] | postgresql-13 [165] |
| | |
| DSA-5137 [166] | needrestart [167] |
| | |
| DSA-5138 [168] | waitress [169] |
| | |
| DSA-5139 [170] | openssl [171] |
| | |
| DSA-5140 [172] | openldap [173] |
| | |
| DSA-5141 [174] | thunderbird [175] |
| | |
| DSA-5142 [176] | libxml2 [177] |
| | |
| DSA-5143 [178] | firefox-esr [179] |
| | |
| DSA-5145 [180] | lrzip [181] |
| | |
| DSA-5147 [182] | dpkg [183] |
| | |
| DSA-5148 [184] | chromium [185] |
| | |
| DSA-5149 [186] | cups [187] |
| | |
| DSA-5150 [188] | rsyslog [189] |
| | |
| DSA-5151 [190] | smarty3 [191] |
| | |
| DSA-5152 [192] | spip [193] |
| | |
| DSA-5153 [194] | trafficserver [195] |
| | |
| DSA-5154 [196] | webkit2gtk [197] |
| | |
| DSA-5155 [198] | wpewebkit [199] |
| | |
| DSA-5156 [200] | firefox-esr [201] |
| | |
| DSA-5157 [202] | cifs-utils [203] |
| | |
| DSA-5158 [204] | thunderbird [205] |
| | |
| DSA-5159 [206] | python-bottle [207] |
| | |
| DSA-5160 [208] | ntfs-3g [209] |
| | |
| DSA-5161 [210] | linux-signed-amd64 [211] |
| | |
| DSA-5161 [212] | linux-signed-arm64 [213] |
| | |
| DSA-5161 [214] | linux-signed-i386 [215] |
| | |
| DSA-5161 [216] | linux [217] |
| | |
| DSA-5162 [218] | containerd [219] |
| | |
| DSA-5163 [220] | chromium [221] |
| | |
| DSA-5164 [222] | exo [223] |
| | |
| DSA-5165 [224] | vlc [225] |
| | |
| DSA-5166 [226] | slurm-wlm [227] |
| | |
| DSA-5167 [228] | firejail [229] |
| | |
| DSA-5168 [230] | chromium [231] |
| | |
| DSA-5169 [232] | openssl [233] |
| | |
| DSA-5171 [234] | squid [235] |
| | |
| DSA-5172 [236] | firefox-esr [237] |
| | |
| DSA-5174 [238] | gnupg2 [239] |
| | |
+—————-+————————–+

82: https://www.debian.org/security/2021/dsa-4999
83: https://packages.debian.org/src:asterisk
84: https://www.debian.org/security/2021/dsa-5026
85: https://packages.debian.org/src:firefox-esr
86: https://www.debian.org/security/2022/dsa-5034
87: https://packages.debian.org/src:thunderbird
88: https://www.debian.org/security/2022/dsa-5044
89: https://packages.debian.org/src:firefox-esr
90: https://www.debian.org/security/2022/dsa-5045
91: https://packages.debian.org/src:thunderbird
92: https://www.debian.org/security/2022/dsa-5069
93: https://packages.debian.org/src:firefox-esr
94: https://www.debian.org/security/2022/dsa-5074
95: https://packages.debian.org/src:thunderbird
96: https://www.debian.org/security/2022/dsa-5086
97: https://packages.debian.org/src:thunderbird
98: https://www.debian.org/security/2022/dsa-5090
99: https://packages.debian.org/src:firefox-esr
100: https://www.debian.org/security/2022/dsa-5094
101: https://packages.debian.org/src:thunderbird
102: https://www.debian.org/security/2022/dsa-5097
103: https://packages.debian.org/src:firefox-esr
104: https://www.debian.org/security/2022/dsa-5106
105: https://packages.debian.org/src:thunderbird
106: https://www.debian.org/security/2022/dsa-5107
107: https://packages.debian.org/src:php-twig
108: https://www.debian.org/security/2022/dsa-5108
109: https://packages.debian.org/src:tiff
110: https://www.debian.org/security/2022/dsa-5110
111: https://packages.debian.org/src:chromium
112: https://www.debian.org/security/2022/dsa-5111
113: https://packages.debian.org/src:zlib
114: https://www.debian.org/security/2022/dsa-5112
115: https://packages.debian.org/src:chromium
116: https://www.debian.org/security/2022/dsa-5113
117: https://packages.debian.org/src:firefox-esr
118: https://www.debian.org/security/2022/dsa-5114
119: https://packages.debian.org/src:chromium
120: https://www.debian.org/security/2022/dsa-5115
121: https://packages.debian.org/src:webkit2gtk
122: https://www.debian.org/security/2022/dsa-5116
123: https://packages.debian.org/src:wpewebkit
124: https://www.debian.org/security/2022/dsa-5117
125: https://packages.debian.org/src:xen
126: https://www.debian.org/security/2022/dsa-5118
127: https://packages.debian.org/src:thunderbird
128: https://www.debian.org/security/2022/dsa-5119
129: https://packages.debian.org/src:subversion
130: https://www.debian.org/security/2022/dsa-5120
131: https://packages.debian.org/src:chromium
132: https://www.debian.org/security/2022/dsa-5121
133: https://packages.debian.org/src:chromium
134: https://www.debian.org/security/2022/dsa-5122
135: https://packages.debian.org/src:gzip
136: https://www.debian.org/security/2022/dsa-5123
137: https://packages.debian.org/src:xz-utils
138: https://www.debian.org/security/2022/dsa-5124
139: https://packages.debian.org/src:ffmpeg
140: https://www.debian.org/security/2022/dsa-5125
141: https://packages.debian.org/src:chromium
142: https://www.debian.org/security/2022/dsa-5127
143: https://packages.debian.org/src:linux-signed-amd64
144: https://www.debian.org/security/2022/dsa-5127
145: https://packages.debian.org/src:linux-signed-arm64
146: https://www.debian.org/security/2022/dsa-5127
147: https://packages.debian.org/src:linux-signed-i386
148: https://www.debian.org/security/2022/dsa-5127
149: https://packages.debian.org/src:linux
150: https://www.debian.org/security/2022/dsa-5128
151: https://packages.debian.org/src:openjdk-17
152: https://www.debian.org/security/2022/dsa-5129
153: https://packages.debian.org/src:firefox-esr
154: https://www.debian.org/security/2022/dsa-5130
155: https://packages.debian.org/src:dpdk
156: https://www.debian.org/security/2022/dsa-5131
157: https://packages.debian.org/src:openjdk-11
158: https://www.debian.org/security/2022/dsa-5132
159: https://packages.debian.org/src:ecdsautils
160: https://www.debian.org/security/2022/dsa-5133
161: https://packages.debian.org/src:qemu
162: https://www.debian.org/security/2022/dsa-5134
163: https://packages.debian.org/src:chromium
164: https://www.debian.org/security/2022/dsa-5136
165: https://packages.debian.org/src:postgresql-13
166: https://www.debian.org/security/2022/dsa-5137
167: https://packages.debian.org/src:needrestart
168: https://www.debian.org/security/2022/dsa-5138
169: https://packages.debian.org/src:waitress
170: https://www.debian.org/security/2022/dsa-5139
171: https://packages.debian.org/src:openssl
172: https://www.debian.org/security/2022/dsa-5140
173: https://packages.debian.org/src:openldap
174: https://www.debian.org/security/2022/dsa-5141
175: https://packages.debian.org/src:thunderbird
176: https://www.debian.org/security/2022/dsa-5142
177: https://packages.debian.org/src:libxml2
178: https://www.debian.org/security/2022/dsa-5143
179: https://packages.debian.org/src:firefox-esr
180: https://www.debian.org/security/2022/dsa-5145
181: https://packages.debian.org/src:lrzip
182: https://www.debian.org/security/2022/dsa-5147
183: https://packages.debian.org/src:dpkg
184: https://www.debian.org/security/2022/dsa-5148
185: https://packages.debian.org/src:chromium
186: https://www.debian.org/security/2022/dsa-5149
187: https://packages.debian.org/src:cups
188: https://www.debian.org/security/2022/dsa-5150
189: https://packages.debian.org/src:rsyslog
190: https://www.debian.org/security/2022/dsa-5151
191: https://packages.debian.org/src:smarty3
192: https://www.debian.org/security/2022/dsa-5152
193: https://packages.debian.org/src:spip
194: https://www.debian.org/security/2022/dsa-5153
195: https://packages.debian.org/src:trafficserver
196: https://www.debian.org/security/2022/dsa-5154
197: https://packages.debian.org/src:webkit2gtk
198: https://www.debian.org/security/2022/dsa-5155
199: https://packages.debian.org/src:wpewebkit
200: https://www.debian.org/security/2022/dsa-5156
201: https://packages.debian.org/src:firefox-esr
202: https://www.debian.org/security/2022/dsa-5157
203: https://packages.debian.org/src:cifs-utils
204: https://www.debian.org/security/2022/dsa-5158
205: https://packages.debian.org/src:thunderbird
206: https://www.debian.org/security/2022/dsa-5159
207: https://packages.debian.org/src:python-bottle
208: https://www.debian.org/security/2022/dsa-5160
209: https://packages.debian.org/src:ntfs-3g
210: https://www.debian.org/security/2022/dsa-5161
211: https://packages.debian.org/src:linux-signed-amd64
212: https://www.debian.org/security/2022/dsa-5161
213: https://packages.debian.org/src:linux-signed-arm64
214: https://www.debian.org/security/2022/dsa-5161
215: https://packages.debian.org/src:linux-signed-i386
216: https://www.debian.org/security/2022/dsa-5161
217: https://packages.debian.org/src:linux
218: https://www.debian.org/security/2022/dsa-5162
219: https://packages.debian.org/src:containerd
220: https://www.debian.org/security/2022/dsa-5163
221: https://packages.debian.org/src:chromium
222: https://www.debian.org/security/2022/dsa-5164
223: https://packages.debian.org/src:exo
224: https://www.debian.org/security/2022/dsa-5165
225: https://packages.debian.org/src:vlc
226: https://www.debian.org/security/2022/dsa-5166
227: https://packages.debian.org/src:slurm-wlm
228: https://www.debian.org/security/2022/dsa-5167
229: https://packages.debian.org/src:firejail
230: https://www.debian.org/security/2022/dsa-5168
231: https://packages.debian.org/src:chromium
232: https://www.debian.org/security/2022/dsa-5169
233: https://packages.debian.org/src:openssl
234: https://www.debian.org/security/2022/dsa-5171
235: https://packages.debian.org/src:squid
236: https://www.debian.org/security/2022/dsa-5172
237: https://packages.debian.org/src:firefox-esr
238: https://www.debian.org/security/2022/dsa-5174
239: https://packages.debian.org/src:gnupg2

Removed packages
—————-

The following packages were removed due to circumstances beyond our
control:

+———————+——————————-+
| Package | Reason |
+———————+——————————-+
| elog [240] | Unmaintained; security issues |
| | |
| python-hbmqtt [241] | Unamintained and broken |
| | |
+———————+——————————-+

240: https://packages.debian.org/src:elog
241: https://packages.debian.org/src:python-hbmqtt

Debian Installer
—————-

The installer has been updated to include the fixes incorporated into
stable by the point release.

URLs
—-

The complete lists of packages that have changed with this revision:

https://deb.debian.org/debian/dists/bullseye/ChangeLog

The current stable distribution:

https://deb.debian.org/debian/dists/stable/

Proposed updates to the stable distribution:

https://deb.debian.org/debian/dists/proposed-updates

stable distribution information (release notes, errata etc.):

https://www.debian.org/releases/stable/

Security announcements and information:

https://www.debian.org/security/

About Debian
————

The Debian Project is an association of Free Software developers who
volunteer their time and effort in order to produce the completely free
operating system Debian.

Contact Information
——————-

For further information, please visit the Debian web pages at
https://www.debian.org/, send mail to , or contact the
stable release team at .

--
Brian Masinick
May 21, 2022 at 2:38 pm #83398

In reply to: What are you “here” with today?
Member
seaken64
marcelocripe wrote:

I believe your computers are not old enough. I revive computers with Pentium 4 and Celeron, eventually Pentium D or Dual Core. Core 2 Duo or higher are rare. The RAM memory card is DDR or DDR2, eventually I find DDR3.

So my gratitude to the creator, developers and programmers of antiX Linux.

“I believe your computers are not old enough.”

That made me laugh 🙂

I also use a lot of old Pentium 4 and Pentium 3 systems with antiX. But, admittedly, I don’t do a lot of browsing on this forum with that equipment. I use those systems mostly for experiments and setting up OS software and user interfaces. When I do use the internet on those systems it is usually streaming audio from internet radio and some light browsing like Wikipedia and forums.

Today I am using my “luxury” model laptop, a Lenovo Core i3-8130U Model 330S-15IKB, running MX-21 XFCE. Unfortunately, I don’t have a lot of older laptops. Most of my ancient kit is desktops. And this week I am traveling so I brought this laptop. However, I did recently pick up an old HP ProBook from about 2011. It’s a model 4520s and runs antiX and MX very well. But I didn’t bring that machine on this trip.

Keep it up. I love to read about what old equipment people can keep alive with antiX.

Seaken64
March 28, 2022 at 5:20 pm #80044

In reply to: Sway on antiX with elogind
Member
Dzhigit
Hello, after a long time I am finally an active user of antiX again. I again set out to make an antiX Testing (bookworm) runit net Live USB with Sway. However a lot has changed about Sway and libwlroots9 since last time.

Sway’s latest libwlroots9 makes use of libseat1 instead of logind directly, which in turn has backends for logind and seatd. However Sway itself still has a dependency on libsystemd0. Maybe it uses sd-bus. antiX’s libseat1 package conflicts with libsystemd0 and libelogind0, making it impossible to install both libseat1 and libelogind0 to satisfy the dependencies for Sway. Debian fixed this several months ago. I pinned antiX libseat1 to -1 and installed Debian’s instead.
```
Package: libseat1
Pin: release l=antiX Repository
Pin-Priority: -1
```
Now that Debian has packaged libseat1, if antiX removes libseat1 from antiX testing and unstable, the issue would be fixed for everyone.
However, I cannot get Sway to work on antiX, with either seatd or logind. I have to use the Sway wiki‘s last resort. setuid the Sway executable. It’s not too big of a deal, other than the vulnerability it opens, but I think there is some underlying issue with polkit, which is preventing other things from working like pipewire. This is a log of Sway working with setuid:
```
/bin/sh: 1: systemctl: not found
dbus-update-activation-environment: error: unable to connect to D-Bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
2022-03-27 21:10:10 - [main.c:340] Found config * for output eDP-1 (Unknown 0x162C 0x00000000)
00:00:00.011 [ERROR] [swaybar/tray/tray.c:42] Failed to connect to user bus: No such file or directory
00:00:01.364 [ERROR] [common/ipc-client.c:87] Unable to receive IPC response
```
With setuid Sway works, but still has a few errors in the log. With LIBSEAT_BACKEND=logind, it doesn’t work:
```
00:00:00.005 [ERROR] [wlr] [libseat] [libseat/backend/logind.c:310] Could not activate session: Interactive authentication required.
00:00:00.005 [ERROR] [wlr] [libseat] [libseat/libseat.c:58] Backend 'logind' failed to open seat: Permission denied
00:00:00.005 [ERROR] [wlr] [backend/session/session.c:84] Unable to create seat: Permission denied
00:00:00.005 [ERROR] [wlr] [backend/session/session.c:218] Failed to load session backend
00:00:00.005 [ERROR] [wlr] [backend/backend.c:353] Failed to start a DRM session
00:00:00.005 [ERROR] [sway/server.c:53] Unable to create backend
```
There are errors about “interactive authentication required” and DISPLAY not being set elsewhere in the system, like pipewire. This is an area I don’t know anything about. Interactive authentication sounds like polkit is doing the same thing as sudo, asking for a password. I don’t know if polkit configuration should be changed, or DISPLAY needs to be set. Maybe to WAYLAND_DISPLAY? Sway with seatd had even more errors about not having permissions.

Unrelatedly, a broken symbolic at /etc/resolv.conf was preinstalled on the image, and libeudev-dev preinstalled for some reason. Though I am not completely sure if the symbolic link was already on the ISO or not, I think it was.
- This reply was modified 1 year, 1 month ago by Dzhigit.
February 16, 2022 at 3:20 am #77505

In reply to: Libre-antiX 21 respin
Member
andyprough
JWM-Kit wrote:

wallpaper

I think antiX is a good match for JWM Kit. The only issue is that they have very different ideas on how to build a jwm configuration. This means that if you wish to use JWM Kit on antiX you might want to backup your jwm configuration.

Yes, that wallpaper does look good, thank you for that. The slight glow along the edges is a nice touch, I agree. I think it will work with the conky. I’ll try it on a couple of systems with low-res monitors.

My best experience with JWMKIT on antiX has been by completely removing everything JWM related from the standard antiX install, including any config files and the antiX desktop-defaults package for JWM, and purging JWM itself. Then installing JWM from the Debian repo from scratch, adding JWMKIT, and running the JWMKIT_firstrun setup. That may be due to my lack of in-depth knowledge about JWM and JWMKIT, but that does seem like the most straightforward way to go. Otherwise it seems like the antiX JWM defaults and the JWMKIT defaults were creating some problems. I don’t even recall what the problems were, but starting from a fresh slate seemed to give me a very good JWMKIT experience.

One thing I really like with this respin is the incredibly low memory usage. 32-bit is often overlooked in terms of giving you drastically lower memory usage. If a person doesn’t need to do complex projects on a system, and just wants a light, fast system for simple web browsing and light tasks, it would be hard to beat this kind of antiX setup. I’ve used some of the Puppy spins and TinyCore Linux, but this kind of antiX setup with 32-bit gives you really low resource usage PLUS all the instant access to the full Debian repos, plus a bunch of 3rd party software that can be installed with one mouseclick in the antiX Package Installer. Plus the great tools – are you aware of the great Live USB tools on antiX? Not only does it have multiple built-in persistence options and frugal install options, but you’ve got the ability to update to a newer kernel on a Live USB, and to make snapshot ISO’s to share with others (which is how I make the respin). Plus you’ve got the multi-arch options, the multiple init system options – A person (such as yourself) wanting to make a specialized ISO to show off JWMKIT could hardly do better than using antiX as the base.
February 4, 2022 at 2:53 am #76740

Topic: new release: Slackware Linux 15.0

in forum Other Distros
Anonymous
FYI
(and interested in reading feedback from anyone who test drives it…)

http://www.slackware.com/announce/15.0.php
BREAKING NEWS, SEBEKA MINNESOTA 2022-02-02:

.
{———- snip ————}
.

This has been an interesting development cycle (in the “may you live in interesting times” sense). Anyone who has followed Linux development over the years has seen the new technology and a slow but steady drift away from the more UNIX-like structure. The challenge this time around was to adopt as much of the good stuff out there as we could without changing the character of the operating system. Keep it familiar, but make it modern. And boy did we have our work cut out for us. We adopted PAM (finally) as [some] projects we needed [have] dropped support for pure shadow passwords. We switched from ConsoleKit2 to elogind, making it much easier to support software that targets that Other Init System and bringing us up-to-date with the XDG standards. We added support for PipeWire as an alternate to PulseAudio, and for Wayland sessions in addition to X11. Dropped Qt4 and moved entirely to Qt5. Brought in Rust and Python 3. Added many, many new libraries to the system to help support all the various additions. We’ve upgraded to two of the finest desktop environments available today: Xfce 4.16, a fast and lightweight but visually appealing and easy to use desktop environment, and the KDE Plasma 5 graphical workspaces environment, version 5.23.5 (the Plasma 25th Anniversary Edition). This also supports running under Wayland or X11.

We still love Sendmail, but have moved it into the /extra directory and made Postfix the default mail handler. The old imapd and ipop3d have been retired and replaced by the much more featureful Dovecot IMAP and POP3 server.

The Slackware pkgtools (package management utilities) saw quite a bit of development as well. File locking was implemented to prevent parallel installs or upgrades from colliding, and the amount of data written to storage minimized in order to avoid extra writes on SSD devices.

For the first time ever we have included a “make_world.sh” script that allows automatically rebuilding the entire operating system from source. We also made it a priority throughout the development cycle to ensure that nothing failed to build. All the sources have been tested and found to build properly. Special thanks to nobodino for spearheading this effort.

We have also included new scripts to easily rebuild the installer, and to build the kernel packages. With the new ease of generating kernel packages, we went on to build and test nearly every kernel that was released, finally landing on the 5.15.x LTS series which we’ve used for this release. There are also some sample config files to build 5.16 kernels included in the /testing directory for anyone interested in using those kernels.

There’s really just way too many upgrades to list them all here. For a complete list of included packages, see:
ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/PACKAGES.TXT

Downloading Slackware 15.0:
—————————

The full version of Slackware Linux 15.0 is available for download from the central Slackware FTP site hosted by our friends at osuosl.org

If your machine supports x86_64, it is highly recommended that you use the Slackware64 (64-bit) version for the best possible performance:
ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/

The 32-bit x86 version may be found here:
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/

The links above are for the Slackware file tree. If you already have Slackware 14.2 installed, you can use these files and follow the instructions in the UPGRADE.TXT document to upgrade your system to Slackware 15.0. Instructions for burning the Slackware file tree onto install discs may be found in the isolinux directory.

If you’re looking for a bootable installer, ISO images are available that can be written to a DVD or (using dd) to a USB stick:
ftp://ftp.slackware.com:/pub/slackware-iso/slackware64-15.0-iso
ftp://ftp.slackware.com:/pub/slackware-iso/slackware-15.0-iso

If the sites are busy, see the list of official mirror sites here: mirrors.slackware.com

We will be setting up BitTorrent downloads for the official ISO images. Stay tuned to slackware.com and the ##slackware IRC channel on
libera.chat for the latest updates.
.
{———- snip ————}
.

—
Patrick J. Volkerding {email@redact.ed}

Visit us on the web at: http://slackware.com
January 30, 2022 at 6:13 pm #76432

In reply to: Linux Live Kit
Forum Admin
rokytnji
https://www.antixforum.com/forums/topic/init-a-modular-linuxfs/#post-5788

That figures. I did a search forum 1st to see if the thread I started had already been posted. I guess my search term was not good enough for the r/h taskbar search box . I say my screw up because I just perused the titles of the threads instead of the content. At least now. Linux Live Kit will show up in the search box.
https://www.antixforum.com/forums/search/linux+live+kit/

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
Author

Search Results

Viewing 15 results - 1 through 15 (of 57 total)

1 2 … 4 →

Cookie	Duration	Description
cookielawinfo-checkbox-analytics	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional	11 months	The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy	11 months	The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.

In reply to: What are you “here” with today?

In reply to: antiX-23-alpha1-runit-full (64bit) for testing

In reply to: Can I make my custom locked-down computer more “open”?

In reply to: Pipewire without systemd

In reply to: Pipewire without systemd

In reply to: What are you “here” with today?

In reply to: Troubles with Broadcom WiFi BCM4318

In reply to: Hello All From UK – HP G60 3GiB RAM 2008

Attachments:

In reply to: AntiX on Asus eee PC

Topic: Updated Debian 11: 11.4 released

In reply to: What are you “here” with today?

In reply to: Sway on antiX with elogind

In reply to: Libre-antiX 21 respin

Topic: new release: Slackware Linux 15.0

In reply to: Linux Live Kit