Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!leah!rpi!rpi.edu!shadow From: shadow@pawl.rpi.edu (Deven T. Corzine) Newsgroups: comp.sys.amiga.tech Subject: Re: Unix V7 functionality under (or along with) AmigaDOS? (*LONG*) Message-ID: Date: 19 Mar 89 13:28:30 GMT References: <0776.AA0776@julie> <3632@sugar.hackercorp.com> Sender: usenet@rpi.edu Reply-To: shadow@pawl.rpi.edu (Deven Thomas Corzine) Organization: RPI Public Access Workstation Lab, Troy NY Lines: 38 In-reply-to: peter@sugar.hackercorp.com's message of 16 Mar 89 11:27:39 GMT In article <3632@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes: >In article , deven@pawl.rpi.edu (Deven Corzine) writes: >>In article <3626@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes: >>>Ah, pretty please. If you do nothing else in 1.4 could you let us dup() >>>filehandles, and track them so I can pass a FH to a process and not have >>>to worry about getting it back to close it? >>Why can't you, if the program you pass it to closes it? >I'm working on a shell (it's called "browser"). The program I pass >it to does not, in general, know that I want them to close it. >>>I can deal with untracked memory, but there's ever so much UNIXy code out >>>there that expects UNIX file descriptor semantics... >>Surely so. Got a simple example in mind? >Surely. Any UNIX program that does I/O redirection. > if(!fork()) { > close(0); > fd = open("/tmp/workfile", 1); > if(fd!=0) exit(1); > execl("/usr/peter/bin/output", "output", (char *)0); > exit(2); > } >No need to do ANYTHING to clean up /tmp/workfile. Duh. Yeah, that's a simple example. I see what you mean. Well, hey. Use my "Amigix" environment, when/if I finish it... :-) Deven -- ------- shadow@pawl.rpi.edu ------- Deven Thomas Corzine --------------------- Cogito shadow@acm.rpi.edu 2346 15th Street Pi-Rho America ergo userfxb6@rpitsmts.bitnet Troy, NY 12180-2306 (518) 272-5847 sum... In the immortal words of Socrates: "I drank what?" ...I think.