Search Results for 'boot from iso'

[Moderator BobC]

I agree, that’s a great pic, skidoo.

Ok, but more serious… I used antiX 19.3 full x64 and followed Xecure’s instructions to make it a testing system, down to just before the reboot, and instead remastered it on my “flashdrive” (32gb SSD hooked up USB 3.0). I’m not that comfortable that virtualbox will really work the same as a machine, myself, and so I’m using the flashdrive booted live with no persistence to test with. I then created a new ISO from it, which could be used to install from. I was thinking of posting it up on the net, but wondering (because I had different problems than some others testing the wallpaper app), how do I know if I really have it all correct?

I was thinking I could make a package list that could be compared? any thoughts?

[Anonymous]

sudo touch /usr/local/share/excludes/iso-snapshot-exclude.list

ouch.
OMG, no that wouldn’t lead to a happy ending…

There are things that need to be excluded from the snapshot if you want the final iso to boot on other systems.

… and, in the absence of a suitable exclusions list, the operation would never reach completion, period. Instead, endless recursion would result, attempting to read (and create squashed copies of) “virtual” files from the vfs directories, e.g. /sys/ and /proc/ …ultimately leading to “kernel panic” once the recursive process has fully exhaused all available (memory, swap) resources.

[Member Xecure]

naaan wrote:

Also iso-snapshot app complains about a missing file which I fix by – ‘sudo touch /usr/local/share/excludes/iso-snapshot-exclude.list’

Your issue is there. There are things that need to be excluded from the snapshot if you want the final iso to boot on other systems. If that file is missing, you need to recover it. reinstall iso-snapshot-antix
sudo apt update && sudo apt install --reinstall iso-snapshot-antix

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

[Member naaan]

It was indeed the compression scheme that caused the large size.
Have another issue. Remastered iso won’t boot. Kernel Panic
First I thought I was removing too many packages. But even without removing a single package. I get an kernel panic, in a VM as well.

Screenshot: https://i.imgur.com/PGWYXBL.png
Also iso-snapshot app complains about a missing file which I fix by – ‘sudo touch /usr/local/share/excludes/iso-snapshot-exclude.list’

• This reply was modified 2 years, 4 months ago by naaan.

Hello . I am trying to create a modified iso on antix.
I created a live-usb . Booted from it. Removed packages > use iso snapshot > but the created ISO was much bigger than the original! Starting with 750mb base iso I ended up with a 1gb modified ISO.
Any help please ? Could this be due to different compression technique ? Intially I had neglected to remove certain cache files. But removing those didn’t appear to affect the iso size.

Thanks!

[Anonymous]

Here’s an example in which “giving proper credit” (and recycling the name of a pre-existing utility) has led to a less-than-ideal outcome:

Confusion among users regarding “live-usb-maker” should be expected.
Although it has been in use in antiX since 2016 (or earlier),
the antiX FAQ and wiki still lack documentation for it…
and docs for the same-named, AppImage-packaged, version application provide contradictory information.

——————————————————————————-

https://www.antixforum.com/forums/topic/how-can-the-toram-functionality-be-used/#post-47301 (Dec 13, 2020)
“ you need to use the live-usb-maker program from a live USB session”

https://gitlab.com/antiX-Linux/live-usb-maker
“Create a live-usb from an iso-file, from another live-usb, from a live-cd/dvd or from a running [antiX] live system.”

https://antixlinux.com/the-most-extensive-live-usb-on-the-planet/
“We encourage you to use the live-usb-maker tool (available for both gui and command line) to make antiX and MX live-usbs. This will ensure you get a full featured live-usb. If you have already made a “dd” live-usb or were forced to boot with a live-cd or a live-dvd, don’t worry! The live-usb-maker tool offers “clone mode” which will copy your currently running antiX or MX live system to a new usb stick without a copy of the iso file.”

—————————————– vs ————————————–

live-usb-maker tool now available as an AppImage
https://mxlinux.org/blog/live-usb-maker-tool-now-available-as-an-appimage/
“For those non-MX or non-antiX linux users who might need to write iso images to USB sticks,
we now have the joint antiX/MX live-usb-maker tool available as an AppImage…”
https://github.com/MX-Linux/lum-qt-appimage/releases/tag/19.11.02 (currently, only a 64bit only AppImage is available)

video (duration: 5m30s) Make a MX/antiX live-usb from other linux distros with the live-usb-maker-qt appimage

[Member Xecure]

ArchiMark wrote:

