-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Live USB filesystem is too small #406
Comments
One more piece of info - The OS im building on is Arch. |
The time you tell is long enought to try to imagine the problem...
|
Let me try If its the solution and I can find it I will open a PR. |
Just checked my build command, it already uses What part of the code creates the RAM disk? I can look into it |
penguins-eggs/src/classes/ovary.ts Line 1741 in f000a83
|
A possible work around is to use Ventoy with Persistence Plugin |
Ventoy looks interesting, but I would much rather use this project if I can. Ive been using it for almost a year, and this bug was only added recently, in the last month or so. What version can I roll back to where Arch would be better supported? |
Hey @pieroproietti What is the name of the command that creates the ramdisk? Tried Ventoy with the persistence plugin, still only shows 150mb of space. How can I help you get this fixed? |
@pieroproietti The suggestion in the stack overflow solved it: https://superuser.com/q/753134 By adding |
I have been using penguins eggs to make a live usb stick for several months, and recently after updating, when I boot the usb, the os only has about 150mb of free space on the in-memory filesystem. It makes it impossible to use the live OS because not everything can be moved to a mount point, and some things will still write to the ramdisk. And once it runs out of space I need to reboot.
Did something update that made the live disk smaller? I havent been able to figure out what it is if I broke something on my end, but this looks like some configuration change in eggs.
Any idea what this could be?
The text was updated successfully, but these errors were encountered: