Search Results for 'boot from iso'

[Forum Admin rokytnji]

Guys. I think we are dealing with award bios since Windows XP was mentioned.

MBR drive instead of GPT drive pick on drive partitioning probably applies here. No real need for 512MB boot partition for EFI type of gear that comes later.

Makes for the easiest solo install. I am staying mostly out of this thread because of the desire to keep XP and with boot repair being mentioned.

Only mistake I can figure is the grub screen on installer is too confusing maybe for some users. Like installing grub to / of a partition instead of on the mbr of the drive.

I have not had to use grub repair except for once on a my screwup on my MX box during a grub update. With no windows on my MX box. It was no brainer to fix. On the update. I installed grub to root partition. instead of the MBR on the drive. I used the antiX full iso usb though to fix it during a live session.

So I’ll leave here with my standard search for antiX problems

Edit: Probably be a big help booting another live session and post terminal output of

sudo parted -l

I like that command more than fdisk -l .

• This reply was modified 3 months, 2 weeks ago by rokytnji.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Forum Admin anticapitalista]

antiX is built using the build-iso tools pointed out by marcello. This enables consistency of builds and it took us years (yes plural) to develop. MX and AVLinux are now using it, modified of course. All antiX isos are built from scratch using this tool; there is no remaster of anything from Debian. Any budding devs should really use this tool rather than remaster/snapshot.

At the same time as ‘perfecting’ build-iso, we developed our unique live system (including persistence, remaster, snapshot), initially influenced by MEPIS and KNOPPIX live scripts. Our live system also took years to develop and it is completely different from Debian live. MX and AVLinux also use our live system. https://antixlinux.com/the-most-extensive-live-usb-on-the-planet/

Dave also developed the desktop series of scripts, which basically provides a sort of ‘desktop environment’ for antiX-base and full. Early versions of antiX used the common .xinitrc ‘way’ to load window managers, which is fine, but limited IMO. ‘daves-desktop’ is unique to antiX.

Of course we do not use systemd nor elogind. This means we have to provide nosystemd packages. A cursory look into the nosystemd repos will show how much work is needed, particularly on Debian sid where we are playing catch up. We also provide our version of runit scripts that are different to how Debian runs runit.

So, yes, a lot of work from lots of people have gone into making antiX what it is.

Build-iso basically does these things within a chroot.

1. debootstrap basic apps from Debian
2. Immediately after this, we remove all systemd packages out of debootstrap
3. Packages are installed from Debian and antiX repos
4. eudev replaces udev
5. squashfs file created (we call this linuxfs)
6. live system added to create bootable live iso.

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

antiX with runit - leaner and meaner.

[Forum Admin anticapitalista]

Might it be because you are using a 4.9 kernel?

I just tested live iso of antiX-22-full (64bit) booted in Virtualbox for both kernels and ping as user works out of the box.
However, you are correct about antiX-22-base (64bit)

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

antiX with runit - leaner and meaner.

[Member Kempelen]

Hi @Robin

I did “tx migrate” yesterday, before I posted my reply. Without that nothing worked. (E.g. you can see, I can download the whole project.) So the rest hostname is there already (I double checked now). So the error 404 lies somewhere else. Please note that the error says:

No Project resource found with the identifier o:antix-linux-community-contributions:p:antix-contribs

Is that a correct reference to “project resources”? I cannot spot any more typos in it, but there might be some error with that o:…p:… thing. And I did completely delete the folders that your script created, to make a fresh start (that was yesterday too). I’m sorry if this is still my “user error”. 🙂

Regarding comparison: since I didn’t try yet, I cannot really tell. I have two ideas in advance:

I will commit yesterday’s backup to a local git repository. Then with any future update I can do a git diff – or use a visual git diff program. If strings do not shuffle up and down in high numbers, this should be easy to overview. What I will want to spot is total failures in translations, from contributors who clearly have no clue about what the text means. Those should be easy to spot. And then I fix them on Transifex. Download again, if looks better, commit to git. And leave it for another time period.

The line-break change you mentioned: I could easily skip those in the DIFF VIEW, if they don’t happen in large quantities.

My plan B is to use Lokalize’s PO file comparison functions. I have not tried this yet, but I heard some other Hungarian translators use this to find new translations to overview others’ changes. It can compare two PO files visually, and I hope that does all the file parsing correctly.

I just need to skim over all changes, and if updated texts look “reasonable”.

Most errors in antiX original HU translation were so bad, that they are easy to spot. E.g. “Firefox localization for Hungarian” was something like “Firefox positioning for Hungarian” (location, rather than localization). Or “Midnight Commander” was translated to “Éjfél Parancsnok”. I can easily spot if the translator knew what he is doing or not, and that is my aim. Not perfect in-context checking of everything. The current (original antiX 22) translation is so bad, it’s painful to open in Hungarian. (Fortunately it was 5% translated only. 🙂 )

I maintain some other translations too, in software that allows seeing “list of changes”. On those I usually just read the change list quickly. (Mouse over displays the English text in CrowdIn if I want to verify better.) Usually the errors are “typical”, e.g. translating a term that I pre-defined to something else – I spot those easily. Or using Friendly language instead of Formal. If the translation looks as a perfect Hungarian sentence, I usually skip to next. Or if I suspect, that the sentence had such complexity as it could be misunderstood by the translator, then I double check with “mouse over”. (Some sentences are very tricky – that’s where machine translation bleeds out too, but some Hungarians fail more often than Deepl.com! :-))) (Especially if they don’t know the specifics of the software. E.g. Live USB things in antiX. I did try all the Remaster and other things on Pendrive before even starting translation. I have to pendrive with antiX. And I have the full install, both x86_64 on my PC, and 32bits on old laptop. And I’m testing the installer too (Live->Install) in VirtualBox that is. I do that in Ubuntu because I cannot boot the antiX Live in antiX VirtualBox. 🙂 I took screenshots of all that, so I can look back any of the original English strings without installing or booting. Maybe I should upload those screenshots somewhere, so other translators can see too. But I have OCR-ed their text, and I want to make a program so that text can be searched somehow… (Even if only with CTRL-F in the browser.) (OCR does not work well on boot process, but it works OK in normal GUI programs.))

Thanks for your help!

[Forum Admin anticapitalista]

@marcelocripe I understand your concern which is why I installed antiX-22-full 64bit to a disk to see if I can reproduce this but I can’t.

I booted live iso set to pt_BR via F2.
Live session shows pt_BR menus
Installed to hard drive
Rebooted to installed desktop
All menus in pt_BR
sudo apt update && sudo apt dist-upgrade
Answered Yes to all prompts
All menus in pt_BR

Have you made any changes to default menu set up?
I know you were testing the various menu formats that Robin (I think) designed to show Generic rather than Name in the menus.
Perhaps that is the cause of this issue, though I would be very surprised if it is.

Can you check that your menu files in for example ~/.icewm are not symlinked to /etc/skel/.icewm/menu

(outage posting this)

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

antiX with runit - leaner and meaner.

[Member Jovi Fly]

caprea wrote:

Oh, I forgot you are booting in bios mode , not uefi.
But in bios mode the kernels are easy to find, directly on the first screen you see, there’s
Use legacy kernel
Use modern kernel
Memory Test

The “from usb” option in Bios mode is on the second screen in the F4 options.

Maybe could be that i´m using the x32 bits ISO, but i can´t see those options. The only ones that appear are:

antiX-22 386-full (18 october 2022)
Safe Video Mode
Virtual Box Video
Failsafe Boot
Boot from Hard Disk
Memory Test
Switch to Grub Bootloader

Then are the Boot options box and the shortcuts F1,F2,… (Y.Y)

[Member Jovi Fly]

No way! Seriously??? All the hours that i spent… *Loads the gun* All that times focused in the laptop instead of playing with my friends… *Aims to the temple* For nothing… *Press the trigger*

I´m a bit tired, so i´ll puspose this really appreciated advices for tomorrow.

Thanks guys!

EDIT: Couldn´t hold on and decided to at least try with the other kernel, the thing is… that i dont find it. I´m using the full AntiX 22 ISO, and checked Bootscreen > Switch to Grub Bootloader > >>>Advanced Options<<< Even after search through the forum, i still dont get it.

Where is supposed to be, or what i´m doing wrong?

• This reply was modified 4 months ago by Jovi Fly.

[Member calciumsodium]

Hi Brian.

You have a new nickname since I last checked in. The version is SliTaz 5.0 RC4. It was just released last month. Please see picture.

In order to get the internet to autoload upon boot, I had to modify the /etc/network.conf file.
In it, I had to change the default interface, which is default to ethernet, to wifi:
INTERFACE=”wlan0″

and I had to enable the wifi at boot:
WIFI=”yes”

The nice thing about SliTaz is that once I set this network.conf file correctly, I can load this iso file on any computer in my home network and the wifi would autoconnect, even if I have never launched SliTaz on that computer. With antiX, I would have to set the password on every new computer. Not with SliTaz.

Now, not all wifi dongles work. antiX has more extensive firmware support. The wifi dongle that worked for me without adding extra firmware is:

Device-3: Ralink RT2870/RT3070 Wireless Adapter type: USB driver: rt2800usb

The iso that I downloaded from the SliTaz site was only about 55 Mb. I added some apps and now my iso is only 64 Mb.

Good luck.

Attachments:

1. 

   screenshot-1.png
   

[Member iznit]

iso-snapshot-cli

The details I posted earalier were from looking at “iso-snapshot” program. The “iso-snapshot-cli” pause message is slightly different. The message shown when edit_boot_menu=yes is simply “The program will pause the build and open the boot menu in your text editor.”

I have not previously looked into “iso-snapshot-cli”….. and one aspect of it seems wierd (((inappropriate))). It is a cli app, but by default it wants to call “leafpad” as a default text editor. Deleting or commenting the iso-snapshot.conf line “gui_editor=/usr/bin/leafpad” will cause it to instead look for “nano” as the editor. Not important for techore or other CORE users except leafpad may not be found and/or no X session may be available for other “gui_editor” assignment.

[Member techore]

I ran into a problem using iso-snapshot via cli (-c) and “edit_boot_menu=yes.”

It launches the default editor and prints at the top of the screen “Processing command…” where the three dots blink. Attempting to exit nano using ctrl-x or :q using vi/vim/nvim do not work and ctrl+c/z results with iso-snapshot aborting. Not exactly a surprise that last bit.

I don’t use xorg (startx) as part of my spin creation process, but seeing a reference to leafpad in the iso-snapshot.conf, I installed leafpad, startx, and iso-snapshot without “-c” and it worked using leafpad. Substituting leafpad with a cli text editor in iso-snapshot.conf resulted with “Processing command…” It does state GUI text editor in the conf file so not exactly surprising.

The option “-c” and having to launch xorg and install a GUI editor feels like a contradiction and my preference is to do all this from the cli wihthout xorg. I know, I am stubborn. 🙂

I can change my process and launch xorg but is this an oversight?

Correction: see struck-out text.

• This reply was modified 4 months ago by techore.

[Member techore]

dolphin_oracle’s statement was useful in guiding me to look elsewhere. Thank you, @dolphin_oracle.

@iznit, wow! and thank you. I see the relationship and excellent explanation. Need to retain it for future reference.

@christophe, on using iso-snapshot-cli 0.4.06, I get an unrecognized format error from grub on boot. I did it three times and the error was consistent. I appreciate the suggestion and may revisit iso-snapshot-cli using an unaltered antix-core install to verify my changes didn’t break something.

iznit wrote:

The pause mentioned in my previous post, it occurs after the automated placement of files. You then have opportunity to edit or add or delete any files within <workdir> before the snapshot iso is finalized.

@iznit, it appears to be the best course of action. I was unaware of this option and appreciate you sharing your knowledge. I’ll give it a go tomorrow after some sleep.

[Member iznit]

techore, I will dare to expand dolphin_oracle’s statement to clarify
“snapshot does not DIRECTLY write anything to <workdir>/etc/skel”

