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: RFC: Amigix Message-ID: Date: 30 Mar 89 09:58:31 GMT References: <6405@cbmvax.UUCP> Sender: usenet@rpi.edu Reply-To: shadow@pawl.rpi.edu (Deven T. Corzine) Organization: RPI Public Access Workstation Lab, Troy NY Lines: 46 In-reply-to: jesup@cbmvax.UUCP's message of 28 Mar 89 19:10:52 GMT In article <6405@cbmvax.UUCP> jesup@cbmvax.UUCP (Randell Jesup) writes: >In article shadow@pawl.rpi.edu (Deven T. Corzine) writes: >>For the shell *I* write, I fully intend to implement Unix-style >>wildcards (with some extensions I have in mind) AND Unix-style >>pathnames. (i.e. open("../file",...) would be internally translated >>to an AmigaDOS Open("/file",...) call, while "/file" would be >>translated to ":file", etc.) > How are you going to deal with device and volume names? A fair question. Undecided. Possibly I will stick to the device:path approach, though contrary to the general scheme of Unix. I suppose I COULD implement it as /dev/device/path, but that seems rather contrived and awkward, so... Of course, there is the point that Unix is NOT well suited for a floppy disk-based environment... allowances must be made. (along with changes. I see things in Unix to be improved upon.) >>The AmigaDOS CLI is a shell. A pathetically simple and poorly >>designed shell, but it IS a shell. And it is ALWAYS in memory, using >>that space. However, ALL the CLI's in the system use the SAME code >>for their CLI, so the overhead isn't so great; probably on the order >>of 10K + 1K/CLI or so... > CLI is MUCH smaller than 10K, AND it's in ROM. Good. It would be a sad commentary on someone if it were as large as 10K for what little it does. A more realistic estimate is maybe 1-2K, depending mostly on the overhead of BCPL... [but of COURSE it's in ROM... :-)] BTW, why is it that C:Execute is 8K [or so] simply to execute a command file, when the code is clearly in ROM or in the boot code of AmigaDOS to begin with, for S:Startup-Sequence behaves no differently from any other execute file... except that it does not require C:Execute to exist... [well, I suppose .key type stuff may not be supported [or logical] for the startup-sequence, but the point remains...] 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.