Tiny Core Base > TCB Q&A Forum
(Tiny)Core x86 : is there a reason not to enable PAE ?
Juanito:
..or, install Core, then make the minor changes required to run Core64.
SeventhSin:
--- Quote from: Juanito on July 16, 2019, 04:11:11 PM ---..or, install Core, then make the minor changes required to run Core64.
--- End quote ---
That could definitely work for me. However, one could argue pro another or:
... or upload a (Tiny)Core64 ISO to the website so that everyone can build software on x86 without seeing non-sense such as this:
--- Code: ---ld: final link failed: No space left on device
--- End code ---
... when there is more than 1.2 GB of RAM available at the time the error manifests and the build directory is on /mnt/sda1 which has roughly 6 GB of free space. :o
Juanito:
I’d guess there’s something amiss since I can build libreoffice on Core with 4gb ram (with the source on permanent storage).
SeventhSin:
--- Quote from: Juanito on July 16, 2019, 05:49:28 PM ---I’d guess there’s something amiss since I can build libreoffice on Core with 4gb ram.
--- End quote ---
My guess as well. I've seen "No space left on device" errors on Pure64 as well, however in that case the system was indeed out of RAM. All I had to do was to add a bit more RAM to the build VM and the error would go away, depends on what I build and how many dependencies I have to pull.
On x86 however, (bot installed and ephemeral RAM only boot), "No space left on device" does not make sense when looking at the resources available to the machine. What makes it worse is that the issue is semi-reproducible. Sometimes it happens, other times it doesn't.
Unfortunately, just adding more RAM isn't a solution due to no PAE in the kernel. As a matter of fact, that's what prompted me to open this thread in the first place. I was hoping to get away without a) having to build a custom Core x86 + 64 bit kernel ISO or b) having to investigate the issue further. ::) :P
As a note, I noticed this issue mentioned on a couple of older threads (2009-2011 if I remember correctly). In the threads that I saw, the original poster(s) were asked for all kinds of command output from their system (relating to RAM & DISK), however everything seemed fine. No solution was available as far as I remember.
I also noticed another error. I don't have the precise text handy right now, but it was related to mounting dependency extensions: cannot mount loopXXX blah-blah and then some mention to not enough space left. There was of course enough RAM & DISK available.
andyj:
What are the use cases for needing more than 4 GB on a 32-bit system in 2019? The only one I know of is compiling mariadb, and I have to use a VM to even have that kind of environment. A non-PAE capable processor is going to be quite old, and the rest system it comes with will be limited as well. This is one of the use cases for TC. Requiring PAE would create at least a few orphans.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version