public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: "Bernhard R. Link" <brl@pcpool00.mathematik.uni-freiburg.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Olivier Galibert <galibert@pobox.com>
Subject: Re: File type by extension is evil (was Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time)
Date: Tue, 10 Jan 2006 15:28:07 -0500	[thread overview]
Message-ID: <1136924888.2007.81.camel@mindpipe> (raw)
In-Reply-To: <20060110103259.GA9285@pcpool00.mathematik.uni-freiburg.de>

On Tue, 2006-01-10 at 11:32 +0100, Bernhard R. Link wrote:
> * Olivier Galibert <galibert@pobox.com> [060109 19:44]:
> > >From what I can see it does icons on non-executable entirely based on
> > the extension and nothing else on the first pass.
> > 
> > Not a bad strategy, too.  Doing a file(1) on everything can only be
> > slow given the random disk accesses it generates.  Maybe a file(1) as
> > a _second_ pass would work.
> 
> That may be a good strategy if you have user conditioned to all the
> effects you get by this (i.e. if you only focus on Windows users and
> want them provide with a system as broken as they know it) and programs
> adopted to cope with the most ill effects (ever asked why some browsers
> always foozle the name of downloaded files with some .html or the like?)
> 
> For everyone else looking at the file is the only sane way to know the type
> of file.

OK so it's prohibitively expensive to get the file type so this is not
something Nautilus should be doing to every file before even starting to
display the icons.

Lee


  reply	other threads:[~2006-01-10 20:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5t06S-7nB-15@gated-at.bofh.it>
     [not found] ` <5t34G-3Zu-21@gated-at.bofh.it>
     [not found]   ` <5t5pU-7tD-37@gated-at.bofh.it>
     [not found]     ` <5t5JU-7Sn-11@gated-at.bofh.it>
2006-01-09 14:18       ` Why the DOS has many ntfs read and write driver,but the linux can't for a long time Robert Hancock
2006-01-09 14:28         ` Oliver Neukum
2006-01-09 15:15           ` Lee Revell
2006-01-09 16:02             ` Oliver Neukum
2006-01-09 16:04               ` Lee Revell
2006-01-09 16:14                 ` Oliver Neukum
2006-01-09 16:19                   ` Lee Revell
2006-01-09 16:29                     ` Bernd Petrovitsch
2006-01-09 16:41                       ` Lee Revell
2006-01-09 16:53                         ` Oliver Neukum
2006-01-09 16:56                           ` Lee Revell
2006-01-09 17:14                           ` Olivier Galibert
2006-01-09 17:28                             ` Lee Revell
2006-01-09 19:35                               ` Anton Altaparmakov
2006-01-10 10:32                             ` File type by extension is evil (was Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time) Bernhard R. Link
2006-01-10 20:28                               ` Lee Revell [this message]
2006-01-09 17:14                           ` Why the DOS has many ntfs read and write driver,but the linux can't for a long time Bernd Petrovitsch
2006-01-09 17:31                           ` Alan Cox
2006-01-09 16:45                             ` Jeff V. Merkey
2006-01-09 17:33                             ` Lee Revell
2006-01-09 18:11                               ` Marcin Dalecki
2006-01-09 17:45                             ` Oliver Neukum
2006-01-09 16:59                         ` Bernd Petrovitsch
2006-01-10  1:44                         ` Alistair John Strachan
2006-01-10  4:30                           ` Lee Revell
2006-01-10 10:13                             ` Jakob Oestergaard
2006-01-10 10:34                               ` Jesper Juhl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1136924888.2007.81.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=brl@pcpool00.mathematik.uni-freiburg.de \
    --cc=galibert@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox