Search Results for 'boot from iso'

[Member KouDy]

caprea wrote:

This is not normal behaviour, you should be able to upgrade the live-usb-stick.
How did you create the usb-stick?
Did you check the md5sum ?

I used PowerISO (free version), also tried the Universal-USB-Installer. md5sum is matching on the iso yes.
Do you have any recommended software?

Anonymous wrote:

I have googled something after this Alix3D3 board…

The way you want to install antiX17 doesn’t work at all!

There are extensive preparations of the CF card; installation of the OS; BIOS of the Alix etc. necessary, before(!) you can transfer the CF card into the Alix.

Unfortunately I found only current German instructions for this… and I have no idea.
https://wiki.ubuntuusers.de/Archiv/Alix/
https://wiki.ubuntuusers.de/Alix/CF-Bootmedium_erstellen/
https://www.pcengines.ch/alix.htm

I am not sure if this applies to 3D3 because it has normal bios, boots like regular PC. For sure i will try to go through those links with some translator.

I am also going through the videos. Perhaps i will find something there.

• This reply was modified 4 years, 6 months ago by KouDy.
• This reply was modified 4 years, 6 months ago by KouDy.

[Anonymous]

For further reading, here’s a list of articles which present various criticisms of systemd

EWONTFIX – Broken by design: systemd
EWONTFIX – systemd has 6 service startup notification types, and they’re all wrong
systemd: The Biggest Fallacies
Debian Bug #762194 “Automatic switch to systemd on wheezy->jessie upgrades”
“On the architecture of systemd, I have a legitimate concern with the scope…” article, plus infographic
Erosion of Choice?
Combatting revisionist history (debian forum: 2015)
Debian init system debate: arguments against systemd (and upstart)
systemd: harbinger of the linux apocalypse infoworld.com article
(anti) systemd articles by Steve Litt
Laurent Bercot’s (anti) systemd page
preserve freedom of choice of init systems
systemd: Please, No, Not Like This
The bad side of systemd: two recent systemd failures
“…There are several problems with systemd unrelated to code quality…”
systemd is the best example of Suck (explained by suckless.org)
Patrick’s playground – systemd propaganda: It’s a crap!
Fast boot? in-the-wild discussion (workarounding slow OOTB systemd boot) “Performance tuning the boot process”
systemd: Assumptions, Bullying, Consent
Open letter to the Linux World
an experience shared by software engineer on systemd
systemd pitfalls (July 2017)
systemd Or Poettering, Name Your Poison
another list of technical points explaining why systemd is bad (by boycottsystemd.org)
Ts’o and Linus And The Impotent Rage Against systemd
A realization that I recently came to while discussing the whole systemd controversy (by Theodore Ts’o)
systemd Forward Secure Sealing of System Logs Makes Little Sense
journald and rsyslog
What I don’t like about journald / Linux Journal
Why I dislike systemd
Top 5 systemd troubles – a strategic view for distros
systemd sucks (experience of galexander)
Lamest Vendor Response 2017 #PwnieAwards goes to Lennart Poettering for systems f*ckups photo
Structural and semantic deficiencies in the systemd architecture for real-world service management, a technical treatise
systemd requiring CAP_SYS_ADMIN weakening container safety in coreOS/rkt
Problems with systemd and Why I like BSD Init (by Randy Westlund)
Debian Bug #668001 “debootstrap: cant install systemd instead of sysvinit” (2014 mailing list thread, 100+ msgs)<br>
“systemd” and “zeitgeist” daemons as great security risks
A timesyncd total failure and systemd’s complete lack of debugability
Systemd’s DynamicUser feature is (currently) dangerous

[Anonymous]

Ask a simple question (or 2), receive a not-so-simple response…

