Xref: utzoo comp.unix.questions:12287 comp.unix.wizards:15105
Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!mailrus!purdue!bu-cs!buengc!bph
From: bph@buengc.BU.EDU (Blair P. Houghton)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: Future at Berzerkeley
Message-ID: <2344@buengc.BU.EDU>
Date: 19 Mar 89 04:52:00 GMT
References: <15184@cup.portal.com> <15407@cup.portal.com> <16230@mimsy.UUCP> <21216@agate.BERKELEY.EDU> <13324@steinmetz.ge.com> <28819@bu-cs.BU.EDU>
Reply-To: bph@buengc.bu.edu (Blair P. Houghton)
Followup-To: comp.unix.questions
Organization: Boston Univ. Col. of Eng.
Lines: 28

In article <28819@bu-cs.BU.EDU> bzs@bu-cs.BU.EDU (Barry Shein) writes:
>
>4. Is the Unix file system, unenhanced, the right view for personal
>workstations with a few GB of disk? I would claim that the MacOS file
>system view has collapsed as an abstraction with the popularity of
>300MB or larger disks, as cute as it was with a few files. Is there a
>similar threshold for the Unix system? It's 10PM, do you know where
>your sources are?

Well put.  I'd just like to clarify my misgivings about the simple-tree
directory system:  it's too hard to find what you put down when you
were drunk, or six weeks ago, or...well...

Some sort of cross-referencing, indexing, dewey-decimal systematization,
etc., would be exceptionally helpful.

Having a README in the directories that collect cryptically-named files
just doesn't cut it.  At the moment I'm personally responsible for
around three thousand files on the four largest machines I use (and
please don't ask how many bytes that is...there are some things better
left uninvestigated...:-S), few of them interrelated.  You'd think I would
have seen it coming.

Any good ideas?

				--Blair
				  "Better living through the sheer
				   weight of stored charge..."