Artix: simply artix

Arch based Porteus community project
Post Reply
User avatar
francois
Contributor
Contributor
Posts: 5136
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus artix
Location: C'est l'hiver: la neige soudainement est là à Montréal.

Artix: simply artix

Post#1 by francois » 07 Dec 2017, 19:15

To work with artix is surely good practice as we are now nemesis artix based. Any other considerations about artix could be addressed in this thread. Your questions, comments and setup under artix are quite welcome.

Grub2 syntax to boot the artix.iso file.

Code: Select all

    menuentry "ARTIX  grub_iso" --class dvd {
    set root=(hd0,5)
    set isofile="/isos/artix-lxqt-20171015-x86_64.iso"
    set dri="free"
    search --no-floppy -f --set=root $isofile
    probe -u $root --set=abc
    set pqr="/dev/disk/by-uuid/$abc"
    loopback loop $isofile
    linux  (loop)/boot/vmlinuz-x86_64  img_dev=$pqr img_loop=$isofile driver=$dri  rw
    initrd  [s](loop)/boot/intel_ucode.img[/s] (loop)/boot/initramfs-x86_64.img
    }
It differs from the manjaro grub2 syntax as (loop)/boot/intel_ucode.img will prevent the iso image from booting.
Carpe diem.

User avatar
francois
Contributor
Contributor
Posts: 5136
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus artix
Location: C'est l'hiver: la neige soudainement est là à Montréal.

Artix: simply artix

Post#2 by francois » 07 Dec 2017, 19:33

This is easy with porteus because of the cheatcode change= .

But how could I save changes while booting the artix iso with grub2? I do not want to do a full install of artix on a partition.

Thanks.
Carpe diem.

User avatar
Ed_P
Contributor
Contributor
Posts: 3423
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Artix: simply artix

Post#3 by Ed_P » 07 Dec 2017, 21:27

If it doesn't have a changes= cheatcode, or something similar, or a cfg file, saving changes may not be an option with ISO booting. In fact ISO booting itself may not be possible. Does it support one of these ISO boot parms: from=all from=$iso, fromiso=$iso, findiso=$iso, iso-scan/filename=$iso?
Ed

User avatar
francois
Contributor
Contributor
Posts: 5136
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus artix
Location: C'est l'hiver: la neige soudainement est là à Montréal.

Artix: simply artix

Post#4 by francois » 10 Dec 2017, 00:49

Booting is possible with the grub2 syntax that I have proposed in the first post. It works.

Fanthom has implemented a lot of cheat codes for porteus. Brokenman might know something about it.Cheatcodes seems to be instructions given to the kernel at bootup. Maybe we should search on this side. Tome is a regular user of the boot iso mode, maybe he knowe. Donald ... :)

A few links related to persistence (cd or usb are the same):
Tomas M. live kit:
https://www.slax.org/blog/18623-Persistent-changes.html
I've successfully compiled posixovl statically with uClibc for all my target architectures (x86 32bit and 64bit), and implemented Persistent Changes to Live Kit (and thus to Slax). If you boot such system, you can create and modify all files and directories and your changes will be preserved even if you reboot.

https://bbs.archlinux.org/viewtopic.php?id=129418

https://help.ubuntu.com/community/LiveCD/Persistence

Ahhhh! and one from me in 2010 on adding changes to salix os live cd, quite alike porteus persistence:
https://forum.salixos.org/viewtopic.php?f=31&t=1114
Carpe diem.

User avatar
francois
Contributor
Contributor
Posts: 5136
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus artix
Location: C'est l'hiver: la neige soudainement est là à Montréal.

Artix: simply artix

Post#5 by francois » 10 Dec 2017, 02:46

COW
Copy-on-write

On artix there is a COW folder:
/run/artix/cowspace/persistent_/
Carpe diem.

User avatar
francois
Contributor
Contributor
Posts: 5136
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus artix
Location: C'est l'hiver: la neige soudainement est là à Montréal.

Artix: simply artix

Post#6 by francois » 10 Dec 2017, 04:03

File structure is completely different from porteus and naming convention too:

Changes seem to be located in:
/run/artix/overlay_root/upper/

Modules end with .sfs, they are located in
/run/artix/img_dev/artix/artix/x86_64/

So saving changes could be performed:
http://forum.porteus.org/viewtopic.php?f=114&t=2386

Code: Select all

mksquashfs /run/artix/overlay_root/upper/ /changes.sfs -comp xz -b 524288 -Xbcj x86
Then it should be moved somewhere like:
/mnt/sdax/artix
where:
fromhd=/mnt/sdax/artix
Carpe diem.

Post Reply