( copypasting a portion of the page from http://without-systemd.org/wiki/index.php/Arguments_against_systemd )

systemd suffers from scope creep. It overreaches, way beyond providing an init system
^————————v
systemd provides an UEFI boot loader, systemd-boot (previously gummiboot)
systemd provides a login manager, systemd-logind
systemd provides a syslog daemon, systemd-journald
systemd provides a mount front-end, systemd-mount
The udev sources were merged into the systemd source tree.
systemd provides systemd.timer timer units, intended to replace cron and at
systemd provides a D-Bus client library, sd-bus
systemd developed an in-kernel D-Bus implementation (kdbus). They tried to get it merged into the kernel, failed, and are now trying again with BUS1.
systemd provides automount via systemd.automount to substitute autofs
systemd provides a caching DNS resolver, systemd-resolved
systemd provides a network manager and DHCP client, systemd-networkd
systemd provides a HTTP server for journal events, systemd-journal-gatewayd (can be disabled with remote compile option)
systemd functionality now even includes IP Forwarding, IP Masquerading & Basic Firewall Controls
systemd init requires (even on a server) a library for rendering QR codes

———————— Issues
fsck cannot be cancelled (used to be possible via C-c or c on the console). 7f110ff9b8, Fedora#719952
systemd defaults to Google’s DNS nameservers. e16cb2e4ef, Debian#761658
systemd defaults to Google’s NTP servers, which serve leap-smeared time. GitHub#437
systemd by default uses Predictable Network Interface Names, which are actually less predictable when you only have one interface per type.
systemd by default kills background processes after the user logs out. 97e5530cf2, Debian#825394
“In my view it was actually quite strange of UNIX that it by default let arbitrary user code stay around unrestricted after logout.” -Poettering[6]
As systemd depends on many files on a rootfs, in case of any problems with rootfs, it is not able to control processes and (cleanly) shutdown/reboot when Crtl-Alt-Del is pressed.[7]
systemd-resolved breaks the traditional glibc behavior by skipping a DNS server in all following queries, if it does not respond once. GitHub#5755, [8]

———————— Conceptional problems
Do not parse “debug” command line parameter – Response on LKML Response: That is the expected current behaviour, “debug” can cause “too many” messages to be useful anymore if things are broken.
journal ip anonymization — It’s very difficult to use systemd/journal on a privacy-aware system or infrastructure.

———————— Poor design
Among the systemd files is a filename that starts with a hyphen! – This causes all sorts problems as it will usually be interpreted as the start of a command option when used on the command line. You don’t even need to specify the filename for it to cause problems as it will affect commands that use globbing. Not to mention that the file in question, “-.slice”, they refer to as the “root slice” which causes confusion as the term “slice” has been used for decades as an alternative way of referring to a disk partition yet their usage is completely unrelated.
systemd mounted efivarfs read-write, allowing motherboard bricking via ‘rm’ See also No POST after rm -rf / – Lennart’s argument for mounting /sys/firmware/efi/efivars as read/write as a default behaviour doesn’t hold water. Yes it’s true that some tools may need to write to it but those tools are not needed for the general running of a system. efivars should not even be mounted as read-only by default. Those tools that need to write to efivars will generally only be invoked by a system administrator. A competent sysadmin will know how to mount efivars with read/write permissions when they need to to use those tools. The only reason to mount efivars by default is for convenience. This is by no means a good reason. From a security perspective, mounting efivars by default should be strongly discouraged as it breaks the principle of least privilege. Lennart goes on to state that systemd needs to write EFI variables. This demonstrates yet another example of scope creep and thus poor design.
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=28640752854
https://bugzilla.redhat.com/show_bug.cgi?id=1170765
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784720

———————— Scope creep leads to (has led to these, documented) vulnerabilities
systemd-resolved DNS cache poisoning
To run systemd properly in container a FUSE LXCFS had to be created, and surely its own share of vulnerabilities:
LXCFS before 0.12 does not properly enforce directory escapes CVSS 4.6
The do_write_pids function in lxcfs.c in LXCFS before 0.12 does not properly check permissions CVSS 7.2
systemd vulnerability allows attackers to hack Linux machines via malicious DNS response
Remote code execution via DHCPv6

———————— Absurd bugs and responses
freedesktop#74589 Unchecked null pointer dereferencing in PID 1 not considered a serious issue.
openSUSE#918226 systemd segfaults after updating from 208-23.3 to 208-28.1
GitHub#2402 Mount efivarfs read-only – Doing rm -rf / bricks your computer
Debian#776171 Unable to shutdown
freedesktop#61191 systemd-journald eats 100% CPU
freedesktop#64116 Corrupted binary logs
GitHub#5644 tmpfiles: R! /dir/.* destroys root, also see systemd again (or how to obliterate your system)
GitHub#6237 systemd can’t handle the process previlege that belongs to user name startswith number, such as 0day
GitHub#2039 Default value of RemoveIPC doensn’t allow to use third party daemons. — “This is an issue tracker, not a support forum.”
GitHub#8596 redhat#1494014 systemd incorrectly unmounts a reused mount point after a device removal / systemd automatically unmounts filesystem mounted using “mount <mountpoint>” command
Github#9602 systemd won’t allow the system to start if the system is configured correctly (/etc/localtime as a symlink) (you can even use systemd’s tool to configure it!)
how to crash systemd in one sweet (works as any user, not just root) and response and rebuttal
systemd v228 local root exploit
systemd Using 4GB RAM After 18 Days of Uptime
Phoronix – Screen locking issues (including a security issue) with gnome-shell — remained unfixed for over a year
SoylentNews – PID 1 segfaulting on upgrade; journalctl usability issue – bug report still marked as “NEW”
“Tried to boot my laptop from a cafe…”

———————— Unprofessionalism
Lead systemd developer doesn’t understand su, expects it to do something else and then labels it a “broken concept” – su isn’t supposed to inherit cgroups or audit, those concepts are relatively new and arrived well after the creation of su. TTYs were originally physical devices so of course su is supposed “inherit” the same device otherwise it would be truly broken. Pseudo TTYs emulate real TTYs so their behaviour is obviously expected to be identical. su really is just a simple mechanism that calls setuid(2) in order to switch to another user. If he needs to write a new utility to handle scenarios that su was never designed to handle, no problem, but to label it as a “broken concept” demonstrates a lack of understanding of what su actually is.

[Anonymous]

For the person who elsewhere linked us the definition of “order”, I now link you the definition of rouge.

olsztyn, until recently (2yrs ago?) when antiX devs invented the “live-kernel-updater” tool, it was difficult to update the kernel on a liveboot system. Does any other live system by any other distribution support kernel replacement? I don’t think so, I’m not aware of any that do.

So, historically, a benefit (more like a necessity) of installing would be to gain ability to easily update the kernel. After doing so, we would squish the system back into an ISO or remaster to a fresh usb drive.

My thinking is that when Live it is more permanent and secure

I agree. Regardless the ignorant response you received above, we can disallow mounting of fixed drives, and choose “toram” boot option and remove the pendrive we booted from. If someone wants to claim this does not provide a bulletproof method of ensuring one’s system, they’ll be hard-pressed to do so. No, sorry, we’re not immune from a bios rootkit being injected via an OpenGL exploit. If you visit porn site or download torrent and fall for the ruse “you needs to install a ‘codec’ to view this content”, all bets are off.

Installed could be favorable for use with some old hardware, like, if the machine has only USB I ports, right? Some of our PCs have the opposite challenge, writing to their upcycled (salvage, repurposed) SATA I hard drive is slower than writing to a pendrive attached to their comparatively fast(er) USB II or USB III ports.

Hello all,
i am trying to install antiX 17.2 32-bit on Alix 3D3 (single board PC, quite old one). So i created usb flash disk, booted into live and ran install. I choose to use whole disk automatically. Later i chose both ways of placing grub (MBR and root). That ends the installation for me. After restart i get error: attempt to read or write outside of disk 'hd0'. After much googling and attempts i am unable to move forward.
So i took the same ISO image and installed it in VirtualBox. The installer does not end by choosing location for grub but continues onward by creating user etc. This the problem that’s causing it i think, installer does not finish correctly.

Originally i suspected the compactflash card being corrupted but badblocks didn’t find anything wrong.

What can i do to fix this?

[Anonymous]

I used anticapitalista way and the rest did:

sudo apt-get purge iso-snapshot-antix iso-template-antix live-boot-docs-antix live-init-antix live-kernel-updater remaster-antix

sudo apt-get autoremove

It worked fine.

Thanks!

[Anonymous]

Consider:

“duplicate” applications (to your example of Midnight Commander) are present because some people still prefer to use it, instead of or alongside the other similar apps. It’s tiny, and you can easily remove it from your system.

“duplicate” menu items, identical to control center buttons
If you research the older antiX versions (ISOs for older versions are available from some archive?) or read the betatesters feedback during antiX15, 16, 17… you’ll learn that it has gone back and forth (decision to include duplicates or not). Because many people were not finding control center, or were finding control center but getting lost in the maze of tabs and available tools, and posting and repeatedly reposting to ask “how do I xyz?” the redundant menu items were reintroduced into the menu for antiX17. Anyhow, that’s my understanding for the reason duplicates menu items are present.

Searchmonkey inclusion isn’t concerned with impressing “Doctors”. It is a user-requested tool, it is effective, and is TINY compared to similar apps found in other distros, so it fits well the “lean and mean” antiX ethos.

Across distros the pulseaudio situation is weird, and I don’t fully understand the ins and outs. I guess we can use “apulse” as a replacement but it doesn’t work with all apps? On some other distros I have to go in and “turn up volume, to 120%” before I can hear anything. When I boot antiX, the sound “just works, without fiddling” so I’m content with whatever its set to in antiX17.

[Moderator caprea]

If you created a usb-stick with the antix-iso (64bit or 32bit doesn’t matter) and rufus , you created a live-usb-stick.(there is no need for another usb-stick or to modify the stick or something like that)
It should boot you to a desktop.
That worked flawlessly with your toshiba laptop.

The asus-laptop seems to have some problems, it’s a uefi-boot and the boot-menu has a different appearance, but anyway the stick should boot into a working desktop.
you should normally not get to the point were one must log in as Root and run the cli-installer

So the question is, why it doesn’t do so ?
To begin from the start, did you check the md5sum for the downloaded iso ?

You maybe have to play a little more with the boot-options available in the text-based settings.
Which options did you try ?
The problems are maybe related to the relatively modern hardware.

[Member MacRavn]

It is encouraging to know that an install to the primary disk worked, eventually I will do that.

To tune the scope of this thread and my question: Can anyone confirm or deny: Is it in fact possible to run a single complete LIVE USB version in the 64BIT version?

To compare:

32BIT Full ISO to USB (old 2007 Toshiba): presents “Boot Options” textbox with F-menus, etc. Once options chosen, install proceeds to create a self-contained complete system on same USB, with full DE, running etc.

64BIT Full ISO to USB (2018 ASUS machine, UEFI, Secure Boot OFF (or on, no diff)): Presents “Install with Text Menus”. First part of the process allows setting such options through text chain. after this comes “Login as Root and run cli-installer”, with a guided process to install on some other media.

Primary question: Is this the only option? is there not one where it creates a system on the some USB like the 32 Bit version did?

(I’ll leave out the experiences attempting to install it over to a second USB for later – in short, some succeeded in “installing”, but none of these yielded a recoginzable bootable USB. More on that later if needed)

Just getting started with AntiX. First used on a 13-year old Toshiba as a Live USB (this machine has no HDD – yet still is fully functional with AntiX)

My current project is to us it on:
ASUS E203MA: 4GB/32GBsNMC – basically configured with Win 10-Smode but this will be dumped as soon as I decide I like the machine.
(Specs per inxi attached [inxi run by Xubuntu))

Process: Create USB from the ISO (Rufus or PenDriveLinux Utility). Boot from USB on the ASUS:
The options presented in the initial boot screen do NOT include many items that DO appear in the 32 Bit version I have been using on the old Toshiba.
In Particular: The “Boot Options” text Box, any of the F# menu options.
My options are
antiX 17.2 full
antiX 17.2 full Customie Book (text Menus)
Advanced: Failsafe, Boot Chart, etc.
(These same options appear regardless of if it is FULL, BASE or CORE, and regardless of the states of FastBoot and SecureBoot)

From what I could tell, UEFI makes the “Pop-Up System” available.
I used the text options to set various modes, and successful made it through to the point were one must log in as Root and run cli-installer:
My original intention was to make the USB that I was booting from, be the Live USB. I am not sure how I should have answered the repartitions questions. I chose NO, and chose the sdb for the current USB Drive, and “no” for “Separate Home Partition.”. Subsequently, came an endless list of “cp:error writing… no space on disk”.

I got the same results with the same process but targeting a second, empty USB. This does not surprise me as I do not see how the second USB would end up bootable.

Ideally I would like to make the ISO USB become the Live USB, at least the first one, from which I could make others, and most likely make a proper install of this, likely as the primary OS for this little machine.

What am I doing wrong?

Thanks

• This topic was modified 4 years, 6 months ago by MacRavn.

[Forum Admin rokytnji]

install gmtp. It does not come installed on the live session. Only systemd distro probably worked is they throw the kitchen sink into the iso which takes up gigs of iso space, then transfers those gigs onto your hard drive. Here is my Samsung Galaxy S7

I use airdroid when I don’t have a cable.
My install

harry@biker:~
$ inxi -v8
System:    Host: biker Kernel: 4.15.9-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: IceWM 1.4.2 info: icewmtray dm: SLiM 1.3.4 
           Distro: antiX-17_x64-full Heather Heyer 24 October 2017 base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Desktop System: Google product: Parrot v: 1.0 serial: <root required> Chassis: type: 3 
           serial: <root required> 
           Mobo: Google model: Parrot v: 1.0 serial: <root required> BIOS: coreboot v: 4.0-6588-g4acd8ea-dirty 
           date: 09/04/2014 
Battery:   ID-1: BATX charge: 32.8 Wh condition: 32.8/37.0 Wh (89%) volts: 17.2/14.8 model: SANYO AL12B32 
           type: Li-ion serial: 00000000000026FC status: Full 
Memory:    RAM: total: 3.79 GiB used: 922.5 MiB (23.8%) 
           RAM Report: permissions: Unable to run dmidecode. Are you root? 
PCI Slots: Permissions: Unable to run dmidecode. Are you root? 
CPU:       Topology: Dual Core model: Intel Celeron 1007U bits: 64 type: MCP arch: Ivy Bridge family: 6 
           model-id: 3A (58) stepping: 9 microcode: 17 L2 cache: 2048 KiB bogomips: 5986 
           Speed: 1289 MHz min/max: 800/1500 MHz Core speeds (MHz): 1: 1176 2: 1246 
           Flags: acpi aperfmperf apic arat arch_perfmon bts clflush cmov constant_tsc cpuid cpuid_fault cx16 
           cx8 de ds_cpl dtes64 dtherm dts epb ept erms est flexpriority fpu fsgsbase fxsr ht lahf_lm lm mca 
           mce mmx monitor msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pebs pge pln pni popcnt 
           pse pse36 pti pts rdtscp rep_good sep smep ss sse sse2 sse4_1 sse4_2 ssse3 syscall tm tm2 tpr_shadow 
           tsc tsc_deadline_timer vme vmx vnmi vpid x2apic xsave xsaveopt xtopology xtpr 
           Vulnerabilities: Type: meltdown mitigation: PTI 
           Type: spectre_v1 mitigation: __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline 
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:0156 
           Display: server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 3.3 Mesa 13.0.6 compat-v: 3.0 
           direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:1e20 
           Sound Server: ALSA v: k4.15.9-antix.1-amd64-smp 
Network:   Device-1: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: Foxconn driver: ath9k v: kernel 
           port: 0400 bus ID: 01:00.0 chip ID: 168c:0034 
           IF: wlan0 state: up mac: 3c:77:e6:26:f5:b5 
           IP v4: 192.168.254.70/24 scope: global broadcast: 192.168.254.255 
           IP v6: fe80::3e77:e6ff:fe26:f5b5/64 scope: link 
           Device-2: Broadcom Limited NetLink BCM57785 Gigabit Ethernet PCIe vendor: Acer Incorporated ALI 
           driver: tg3 v: 3.137 port: 0400 bus ID: 02:00.0 chip ID: 14e4:16b5 
           IF: eth0 state: down mac: 20:1a:06:14:09:d9 
           WAN IP: 162.40.218.204 
Drives:    Local Storage: total: 14.91 GiB used: 4.99 GiB (33.5%) 
           ID-1: /dev/sda vendor: SanDisk model: SSD U100 16GB size: 14.91 GiB block size: physical: 512 B 
           logical: 512 B speed: 3.0 Gb/s serial: 132553400495 rev: 6.14 scheme: MBR 
           Message: No Optical or Floppy data was found. 
RAID:      Message: No RAID data was found. 
Partition: ID-1: / raw size: 14.91 GiB size: 14.62 GiB (98.01%) used: 4.99 GiB (34.1%) fs: ext4 dev: /dev/sda1 
           label: rootantiX uuid: ea719934-26e3-4f25-af62-4f54438f456d 
Unmounted: Message: No unmounted partitions found. 
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 3 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 
           Hub: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 4 rev: 2.0 speed: 480 Mb/s 
           chip ID: 8087:0024 
           Device-1: 1-1.1:5 info: Foxconn / Hon Hai type: Bluetooth driver: btusb interfaces: 2 rev: 1.1 
           speed: 12 Mb/s chip ID: 0489:e04e 
           Device-2: 1-1.3:4 info: Chicony type: Video driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s 
           chip ID: 04f2:b336 
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 3 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 
           Hub: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 4 rev: 2.0 speed: 480 Mb/s 
           chip ID: 8087:0024 
           Device-3: 2-1.3:5 info: Samsung Galaxy (MTP) type: Still Imaging driver: N/A interfaces: 1 rev: 2.0 
           speed: 480 Mb/s chip ID: 04e8:6860 serial: 8dc3ad9d 
Sensors:   System Temperatures: cpu: 50.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list.d/MX.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://repo.antixlinux.com/stretch stretch main nosystemd nonfree
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           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: 54.5% command: firefox-esr pid: 11693 mem: 288.4 MiB (7.4%) 
           2: cpu: 24.7% command: [kworker/0:2] pid: 152 mem: 0.00 MiB (0.0%) 
           3: cpu: 19.3% command: firefox-esr pid: 11648 mem: 451.6 MiB (11.6%) 
           4: cpu: 2.0% command: firefox-esr pid: 11791 mem: 155.4 MiB (4.0%) 
           5: cpu: 1.7% command: xorg pid: 2247 mem: 63.9 MiB (1.6%) 
           Memory top: 5 
           1: mem: 451.6 MiB (11.6%) command: firefox-esr pid: 11648 cpu: 19.3% 
           2: mem: 288.4 MiB (7.4%) command: firefox-esr pid: 11693 cpu: 54.5% 
           3: mem: 155.4 MiB (4.0%) command: firefox-esr pid: 11791 cpu: 2.0% 
           4: mem: 79.4 MiB (2.0%) command: firefox-esr pid: 12446 cpu: 0.0% 
           5: mem: 63.9 MiB (1.6%) command: xorg pid: 2247 cpu: 1.7% 
Info:      Processes: 135 Uptime: 53m Init: SysVinit v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0 
           alt: 6 Shell: bash v: 4.4.12 running in: lxterminal inxi: 3.0.25 
harry@biker:~
$ 

Phones interfacing with Linux can be a PITA sometimes. I don’t use my file managers when it comes ro AntiX and phones. gMTP handles the heavy lifting for that. Of course You got give the the phones approval ( trust prompt) before getting my results.

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

Thinkpad A31p (2003-06) Running AntiX 17 Base Buster 32-bit with Kernel 4.9.126 (2018-09-11) SpaceFM-IceWM, running dual-boot with MX17.1 on a 500gb mSATA SSD Pentium 4M with 2gb RAM (currently has UltraBay with DVD/CD in it but also has removable UltraBay with 2TB Hybrid SSD/HDD for Backup and extra storage) :

$ neofetch

                                  jason@Thinkpad-A31p-Linux-AntiX17BaseBuster 
                    \             ------------------------------------------- 
         , - ~ ^ ~ - \        /   OS: antiX 17.1 i686 
     , '              \ ' ,  /    Host: 2653R4U Not Available 
   ,                   \   '/     Kernel: 4.9.126-antix.1-486-smp 
  ,                     \  / ,    Uptime: 25 mins 
 ,___,                   \/   ,   Packages: 1948 (dpkg) 
 /   |   _  _  _|_ o     /\   ,   Shell: bash 4.4.23 
|,   |  / |/ |  |  |    /  \  ,   Resolution: 1600x1200 
 \,_/\_/  |  |_/|_/|_/_/    \,    WM: IceWM 1.4.3.0~pre-20180822 (Linux/i686) 
   ,                  /     ,\    WM Theme: Clearview Blue Medium 
     ,               /  , '   \   Theme: Arc [GTK2/3] 
      ' - , _ _ _ ,  '            Icons: Faenza-Cupertino-mini [GTK2/3] 
                                  Terminal: lxterminal 
                                  Terminal Font: DejaVu Sans Mono 15 
                                  CPU: Mobile Intel Pentium 4 - M 2.00GHz (1) @ 2.000GHz 
                                  GPU: AMD ATI Mobility FireGL 7800 
                                  Memory: 136MiB / 2016MiB 

$ sudo inxi -v8 -z

System:    Host: Thinkpad-A31p-Linux-AntiX17BaseBuster Kernel: 4.9.126-antix.1-486-smp i686 bits: 32 
           compiler: gcc v: 8.2.0 Desktop: IceWM 1.4.3.0~pre-20180822 dm: SLiM 1.3.4 
           Distro: antiX-17.1_386-base Heather Heyer 17 March 2018 base: Debian GNU/Linux buster/sid 
Machine:   Type: Laptop System: IBM product: 2653R4U v: N/A serial: <filter> Chassis: type: 10 serial: N/A 
           Mobo: IBM model: 2653R4U serial: <filter> BIOS: IBM v: 1NET16WW (1.10 ) date: 10/19/2006 
Battery:   ID-1: BAT0 charge: 12.6 Wh condition: 12.9/43.2 Wh (30%) volts: 12.4/10.8 model: SANYO IBM-02K6898 
           type: Li-ion serial: <filter> status: Unknown 
Memory:    RAM: total: 1.97 GiB used: 146.5 MiB (7.3%) 
           Array-1: capacity: 2 GiB note: est. slots: 2 EC: None max module size: 1 GiB note: est. 
           Device-1: DIMM 1 size: 1 GiB info: double-bank speed: Unknown type: SDRAM detail: synchronous 
           bus width: 64 bits total: 64 bits manufacturer: N/A part-no: Not Specified serial: <filter> 
           Device-2: DIMM 2 size: 1 GiB info: double-bank speed: Unknown type: SDRAM detail: synchronous 
           bus width: 64 bits total: 64 bits manufacturer: N/A part-no: Not Specified serial: <filter> 
PCI Slots: Slot: Adapter 0, Socket 0 type: 32-bit PC Card (PCMCIA) CardBus Slot 1 status: Available 
           length: Other 
           Slot: Adapter 1, Socket 0 type: 32-bit PC Card (PCMCIA) CardBus Slot 2 status: Available 
           length: Other 
           Slot: 1 type: 32-bit PCI Mini-PCI Slot 1 status: Available length: Other 
CPU:       Topology: Single Core model: Mobile Intel Pentium 4 - M bits: 32 type: MCP arch: Netburst Northwood 
           family: F (15) model-id: 2 stepping: 7 microcode: 39 L1 cache: 8 KiB L2 cache: 512 KiB 
           bogomips: 3996 
           Speed: 2000 MHz min/max: 1200/2000 MHz Core speed (MHz): 1: 2000 
           Flags: acpi bts cid clflush cmov cx8 de dts fpu fxsr ht mca mce mmx msr mtrr pae pat pbe pebs pge 
           pse pse36 sep ss sse sse2 tm tsc vme xtpr 
           Vulnerabilities: Type: l1tf status: Vulnerable 
           Type: meltdown status: Vulnerable 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] RV200/M7 GL [Mobility FireGL 7800] vendor: IBM 
           driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:4c58 
           Display: server: X.Org 1.20.1 driver: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1600x1200~60Hz 
           OpenGL: renderer: Mesa DRI R100 (RV200 4C58) x86/MMX/SSE2 DRI2 v: 1.3 Mesa 18.1.7 direct render: Yes 
