From mint-bounce@lists.fishpool.fi Wed Feb 3 05:51:22 2010 Message-ID: From: "Jo Even Skarstein" To: "mint" References: <00933E7C-3B49-425B-AFCD-C7BF39DCD2AE@gmail.com> <4B689958.50001@lutece.net> <11a6f2b11002030054j4bd32a42me4037e91497e1f70@mail.gmail.com> In-Reply-To: <11a6f2b11002030054j4bd32a42me4037e91497e1f70@mail.gmail.com> Subject: Re: [MiNT] LDG vs. SLB vs. custom OVL-thingies Date: Wed, 3 Feb 2010 11:47:07 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726 X-EsetScannerBuild: 6517 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: -------------------------------------------------- From: "Paul Wratt" Sent: Wednesday, February 03, 2010 9:54 AM To: "mint" Subject: Re: [MiNT] LDG vs. SLB vs. custom OVL-thingies >> For this job there is alway's a good reason to add to system, this is >> memory >> management, simple application have no sure way to lock a memory bloc if >> a >> software allocate a memory bloc and crash there is no way to forbid >> destruction by the system, even Mint SHM not lock memory (I don't >> remember >> if Mint share the memory or do a copy, I think it share it). Are you sure? I had the impression that a shared memory block exists as long as atleast one process has an open handle on it. So if two apps (or a shared lib and an app) shares a memory block and one of them crashes, the memory block will not be freed. >> This is a real big problem to share memory to be able lock we should do a >> server, if it crash or kill all applications using libs will crash. With SLB this is taken care of by the kernel. > The server idea means more overhead, something which is a current > problem for low spec machine. That's true, and it's not necessary either. > garbage collector also, that they can be updated or changed or even What do you mean by "garbage collector"? > The documentation for all these just needs to be consolidated and made > available in at least one (if not 2 or more) central locations, as LDG SLB is documented in tos.hyp. Unfortunately there seems to be a lot of broken links in tos.hyp (well, atleast in the HTML-version at toshyp.atari.org) ATM. Jo Even __________ Information from ESET NOD32 Antivirus, version of virus signature database 4830 (20100203) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com