Search Results for 'boot from iso'

[Member sybok]

Two suggestions what to try:
IGNORE THIS ONE: 1) Which version of the ISO did you download (what is the name of the ISO file)?
If it contains ‘net’ or ‘core’, then run the bellow command that includes ‘install’:
sudo apt update && sudo apt install cli-installer-antix
Mentioned in the thread with the installer issue (referred by @skidoo) by anticapitalista.
If the cli-installer-antix is already installed, then the upgrade should replace it with the newest version.
If it is not installed, in ‘net’ or ‘core’, then you must install it first.

BTW, you may want to try the ‘full’ antiX version instead.
It has graphical user interface installed and it is more friendly to the beginners.

Command explanation: && = execute the following command only if the previous command terminated successfully

2) [The same thread] fatmac mentions to perform the (manual) partitioning, then reboot so that the partition changes are correctly detected by the system.

EDIT: Sorry, I did not notice the ‘full’ in the output of the inxi command. 🙁

• This reply was modified 2 years, 5 months ago by sybok.
• This reply was modified 2 years, 5 months ago by sybok. Reason: Restructured (1st edit), sudo (2nd edit)
• This reply was modified 2 years, 5 months ago by sybok.

[Anonymous]

Test at your own risk

virtualbox instance, FTW

First boot, as soon as I attempted apt update, it’s trying to ?setup “firmware-b43legacy-installer” and apparently tries to download something from openwrt.org … and fails with an errormsg “some problem occurred during the firmware download. Please check your network connection.”

apt purge firmware-b43legacy-installer
and carry on…

Hmm, buster-backports is permanently enabled, from the get-go.
I’ve been operating under the impression that leaving it permantly enabled was inadvisable.

suggest:
add a line to /etc/skel/.profile
export NO_AT_BRIDGE=1
to suppress gtk accessibility warning messages

privacy-unfriendly:
app called “celluloid” ships with default preferences set to “automatically retrieve metadata” ~~ calls out to a webserver

noted: at start of session, conky shows 59.5MB used

it’s a very solid result. Congrats on your quick mastery of build-iso !

[Member Xecure]

Because of my inexperience, I have been fighting with the Build-iso (created and used by the antiX team for building all antiX releases), and think I have a “more or less” got it to work.
I had to use the initrd and boot folders from the latest iso-template-antix package as nothing else worked for me.
I got it to boot in a VM with safe videomode (and it doesn’t auto log-in 🙁 ), but didn’t test on real hardware yet.

Test at your own risk. Just try to boot it once or twice with and without safe video options and see if you can get to a graphical environment on the problematic sis and via machines. If it doesn’t work, I will keep experimenting on the coming weekend.

This iso is built on antiX 19.3 i386 base + updates (for some reason I couldn’t install the broadcom drivers package, so hopefully you don’t need them).
Differences with main antiX release:
– Kernel: 4.4.240-antix.2-486 i686 (not sure if it is the right one).
– Xorg version 1.16.4 (same as antiX 16) put on hold.
– ISO size: 770 MBs
Only download and test if you have free time. This is probably a failed experiment, so I don’t have much hope anything good can come from it.

Special thanks to anticapitalista for updating the build-iso project on my request.

Download link: https://drive.google.com/file/d/1PSMBcPy5kjVCTa07bQhkvw4jvrOBcITn/view?usp=sharing

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

[Anonymous]

> When I boot other OS’s, I miss the […] power to create respins.

(from 2012!) topic: refracta-installer-and-snapshot-used-on-other-distros
skidoo == thwak
.
(search in page: refracta)
http://www.extix.se/
http://ftp.svenskalinuxforeningen.se/distributions/exton/
.
devuan + TrinityDesktopEnvironment (KDE3) + refracta snapshot/installer
http://exegnulinux.net/

As has been previously discussed in antixforum (and, as notated within script header comments) the antiX snapshot utility forked from refractasnapshot antixlinux.com/forum-archive/antix-test-versions-to-play-with back around 2012.

Here is an excerpt of content from the most recent refractasnapshot release:
(pasted to pastebin)
— the bash script
— default conf file
— readme doc
— copy of the liveboot “F1” help menu text, page 3 (packed within the provided initrd)

a separately packaged “gui” version (employs yad dialogs) is available from the refracta project site at sourceforge

It seems to need SysV and does not work on Debian with systemd.
Would iso-snapshot-antix work on antiX with runit as init software?

You would need to unpack the initrd (a cpio archivefile)
( on antiX, see: /usr/local/lib/cli-shell-utils/bin/unpack-initrd )
and examine/edit the live init.
As a final operation, the live init script “hands over” (exec pivot_root command) control. As written, it (both the antiX and in Refracta versions) hands off to /sbin/init
.
If you want “runit” or “systemd”, you would need to edit the script to “hand off to” whichever executable shall launch PID1.

Original title in Brazilian Portuguese: How to use antiX on computers with a motherboard with SIS or VIA chipset

Hello Anticapitalista and antiX Developers

You already know that I am a beginner in this “world of Linux distributions”, I arrived here at antiX in June 2020, since then, I am learning a lot from our colleagues in the forum. I know I still have a lot to learn, so my considerations below are still of a limited view on the subject.

The information I searched for on the internet indicates “that most drivers are in the kernel”

Motherboard of the brand ASUS, as it will be in the following example, of the model P5S800-VM (with chipset SIS), when they arrived in Brazil they were the dream of consumption of several computer users (including mine), at the time who did not have financial conditions to buy an ASUS or Gigabyte motherboard, I bought MSI 238318 or STI 910090 (with Via chipset) or one made in China and then suffered to find the drives, Two other computers from the NGO arrived for me to prepare, but because they are computers with motherboard with SIS chipset and another with VIA antiX 19.3 or 19.2 make the video very slow, failing and with “ghosts”. It is impossible to use the operating system like that.

I applied all the teachings on the topic https://www.antixforum.com/forums/topic/how-to-set-the-set-gfxmode-1024x768x16-1024×768/ to identify ASUS P5S800- branded motherboard devices VM. (Commands are available after the original Brazilian Portuguese text)

