- This topic has 19 replies, 5 voices, and was last updated Jun 24-2:59 pm by dski.
-
Posts
-
dacomboman
Hi,
After listening to Dolphin Oracles’ video on running Antix from usb,
things seem to be pretty easy to do.
Have an extra usb device and plan on downloading the latest Antix iso with Rufus.
Question!
If persistence is made to same usb, will .iso be automatically overwritten (deleted)?dski
I don’t know for sure, but I doubt very much that the iso would be overwritten.
I, too, am confused about persistence, however. After reading all the help I
could find for it, I still didn’t know WHERE persistence data is stored, so I
gave up on the idea and went ahead with a regular install.Many thanks to the team for not going the systemd/Wayland way, and for including
a text-mode browser and a WordStar-like editor.On the Mac, Ctrl didn't exist; in Windows, Ctrl-A through Ctrl-Z did virtually nothing. From 1985 on, the choice was clear: you could get the full benefit of the most basic standard of computing, or you could use a GUI and a crippled keyboard and become this or that vendor's slave. I chose WordStar. LIVE FREE OR DIE.
Anonymous
Nothing will get overwritten, only the changes will get saved in a file.
The ISO file never lands on the USB drive when using rufus.
Rufus formats the USB drive then copies content extracted from the ISO file and adds a bootloader.Afterward, the ISO file is not needed, is never looked for.
If, for some reason, you decided to copy the ISO file (or any other file(s)) onto the liveboot pendrive, you can expect that nothing will disturb//overwrite them ~~ they’ll just take up storage space until or unless you manually delete them.WHERE persistence data is stored
If you attach the liveboot drive to an already running system, when you use a file manager to explore its contents you would see in its toplevel directory an “antiX” subdirectory. The persistence files reside in this subdirectory.
I haven’t used “static” persistence for a while, so I’ll just describe
the persistence files associated with “dynamic” (saved on-demand and/or at shutdown) persistenceThe arrowed files are squashfs files. They provide “filesystem within a file” storage.
(to learn more, websearch “squashfs” or from commandline: apropos squashfs)rootfs {——-
homefs {——-
linuxfs
initrd.gz
vmlinuz
random-seed
initrd.gz.md5
vmlinuz.md5
linuxfs.md5
/state
/state.oldWHERE persistence data is stored
To access that same storage location from a running liveboot session (and you have booted from that device), you can (AsRoot) browse to /live/boot-dev/antiX
If you inspect /etc/fstab
(or at commandline, type: mount)
you can see the mountpoint associated with this storage location, e.g.
/dev/sdb1 on /live/boot-dev[redacted]
dksi, as explained in FAQ docs-antiX-17/FAQ/persistence.html
we are able to choose a non-default storage location for the persistence files.[redacted] this post was a bit off-topic
As a former technical writer, I can’t object to being told to read
the, uh, fine manual, but it’s a lot of steps from the live media
bootup screen to the FAQ and back, and I wasn’t going to spend a
lot of time on it after seeing “You can make permanent changes on
SOME LiveUSBs” (emphasis mine) under Boot Option Instructions.At the very least, I think “some LiveUSBs” should be changed to
“LiveUSBs created with Live USB Maker (but not the dd command)” or
something along those lines.Regards,
Dan StrychalskiOn the Mac, Ctrl didn't exist; in Windows, Ctrl-A through Ctrl-Z did virtually nothing. From 1985 on, the choice was clear: you could get the full benefit of the most basic standard of computing, or you could use a GUI and a crippled keyboard and become this or that vendor's slave. I chose WordStar. LIVE FREE OR DIE.
There are some help videos on the topic too.
https://www.youtube.com/user/runwiththedolphin/videos
https://www.youtube.com/channel/UCFWlej2CSKlXW5uE9opXukQThe ability to create a fine working Distro doesn’t automatically imply that the developers are able to make it look properly or that they understand how to write a good manuals.
That said, as a former technical writer, you might be willing to participate and make what you can — help writing some better documentation.
dacomboman
Well, i finally got Antix to run off a usb device, yay! 🙂
There’s so much to discover!
Can’t figure why password was not requested on boot though.BobC
dacomboman, if you go to control centre and go to the maintenance tab, there is a user manager option where you can setup user id’s, assign password, and on the options tab of it you can control autologin and if a password is required. Maybe that will work for you if saved via root and home persistence. I haven’t tried it that way, myself.
What I did was to install everything, change the setups to my liking, then created an iso and made a live usb of it, which I then could insert to boot. I did find that wasn’t perfect, because it did work in a number of machines but not one of them, due to hardware differences.
I ended up creating a process to almost semi-automatically tweak an antiX install to add, remove and configure things to the way I want them from a stock install.
Attachments:
dacomboman
@BobC – thanks!
I’m sure it’ll work out.
Have issues when booting from cold start.
Can’t get to usb device.
But if i do restart when in Windows, no problem.
That’s when i did what you showed, so it should be just fine.
Just an update.I have had problems where I couldn’t boot from USB on my EFI Dell laptop, but I haven’t seen that problem before.
Have issues when booting from cold start. Can’t get to usb device. But if i do restart when in Windows, no problem.
Please check the first screenshot first.
If that’s how your settings look like, then you have no issues when cold booting but, you probably don’t know how exactly Windows works.
Windows 8 / 8.1 / 10 have the ‘Quick Boot’ function turned on per default.
It’s some kind of suspend / hibernate ‘trick’ where, when you press the regular shutdown button, it doesn’t shutdown but, it goes into the ‘fake shutdown’ state.
It closes all open applications (in opposite to suspend / hibernate) but, it puts the system itself and some chosen / important applications (Edge) to sleep.
If you are dual-booting, you must always insure that the Windows is fully turned off before you access its partitions from another system.
There are a couple of ways to shutdown Windows completely.
The second screenshot shows you the ‘regular full shutdown’, as intended by Microsoft.
You have to go into Windows settings / recovery options and then press the restart now option.
New screen will open and there you get a couple of options, one of them being to shutdown your computer and the other one, to boot directly from another device.
There are three other ways to perform the complete shutdown too:
1. by reconfiguration of shutdown button in energy / power settings of Windows
2. command line shutdown (you can make a shortcut for the command to)
3. over the keyboard and mouse combinationYou can easily find many ‘how-to’s in internet on that matter.
Once your Windows is completely shutdown, if your BIOS is properly configured and you’re not using Asus, you shouldn’t have any cold boot issues any more.
Why Asus? HP usually has the boot options on F9, Dell and Lenovo at F12 but, Asus choose nothing else but exactly F8.
That’s very ‘sub-optimal’ since the Windows itself is using F8 for some extra boot options.
** It’s absolutely essential to understand how the ‘Quick Boot’ works.
1. Since the regular installation is never shutdown but, only in ‘fake shutdown’ state, that implies that it always needs / uses energy — even after ‘shutdown’.
Will say, if you let your computer laying around for a couple of months (HW dependent!), it can happen that your battery gets drained and damaged beyond repair (I know few such cases). Removing battery is also no option — Windows might (not will!) get damaged.
2. Windows ‘remembers’ in which state the files were on ‘fake shutdown’. Even accessing the files from another O/S during that ‘fake shutdown’ can lead to file inconsistencies because, Windows writes a lot of additional meta-data. That’s why, one should never change any files (write/save) on Windows partitions, and that’s why one should rather avoid even reading (opening) the files during the ‘fake shutdown’ condition. Even the auto-mount partitions function might kill Windows.
dacomboman
Wish i could understand German!
At present time, i’m dual booting with another Linux distro on Windows 10.
Everything there works just fine.What i find odd, is that i can boot live mode from usb with any Linux distro (.iso) just as it did with Antix,
but now that Antix is installed on it, it ceases to work (from cold boot with F9 as it is an HP).
- You must be logged in to reply to this topic.