In Applications / antiX category:
Backlight Brightness
Chroot Rescue Scan
CLI APT-based Package Manager
Command Line Control Centre
Live-USB Kernel Updater

In Accessories category:
Calcurse
Midnight Commander Editor
[…]

In Internet:
Ceni
Droopy

For terminal based applications, change the terminal app using the instructions I gave before:

Xecure wrote:

Use the Preferred Applications program in the Cntrol Centre to set the default terminal to the one you are using now.

and see if they load after the change.

If possible, when you again have free time, re-download the 19.3 ISO and try to boot live again with the new downloaded version. See if roxterm loads on the live system. I want to be sure that the problems you are experiencing are not due to corrupted a ISO.

ArchiMark wrote:

B. Booting Up – Console Info

When I boot up, I see the following various lines in Console:

nce: Unable to init device /dev/ncelog (rc: -5)
...
AC ’97 1 access is not valid [0xffff…] removing mixer.
Snd_ali5451
...
Setting sensor limits….No sensor found.
Try sensors-detect

Any concern over these messages?

No idea. It seems related to the sound driver, but I am no expert reading the kernel messages.

ArchiMark wrote:

C. Conky – Battery
In Conky, battery only shows 0%.

For conky to display the correct battery level, we will have to figure out if the battery is recognized. Run in terminal:
ls -lh /sys/class/power_supply
If you have the green bar in the icewm toolbar indicating battery level, maybe changing the variable in conky from BAT0 to BAT1 (if that is the correct identifier) may work.
For now share the output of the command above.

ArchiMark wrote:

D. Connman
When the window opens up for you to select the browser to open, Pale Moon, the browser that I recently installed is not in the list. Is there an easy way to have it added to the list?

I am not sure if this is connman, but if you mean the “Web Browser” menu entry, use the “Preferred Applications” program I mentioned to change the default web browser to palemoon. This should fix it so it would load properly when clicking the “Web browser” menu entry.

ArchiMark wrote:

However, I don’t have any audio volume control in the taskbar. Is this because I don’t have Alsamixer working right now or ?

My guess this is because you are running minimal-icewm. try only desktop-session icewm (Menu > Desktop > Other Desktops > icewm). It takes over 8 MBs or RAM, but will give you the volume icon to manage/control the volume level.
If you see it uses too much RAM, create a key shortcut to raise and lower the volume, so you can do it without needing the volume icon.

See the ~/.icewm/keys as I think a combination is already there (amixer sset Master 5%-/5%+). Change it to the key combination you prefer (if you are interested in following this path).

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

[Member Xecure]

That is not a live install. That is a normal install to a USB. Nothing to do with live or persistence.

To get the best out of the antiX live system, you need to use the live-usb-maker program from a live USB session (for example, with Easy2Boot you boot into antiX and then you use the live USB maker to clone the Easy2Boot live system to the other USB device).

If you have customized your USB install, use the ISO Snapshot (Control Centre > Maintenance > ISO Snapshot) to create a “copy” of your installed system to a live ISO. Make sure you select the option “Preserve accounts (for personal backup)”.
After creating the ISO, if you want to make that installed USB into a live USB, you need to move that iso to a separate usb and reboot using the E2B antiX live USB.

