Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ames!oliveb!amiga!cbmvax!jesup From: jesup@cbmvax.UUCP (Randell Jesup) Newsgroups: comp.sys.amiga.tech Subject: Re: Unix V7 functionality under (or along with) AmigaDOS? (*LONG*) Message-ID: <6298@cbmvax.UUCP> Date: 15 Mar 89 23:23:05 GMT References: <6157@cbmvax.UUCP> <6185@cbmvax.UUCP> <6237@cbmvax.UUCP> Reply-To: jesup@cbmvax.UUCP (Randell Jesup) Distribution: comp Organization: Commodore Technology, West Chester, PA Lines: 56 In article deven@pawl.rpi.edu (Deven Corzine) writes: > >>Say, if I replaced that Command Dir lock that's in the CLI structure > >>for that one CLI process, would it look there without having to > >>assign c: elsewhere? > > > You believed the name of the field, didn't you? Poor naive boy. :-) > >It's really the BPTR to the path list. > >Figures. What form is this path list in? BCPL array of BSTRs? BCPL >array of locks? Something else? BPTR to a linked (BPTR) list of locks. (as in: {BPTR next; BPTR lock;}). (Note all locks are BPTRs to filelock structure (or things bigger than filelock structures)). >In other words, there would be a program which would be run (from the >CLI or Workbench) which would initialize the Unix-type system, install >the run-time library as permanently ram-resident, You can do this >easily, can you not? I mean, without dealing with LIBS: and >disk-based libraries and all that? I want the library to be part of >the data (and/or code) of this executable program, and have it use >that to install it as a permanently ram-resident Exec Library, without >any such library in LIBS:... I haven't looked closely at the Library >routines, but as I recall, it seemed doable enough. Sure, just make sure it isn't unloaded (cli_module = NULL), and do a MakeLibrary exec call. >The original program would return to caller after completing >initialization and starting the separate system process, so as to >avoid any hassles with having to RUN the program, etc. Will work fine. >One more thing. I need a name. "Unix" is clearly out. "Amix" I >rather like and would use, but now it's taken, too. "Minix" I don't >especially like and would give the wrong impression, as this would not >be a Minix port. ... >I'm pretty much at a loss for what to call it. It would probably be >nice to have it end in "ix", just for consistency. (everyone ELSE >does it!!) :-) So... have you (or anyone) ANY suggestions what this >could be called? Well, if it takes forever to finish, you could call it Vaporix. :-) How about Maxix? Micrix? Amigix? (AIX is out) Fooix, Barix, FooBarix? Fix? Trix (maybe GNU or some such grabbed this) Vix (visual Unix)? >p.s. I saw your old address in shell.doc on that shell 1.03 beta >disk... 2340 15th Street??? I live at 2346!! Hey, we're neighbors! Yup, used to live there around 2 years back. Had friends that lived at 2348 (the "O-den"). Isn't the circularity of the world suprising? -- Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup