Virtual Memory Settings in Mac OS
Francois Taiani
mol-general@lists.maconlinux.org
Mon, 12 Aug 2002 09:23:53 +0200
Hi Sascha,
apparently my freezes were caused by some obscure bug in the virtual
memomy emulation of mol. The solution I was suggested by Samuel, the
original developper of mol, was to deactivate the virtual memory in
MacOS (in the apple menu, then in the config menu, the "memory" entry),
and allocate more memory to mol in .molrc (I put "ram_size: 125", and
it's fine for what I do in MacOS).
Since Linux has its own swap, and mol its own virtual address space, you
don't need worry about exhausting your main memory. I think you can
correctly see the "ram_size: 125" as an upper limit on the memory mol is
allowed to used, but in most cases mol will stay far below it.
Now this solution has serious drawbacks if you want to regularly boot
directly in MacOS and do normal work without mol, since you won't have
any VM management at all in the bare MacOS :(
Furthermore, I'm still using a 0.9.63-x version of mol (actually an
intermediary source snapshot, so it's something between -63 and -64),
and those VM bugs should have been corrected in the 0.9.64 version you
have. It would be interesting if you could try the above workaround and
report the result to the mol mailing list
(mailto:mol-general@lists.maconlinux.org).
Viel Erfolg !
Francois
> Hi Francois...
>
>
> i recently read your post on the debian-powerpc@lists.debian.org mailing
> list. did you yet find any solution for the freezing problem. i got
> exactly the same one.
>
> i am running Mac-on-Linux 0.9.64 on a lombard powerbook with kernel
> 2.4.18-9a (ydl 2.2)
>
> if you got any hint for me, please reply.
>
> thank you in advance
> sascha
--
Francois Taiani Dependable Computing
http://www.laas.fr/~ftaiani and Fault Tolerance