we can say:
1) isosnapshot does depend on package “remaster-antix”.
2) remaster-antix package does contain copies of the default ((( /etc/skel/*/menu ))) menu files.
3) remaster-antix package does also contain an executable script named “installed-to-live”.
4) Within the installed-to-live script, the variable $LIVE_FILE_LIST enumerates a list of files.
      you can view the script to see the /etc/skel/*/menu and other files listed there

5) isosnapshot calls the installed-to-live script which, in turn, does place copies of the default menu files within the workdir.

isosnapshot source file: work.cpp

// Setup the environment before taking the snapshot
void Work::setupEnv()
{
    writeSnapshotInfo();

    // setup environment if creating a respin (reset root/demo, remove personal accounts)
    if (settings->reset_accounts) {
        RUN("installed-to-live -b /.bind-root start " + bind_boot + "empty=/home general version-file read-only");
    } else {
        RUN("installed-to-live -b /.bind-root start bind=/home" + bind_boot_too + " live-files version-file adjtime read-only");
    }
}

The pause mentioned in my previous post, it occurs after the automated placement of files. You then have opportunity to edit or add or delete any files within <workdir> before the snapshot iso is finalized.

• This reply was modified 4 months, 1 week ago by iznit. Reason: fix too many typos

[Member iznit]

techore, before launching the snapshot program, edit iso-snapshot.conf
edit_boot_menu=no
edit_boot_menu=yes

Even though you may not want to edit specifically the boot menu, this setting should cause the snapshot program to pause during its operation

“The program will now pause to allow you to edit any files in the work directory. Select Yes to edit the boot menu or select No to bypass this step and continue creating the snapshot.”

then you select “Yes” and while the program is paused, you can go into work directory and edit or remove <workdir>/etc/skel/.icewm/menu or any other files you wish to customize different from the system being snapshotted.

[Moderator Brian Masinick]

Please note that the PPC link containing the antiX wiki: https://antixlinuxfan.miraheze.org/wiki/How_to_install/en#Verification_of_signature also states this:
“Verification of the integrity of the ISO file

Verifying, any one of the md5sum or sha256sum will be enough. ”

So even though the gpg stuff isn’t working to your satisfaction, you did say “I managed to download the iso, sha256, md5 and sig files. from Sourceforge. The checksums matched.”

Since the comments above say that verifying any one… will be enough, I think you are OK.
To be honest with you, these days I rarely even do any of the checksums; most of them are usually fine; IF an image doesn’t work, THEN I go back and figure out why, and typically either download it again or if it’s not one of my “usual distros” and it’s having problems, after a couple of tries, I move on.

I’m not saying that my blatant sidestep of ignoring checksums is wise; I have often checked them over the years, I just think that if TWO of the checksums, for instance, the sha256 and/or the md5, I’m going out on a limb and guessing that you’ll be OK; In any case, it won’t be a horrible thing to create a USB image here, and get into what’s going on with the signature file after you’ve had some fun experimenting with the USB image.

As an aside, I downloaded a ISO image of another distribution today that was over 2GB in size. I had no intention to install it; I was merely checking it out. The download was fast, on a generally reliable network, so I copied the bootable image onto a USB using our Live USB Maker; no checksums done, booted it and ran it live for a while; worked fine.
Now if this image had any problems I would have most certainly checked it out; if I was doing something important with it, I would have also checked it out. If I was installing Enterprise software for a company, I’d follow every best practice. Nevertheless, a single sha256 verification would be sufficient to verify if the image matched the correct size. It’d only be if I had any reason to be suspicious of the image that I would perform every possible verification, but in that case, I’d be investigating the site of the download BEFORE doing anything else. There have been a few hacks of download sites over the years so it’s reasonable to desire some assurance that the images are what they claim to be; nevertheless two checks does seem to be more than adequate. In years past when most downloads went over analog lines, there were more reasons for concern. Today the main concern is that the images are what they are claimed to be and not a scam; if you’re satisfied with the source of the image, then it’s OK.

Let us know how things progress, and also let us know if you have created a USB image and attempted to boot from it yet. Best wishes!

--
Brian Masinick

I am using antiX 22 runit core. Attached inxi output.

Goal: I do not want the antiX base/full menu files created on generating an ISO for distribution.

After using iso-snapshot and boot or installing from the ISO, the /etc/skel directory contains .fluxbox/menu, .icewm/menu, and .jwm/menu. These were not present prior to using iso-snapshot nor was desktop-menu-antix installed.

Are these in fact created by iso-snapshot?
If true, can it be disabled using an “-x?”
Guidance on preventing or removing them would be appreciated.

iso-snapshot syntax I used to create the ISO.

iso-snapshot -c -r -s -z lz4 -x Desktop -x Documents -x Downloads -x Music -x Networks -x Pictures -x Steam -x Videos -x VirtualBox -f "$isoname"

Resulting /etc/skel.

ls -a /etc/skel/
./  ../  .config/  .fluxbox/  .gtkrc-2.0  .icewm/  .icons/  .jwm/  .xinitrc  .Xresources

dpkg-query results.

sudo dpkg-query -S /etc/skel/.fluxbox/menu
dpkg-query: no path found matching pattern /etc/skel/.fluxbox/menu

Edit: updated title

• This topic was modified 4 months, 1 week ago by techore.
• This topic was modified 4 months, 1 week ago by techore.
• This topic was modified 3 months, 4 weeks ago by Brian Masinick.

Attachments:

1. inxi.txt