-
Search Results
-
I dont know if am doing something wrong. i used antix-snapshot gui utility to create iso image of my installed system, the process completed without errors. I also used live-usb-maker to create bootable usb from the iso also without error but when i tried booting up the iso; i was greeted with the error “cannot find /antix/linuxfs”. the only options is to either type “p” to shutdown or “r” to reboot.
I have also used iso-snapshot and refractasnapshot packages with the same outcome. I need to have a backup of my system to avoid complete reinstall. I need help Please.
#inxi:
CPU: Dual Core Intel Celeron N2840 (-MCP-) speed/min/max: 500/500/2582 MHz
Kernel: 4.9.160-antix.1-amd64-smp x86_64 Up: 57m
Mem: 802.0/1890.6 MiB (42.4%) Storage: 465.76 GiB (54.0% used) Procs: 142
Shell: bash 4.4.12 inxi: 3.0.29#neofetch:
OS: antiX 17.4.1 x86_64
####### Model: 80G0 Lenovo G50-30
########### Kernel: 4.9.160-antix.1-amd64-smp
############# Uptime: 59 minutes
############### Packages: 1281
################ Shell: bash 4.4.12
################# Resolution: 1920×1080
##################### WM: Sawfish
##################### Theme: Adwaita [GTK3]
################# Icons: Adwaita [GTK3]
CPU: Intel Celeron N2840 (2) @ 2.5GHz
GPU: Intel Integrated Graphics
Memory: 883MB / 1890MBTopic: antix +s6/66 -sysv -runit
1st some history/background:
Back some time ago an alternative to sysv was developed called daemontools and people liked it. From it runit was cloned, very similar but started from scratch, to be as small, as light, as simple, and as responsive as hw itself. Runit set some goals for its development, kept being refined and eliminating any bugs, it worked on as many architectures as people could get their hands on, and the chief runit man decided to put it to bed.
While runit was running s6 (and a few others) took different aims based on the same daemontool idea. Runit was being overly simplistic and therefore limited, s6 was designed not to just handle the needs of a pc or a pocket device but be able to handle the complexities of the largest machines conceived (I think). While runit was placed to rest, it is being kept alive and polished by Void, s6 keeps on maturing. I believe it is nearing 10y in development. The two are like comparing a 70s local race car to a 24hr LeMans racer of the future.
66 is the management front for s6 that works for common mortals. Using s6 out of the box (from skarnet not debian) requires much previous knowledge and some more studying of s6. It is not a plug and play system. 66 makes it plug and play.So with the courage that anti provided (to publish a runit-antiX iso) and with admitted little investigation I undertook the task of converting a 19 installation to s6 and 66. I also had the faith it would work since the 66 developer/s would get a quick success from trying it (adelie, void, alpine, funtoo, devuan) and since 66 is native in void now, I had succeeded in void myself. But debian is a very different monster.
The first mistake was not to study antiX-runit as closely. I realized right away that it was not like void and didn’t spend time to see how it actually worked (with sysvinit on its side).Basically you get the installation running, as you want it to, and then exit and work from chroot. This helps if you don’t want to crash reboot/shutdown since what is doing this properly will not be there and what replaces it will not work with the old system in memory. So there would be a chance of corrupting data on all mounted volumes when you just pull the plug on it (sort of speak).
The one way is to begin by struggling to make what is on debian as s6, and removing runit/sysvinit.
The other way (suggested by the 66 developer) is to leave things as they are and just replace /usr/bin/init after you installed the proper software. Debian has first incorporated execline in a different place than it was designed to work by skarnet, so s6-rc can’t work. Also, s6 on buster and testing is 2 versions back, the real current software is 2.9 not 2.7 and it is only on sid, still incomplete and wrongfully packaged. You can install it (from sid) and take all its tools and move them/copy them to /usr/bin/. Then the s6 skarnet libraries are not completely adopted, s6-linux-utils netw..-utils, etc. have been left out. So here is a set of instructions on how to properly install the real software from skarnet and obarun (66) into your antix. After having some minor issues the 66 developer (Eric Vidal) came to rescue me and here is what he advised as a complete procedure:– update and install git with apt (if it is not there already, I don’t remember)
Note: % (user) # (root)
% cd /tmp
% git clone https://github.com/skarnet/skalibs
% git clone https://github.com/skarnet/execline
% git clone https://github.com/skarnet/s6
% git clone https://github.com/skarnet/s6-rc
% git clone https://github.com/skarnet/s6-linux-utils
% git clone https://github.com/skarnet/s6-portable-utils
% git clone https://framagit.org/obarun/oblibs
% git clone https://framagit.org/obarun/66
% git clone https://framagit.org/obarun/66-tools
% git clone https://framagit.org/obarun/boot-66serv
% git clone https://framagit.org/pkg/observice/tty_instance-66serv(remember to return to /tmp after each step/group)
% cd skalibs
% ./configure –bindir=/usr/bin
% sudo make install% cd ../execline
% ./configure –bindir=/usr/bin –with-lib=/usr/lib/skalibs
% sudo make install% cd ../s6
% ./configure –bindir=/usr/bin –with-lib=/usr/lib/skalibs –with-lib=/usr/lib/execline
% sudo make install% cd ../s6-rc
% ./configure –bindir=/usr/bin –with-lib=/usr/lib/skalibs –with-lib=/usr/lib/execline –with-lib=/usr/lib/s6
% sudo make install% cd ../s6-linux-utils
% ./configure –bindir=/usr/bin –with-lib=/usr/lib/skalibs
% sudo make install% cd ../s6-portable-utils
% ./configure –bindir=/usr/bin –with-lib=/usr/lib/skalibs
% sudo make install% cd ../oblibs
% ./configure –bindir=/usr/bin –with-lib=/usr/lib/skalibs –with-lib=/usr/lib/execline
% sudo make install% cd ../66
% ./configure –bindir=/usr/bin –with-lib=/usr/lib/skalibs –with-lib=/usr/lib/execline –with-lib=/usr/lib/s6 –with-lib=/usr/lib/s6-rc –with-lib=/usr/lib/oblibs
% sudo make install% cd ../66-tools
% ./configure –bindir=/usr/bin –with-lib=/usr/lib/skalibs –with-lib=/usr/lib/execline –with-lib=/usr/lib/oblibs
% sudo make installBe carefull of the single quote at –KEYMAP option. Also, you can omit all options except –bindir and edit manually the /etc/66/boot.conf. It’s up to you – in this case the hostname is set as 66 and TZ is out in the middle of nowhere 🙂 your keymap is gr in honor of “Marinos Antipas” 😛
% cd ../boot-66serv
% ./configure –bindir=/usr/bin –HOSTNAME=66 –TZ=Pacific/Noumea –KEYMAP=’!gr’
% sudo make install% cd ..
% sudo cp tty_instance-66serv/trunk/tty@ /usr/share/66/serviceNow you are ready to configure the system:
– Edit the /etc/66/init file and add the -m option to 66-boot as:
#!/usr/bin/execlineb -P
66-boot -mMake copies of skeleton files at /usr/sbin (debian use /usr/sbin)
# cp -f /etc/66/{init,reboot,poweroff,shutdown,halt} /usr/sbin
There is a tree of services that are needed to boot the system (mount file systems, checks fs, set hostname, devices, etc.) that are all inside the boot-66serv. You simply create a tree (bundle of services) named boot and enable the boot bundle in it as a single service.
# 66-tree -n boot
# 66-enable -t boot bootThen you create at least one tree, by convention it is called root, and enable ttys and services dhcpcd, dbus, wpa_supplicant etc.
# 66-tree -cnE root
# 66-enable tty@tty{1,2,3,4,5} dhcpcd .. etc.dhcpcd works out of the box as it is in obarun, dbus needs some editing of dbus syntax as used on antix, slim (if you want to run it) I have a copy of a service file below that should work. Anything else you have to see the template of a service and write one. Anything that is already made is on https://framagit.org/pkg/observice
You are done you can now boot if you are on chroot or you can try to reboot with this command below:
# 66-hpr -r -f
Extra configuration
create the slim service at /usr/share/66/service/slim. This is frontend :
[main]
@type = classic
@description = “slim daemon”
@user = ( root )[start]
@build = auto
@execute = (slim -d)enable it
# 66-enable slim
For how and why things work the way they do see the wiki at obarun (last link).
Sources:
http://cr.yp.to/daemontools.html
http://smarden.org/runit/
https://skarnet.org/software/s6/
https://web.obarun.org/software
https://wiki.obarun.org/doku.php?id=66introPS: This should work equally on devuan, mx, or anything debian based, but it is meant for antix which is trully a non-systemd distribution and not something of a gray shade.
PS2: As s6 and 66 is not handled by apt don’t expect it to magically be upgraded when new editions come out, so keep an eye on framagit for 66 and github/skarnet for s6 updates. If you knew nothing about init and service supervision before this, give 66 a couple of weeks and it will all make sense. If you do know about them, good for you! Tell us how it compares.
PS3: Will this work on an antiX live system? I don’t know yet, you tell me or I’ll tell you when I try it.
PS4: This is all written in C and is meant to be portable anywhere and this far it seems to be. Void has as many or more architectures it supports and two different C libraries (gnu and musl) and all their software is crosslinked to work on all combinations. Debian twisted and scraped s6 around and didn’t even apply it to all architectures, which are all glibc. Arch is all amd64 and glibc, nothing else. It is good to keep such things in mind … you can like manjaro and mint all you want but what have they contributed to development?
PS5 (final): Expect computer scientists and mathematicians in universities to really appreciate s6 and 66. Expect state agency executives and large corporations to continue liking systemd “and keep using the irrational argument” <systemd is better than sysvinit> as an excuse. The future is here!
- This topic was modified 3 years, 4 months ago by anticapitalista.
- This topic was modified 3 years, 4 months ago by fungalnet.
anti-X - Adélie - obarun - systemd Free Space
Greetings All,
attempting to install VLC and Audacious using apt-get, downloads the files and then locks up the system completely during the install.
using synaptic for the same S/W returns a broken package error and will not install and does not freeze the system.
over several attempts to resolve the above issue, i have lost the setting for changing work spaces via mouse scroll (not sure where to find that setting), the ‘man’ pages have become farkled and attempting to reinstall them via apt-get locks up the system, and sleep does not work, nor does shutdown actually power off the system.
using apt-get or synaptic for other S/W works as expected.
two other issues: screenlight does not work and wifi is not found with connman (wifi greyed out).
Thank YOU ALL in advance for any suggestions in resolving these issues.
fresh full install of Antix19 on an MSI Alpha15 total AMD system, machine specs below:
inxi -r Repos: Active apt sources in file: /etc/apt/sources.list.d/cisofy-lynis.list deb https://packages.cisofy.com/community/lynis/deb/ stable main Active apt sources in file: /etc/apt/sources.list.d/debian.list deb http://ftp.us.debian.org/debian/ jessie main contrib non-free deb http://security.debian.org/ jessie/updates main contrib non-free deb http://download.videolan.org/pub/debian/stable/ / deb-src http://download.videolan.org/pub/debian/stable/ / deb http://security.debian.org/ testing/updates non-free contrib main$ inxi -zv7
System: Host: rookery Kernel: 4.9.193-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Fluxbox 1.3.5 dm: SLiM 1.3.6 Distro: antiX-19_x64-full Marielle Franco 16 October 2019 base: Debian GNU/Linux 10 (buster) Machine: Type: Laptop Mobo: Micro-Star model: MS-16U6 v: REV:1.0 serial: <filter> BIOS: American Megatrends v: E16U6AMS.106 date: 10/09/2019 Memory: RAM: total: 13.64 GiB used: 2.46 GiB (18.1%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. CPU: Topology: Single Core model: AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx bits: 64 type: UP arch: Zen+ rev: 1 L2 cache: 512 KiB bogomips: 4591 Speed: 2296 MHz min/max: N/A Core speed (MHz): 1: 2296 Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1 bmi2 bpext clflush clflushopt clzero cmov cmp_legacy constant_tsc cpb cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb irperf lahf_lm lbrv lm mca mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_l2 perfctr_nb pfthreshold pge pni popcnt pse pse36 rdrand rdseed rdtscp rep_good sep sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 succor svm svm_lock syscall tce topoext tsc tsc_scale vmcb_clean vme vmmcall wdt xgetbv1 xsave xsavec xsaveopt xsaves Graphics: Device-1: AMD vendor: Micro-Star MSI driver: N/A bus ID: 03:00.0 chip ID: 1002:7340 Device-2: AMD vendor: Micro-Star MSI driver: N/A bus ID: 07:00.0 chip ID: 1002:15d8 Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1920x1080~N/A OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1 direct render: Yes Audio: Device-1: AMD vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 03:00.1 chip ID: 1002:ab38 Device-2: AMD driver: N/A bus ID: 07:00.5 chip ID: 1022:15e2 Device-3: AMD vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 07:00.6 chip ID: 1022:15e3 Sound Server: ALSA v: k4.9.193-antix.1-amd64-smp Network: Device-1: Realtek vendor: AzureWave driver: N/A port: f000 bus ID: 05:00.0 chip ID: 10ec:c822 Device-2: Realtek vendor: Micro-Star MSI driver: r8169 v: 2.3LK-NAPI port: e000 bus ID: 06:00.0 chip ID: 10ec:2600 IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> IP v4: <filter> scope: global broadcast: <filter> IP v6: <filter> scope: link WAN IP: <filter> Use of uninitialized value $speed in pattern match (m//) at /usr/local/bin/inxi line 9083. Drives: Local Storage: total: 2.73 TiB used: 25.46 GiB (0.9%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB serial: <filter> rev: 2B2QEXM7 scheme: GPT ID-2: /dev/sda vendor: Seagate model: ST2000LX001-1RG174 size: 1.82 TiB speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: SDM1 scheme: GPT Message: No Optical or Floppy data was found. RAID: Message: No RAID data was found. Partition: ID-1: / size: 145.77 GiB used: 4.92 GiB (3.4%) fs: ext4 dev: /dev/sda3 label: rootantiX19 uuid: c2b63121-e2f2-44fc-98e5-915ee3bdfaaa ID-2: /boot size: 4.32 GiB used: 65.3 MiB (1.5%) fs: ext4 dev: /dev/sda1 label: boot uuid: 4a591ee3-44ca-4ed0-ab70-fd5014ce88c4 ID-3: /home size: 612.03 GiB used: 20.48 GiB (3.3%) fs: ext4 dev: /dev/sda4 label: homeantiX uuid: 580cc734-2384-41de-942b-f6d9e758c9d4 ID-4: swap-1 size: 343.44 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 label: swap uuid: a352ff3d-be07-4e57-b79d-f0dca1a156a8 Unmounted: ID-1: /dev/nvme0n1p1 size: 300.0 MiB fs: vfat label: SYSTEM uuid: 5E98-A22E ID-2: /dev/nvme0n1p2 size: 128.0 MiB fs: <root required> label: N/A uuid: N/A ID-3: /dev/nvme0n1p3 size: 68.85 GiB fs: ntfs label: Windows uuid: 8E0E99520E9933E5 ID-4: /dev/nvme0n1p4 size: 900.0 MiB fs: ntfs label: WinRE tools uuid: 062C99FD2C99E847 ID-5: /dev/nvme0n1p5 size: 241.21 GiB fs: vfat label: N/A uuid: D12B-D078 ID-6: /dev/nvme0n1p6 size: 301.40 GiB fs: ext4 label: N/A uuid: 2351cdc0-df06-412b-9ced-c617d8ad23b0 ID-7: /dev/nvme0n1p7 size: 318.76 GiB fs: ext4 label: N/A uuid: a2b64641-986d-4dbc-ae11-aa928c8caabe ID-8: /dev/sda2 size: 20.06 GiB fs: ntfs label: BIOS_RVY uuid: 8EC8A330C8A3160D ID-9: /dev/sda6 size: 723.14 GiB fs: ext4 label: futuremax uuid: 8e0067bc-22a5-48b1-9d3d-1d42df6deb75 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: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 speed: 10 Gb/s chip ID: 1d6b:0003 Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 Device-1: 3-1:2 info: N/A type: Video driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s chip ID: 5986:211c Hub: 3-2:3 info: Full speed (or root) Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip ID: 05e3:0608 Device-2: 3-2.1:4 info: N/A type: <vendor specific> driver: rtsx_usb,rtsx_usb_ms,rtsx_usb_sdmmc interfaces: 1 rev: 2.0 speed: 480 Mb/s chip ID: 0bda:0129 serial: <filter> Device-3: 3-2.2:5 info: N/A type: HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s chip ID: 1038:1122 Device-4: 3-2.3:6 info: N/A type: Mouse,Keyboard driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s chip ID: 0db0:0d10 Device-5: 3-2.4:7 info: N/A type: Bluetooth driver: btusb interfaces: 2 rev: 1.0 speed: 12 Mb/s chip ID: 13d3:3549 serial: <filter> Hub: 4-0:1 info: Full speed (or root) Hub ports: 1 rev: 3.1 speed: 10 Gb/s chip ID: 1d6b:0003 Sensors: Message: No sensors data was found. Is sensors configured? Info: Processes: 153 Uptime: 3h 57m Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: roxterm inxi: 3.0.36Topic: antiX-19 runit release
Thought I would see how this works.
antiX-19 base version (sort of), but with runit as the init system instead of SysVinit.
This is an official version of antiX-19 and though it is stable, it is a bit of an experiment.
Available in 32 and 64 bit.* Default kernel is 4.9.200
* based on antiX-base version, but with some changes
* live iso built using lz4 compression, which means a faster boot, but larger iso file size.
* IceWM only (fluxbox, JWM and herbstluftwm removed)
* plain IceWM is default window manager to keep RAM usage low – ie no rox ‘desktop’ meaning that no icons on the desktop (live boot though via F6 or installed under Desktop menu give Rox-IceWM and min-IceWM options)
* spacefm removed
* uses ceni for networking – no connman installed
* there are bugs especially when running live eg on boot you will see some sequence of green ‘OK’s and reboot will actually shutdown the computer.
* as is the case with base versions of antiX, synaptic is not installedIf you find on installation that no drives are shown in /media, then delete the /etc/fstab file and type this in a terminal
sudo make-fstabGive it a try – post your impressions/comments/bugs over at antiX forums.
Files here:
Enjoy!
anticapitalista
Thessaloniki, 10 December 2019.
- This topic was modified 3 years, 5 months ago by anticapitalista. Reason: added more info
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.