Search Results for 'boot from iso'

Our first alpha build of the upcoming antiX-19 release, based on Debian Buster.

Get the iso from here

Changes from antiX-17:

* connman replaces wicd and is default. ceni still included.
This means a faster boot with only a slight increase in RAM.
The connman gui is included in the startup file, but not enabled (to keep RAM usage down).

* More up to date look via a ‘new’ icon them (numix-bevel plus additions).

* Still using the 4.9 kernel. 4.19 and 5.0 kernel versions easily installable.

* live grub rescue options (thanks to fehlix)

* Time-saver installer (thanks to AK-47)

* chroot-rescue added (thanks to BitJam)
“These programs are meant to supplement the fehlix live rescue system. The main thing is these allow you to get into a system even if its initrd.img is broken. It also let’s you get into multiple systems without rebooting”.

* Various rox-filer right-click additions

* screenlight included (thanks to SamK)

* virtualbox-guest apps 6.0.6-dfsg-1

* synaptic without zenity dependency

* gksu and gexec included/updated (thanks to skidoo)

* persistence sizes increased and the persist menu F5 now includes p_static_root and f_static_root (thanks BitJam)

* Others

Please test and give feedback.

Post bugs here: Bugzilla

Known Issues:

* conky flashes when running IceWM (annoying)
* antiX-gui-cli.sh: line 71 error (harmless) when setting up persistence/remastering
* Once installed, resolv.conf warning (harmless)

Enjoy!

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

antiX with runit - leaner and meaner.

[Member zeh]

Hi Jim,

Did you do “ls -l /usr/bin/sudo”?
Mine shows: “-rwsr-xr-x 1 root root 157192 Jan 12 12:10 /usr/bin/sudo”

Following the previous posts I’ve searched a bit more and I’ve found that one, yes.

“ls -l /usr/bin/sudo” showed the version with incorrect permissions
I then did “chmod u+s /bin/sudo” (as per the instructions)
and “ls -l /usr/bin/sudo” again – it now showed the correct permissions (it looks like yours)

After this su is working fine (sudo was corrected before and also works fine) – no more “authentication failure”.

However, I still get a blank sreen at boot.
At the blank screen, Ctrl+Alt-F1 gives me the CLI with the boot info.

Visible part of the boot info:

[....] Starting session management daemon: elogind [   22.991661] cgroup:Cgroup2: unknown option "nsdelegate"
[   23.106731] elogind-daemon [1983]: New seat seat0. 
.
[OK] Starting mouse interface server: gpm.
[OK] Starting SMO IRQ Balancer: irqbalance.
[OK] Loading cpufreq kernel modules... done (acpi-cpureq).
[OK] CPUFreq Utilities: Setting ondemand CPUFreq governor... CPU0... CPU1... done.
[OK] Starting SANE Network scanner server: saned.
Starting X display manager: slim.
[OK] Starting OpenBSD Secure Shell server: sshd.
Applying Power save settings... done.
Setting battery charge thresholds... done.
[warn] VirtualBox Additions disabled, not in Virtual Machine... (warning).
[OK] Starting Network connection manager: wicd.

Debian GNU/Linux buster/sid Sat2aX2 tty1

Sat2aX2 login: axTest
Password:
Last login: Sun Apr 20 21:28:22 BST 2019 on tty1
No mail.
[84.482465] elogind-daemon[1983]: New session 2 of user axTest.
axTest@Sat2aX2:~

When I try “startx” I get:

startx
xauth: timeout in locking authority file /home/axTest/.Xauthority
xauth: timeout in locking authority file /home/axTest/.Xauthority
[EE]
Fatal server error:
[EE] Cannot open log file: "/home(axTest/.local/share/xorg/X.org.1.log"
[EE]
[EE]
Please consult the The X.org Foundation ....
[EE]
xinit: unable to connect to X server: Connection refused
xinit: server error
xauth: timeout in locking authority file: /home/axTest/Xauthority
axTest@Sat2aX2:~