If you don’t want to preserve the changes on your installed USB, boot from your E2B antiX live system and launch Live USB Maker (Control Centre > Disks > Live USB Maker (gui).
Select the USB device where you want to “install” antiX live system and, either select to clone the current E2B live system or the ISO you created in the instructions above.

After finishing the process, if all goes well, reboot into your new live USB and go through the menus options “Customize Boot (text menus)”. Select language, timezone, etc, and most importantly, select the type of persistence you want (I recommend persist_root) and also the toram option when that pops up. Save all changes and then you will be running on a real Live persistence that loads everything to RAM.

Read more:
https://antixlinux.com/the-most-extensive-live-usb-on-the-planet/

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

[Member naaan]

@Xsecure I think I am in the wrong place with respect to the installation, because my boot menu screen is completely different to that picture. Mine looks like a standard grub menu . Like this, except its antix instead of ubuntu:

Here is how I installed. Loading iso into a bootable usb (easyboot). Booted from said USB into antix. Used ‘install’ shortcut to install antix onto another USB. During installation I selected the “install grub” and “enable persistance” options.
Then rebooted into the second USB, where I find the standard grub screen..
What can I do differently ?

[Member Xecure]

First make sure there is enough RAM.
If you are using standard dynamic persistence, the changes (persistence file) are being saved in RAM. If apart from that you are loading the whole OS in RAM, you may be find tha, as some point your system will be even slower because RAM is full and it is using swap.

If you are sure there is enough RAM, there are 2 different ways to add the toram option.

1. From the Live Boot screen.
A.If running in Legacy Bios, the screen will look like this:

The F4 menu will give you the toram option. Once selected, you can save the boot parameters with the F8 “Save” menu.
B. If running on UEFI systems, you need to write the boot parameter inside your Custom boot option. Move the selection to the Custom menu entry, hit the ‘e’ key and edit the line containing the boot parameters (third line). You need to add toram and menus=s
It could look similar to:
linux /antiX/vmlinuz quiet splash=v persist_root toram menus=s
When ready, hit F10 key and it will ask you if you want to save the boot changes. Select the “yes” option.

2. From inside the running antiX system.
Depending on if UEFI or Legacy Bios boot, you need to edit (with root privileges)
Legacy Bios: /live/boot-dev/boot/isolinux/isolinux.cfg and /live/boot-dev/boot/syslinux/syslinux.cfg (and add the boot parameters there)
UEFI: /live/boot-dev/boot/grub/grub.cfg (and add the boot parameters to the Custom entry)

More info in:
https://antixlinuxfan.miraheze.org/wiki/AntiX_Live_System
https://antixlinuxfan.miraheze.org/wiki/Boot_Parameters

• This reply was modified 2 years, 5 months ago by Xecure. Reason: correcting EUFI keys

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

[Member ModdIt]

I assume you checked the ISO download was ok.

Maybe experts will disagree :-).
As a very new user maybe you could be pragmatic, do a semi automated full install, that sets up your drive for you.
Then you can better understand what you need and make any changes from there, if you want to. I did that more than once.

I attached my main Partition scheme for reference as a screenshot Sorry twice failed to upload.
If semi auto fails or you do not wish to do so please take a screenshot of your partitioning, and post.
Maybe also useful, how you prepared the USB boot stick.

Often small problems trip us up. Somebody helps you get on your feet again :-).

• This reply was modified 2 years, 5 months ago by ModdIt.
• This reply was modified 2 years, 5 months ago by ModdIt.

[Anonymous]

I really want to learn how to remaster antiX [..] But first

blahblah wall of text

Just do it. Learn by doing.
No harm, and certain enlightenment, if you will just dive in and launch the isosnapshot program.

Let’s take care in communicating the terminology, the utility program names:

remaster, aka “live-remaster”, can only run within liveboot scenario. it (over)writes one’s liveboot device.

snapshot, aka “isosnapshot”, can be run both from a live session and from an installed-to-disk system.
Its work output is an ISO file, suitable for use on a liveboot device, containing a faithful copy of the operating system in its current state (reflecting any additions, customizations, deletions you have performed to date). It provides choice of modes ~~ “general” (intended for redistribution) or “personal” (the copied system will include any existing user login accounts and home directories, replete with web browser profiles-n-history and/or other files which may contain sensitive personal information).

After examining the sequential isosnapshot user interface screens, you are free to exit the program without actually generating an ISO file. If you generate an ISO file, you may (while experimenting) choose to immediately delete it and start afresh ~~ choosing a differenct set of options during your next isosnapshot trial-run.

A third utility, named “live-usb-maker” provides additional functionality, some of which overlaps the aforementioned tools. After generating a custom ISO via isosnapshot, you can employ live-usb-maker to generate liveboot media from the ISO. Someone pursuing distribution of a “respin” might skip this step and, instead, upload the ISO to a public http//ftp server (or share via a p2p application) and publicize its availability.

[Moderator Brian Masinick]

Xecure wrote:

@all
Maybe you missed it, but there is an official announcement by anticapitalista here:
Future antiX
where the things that need to be addressed and where help is needed is organized and explained.

All of us who want can try helping in any of the points raised there.

SamK wrote:

marcelocripe wrote:

I thought the ISO of the antiX full version was aimed at novice users. So what kind of user is it for?

antiX-Full is not aimed specifically at novice users, it is aimed at all users. The idea of it being for novice users is a very recent and incorrect presumption made by some people.

Historically, antiX did not offer the range of ISOs it currently does. There were some requests to have an ISO that did not include all the programs shipped in antiX-Full. Some users wanted to reduce the amount of bandwidth and time required to download the ISO, some did not want the full range of programs, some wanted to choose for themselves what was installed. To meet these requests the range of ISOs evolved to their current number.

