Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!bionet!csd4.milw.wisc.edu!leah!rpi!batcomputer!cornell!rochester!pt.cs.cmu.edu!andrew.cmu.edu!bader+ From: bader+@andrew.cmu.edu (Miles Bader) Newsgroups: comp.sys.amiga Subject: Re: arp CD command change??? Message-ID: Date: 14 Feb 89 21:01:31 GMT References: <8902131846.AA21527@postgres.Berkeley.EDU>, <35960@bbn.COM> Organization: Information Technology Center, Carnegie Mellon, Pittsburgh, PA Lines: 25 In-Reply-To: <35960@bbn.COM> cosell@bbn.com (Bernie Cosell) writes: > The UNIX 'wildcard standard' is > just plain cretinous. You might ask why UNIX files follow an > unbelivably cramped and unnatural 'extension' scheme . The primary > answer is that because of the DUMB wildcard facility, you could not > easily pick up all of the object files if the extension was a > reasonable ".REL", or check out all the libraries if they were ".LIB" > (whereas "*.o" and "*.a" _does_ work). It is a *real* loser that UNIX > doesn't support full regular expressions in its filename matching. What on earth do the extensions used for object (of COURSE, .rel stands for "object!") and archive files have to do with wildcards? *.rel and *.lib work just the same as *.o & *.a. > If you wanted *my* wish for the 1.4 filesystem, I'd really like both hard- > and sym-links. In fact, that mostly would make the '..' problem go away: you > could just do "link -s / .." in any directory you care about (or make > 'makedir' be an alias to do that for you automatically, which is **ALL** that > unix does. '.' and '..' are ***NOT*** built inot the kernel!! --- with a bit > of hackery, you can *remove* the '..' entry from a directory and everything > works just fine, except that .. out of THAT directory doesn't!). Definitely. Symlinks for 1.4 (pretty please...)! -Miles