Search Results for 'boot from iso'

[Member calciumsodium]

anticapitalista wrote:

https://www.fsfla.org/ikiwiki/selibre/linux-libre/freesh.en.html

In a previous post, I provided the instructions for installing the trisquel variation of the 64-bit linux libre kernel into 64-bit antiX21 operating system. In this post, I am providing instructions to install the standard 64-bit linux libre gnu kernel provided by fsfla.org. These instructions are based on my own attempts to install the linux libre gnu kernel.

Start with an antiX21 system, base or full.

1. Add the sources.list file in the /etc/apt folder:
sudo apt edit-sources

Add the line:
deb mirror://linux-libre.fsfla.org/pub/linux-libre/freesh/mirrors.txt freesh main

2. Re-enable FTP access:
echo ‘Dir::Bin::Methods::ftp “ftp”;’ | sudo tee -a /etc/apt/apt.conf.d/99local-ftp

3. Add the key:
wget -O – https://jxself.org/gpg.asc | sudo apt-key add –

4. Update:
sudo apt update

5. Install linux libre kernel:
sudo apt install linux-libre-5.15

I chose the current long-term support kernel 5.15.

6. reboot

In the iso that I created, it has both the linux-libre-5.15 for its efficiency and the antiX 5.10.104 for its flexibility.

I had the altheros wifi adapter, so I was ready to start wifi immediately after reboot.

$ inxi -b
System:
  Host: jakersfan Kernel: 5.15.40-gnu arch: x86_64 bits: 64 Desktop: IceWM
    v: 2.6.0 Distro: antiX-concept-21-b1.1_x64-full Kaze no denwa 20 July 2021
Machine:
  Type: Desktop Mobo: N/A model: N/A serial: <superuser required>
    BIOS: American Megatrends v: 080015 date: 05/06/2010
CPU:
  Info: dual core Intel Pentium D [MCP] speed (MHz): avg: 2403
    min/max: 2403/3403
Graphics:
  Device-1: Intel 4 Series Integrated Graphics driver: i915 v: kernel
  Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: intel gpu: i915
    resolution: 1280x1024~60Hz
  OpenGL: renderer: Mesa DRI Intel G41 (ELK) v: 2.1 Mesa 20.3.4
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169
  Device-2: Qualcomm Atheros AR5416 Wireless Network Adapter [AR5008
  802.11bgn]
    driver: ath9k
Drives:
  Local Storage: total: 74.51 GiB used: 3.45 GiB (4.6%)
Info:
  Processes: 124 Uptime: 21m Memory: 3.81 GiB used: 991.2 MiB (25.4%)
  Shell: Bash inxi: 3.3.19

[Forum Admin Dave]

Ok. So you are live booting the remastered iso every time. Not running an installation or a persistence file.

The min- option (or other session options: rox-, space-, jwm-, etc) should be selectable from the boot menu “f” buttons, or the grub boot options. Once booted you can select a different session by pressing f1 at the login screen. If past the login screen you can select another session by menu -> desktop -> other desktop -> *-wm. (This can also be done by editing ~/.desktop-session/default-desktop and rebooting.)

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member Pelucia Siffred]

I choose my harddrive as destination of the remastered ISO, not a readonly media. I am using Easy2Boot to boot the antiX’s .iso file that I copy to my usb stick. I use the antiX’s live snapshot tool to generate de new ISO file and choose my harddrive to receive the remastered ISO. The remastered ISO works perfectly as expected (all programs I install go in remastered ISO), however the autostart do not work. The only thing did not work is autostart. The remaster is made successulfy.

[Moderator Brian Masinick]

andyprough wrote:

Happy 4th of July Brian, I hope you get to see some fireworks or do something nice with your family today. It will be hot here in Texas, about 100 degrees.

Regarding ‘what are you here with today‘, it’s the same thing every day – antiX. All other distros simply fall short and end up disappointing me. I tried to give Void a good try, but it’s missing so much important software for my work flow, and it has zero tools for USB sticks and for creating ISO snapshots. I liked the fact that it was minimal and fast and used runit, but antiX has those features and so much more.

