Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!lll-lcc!pyramid!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: <6278@cbmvax.UUCP> Date: 15 Mar 89 04:00:05 GMT References: <6157@cbmvax.UUCP> <6185@cbmvax.UUCP> <6237@cbmvax.UUCP> <1292@dukeac.UUCP> Reply-To: jesup@cbmvax.UUCP (Randell Jesup) Distribution: comp Organization: Commodore Technology, West Chester, PA Lines: 43 In article <1292@dukeac.UUCP> rsb@dukeac.UUCP (R. Scott Bartlett) writes: >In article <6237@cbmvax.UUCP> jesup@cbmvax.UUCP (Randell Jesup) writes: >> Agreed, it is too few. This may change. > >What about setting the CLI proc number to 0? Will some cli things choke on >this? Lattice's forkv() uses proc number 0. (What do workbench programs do?) Not normally a good idea. It removes the ability to Break the program, or to have Status return anything reasonable. Isn't really too dangerous, though. >Let me know how you want to eliminate the BCPL stuff. I plan on writing a ROOT: >to allow other filesystems to be mounted onto it. It would be a great place to >eliminate some BCPL garbage (or at least hide it from those that are in the >know). Talk to Bill Hawes. He wrote a PATH: that does similar sorts of things. Warning: packet-forwarding can get tricky. >> I've seen it done. Check the arp programmers docs. > >Please use the magic number. I think using the file protection bits is a BIG >kludge. If we go ahead and implement magic numbers, programs that depend on >the MMU for different memory setups, etc. can be identified and dealt with >accordingly. For instance programs that are very time sensitive can be labled Well, I don't really approve too much of magic number headers. This really is exactly waht the "protection" bits were designed for. There are even 16 user-defined bits you could use. >with a noswap attribute (are you happy Peter? :-). And things that depend on >having an 881 around can be identified at load time and the user can be informed >about the problem instead of having the machine go through an F-line trap or >whatever. (this can go on to include 020's and 030's...040's 050's :-) Bad example, it's trivial for the program to check execbase for 68881/2. We don't use traps for non-881 systems. If you want to work regardless of '881 or not, use the math libraries. They will automatically take advantage of the '881 if it's there. Far faster than traps, not as fast as in-line '881, but works on all amigas without modification. -- Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup