Search Results for 'boot from iso'

please see previous discussion το ΜΧ-linuxforum…

https://forum.mxlinux.org/viewtopic.php?f=40&t=52490

$ inxi -zv7
System:
Host: antix1dim 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: Laptop System: Hewlett-Packard product: HP Compaq 6730b (GW687AV) v: F.08
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: Hewlett-Packard model: 30DD v: KBC Version 96.18 serial: <filter>
BIOS: Hewlett-Packard v: 68PDD Ver. F.08 date: 09/18/2008
Battery:
ID-1: BAT0 charge: 45.7 Wh condition: 46.5/46.5 Wh (100%) volts: 12.5/11.1
model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Unknown
Memory:
RAM: total: 1.90 GiB used: 677.8 MiB (34.8%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
Topology: Dual Core model: Intel Core2 Duo P8400 bits: 64 type: MCP arch: Penryn
rev: 6 L2 cache: 3072 KiB bogomips: 9044
Speed: 1600 MHz min/max: 800/2267 MHz Core speeds (MHz): 1: 1600 2: 1600
Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc cx16 cx8 de
ds_cpl dtes64 dtherm dts est flexpriority fpu fxsr ht lahf_lm lm mca mce mmx monitor
msr mtrr nx pae pat pbe pdcm pebs pge pni pse pse36 sep smx ss sse sse2 sse4_1 ssse3
tm tm2 tpr_shadow tsc vme vmx vnmi xtpr
Graphics:
Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Hewlett-Packard
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a42
Display: server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa
resolution: 1280×800~60Hz
OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express x86/MMX/SSE2 v: 2.1 Mesa 13.0.6
direct render: Yes
Audio:
Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard driver: snd_hda_intel
v: kernel bus ID: 00:1b.0 chip ID: 8086:293e
Sound Server: ALSA v: k4.9.160-antix.2-486-smp
Network:
Device-1: Broadcom Limited BCM4312 802.11b/g LP-PHY vendor: Hewlett-Packard
driver: wl v: kernel port: 6000 bus ID: 02:00.0 chip ID: 14e4:4315
IF: wlan0 state: up mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IP v6: <filter> scope: link
Device-2: Broadcom Limited NetLink BCM5787M Gigabit Ethernet PCI Express
vendor: Hewlett-Packard driver: tg3 v: 3.137 port: 6000 bus ID: 85:00.0
chip ID: 14e4:1693
IF: eth0 state: down mac: <filter>
WAN IP: <filter>
Drives:
Local Storage: total: 126.33 GiB used: 6.23 GiB (4.9%)
ID-1: /dev/sda vendor: Toshiba model: MK1252GSX size: 111.79 GiB speed: 3.0 Gb/s
serial: <filter> rev: 1C scheme: MBR
ID-2: /dev/sdb type: USB vendor: Toshiba model: TransMemory size: 14.53 GiB
serial: <filter> rev: PMAP scheme: MBR
Optical-1: /dev/sr0 vendor: Optiarc model: DVD-ROM DDU820S rev: MH04
dev-links: cdrom,dvd
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: none state: running
RAID:
Message: No RAID data was found.
Partition:
ID-1: / size: 17.40 GiB used: 3.64 GiB (20.9%) fs: ext4 dev: /dev/sda3
label: rootantiX17.4.1 uuid: 3820c3bb-0b7f-447b-9b6f-547a4c7e1a7d
ID-2: /home size: 20.84 GiB used: 2.54 GiB (12.2%) fs: ext4 dev: /dev/sda4
label: homeantiX uuid: f01c1ec2-fb66-49b9-b5c5-e5fddc12f018
ID-3: /media/-rw size: 11.66 GiB used: 40.0 MiB (0.3%) fs: ext4 dev: /dev/sdb5
label: -rw uuid: 3cd1ace9-6a9d-43a0-933e-a1a45fd7793d
ID-4: /media/MX-Live raw size: 1.41 GiB size: <root required> used: <root required>
fs: iso9660 dev: /dev/sdb4 label: MX-Live uuid: 2019-10-21-17-35-05-00
ID-5: /media/usbboot size: 240.2 MiB used: 7.0 MiB (2.9%) fs: vfat dev: /dev/sdb3
label: usbboot uuid: 3055-742E
ID-6: /media/usbdata size: 1.03 GiB used: 5.8 MiB (0.6%) fs: ntfs dev: /dev/sdb1
label: usbdata uuid: 0504B837002B90F5
ID-7: swap-1 size: 6.52 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 label: N/A
uuid: 40ccc468-e3a5-4544-82b8-ee84ab6df0b5
Unmounted:
ID-1: /dev/sda1 size: 1 KiB fs: <root required> label: N/A uuid: N/A
ID-2: /dev/sda2 size: 46.57 GiB fs: ext4 label: N/A
uuid: 743f0e89-2ac8-42cb-a66d-bbef565e1ecc
ID-3: /dev/sda6 size: 18.62 GiB fs: ext4 label: N/A
uuid: d478de32-5949-4f6f-b9d3-aabeaaf9bcc9
ID-4: /dev/sdb2 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
Hub: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 speed: 480 Mb/s
chip ID: 1d6b:0002
Device-1: 2-5:2 info: Toshiba Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB
/ PNY Attache 4GB Stick
type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s
chip ID: 0930:6545 serial: <filter>
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Device-2: 3-1:2 info: HP Bluetooth 2.0 Interface [Broadcom BCM2045] type: Bluetooth
driver: btusb interfaces: 4 rev: 2.0 speed: 12 Mb/s chip ID: 03f0:171d
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
Hub: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 7-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 8-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: 50.0 C mobo: 43.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 161 Uptime: 1h 08m 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.36

[Member melodie]

Hello BitJam,

I would most certainly like to learn new ways to create ISOs for redistribution, however I am almost sure I will crually lack time for that. I have climbed learning curves in doing so before this is why I think I can say for sure. I learned to use a script from within a running distribution, as it is here, I have learned to do so with Ubuntu using a chroot and rebuild using the python script “Customizer“, which is nice too. Ideally, “Customizer for antiX” would be lovely! It’s soo easy to use, either with the GUI or even easier with the command line (on a remote server for instance), it is a wonder why it’s not known more widely.

Now, if I stick to the rebuilds inside a running antiX edition, why does isn’t the produced ISO capable of providing the same advantage? I mean:

1/ install antiX
2/ tweak it, rebuild the system
3/ install the resulting new ISO on bare metal to another computer
4/ retweak it (ie : update, add a program, change a detail) and rebuild it : build fails!

?

(just the name at boot isn’t the problem anymore, because editing the isolinux.cfg file has done the job).

Also I find strange that after I installed my respin, there is no symlink pointing to ‘/boot/vmlinuz’ and ‘/boot/initrd.im’g in the ‘/’ directory. Isn’t that strange?

Many thanks for your kind help.

• This reply was modified 3 years, 6 months ago by melodie.

[Forum Admin rokytnji]

I zm not using synaptic for this. Recommends are not depends as far as I know. Up to you.

Writing file: /usr/share/desktop-session/wm-menus/fluxbox-wm-menu
Writing file: /usr/share/desktop-session/wm-menus/icewm-wm-menu
Writing file: /usr/share/desktop-session/wm-menus/jwm-wm-menu
Writing file: /usr/share/desktop-session/wm-menus/RAW-wm-menu
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@biker:/home/harry# apt-get -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  dh-python gnome-themes-standard libappindicator1 libass5 libavdevice57 libavfilter6 libavformat57 libavresample3 libbind9-140 libblas-common libbluetooth3
  libbluray1 libcdio-cdda1 libcdio-paranoia1 libcdio13 libcmd libdbusmenu-gtk4 libdirectfb-1.2-9 libdns162 libebur128-1 libetpan17 libfile-copy-recursive-perl
  libgcr-3-common libgfortran3 libglew2.0 libgltf-0.0-0v5 libgnome-desktop-3-12 libgtop-2.0-10 libgutenprint2 libhunspell-1.4-0 libicu57 libilmbase12 libindicator7
  libisc160 libisccc140 libisccfg140 libiso9660-8 libjim0.76 libjpeg8 libkeybinder0 liblwres141 libmaa3 libmagickcore-6.q16-3 libmagickwand-6.q16-3 libminiupnpc10
  libnfs8 libntfs-3g871 libopencv-calib3d2.4v5 libopencv-core2.4v5 libopencv-features2d2.4v5 libopencv-flann2.4v5 libopencv-highgui2.4-deb0 libopencv-imgproc2.4v5
  libopencv-objdetect2.4v5 libopencv-video2.4v5 libopenexr22 liborcus-0.11-0 libpcre16-3 libperl5.24 libpisock9 libpng12-0 libpoppler64 libpostproc54 libpython3.5
  libpython3.5-minimal libpython3.5-stdlib libqpdf17 libqt5opengl5 libqt5sql5 libreoffice-gtk2 libsodium18 libsox2 libsrtp0 libsuitesparseconfig4 libswscale4 libtbb2
  libtorrent19 libusb-0.1-4 libva-wayland1 libwayland-egl1-mesa libx86emu1 libxfont1 nvidia-detect python-certifi python-cssselect python-idna python-keybinder
  python-pyquery python-requests python-simplejson python-urllib3 python-webob python3.5 python3.5-minimal
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up broadcom-sta-dkms (6.30.223.271-10) ...
Removing old broadcom-sta-6.30.223.271 DKMS files...

------------------------------
Deleting module version: 6.30.223.271
completely from the DKMS tree.
------------------------------
Done.
Loading new broadcom-sta-6.30.223.271 DKMS files...
Building for 5.2.3-antix.1-amd64-smp
Building initial module for 5.2.3-antix.1-amd64-smp
Error! Bad return status for module build on kernel: 5.2.3-antix.1-amd64-smp (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
dpkg: error processing package broadcom-sta-dkms (--configure):
 installed broadcom-sta-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
 broadcom-sta-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@biker:/home/harry# 

Looks like broadcom.dkms is going out the door on this chromebook.

root@biker:/home/harry# apt-get purge  broadcom-sta-dkms
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  dh-python gnome-themes-standard libappindicator1 libass5 libavdevice57 libavfilter6 libavformat57 libavresample3 libbind9-140 libblas-common libbluetooth3
  libbluray1 libcdio-cdda1 libcdio-paranoia1 libcdio13 libcmd libdbusmenu-gtk4 libdirectfb-1.2-9 libdns162 libebur128-1 libetpan17 libfile-copy-recursive-perl
  libgcr-3-common libgfortran3 libglew2.0 libgltf-0.0-0v5 libgnome-desktop-3-12 libgtop-2.0-10 libgutenprint2 libhunspell-1.4-0 libicu57 libilmbase12 libindicator7
  libisc160 libisccc140 libisccfg140 libiso9660-8 libjim0.76 libjpeg8 libkeybinder0 liblwres141 libmaa3 libmagickcore-6.q16-3 libmagickwand-6.q16-3 libminiupnpc10
  libnfs8 libntfs-3g871 libopencv-calib3d2.4v5 libopencv-core2.4v5 libopencv-features2d2.4v5 libopencv-flann2.4v5 libopencv-highgui2.4-deb0 libopencv-imgproc2.4v5
  libopencv-objdetect2.4v5 libopencv-video2.4v5 libopenexr22 liborcus-0.11-0 libpcre16-3 libperl5.24 libpisock9 libpng12-0 libpoppler64 libpostproc54 libpython3.5
  libpython3.5-minimal libpython3.5-stdlib libqpdf17 libqt5opengl5 libqt5sql5 libreoffice-gtk2 libsodium18 libsox2 libsrtp0 libsuitesparseconfig4 libswscale4 libtbb2
  libtorrent19 libusb-0.1-4 libva-wayland1 libwayland-egl1-mesa libx86emu1 libxfont1 nvidia-detect python-certifi python-cssselect python-idna python-keybinder
  python-pyquery python-requests python-simplejson python-urllib3 python-webob python3.5 python3.5-minimal
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  broadcom-sta-dkms*
0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded.
1 not fully installed or removed.
After this operation, 14.5 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 179851 files and directories currently installed.)
Removing broadcom-sta-dkms (6.30.223.271-10) ...

------------------------------
Deleting module version: 6.30.223.271
completely from the DKMS tree.
------------------------------
Done.
(Reading database ... 179787 files and directories currently installed.)
Purging configuration files for broadcom-sta-dkms (6.30.223.271-10) ...

There. got rid of error code 1

root@biker:/home/harry# apt-get -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  dh-python gnome-themes-standard libappindicator1 libass5 libavdevice57 libavfilter6 libavformat57 libavresample3 libbind9-140 libblas-common libbluetooth3
  libbluray1 libcdio-cdda1 libcdio-paranoia1 libcdio13 libcmd libdbusmenu-gtk4 libdirectfb-1.2-9 libdns162 libebur128-1 libetpan17 libfile-copy-recursive-perl
  libgcr-3-common libgfortran3 libglew2.0 libgltf-0.0-0v5 libgnome-desktop-3-12 libgtop-2.0-10 libgutenprint2 libhunspell-1.4-0 libicu57 libilmbase12 libindicator7
  libisc160 libisccc140 libisccfg140 libiso9660-8 libjim0.76 libjpeg8 libkeybinder0 liblwres141 libmaa3 libmagickcore-6.q16-3 libmagickwand-6.q16-3 libminiupnpc10
  libnfs8 libntfs-3g871 libopencv-calib3d2.4v5 libopencv-core2.4v5 libopencv-features2d2.4v5 libopencv-flann2.4v5 libopencv-highgui2.4-deb0 libopencv-imgproc2.4v5
  libopencv-objdetect2.4v5 libopencv-video2.4v5 libopenexr22 liborcus-0.11-0 libpcre16-3 libperl5.24 libpisock9 libpng12-0 libpoppler64 libpostproc54 libpython3.5
  libpython3.5-minimal libpython3.5-stdlib libqpdf17 libqt5opengl5 libqt5sql5 libreoffice-gtk2 libsodium18 libsox2 libsrtp0 libsuitesparseconfig4 libswscale4 libtbb2
  libtorrent19 libusb-0.1-4 libva-wayland1 libwayland-egl1-mesa libx86emu1 libxfont1 nvidia-detect python-certifi python-cssselect python-idna python-keybinder
  python-pyquery python-requests python-simplejson python-urllib3 python-webob python3.5 python3.5-minimal
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.

Now install missing stuff not included . I will not pick and choose. Reboot. Then clean cruft. Crosses fingers.

Scratch that. Gotta reboot 1st. Then apt-get update again.

root@biker:/home/harry# apt-get install app-select-antix artwork19-antix blueman bluez-obexd breeze-amber-cursor-theme-antix breeze-snow-cursor-theme-antix chroot-rescue cputool entr f2fs-tools firejail-profiles formatusb gnome-bluetooth icewm-icons-numix-square-antix icewm-icons-papirus-antix isomount lxtask newsboat ntpdate numix-gtk-theme numix-square-antix oxy-black-cursor-theme-antix oxy-white-cursor-theme-antix papirus-antix prettypink-themes qpdfview roxterm-common roxterm-gtk2 screenlight-antix sct slim-themes-extras-antix volumeicon-alsa-icons xserver-xorg-input-mouse
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package artwork19-antix
E: Unable to locate package chroot-rescue
E: Unable to locate package icewm-icons-numix-square-antix
E: Unable to locate package icewm-icons-papirus-antix
E: Unable to locate package isomount
E: Unable to locate package numix-square-antix
E: Unable to locate package papirus-antix
E: Unable to locate package prettypink-themes

• This reply was modified 3 years, 6 months ago by rokytnji.
• This reply was modified 3 years, 6 months ago by rokytnji.

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

This is what I did to upgrade antiX-17.4.1 pristine (ie nothing added nor removed) to antiX-19.
Make sure all your valuable data is backed up.
You may want to use iso-snapshot to create an iso of your present install and test the newly created snapshot does boot and install … just in case things go wrong.

This guide will not produce an identical antiX-19, but I assume most people want to upgrade from ‘stretch – old stable’ to ‘buster – new stable’ and are less concerned about the looks, themes etc.

If you try this and it breaks your install, don’t blame me!

Use a root terminal and not synaptic and do READ the output before pressing Enter.

1. Make sure your antiX-17 version is fully up to date before changing any repos.
Also, do not have any packages set on hold.
Only use the official sources.

apt-get update && apt-get dist-upgrade

2. Change sources to buster so they look something like this

antix.list:

# Use with Debian Stable/buster repositories. Set as default for antiX-19.
deb http://iso.mxrepo.com/antix/buster buster main nonfree nosystemd 
#http://iso.mxrepo.com/antix/buster buster main nonfree nosystemd 

debian.list:

# Debian Stable. Default for antiX-19.
deb http://ftp.gr.debian.org/debian/ buster main contrib non-free 
deb http://security.debian.org/ buster/updates main contrib non-free
#deb-src http://ftp.gr.debian.org/debian/ buster main contrib non-free 

debian-stable-updates.list:

# Debian Buster Updates
deb http://ftp.gr.debian.org/debian/ buster-updates main contrib non-free

3. Remove libapulse and apulse otherwise you will get errors.

apt-get purge libapulse apulse

4. Refresh the new buster repos

apt-get update

5. Install apulse before doing a dist-upgrade

apt-get install apulse

6. Now dist-upgrade. Make sure you read the output to see if it will remove anything important.

apt-get dist-upgrade

7. When prompted to accept new version of files or not, choose Y(es).

8. Once the dist-upgrade has finished, remove unneeded packages/libs and tidy up Other desktops menu

apt-get autoremove

apt-get install --reinstall desktop-session-antix

9. Reboot – and cross your fingers! (You DID make a backup didn’t you?

10. Hopefully, you logged in to your newly upgraded to buster antiX.

NOTE: /etc/antix-version, inxi etc will still show antiX-17. This is deliberate.

11. Install apps not included in antiX-17 but are included in antiX-19. You can pick and choose.

apt-get install app-select-antix artwork19-antix blueman bluez-obexd breeze-amber-cursor-theme-antix breeze-snow-cursor-theme-antix chroot-rescue cputool entr f2fs-tools firejail-profiles formatusb gnome-bluetooth icewm-icons-numix-square-antix icewm-icons-papirus-antix isomount lxtask newsboat ntpdate numix-gtk-theme numix-square-antix oxy-black-cursor-theme-antix oxy-white-cursor-theme-antix papirus-antix prettypink-themes qpdfview roxterm-common roxterm-gtk2 screenlight-antix sct slim-themes-extras-antix volumeicon-alsa-icons xserver-xorg-input-mouse

12. If you get a flashing conky, edit ~/.conkyrc

Add this line (about line 39) own_window_type desktop

eg

# Create own window instead of using desktop (required in nautilus, pcmanfm and rox desktops)
own_window yes
own_window_transparent yes
own_window_hints undecorated,below,sticky,skip_taskbar
own_window_type desktop

13. Set your themes, icons etc as you see fit.

12. You should really upgrade the kernel. To do so, best to use cli-aptiX in the Menu under Applications – antiX

Remember: If you try this and it breaks your install, don’t blame me!

• This topic was modified 3 years, 6 months ago by anticapitalista.
• This topic was modified 3 years, 6 months ago by anticapitalista. Reason: Added kernel upgrade
• This topic was modified 3 years, 1 month ago by anticapitalista.

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

antiX with runit - leaner and meaner.

[Forum Admin BitJam]

melodie wrote:

Hello, my test version number 7 starts to have more or less the right behavior, just this strange thing that happens at the first boot of the live, the distro given name is replaced with the macro commands, which is very very ugly.

Please see the screenshot, and please tell me how I can get the system to display the dedicated name instead of the macro commands?

The tool to fix this is in my build-iso repo. This repo contains the tools used to build both the antiX and MX distro iso files. If you are serious about making a respin then you may want to learn to use these tools some day. It is best to start off with snapshots like you are doing now.

The tool to fill in those blanks is Tools/bootloader-template.

This tools is also used in my antiX-Gfxboot repo which is used to create our live bootloaders. I have a “Tools” symlink in this repo to the Tools directory of the build-iso repo.

We have tried to make our build process as open and as accessible as possible although it may not seem this way. Several people have mastered the use of build-iso to create their own ongoing repsins.

I believe the lead developers of both antiX and MX rely on a live system with persistence and remastering to build their prototypes of our releases. We designed the live system to be the best OS development environment possible (for OSes based on antiX or MX, but in theory it could be ported to others as well). The combination of semi-automatic persistence coupled with live-remaster and “rollback” give an OS developer tremendous flexibility and safety. Add notes every time you do a remaster. These are saved in the file /etc/live/version/linuxfs.ver so you can trace back the linage of your live system.

For your situation, you can run snapshot on your live development system to make iso files for others to use. If you don’t have a fast usb-stick and fast usb-port then you can do a frugal install to run live off of your hard drive.

IMO these automation tools and the live development environment have helped both antiX and MX become real contenders in the distro world while at the same time have small enough teams to allow devs and leaders to interact with users in the forums. This is good for users, obviously, but it also helps devs “keep it real” and be in touch with the needs of users and know what works and what doesn’t.

We heavily invested our extremely limited developer resources on the live system and on automation. IMO that investment paid off handsomely for antiX and now for MX as well.

• This reply was modified 3 years, 6 months ago by BitJam.

Context is worth 80 IQ points -- Alan Kay

Antix 19 does not start.
It may seem curious in a Virtual Box virtual machine, antix 19 starts very quickly and correctly. But on a real computer, Antix 19 does not start, it goes very slow and in the boot processor it is completely stopped in the window called ….. “start X”.
The loading process up to that “Start X” window is slower than with Antix 17.4.1

I have installed Antix 17.4.1, Mx Linux 18.3 on that same computer and they work perfectly. I created the live usb with rufus or MX Constructor Usb. I have tried the Isos: Full and Base.

Regards

[Forum Admin BitJam]

We could go 1990s retro and make a 2nd cd-sized iso file that just has a bunch of .deb packages on it.

It’s a real struggle. One of the reasons we use our own live system is we’ve been able to keep it small, under 5 Meg. But Grub makes up for this by consuming 13 Meg which blows my mind.

For machines that have a usb port but only boot from cd, you can use an antiX cd to boot from an antiX live-usb (assuming they use the same kernel). With the fehlix rescue system we added to grub on the live system (its not the thing gobbling up space) even the same-kernel restriction could be lifted, if it hasn’t already. I’ll ask him about this.

The cd-size restriction on one hand and the bloat bloat bloat (and legitimate growth) of software on the other puts us between a rock and a hard place. I hope we can make use of creative solutions to get around these restrictions and try to get the solutions well publicized.

Context is worth 80 IQ points -- Alan Kay

[Anonymous]

As a followup to kenzo’s post (idunno which language, or languages plural kenzo would keep)
I tested “whatif remove extraneous locales and such from antiX19 base”.
(this test involved the removal of ZERO pre-installed packages)

================================

browse to /usr/share/locale/ and not that it contains 199Mb files

sudo apt update
sudo dpkg-reconfigure locales (on test machine, I kept only en_US.UTF8)
sudo install localepurge (skim the list, click OK, answer Yes to “Use dpkg –path-exclude”)
sudo install bleachbit

sudo bleachbit —-}
…click OK to close the autopopup “preferences” dialog
…find and tick “Localizations” in left pane, click OK to dismiss autopopup dialog
…click the TrashCan bleachbit toolbar icon, click “Delete” button in the confirmation dialogbox
noted: bleachbit reported (in my test) Disk space recovered 210Mb
…exit bleachbit

sudo apt purge bleachbit

browse to /usr/share/locale/
noted (in my test) that bleachbit missed 8.7 Mb files here
On the test machine, I nixed all here EXCEPT:
/usr/share/locale/en/
/usr/share/locale/en_US/
/usr/share/locale/[[[symlink to]]]locale.alias
( and now /usr/share/locale/* occupies only 212Kb )

2.5Mb /usr/share/gnome/help/gparted/
(on an English-only system) delete all items here except the subdir named “C” …leaves 215kb
.
1.5Mb /usr/share/gnome/help/synaptic/ {——— if synaptic package is currently installed
Similarly, (on an English-only system) delete all items here except the subdir named “C” …leaves 480kb
.
Note: As additional programs are installed, locale-specific files may accumulate here (localepurge seems unaware of these)

1.4Mb (on an English-only machine, these are never utilized)
sudo rm /usr/share/perl/5.28.1/Unicode/Locale/*
sudo rm /usr/share/perl/5.28.1/Unicode/CJK/*

====================

Next, I used “ncdu” to quickly look for fluffernutter items, and nixed:

2.8Mb
sudo apt purge breeze-snow-cursor-theme-antix

deleted these:
2.0Mb /usr/share/wallpaper/PrettyPink.png
130Kb /usr/share/wallpaper/auditorio-de-tenerife2.jpg
150Kb /usr/share/wallpaper/login/auditorio-de-tenerife2.jpg

4.8Mb /usr/share/icons/Adwaita/256×256/*
2.3Mb /usr/share/icons/Adwaita/512×512/*
704Kb /usr/share/icons/Adwaita//96×96/*

805Kb /usr/share/icons/hicolor/512×512/cmst.png
384Kb /usr/share/icons/hicolor/384×384/cmst.png

then, to guard against pkg upgrades causing unwanted reinstallation of the above:

sudo apt-mark hold adwaita-icon-theme
sudo apt-mark hold papirus-antix
sudo apt-mark hold breeze-snow-cursor-theme-antix (idunno, would a dist-upgrade operation attempt to reinstall it?)
sudo apt-mark hold artwork19-antix

===========================

sudo apt install synaptic (its installation is counterproductive for this, but oh well)
sudo updatedb (freshens the db index employed by the “locate” command)

after the above, launching iso-snapshot reported Space Used: 1.9G (w/ original, was reported as 2.1G)
click Next, choose xz compression scheme, click Next, click OK in the popup dialogbox
. . .
the resulting ISO file is 653.7Mb 685768704 bytes
.
from original antiX-19_386-base.iso 697.0Mb 730857472 bytes
(reduction of 6.3% or 44Mb)

counted estimate, from my notes above + bleachbit output ~= 259M
(IOW, approx 250Mb less overhead during a toram liveboot session)

[Moderator BobC]

I saw its been updated today. I burned it again with the cli version, told it to check md5, and it said they were ok. I booted it in a different machine with checkmd5 on at boot and it booted and ran fine. I think the test command that tested the md5 of the flashdrive doesn’t work in all cases anymore, suspecting the ones that are not written in straight dd mode.

Yes, I am pretty sure the last command to get the md5 of the flashdrive doesn’t work right for a distro burned as an iso-hybrid, and that’s why it doesn’t match. It makes sense, but I would have thought there would be a way to calculate it and get a matching number. Sometimes flashdrives are bad.

Anyway, the current program is working, so I feel better… Thanks for antix-19!

• This reply was modified 3 years, 6 months ago by BobC.

[Member olsztyn]

BitJam wrote:

I also gave a quick fix over in the MX forums. To fix an encrypted live-usb that does not boot, (assuming it is at /dev/sdd) run this command:
sudo parted /dev/sdd set 2 boot off set 1 boot on print
It should show the “boot” flag on the first (ex4) partition.

Thanks BitJam for this tip. So it is the boot flag that was set to second partition…
Running this to set boot flag to the first partition worked fine and antiX starts to boot however it stops with a fatal error complaining that encrypted partition is not a LUKS device, giving just two opportunities:
P – Power off
r – reboot.
Am I still missing something? Normally, antiX 17 was asking to set encryption password at this point…
Just to add, I saw this reported on MX forum as you mentioned but I have not seen a resolution…
Considering Live-USB-Maker is already 0.4.0, in case there is no fix I am OK with suggestion from anti to use antiX 17 for Live USB making. This way requires an extra step of creating an ISO from a fully configured antiX 19, as option ‘Create from run system’ cannot be used due to the run system being antiX 17, so just a tool to burn the actual fully configured antiX 19 system.
Thanks again and Regards…

• This reply was modified 3 years, 6 months ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member KenzoG]

There is one more aspect that in my opinion ought to be considered:
If the i386 Base version at 698 MiB NOW fits in on (some brands of) 700 MiB standard CD-R,
in a few months time the programs, such as the web browser, will have GROWN in size,
and by the time of the first point release it will be well OVER 700 MiB, and thus no longer fit upon a CD-R.

Wouldn’t it be better to make the ISO SMALLER NOW, as I somehow don’t believe that it will be done when the 19.1 and 19.2
point releases arrive.
This would make those i386 Base version upcoming point releases useless for many people, including me, that have older computers
that neither can burn DVDs nor be booted from USB.

• This reply was modified 3 years, 6 months ago by KenzoG.
• This reply was modified 3 years, 6 months ago by KenzoG.

[Member ex_Koo]

All tested with antiX-17.4.1_x64-base.iso.

Both cli Full featured and dd burned and booted
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
GUI dd burned and booted

GUI Full featured failed to even burn . (Even tried twice)

LOGS~~~

live-usb-maker-gui-antix version: 0.2.2
df -T / |tail -n1 |awk '{print $2}'
live-usb-maker --help | grep data-first
lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259
mount: /media/koo/antiX-uefi: /dev/sdc2 already mounted or mount point busy.
devmon: error mounting /dev/sdc2 (32)
mount: /media/koo/antiXlive-2: /dev/sdc1 already mounted or mount point busy.
devmon: error mounting /dev/sdc1 (32)
live-usb-maker-gui-antix version: 0.2.2
df -T / |tail -n1 |awk '{print $2}'
live-usb-maker --help | grep data-first
lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259
. /usr/local/lib/cli-shell-utils/cli-shell-utils.bash;get_drive $(get_live_dev) 
Empty filename passed to function
Options:  "-N "
start io is  0
max progress bar is  1294336
live-usb-maker gui -N -C off --from="/media/storage1/antiX-17.4.1_x64-base.iso" -t /dev/sdc
live-usb-maker-gui-antix version: 0.2.2
df -T / |tail -n1 |awk '{print $2}'
live-usb-maker --help | grep data-first
lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259
. /usr/local/lib/cli-shell-utils/cli-shell-utils.bash;get_drive $(get_live_dev) 
""
EXIT="abort"
live-usb-maker-gui-antix version: 0.2.2
df -T / |tail -n1 |awk '{print $2}'
live-usb-maker --help | grep data-first
lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259
mount: /media/koo/antiX-uefi: /dev/sdc2 already mounted or mount point busy.
devmon: error mounting /dev/sdc2 (32)
mount: /media/koo/antiXlive-2: /dev/sdc1 already mounted or mount point busy.
devmon: error mounting /dev/sdc1 (32)
EXIT="abort"
live-usb-maker-gui-antix version: 0.2.2
df -T / |tail -n1 |awk '{print $2}'
live-usb-maker --help | grep data-first
lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259
. /usr/local/lib/cli-shell-utils/cli-shell-utils.bash;get_drive $(get_live_dev) 
EXIT="abort"
lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259
. /usr/local/lib/cli-shell-utils/cli-shell-utils.bash;get_drive $(get_live_dev) 
Empty filename passed to function
Options:  "-N "
start io is  0
max progress bar is  1296384
live-usb-maker gui -N -C off --from="/home/koo/antiX-17.4.1_x64-base.iso" -t /dev/sdc

The above GUI burns were done on live-usb-maker-gui-antiX 0.2.2 before todays update to 0.2.3 after the update.

GUI Full featured burned and booted. Fixed

mv: cannot stat '/home/koo/scr/screenshot-thumb.jpg': No such file or directory
mv: cannot stat '/home/koo/scr/screenshot-thumb.jpg': No such file or directory
info: restarting jgmenu...
live-usb-maker-gui-antix version: 0.2.3
df -T / |tail -n1 |awk '{print $2}'
live-usb-maker --help | grep data-first
lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259
. /usr/local/lib/cli-shell-utils/cli-shell-utils.bash;get_drive $(get_live_dev) 
EXIT="abort"
Empty filename passed to function
Options:  "-N "
start io is  676
max progress bar is  1297060
live-usb-maker gui -N -C off --from="/home/koo/antiX-17.4.1_x64-base.iso" -t /dev/sdc
""

[Member ile]

Hello anticapitalista
using hp 8440p antiX-19.b3_x64, 4.9.189-antix.1-amd64-smp x86_64,upgraded, spacefm-fluxbox
live-usb-maker 0.4.0 , live-usb-maker-gui-antix 0.2.3

2 using fluxbox menu, ControlCentre >Disks >Live USB Maker (gui)=
target usb2 100% Full-featured mode , checkmark Make the ext4 filesystem even if one exists. burn MX-19 beta-3_x64iso to device.
This live OS device booted yes normally to default desktop on one desktop Firsti3intel and on one notebook Firsti5intel machines.
one for one on #Test 2

3 target usb2 Image mode , burn antiX-19.b3_x64-fulliso to device.
This completed dd file device booted yes normally to default desktop on one desktop and on one notebook machines.
one for one on #Test 3

1 using fluxboxmenu, Applications >System >App Select >>Command Line Control Centre >>Execute or
using fluxbox menu, Applications >antiX >Command Line Control Centre >>Live System Centre >>live-usb-maker
target usb2 , full-featured, from ISO antiX-19.b3-full_x64. make_, copy.
This completed live OS device booted yes normally to default desktop on one desktop and on one notebook machines.
one for one on #Test 1

That is full success but just one trial each. The full-featured devices took five and a half minutes to burn.

• This reply was modified 3 years, 6 months ago by ile. Reason: additional machine trial

[Member seaken64]

It depends on whether you have access to the BIOS. In my case, I am the boss and the IT dept. So I have full access – and I am careful. But if your IT dept does not allow BIOS access to you it will be near impossible to boot anything other than what the IT dept allows you to boot.

If you have BIOS access you can turn on the features that allow booting from USB.

You may be able to run Virtual Machine software and “install” to a virtual machine from an .iso. I use Virtualbox for this. But again, you have to be permitted to run the software. You can keep your personal data on the USB even while the OS is on a VM.

Good luck, and have fun with antiX!

Seaken64

Hey antiXers!

After toying with antiX (17.4) and other LBOSes (Linux-based OSes) for a couple of weeks, especially what I call eye candy distros (Manjaro, ArcoLinuxB, endeavorOS, elementaryOS, MX-18.3) and slimmer ones (BionicPuppy, FatDog64, Slax, Porteus Mate), I settled on an install-to-HDD once I found antiX-19b3.

After a couple of Microsoft Windows 10 forced update screw-ups (the first one moved my data files to a new user account; the second one failed and put my machine into a coma), I knew I could put Linux on a stick from my days of toying with Puppy (circa 2010) as well as Knoppix and Damn Small Linux (circa 2001) to see if my data files (pictures, music, writings, etc.) were safe.

I knew also I could put the WIN 10 ISO to a stick and install again Windows because MS tracks all previous licensed installs by machine address.

I had thought about burning the MS WIN 10 ISO to a stick, but while awaiting for Amazon to deliver a USB 5-pack, I read more about the latest developments of Linux on distrowatch.com and other easy sites (lifewire, gHacks, mechtecheaser) and some more techy-oriented. I took some notes.

It was then I decided then I would give Linux another shot. I settled on lightweight ones, BionicPuppy and antiX-17.4. Also in the downloads were Bodhi, Lite, Sparky, Zorin and BionicDog. While waiting for those sticks my excitement for a LBOS grew.

Well, never did I get around to trying that latter roster because antiX-17.4 was too good out of the gate. I tried afterward the eye candy ones to see if I was missing anything. Those are simply too heavy, too constricting, too old paradigm.

During my two-week adventure, and having used cross-platform apps (Yandex and Dissenter Chromium-based browsers, VS Code), I made some key discoveries on my third time with Linux (note: Along with my 2010 and 2001 experiences, I tried Red Hat in 1996, but that failed on the extant hardware). Getting the AppImage of VS Codium (the no-telemetry version of VS Code), with symlinks and workspaces, it flashed before my eyes—like the browser having become the main UI—VS Codium is the all-everything for files. Right away, I turned it into a tree-based note taker. With that, I could ditch CherryTree and Geany. Why use a single-tasking tool (CherryTree) when one can use a multi-tasker?

Also in my adventure of using antix-17.4 and getting up-to-speed on the command line, mounting, package management, AppImage vs Flatpak and Snap, symlinks, Rox, Fluxbox, getting media keys to work and a host of other things, I discovered that “community” might be the most overused, wrongly used word in English, especially by the Linux world. There are no communities, there are only tribes, insular tribes with stubborn views of things. Most are quite childish (e.g., the Archers, aka Arch Linux tribe), people who believe they should be rewarded with awe because they have memorized things rather than having natural insight into things.

Anyway, I plan to respin this antiX into something that turns a computer into a productivity machine. Here is a hint: Most OSes, e.g., Microsoft Windows, macOS, and the eye candy distros (e.g., elementaryOS, Manjaro, Ubuntu, et. al, keep people focused on using the computer, i.e., “what is the app to do X?” rather than getting done stuff.

Yet, done right, all of that can fade into the background, which should let the computer become a container for a work-focused / activity-focused approach.

Using ROX the right way lets one do that. The same holds true with using the browser or something like VS Codium with markdown files.

The Linux World has come into its own, truly. There are neat possibilities, like using FUSE (filesystems in user space) to create app, maybe like a Tiddlywiki (tiddlywiki.com) using markdown files in a tree inside a ROX directory.

On a side note: Putting on a partition 17.4 in a frugal install, my remastered Live USB would not do a full install on the same partition. After booting up the first time with antiX but before the frugal install, I set up the box with a swap (primary), ext4 (primary) and a NTFS (primary). Later, I let ArcoLinuxB cut that ext4 primary in half for its install.

Later still, I turned it into an extended container with a few virtual (aka logical) partitions, one of which is where antix-19b3 sits as a full install.

Anyway, there is much more to come. I’m considering blogging and bitchuting about my antiX and Linux experience from the viewpoint of practical people who use computers as means to an end (e.g., android-based phones, set-top boxes, thermostats) rather than the means being the end, if you catch my meaning. I will let you know URLs and such if that happens.

I welcome all of you to my antiX journey.

• This topic was modified 3 years, 7 months ago by JohnGritt.