delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f |
X-Trace-PostClient-IP: | 68.147.131.211 |
From: | Brian Inglis <Brian DOT Inglis AT SystematicSw DOT Invalid> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Using DR-DOS fork in DJGPP |
Organization: | Systematic Software |
Message-ID: | <qhd3b0lp3lj5ja2jhb0cnaqkiru69mkg32@4ax.com> |
References: | <7704-Wed19May2004233123+0300-eliz AT gnu DOT org> <4d201f78 DOT 0405191847 DOT 6697f90d AT posting DOT google DOT com> <u3c5vbous DOT fsf AT gnu DOT org> <4d201f78 DOT 0405200540 DOT 307bb15a AT posting DOT google DOT com> <9743-Thu20May2004201223+0300-eliz AT gnu DOT org> <4d201f78 DOT 0405210913 DOT 26a5ffcb AT posting DOT google DOT com> <uwu33ad61 DOT fsf AT gnu DOT org> <4d201f78 DOT 0405230527 DOT 3f17fb4b AT posting DOT google DOT com> <2719-Sun23May2004185224+0300-eliz AT gnu DOT org> <f7f2b0tp6atvgj7rgqg83bo9mo2asdsndf AT 4ax DOT com> <ud64u8jcz DOT fsf AT gnu DOT org> |
X-Newsreader: | Forte Agent 1.93/32.576 English (American) |
MIME-Version: | 1.0 |
Lines: | 31 |
Date: | Mon, 24 May 2004 08:45:59 GMT |
NNTP-Posting-Host: | 24.71.223.147 |
X-Complaints-To: | abuse AT shaw DOT ca |
X-Trace: | pd7tw3no 1085388359 24.71.223.147 (Mon, 24 May 2004 02:45:59 MDT) |
NNTP-Posting-Date: | Mon, 24 May 2004 02:45:59 MDT |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
On 24 May 2004 07:49:48 +0200 in comp.os.msdos.djgpp, Eli Zaretskii <eliz AT gnu DOT org> wrote: >> From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT Invalid> >> Newsgroups: comp.os.msdos.djgpp >> Date: Mon, 24 May 2004 00:11:44 GMT >> >> Alternatively, the fork routine, after copying the VM, has to look at >> the child process' file handle table, and reestablish the open file >> handles. > >I don't see how this could be done, at least not easily. We don't >need just to have the same file open, we need their file handles to >refer to the same entry in the DOS System File Table (SFT), so that if >the child moves the file position (by, e.g., reading or seeking into >the file), the file position of the parent is moved as well to the >same place. I.e., we need the equivalent of the `dup' system call >(except that we cannot call `dup' because it doesn't work with handles >from another process). > >Therefore, if the DR-DOS's fork doesn't handle these problems, there's >no way we could, unless we know enough about DR-DOS internals to >manipulate the SFT entries directly. Precisely my point. -- Thanks. Take care, Brian Inglis Calgary, Alberta, Canada Brian DOT Inglis AT CSi DOT com (Brian dot Inglis at SystematicSw dot ab dot ca) fake address use address above to reply
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |