Return to BSD News archive
Newsgroups: comp.os.linux.development.system,comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!news.gan.net.au!act.news.telstra.net!psgrain!news.uoregon.edu!europa.chnt.gtegsc.com!news.kreonet.re.kr!news.dacom.co.kr!newsrelay.netins.net!solaris.cc.vt.edu!newsfeed.internetmci.com!howland.reston.ans.net!ix.netcom.com!netcom.com!kalessin From: Adam Megacz <kalessin@netcom.com> Subject: Re: Ideal filesystem Content-Type: text/plain; charset=us-ascii Message-ID: <314E1023.2A7C1004@netcom.com> Sender: kalessin@netcom5.netcom.com Content-Transfer-Encoding: 7bit Organization: NETCOM On-line Communication Services (408 261-4700 guest) References: <4gejrb$ogj@floyd.sw.oz.au> <3140C968.20699696@netcom.com> <4ia7im$i4m@usenet.srv.cis.pitt.edu> <4if9gb$4kh@park.uvsc.edu> <4iibd2$ng@EARTH.baylor.edu> Mime-Version: 1.0 Date: Tue, 19 Mar 1996 01:38:43 GMT X-Mailer: Mozilla 2.0 (X11; I; Linux 1.2.13 i486) Lines: 57 Xref: euryale.cc.adfa.oz.au comp.os.linux.development.system:19620 comp.unix.bsd.freebsd.misc:15637 Pyramids-R-Us wrote: > >1) Application icon information > I gave up on using icons.... Because your system didn't have EA's. > >2) Desktop position information for an icon > This is not good for a multi-user environment. No two users will want > icons in the same place. In that case, only the owner could set icon location. When a user brings up a folder containing a file he owns, it goes in the proper place. If he doesn't own it, it would be aligned in a grid with the other icons (NOT put in the place that the owner chooses). This soloution is still better than whatever hacks are used on systems without EA's. > >5) Name/location attribution so that they don't end up as > > an inode number in lost and found: with full referential > > integrity, fsck can put the files back where they belong. > To do this right would mean altering this data whenever a user did a > 'ln', even when that user does not own the file Yeah - I don't like this particular feature - it should be implemented in the FS, not in the EA's. > >7) Creator application information, so that a document can > > "know" the application needed to access it, and a desktop > > reference to it will cause the *right* application to be > > invoked, with the document as an argument (what Windows > > 95 laugahably does using file extensions). > > Problem A: What would be stored? Surely something better than the > four letter codes used on the Mac. How would you tell the difference > between the system copy of 'foo' and the new version of foo that I put > in my home directory Do it the way OS/2 does it. A master associations table, and a private associations table in each user's home directory that can override the master (so the user can specify that his personal copy of foo be used). > Problem B: What is the *right* application in the first place? I > unix there is often a speration between the program used to modify a > file and the program used to view/act on the file. If I double click > on a man file should I get the editor used to create it or wil I get > the man page viewer. Again, do it the way OS/2 does it. Multiple file associations. When you double click, you view the man page. When you right click, you get a menu of all the applications (emacs, groff, man, xman) associated with the file type. Thanks to whoever posted the origional list of reasons for EA's! They're great ideas! -- Adam Megacz <kalessin@netcom.com> Website ftp://ftp.netcom.com/pub/ka/kalessin/adam.html Linux - OS/2