From: Larry Garfield <lgarfiel@students.depaul.edu>
To: linux-kernel@vger.kernel.org, zaurus-general@lists.sourceforge.net
Subject: Re: [Zaurus-general] Re: New Zaurus Wishlist - removable media handling
Date: Wed, 26 Jun 2002 21:38:41 -0500 [thread overview]
Message-ID: <3D1A7AB1.D4955601@students.depaul.edu> (raw)
In-Reply-To: Pine.LNX.3.96.1020627032159.2332J-100000@pioneer
Tomasz Rola wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, 27 Jun 2002, David Golden wrote:
>
> >
> > > And Unix filesystems were NOT designed for removable media.
> >
> > (LKML cc'd because this rant *might* be coherent enough to explain it
> > to Linux kernel hackers)
> >
> > The main problem I have with the Linux filesystems is this:
<snippink>
> As a former Amiga user and now yet another Linux user, I probably know
> what you mean. Well, I'm not a kernel engineer but maybe it could be done
> with a virtual fs like /dev - so that
>
> 1. /dev/ is not polluted
> 2. /mnt and other real disk space is not polluted
Well, I am neither a former Amiga user nor a kernel developer (but
GNU/Linux user), so I understood MOST of what you two said. ;-) Coming
from a user-angle, though, the main problem with the Linux file system
"style", for lack of a better word, is the unified file tree.
What? The unified file tree? Yes, the unified file tree. The idea
that the silver plastic round thing you just put into the front of the
computer is accessed.... "under" the "storage" in the computer? Does
that, conceptually, metaphorically, make sense? No, it doesn't. Nor
does the need to explicitly "mount" and "umount" (the n having gotten
lost while moving from one office to another a few years back) a floppy
disk. This is one place where, I hate to say it, drive letters a la
DOS/Windows (or some other top-level identifier) are significantly
better from a user perspective.
--
Larry Garfield AIM: LOLG42
lgarfiel@students.depaul.edu ICQ: 6817012
-- "If at first you don't succeed, skydiving isn't for you." :-)
next prev parent reply other threads:[~2002-06-27 6:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D1A2DC1.6040401@travellingkiwi.com>
2002-06-27 0:19 ` New Zaurus Wishlist - removable media handling David Golden
2002-06-27 1:40 ` Tomasz Rola
2002-06-27 1:58 ` kernel: journal /ext3 problem. "Assertion failure" louie miranda
2002-06-27 2:18 ` New Zaurus Wishlist - removable media handling David D. Hagood
2002-06-27 8:11 ` Xavier Bestel
2002-06-27 11:29 ` David D. Hagood
2002-06-27 13:42 ` Tomasz Rola
2002-06-27 2:38 ` Larry Garfield [this message]
2002-06-27 17:26 ` [Zaurus-general] " Kent Sandvik
2002-06-27 17:36 ` Denis Vlasenko
2002-06-29 0:39 ` Horst von Brand
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=3D1A7AB1.D4955601@students.depaul.edu \
--to=lgarfiel@students.depaul.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=zaurus-general@lists.sourceforge.net \
/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