When I do “sudo startx” I get a IceWM root session without the wallpaper. And when I try to log in into this forum I’m not able to enter my username or password. I just can’t type anything in the two boxes.

When I try to change to one of the other Desktops (rox-fluxbox, space-icewm, etc) the system just logs me out of the session and gives me the CLI back

When I update the system everything seems to go as usual except for some problem with /usr/bin/mandb

root@Sat2aX2:~
# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  antix-libs bash packageinstaller-pkglist
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,508 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.gr.debian.org/debian testing/main amd64 bash amd64 5.0-4 [1,378 kB]
Get:2 http://repo.antixlinux.com/testing testing/main amd64 antix-libs all 0.6.15 [85.3 kB]                                                                  
Get:3 http://repo.antixlinux.com/testing testing/main amd64 packageinstaller-pkglist all 0.2.17 [45.0 kB]                                                    
Fetched 1,508 kB in 14s (104 kB/s)                                                                                                                           
(Reading database ... 274011 files and directories currently installed.)
Preparing to unpack .../archives/bash_5.0-4_amd64.deb ...
Unpacking bash (5.0-4) over (5.0-3) ...
Setting up bash (5.0-4) ...
update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode
(Reading database ... 274011 files and directories currently installed.)
Preparing to unpack .../antix-libs_0.6.15_all.deb ...
Unpacking antix-libs (0.6.15) over (0.6.13) ...
Preparing to unpack .../packageinstaller-pkglist_0.2.17_all.deb ...
Unpacking packageinstaller-pkglist (0.2.17) over (0.2.16) ...
Setting up packageinstaller-pkglist (0.2.17) ...
Setting up antix-libs (0.6.15) ...
Installing new version of config file /etc/sudoers.d/antixers ...
Processing triggers for man-db (2.8.5-2) ...
/usr/bin/mandb: can't chmod /var/cache/man/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/vi/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/vi/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/vi/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/cs/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/cs/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/cs/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/sr/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/sr/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/sr/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/sv/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/sv/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/sv/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/ru/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/ru/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/ru/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/zh_TW/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/zh_TW/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/zh_TW/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/fr.ISO8859-1/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/fr.ISO8859-1/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/fr.ISO8859-1/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/pt/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/pt/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/pt/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/fr/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/fr/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/fr/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/hr/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/hr/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/hr/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/fr.UTF-8/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/fr.UTF-8/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/fr.UTF-8/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/id/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/id/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/id/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/fi/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/fi/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/fi/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/pl/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/pl/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/pl/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/es/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/es/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/es/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/pt_BR/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/pt_BR/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/pt_BR/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/da/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/da/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/da/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/tr/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/tr/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/tr/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/nl/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/nl/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/nl/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/ko/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/ko/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/ko/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/ja/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/ja/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/ja/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/de/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/de/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/de/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/it/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/it/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/it/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/zh_CN/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/zh_CN/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/zh_CN/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/hu/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/hu/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/hu/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/sl/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/sl/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/sl/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/oldlocal/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/oldlocal/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/oldlocal/4658: Permission denied
Processing triggers for menu (2.1.47+b1) ...
root@Sat2aX2:~
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@Sat2aX2:~
# 

Trying to find something out of normal related to xauth, the only thing I could notice is the difference in size between the files .Xauthority of my Testing install (104 B) and of my Stable install (53 B). My blind guess is that there may be a problem with my /home/axTest/.Xauthority file. Its permissions are “r–- r– –– —”.

Thanks for trying to help,
Zeh

[Forum Admin anticapitalista]

It is included on the iso – as xf86-video-sisimedia-antix

http://repo.antixlinux.com/stretch/pool/main/x/xf86-video-sisimedia-antix/

As live user, did you boot with default option?

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

antiX with runit - leaner and meaner.

[Anonymous]

… will NOT boot from iso that has been loaded on “MultiBootUSB”

It’s like saying: Can’t install GIMP 2.10.8 in Windows 10.
Where’s the exact version/subversion/build …
I make my multi-boot USB’s with YUMI.
For BIOS/Compatibility mode.

Please be advised that antiX,v17.4.1_386-full will NOT boot from iso that has been loaded on “MultiBootUSB” flash drive. Same thing applies to previous version. No problem with loadind, and using, other iso’s on that drive. BTW-I’m running linux Mint-MATE,19.1,64b. Thank you.

[Forum Admin BitJam]

fatmac wrote:

So, if a lot of people might have a problem with a 5.0 kernel, perhaps offer the option of both when booting live, & only install the one chosen when installing to disk.

We tried putting two kernels on one of the MX iso files a few years back. It wasn’t a disaster but it caused complications that I don’t think anyone is looking forward to repeating. Plus, on antiX, we are trying very hard to keep the size of our iso files down. Adding a kernel blows those efforts out of the water.

I agree though, that given these constraints, we should try to make it as easy as possible for people to change to the kernel they need. IIRC, most of the problems are with the graphics drivers but I really didn’t stay up on the conversations so I don’t know for sure.

Context is worth 80 IQ points -- Alan Kay

Four different times today(21Mar2019), dl the full 386v, and, using the app “MultiBoot USB”, which I’ve been using for over a year, cannot get antiX to load. All I get is page that says “For help press F1”. Well, that does absolutely nothing. Be advised that the 16GB flash card I am using is good, and BTW, Bionic Pup, and also FatDog64, are on it, and also Makulu Full, and all work well. A few months ago, I also tried loading and running antiX, and had same problem. The iso placed on a “LiveCD” runs fine. Would sure appreciate some advice on this. Thank you.

[Anonymous]

For a bootable CD/DVD, the APPEND line as seen here —}/boot/isolinux/isolinux.cfg
is where you would need to add the mount=all declaration

Prior to running the “isosnapshot” tool, if you edit /etc/iso-snapshot.conf and specify
edit_boot_menu=yes
you’ll be offered an opportunity to hand-edit the working_dir copy of isolinux.cfg & other files

edited to add//ask:

BitJam, hoping you will post to fill in the details for one of the “other ways”:
1) git clone https://github.com/BitJam/antiX-Gfxboot
2) edit/customize the contents of the various files
3) make

Looking to hear “make suchandsuch target” then…
then you can edit suchandsuch then “make ___” (all?)

[Forum Admin BitJam]

mattig89ch wrote:

Right, but thats on a flash drive. i want to create an ISO image with that, then burn that image to a disc.

The boot options are basically the same for an iso and a live-usb. So you can use “mount=all” on a live-cd/dvd made with our existing iso files. If you want to skip the step of typing in the cheat and have it “hard coded” into the iso then I can give you instructions for how to do that. You basically need to change the file /boot/isolinux/isolinux.cfg in the iso. There are several ways to do this.

Context is worth 80 IQ points -- Alan Kay

[Anonymous]

The antixers file contains some additional “cruft”:

%users ALL=(root) NOPASSWD: /usr/local/bin/update-default-desktop
^———- does not exist in antiX17 Full (outdated, or is this an optionally-installed item)
(i noticed the isolinux README file mentions update-default-desktop)

%users ALL=(root) NOPASSWD: /sbin/fdisk.distrib
^——— I had to “go look it up”
is outdated, and would only ever be seen if “gnu-fdisk” package was installed
.

%users ALL=(root) NOPASSWD: /usr/local/bin/persist-save
^——— an as-shipped “convenience” which AFAIK is undocumented and presents a vulnerability.
Unless toram boot option is selected and the boot device can be removed,
a bad actor (or scripted malware) has opportunity to permanently cement unknown/unwelcome
permanent changes to the live system by surreptitiously performing a perist-save operation.

%users ALL=(root) NOPASSWD: /usr/local/bin/persist-config
^——- presents an outright vulnerability ~~ ability to run root-permissioned arbitrary commands
Demonstration:

persist-config --mute --command "touch /etc/nasty_stuff"
persist-config --mute --command "ps_mem.py"

[Forum Admin rokytnji]

Does puppy linux use a whole lot less resources out of the box?

Depends. Puppy usually boots into using ram so you can pull the live media. There is a Puppy boot cheat code to not do this.
Read this:
https://puppylinux.org/wikka/BootParametersPuppy

I am hip noclue on Windows 10 hibernation issues and linux. Thanks for the tip.I am still waiting on my lovable control freaks permission to put my big ham grubby fingers on her laptop yet though.

I keep some isos like Hirens on a 1 TB drive. I used to use the cloud . But my Iso files started to disappear when sites went down.
Ubuntu Cloud. Mega. So I decided to just use hard storage.

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

[Anonymous]

clarifying what I had tested, in virtualbox:
pristine antiX-17.3.1_x64-full.iso ( but /etc/lsb-release states DISTRIB_DESCRIPTION=”antiX 17.2.1″ )

from terminal:
/usr/local/bin/menu_manager.sh

The app launches and, upon clicking “Personal”, the terminnal output shows
mkdir: cannot create directory ‘/home//.local'” Permission denied
chown: cannot access ‘/home//.local/share/applications/TCM’: No such file or directory

The app allows us to continue.
Click “Add”, choose an item to add, and upon clicking “OK”, terminal output shows
/usr/local/bin/menu_manager_personal.sh: line 483: /home//.local/share/applications/TCM…
… filenameofselecteditem.desktop: No such file or directory
chown: cannot access… no such file or directory

FWIW, identical result with the as-shipped ISO… and after apt full-upgrade has been performed

Running app from the menu works

aha, previously I hadn’t found a desktop menu item for “Menu Manager”.
Rechecking today, I found it (Preferences) submenu, but only after choosing a “small” theme variant.
With default theme, that item and quite a few others (SystemTools) were displaying offscreen
and “scroll to see more” (seriously, not sarcasm) didn’t occur to me.

^———- Yes, launched from the desktop menu, “Menu Manager” is working properly.
(note: full-upgrade has been performed. I haven’t retested this booting from as-shipped ISO)
Also tested today, launching “Menu Manager” via ControlCenter and that too is working properly.

[Forum Admin rokytnji]

I may be in the same boat. But on a Newer Asus Windows 10 laptop my wife uses for her work.
Won’t boot anymore.
Bios sees the hard drive.

There is a F key mount all option during the 1st live boot screen. I will probably use that. Like Anti said. Everything should show up in /media.

harry@biker:~
$ cd /media
harry@biker:/media
$ ls
E10C-A032

To make sure I have ntfs file support installed during my live session. Since I use full isos. It is usually a given thing ntfs support is installed.

$ apt-cache policy ntfs-3g
`

• This reply was modified 4 years, 2 months 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 rokytnji]

I mention the above because some world users with non-sse2 have been surviving on Opera 12 for ages now.

As far as Installing over 17.2.

No need. Just

sudo apt-get update

after that is done

sudo apt-get dist-upgrade

Say yes when asked. Let it finish. You are current now n 17.3.

If you just wanna start over anyways with a md5sum checked iso of AntiX 17.3
Just boot the install usb or dvd. Install over previous install. Nothing special. It is going to ask to format the drive anyways.
Just point it at

ID-1: / size: 143.71 GiB used: 4.25 GiB (3.0%) fs: ext4 dev: /dev/sda1
label: rootantiX17.1 uuid: f7bae392-2ec7-42a1-a629-9f8198b20d91

and tell the installer to put 17.3 there.
I’ll leave the video editing suggestions to other more knowledgeable members about that subject.

• This reply was modified 4 years, 2 months ago by rokytnji.
• This reply was modified 4 years, 2 months 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

[Member Xaver]

@ anticapitalista – Thank you for fixing iso-snapshot-antix.

iso-snapshot-antix_0.2.16_amd64 works fine in Sid and in Stretch.
Both snapshots boot without any problems.