Due to the teachings of the topic I mentioned earlier, antiX 16.3 will certainly work, with these two computers that have only 1GB of DDR RAM. I will need to install a full 32-bit version in order to save as much RAM as possible, but I have some doubts:

1-antiX 16.3 had its “end of life” on June 6, 2020 or I can also understand that it was discontinued. Do the repositories still work for antiX 16.3 full 32 bits and antiXfull 64 bits?

2- If the repositories still work for antiX 16.3 32 bits and antiX 64 bits, how much longer will they be available?

The antiX 16.3 64 bits that I prepared for the computer with the VIA motherboard and 2GB of DDR RAM, from the topic I mentioned earlier. At the time, for example, I was unable to install the LibreOffice translations that already come with antiX. What I did to get around this, was to download the LibreOfficetraduced AppImage for PT-BR and the other programs were with AppIamge. I managed to make antiX 16.3 64 bits friendly to the end user with the programs and with the Menu translated to PT-BR added in the Personal Menu. All of these were palliative solutions, but 32-bit AppImage practically does not exist, it will be difficult to use antiX 16.3 32 bits. I still don’t know how to prepare AppImage to be able to use in antiX 16.3 32 bits. When I learn to create AppImage, if ever I will learn to do it, as I cannot find consultation material in Portuguese teaching how to create the 32-bit AppImage. All the material is available for consultation in the English language and usually refer to to 64 bits. Translations remain a daily challenge, it is not enough to translate the words, it is necessary to adapt the text so that the words can make complete sense in the sentences, but this is not always possible, as they depend on the context being used. Therefore, I continue to dedicate myself to make each text the best possible on the site transifex for PT-BR for antiX.

After this long introduction, there are the next questions, which are the important ones in this topic:

3-Would it be possible to create antiX 19.3 with the antiX 16.3 kernel?

Since I got here (on antiX and the forum), I have stopped searching for other Linux distributions. I already know that this is my place, I met excellent people here. But if it is not possible to use an antiX due to the drivers, unfortunately, I will have to continue the search, just so that I can continue saving old computers (that are working) from being thrown in the trash.

I hope, Anticapitalista, that you and the developers can evaluate this topic and analyze if this is possible or if it is feasible to accomplish. I know that there are already several antiX options and these options require a lot of work time to be produced and made available.

Regardless of the answer, I thank you for creating and making antiX available.

Thank you.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Título original em Português do Brasil: Como utilizar o antiX em computadores com placa-mãe com chipset SIS ou VIA

Olá Anticapitalista e Desenvolvedores do antiX

Vocês já sabem que eu sou iniciante neste “mundo das distribuições Linux”, cheguei aqui no antiX em Junho de 2020, desde então, eu estou aprendendo muito com os nossos colegas do fórum. Eu sei que ainda tenho muito o que aprender, por isso as minhas considerações a seguir ainda são de uma visão limitada sobre o assunto.

As informações que eu pesquisei na internet indicam “que a maioria dos drivers estão no kernel”

Placa-mãe da marca ASUS, como será no exemplo a seguir, do modelo P5S800-VM (com chipset SIS), quando chegaram no Brasil eram o sonho de consumo de vários usuários de computador (inclusive o meu), na época quem não tinha condições financeiras de comprar placa-mãe ASUS ou Gigabyte, comprava MSI 238318 ou STI 910090 (com chipset Via) ou alguma fabricada na China e depois sofria para encontrar os drives, Chegaram outros dois computadores da ONG para eu preparar, mas por serem computadores com placa-mãe com chipset SIS e outra com VIA o antiX 19.3 ou 19.2 ficam com o vídeo muito lento, falhando e com “fantasmas”. É impossível utilizar o sistema operacional assim.
 
Eu apliquei todos os ensinamentos do tópico https://www.antixforum.com/forums/topic/how-to-set-the-set-gfxmode-1024x768x16-1024×768/ para identificar os dispositivos da placa-mãe da marca ASUS P5S800-VM. (Os comandos estão disponíveis após o texto original em Português do Brasil)

Devido aos ensinamentos do tópico que citei anteriormente, o antiX 16.3 certamente irá funcionar, com estes dois computadores que possuem apenas 1GB de memória RAM DDR. Eu precisarei instalar o uma versão full 32 bits para poder economizar o máximo possível de memória RAM, mas tenho algumas dúvidas:      

1-O antiX 16.3 teve o seu “fim de vida” no dia 06 de junho de 2020 ou também posso compreender que foi descontinuado. Os repositórios ainda funcionam para antiX 16.3 full 32 bits e para o antiXfull 64 bits?

2- Se os repositórios ainda funcionam para antiX 16.3 32 bits e para o antiX 64 bits, por quanto tempo mais estarão disponíveis?

O antiX 16.3 64 bits que eu preparei para o computador com a placa-mãe VIA e 2GB de memória RAM DDR, do tópico que citei anteriormente. Na ocasião, por exemplo, eu não consegui instalar as traduções do LibreOffice que já vem com o antiX. O que eu fiz para contornar isso, foi baixar o AppImage do LibreOfficetraduzidos para PT-BR e os demais programas foram com os AppIamge. Eu consegui tornar antiX 16.3 64 bits amigável para o usuário final com os programas e com o Menu traduzido para PT-BR adicionado no Menu Pessoal. Todas estas foram soluções paliativas, mas AppImage de 32 bits praticamente não existem, ficará difícil utilizar o antiX 16.3 32 bits. Eu ainda não sei preparar AppImage para poder usar no antiX 16.3 32 bits. Quando eu aprender a criar AppImage, se é que um dia eu conseguirei aprender a fazer isso, pois não encontro material de consulta em Português ensinando a criar o AppImage de 32 bits Todo o material está disponível a para consulta em idioma Inglês e normalmente se referem a 64 bits. As traduções continuam sendo um desafio diário, não basta traduzir as palavras, é preciso adaptar o texto para que as palavras possam fazer sentido completo nas frases, mas nem sempre isso é possível, pois dependem do contexto que estão sendo utilizadas. Por isso, continuo me dedicando para fazer cada texto o melhor possível no site transifex para PT-BR para o antiX.            

