Search Results for 'boot from iso'

[Member Robin]

Test
some part of a guidance for beginners I just wrote and tried to submit causes a 403 repeatedly:

A potentially unsafe operation has been detected in your request to this site
Your access to this service has been limited. (HTTP response code 403)

I am posting from antiX 17.4.1 using firefox 78.4.1esr-1~deb9u1. Don’t see where an “unsafe operation” should come from.
Already disconnected and reconnected from internet in order to get a new IP just in case somebody to whom the first IP was assigned to just before me has done some mischief. Didn’t help.

So I’ll now cut the text in parts, post them here separately first to figure out which part causes the blocking.
—-starts form here—

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 couldn’t 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 succesively 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 ben 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, preformated 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 realy down. Everything from 2.0 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 prefere 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 new stick):

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

[Member burrezo]

Hi all, after get nvidia legacy 304xx working in Debian Buster ( http://forums.debian.net/viewtopic.php?f=5&t=144257&p=730543#p730543 ), I’ve tested the method in Antix 19.3

PC: Asus P5N73-AM (chipset NForce 610i, integrated nvidia 7050) + Xeon x5450 [775 mod] + 4Gb Ram + SSD

https://www.asus.com/us/Motherboards/P5N73AM/

[1] Fresh install antiX-19.3_x64-full.iso Once finished, reboot, enter in desktop mode, open a terminal and update/upgrade as root:

sudo apt-get update && sudo apt-get upgrade

[2] Blacklist nouveau modules: as root, create the file /etc/modprobe.d/disable-nouveau.conf , with this content:

blacklist nouveau
blacklist vga16fb
blacklist rivafb
blacklist nvidiafb
blacklist rivatv
blacklist amd76_edac
options nouveau modeset=0

[3] Edit grub config (/etc/default/grub) for better tty resolution:

Check the supported resolutions, and choose the higher:

sudo hwinfo –framebuffer

Install hwinfo if necessary:

sudo apt install hwinfo

Edit this line like this (delete ‘vga=0x0317’):

GRUB_CMDLINE_LINUX_DEFAULT=”quiet”

Un-comment/edit the line (note 1400×1050 is the higher resolution supperted by my monitor, check yours):

GRUB_GFXMODE=1400X1050

And then add a new line with:

GRUB_GFXPAYLOAD_LINUX=keep

Update grub:

sudo update-grub

And reboot

[4] When grub boot-menu shows up, press letter ‘e’, move to the end of the line /boot/vmlinuz-4.9.235-antix.1-amd64-smp root=UUID=………………….. ro quite, and add a ‘3’ at the end, like this:

linux /boot/vmlinuz-4.9.235-antix.1-amd64-smp root=UUID=………………….. ro quite 3

And press ‘F10’ to continue, the system starts in terminal mode, log in normally whit your user/password.

[5] Remove Xorg 1.20 (nvidia legacy driver 304xx only works up to Xorg 1.19):

sudo apt remove xserver-xorg-core

[6] Install git, we will need it later:

sudo apt install git

[7] Move all the .list files in /etc/apt/sources.list.d/ to other location, for example, /home/YourUser/repos, and create inside that directory, the file debian-stretch.list, whith this content:

deb http://deb.debian.org/debian stretch main contrib non-free

Update repositories:

sudo apt-get update

[8] Install Xorg 1.19 and some packages needed:

sudo apt install xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-mouse xserver-xorg-input-evdev xserver-xorg-input-kbd

[9] Download de Nvidia official proprietary driver for your old nvidia GPU, in my case is a 7050, but I suppose this method will work with A LOT of old chipsets/cards ( https://www.nvidia.es/Download/driverResults.aspx/123847/ <- ‘SUPPORTED PRODUCTS‘ tab )

Make the file executable:

chmod +x NVIDIA-Linux-x86_64-304.137.run

Extract, NOT execute, the file (note the ‘-x’ at the end):

./NVIDIA-Linux-x86_64-304.137.run -x

Directory ‘NVIDIA-Linux-x86_64-304.137‘ is created.

[10] Get some patches from Jorge Maidana ( https://github.com/jorgem-seq )

git clone https://github.com/jorgem-seq/NVIDIA-Linux-304.137-patches.git

Navigate into the ‘NVIDIA-Linux-x86_64-304.137‘ directory, and apply the patch 0001 (*) (adjust your path when patching, depending on where the files were downloaded, extracted, cloned, etc…):

patch -p1 <../NVIDIA-Linux-x86_64-304.137-patches/patches/0001-disable-mtrr-4.3.patch

[11] Run the nvidia installer:

sudo ./nvidia-installer

Check for nvidia modules:

lsmod | grep nvidia

[12] Restore antix default repositories, delete /etc/apt/sources.d.list/debian-stretch.list and move back to this directory all the .list files previously moved to /home/YourUser/repos/ , and update repositories:

sudo apt-get update

Mark xserver-xorg-core as NOT upgradeable:

sudo apt-mark hold xserver-xorg-core

For listing packages status:

dpkg –get-selections

Reboot

https://i.ibb.co/DwnkkPP/antix-nvida304-1.png

https://i.ibb.co/8dLL7dK/antix-nvida304-2.png

Enjoy your nvidinosaur!!

(*)
In case you upgrade/install a new kernel, depending on the kernel version, you will need to apply more patches, IN ORDER, so if you install the kernel 4.19.152, you need to apply patches 0001, 0002, 0003, 0004 and 0005 (adjust your path when patching, depending on where the files were downloaded, extracted, cloned, etc…)

patch -p1 <../NVIDIA-Linux-x86_64-304.137-patches/patches/0001-disable-mtrr-4.3.patch
patch -p1 <../NVIDIA-Linux-x86_64-304.137-patches/patches/0002-pud-offset-4.12.patch
patch -p1 <../NVIDIA-Linux-x86_64-304.137-patches/patches/0003-nvidia-drm-pci-init-4.14.patch
patch -p1 <../NVIDIA-Linux-x86_64-304.137-patches/patches/0004-timer-4.15.patch
patch -p1 <../NVIDIA-Linux-x86_64-304.137-patches/patches/0005-usercopy-4.16.patch

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

[Forum Admin rokytnji]

Pretty much a Base Iso CD. A external amp to power some speakers. A fancy jack to hook up computer head phone jack .
Stored music. If land line access is available. Internet radio is now accessible.

All crappy hardware can be used like this. My other old crap are PDF manual holders. Being in the desert. I burn up dumpster computers till they won’t boot up anymore.
Aint worth replacing the hardware anymore. Inverter for Panasonic CF – 48 screen problems was 15 bucks. Ext CRT was a bit too big to lug around with a laptop.

Even music on console player with a terminal on Slitaz will boot and run on must ancient hardware. Just don’t pick the latest release since your box will be a specialty box. Same goes for older versions of AntiX. One does not need tons of functions and the latest software for a jukebox or repair manuals.

If you are stuck with Pentium 2 and 128 MB of ram as your main box. Well? Sux to be you. DSL, WOMP, SLITAZ, AntiX. Plus. You better learn something new.

It is referred to as command line utilities.

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

[Member GeoffC]

Thanks both of you for taking the time to field my query. I had actually encountered all three of these documents myself before writing my question but none of them mentioned an “F” option. The /live/README file is a great help. The uppercase options it lists for enabling services is why I mentioned that in my initial query.

The reason I am asking about “disable=lxF” is because I built a live usb from the (Oct 15th) antiX-19.3_386-full.iso and OOTB it has boot options “quiet splasht disable=lxF”. I had a few problems due to my lack of understanding of the implications of the “lx” options, so I thought it would be a good idea to find out what the “F” option does too.

Has it just been included by mistake then?

I built a live usb from the (Oct 15th) antiX-19.3_386-full.iso (sha256 verified), upgraded all packages, then remastered it. Now when I enable UFW then reboot, UFW boots up in a disabled state.

I didn’t notice this happening before. Has something changed or did I just miss this behaviour?

[Member ThakurMsh]

@skidoo, …disk partitioning…
@xecure,

th@anx:~
$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 111,8G  0 disk 
├─sda1   8:1    0   256M  0 part /boot/efi
├─sda2   8:2    0 109,5G  0 part /
└─sda3   8:3    0     2G  0 part [SWAP]
sr0     11:0    1   5,7M  0 rom  /media/sr0

th@anx:~
$ blkid
/dev/sda1: UUID="1BA2-9BD6" TYPE="vfat" PARTLABEL="ESP" PARTUUID="8d82a762-b9cb-4a6e-9b58-13b880c663f9"
/dev/sda2: LABEL="rootantiX19" UUID="5f5cee75-af3f-4235-bf1f-43912d6f0ef3" TYPE="ext4" PARTLABEL="primary" PARTUUID="a3453ec6-21a9-4eb0-a2bf-624cdcceb4de"
/dev/sda3: LABEL="swapantiX" UUID="ef1cb892-6cf9-4c0f-8a7a-f22bfefbc70b" TYPE="swap" PARTLABEL="primary" PARTUUID="443a0dbc-1343-47c2-977c-7b08425632ca"
/dev/sr0: UUID="2018-11-29-11-25-39-00" LABEL="4G USB M-PM-<M-PM->M-PM-4M-PM-5M-PM-<" TYPE="iso9660" PTTYPE="mac"

then the question arises:
I have a disk of 120G, but if you add it up, it will be 112G
what is it? Disk /dev/ram*`

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

[Member rayluo]

Thanks @skidoo for trying to help! 🙂 I modified my original post to remove the mentioning of Chrome. It was confusing and misleading. What I meant to say was indeed “a live boot, pristine 19.3-386-base ISO, WITHOUT adding extra software, ended up becoming a larger ISO than what we can download from official website”.

Your command line samples are definitely intriguing. I might try it the other day. This post was largely a brainstorming attempt, perhaps more for AntiCapitalista. 😉 Personally I use antiX-full ISO which has long been passed that 711MB mark. 🙂

[Member catfood]

Broad assumption here, but the antiX live is a bit bloated, it has ALL the firmware it can hold on an older kernel to allow it all. A remaster after the installer finds its target architecture, is likely to shave half the initial live requirements and ” MTUNE=Intel or AMD”. It’s designed to be leaner when possible. I believe Dolphin has a few videos too going further in depth about antiX live saving hardware profiles, so when you go from desk to lap, etc, it knows one needs wifi or not, etc. Hardware tuned kernel will run faster than a boot on everything kernel…

Also, when you remaster, it gives you a few various compression formats. Yes some are half the size, but as the notes even say, some formats will reload and boot way faster. I’d guess the antiX live iso is tuned towards medium or speed, vs. size. A lower remaster could just be choosing a smaller zip choice.

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

Howdy Jessie.

[Anonymous]

> I tried all 4 options in the ISO snapshot tool

further permutations are possible.
For example, with gz or xz, you can specify “level=” [0-9]
If level= is not explicitly specified, IIRC the default level applied is “6”

another benchmarking article: gzip-vs-bzip2-vs-xz-performance-comparison/ ./a> .

> antiX-19.3_386-base.iso size is 752 MB. I did NOT add anything
> (except upgrading the iso-snapshot-antix and iso-template-antix),
> and created a snapshot using xz, but the outcome (775 MB) is bigger than the original. Why so?

it is probably primarily due to
> I added chrome into it, and

no one using chrome(ium) has contributed a pattern (“home/*/.cache/chromestuffhere”)
or list of patterns for excluding chrome-related cache//junk files
iso-snapshot-exclude.list
After tracking down the relevant paths, you might consider posting a list in the forum and/or in a gitlab.com/antiX-Linux/iso-snapshot pull request.

To recreate the scenario, you can:
liveboot the pristine iso, setup dynamic root persistence, perform chrome install (and repeat whatever other actions) perform the snapshot operation, then persist-save, shutdown, reboot…

In the subsequent session, mount the rootfs and inspect its content(s), ala

sudo mkdir -p /mnt/shadowrootfs
mount -t ext4 /live/boot-dev/antiX/rootfs /mnt/shadowrootfs -o loop,user,ro,noexec
find /mnt/shadowrootfs * >> /tmp/MyRootfsManifest.txt

[Member catfood]

Using:
antiX-19.3-sid_x64-core.iso
sha256 verified, but my gpg -recv keys sites all seem to be acting up lately for full gpg verify

lsblk partially posted above
loop0 /live/linux
sda
-sda1 9G ext4
-sda2 7G ext4
-sda3 2G swap
sr0 /live/boot

The first attempt was in the cli-installer, so no reboot there.
Then made partitions with parted, and set fs types with fdisk(which have stayed since reboots).
lsblk showed my partitions fine every time, but always stuck mid installer, so guessing Dave’s answer is right.

These settings above are all being tried in virtual box, but I was getting same issue on a netbook trying to keed old debian sid home, but install antix sid over debian 10 sid there. Those partitions have been set in stone for a few years there, but same fail. It’s not urgent for VB testing, but when I put it on hardware, a separate home has saved me a lot of extra backups when I break things.

I don’t know enough to splice the git tar into the sid iso, and without a home directory created yet, no idea how to extract into primordial install void and use 😀
I will try again later after I see my antix live usb get a cli-installer in it’s apt updgrades.
Thank you everyone.

Howdy Jessie.

[Member Xecure]

marcelocripe wrote:

Mandefu, I don’t know how to read in English, the Brazilian Portuguese translation was confusing. Does your laptop have 3 GB of RAM or is it 3 GB of hard disk space? What is the hard disk space? What is the amount of RAM?

It probably is 512 MBs of RAM and 4 GBs of disk space, based on https://www.notebookcheck.net/Asus-Eee-PC-701-4G.6745.0.html
Probably a frugal install will save even more space, but with such a limited CPU, it is better to use the minimum amount of HD. Starting from net install, there is no need for most firmware. Once we know what xorg driver the machine needs, we can remove all the other ones and reduce the amount of space they take up.

marcelocripe wrote:

Xecure, from this topic initiated by Mandefu will come an important tutorial and material for the Wiki of “how to prepare an antiX operating system from ISO antiX-19.3_386-net.iso”.

It is a good idea to have an article explaining the basics for installing a graphical environment in core, as it is much easier that what it seems. Though first we need to get the eeepc to boot to a graphical environment, and not experience what you experienced, marcelocripe, with your VIA graphics, that couldn’t boot to a graphic environment or was extremely slow.

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

[Member rayluo]

Well then, I’m not in a hurry, so I can wait. Meanhile, it seems that “4 hour 55min” countdown is not intermitten. And in fact, the “apt update” emits another 3~4 errors/countdowns for some other repositories. That would mean hours-long downtime for the entire community, wouldn’t it? Brian you can also try run “apt update” (even if you won’t be intend to install anything), and see if you meet the same error.

By the way, it turns out, the current “apt update” error is only on antiX 64 bit. My another machine running antiX 19.2 32bit can run “apt update” without error.

(UPDATED from my prior post, with latest test result.)

That “4 hour 55 min” countdown is not intermittent. So, that is a many-hours downtime for the entire community.

1. 5 hours later, I successfully ran “apt upgrade” which includes the latest iso-snapshot-antix and its template.
2. I also edit /etc/iso-snapshot.conf, and change edit_boot_menu=no to yes, then during the snapshot procedure, a popup appears for user to edit the boot menu of the snapshot. I can see the last menu entry is already “switch to grub bootloader”, so I did not need to add or change anything, and I just altered the overall menu title from “Welcome to antiX” to my personalized greeting message.

Upon next reboot, I noticed that:

* The “switch to grub bootloader” menu item does show up, finally. Yay! My guess is only step 1 i.e. upgrading the distro (which includes iso-snapshot-antix and its template) would be sufficient for this fix. Not sure whether step 2 i.e. edit_boot_menu=yes is also relevant, but I don’t bother spend another hour to build yet another snapshot to test. So, this “Boot Recovery” topic is considered to have a happy ending from my side, too. 🙂 (The actual Boot Recovery functionality seems not as helpful as I thought, though, but that is a different topic anyway.)

* The overall boot menu title is simply “antix”, not “Welcome to antiX”, nor my personalized title. So, step 2 above seems ineffective, too. But that is not a big deal. Just a FYI here.

All in all, thanks Anticapitalista, Skidoo, Xecure, Brian and the community for all your guidance! I’m now on board to 19.3. 🙂

[Anonymous]

If you edit /etc/iso-snapshot.conf, and change edit_boot_menu=no to yes, then during the snapshot procedure, a popup appears for user to add the title of the snapshot (plus some other things). Is this broken, skidoo?

It is working perfectly.
I had forgotten the requirement to edit the .conf file

[Member Xecure]

I am not sure what you are asking.
Do you want a frugal install to be inside your /home folder?

Frugal install is simply install antiX inside a folder instead of a partition, and boot to it as if it was an antiX live session, as you are already aware by your post.

You can create it automatically from a live CD/USB at boot or manually from inside an installed or live system, taking the content of the /live/boot-dev/antix/ folder live system or from inside an .iso file to the folder you want to install it.
You would then add the grub.entry (or create it manually following any of christophe’s guides) as a custom grub entry and be able to boot to it from your grub at boot.

A few manual instructions in the forum, or dolphin_oracle videos (like https://www.youtube.com/watch?v=6ZGTBUW3bnA)

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

[Forum Admin anticapitalista]

About the snapshot issue, I don’t know how to solve (probably anticapitalista’s suggestion), but on the live USB issue, you can simply edit /live/boot-dev/boot/ and replace/edit some of the files there.
I would replace the grub folder with the one on antiX 19.2 iso and add the “switch to Grub bootloader” entry to syslinux/isolinux, copying it from the syslinux/isolinux config (or simply replace the whole boot folder. Justin case, make a backup).

The latest iso-template-antix includes the bootloader stuff.

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

antiX with runit - leaner and meaner.