Forum › Forums › New users › New Users and General Questions › [SOLVED] frugal install 32-bit antiX
Tagged: tags: extra large, use no bleach
- This topic has 153 replies, 10 voices, and was last updated May 5-10:25 pm by Brian Masinick.
-
AuthorPosts
-
April 19, 2022 at 6:13 am #81687Member
dugin
::I got a boot error when I just copied files over to the larger 16-MB USB. Then I tried to remaster 8-MB liveUSB, and got an error that I have 762 MB free space, but i need 972 MB to remaster. Any way to get more free space?
I just did a fresh install of antiX on the 16-GB usb. I gave the save file 10 GB of room to expand. I installed the apps I want from package installer. Then I tried to do a remaster. Error: You only have 665 MB, you need 995 to remaster. I thought maybe this error was because I was running in RAM. I rebooted without the toram option, same error. How is it even possible not to have enough space with a new install?
During installation, which files or directories give an option to change size?
- This reply was modified 1 year ago by dugin.
- This reply was modified 1 year ago by dugin.
- This reply was modified 1 year ago by dugin.
April 19, 2022 at 11:42 am #81710Moderator
christophe
::If you were to set up a new 16 gb flash drive for live-usb, this may be a good setup:
The live usb may take up 1 gb to start.
The root persistence file maybe 4 gb (to be generous) to begin adding programs & files.
This leaves maybe 10 gb space for remastering.So do that on first-run. Install everything you want. Then remaster.
After reboot, run the “set up persistence” program, to “fix/remove” old persistence files (rootfs.old, linuxfs.old), to regain disk space.
Once you know your newly remastered system is running as it should, you should (IMO) delete those obsolete files to regain the space they are using on disk.This routine should ensure you don’t run out of space.
Also, check the ~/Live-usb-storage directory, too, for any misc. files you have saved that may be moved (at least temporarily) to get a remaster done.
- This reply was modified 1 year ago by christophe.
- This reply was modified 1 year ago by christophe.
- This reply was modified 1 year ago by christophe.
confirmed antiX frugaler, since 2019
April 19, 2022 at 11:45 am #81712Forum Admin
anticapitalista
::You have probably run out of RAM.
How much do you have?Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
April 19, 2022 at 12:39 pm #81716MemberRobin
::When running in this remaster error due to lack of free space: I’ve described a possible solution here: https://www.antixforum.com/forums/topic/how-to-recover-from-live-remaster-error-on-frugal/
On a System with 2GB RAM you might run into out-of-RAM error while doing a complete apt-upgrade in one shot. So my path to overcome this is: Update in tranches.
apt list --upgradable
then update from this output list 10 or 15 packages using the apt-get install command, and then check your free amount of RAM. Repeat this step until you have only something between 500MB and 1GB RAM left free. Then start a first remaster. Once it ran through, and after reboot, repeat the whole process starting with apt list –upgradable and again update as many packages your amount of RAM (or space in rootfs file in case of persistence) would allow you. And remaster again. Always take into account you need some amount of space to allow the remaster tool to be executed still.
Repeat this procedure until you have updated the complete system, and no packages are left on the list apt shows you.
This path will work on Live antiX with or without persistence, and also on a frugal install. But in case you are short of disk space on your boot device (e.g. only 8GB), follow the path I described in the linked thread, temporarily deactivating the persistence and moving the persistence files out of your way, until the last remaster is done. Then you may restore the home persistence file (homefs) back in its place on the boot device, (while the root persistence is merged into the linuxfs file now, so let it get created anew by the system itself). And you can boot to persistence again after this if you like.The same is true when installing a heavy amount of new packages (programs). You may run into exactly the same problem, and it can be overcome the same way.
Windows is like a submarine. Open a window and serious problems will start.
April 19, 2022 at 1:44 pm #81719Memberdugin
April 19, 2022 at 1:44 pm #81720Moderator
christophe
::I would switch to static persistence, at least temporarily, if you find you are running out of ram.
Test what the performance difference is on your machine. Maybe it’s better as static, anyway…
confirmed antiX frugaler, since 2019
April 19, 2022 at 1:47 pm #81721Moderator
christophe
::Switch to pae kernel to get 4 gb or more on 32 bit (assuming you have 4 gb or more installed). (Live kernel updater – maybe solve this current issue first before making it more complicated, though…)
- This reply was modified 1 year ago by christophe.
confirmed antiX frugaler, since 2019
April 19, 2022 at 1:53 pm #81723Memberdugin
::I think you’re saying that remastering is done on unused RAM or unused USB drive space, in which case I would need to reduce the size of the root persistence file. I also set up a 1 GB swap file on the USB. Not to argue, but the error claims that less than 1 GB is needed to remaster, is this estimate realistic?
April 19, 2022 at 3:20 pm #81729Moderator
christophe
::yes. unused space on usb stick.
yes, on accuracy of the program’s free-space-o-meter. šconfirmed antiX frugaler, since 2019
April 19, 2022 at 3:41 pm #81731MemberRobin
::in which case I would need to reduce the size of the root persistence file.
In this case you might also run into a no-space-left-on-DISK problem when trying to update your system and save the modifications in persistence before powering down the machine. Then the root file system is possibly to small to take all the new files.
And you also might run into no-space-left-in-RAM, when you do it while root persistence is activated: This keeps the root file system in RAM while working, it is stored to the file only either on system shutdown (if set in the preferences this way) or by manually choosing the respective save root persistence entry from antiX menu.
So on systems with small amount of RAM and/or Diskspace you have to keep the balance carefully between the different amounts of free space involved: Making the rootfs file too small, it can’t take the updates. Making it too big, the remaster will fail, since rootfs takes all the space on disk… And updating a system with small RAM completely will only work in tranches at all.As said above, in case of small amount of Disk space on live boot medium best is to deactivate persistence temporarily and put the corresponding files aside while updating the system and remastering (don’t forget to remaster before you start, so the existing root file system content is merged into the linuxfs file already. You’ll get a new empty rootfs after the system update and last remaster)
Windows is like a submarine. Open a window and serious problems will start.
April 19, 2022 at 4:20 pm #81733Memberdugin
::I selected Default for the persistence file (6 GB), leaving 7.15GB free space (out of 14.4GB). After compression, the linuxfs file grew from 734 MB to 1.01 GB using gzip. After compression I am being prompted to select size of rootfs.new (for remastering), with available space of 6.13 GB. The size can be up to 4 GB. Please recommend an appropriate size for rootfs.new. So far I have installed about 3/4 of the apps that I want.
I decided to switch to 64-bit. There is a PAE flag on the processor, according to inxi -zv7. The choppy video lag is much improved using USB 3.0 thumb drive, although computer USB is 2.0. The video stream is no longer choppy, video continuity and flow is good, but may lag the sound by a fraction of a second. Hardly noticeable.
- This reply was modified 1 year ago by dugin.
- This reply was modified 1 year ago by dugin.
- This reply was modified 1 year ago by dugin.
April 19, 2022 at 5:13 pm #81752Moderator
christophe
::Choose 3 GB.
Install everything you want. Then remaster.
After reboot, run the āset up persistenceā program, to āfix/removeā old persistence files (rootfs.old, linuxfs.old), to regain disk space.
Once you know your newly remastered system is running as it should, you should (IMO) delete those obsolete files to regain the space they are using on disk.This routine should ensure you donāt run out of space.
confirmed antiX frugaler, since 2019
April 19, 2022 at 5:20 pm #81754Memberdugin
::I’m in the process of remastering. It asks me to select size of rootfs.new, up to 4 GB with 6.13 GB available space. Please recommend size of rootfs.new. I’ll remaster again after I install the rest of the apps and do browser bookmarks. For practice.
What happens to free space if I select 4GB? Will free space be reduced as, 6.13 – 4 = 2.13 GB free space? I have no idea what I’m anticipating in selecting this file size. I don’t know if the selected file size is permanent, or adjustable every time I remaster.
EDIT: 3GB. Thanks (That would have been my guess, but what do I know.)
- This reply was modified 1 year ago by dugin.
- This reply was modified 1 year ago by dugin.
- This reply was modified 1 year ago by dugin.
April 19, 2022 at 6:07 pm #81770Memberdugin
::When I started this remaster, I had disabled Conky, put Connman in the systray, put maybe 15 shortcuts on desktop. Those mods did not get implemented in the remaster. Are these mods in the “Personal” category? What about bookmarks, will they carry over through a remaster? Should I be selecting Personal rather than General for type of remaster? Is this why the mods didn’t take?
I wonder if 32-bit would have better effect on the video lag, as opposed to 64-bit. Would there be much difference?
- This reply was modified 1 year ago by dugin.
April 19, 2022 at 9:23 pm #81791Moderator
christophe
::You select size each time you remaster.
You want personal remaster – to save your prersonal settings. General will not.I wonder if 32-bit would have better effect on the video lag, as opposed to 64-bit. Would there be much difference?
You’ll have to experiment on that one…
confirmed antiX frugaler, since 2019
-
AuthorPosts
- You must be logged in to reply to this topic.