*BSD News Article 65465


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!harbinger.cc.monash.edu.au!news.cs.su.oz.au!inferno.mpx.com.au!news.mel.aone.net.au!imci4!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: <316C5D6B.73215CAB@netcom.com>
Sender: kalessin@netcom19.netcom.com
Content-Transfer-Encoding: 7bit
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
References: <4hptj4$cf4@cville-srv.wam.umd.edu> <3140C968.20699696@netcom.com> 	  <4ilgto$861@floyd.sw.oz.au> <4j6if4$15gk@news.missouri.edu> 	  <315834CD.7C4DA6C7@netcom.com> <4jc6q5$bgd@josie.abo.fi> 	  <315B0727.70172281@netcom.com> <4jnvb4$608@floyd.sw.oz.au> <31608939.342B2F46@netcom.com> <DpAGp3.3tD@pe1chl.ampr.org> <31631142.59EBBBEF@netcom.com> <DpJDE0.Iqq@white.schulung.netuse.de>
Mime-Version: 1.0
Date: Thu, 11 Apr 1996 01:16:27 GMT
X-Mailer: Mozilla 2.01 (X11; I; Linux 1.2.13 i486)
Lines: 22
Xref: euryale.cc.adfa.oz.au comp.os.linux.development.system:20962 comp.unix.bsd.freebsd.misc:16972

> This is how Nextstep does it. You can have the files .dir.tiff
> and .opendir.tiff in any directory Nextstep shows a default icon
> (an image of a folder) when the files are not present or the
> contents of the tiff images (scaled down to fit) if they are in
> place and readable.
> 
> The user must not use dotfiles of this specific name for other
> purposes. In practice, this is not a problem.

  1) This is a stupid restriction. Just like the old 640k memory 
     restriction in DOS/realmode.
  2) NeXT can do this since most NeXT apps are custom-made for NeXT,
     and they don't have to worry about compatibility (much). Linux
     must remain POSIX-compatible, and run POSIX apps (which don't
     know about the restriction on filenames not being ".dir.tiff")
  3) This restriction also compromises NeXTStep's UNIX/POSIX
     compatibility.

Admittedly, this works, but I would really like to see a better
soloution.