Audio:     Device-1: Intel 82801CA/CAM AC97 Audio vendor: IBM ThinkPad T30 driver: snd_intel8x0 v: kernel 
           bus ID: 00:1f.5 chip ID: 8086:2485 
           Sound Server: ALSA v: k4.9.126-antix.1-486-smp 
Network:   Device-1: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200 v: 1.2.2kmprq port: 3000 
           bus ID: 02:02.0 chip ID: 8086:4220 
           IF: eth1 state: down mac: <filter> 
           Device-2: Intel 82801CAM PRO/100 VE Ethernet vendor: IBM ThinkPad A/T/X Series driver: e100 
           v: 3.5.24-k2-NAPI port: 8000 bus ID: 02:08.0 chip ID: 8086:1031 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           IP v4: <filter> scope: global broadcast: <filter> 
           IP v6: <filter> type: dynamic mngtmpaddr scope: global 
           IP v6: <filter> scope: link 
           IF-ID-1: irda0 state: down mac: <filter> 
           WAN IP: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 10.81 GiB (2.3%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO mSATA 500GB size: 465.76 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 1B6Q scheme: MBR 
           Floppy-1: /dev/fd0 
           Optical-1: /dev/sr0 vendor: HL-DT-ST model: RW/DVD GCC-4240N rev: 0211 dev-links: cdrom 
           Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw state: running 
RAID:      Message: No RAID data was found. 
Partition: ID-1: / raw size: 32.00 GiB size: 31.25 GiB (97.65%) used: 7.68 GiB (24.6%) fs: ext4 
           block size: 4096 B dev: /dev/sda2 label: rootantiX17 uuid: f3c4bf6a-70c2-4067-9aa0-6d292d4680c7 
           ID-2: /media/DATA raw size: 303.76 GiB size: 297.99 GiB (98.10%) used: 3.13 GiB (1.0%) fs: ext4 
           block size: 4096 B dev: /dev/sda4 label: DATA uuid: e67cc135-36b4-437a-aa53-3a5bad02e931 
           ID-3: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60) 
           cache pressure: 50 (default 100) dev: /dev/sda1 label: SWAP 
           uuid: af9c16d5-bfb8-49eb-bde2-0edf2cf1e1a6 
Unmounted: ID-1: /dev/sda3 size: 128.00 GiB fs: ext4 label: rootMX17.1 
           uuid: 2f46c697-c231-4183-8a56-e41e0db255f6 
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001 
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001 
           Hub: 3-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: 38.0 C mobo: 29.0 C 
           Fan Speeds (RPM): cpu: 3399 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/testing testing main nosystemd
           2: deb-src http://iso.mxrepo.com/antix/testing testing main nosystemd
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.ca.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.ca.debian.org/debian/ testing main contrib non-free
           2: deb http://security.debian.org/ testing/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: 23.0% command: sudo pid: 6760 mem: 5.68 MiB (0.2%) 
           2: cpu: 7.8% command: xorg pid: 2365 mem: 50.6 MiB (2.5%) 
           3: cpu: 1.1% command: spacefm pid: 2607 mem: 59.1 MiB (2.9%) 
           4: cpu: 0.9% command: conky pid: 2692 mem: 9.60 MiB (0.4%) 
           5: cpu: 0.7% command: lxterminal pid: 2955 mem: 31.2 MiB (1.5%) 
           Memory top: 5 
           1: mem: 59.1 MiB (2.9%) command: spacefm pid: 2607 cpu: 1.1% 
           2: mem: 50.6 MiB (2.5%) command: xorg pid: 2365 cpu: 7.8% 
           3: mem: 31.2 MiB (1.5%) command: lxterminal pid: 2955 cpu: 0.7% 
           4: mem: 19.1 MiB (0.9%) command: mpd.conf started by: mpd pid: 2188 cpu: 0.0% 
           5: mem: 17.4 MiB (0.8%) command: icewm pid: 2594 cpu: 0.2% 
Info:      Processes: 134 Uptime: 22m Init: SysVinit v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 8.2.0 
           alt: 6/8 Shell: bash (sudo) v: 4.4.23 running in: lxterminal inxi: 3.0.25 

$ cat /etc/debian_version
buster/sid

free -m

              total        used        free      shared  buff/cache   available
Mem:           2016         122        1497          17         396        1811
Swap:          2047           0        2047

$ sudo ps_mem.py

 Private  +   Shared  =  RAM used	Program

160.0 KiB +  53.5 KiB = 213.5 KiB	acpid
176.0 KiB +  43.0 KiB = 219.0 KiB	gpm
204.0 KiB +  46.0 KiB = 250.0 KiB	vnstatd
236.0 KiB +  65.5 KiB = 301.5 KiB	init
188.0 KiB + 130.0 KiB = 318.0 KiB	ifplugd (2)
204.0 KiB + 150.5 KiB = 354.5 KiB	icewm-session
276.0 KiB + 106.0 KiB = 382.0 KiB	cron
304.0 KiB + 132.5 KiB = 436.5 KiB	dbus-launch
356.0 KiB + 186.5 KiB = 542.5 KiB	rpcbind
528.0 KiB +  62.5 KiB = 590.5 KiB	rpc.idmapd
364.0 KiB + 232.5 KiB = 596.5 KiB	udevil
444.0 KiB + 434.0 KiB = 878.0 KiB	devmon
468.0 KiB + 439.0 KiB = 907.0 KiB	desktop-session
512.0 KiB + 441.5 KiB = 953.5 KiB	gconfd-2
792.0 KiB + 223.5 KiB =   1.0 MiB	rpc.statd
740.0 KiB + 474.5 KiB =   1.2 MiB	at-spi-bus-launcher
752.0 KiB + 498.0 KiB =   1.2 MiB	polkitd
684.0 KiB + 586.0 KiB =   1.2 MiB	getty (6)
732.0 KiB + 560.0 KiB =   1.3 MiB	at-spi2-registryd
  1.3 MiB +  51.0 KiB =   1.4 MiB	dhclient
  1.3 MiB +  82.0 KiB =   1.4 MiB	udevd
892.0 KiB + 565.5 KiB =   1.4 MiB	icewmbg
960.0 KiB + 640.0 KiB =   1.6 MiB	dbus-daemon (3)
  1.4 MiB + 197.0 KiB =   1.6 MiB	exim4
  1.3 MiB + 443.0 KiB =   1.7 MiB	bash
  1.7 MiB +  92.0 KiB =   1.7 MiB	rsyslogd
  1.4 MiB + 566.0 KiB =   2.0 MiB	console-kit-daemon
  1.2 MiB +   1.4 MiB =   2.6 MiB	gksu
  2.1 MiB + 591.0 KiB =   2.7 MiB	sudo
  2.7 MiB +   1.4 MiB =   4.1 MiB	slim
  2.9 MiB +   1.3 MiB =   4.2 MiB	conky
  1.9 MiB +   2.3 MiB =   4.3 MiB	volumeicon
  4.7 MiB +   2.3 MiB =   7.0 MiB	icewm
  5.0 MiB +   4.0 MiB =   9.0 MiB	leafpad
 14.0 MiB +   2.9 MiB =  17.0 MiB	mpd
 14.6 MiB +   3.6 MiB =  18.2 MiB	lxterminal
 19.8 MiB +  14.6 MiB =  34.4 MiB	spacefm
 26.8 MiB +  10.4 MiB =  37.2 MiB	Xorg
---------------------------------
                        166.0 MiB

• This topic was modified 4 years, 7 months ago by Hierax_ca.
• This topic was modified 4 years, 7 months ago by Hierax_ca.

AntiX 17.x:
- (32-bit): IBM Thinkpad 600X (2000), IBM NetVista X41 (2002), IBM Thinkpad A31p (2003);
- (64-bit): Lenovo Thinkpads x61s (2008), x200 (2009), x301 (2009).

[Member delix02]

Bingo !!
17.2 is installed without problems from a 2GB USB stick using the .iso file from the mx server.
EXTLINUX is already included, only an extlinux.conf is missing.
The client booted just as it should do.
The full install occupies 1.27 GB disk space.

Seems to be perfect 🙂 – thx guys, you’ve done a perfect job !

In the next days I’ll correct the German translation of the cli-installer as I’m not really happy with te current version.

[Member light]

of cource, iso is checked and booting right in some computers with normal BIOS

[Forum Admin anticapitalista]

dolphin_oracle wrote:

anticapitalista wrote:

I’m interested, firstly, in making sure the installer worked correctly. The rest can wait.

I tested 64 bit full in VBox and the installer crashed after setting up grub so I ran it again and it completed and re-booted into installed OS without error.

hmm…sounds like something odd is going on.

I can’t look right now, but what version of libcmd is on the antiX 17.2?

d_o – libcmd 0.18.2.1 is on the iso

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

antiX with runit - leaner and meaner.