[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [MiNT] What's in, what's out?

To: "Guido Flohr" <gufl0000@stud.uni-sb.de>, "MiNT mailing list" <mint@fishpool.com>
Subject: RE: [MiNT] What's in, what's out?
From: "Julian Reschke" <reschke@muenster.de>
Date: Sun, 28 Nov 1999 12:20:57 +0100
Importance: Normal
In-reply-to: <19991128032222.F37@stud>
Reply-to: <reschke@muenster.de>
Sender: owner-mint@fishpool.com

> From: owner-mint@fishpool.com [mailto:owner-mint@fishpool.com]On Behalf
> Of Guido Flohr
> Sent: Sunday, November 28, 1999 3:22 AM
> To: MiNT mailing list
> Subject: Re: [MiNT] What's in, what's out?
> mbaserel has only one effect: The text segment is shared on fork(). But if
> your program forks and then execs another image you win nothing.  The fork
> is a little faster but that is eaten up by the base-relative addressing.

It's also shared on Pexec(), right?

Follow-Ups:
- Re: [MiNT] What's in, what's out?
  - From: Guido Flohr <gufl0000@stud.uni-sb.de>

References:
- Re: [MiNT] What's in, what's out?
  - From: Guido Flohr <gufl0000@stud.uni-sb.de>

Prev by Date: Re: [MiNT] What's in, what's out?
Next by Date: RE: [MiNT] What's in, what's out?
Previous by thread: Re: [MiNT] What's in, what's out?
Next by thread: Re: [MiNT] What's in, what's out?
Index(es):
- Date
- Thread