… and a happy day of Independence and fun for you and your family too!
My son, who turns 22 in October, moved from Hendersonville, NC, about 35-40 minutes from us in Greenville, SC back to the state of New Hampshire where he was born.
He found a place of employment about an hour from where he grew up, but he keeps coming back to all of the places around our previous home, and also along the seacoast; I think the only reason he didn’t move there was that it’s now way too expensive to live there. He went and watched the fireworks in New Hampshire’s largest city, Manchester, though he had been considering going to Boston, right on the Esplanade, to watch the Boston version of the 4th; I did that only once when he was just shy of his sixth birthday; then we got there in early to mid-afternoon and secured a spot directly across the Charles River from the Esplanade and the fireworks; so we had front-row seats. I don’t do that very often; I saw the Detroit/Windsor Freedom Festival Fireworks once, and the Boston Pops once; other than that, small, local events.

As far as today, if we watch any fireworks, it’ll be on TV; we did our stuff out and about on Saturday and Sunday, so we’re “laying low” today.

Regarding “what an I here with”, yes, I’ve been an antiX fan and supporter since the beginning, but long before the arrival of antiX, I was using Slackware (1995). In 2001 I was given a Dell Dimension 4100 desktop and a freelance contract to write an article about Linux distributions, so I compared Mandrake, Red Hat, SUSE and Debian Sid in the “sidux” variation. In those days, I felt that Mandrake was a distribution well suited to first time users, (though to be honest, there really were very few really good “beginner” distributions until a few years later).

What led me to antiX and several other distributions was an interest in “Live CDs”, later Live DVDs, which have since moved to very small form factor removable USB devices, which I use when I’m not running my already installed software. I have concluded a long time ago that antiX is the “ideal balance” for me when it comes to lean systems. A few others may be “leaner”, but they lack functionality. A few others are more “functional” but they lack the overall balance and efficiency of antiX.

When it does come to “performance”, I’ve been finding that two distributions fit that niche well for me: siduction and EndeavourOS. The siduction distribution is the current day successor to the sidux distribution I referred to earlier. EndeavourOS is appealing, not only for it’s efficiency; for me, it’s the only Arch-based distribution that has remained both efficient and stable long enough for me to keep it; maybe that has changed; but I’m not hunting for distributions any more.

My other category of interest is general purpose distributions. I find MX Linux to be a reliable distribution on the light mid range of general distributions, and it has a common lineage with antiX and a similar attention to reliability and excellent builds; I can run Alpha and Beta builds with antiX and MX Linux; with very rare exceptions, they work and are usable. PCLinuxOS is another distribution in this category. Back when I found it, MEPIS and PCLinuxOS were in their early days; both worked as Live CDs, I have enjoyed them, so both are on my keeper list.

So that’s why I have antiX, MX Linux, siduction, EndeavourOS, and PCLinuxOS in my list of distributions that I actually install; all of them are able to boot and run in “Live” mode. I do have antiX on every system; I run it from USB on the Acer, I use HDD, SDD, or USB on all others.

--
Brian Masinick

[Member olsztyn]

andyprough wrote:

I disagree with @olsztyn on the recommended new features. The beauty of these tools lies in their simplicity. I think it would be good to have tools that can handle encrypted drives and network shares and so forth like @olsztyn requests, but not as expansions of the current utilities. Maybe as separate new tools.

I appreciate such insight and I am all for simplicity. That is what antiX stands for – simplicity and utmost dexterity that goes with adopted strategy.
With all my respect I would shed some additional light on these points:
– Handling encrypted usb drives by Live-USB-Maker is not an extension. Live-USB-Maker has been capable of handling encrypted drives for years. You can use an encrypted USB drive as source for Live-USB-Maker now and e.g. make an unencrypted USB drive and vice versa. So handling encrypted USB drives is already included in Live-USB-Maker and works for the above tasks. So what I was proposing was to resolve an issue that was discussed some two years ago that BitJam had started. I would have to dig out that conversation from those times but it boils down to technical details how it is implemented, an issue arises when kernel is changed on an encrypted Live instance of antiX, subsequently Live-USB-Maker creates an non-bootable stick. Also cloning an encrypted Live antiX to an encrypted clone directly does not work for the same reason.
Therefore what I was proposing is not any extension of Live-USB but simply streamlining and perfecting of existing Live-USB-Maker. This was the project BitJam had started about two years ago that I was referring to.
On the other hand it is not affecting any large population of users, so it was apparently far from being a priority. Also there are workarounds in the meantime. E.g. if I want to clone an encrypted Live antiX to create another encrypted antiX copy, I run Live-USB-Maker twice – first to unencrypted, then from such unencrypted to encrypted.

– Streamlining of Live boot menus I was suggesting is also not any extension or a ‘new feature’. These functions already exist, such as dynamic discovery of Frugal instance and building a menu of them for the user to select. But they are buried in the boot menu hierarchy. So my suggestion was to make them more clearly exposed.

– Handling network shares for target of ISO-Snapshot is a rather naturally arising requirement, since snapshots are often large in size and the size of local /Home is often limited. Besides, ISO-Snapshot does not seem to balk at existing network share selected as target. It just fails in further process, which is just an inconsistency in behavior.

– So the only ‘additional feature’ from what I was proposing was the capability of Live-USB-Maker to make an ISO in addition to working directly on hardware media as target. IMHO this would be a nice enhancement.

None of these is critical, so I do not expect development team to focus on these. However I just want to keep them in sight as ideas. And some such could contribute to antiX 22 being more than just making antiX *elogind*-free from the outset. It is *elogind*-free now, which I appreciate, so some additional value as part of antiX 22 would be great to have.
The above are just ideas for streamlining existing antiX, not additional features, for consideration…

• This reply was modified 10 months, 2 weeks ago by olsztyn.

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

[Member calciumsodium]

Hi, I wanted to make a suggestion for future antiX versions. Perhaps this is similar to what @olsztyn was suggesting. Is it possible to create an iso snapshot that memorizes the network settings for your local network such that the iso can boot up automatically to the local network on different computers? For example, I created an iso snapshot on the Slitaz os that memorized the network settings for my local network. When I boot up the Slitaz iso on different computers, the network is automatically connected. Thanks.

[Member olsztyn]

Xaver wrote:

@ olsztyn
I am very happy, that we have iso-snapshot. The snapsshots are bootable and installable.
Does any other distro offer that? To my very delight iso-snapshot even works with runit.

Again, needless to say for me that I consider ISO-Snapshot, Live-USB-Maker and Remaster the great assets of antiX that have no comparison out there. As I previously mentioned, I experimented a bit in the past with leveraging ISO-Snapshot going beyond antiX, to make it a more general tool, so it could be used for other distros as well. My experiments were working but the process was not quite straightforward.
As I mentioned over a year ago, Q4OS announced plans that working with MX team, ISO-Snapshot would be implemented for Q4OS as well. However, I have not seen that it actually materialized yet. It must be still worked on…

Back to the antiX 22 context though:
Aside from antiX 22 being completely *elogind*-free right from start, I would like to see also some additional enhancements in these areas:

Further enhancements to ISO-Snapshot:
– Great as it is, it appears to not work with network shares. Although it initially accepts network share as target for saving the snapshot, after start it comes back with a message on insufficient space on Home. In Live, it works though with Live-USB-Storage.
– In antiX Live scenario (at least) it misses to faithfully copy the content of fstab. Any manual, hard added entries are not carried over into the snapshot. I am not sure if the same issue is with the traditionally installed antiX as well. When I mentioned some issues with ISO-Snapshot in this forum almost two years ago, anticapitalista mentioned that ISO-Snapshot was meant to be for traditionally installed antiX only, not for antiX Live installations. Do we need to make such distinction anymore?…
antiX installed on the internal SATA HD is the best thing that exemplifies existing flexibility of antiX and the best of two worlds… Thanks to Xecure and Christophe for highlighting this feature in those times…

Further enhancements to antiX Live boot architecture:
Much has been done in terms of these enhancements in antiX 21. Thank you… However, looking at antiX 22 around the corner, can we please pursue further evolution of these enhancements, such as:
– Clearer and more standing out discovery and ad-hoc built menu for any Frugal antiX installations
– To confirm: Do we still need a separate UEFI boot partition? It appears to me that the current version of syslinux do support UEFI booting. I was able to construct an antiX Live instance with all in just one EXT4 partition, no separate UEFI partition, and the resulting antiX booted both legacy and UEFI laptops just fine….

Live-USB-Maker possible enhancement:
Just want to stress that Live-USB-Maker is so good already… Just these, if it is not too much to ask though:
– Cloning of encrypted Live antiX instance. This was mentioned about two years ago and BitJam had started a project at that time…
– Adding an option to create an ISO image of Live antiX, in addition to USB, as target destination of Live-USB-Maker operation. I know, that this would mean the same process as the ISO-Snapshot, so at first it appears to be duplicating ISO-Snapshot process. However, I believe this would not be the same. Looking at boot process and boot log messages appear to differ between using Live USB clone using Live-USB-Maker and Live USB created from image of ISO-Snapshot. This might be what anticapitalista mentioned in the past that ISO-Snapshot was not intended to use on Live antiX. It appears to me that the snapshot seems to remember the specific hardware configuration of the host, while Live-USB-Maker makes target completely dynamic, regardless where it would be booted…
Please correct me if I am mistaken…

In any case, thank you for continued evolution of antiX to the new heights…

• This reply was modified 10 months, 2 weeks ago by olsztyn.
• This reply was modified 10 months, 2 weeks ago by olsztyn.

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

[Member sybok]

Hi, you forgot to mention three key points so that someone may assess what/where the issue is:
1) antiX version (+ was integrity of the ISO used to create live USB – check-sum verified)?
2) Descrption of the HW: e.g. via output of ‘inxi -Fxz’ [run in terminal]
3) Is any of RAID, secure-boot or UEFI turned on? If so, which one(s)?

Installing on modern HW can get tricky, see e.g. https://www.antixforum.com/forums/topic/install-at-dell-latitude-7410-n62p4/

[Member Xaver]

Connman seems to be ok, no complains except, that resolv.conf is not created.

Installed on VirtualBox-HD lxdm works as it should.
From the iso-snapshot shutdown and reboot logout to the console. I then have to halt as root.

[Member olsztyn]

Xaver wrote:

I am very happy, that we have iso-snapshot. The snapsshots are bootable and installable.
Does any other distro offer that? To my very delight iso-snapshot even works with runit.

Yes, indeed. ISO Snapshot plus Live-usb-maker are some of the greatest assets of antiX. My pointing to some bugs does not mean I do not fully recognize the overall value. It was just for further enhancement to consider.
By the way, ISO Snapshot can also be installed on distros other than antiX or MX, to create snapshots of other distros. It creates squashfs snapshot files the same way and Live snapshots of such distros are bootable, although with ‘MX 19’ splash screen… Therefore its value goes beyond just antiX.

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

[Member Xaver]

@ olsztyn
I am very happy, that we have iso-snapshot. The snapsshots are bootable and installable.
Does any other distro offer that? To my very delight iso-snapshot even works with runit.

@ iznit
No, I do not desire to remove anything and fortunately I must not decide that. I am quite ignorant concerning policykit. From my limited experience with xfce4-power-manager I just wonder, if policykit without elogind makes sense.
The system I have built does work without policykit and yes, that narrows your choice of software. In some cases the dependencies are not neccassary (i.e. BackInTime) and should better be recomendations instead. In such cases a dummy package, which catches the dependencies, would help.

