Search Results for 'boot from iso'

[Member Xecure]

marcelocripe wrote:

Eu fiz um teste que falta fazer, utilizar o Adaptador Wireless USB Ralink MT7601U no antiX Legacy (“antiX-19-legacy-bet2_386-base.iso”). Eu não sei porque, mas no Legacy este dispositivo está funcionado muito bem e é possível navegar na internet e fazer a atualização normalmente com o “Ceni” gerenciando a conexão de rede.

That is good news. This means that the 4.4 kernel version works properly for this device. You can downgrade the kernel for the other computers to 4.4 and test the Ralink Wifi USB Adapter with that kernel. You can find it in the package installer under Kernel-antiX_64bit_legacy_LTS (or Kernel-antiX_32bit_legacy_LTS on 32 bits systems). If you need to download them offline, you can use the my-offline-repo program and search for antix legacy kernel, I think, so you can later install it offline.
I will have to take a look at the my-offline-repo and update it to account for the new translated descriptions in packageinstaller-pkglist.

If the other rtl8188fu driver works well after installing both dkms driver and firmware, then keep them for 64 bit systems and swap the Ralink one for 32 bit systems. This would be the easiest solution if you can’t compile the rtl8188fu driver for 32 bit systems.

A note related to installing kernels. After installing a new kernel, you need to reboot to select it in the grub menu. If it is a newer kernel, it will be selected automatically, but if it is a lower version number kernel (like downgrading from 4.9 to 4.4), you need to select this “older” kernel from the advanced boot options in the grub menu. It should display all available kernels installed for you to select for boot. Select the desired kernel version, boot into your system, check that everything works as before, and then remove the other newer kernels you don’t want to use. You can use the cli-aptiX command to manage all installed kernels.
Automatically, it will always try to boot the newest available kernels version, so that is why I recommend removing all higher kernel kersions you don’t want or need.

Let me know if you want a more detailed or step by step explanation, in case the above is not too clear.

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

[Member xinomilo]

just tested runit version in qemu/kvm, there’s some error when decrypting luks partitions after installation – first boot.. (couldn’t find 2.something partition iirc ).
didn’t dig more, but will try to post more details tomorrow… there was no error during installation…

live iso looked pretty fast/neat as always, thx 🙂

[Member Xecure]

The same as Jing-Jo has experienced, the boot menu (UEFI-grub) displays -runit-, but is in fact sysvinit as previously stated, so it is only an erroneous message in BOOT.

Is no-one else going to comment the amazing feat of ONE antiX ISO with TWO different kernels! I was really surprised after trying it out and reaaaaaly surprised after seeing how well each worked!
I haven’t had much time these weeks for anything, as some personal problems have popped up. No detailed feedback for the new build yet, but so far it is working fine.

My congratulations on finally getting connman to correctly start (for the first time on my laptop) with wifi enabled, all ready to start working. I think this will finally end with most of the “wifi problems” related posts in the future.

I will try to provide detailed feedback when I have time again. Sorry for this empty post.

anticapitalista wrote:

runit – yes

Is there a plan to release a sysvinit-to-runit service conversion manual/instructions so we can create the correct service init files for services not originally contemplated in antiX-runit edition? Is there a plan to make runit the “main” init in the future (seeing the related information post)? Do I need to update the antix-wifi-switch so it properly work for runit (I haven’t tested it yet on antiX21-runit-a2)?

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

[Member Danathar]

christophe wrote:

Please give us what caprea requested, copy & paste the inxi output between “CODE” tags, if possible:

A suggestion would be you first post your hardware here and which antiX is running etc..
inxi -zv7

Would you like the output from both the Antix running Kernel and when I boot up MX Linux (for comparison)?

[Member oops]

Re: (installed on VM VirtualBox)
Tried and tested a little more, almost seems working correctly until now so congratulations, except:

1-) At slim login, the halt user + rootPwd does not work, but reboot + rootPwd works.
2-) Smbclient does not work (smbtree, etc)

Edit: I also tried a .iso snapshot via antixcc.sh, and it worked well.

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

This is a work in progress.

Much of the information has been copied from Artix wiki on runit, but modified to how it runs on antiX.

What is runit?
runit is a suite of tools which provides an init (PID 1) as well as daemontools-compatible process supervision framework, along with utilites which streamline creation and maintenance of services.

Installation
This is very much a work in progress. If users want to try out runit, use the runit version iso. Otherwise, converting an existing antiX-sysvinit to runit will probably end in breakage.

Installation of services
A basic set of runit service packages are provided on the iso and can be found in /usr/share/runit/sv and are copied to /etc/sv if they don’t already exist there. This allows users to customise their runit service scripts in /etc/sv and they will not get overwritten on any update.

Programs
runit has several programs, but usually you will only interact directly with one program only.