Depois desta longa introdução, vem as próxima perguntas, sendo estas as importantes deste tópico: 

3-Seria possível criar o antiX 19.3 com o kernel do antiX 16.3?  

Desde que eu cheguei aqui (no antiX e no fórum), eu parei de pesquisar outras distribuições Linux. Eu já sei que aqui é o meu lugar, eu encontrei aqui pessoas excelentes. Mas se não for possível utilizar um antiX devido aos drivers, infelizmente, eu terei que continuar a busca, só para eu poder continuar salvando computadores antigos (que estão funcionando) de serem jogados no lixo.

Eu espero, Anticapitalista, que você e os desenvolvedores possam avaliar este tópico e analisar se isso é possível ou se é viável de ser realizado. Eu sei que já existem várias opções de antiX e estas opções exigem bastante tempo de trabalho para serem produzidas e disponibilizadas.

Independentemente da resposta, eu agradeço por criarem e disponibilizarem o antiX.

Muito obrigado.   

marcelocripe
(Texto original em Português do Brasil)

demo@antix1:~
$ inxi -Fxz
System:
Host: antix1 Kernel: 4.9.235-antix.1-486-smp i686 bits: 32 compiler: gcc
v: 8.3.0 Desktop: IceWM 1.8.3
Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Desktop Mobo: ASUSTeK model: P5S800-VM v: Rev 1.xx serial: <filter>
BIOS: American Megatrends v: 1022.001 date: 05/11/2006
CPU:
Topology: Single Core model: Intel Celeron bits: 64 type: MCP
arch: Netburst Smithfield rev: 9 L2 cache: 256 KiB
flags: lm pae sse sse2 sse3 bogomips: 5306
Speed: 2653 MHz min/max: N/A Core speed (MHz): 1: 2653
Graphics:
Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or
662/761Gx PCIE VGA Display Adapter
vendor: ASUSTeK driver: N/A bus ID: 01:00.0
Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1024×768~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
direct render: Yes
Audio:
Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound
vendor: ASUSTeK driver: snd_intel8x0 v: kernel bus ID: 00:02.7
Sound Server: ALSA v: k4.9.235-antix.1-486-smp
Network:
Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
vendor: ASUSTeK P5P800-MX Mainboard driver: 8139too v: 0.9.28 port: e400
bus ID: 00:0b.0
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 7.27 GiB used: 14.3 MiB (0.2%)
ID-1: /dev/sda type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB
RAID:
Hardware-1: Silicon Integrated Systems [SiS] RAID bus controller 180
SATA/PATA [SiS]
driver: sata_sis v: 1.0 bus ID: 00:05.0
Partition:
ID-1: / size: 744.0 MiB used: 2.3 MiB (0.3%) fs: overlay source: ERR-102
Sensors:
Message: No sensors data was found. Is sensors configured?
Info:
Processes: 133 Uptime: 12m Memory: 964.9 MiB used: 103.2 MiB (10.7%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3
inxi: 3.0.36

demo@antix1:~
$ inxi -G
Graphics:
Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or
662/761Gx PCIE VGA Display Adapter
driver: N/A
Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1024×768~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6

demo@antix1:~
$ inxi -v8
System:
Host: antix1 Kernel: 4.9.235-antix.1-486-smp i686 bits: 32 compiler: gcc
v: 8.3.0
parameters: vga=0x0317 lang=pt_BR tz=America/Sao_Paulo quiet splasht
disable=lxF xorg=safe
Desktop: IceWM 1.8.3 dm: SLiM 1.3.6
Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Desktop Mobo: ASUSTeK model: P5S800-VM v: Rev 1.xx
serial: <root required> BIOS: American Megatrends v: 1022.001
date: 05/11/2006
Memory:
RAM: total: 964.9 MiB used: 105.8 MiB (11.0%)
RAM Report:
permissions: Unable to run dmidecode. Root privileges required.
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Topology: Single Core model: Intel Celeron bits: 64 type: MCP
arch: Netburst Smithfield family: F (15) model-id: 4 stepping: 9
microcode: 3 L2 cache: 256 KiB bogomips: 5306
Speed: 2653 MHz min/max: N/A Core speed (MHz): 1: 2653
Flags: acpi apic bts cid clflush cmov constant_tsc cx16 cx8 de ds_cpl
dtes64 dts fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr pae pat pbe
pebs pge pni pse pse36 sep ss sse sse2 tm tm2 tsc vme xtpr
Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable
Type: l1tf status: Vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown status: Vulnerable
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or
662/761Gx PCIE VGA Display Adapter
vendor: ASUSTeK driver: N/A bus ID: 01:00.0 chip ID: 1039:6330
Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1024×768~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: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound
vendor: ASUSTeK driver: snd_intel8x0 v: kernel bus ID: 00:02.7
chip ID: 1039:7012
Sound Server: ALSA v: k4.9.235-antix.1-486-smp
Network:
Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
vendor: ASUSTeK P5P800-MX Mainboard driver: 8139too v: 0.9.28 port: e400
bus ID: 00:0b.0 chip ID: 10ec:8139
IF: eth0 state: down mac: XX:XX:XX:XX:XX:XX (I changed the MAC to XX/eu alterei o MAC para XX)
WAN IP: No WAN IP data found. Connected to the web? SSL issues?
Drives:
Local Storage: total: 7.27 GiB used: 14.3 MiB (0.2%)
ID-1: /dev/sda type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB
block size: physical: 512 B logical: 512 B
serial: 001CC0EC330FEB816605000A rev: PMAP scheme: MBR
Floppy-1: /dev/fd0
RAID:
Hardware-1: Silicon Integrated Systems [SiS] RAID bus controller 180
SATA/PATA [SiS]
driver: sata_sis v: 1.0 port: 0000 bus ID: 00:05.0 chip ID: 1039.0180
rev: 01
Partition:
ID-1: / raw size: N/A size: 744.0 MiB used: 2.3 MiB (0.3%) fs: overlay
source: ERR-102 label: N/A uuid: N/A
ID-2: /live/boot-dev raw size: 1.17 GiB size: <root required>
used: <root required> fs: N/A dev: /dev/ventoy label: N/A uuid: N/A
ID-3: /live/linux raw size: 1.14 GiB size: <root required>
used: <root required> fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A
ID-4: /media/VTOYEFI raw size: 32.0 MiB size: 31.9 MiB (99.75%)
used: 12.0 MiB (37.4%) fs: vfat dev: /dev/sda2 label: VTOYEFI
uuid: ADB8-4480
Unmounted:
ID-1: /dev/dm-0 size: 1.17 GiB fs: <root required> label: N/A uuid: N/A
ID-2: /dev/sda1 size: 7.24 GiB fs: exfat label: Ventoy uuid: 4E21-0000
USB:
Hub: 1-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0
speed: 480 Mb/s chip ID: 1d6b:0002
Device-1: 1-4: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: 001CC0EC330FEB816605000A
Device-2: 1-8:3 info: Alcor Micro Flash Card Reader/Writer
type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0
speed: 480 Mb/s chip ID: 058f:6362 serial: 058F312D81B
Hub: 2-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 3-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Sensors:
Message: No sensors data was found. Is sensors configured?
Repos:
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://mirror.ufam.edu.br/mx/antix/buster buster main nonfree nosystemd
Active apt repos in: /etc/apt/sources.list.d/buster-backports.list
1: deb http://deb.debian.org/debian buster-backports main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.br.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.br.debian.org/debian/ buster main contrib non-free
2: deb http://security.debian.org/ buster/updates main contrib non-free
No active apt repos in: /etc/apt/sources.list.d/onion.list
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes:
CPU top: 5
1: cpu: 34.5% command: xorg pid: 3302 mem: 47.3 MiB (4.8%)
2: cpu: 0.9% command: [rcu_sched] pid: 7 mem: 0.00 MiB (0.0%)
3: cpu: 0.6% command: slim pid: 3284 mem: 10.2 MiB (1.0%)
4: cpu: 0.6% command: conky pid: 3640 mem: 10.4 MiB (1.0%)
5: cpu: 0.5% command: [ksoftirqd/0] pid: 3 mem: 0.00 MiB (0.0%)
Memory top: 5
1: mem: 47.3 MiB (4.8%) command: xorg pid: 3302 cpu: 34.5%
2: mem: 26.0 MiB (2.6%) command: roxterm pid: 4081 cpu: 0.2%
3: mem: 25.5 MiB (2.6%) command: rox pid: 3558 cpu: 0.1%
4: mem: 16.4 MiB (1.6%) command: volumeicon pid: 3571 cpu: 0.0%
5: mem: 14.3 MiB (1.4%) command: fbxkb pid: 3591 cpu: 0.0%
Info:
Processes: 133 Uptime: 14m 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.36

demo@antix1:~
$ lspci -v
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host (rev 11)
Subsystem: ASUSTeK Computer Inc. 661FX/M661FX/M661MX Host
Flags: bus master, medium devsel, latency 32
Memory at e0000000 (32-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: agpgart-sis

00:01.0 PCI bridge: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge) (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, fast devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: dfe00000-dfefffff
Prefetchable memory behind bridge: cfd00000-dfcfffff
Kernel modules: shpchp

00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] LPC Controller (rev 36)
Flags: bus master, medium devsel, latency 0
Kernel modules: i2c_sis630

00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE Controller (rev 01) (prog-if 80 [ISA Compatibility mode-only controller, supports bus mastering])
Subsystem: ASUSTeK Computer Inc. 5513 IDE Controller
Flags: bus master, medium devsel, latency 128, IRQ 16
I/O ports at 01f0
I/O ports at 03f4
I/O ports at 0170
I/O ports at 0374
I/O ports at ffa0
Capabilities: <access denied>
Kernel driver in use: pata_sis

00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC’97 Sound Controller (rev a0)
Subsystem: ASUSTeK Computer Inc. SiS7012 AC’97 Sound Controller
Flags: bus master, medium devsel, latency 64, IRQ 18
I/O ports at e800
I/O ports at ec00
Capabilities: <access denied>
Kernel driver in use: snd_intel8x0
Kernel modules: snd_intel8x0

00:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. USB 1.1 Controller
Flags: bus master, medium devsel, latency 64, IRQ 20
Memory at dfff4000 (32-bit, non-prefetchable)
Kernel driver in use: ohci-pci

00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. USB 1.1 Controller
Flags: bus master, medium devsel, latency 64, IRQ 21
Memory at dfff5000 (32-bit, non-prefetchable)
Kernel driver in use: ohci-pci

00:03.2 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. USB 1.1 Controller
Flags: bus master, medium devsel, latency 64, IRQ 22
Memory at dfff6000 (32-bit, non-prefetchable)
Kernel driver in use: ohci-pci

00:03.3 USB controller: Silicon Integrated Systems [SiS] USB 2.0 Controller (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. USB 2.0 Controller
Flags: bus master, medium devsel, latency 64, IRQ 23
Memory at dfff7000 (32-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: ehci-pci

00:05.0 RAID bus controller: Silicon Integrated Systems [SiS] RAID bus controller 180 SATA/PATA [SiS] (rev 01) (prog-if 85)
Subsystem: ASUSTeK Computer Inc. RAID bus controller 180 SATA/PATA [SiS]
Flags: bus master, 66MHz, medium devsel, latency 128, IRQ 17
I/O ports at eff0
I/O ports at efe4
I/O ports at efa8
I/O ports at efe0
I/O ports at ef90
I/O ports at 0000
Kernel driver in use: sata_sis

00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
Flags: bus master, medium devsel, latency 64, IRQ 19
I/O ports at e400
Memory at dfff3c00 (32-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: 8139too
Kernel modules: 8139cp, 8139too

01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. SiS Real 256E (ASUS P5S800-VM motherboard)
Flags: 66MHz, medium devsel, IRQ 11
BIST result: 00
Memory at d0000000 (32-bit, prefetchable)
Memory at dfee0000 (32-bit, non-prefetchable)
I/O ports at dc00
[virtual] Expansion ROM at 000c0000 [disabled]
Capabilities: <access denied>

demo@antix1:~
$ cat /proc/cmdline
vga=0x0317 lang=pt_BR tz=America/Sao_Paulo quiet splasht disable=lxF xorg=safe
demo@antix1:~

[Moderator BobC]

When I boot other OS’s, I miss the ISO-Snapshot and Live-USB-Maker combo., especially the Personal/General option, which really gives it the power to create respins.

[Anonymous]

Is Timeshift much different from ISO-Snapshot or doing virtually the same?

What is the work product, the output, of Timeshift?
An ISO file? A mapped rsync directory tree? A backupdata.pqz archive file?
.
Neither Timeshift nor BackInTime capture the state of the FULL operating system, per their default settings, IIRC.

Is there a way to assemble such dependent infrastructure

“infrastructure” really isn’t an accurate term here.
I would say that the defining difference is one of “finesse” ~~ reasoning what to backup, vs what to include, vs what files to substitute (pristine copies of) in the produced output.

[recognize] this antiX/MX superiority and try to re-create

Is it a matter of superiority, though, or just a matter of pursuing different goals?
(skimread, 45seconds)
https://live-team.pages.debian.net/live-manual/html/live-manual/about-project.en.html#86

Porteus, Puppylinux, and others do have utilities similar to snapshot.
Usually the functionality overlaps (backup+remaster)
and attention to that, I reckon, is where the term “infrastructure” crept in.
(creation of “deb” or “sfs” packages, setup and maintenance of package repositories…)

Booting puppylinux, at each boot you might pick-n-choose which bundles to load (not loading “stuff” you won’t need during today’s session, in order to achieve a smaller memory footprint) but you will lack the presumed benefit of having available a “package manager” which knows/tracks which programs are installed and are up-to-date (cannot guess//presume which currently unloaded sfs bundles may be downloaded and//or loaded). Rhetorically: Is that scenario comparatively superior, inferior, or just different?

Hi,
how to install a full antix desktop from a core install?
is there a magic sudo apt install antix-desktop ?

I succeeded to install antix from the core iso burned on a CDrom (no boot from usb). I also failed to install a full antix desktop from the full iso burned on dvd.

thank you

• This topic was modified 2 years, 5 months ago by jeanpat.

[Member DaveW]

Moddit, These cards are micro-SD. As far as I know, they don’t have a lock switch. But you make a good point regarding the regular SD cards, or SD to micro-SD adapters.

I reformatted the original micro-SD (that might have been corrupted), and remade the LiveUSB from the same iso, using the D620 computer and the USB to microSD adapter. The make LiveUSB process went smoothly. But Boot-up still fails after the login dialogue.

However, the same microSD, placed in an SD to microSD adapter, boots up nicely in my Asus eeepc900. (The D620 computer does not have an SD slot.) With the same microSD card in a USB to microSD adapter, the eeepc fails at the same place as the D620.

I’ll see if the guy who sold me the USB adapter has any clues.

Thanks to all for your suggestions.

[Member chevyiron420]

I am currently using 17.4.1 base, but have tried full iso’s on usb as well.It seems to have less problems booting from a cd.
Also, if I disable my onboard video and install a pci card it will boot and work.However its only a one meg card and performance is horrible.

[Forum Admin rokytnji]

Try some boot cheat codes.

https://download.tuxfamily.org/antix/docs-antiX-19/Boot_Menu/antiX-gfxboot.html

Also. You using full iso or base iso?

32 bit for sure.

Gateway? Surprised it survived. 512MB of ram would be better.

Gateway Essential 433c System Details
System Information

Kingston Part No: SGY-P450/128
Kingston Part No: KGT-1000/32
Kingston Part No: SGY-P450/64
Total Memory Slots: 2
Maximum Memory: 512
Standard Memory: 128
System Type: Desktop/Server
Module Type: PC100
Module Type: PC66
Form Factor: DIMM
ECC: FALSE
Registered: None

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

I am working on a gateway essential 433c with 256mb. antix 16-b2.1 will boot normally and install fine, but nothing else will. I would like to install 17.4 on it. it will go through the boot prosess then after the login prompt, black screen. Te cd drive continues to run. This happens with every other iso i try. video is intel 82810. Can you help?

I just want to share my experiences for the benefit of other antiX users who might want to pursue a similar strategy.
The text is written for the real beginner, step by step and as detailed as possible, so the old-timer might feel a little impatient and bored while reading. But I’m sure he could amend some improvements of the workflow in the end.

As I’ve stated elsewhere here in the forum, my final goal is to have the antiX system installed on the hdd of my notebook.
But what about the old, well oiled and fine tuned system installed on it? I prefer to keep it, since there are many helper programs installed, which I’ll probably won’t notice missing before I need one of them again, which then isn’t installed on the antiX system yet and then I could’nt remember its name, which causes me researching for some hours again.
Moreover there are some homebrew shellscripts for solving dedicated problems stored on it, which I also don’t remember exactly what and where, but if I need one, I’ll know: It has bin there and there.
From past times I remember, when dd-ing the complete hdd or partition two things will happen:
The resulting partition-images are not really handy, they need to be cut into parts, compressed to fit on a couple of DVD and I’ll probably never again have the diskspace to recreate and re-open them when I’d like to search them for a script or program I perfectly know I’ve had at hand for a special task in the old system. The second thing to happen is: Taking the before said into account, I will litter them, after having stored them for years without having any way to make use of them.
So this time I decided to manage things the another way around:
I want to move the complete existing system from hdd to an usb-stick, keeping it bootable and usable, just as antiX runs now from the stick. The roles will be changed after that. antiX will boot form hdd, and the old system will boot from the stick.

I’ll repartition the hdd to current needs (it’s still partitioned as historically grown by successively installing
different operating systems, which means: a couple of pretty small partitions, in a crude order spread over the hdd. I’d prefer to make a clean cut and from now on use GPT instead of MBR, which should be possible even when this notebook does only provide BIOS, (no EFI). Then I’ll create one small (2 GiB) Boot partition, one 12GiB for / (root), one swap (4GB) and all the remaining space will be used for the /home partition. I’ll try to use Extlinux instead of grub now, the isolinux/syslinux bootprocess on antiX-live/persist has been convincing. And after these preliminaries I’ll finally install antiX in the newly created hdd structure. That is the line of approach.

Back to the first step:
Exporting the complete system to a memory stick. Sounds easy, but there are some pitfalls. Sounds difficult on the other hand, but it isn’t really.

First I had to prepare the USB-memory-stick. It is a cheap standard 64GB USB2/3 type, preformatted for use on Windows-systems. I’ll give a step by step explanation of the complete process just in case someone wants to undertake the same procedure before installing antiX.

(Make sure to use the fastest USB your PC provides. Some older models have USB 1.x and 2.0 both, and using the 1.0 only will slow things really down. Everything from 2.0 upwards should be ok, but it works even with 1.0, if you have no choice. You can check with lsusb as described below.)

Boot from antiX live-USB-Stick (or from CD/DVD). Don’t use a frugal install for this since it uses the hdd, possibly partitions you need to be untouched (unchanged) during the process.

Open a terminal (Menu–>Terminal), type “sudo su” and give your sudoer-password. (As you probably know, since it can be found in the antiX manuals, the standard PW for a non-persistent live system is “demo”.) Keep this terminal open until we’ve finished. Some people prefer to prefix every single command they key in with “sudo”. You can do it that way as well, omit simply the line “sudo su” and set sudo in front of each command instead.
hint:
– the “#” shows that you are in the role of “root” in that very moment, the command you key in is executed with root privileges.
– the “$” denotes that you are in simple user context and the commands are executed with the restricted privileges of the actual user.

You’ll always find these marks in the terminal somewhere at the beginning of the commandline.
Don’t key in these signs, only the commands behind them.

 
        $ sudo su
	demo		<--- sudoer pw in antiX live, key in when asked.
	# lsusb
	# lsblk

Example Output of lsusb and lsblk (before pluging in the new stick):

# lsusb
Bus 001 Device 003: ID 090c:2000 Silicon Motion, Inc. - Taiwan			<--after knowing which bus is capable of USB2.0 we can see antiX live stick is pluged in one of the proper slots already.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub   <--here we have the USB2.0 Hub, look for which bus-Number it has
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 093a:2533 Pixart Imaging, Inc.              <--this is an USB-mouse only, at one of the USB1.1 plugs.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
# lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0     7:0    0  2,6G  1 loop /live/linux	  <- these two loop-entrys belong to the antiX live system.
loop1     7:1    0  1,5G  0 loop /home					it is *not* your home-partition on your hdd, it contains antiX user "demo".
sda       8:0    0 93,2G  0 disk 				  <--here starts the hdd
├─sda1    8:1    0    8G  0 part /media/_daten1	  <--this is the primary partition, originally used by another OS, nowadays used as file-storage
├─sda2    8:2    0    1K  0 part 				  <--this is the extended partition (look at its size)
├─sda5    8:5    0   20G  0 part /media/_home	  <--this is the first logical partition within the extended partition
├─sda6    8:6    0   10G  0 part /media/_daten2	  <--another partition previously used by an even older OS , now file-storage
├─sda7    8:7    0 42,5G  0 part /media/_daten3   <--this was preveously the home-partition of that even older OS, now file-storage
├─sda8    8:8    0    3G  0 part /media/_daten4   <--another historically grown partition now in use as file-storage. 
├─sda9    8:9    0  2,2G  0 part [SWAP]			  <--this is the swap-partition of the old ubuntu system
└─sda10   8:10   0  7,5G  0 part /media/sda10	  <--this is actually the root partition of the old ubuntu system.
sdb       8:16   1 29,5G  0 disk 					<--here starts the USB stick with antiX on it, even if it is named "disk" here.
├─sdb1    8:17   1 29,5G  0 part /live/boot-dev		<--this is one of its partitions
└─sdb2    8:18   1   50M  0 part /media/antiX-uefi	<--and that is the other one.
sr0      11:0    1 1024M  0 rom  					<--finally we have a cd/dvd-drive.

This PC has as well 1.x as 2.0 USB connectors, you’ll have to look for the description at the end of the line for the word “2.0 root hub” (or even higher) and then at the beginning of that line where is written the bus number, in this example it is bus 001. Now look for what else is connected to that very bus number. In this case there is a Bus001 Device 003, which is the Live antix USB stick. Nice to know it sits on USB2.0 bus also. On one of the USB 1.1 plugs you can see the mouse (Bus 002, Device 002 in my example)

The partition order and usage is a little confused, since it is historicaly grown ;). Never mind, it’ll work anyway, since the partitions used for file-storage don’t need to be transferred to the stick. They’ll get stored elsewhere later on to free up the harddrive completely, which will be a really easy job then. The concern for today is to move the existing OS to a stick from within antiX live and make it bootable at its new residence.

Plug in the fresh USB-Stick. key in again:

	# lsusb
	# lsblk

Example output (after pluging new stick):

#lsusb
Bus 001 Device 003: ID 090c:2000 Silicon Motion, Inc. - Taiwan
Bus 001 Device 004: ID 058f:6387 Alcor Micro Corp. Flash Drive	<--the new USB-stick, connected also to USB2.0 capable slot.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 093a:2533 Pixart Imaging, Inc. 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
#lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0     7:0    0  2,6G  1 loop /live/linux
loop1     7:1    0  1,5G  0 loop /home
sda       8:0    0 93,2G  0 disk 
├─sda1    8:1    0    8G  0 part /media/_daten1
├─sda2    8:2    0    1K  0 part 
├─sda5    8:5    0   20G  0 part /media/_home
├─sda6    8:6    0   10G  0 part /media/antiX
├─sda7    8:7    0 42,5G  0 part /media/_daten3
├─sda8    8:8    0    3G  0 part /media/_daten4
├─sda9    8:9    0  2,2G  0 part [SWAP]
└─sda10   8:10   0  7,5G  0 part /media/sda10
sdb       8:16   1 29,5G  0 disk 
├─sdb1    8:17   1 29,5G  0 part /live/boot-dev
└─sdb2    8:18   1   50M  0 part /media/antiX-uefi
sdc       8:32   1 58,6G  0 disk 									<--here we are!
└─sdc1    8:33   1 58,6G  0 part /media/sdc1-usb-Generic_Flash_Di	<--and this is the (empty) partition the manufacturer has put on it.
sr0      11:0    1 1024M  0 rom  

After plugging the new stick to an USB-connector, it should better be also located at bus 001, since we know by now this is the one which provides USB2.0 in this case. If not, try another plug and restart this procedure.
The Plugs aren’t to distinguish optically from outside. You’ll have to adapt the concept to what you will find at your PC, maybe you even find USB3.0

Compare the output of the first with the second lsblk command. The enty which hasn’t been present there before is the devicename of the USB-stick for now (It will be changed when you plug it later again, depending on what else drives you have pluged in which order before, it might be /dev/sdd or /dev/sde then). You can clearly see the new device sdc in the example output, which refers to the drive as a whole, and the device sdc1 which is the partition, it has only one in this case, otherwise there would be entrys like sdc2 sdc3 and so on. These new entries are what we are looking for.
Write down:

/dev/sdc (for sdc, the drive) and
/dev/sdc1 (for sdc1, the partition).

(This is an example from my setup only, you’ll have to write down what you get from your own screen).

These are the folders in your system where the programs can find and address that very drive and its partition(s).
It is absolutely important to be sure about which device you want to address later, since any mistake in these names will probably result in complete erasing another drive unwantingly! Don’t plug off or on anything before having gone through the following procedure completely, hence this might change these names in your system with all conseqences.

Now start from the antiX main menue the program “gparted”:
Menu–>Programs–>Systemtools
(or just type in the root console window “gparted&”, the ampersand is not a typo! it lets you work on at the console while the program is still running.)

At the upper right corner of gparted program window choose the “Drive” you just have found.

+++ WATCH OUT: A fault in choosing the correct drive here will delete your data without return!

– remove all the partitions on that drive (and only on that one)
– start the execution, wait until it is done.

Maybe you get a warning, the partitions were just in use, since they probably have been mounted automatically while plugging on the stick. In this case you’ll have to unmount before proceeding: Key in your root terminal window from above:

	
# umount /dev/sdc1

You can check whether you have successfuly unmounted the device completely by typing

	
# mount |grep "sdc"

The answer of this command needs getting used to a little, since you are done when it doesn’t answer anything. If it comes up with something, you haven’t been successfull still.
Or just let all this be done by the drive-unmounter from the antiX taskbar. Now the deletion of the partition in gparted should complete without complaints.

Next in the gparted window create new Partitions, according to your old system on the hdd:
1.) 1x Primary, ext 4, Name: “/”, Size as required, but bigger (or at least same size) than that partition containig the root-filesystem on your hdd, in my case this was 7,5GiB, I’ve chosen 10GiB which is 10240MiB (gparted asks for MiB)
2.) 1x Extended (size: all the rest of the Drive)
3.) 1x Logical, within the Extended one. ext4 also, named “/home”. Size may take the complete remains of the drive, as you like. At least it must have the size of the /home partition of your old system on hdd.
(at this point you’ll have to add more logical partitions if your old system you want to transfer requires them, name them as they are named in the old system. You can
get the correct names by keying in “blkid” in the still opened root-terminal from above.)
(Swap partition will not be created on this SDD, one can create this later, but there will be probably be always a swap partition on your hdd you can use, so you don’t really need one on the thumbdrive.)
If you’d like to make the system on the thumbdrive running a little faster, just read this text concerning a correct allignment of your new partitions: (Partition Alignment detailed explanation)
But it will work anyway, even without a correct alignment. Moreover I’m nearly sure gparted in the antiX version I’ve been using would manage this in the correct way automatically for you.

– start the execution, wait until is done.

– Set the Flag “boot” on primary partition.

Close the program gparted, as we don’t need it anymore, but let the root-console window still open.

• This topic was modified 2 years, 5 months ago by Robin. Reason: fix some typos
• This topic was modified 2 years, 5 months ago by Robin. Reason: tiny amendment

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

[Member Robin]

Test

the additional “c” option makes a checksum comparison, so if nothing shows up to have been changed, everything is fine now.

Example output of the check, everything fine:

		# rsync --stats --progress --numeric-ids -axAhHSPc /mnt/Ubuntu-root/ /mnt/USBstick-root
		sending incremental file list

		Number of files: 283,193 (reg: 183,665, dir: 26,884, link: 72,525, dev: 82, special: 37)
		Number of created files: 0
		Number of deleted files: 0
		Number of regular files transferred: 0
		Total file size: 5.97G bytes
		Total transferred file size: 0 bytes
		Literal data: 0 bytes
		Matched data: 0 bytes
		File list size: 1.24M
		File list generation time: 0.220 seconds
		File list transfer time: 0.000 seconds
		Total bytes sent: 13.65M
		Total bytes received: 29.63K

		sent 13.65M bytes  received 29.63K bytes  7.98K bytes/sec
		total size is 5.97G  speedup is 436.01

At this point, everything is written on the USB-stick already.
Now we have still to do some homework for school:
first, we have to modify fstab on the freshly created stick according to the given facts when booting from the stick later. Since we will never guess, which /dev/sdXY the stick will get assigned at boot-time, we will switch to UUID-method to identify the partitions. In case of “/” there is the UUID of the hdd, which has to be replaced with the one of the root-partition of the stick, we have written down at the beginning. Also the entry of the home partition has to be corrected: We replace the /dev/sda5 entry with the UUID of our /home partition of the stick. Moreover we have to replace ext3 by ext4, since we have an ext4 filesystem now.

# cat /mnt/Speichertift-root/etc/fstab
		# /etc/fstab: static file system information.
		#
		# Use 'blkid -o value -s UUID' to print the universally unique identifier
		# for a device; this may be used with UUID= as a more robust way to name
		# devices that works even if disks are added and removed. See fstab(5).
		#
		# <file system>                            <mount point>   <type>  <options>             <dump>  <pass>
		proc                                        /proc           proc    nodev,noexec,nosuid   0       0
		#
		# / was on /dev/sda10 during installation
		#UUID=0eb91a9b-ea52-4f5b-9140-5a06f6f73d1d  /               ext4    errors=remount-ro     0       1
		# moved to new location
		UUID=76135213-70cb-4645-862b-4725026f4727   /               ext4    errors=remount-ro     0       1
		#
		#
		# swap was on /dev/sda11 during installation
		# UUID=dbb40875-198e-4fd7-b6e4-e59ee464426b none            swap    sw                    0       0
		# existing swap on /dev/sda9
		UUID=2d151628-e6f1-4e23-a8a6-7820d17b8a14   none            swap    sw                    0       0
		#
		#
		# existing home on /dev/sda5 94021be3-c160-4166-a151-92ad72b26f9a
		#/dev/sda5 /home ext3 nodev,nosuid 0 2
		# moved to new location, using ext4 now
		UUID=a4489010-a7a5-4249-b88e-4702a5672450   /home           ext4    rw,nodev,nosuid       0       2
#

In the fstab file all the lines beginning with a sharp sign (#) are comments and will be ignored by the system. In this case they contain earlier entrys and comments some of which were created during original installation of the OS by the installer-script. Here are alle the new UUIDs at its place already.
You can edit this file with a graphical text-editor (e.g. geany from antiX menu), but you’ll need root privileges to write it back to the stick after having done all amendments.
So you might key in into the still open root console window

			# geany&

btw, you don’t need to care about the tons of spaces between the entrys on a single line, they are for human readability only. It merely has to be at least 1 Space between them.

And here comes the feestyle skate, after having done all the duty:

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

[Member Robin]

Test

(for details about what you are doing: $ man tune2fs in another console window)
in short:
-O (great “O”ven, to confuse with “Zero” or small “o”) means set/unset Options
the “^” in front of the feature deactivates it
a “+” in front of it activates it.
(I have activated aditionally uninit_bg, since I found it activated on every ext4 filesystem created by my old OS, and it only speeds up the checkup of the filesystem)
The activated 64bit option should be no problem since it is implemented since kernel 2.6.28, even if it was not active in other ext4 filesystems created under the old OS.

It might be possible, that you get asked by tune2fs to execute

	# e2fsck 

in order to check the filesystem after switching features on or off. So just do it when requested.

Now we are ready to transfer the old system from the HDD to the stick.

Since we’ll need the UUID of our new partitions in the process we should write them down for later use:
the primary partition is /dev/sdc1, which will become our boot and root partition,
the first logical partititon in the extended is /dev/sda5 (a rule which is true in most cases for linux systems)
this will be our new /home partition.

	# dumpe2fs /dev/sdc5 |grep "Filesystem UUID:"
	dumpe2fs 1.43.4 (31-Jan-2017)
	Filesystem UUID:          a4489010-a7a5-4249-b88e-4702a5672450

	# dumpe2fs /dev/sdc1 |grep "Filesystem UUID:"
	dumpe2fs 1.43.4 (31-Jan-2017)
	Filesystem UUID:          76135213-70cb-4645-862b-4725026f4727

Then we have to mount the partitions we want to transfer as well as these where it has to be written on:
For preventing accidentally writing something to the original partitions on hdd, we mount them adding the option “-o ro”, for read-only.

	# mkdir /mnt/Ubuntu-root
	# mount /dev/sda10 -o ro /mnt/Ubuntu-root

	# mkdir /mnt/Ubuntu-home
	# mount /dev/sda5 -o ro /mnt/Ubuntu-home

	# mkdir /mnt/USBstick-root
	# mount /dev/sdc1 /mnt/USBstick-root

	# mkdir /mnt/USBstick-home
	# mount /dev/sdc5 /mnt/USBstick-home

(if one of the partition refuses to be mounted, execute “fuser”:
in case e.g. /dev/sda10 won’t mount key in

	# fuser -v -m /dev/sda10

which will show you the culprit in most cases. Close the program which uses the device, then unmount the partition and start again with mounting it as above described.

These preliminarys done, we will now actually start the transfer, using rsync.
This will create a copy of the complete file- and folderstructure of the hdd-partition on the partition USB-stick.
If you’d like to find out more about what the options mean and what they do, you’ll find them listed in ” $ man rsync” typed in a non-root console window.

	# rsync --stats --progress --numeric-ids -axAhHSP  /mnt/Ubuntu-root /mnt/USBstick-root
	# rsync --stats --progress --numeric-ids -axAhHSP  /mnt/Ubuntu-home /mnt/USBstick-home

If you provide aditional the option “–quiet” it will work slightly faster, but you will not get any information about the running process.
Keep cool, it lasts some time until everything is finally at its place…

After that I decided to check the result:

	# rsync --stats --progress --numeric-ids -axAhHSPc /mnt/Ubuntu-home/ /mnt/USBstick-home
	# rsync --stats --progress --numeric-ids -axAhHSPc /mnt/Ubuntu-root/ /mnt/USBstick-root

the aditional “c” option makes a checksum comparison, so if nothing shows up to have been changed, everything is fine now.

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