[Member Xaver]

@ anticapitalista

These are good news. Thank you for all your works and efforts. To remove elogind/libelogind0 (and probably polkitd/policykit-1 as well) seems to be a wise decision. I have recently enabled xfce4-power-manager on my notebook by following this instruction from the debian wiki:
https://wiki.debian.org/Xfce-power-manager-troubleshooting
It is ridiculous: All these many (e)logind security doors must be opened to get a functional system!

Do you also plan to switch to runit completely?

I have build in VirtualBox a small resuesystem on base of the antiX-21-net-runit-sid_x64-net.iso.
When the installer asked, if I would want seatd, I spontaneously decided to go with it.
At every step of the installation I have checked not to get elogind, polkitd or policikit-1.

The system is fast and stable so far. I like its simplicity.

There are three problems only:
1) Iso-files created with iso-snapshot have no access to the internet (resolv.conf is missing).
2) Booted from USB the snapshot freezes on wakup from suspend. (maybe because of problem 3)
3) runit-services-core/base/full-antix cannot be installed.

Details on these problems I have posted in the sid section of the antiX forum.

As rescue system and base for Clonezilla this system is fine and stable already. Internet is ok, if resolv.conf is created and edited manually.

Based on antiX-21-net-runit-sid_x64-net.iso I have built a small rescue system in VirtualBox.
Windowmanager is Openbox with tint2, spacefm, udevil, lxdm – no elogind, polkitd, policykit-1 or gvfs.
To my suprise using this simple system does not feel limited. Only the choice of software is a little limited. because of (often unnecessary) dependencies from policykit-1.

In VirtualBox the system is stable, fast, responsive and does not show any problems, except odd behavior at wakeup from suspend. Snapshots can be made with iso-snapshot and are bootable. So far I have encoutered 3 problems only:

(1) The iso-snapshots have access to the network, but not to the internet. The cause is simple: resolv.conf is missing. Instead there is a link to non existing /run/resolvconf/resolv.conf
If I create /etc/resolv.conf manually, internet is working fine.
Does this problem happen because iso-snapshot is configured to work with sysvinit?

(2) sudo pm-suspend does work, but the system freezes on wakeup. Maybe runit services for X environment are needed, but unfortunately they cannot be installed (–>3).

(3) Further runit services cannot be installed.

(3a) runit-services-core-antix is in conflict with dbus:

root@antix1:~# apt install runit-services-core-antix
[...]
Unpacking runit-services-core-antix (0.1.9) ...
dpkg: error processing archive /var/cache/apt/archives/runit-services-core-antix_0.1.9_all.deb (--unpack):
 trying to overwrite '/usr/share/runit/sv/dbus/check', which is also in package dbus 1.14.0-1.0nosystemd1
Errors were encountered while processing:
 /var/cache/apt/archives/runit-services-core-antix_0.1.9_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Turning dbus down does not help.
Removing dbus does not lool like a good idea either

root@antix1:~# apt remove dbus
[...]
The following packages were automatically installed and are no longer required:
  dbus-system-bus-common libopenconnect5 libpcsclite1 libpskc0 libstoken1 libtomcrypt1 libtommath1 libtss2-esys-3.0.2-0
  libtss2-mu0 libtss2-sys1 libtss2-tcti-cmd0 libtss2-tcti-device0 libtss2-tcti-mssim0 libtss2-tcti-swtpm0 libtss2-tctildr0
  libxmlsec1 libxmlsec1-openssl python3-dbus tpm-udev
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  connman connman-gtk dbus smart-notifier upower
0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.

Maybe the runit-services must be installed before dbus and other stuff.
If that is the case I suggest to include all runit services in any antiX-runit-iso. These packages are so small anyhow. Not needed services can be turned down instead.

Is there a way to resolve this conflict?
I am even unsure, if I need any further runit services. Except suspend the system is ok as it is.

(3b) runit-services-full-antix is going to remove cups. That is not as bad as dbus but still annoying.

root@antix1:~# apt install -s runit-services-full-antix
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  cups-core-drivers cups-daemon cups-filters cups-filters-core-drivers cups-ipp-utils cups-server-common libfontembed1
  libpoppler-cpp0v5 libqpdf28 ssl-cert
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  runit-services-base-antix runit-services-core-antix
The following packages will be REMOVED:
  cups printer-driver-cups-pdf
The following NEW packages will be installed:
  runit-services-base-antix runit-services-core-antix runit-services-full-antix
0 upgraded, 3 newly installed, 2 to remove and 0 not upgraded.

• This topic was modified 10 months, 2 weeks ago by Xaver.

I don’t have a computer that can run applications like rufus, and I tried to extract an iso into my USB, It didn’t work. I also tried to make it bootable using fdisk, but it didn’t work either. With the computer I can still use some Linux commands, not all (I can’t run apt-get etc. but I can run wget, fdisk and more). I’m sorry if this is a really stupid question

• This topic was modified 10 months, 3 weeks ago by xyompltrine.

Recently, I booted a VirtualBox VM with a 2GB virtual disk from an antiX iso, ran the installer and found it requires about 4GB. That made me think about a frugal install and other ways of running antiX in a VM.

1. Frugal install of antiX in VM
After a lot of trial and error, I came up with these steps. Please suggest improvements.
Create a vm with 2GB virtual hard disk. In System/Extended features, EFI should not be enabled. Boot from an antiX iso.
In a terminal on the VM:

su
gparted 
	# create a dos partition table on sda, format to ext4, set boot flag
mkdir /mnt/sda1 ; mount /dev/sda1 /mnt/sda1
mkdir /mnt/sda1/boot
extlinux -i /mnt/sda1/boot
cat /usr/lib/SYSLINUX/mbr.bin > /dev/sda
rsync -a /live/boot-dev/boot/syslinux /mnt/sda1/boot
rsync -a /live/boot-dev/antiX /mnt/sda1
geany /mnt/sda1/boot/syslinux/syslinux.cfg
	# change UI line to simple text menu: UI menu.c32 
	# Add "from=hd" to the APPEND line of the first entry
	# delete the other entries
	# save
reboot

Persistence
I don’t know how to preserve existing rootfs and homefs in this process, so for a customized VM, I remastered and copied the remastered linuxfs and linuxfs.md5 into /mnt/sda1/antiX instead of the ones from the iso. Persistence in the VM can be set up via the Control Centre; also add “persist_all” to APPEND line in syslinux.cfg.

2. Clone a live flash drive in a VM
This is not as frugal but it retains nice antiX boot menus and persistence.
Make a VM with a large enough virtual disk and boot from iso. Mount the flash drive in the VM.
Use gparted to
–make msdos partition table on sda
–unmount the flash drive ext4 partition, copy it and paste it to sda
–set the boot flag on sda1
cat mbr.bin to sda as above. Reboot without iso; in boot menu choose F5: persist option if desired, F8: save and add “from=hd” to the Boot options. Reboot the VM to a clone of the live flash drive, with persistence.

3. Boot VM from a live flash drive
https://www.howtogeek.com/187721/how-to-boot-from-a-usb-drive-in-virtualbox
Create a sort of link to the live flash drive (sdb):
$> VBoxManage internalcommands createrawvmdk -filename flash_drive.vmdk -rawdisk /dev/sdb
Create a VM, use Settings to attach flash_drive.vmdk as sata storage, start the VM, add “from=all” to boot options and F8: save

I hope some of this will be useful. Nothing worked the first time, but that’s just me :/
This was done using antiX-21_x64 on artix host machine.

• This topic was modified 10 months, 3 weeks ago by Vincent17.
• This topic was modified 10 months, 3 weeks ago by Vincent17.