*sv – used for controlling services, getting status of services, and dependency checking.
*chpst – control of a process environment, including memory caps, limits on cores, data segments, environments, user/group privileges, and more.
*runsv – supervises a process, and optionally a log service for that process.
*svlogd – a simple but powerful logger, includes auto-rotation based on different methods (time, size, etc), post-processing, pattern matching, and socket (remote logging) options.
*runsvchdir – changes service levels (runlevels, see below)
*runsvdir – starts a supervision tree
*runit-init – PID 1, does almost nothing besides being the init

Files
There are several files installed by runit.

/etc/runit/1 – stage 1, system’s one-time initialization tasks
/etc/runit/2 – stage 2, Normally runs runsvdir, should not return until the system is going to halt or reboot.
/etc/runit/3 – stage 3, system’s shutdown tasks
/etc/runit/ctrlaltdel – runit will execute this when receiving a SIGINT signal
/etc/runit/runsvdir/* – Runlevels
/etc/sv/* – directory containing subdirectories of available service files
/etc/service – always symlinked to active runlevel, sv will search for running service here

On antiX, one-time initialization task scripts are mostly found in /etc/runit-core and a few in /etc/init.d
antiX has altered Debian’s sysvinit scripts to run as runit scripts.
However, some manual intervention may be needed especially when using antiX-net or antiX-core runit editions.

Basic usage

*Enable service (in runlevel default)# ln -s /etc/sv/service_name /etc/service/
*Disable service # unlink /etc/service/service_name or # touch down /etc/sv/service_name
*Stop immediately # sv down service_name or # sv stop service_name
*Start (if not running) # sv up service_name or # sv restart service_name
*Restart # sv restart service_name
*Reload # sv restart service_name
*Status check # sv status service_name
*Switch runlevels (this will stop all services that are currently running and will start all services in the new runlevel) # runsvchdir runlevel

Thanks to @Xexure, the above can be done via the runit-service-manager app.

Runlevel
By default, on antiX runit has 3 runlevels, default, single and solo. You can make your own runlevels just by creating a new folder in /etc/runit/runsvdir/ and symlinking your desired service to that runlevel.

Service directory structure
This is a tree of a complete service directory structure (aka /etc/sv/servicedir), in some run scripts, typically only run will be available as usually it’s the only file needed.

servicedir
├── run (755)
├── check (755)
├── conf (644)
├── finish (755)
└── log (directory)
├── config (644)
└── run (755)

A runit (or any daemontools-compatible) run script service directory usually contains only one executable file, run, which runs process in the foreground. Processes that run in the background cannot be supervised by runit.

If a service directory contains another directory named log, the output of the run process in the service directory will be piped to the input of the run process in the log directory. If the log service uses svlogd, it may be configured by using the file config. How svlogd can be configured is explained in the svlogd(1) manpage.

A run script may also contain executables like finish and check. finish will be executed when a service is stopped, and check will be executed (if exists) by sv check or sv status.

A run script may also contain a conf file (which is not executable) that modifies the variables available to the script.

Service dependencies
Some services may depend on other services. For example, Connman depends on dbus. To ensure that required dependencies are satisfied, check the service’s run file. For example, for Connman:

# /etc/sv/Connman/run
sv start dbus && sv check dbus || exit 170

This means you have to enable dbus for Connman to start.

• This topic was modified 6 months, 1 week ago by anticapitalista. Reason: Use Connman as an example

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

antiX with runit - leaner and meaner.

[Forum Admin rokytnji]

https://wiki.archlinux.org/index.php/Via_Technologies#The_OpenChrome_driver

I’ll also mention. Every full iso since antiX 8.5 on live boot before install. Gave me line readout of

Either wait or hit key to select screen resolutions on boot.

I finally figured out to wait and antiX always defaulted to 1024X600 on my netbooks. Every time I chose not to wait and decided to try my hand on the other option. I would screw the pooch.

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

[Member Robin]

Well, burrezo, I greet you.
I’m gobsmacked. Really. Hats off to you and Jorge Maidana!
Thank you very much for posting this solution for a problem I was working on for a long time now. This nvidia driver kept me from upgrading to antiX 19 up to now, and I was in doubt whether my notebook would be bricked on purpose by Nvidia finally, which would have happened if no solution for this problem would have been found before next year. Nouveau driver doesn’t work at all on this Notebook, resulting in blurry text and milky fog on the screen in X, which makes it hard to see what you are doing, and a blank black console, not allowing to enter anything.

I followed your guidance and the 304.137 driver installed flawlessly on a fresh antiX 19.3 install (all recent upgrades applied)

Only the command “sudo update-grub” in step [3] didn’t work for me. It responded with an error (“grub: failed to get canonical path”). I tried to chroot to make it work but didn’t figure out which folder on the bootdevice would be the correct place to chroot to, and since the live USB stick (persistent) does engage Isolinux instead anyway, I decided to execute the steps in a different succession instead: First I prepared and executed everything (including the deinstallation of xserver-xorg-core and reinstalling the stretch version after switching the repositories), except for the installation of the already patched nvidia driver itself. Strange enough, the system booted to textmode in runlevel 5 on next boot (without updating grub before). Since X was not running, the patched nvidia driver installed perfectly. So I executed the final steps of your guide before rebooting. You’ll need to enter the command “sudo reboot” on commandline, in order make sure save-persistence for the root file system will be properly completed, so the new nvidia driver is stored. After reboot antiX 19.3 came up with clear, strong colours on screen and pin sharp letters. Everything seems to work as expected at the first glance, but I’ll report here about stability and whether I come across any side effects over time. I’m a bit in doubt about security, having to set xserver on hold. How do I get security updates for this in future?

OK, for now here are the system details:

$ xrandr -q
Screen 0: minimum 8 x 8, current 1440 x 900, maximum 4096 x 4096
VGA-0 disconnected primary (normal left inverted right x axis y axis)
VGA-1 disconnected (normal left inverted right x axis y axis)
VGA-2 connected 1440x900+0+0 (normal left inverted right x axis y axis) 367mm x 230mm
   1440x900      60.00*+

$ sudo hwinfo --gfxcard
26: PCI 100.0: 0300 VGA compatible controller (VGA)             
  [Created at pci.386]
  Unique ID: 
  Parent ID: 
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "nVidia GeForce Go 6600 (0x0148)"
  Vendor: pci 0x10de "nVidia Corporation"
  Device: pci 0x0148 "GeForce Go 6600 (0x0148)"
  SubVendor: pci 0x161f "Rioworks"
  SubDevice: pci 0x203d 
  Revision: 0xa2
  Driver: "nvidia"
  Driver Modules: "nvidia"
  Memory Range: 0xa0000000-0xa3ffffff (rw,non-prefetchable)
  Memory Range: 0xc0000000-0xc7ffffff (ro,non-prefetchable)
  Memory Range: 0x90000000-0x90ffffff (rw,non-prefetchable)
  Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
  IRQ: 16 (7437 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v000010DEd00000148sv0000161Fsd0000203Dbc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: nv
  Driver Info #1:
    XFree86 v4 Server Module: nvidia
    3D Support: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #22 (PCI bridge)

Primary display adapter: #26

demo@antix1:~
$ inxi -zv8
System:    Host: antix1 Kernel: 4.19.180-antix.1-686-smp-pae i686 bits: 32 compiler: gcc v: 8.3.0 
           parameters: vga=0x0317 gfxsave persist_all lang=de_DE tz=Europe/Berlin quiet splasht 
           disable=lxF mount=all 
           Desktop: IceWM 2.2.1 dm: SLiM 1.3.6 
           Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Other-vm? System: Notebook product: RIM2000 v: N/A serial: <filter> 
           Chassis: No Enclosure type: 1 serial: <filter> 
           Mobo: Notebook model: RIM2000 serial: <filter> BIOS: Phoenix v: RIM00F0A 
           date: 05/27/2005 
Battery:   ID-1: BAT0 charge: 0 Wh condition: N/A volts: N/A model: ARIMA LI4403A type: Unknown 
           serial: <filter> status: Unknown 
Memory:    RAM: total: 1.96 GiB used: 181.7 MiB (9.1%) 
           RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
PCI Slots: Permissions: Unable to run dmidecode. Root privileges required. 
CPU:       Topology: Single Core model: Intel Pentium M bits: 32 type: MCP arch: M Dothan 
           family: 6 model-id: D (13) stepping: 8 microcode: 20 L2 cache: 2048 KiB bogomips: 1596 
           Speed: 800 MHz min/max: 800/1733 MHz Core speed (MHz): 1: 800 
           Flags: acpi apic bts clflush cmov cpuid cx8 de dts est fpu fxsr mca mce mmx msr mtrr nx 
           pae pbe pge pse pti sep ss sse sse2 tm tm2 tsc vme 
           Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA NV43M [GeForce Go 6600] vendor: Rioworks driver: nvidia v: 304.137 
           bus ID: 01:00.0 chip ID: 10de:0148 
           Display: x11 server: X.Org 1.19.2 driver: nvidia FAILED: fbdev,nouveau,vesa 
           unloaded: modesetting alternate: nv resolution: 1440x900~60Hz 
           OpenGL: renderer: GeForce Go 6600/PCIe/SSE2 v: 2.1.2 NVIDIA 304.137 direct render: Yes 
Audio:     Device-1: Intel 82801FB/FBM/FR/FW/FRW High Definition Audio vendor: Rioworks 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:2668 
           Device-2: Philips s SAA7131/SAA7133/SAA7135 Video Broadcast Decoder vendor: Animation 
           driver: saa7134 v: 0, 2, 17 bus ID: 06:03.0 chip ID: 1131:7133 
           Sound Server: ALSA v: k4.19.180-antix.1-686-smp-pae 
Network:   Device-1: Marvell 88E8036 PCI-E Fast Ethernet vendor: Rioworks driver: sky2 v: 1.30 
           port: 2000 bus ID: 02:00.0 chip ID: 11ab:4351 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200 v: 1.2.2kmprq 
           port: 2000 bus ID: 06:08.0 chip ID: 8086:4220 
           IF: eth1 state: up mac: <filter> 
           IP v4: <filter> scope: global broadcast: <filter> 
           IP v6: <filter> scope: link 
           WAN IP: <filter> 
Drives:    Local Storage: total: 151.75 GiB used: 49.63 GiB (32.7%) 
           ID-1: /dev/sda vendor: Seagate model: ST9100823A size: 93.16 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 3.02 scheme: MBR 
           ID-2: /dev/sdb type: USB vendor: Generic model: Flash Disk size: 58.59 GiB block size: 
           physical: 512 B logical: 512 B serial: <filter> rev: 8.01 scheme: GPT 
           Optical-1: /dev/sr0 vendor: MATSHITA model: DVD-RAM UJ-840S rev: 1.00 
           dev-links: cdrom,cdrw,dvd,dvdrw 
           Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram 
           state: running 
RAID:      Message: No RAID data was found. 
Partition: ID-1: / raw size: N/A size: 1.54 GiB used: 352 KiB (0.0%) fs: overlay source: ERR-102 
           label: N/A uuid: N/A 
           ID-2: /home raw size: 25.00 GiB size: <root required> used: <root required> fs: ext4 
           dev: /dev/loop1 label: N/A uuid: 12ca6406-5fe3-4480-b013-9de029dd6456 
           ID-3: /live/boot-dev raw size: 58.54 GiB size: 58.36 GiB (99.68%) 
           used: 5.91 GiB (10.1%) fs: ext4 dev: /dev/sdb1 label: antiX-Live-usb 
           uuid: 326eac56-4981-40d1-9a28-14376a8aa6a7 
           ID-4: /live/linux raw size: 1.92 GiB size: <root required> used: <root required> 
           fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A 
           ID-5: /media/_daten1 raw size: 8.00 GiB size: 7.75 GiB (96.87%) used: 18.1 MiB (0.2%) 
           fs: ext3 dev: /dev/sda1 label: /daten1 uuid: 7f579515-fb23-4ef2-a877-4e6865748cd7 
           ID-6: /media/_daten3 raw size: 42.48 GiB size: 41.69 GiB (98.14%) 
           used: 14.33 GiB (34.4%) fs: ext3 dev: /dev/sda7 label: /daten3 
           uuid: c1bc867a-ec28-436d-831b-e47f334471ce 
           ID-7: /media/_daten4 raw size: 3.00 GiB size: 2.89 GiB (96.35%) used: 1.12 GiB (38.9%) 
           fs: ext3 dev: /dev/sda8 label: /daten4 uuid: 556a43c4-118c-4bb5-baa2-7c997faea6da 
           ID-8: /media/_home raw size: 20.00 GiB size: 19.56 GiB (97.80%) used: 16.93 GiB (86.6%) 
           fs: ext3 dev: /dev/sda5 label: /home uuid: 94021be3-c160-4166-a151-92ad72b26f9a 
           ID-9: /media/antiX raw size: 10.00 GiB size: 9.78 GiB (97.80%) used: 5.37 GiB (54.9%) 
           fs: ext4 dev: /dev/sda6 label: antiX uuid: a6852dda-0c34-4c4f-8efc-5d458cbaaeec 
           ID-10: /media/antiX-uefi raw size: 50.0 MiB size: 49.9 MiB (99.77%) 
           used: 6.0 MiB (12.1%) fs: vfat dev: /dev/sdb2 label: antiX-uefi uuid: 01BA-8055 
           ID-11: /media/sda10 raw size: 7.51 GiB size: 7.27 GiB (96.77%) used: 5.95 GiB (81.8%) 
           fs: ext4 dev: /dev/sda10 label: N/A uuid: 0eb91a9b-ea52-4f5b-9140-5a06f6f73d1d 
           ID-12: swap-1 size: 2.16 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60) 
           cache pressure: 50 (default 100) dev: /dev/sda9 label: N/A 
           uuid: 2d151628-e6f1-4e23-a8a6-7820d17b8a14 
Unmounted: ID-1: /dev/sda2 size: 1 KiB fs: <root required> label: N/A uuid: N/A 
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 speed: 480 Mb/s 
           chip ID: 1d6b:0002 
           Device-1: 1-3:3 info: Alcor Micro Flash Drive type: Mass Storage driver: usb-storage 
           interfaces: 1 rev: 2.1 speed: 480 Mb/s chip ID: 058f:6387 serial: <filter> 
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
           Device-2: 2-2:2 info: Pixart Imaging type: Mouse,Keyboard driver: hid-generic,usbhid 
           interfaces: 2 rev: 2.0 speed: 12 Mb/s chip ID: 093a:2533 
           Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
           Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http: //ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/buster buster main nonfree nosystemd
           Active apt repos in: /etc/apt/sources.list.d/buster-backports.list 
           1: deb http: //deb.debian.org/debian buster-backports main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http: //ftp.de.debian.org/debian/ buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http: //ftp.de.debian.org/debian/ buster main contrib non-free
           2: deb http: //security.debian.org/ buster/updates main contrib non-free
           No active apt repos in: /etc/apt/sources.list.d/onion.list 
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Processes: CPU top: 5 
           1: cpu: 24.0% command: yad pid: 15523 mem: 22.9 MiB (1.1%) 
           2: cpu: 2.4% command: xorg pid: 5374 mem: 64.3 MiB (3.2%) 
           3: cpu: 0.6% command: icewm pid: 5657 mem: 17.4 MiB (0.8%) 
           4: cpu: 0.5% command: conky pid: 5761 mem: 9.20 MiB (0.4%) 
           5: cpu: 0.1% command: rox pid: 5674 mem: 20.4 MiB (1.0%) 
           Memory top: 5 
           1: mem: 64.3 MiB (3.2%) command: xorg pid: 5374 cpu: 2.4% 
           2: mem: 25.3 MiB (1.2%) command: roxterm pid: 11117 cpu: 0.0% 
           3: mem: 22.9 MiB (1.1%) command: yad pid: 15523 cpu: 24.0% 
           4: mem: 20.4 MiB (1.0%) command: rox pid: 5674 cpu: 0.1% 
           5: mem: 17.4 MiB (0.8%) command: icewm pid: 5657 cpu: 0.6% 
Info:      Processes: 123 Uptime: 1h 07m Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: 
           gcc: 8.3.0 alt: 8 Client: IceWM v: 2.2.1 inxi: 3.0.36 

Best regards
Robin

Windows is like a submarine. Open a window and serious problems will start.

[Anonymous]

“beta 2” is available for testing
https://gitlab.com/skidoo/slimski/-/blob/master/slimski_1.5.0~b2_amd64.deb

The program looks for “/etc/slimski.local.conf” and, if not present, falls back to loading “/etc/slimski.conf”.

Via conf file, sysadmin can elect to separately enable/disable use of each “special username” (exit,systemhalt,reboot,etc).

Four themes are provided for the purpose of testing.
Within the themes/default directory, locale-specific themefiles are provided for all of the 62 LANGs offered in the antiX legacy boot menu.

To test the autoloading of locale-specific theme variants (for example, Spanish)
from within a desktop session, you can use the commandstring
LANG=”es_ES.UTF-8″ slimski -p default
and
to test from boot, you can choose Spanish (or other) from the legacy liveboot menu, or manually append lang=yourlang to the bootline

The included theme layouts are “sloppy” (careless x/y coordinates assigned for each of the message strings) but demonstrate that 5 “cust” message slots, with customizable {x/y position,color,fontface,fontattributes} are available.

Additional configurable “F2–F12” slots are available for custom messages (and/or commands)

If you want to use xvkdb virtual keyboard along with slimski, assign it (its executable path) to the “popfirst_cmd=” line within the slimski.conf

The conf file contains verbose inline descriptions for most (if not all of) the non-theme-related available optoins. Separate documentation related to theming is installed to /usr/share/doc/slimski/

Lessons learned:

— The beta1 failure to load via initscript deamonmode was due to my presumption that the LANG env var already exists when the initscript runs. Nope, so the initscript (now) consults /proc/cmdline and sets the envvar if lang= was specified on the bootline.

— A small (as seen in “default” theme) panel area cannot accomodate “locale-specific” messages. (consider: “Username” vs “nombre de usuario” ~~ the same, fixed, x-coordinate offset is not be suitable for variable-length strings.)

— Initially, due to “significant differences in features and conf option names”, renaming the program seemed to me advisable toward precluding user confusion. However, the hardcoded name “slim” is entrenched in build-iso and in various antiX scripts spread across multiple packages.

.
The program+docs should stand (or fail) on their own merit. Any aspect of the program which does not “work as described” in the documentation is a reportable bug. Anything unclear in the documentation, or absent from the documentation, is a “documentation request”. I’ll push+announce further versioned builds if any significant issues are reported.

edited to add:

The packaged theme files (including localized variants) should be regarded as “placeholders”.
It would be pointless to tweak the exact details and content of these
until/unless
testers find the program to be a suitable “working solution”
and
the antiX devs decide to use this program to replace the current SLiM

[Member Robin]

OK, my previous statement was outdated, since I had installed on the other antiX 17.4.1 system running on athlon XP hardware a more recent version meanwhile. (I was sure I had, but had to recollect the details, searching for the notes I took about the installation.)
So here you are another one, functioning, proven to work rock stable and with long uptime, and maybe someone can profit from the data.

sudo apt-get install virtualbox
The most recent version present on antiX installs,
but in the end of installation it fails to modprobe vboxdrv:
dmesg |tail shows:

	[3457526.728164] vboxdrv: loading out-of-tree module taints kernel.
	[3457526.740810] vboxdrv: Found 1 processor cores
	[3457526.741396] vboxdrv: Requires SSE2 (cpuid(0).EDX=0x383f9ff)

Specific to athlon thunderbird and XP is that it does support SSE1 only.

According to Oracle database
SSE2 is required starting with VirtualBox version 5.2.10 and version 5.1.24.

The latest Version NOT requiring SSE2 (and running with SSE1 only) is 5.2.8, which can be found at
https://www.virtualbox.org/wiki/Download_Old_Builds_5_2
Following files are required:
https://download.virtualbox.org/virtualbox/5.2.8/virtualbox-5.2_5.2.8-121009~Debian~stretch_i386.deb
https://www.virtualbox.org/download/hashes/5.2.8/SHA256SUMS
https://download.virtualbox.org/virtualbox/5.2.8/Oracle_VM_VirtualBox_Extension_Pack-5.2.8.vbox-extpack
First check whether the files were downloaded without errors:
shasum -a 256 -c SHA256SUMS

apt-get --purge autoremove virtualbox
to remove the nonfunctional virtualbox version from the system

apt-get install /<path>/virtualbox-5.2_5.2.8-121009~Debian~stretch_i386.deb
apt-get install libsdl-ttf2.0-0
modprobe vboxdrv

Add yourself (any user) to group “vboxuser”.

In case you have existing virtual machines you need to register them, e.G. your existing XP box:
registervm '/<path>/WinXP.vbox'

Before the guest will be able to start you may need to add privileges for the folders containing .vbox and .vdi files as well as for the files itself. (I belive it was necessary to alow “read”, “write” and “execution” for “user” and “root” at least, but maybe “other” had to get the privileges also to make it work.)

And you’ll need to add the extension-pack from above from within virtualbox (entry is to be found in virtualbox menu “settings”)

Since I needed an LPT from within Guest system port I had to follow the steps described in this guidance in Virtualbox-Forums
In short:
To activate Virtualbox LPT port support for a virtual machine use

VBoxManage modifyvm "Name_of_VM" --lptmode1 "/dev/parport2"
VBoxManage modifyvm "Name_of_VM" --lpt1 0x378 7

once. Adjust the settings according to your needs. And before each start of virtualbox make sure lp module is unloaded:
sudo rmmod lp
Otherwise no Virtual machine configured as described above will be able to fire up at all.
After this the Parallelport is present and usable in the virtual machine, but it might be necessary to configure it manually inside the guest (only in case it is not autodetected).
After virtualbox is powered down you might want to
‘modprobe lp’
again in order to make the port available to antiX again.

Info from VirtualBox graphical User Interface:
Version 5.2.8 r121009 (Qt5.7.1)
Copyright © 2018 Oracle Corporation and/or its affiliates. All rights reserved.

——————————————————————————————–
Complete System info:

System:    Host: Buche Kernel: 4.9.160-antix.2-486-smp i686 bits: 32 compiler: gcc v: 6.3.0 
           Desktop: IceWM 1.4.2 info: icewmtray dm: SLiM 1.3.4 
           Distro: antiX-17.4.1_386-full Helen Keller 28 March 2019 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Desktop Mobo: ECS model: K7S5A serial: <filter> BIOS: American Megatrends 
           v: 07.00T date: 04/02/01 
Memory:    RAM: total: 1.97 GiB used: 149.2 MiB (7.4%) 
           RAM Report: permissions: Unable to run dmidecode. Are you root? 
PCI Slots: Permissions: Unable to run dmidecode. Are you root? 
CPU:       Topology: Single Core model: AMD Athlon XP 2000+ bits: 32 type: UP arch: K7 Palomino+ 
           family: 6 model-id: 8 stepping: 1 microcode: N/A L2 cache: 256 KiB bogomips: 3319 
           Speed: 1660 MHz min/max: N/A Core speed (MHz): 1: 1660 
           Flags: 3dnow 3dnowext 3dnowprefetch cmov cx8 de fpu fxsr mca mce mmx mmxext msr mtrr 
           pae pat pge pse pse36 sep sse syscall tsc vme vmmcall 
           Vulnerabilities: Type: l1tf status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline 
GraLimited driver: radeon 
           v: kernel bus ID: 01:00.0 chip ID: 1002:5960 phics:  Device-1: AMD RV280 [Radeon 9200 PRO] vendor: PC Partner 
           Display: server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1152x864~75Hz 
           OpenGL: renderer: Mesa DRI R200 (RV280 5960) x86/MMX+/3DNow!+/SSE DRI2 
           v: 1.3 Mesa 13.0.6 direct render: Yes 
Audio:     Device-1: Creative Labs EMU10k1 [Sound Blaster Live! Series] driver: snd_emu10k1 
           v: kernel bus ID: 00:0d.0 chip ID: 1102:0002 
           Sound Server: ALSA v: k4.9.160-antix.2-486-smp 
Network:   Device-1: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet driver: sis900 
           v: kernel port: d400 bus ID: 00:03.0 chip ID: 1039:0900 
           IF: eth1 state: down mac: <filter> 
           Device-2: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too 
           v: 0.9.28 port: d000 bus ID: 00:0b.0 chip ID: 10ec:8139 
           IF: eth0 state: unknown speed: 100 Mbps duplex: full mac: <filter> 
           IP v4: <filter> scope: global broadcast: <filter> 
           IP v6: <filter> scope: link 
           Device-3: Digital Equipment DECchip 21041 [Tulip Pass 3] driver: de2104x v: 0.7 
           port: c800 bus ID: 00:0f.0 chip ID: 1011:0014 
           IF: eth2 state: up speed: 10 Mbps duplex: half mac: <filter> 
           IP v6: <filter> scope: link 
           WAN IP: <filter> 
Drives:    Local Storage: total: 253.10 GiB used: 110.62 GiB (43.7%) 
           ID-1: /dev/sda vendor: Samsung model: SP8004H size: 74.56 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 0-60 scheme: MBR 
           ID-2: /dev/sdb vendor: Western Digital model: WD1600JB-00GVC0 size: 149.05 GiB 
           block size: physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 2D08 
           scheme: MBR 
           ID-3: /dev/sdc type: USB model: SMI USB DISK size: 29.49 GiB block size: 
           physical: 512 B logical: 512 B serial: <filter> rev: 1100 scheme: MBR 
           Floppy-1: /dev/fd0 
           Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD-RAM GSA-H55L rev: 1.03 
           dev-links: cdrom,cdrw,dvd,dvdrw 
           Features: speed: 48 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram 
           state: running 
RAID:      Message: No RAID data was found. 
Partition: ID-1: / raw size: N/A size: 1.56 GiB used: 730.6 MiB (45.8%) fs: overlay 
           source: ERR-102 label: N/A uuid: N/A 
           ID-2: /home raw size: 1.98 GiB size: <root required> used: <root required> fs: ext4 
           dev: /dev/loop1 label: N/A uuid: 51666dbe-9ea1-4171-a801-ab329210a8b5 
           ID-3: /live/boot-dev raw size: 29.49 GiB size: <root required> used: <root required> 
           fs: vfat dev: /dev/sdc1 label: antiX-17 uuid: 8376-6F4E 
           ID-4: /live/linux raw size: 2.12 GiB size: <root required> used: <root required> 
           fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A 
           ID-5: /media/_home raw size: 120.05 GiB size: 118.04 GiB (98.33%) 
           used: 109.90 GiB (93.1%) fs: ext4 dev: /dev/sdb3 label: /home 
           uuid: 8bd14a95-8fa7-4ba9-8505-8c445399c501 
           ID-6: /media/sr0 raw size: 658.0 MiB size: 657.8 MiB (99.97%) used: 657.8 MiB (100.0%) 
           fs: iso9660 block size: 2048 B dev: /dev/sr0 label: antiXlive 
           uuid: 2019-03-28-16-55-22-00 
           ID-7: swap-1 size: 4.00 GiB used: 2.7 MiB (0.1%) fs: swap swappiness: 10 (default 60) 
           cache pressure: 50 (default 100) dev: /dev/sdb1 label: N/A 
           uuid: 61a23275-9f60-46f9-bb71-685c827d64e0 
Unmounted: ID-1: /dev/sda1 size: 3.00 GiB fs: ntfs label: SYSTEM uuid: AE48CEA548CE6AA1 
           ID-2: /dev/sda2 size: 1 KiB fs: <root required> label: N/A uuid: N/A 
           ID-3: /dev/sda3 size: 3.00 GiB fs: ntfs label: Daten_1 uuid: 8A6204B46804A0D5 
           ID-4: /dev/sda4 size: 10.54 GiB fs: ntfs label: Daten_3 uuid: A2B8DC24B86BF52F 
           ID-5: /dev/sda5 size: 3.00 GiB fs: ntfs label: Daten_6 uuid: CE44BDD993409532 
           ID-6: /dev/sda6 size: 15.01 GiB fs: ntfs label: Daten_4 uuid: 13BD6D7EEB87F56C 
           ID-7: /dev/sda7 size: 40.00 GiB fs: ntfs label: Daten_2 uuid: B45ED73B26001395 
           ID-8: /dev/sdb2 size: 25.00 GiB fs: ext4 label: Daten_5 uuid: d7828740-745a-4bb8-870b-5a1bab6f61c3
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 speed: 480 Mb/s 
           chip ID: 1d6b:0002 
           Hub: 1-2:2 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip ID: 05e3:0608 
           Device-1: 1-3:3 info: Silicon Motion - Taiwan (formerly Feiya ) type: Mass Storage 
           driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s chip ID: 090c:3267 
           serial: <filter> 
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
           Hub: 3-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
           Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
           Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
Sensors:   System Temperatures: cpu: 43.0 C mobo: 25.0 C 
           Fan Speeds (RPM): cpu: 1739 fan-1: 2812 fan-3: 1326 
           Voltages: 12v: N/A 5v: N/A 3.3v: N/A vbat: 3.31 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http: //ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/stretch stretch main nosystemd nonfree
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http: //ftp.de.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http: //ftp.de.debian.org/debian/ stretch main contrib non-free
           2: deb http: //security.debian.org/ stretch/updates main contrib non-free
           No active apt repos in: /etc/apt/sources.list.d/onion.list 
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Processes: CPU top: 5 
           1: cpu: 20.0% command: yad pid: 10747 mem: 22.1 MiB (1.0%) 
           2: cpu: 6.2% command: gtkdialog pid: 10690 mem: 21.9 MiB (1.0%) 
           3: cpu: 4.5% command: xorg pid: 4545 mem: 42.6 MiB (2.1%) 
           4: cpu: 2.4% command: antix-buche-info.txt started by: geany pid: 9567 mem: 31.7 MiB (1.5%) 
           5: cpu: 2.2% command: nmbd pid: 4517 mem: 7.75 MiB (0.3%) 
           Memory top: 5 
           1: mem: 48.2 MiB (2.3%) command: spacefm pid: 5715 cpu: 0.8% 
           2: mem: 42.6 MiB (2.1%) command: xorg pid: 4545 cpu: 4.5% 
           3: mem: 31.7 MiB (1.5%) command: antix-buche-info.txt started by: geany pid: 9567 cpu: 2.4% 
           4: mem: 22.1 MiB (1.0%) command: yad pid: 10747 cpu: 20.0% 
           5: mem: 21.9 MiB (1.0%) command: gtkdialog pid: 10690 cpu: 6.2% 
Info:      Processes: 145 Uptime: 31m Init: SysVinit v: 2.88 runlevel: 5 default: 5 Compilers: 
           gcc: 6.3.0 alt: 6 Client: shell wrapper v: 4.4.12-release inxi: 3.0.29 

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

Windows is like a submarine. Open a window and serious problems will start.

[Member seaken64]

dukester wrote:

I need to re-install antiX to 64 bit version. Doing some homework reading first.
I want a traditional Linux HDD install on a 1Tb SATA drive.
How do I get that to happen with antiX? I’m thinking antiX-core and then `apt install’ what I need/want.

Also, I confused about all the offerings on the antiX mirrors!
what is runit-buster and runit-sid? and plain old sid/ ? TIA

find and download the latest version 19.3 FULL in 64-bit then create your Live DVD or Live USB from that ISO file and reboot from that Live system. Install that to your hard drive.

DO NOT use the Core version. It will not give you what you want. It is meant for “builders” who want to build up their own system from a bare bones starting point.

The “plain old” sid would be the current sid from Debian. Sid is an unstable version meant for testing, antiX is based on Debian and you should just start with the “plain old” antiX FULL 19.3 which is based on the STABLE version of Debian.

runit is an alternate initialization setup as opposed to the standard init system used in antiX which is SysInit. Just start with the standard antiX FULL and go from there. You will learn about those other options after you have got your feet wet in the standard antiX.

Again, the “standard” antiX is antiX 19.3 FULL. Use the 64-bit version. The 32-bit version is for older computers.

seaken64

[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 

I’ve got an iso ready on an SD card. Can I re-install from the built-in SD card reader while running antiX.
Of course, there will be a reboot, but can I do this?

--
dukester

[Member andyprough]

BobC wrote:

If you still have the .iso file you used to burn the USB for the Dell B130 laptop, you can burn that to the DVD for the other machine. That way you could run the same software on both. If it happens to have over 4 gb of memory (unlikely I think), you should use the 64 bit version instead.

This from=usb option saved my bacon today. I was trying to work from a 2007 Acer computer that wouldn’t boot from the USB and all I had available to burn were CD-R’s with 700mb max size – too small for a full or a base version of 32-bit antiX. So I burned the smaller antiX net install version to CD, copied the 32-bit base antiX to my USB, booted from the net install CD and chose the “from=usb” option from the F4 menu. Like magic it booted up the antiX base version on the USB.

plop boot manager wouldn’t work on this machine for some reason (or I wasn’t smart enough to get it working), so using the antiX from=usb option was really the only way to get up and running with a live USB without resorting to something like Puppy Linux.

[Moderator caprea]

Hi ddc11 and welcome to antiX and the forum!
I agree with BobC, there’s no need to take an older version of antiX.
If the PC has a DVD-drive there will be no difficulty. You can boot from DVD or if you take the same download for the DVD as you took for the usb-stick you can try the ” from=usb ” trick.It’s one of the options under F3 or F4 on the live-boot menu.The boot first starts from the DVD and then magically continues from usb.

For burning a bootable DVD with Xfburn you have to burn it as an iso.