Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!rpi!rpi.edu!deven From: deven@pawl.rpi.edu (Deven Corzine) Newsgroups: comp.sys.amiga.tech Subject: Re: Alternate environment (Re: Unix V7 functionality under (or along with) AmigaDOS? (*LONG*)) Message-ID: Date: 15 Mar 89 21:38:07 GMT References: <0776.AA0776@julie> <3624@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: 48 In-reply-to: peter@sugar.hackercorp.com's message of 15 Mar 89 11:47:59 GMT In article <3624@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes: >Here's an idea -- for someone feeling adventurous: Oh, reasonably adventurous, it would seem... >Take my "launch" code. What launch code? Normal WB startup or something else? >Have it use an extra bit to mark a file as special. There's still the danger of losing the bit, but ok... >If the file is special: > Don't get locks for arguments, just bundle the full file name. Getting locks for arguments? huh? > Add code to have it set up pr_CIS and pr_COS behind a process' > back, between the time it does a CreatProc and it sends the > startup message. Um, doable, I suppose. >Write an _main() that has, in addition to the normal stuff, a test for the >existance of Input() and Output(). If so, it pulls in argv from the WBArgs >list in the WBStartup structure. Hmm. >This should let you test most of the idea of a better shell without having >to create a whole new environment. Yeah, but I plan to create the new environment. But it's still worth considering... >Maybe add a return code to the end of the WBStartup structure... Perhaps... 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.