From: David Masover <ninja@slaphack.com>
To: Hans Reiser <reiser@namesys.com>
Cc: David Dabbs <david@dabbs.net>, reiserfs-list@namesys.com
Subject: Re: Fibration questions
Date: Sun, 18 Jul 2004 23:23:32 -0500 [thread overview]
Message-ID: <40FB4CC4.80300@slaphack.com> (raw)
In-Reply-To: <40FA22A3.5060503@namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hans Reiser wrote:
[...]
| If FS naming was better designed, filenames would not have extensions.
| I prefer to first better design naming, and then not need to optimize
| the API for extensions.
Still, if we're going to fibrate by file type and want to find a file by
file type, there needs to be -- surprise! -- a standard way to determine
file type.
Extensions are universal, and aren't going away soon. What do we want
to replace them with? Only thing I particularly care about here is that
a file can appear as more than one type -- a script is both a program
and a text file, for example. Of course, you'd only be able to fibrate
by one type (right?), so there'd have to be a "primary" file type.
This is helpful because it's the right thing to do, but also because it
may have implications right now. For example, Gedit and AbiWord should
both show me uncompressed AbiWord docs in their "open" dialogs, by
default. Using file extensions, that isn't possible unless you hack
Gedit to "know" every possible text file extension, or check the magic
on each file in the directory.
The "propor" way to implement it would be to ask the filesystem
something like "List all the text files in this directory". And not,
btw, "List all the *.txt files in this directory".
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQPtMxHgHNmZLgCUhAQKJxA//R1jxJuQ+PerBlgXO0FeGawp/i6Fr0wEU
WnZBG81fX07fcp+BzZWWu0lFE6kOrrmY/nuyKNsV1GT54jz1BkYklCBxGGmgHjGs
GZW3FvHHVWEfKNNuYv9zUVEkgA3RhxbCiQ5v44IrHzBLOFFDGTaOaBtsSC/NJa5C
I95IitqXRDj3AYDgpdu+++absgH47mCzThEdXP++Sb8RQwGEgnaubEDJIWqi+qOu
K5Psgudnu7+QejTlNzU5WuoCAwCX3b2+Trk6qj1bOJk7CucaBtojlwvifLJpZzau
Mi5gBe8cddyderP9f1rDHovUCcRcd5x0If7ESFYwfmNZO/GakJI1MSzt9W6c5PWK
Elap3jaA8aHmPJ6gfN24+GFvEgM7LDM/zw9GpjJ41awcf4Y/m7n8AfRaGv1+Ybvm
B+JmWMexqk+O+phCNvI/lfOOnbOCcaIMihzw5LO/e+jpJkOTuMwozPWMaIy1OZBC
FRjvTv28uCcbTepjHRDw1xmdY3lQ7GuO53/li0DerIYiAC3+zlX1mg1/PV7kl85B
jWXh89OEQd6ak9W/DKJnxd3uFe5c3nue9yr6PzSdC+bqSaN3p/KWmlZxtkqKhxOM
E9QVgtsS9j5snwsf5d+viCZ1eEn3p8UYDZsVvvrqzwaC3opgXpYyQZ/YmnivLnJJ
EXadVtulIuU=
=67XN
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-07-19 4:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 10:35 Fibration questions David Dabbs
2004-07-16 11:04 ` Nikita Danilov
2004-07-16 17:45 ` David Dabbs
2004-07-18 7:11 ` Hans Reiser
2004-07-18 7:47 ` David Dabbs
2004-07-19 4:23 ` David Masover [this message]
2004-07-19 7:21 ` David Dabbs
2004-07-19 21:34 ` David Masover
2004-07-19 22:06 ` Valdis.Kletnieks
2004-07-19 22:32 ` David Dabbs
2004-07-20 6:03 ` Hans Reiser
2004-07-20 7:03 ` David Masover
2004-07-20 5:30 ` Hans Reiser
2004-07-20 7:07 ` David Masover
2004-07-20 8:31 ` David Dabbs
2004-07-21 5:13 ` David Masover
2004-07-21 5:44 ` David Dabbs
2004-07-21 6:20 ` David Masover
2004-07-21 6:36 ` David Dabbs
2004-07-21 8:32 ` mjt
2004-07-22 4:08 ` David Masover
2004-07-22 10:06 ` mjt
2004-07-22 18:14 ` Hans Reiser
2004-07-23 2:45 ` David Masover
2004-07-23 9:42 ` mjt
2004-07-23 18:21 ` David Masover
2004-07-22 10:10 ` Vitaly Fertman
2004-07-23 2:43 ` David Masover
2004-07-23 9:09 ` Vitaly Fertman
2004-07-26 6:28 ` Hans Reiser
2004-07-26 10:11 ` Vitaly Fertman
2004-07-23 9:59 ` Christian Mayrhuber
2004-07-23 9:59 ` mjt
2004-07-23 18:13 ` David Masover
2004-07-23 10:05 ` mjt
2004-07-22 8:03 ` Hans Reiser
2004-07-22 12:16 ` Nikita Danilov
2004-07-22 14:39 ` mjt
2004-07-22 18:17 ` Hans Reiser
2004-07-22 18:26 ` mjt
2004-07-22 19:57 ` Valdis.Kletnieks
2004-07-22 21:05 ` mjt
2004-07-22 21:36 ` Valdis.Kletnieks
2004-07-23 9:28 ` mjt
2004-07-23 22:42 ` Valdis.Kletnieks
2004-07-23 2:40 ` David Masover
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=40FB4CC4.80300@slaphack.com \
--to=ninja@slaphack.com \
--cc=david@dabbs.net \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.