Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!husc6!talcott!ci-dandelion!ulowell!page
From: page@ulowell.UUCP (Bob Page)
Newsgroups: net.micro.amiga
Subject: Re: cd bug
Message-ID: <331@ulowell.UUCP>
Date: Mon, 12-May-86 18:26:08 EDT
Article-I.D.: ulowell.331
Posted: Mon May 12 18:26:08 1986
Date-Received: Wed, 14-May-86 20:59:00 EDT
References: <13147@ucla-cs.ARPA>
Reply-To: page@ulowell.UUCP (Bob Page)
Distribution: net
Organization: University of Lowell
Lines: 76

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!

>
>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.

>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.

>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.

>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!

> 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?

>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.

>And PARSE the input line to see what files you have.

What does that mean?


..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