Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: unknown; site unknown
Path: utzoo!watmath!clyde!cbosgd!ukma!psuvm.bitnet!psuvax1!burdvax!sdcrdcf!ucla-cs!cc1
From: cc1@ucla-cs.ARPA (UCLA Computer Club)
Newsgroups: net.micro.amiga
Subject: Re: cd bug
Message-ID: <13863@ucla-cs.ARPA>
Date: Tue, 20-May-86 18:56:46 EDT
Article-I.D.: ucla-cs.13863
Posted: Tue May 20 18:56:46 1986
Date-Received: Fri, 23-May-86 08:22:36 EDT
References: <13147@ucla-cs.ARPA> <331@ulowell.UUCP>
Reply-To: occ4mgk@oac.ucla.edu, cc1@ucla-cs.UUCP (Michael Gersten)
Distribution: net
Organization: Ucla Computer Club (disclaimer)
Lines: 127

This requires a reply
|> me
| Bob Page

In article <331@ulowell.UUCP> page@ulowell.UUCP (Bob Page) writes:
|In article <13147@ucla-cs.ARPA> Michael Gersten writes:
|>cd df1:
|>cd dir1               # now in sub directory
|># switch disks, put 1 in 0, 0 in 1
|>cd /          # this should put you in df0:
|
|Huh?  Doesn't cd / mean 'go up one level?'  That would put you in
|df1:dir1 - dir1 = df1:
|
|>instead, it puts you in df1:
|
|Good!
|

Not good. I SWITCHED DISKS. Every reference except '/' refers to the disk
now in drive 0.
By the way, saying 'cd' prints the wrong directory in this case.

|>
|>Incidently, the current directory of the initial cli task is 'RDF0:',
|>that is, whatever disk happens to be in drive 0 at the time, not
|>sys:
|
|The current directory of the initial CLI task is INITIALLY df0:, since
|the CLI can't assume you have any other devices.  Well, and for other
|practical reasons.
|

NOT df0:, it IS rdf0:. If you switch disks, it happily changes directory
to the root of the new disk that you just put in. In other words, it
has NO current directory.


|>What I would like to see:
|>The ability to specify 'RDF0:' (or similar) to mean 'Disk in there when
|>you look' in other things as well. So, you could
|>assign c: rdf0:c
|
|NO!  This would create a lot of headaches with hashing and cacheing!
|Disk names are better than device names.  Think generics.  Also (and
|more importantly today, with the current CLI), the ASSIGN structure
|needs disk names, not device names.  Try to ASSIGN to a non-existant
|disk.  You can't, because ASSIGN asks the disk handler process to
|check & make sure it's there.
|

And why can't you assign to a non-online drive? That would be grate--put
them all in my startup-sequence. Remember, RDF0: is in there already, look
at the startup-cli

|>or
|>assign c: path rdf0:c rdf1:
|
|The PATH you want is coming, but you don't use ASSIGN.
|
|>and use whatever drives are on at the time.
|
|This defeats the purpose of MOUNTing disks!  What if you slapped out
|your VAX's Eagle and put in another, with radically different files on it?
|Keep in mind ADOS isn't a fancy program loader, like many of the other
|micro 'operating systems' in use.
|

I still don't understand this.


|>By the way, can 1.2 use 5" drives, or is that still only for the emulator?
|
|>Because of fixed #
|>of files, filename expansion is useless.
|
|You'd be better off complaining about Lattice C's arbitrary restriction
|of 32 arguments on a command line!
|

I wasn't aware of that. Uggh. But 32 is better than 2.

|> WORSE, if I wind up with 2
|>files, then because of the 'hidden to options' that 1/2 the commands have
|>I wind up destroying something.
|>PLEASE, get rid of all those 'TO' options.
|
|Sounds like a job for a more unified command line syntax.  Any takers?
|

Give me a copy of the source and I'll do it.


|>ADD the concept of a standard error output.
|
|Wow.  Sounds like a lot of work... and your asking the people who didn't
|even write the DOS.
|

I'll help.


|>And PARSE the input line to see what files you have.
|
|What does that mean?

It means: Don't assume that the you only have one source file, or that the
second file is the output. In otherwords,
A. I should be able to delete an arbitrary # of files
B. I should be able to type an arbitrary # of files into a destination
C. I should be able to copy an arbitrary # into a directory
etc.
Look at UNiX.

|
|
|..Bob
|--
|UUCP: wanginst!ulowell!page    Bob Page
|ARPA: page@ulowell.CSNET       U of Lowell CS Dept
|VOX:  +1 617 452 5000 x2233    Lowell MA 01854 USA

Michael Gersten
ihnp4!ucla-cs!cc1

--
Views expressed here may not be those of the Computer Club, UCLA, or anyone.