-
AuthorSearch Results
-
June 19, 2019 at 9:04 pm #23456
In reply to: Using snapshot to shrink size for iso
Anonymous
boot the ISO from the HDD
or frugal install to HDD…
June 19, 2019 at 4:23 pm #23437Forum Admin
BitJam
While running the live system, please run the following commands and let us know the output:
cd /live/boot-dev/antiX md5sum -c *.md5 head *.md5 ls -lh linuxfs* vmlinuz* initrd.gz*If you want to save the output to a file you could do something like:
cd /live/boot-dev/antiX md5sum -c *.md5 | tee -a ~/Live-usb-storage/md5-debug head *.md5 | tee -a ~/Live-usb-storage/md5-debug ls -lh linuxfs* vmlinuz* initrd.gz* | tee -a ~/Live-usb-storage/md5-debugI imagine this may be a harmless bug. Perhaps one of our programs did not update an .md5 file correctly.
It was good to check the md5 of then entire iso but that does not guarantee that the md5 checks for the 3 files were done correctly, it just means all the bytes in the iso file are correct even if those correct bytes include an incorrect .md5 file.
You could also run the same commands on a different system with the live-usb plugged in and mounted. Just cd to the $MOUNT_POINT/antiX/ directory and run the same tests.
Context is worth 80 IQ points -- Alan Kay
June 19, 2019 at 2:55 am #23366Member
Xaver
live-usb-maker-gui 0.2.4
live-usb-maker 0.3.1.4
iso-snapshot-antix 0.3.5At the end of creating the live-usb I get this error message:
Non-Fatal-Error At least one md5 checksum did not matchThe iso was created with iso-snapshot. It does boot in VirtualBox without problems.
If I check the iso with GtkHash, md5 and sha512 are ok.
If I check md5 from the boot menu of the iso, I get the same error message.- This topic was modified 3 years, 10 months ago by Xaver.
June 19, 2019 at 12:18 am #23359In reply to: Using snapshot to shrink size for iso
Member
eugen-b
Not the exact answer to your question, but instead of using a CD you could try to boot the ISO from the HDD if you have an existing Linux+Grub installation on it. You can edit /etc/grub.d/40_custom, add the following code for the Grub menu entry
menuentry "antiX-19.b1 x64 ISO" { set root='hd1,gpt6' set isofile='/ISO/antiX-19.b1_x64-full.iso' search --no-floppy --file --set=root $isofile loopback loop $isofile set gfxpayload=1920x1080 linux (loop)/antiX/vmlinuz quiet toram from=hd blab='DataHDD' fromiso=$isofile initrd (loop)/antiX/initrd.gz }and run
sudo update-grub. Reboot and you will have the new menu entry antiX-19.b1 x64 ISO in Grub menu.
Assumptions: The ISO file will be saved in the folder /ISO on a partition 6 (“gpt6”, likewise “msdos6”) of the second disk (“hd1”), blab=’DataHDD’ being the disk label of the partition where the ISO is, toram is optional (better remove it, because you probably don’t have enough RAM for the whole ISO plus the running system).- This reply was modified 3 years, 10 months ago by eugen-b.
June 17, 2019 at 8:48 pm #23244In reply to: antiX-19-b1-full (64 and 32 bit) available
Anonymous
On my install here 19b1-32bit.
I did the install from iso and first boot hooked to my ethernet cable
then on the first boot, I did an “apt update & apt upgrade from the root
terminal and rebooted. Afterwards connman seen my wifi and let me set it up.
Now it works everytime no need to stop and start it again.June 16, 2019 at 11:22 am #23115In reply to: antiX-19-b1-full (64 and 32 bit) available
Memberseaken64
I tried the 19-b1 today in a live session from USB. I used MX Live USB to create using 32-bit iso.
The initial boot is good and everything seems snappy and clean. I like the new default wallpaper but I think the selection of choices for wallpaper is too limited.
I used the new connman program for wifi and it worked beautifully. I usually use Ceni but did not even attempt it yet due to what I had already read on the forum.
I like to increase the font size from 96 to 120. When I used the Control Center app to increase the font size I ended up with an unusable screen. Some of the entries disappeared from the Control Center panel and I could not open the font size app to try and revert back to 96 dpi. I rebooted to get back to the standard 96 dpi and everything is working fine again.
I will stay with 96 dpi while I continue to test out this new version just so I can avoid screen problems while I look around.
On the IceWM menu there is a “Preferences” entry just above Themes. There is also a Preferences entry at the bottom of the Applications menu. It’s a little confusing that they are named the same.
But so far I like the new version. Thanks for continuing to provide a 32-bit option.
Seaken64
June 16, 2019 at 12:19 am #23075In reply to: antiX-19-b1-full (64 and 32 bit) available
Member
koolstofje
When I boot on usb ..
Fatal error..
Neither aufs nor overlays is availablep=power off
r=reboot[is this a snapshot?]
No directly 19-b1
Both with unetbootin and antix-usb-makerSomething is horribly wrong. My bet is a file got named incorrectly to antiX-19.b1_x64-full.iso.
Now
Only to RAM does not work
When I boot the USB directly, it seems to work.
This is what I get now.Error: /init: Line 1: Prog_cp: Not Found
Copy Failed.
Cannot do Toram.June 15, 2019 at 7:01 pm #23070In reply to: antiX-19-b1-full (64 and 32 bit) available
Forum Admin
BitJam
When I boot on usb ..
Fatal error..
Neither aufs nor overlays is availablep=power off
r=reboot[is this a snapshot?]
No directly 19-b1
Both with unetbootin and antix-usb-makerSomething is horribly wrong. My bet is a file got named incorrectly to antiX-19.b1_x64-full.iso. The md5 for the real 19.b1 iso file is:
343c2f0ad8ea36d73459c2ee4222522e
You can use the md5sum program to check the md5 of the iso file you’re using. If the md5 matches and you still get this problem then my last guess is there is another usb-stick or partition or something that you are booting from. There are a number of ways to get the error message you got but I don’t understand how it could happen if you are using the iso file we distributed.Context is worth 80 IQ points -- Alan Kay
June 15, 2019 at 11:59 am #23056In reply to: antiX-19-b1-full (64 and 32 bit) available
Member
koolstofje
When I boot on usb ..
Fatal error..
Neither aufs nor overlays is availablep=power off
r=rebootIs this a snapshot? Has that bug come back again *sigh* https://www.antixforum.com/forums/topic/iso-snapshot-antix-0-3-1-fatal-error/
No directly 19-b1
Both with unetbootin and antix-usb-makerJune 15, 2019 at 11:30 am #23052In reply to: antiX-19-b1-full (64 and 32 bit) available
Forum Admin
anticapitalista
When I boot on usb ..
Fatal error..
Neither aufs nor overlays is availablep=power off
r=rebootIs this a snapshot? Has that bug come back again *sigh* https://www.antixforum.com/forums/topic/iso-snapshot-antix-0-3-1-fatal-error/
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
June 14, 2019 at 2:57 am #22944In reply to: antiX-19-b1-full (64 and 32 bit) available
Member
eugen-b
It would be great to implement a more normal copy and paste in urxvt like in Manjaro i3 edition for example, I will look for the config and post a link. https://gitlab.manjaro.org/profiles-and-settings/desktop-settings/blob/master/community/i3/skel/.Xresources
We already have a mechanism for tweaking urxvt called urxvt-style. Use “urxvt-style –help” to get instructions.
The idea is to make it easy to play with different settings like:
urxvt-style tabbed medium size16 zenburn transbg
Once you find your sweet-spot then append the “save” command:
urxvt-style tabbed medium size16 zenburn transbg save
and those settings will be saved in the ~/.Xresources file.It would be easy to add other options to this system. Or if they are overwhelmingly better than the default perhaps we could add them to ~/.Xresources directly.
I now tried urxvt-style and it works great, I prefer the zenburn colour scheme to the default one in the distro I mentioned.
* But it would be great if the new user wouldn’t start with a white urxvt with small font.
* Which means to get the .Xresources file reliably read at startup without the need of urxvt-style reset command.
* IMO, the options for clipboard are very useful for new users. (They might be undesirable for longtime urxvt users who know how to copy and paste without them.)! Normal copy-paste keybindings without perls URxvt.iso14755: false URxvt.keysym.Shift-Control-V: eval:paste_clipboard URxvt.keysym.Shift-Control-C: eval:selection_to_clipboardUPDATE: @BitJam, I checked that urxvt starts in antix style (black background) on all sessions except herbstluftwm. So the issue with .Xresources is only in hlwm, where you need to run urxvt-style reset or xrdb merge .Xresources on each startup. So it would make sense to put one of these commands into ~/.config/herbstluftwm/autostart as a workaround, or find out if there is something missing in SLiM or antix-sessions for hlwm session.
UPDATE 2: I found the conditions to reproduce it (select herbstluftwm in the boot menu query) and filed a bug report: https://bugs.mxlinux.org/show_bug.cgi?id=115
If I log in to herbstluftwm via SLiM the terminal urxvt is themed according to .Xresources, but I get a session election window which is quite useless at that place, see the bug report for details, no need to flood the topic here more than that.- This reply was modified 3 years, 11 months ago by eugen-b.
- This reply was modified 3 years, 11 months ago by eugen-b.
June 13, 2019 at 6:36 pm #22927In reply to: default to persistent when booting live usb
Membersmolin
Sorry, me again! First of all, I feel a little whiney here, so let me say that the Antix tools are top-notch, I’m really impressed! For me they just barely miss the mark, though: live-usb-maker lets you make new usb with a vanilla live Antix on it; live-remaster gives you a custom live Antix with your modifications (apt installs and so on) applied … but does it in-place on the running usb! Can I get the custom live Antix copied onto a new usb drive?
Exercise: create a pair of live-usb with persistence, DHCP, apt package manager, systemd-free, no GUI, ssh-enabled.
Resources: internet connection, Mac or Linux computer, *four* usb drives.
Warning: replace the # correctly in step 3 or you can wipe your hard drive.
Untested:
1. Download antiX-17.4.1_x64-net.iso 2. insert usb-one, note device path for next step (lsblk in Linux, "diskutil list" in MacOS) 3. dd if=antiX-17.4.1_x64-net.iso of=/dev/disk# bs=8m 4. boot from usb-one 5. insert usb-two and note device path for next step 6. live-use-maker --from=clone 7. reboot from usb-two, using F5 to select persistence option and F8 to save boot parameters. 8. write a *script*, eg adduser jdoe; apt install -y openssl ca-certificates 9. use dd to duplicate usb-two onto usb-three (probably have to reboot using usb-one first) 10. boot from usb-three 11. apply customize script created in step 8 12. live-remaster and follow promptsRepeat steps 9 through 12 with usb-four in place of usb-three to make another one. Suggestions for shortcuts?
June 13, 2019 at 10:51 am #22888In reply to: default to persistent when booting live usb
Membersmolin
Success! Thank you again, Skidoo. In case someone finds this thread and wants to follow in my footsteps, here’s the play-by-play:
Exercise: create a live-usb with persistence, DHCP, apt package manager, systemd-free, no GUI, ssh-enabled
Resources: internet connection, Mac or Linux computer, two usb drives (usb-one > 155M, usb-two > 207M)
1. Download antiX-17.4.1_x64-net.iso 2. insert usb-one, note device path for next step (lsblk in Linux, "diskutil list" in MacOS)Make sure you use the right number in place of # or you can destroy your current system:
3. dd if=antiX-17.4.1_x64-net.iso of=/dev/disk# bs=8m 4. boot from usb-one; insert usb-two and note device path for next step 5. live-use-maker --from=clone 6. reboot from usb-two, using F5 to select persistence option and F8 to save boot parameters.You can remove usb-one, you’re done with that one.
7. at this boot you'll be prompted for persistence settings 8. apt install -y openssl ca-certificatesStats (approximate, I’ve added a couple other packages): 284 packages, 207M disk space, 92M RAM, 155 processes, 29 services
[edit: use “code” tag to preserve double-dash]
- This reply was modified 3 years, 11 months ago by smolin.
June 13, 2019 at 7:59 am #22877In reply to: antiX-19-b1-full (64 and 32 bit) available
MemberPPC
Just downloaded 19b1, ran it live, seemed OK, installed it, went OK, however, it didn’t carry over my wifi settings, (keep settings), setup ceni from internet menu didn’t work, setup wifi from control centre, ceni, worked – but – it doesn’t connect to the internet. Checked the site is working OK on another laptop.
Control centre > Network > Connman = ????? – Couldn’t get any wifi at all.
Ifup says it is configured, my other laptop is still connected to the internet OK, so it’s not my internet connection.
Ran ifdown, & ifup again, still not connecting to the internet, (using firefox).
Tried dillo, still not connecting to the internet.
Previously was running 17.1, I think, on this netbook OK.
P.S. Ifconfig -a shows no activity.
EDIT: Modules loaded, ath9k, ath9k_common, ath9k_hw, ath, mac80211, cfg80211
Oops, forgot, this is the 64bit full .iso (loaded on/from a pendrive).
@Fatmac- I had a similar problem with antiX 19A2- I haven’t tried the beta yet, but, anti still says “* connman replaces wicd and is default.ceni still included, but to use it you need to remove connman.”, so you can’t use ceni without deleting connman…
In alpha2 I configured my wi-fi, booting from live USB (sometimes connman refused to see wi-fi signals and I had to reboot), but when I did a frugal install with root/home persistence, after rebooting connman did not detect any wi-fi networks. My workaround was running ceni and choosing the first option related to my wifi network (something like delete Wlan0 configuration, or something like that). Once I do that, connman starts showing wi-fi networks and does what it should, and auto-connects to my wi-fi network. Maybe the same applies to the Beta1?@ the dev team: As always glad to see “my” OS evolving, even doing the mainstream thing and skip a version number, just like the most used desktops OS in the world did. In the end I like that option- now the antiX number matches the current year 🙂
Edits 1 and 2: I couldn’t wait and tried the 32 bits version on virtualbox (it runs slow to really in my system to really test anything, I just gave a quick glance): the papirus theme out of the box looks great. The “Exit session” menu now looks very modern and all icons match perfectly there (How to improve perfection? If that exit menu is done in YAD, maybe remove windows decoration and add a cancel GTK button?- it’s just a minor change but it would improve even more that menu, making it even more modern). The Control Centre icons look really, really much better tham those in antiX 17.X and antiX 19alphas, now the user can mostly guess what the icons do with a quick glance. Still love the new wallpapers and the fact that they are not “branded”.
I know the 32 bits version is way less demanding on RAM, but how the hell does a full system run on 58Mb of idle RAM? Sorcery? 🙂
I’m just sorry that anti warned that the feature I used the most on antiX19A2- smtube youtube player does not work with the current youtube-dl version. Not a really big problem, for most users.@devs: I found not a bug but some strange little error in the menu. I’m using the portuguese version, if that’s relevant… If I, in IceWm ( I did not test any other desktop), click Menu- applications – Internet- the menu displays way more than just the “internet” itens, it seems to mix the “application” menu and the “internet” menu itens- but if I click the “internet” option available from that part of the menu, the correct “internet only” itens are displayed in the new column… Copy/paste error on the “menu” file I guess?
P.
- This reply was modified 3 years, 11 months ago by PPC.
- This reply was modified 3 years, 11 months ago by PPC.
June 13, 2019 at 3:47 am #22867In reply to: antiX-19-b1-full (64 and 32 bit) available
Member
eugen-b
My previous posts on antiX-19-b1-full:
Sorry for posting my reply about antiX-19.b1 here, but the isn’t any topic for it yet. (I hope you will move this post there.)
* With the boot parametertoramwhen loadin the ISO with Grub directly (haven’t tried a live USB, yet) I get the error:
Create toram tmpfs at /live/to-ram (1115 MB)
/bin/mount -t tmpfs -o size=1115m,noatime tmpfs /live/to-ram
Will copy files from /live/iso-file/antiX to /live/to-ram/antiX. Please be patient ...
cp -a /live/iso-file/boot /live/iso-file/EFI /live/iso-file/version /live/to-ram
Copy failed. Cannot do toram
Error: /init: line 219: prog_cp: not found
initrd.log is attached.* Fluxbox with papirus-antix looks great!
* All menu entries open, Applications -> System Tool not tested (too many).
* Personal -> Personal Help Video gives an error, screenshot attached.
https://www.antixforum.com/wp-content/uploads/2019/06/personal-menu-help-video-ERROR.jpg* I got the same error with a live USB on a different machine (Lenovo idepad 110S netbook)
Error: /init: line 219: prog_cp: not found
EDIT I forgot to mention explicitely that it didn’t happen with a1/a2.* Both wpa_gui and ceni don’t find any connections. In Connman Settings I needed to enable WiFi first then the connections appeared. I think Connman Settings should be also in the Internet submenu.
* Is it possble make the live system set the keyboard layout according to the boot menu options selected? keytable=xy
I had to do it from CC.* Update: Personal -> Personal Help Video works on laptop.
- This reply was modified 3 years, 11 months ago by eugen-b.
Attachments:
-
AuthorSearch Results
Search Results for 'boot from iso'
-
Search Results
-
live-usb-maker-gui 0.2.4
live-usb-maker 0.3.1.4
iso-snapshot-antix 0.3.5At the end of creating the live-usb I get this error message:
Non-Fatal-Error At least one md5 checksum did not matchThe iso was created with iso-snapshot. It does boot in VirtualBox without problems.
If I check the iso with GtkHash, md5 and sha512 are ok.
If I check md5 from the boot menu of the iso, I get the same error message.- This topic was modified 3 years, 10 months ago by Xaver.