Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ig!bionet!csd4.milw.wisc.edu!indri!nic.MR.NET!umn-cs!uf!brant From: brant@uf.msc.umn.edu (Gary Brant) Newsgroups: comp.sys.amiga.tech Subject: Re: RFC: Amigix Message-ID: <11844@umn-cs.CS.UMN.EDU> Date: 1 Apr 89 00:07:41 GMT References: <6405@cbmvax.UUCP> Sender: news@umn-cs.CS.UMN.EDU Reply-To: brant@uf.msc.umn.edu (Gary Brant) Organization: Minnesota Supercomputer Center, Inc. Lines: 42 In article shadow@pawl.rpi.edu (Deven T. Corzine) writes: +In article <6405@cbmvax.UUCP> jesup@cbmvax.UUCP (Randell Jesup) writes: + +> 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.) Just sticking my $0.02 in here; I think that your system would be much more useful if you stay compatible with the AmigaDOS file system, at least to the extent that they can coexist on the same disk/ partition. This way all files would be accessible from either system (an important consideration I think). I also think that AmigaDOS deals with named volumes better than *nix. Count me as another who would love to see V7 functionality on the Amiga & couldn't care less whether internally it is really *nix in the purist sense. + + +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. -Gary Brant ARPA: brant@uf.msc.umn.edu