antiX-Full always remained available. It contains the full range of programs without being modified to suit any particular group of users. It has never been abridged for novice users. antiX-Full is the standard version of our distro for all users.

marcelocripe wrote:

Doing a “re-spin”, I still don’t really know what it is or how to do it. For me this is still far from my reality, I will need to learn a lot to be able to reach this level. Would the “re-spin” make another version of antiX from the original version? Do the developers authorize the anti-re-spin of antiX?

You are encouraged to create it, use it and distribute it if you want to. There is even a section of the antiX forum (sub-section of Development) where you can post about it or request help etc. The term re-spin is a slang word. In antiX is properly named Remaster. The antiX-FAQ has a section about it (in English). The first line is most informative.
“The primary purpose of live remastering is to make it as safe, easy, and convenient as possible for users to make their own customized version of antiX.”

These two messages really bring home the importance of the ideas, and also the importance of understanding the capabilities of antiX in its current form.

The first thing to realize is that even though we have been discussing ideas for improvement in future releases, we also have to remember that the decisions made for this distribution entirely belong to those who formed, and are responsible, for this distribution. One of the main aims is to provide support for old hardware. Some of the changes made at levels in the Linux ecosystem actually make this difficult because support for some components has been dropped at the Linux kernel, while support for many more hardware components has been added. The antiX team does as much as possible to preserve and extend the life expectancy of older systems, but is constrained by some OS features that are supported by other teams not managed by antiX.

Another goal is to remain as light and nimble as possible; this is also affected by resources outside of the direct control of antiX, though the team still does a remarkable job.

Finally, while some people aim for the simplest, easiest possible interface, let me highlight what SamK said and what’s possible. AntiX does have a rich toolset, and the use of remastering, that is, adding, removing, changing, and configuring the software and the appearance, then saving the result into a different bootable ISO image, is something that antiX provides as a standard capability. Therefore, while the stock, standard antiX images are NOT going to appeal to every possible feature or capability, suppose, just for the sake of discussion, that the system you envision closely resembles something that Mint, Ubuntu, or even Apple or Microsoft has created, if you really desire that kind of look or feature capability, with antiX you still have some choices. Of course, one choice is to actually use one or more of those other systems; we have the freedom of choice after all. There are other ways too. With the different window managers, desktop environments, software applications, and utility tools available, only your own creativity and willingness to experiment prevents you from creating your own very personal and custom version of antiX.

I recommend for those looking for a different experience to experiment – try the various antiX tools; see if you can create something DIFFERENT that actually works, and then remaster the image. Make sure you have ways of getting back to what you had before – keep an image of antiX handy, back up your work, and ideally have a spare system or something you can use, recreate, or recover from in case of making mistakes. The first time you experiment, you may indeed make mistakes. This is how we learn. Still, I highly recommend that those of you looking for something different try to actually MAKE it YOURSELF – with the antiX tools.

Those of you that are successful in doing so will feel a great sense of accomplishment, and you will also see the power, flexibility and advantages of the antiX approach. You can keep the work to yourself if you wish, or you can post pictures or even system images of the work that you’ve done, but believe me, you’ll have fun doing it if you can take the time and effort to build exactly what you want, and antiX is one of the best distributions available for doing this kind of work.

Let me know what you think about this, and if you are not sure what I mean, please ask. We’ve mentioned the tools to use in various posts and threads in this forum and we can point out a few, plus the docs if they are not obvious; I do hope that this is very helpful and stimulates some excitement and some great ideas that you can make your very own this year!

--
Brian Masinick

[Member olsztyn]

anticapitalista wrote:

Can you try again after a reboot.

Remastered and rebooted (running without persistence).
ISO-Snapshot still results in the same error with new squashfs-tools…

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

[Member olsztyn]

Installed the new squashfs-tools ver. 4.3-12.0antix1 (64bit) and re-executed ISO-Snapshot to SMB share as output destination. Unfortunately it is resulting in the same error. From execution log it seems it is abending on creating 4.0 filesystem on iso-template/antiX/linuxfs.
Again, it is not an important issue and workaround is to output to Live-USB-Storage and then move to SMB share. So it might not be worth to spend precious time to fix it…
Just to clarify:
I executed ISO-Snapshot right after squashfs-tools update, I did not reboot. So if squashfs-tools gets pre-loaded in memory on boot and is not refreshed then the old version might have been executed. I do not suppose this would be the case though…

• This reply was modified 2 years, 5 months ago by olsztyn.

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