public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: zhilla <zhilla@spymac.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Supermount
Date: Sun, 24 Jul 2005 22:05:08 +0200	[thread overview]
Message-ID: <42E3F474.90104@spymac.com> (raw)
In-Reply-To: <42E00DD3.9060407@trn.iki.fi>

well, for a bit of OT discussion sake, here's how it imho SHOULD work, 
from user (noobs and non guru) desktop point of view:
cd/dvds: mounted automatically on insert / first access. if a program is 
running from it (or a file is open from it), and user tries to eject it 
using button, or any eject-like software, kernel sends a signal to a 
central place. which is, for example, picked up from a window manager, 
or even X itself. which, in a friendly and non intrusive way, displays 
something like this: "drive hdc busy, please close the following 
processes first: 1. mplayer 2. blabla".
also, if a blank media is detected on access, it should not be mounted.
usb drives: similar. if user plugs it out without unmounting, its 
unmounted, and processes using files on it gracefully killed, or somehow 
"warned". how to "warn" them? ill let someonbe smarter think of the way 
:) and about ripping it out without closing, wm/anything should yell 
"bad user!! you should ALWAYS unmount first!"
floppys: i suggest leaving things 100% same. btw. i saw some distros 
having problem with accessing ie /mnt/floppy when there is no floppy 
present. bash goes wild with autocompletion. programs pause for a looong 
time. this could be a kernel bug.
other stuff: dont want to sound like troll, but i guess 98% of people 
dont use anything else.
system partitions: make a clear cut between folders which should be seen 
at all by anyone but root, kernel, special software. in other words: 
reduce clutter in / by hiding almost anything! and partition specific 
mount option such as
"userinvisiblefolder=/dev;/sys;/lib;/proc;/sys;/var"
should also be possible. face it, for regular user in varoius distros, / 
is to crowded.
i'm not saying this is all 100% correct or possible. couse this is, 
imho, greatest ugliness, user friendlyness and productivity reducer in 
linux. m$ has it a bit better in some ways, but crappier in other. any 
of these could be a killer feature for 2.8 kernel series. or 2.6.2x :)
i would like people to discuss this. be polite please :)

  parent reply	other threads:[~2005-07-24 20:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 21:04 Supermount Lasse Kärkkäinen / Tronic
2005-07-21 21:41 ` Supermount Francois Romieu
2005-07-21 21:50 ` Supermount ioGL64NX
2005-07-22 16:38   ` Supermount Lasse Kärkkäinen / Tronic
2005-07-23 10:47     ` Supermount Oliver Neukum
2005-07-23 17:35       ` Supermount Lasse Kärkkäinen / Tronic
2005-07-24  1:44         ` Supermount Ian Kent
2005-07-24  1:48       ` Supermount Ian Kent
2005-07-24 20:05 ` zhilla [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 13:41 supermount ismail donmez
2003-05-14 13:54 ` supermount Alan Cox
2003-05-14 13:40 supermount ismail donmez
2003-05-14 15:04 ` supermount Con Kolivas
2003-05-15  6:16   ` supermount ismail (cartman) donmez
2003-05-13 16:30 supermount Maciej Górnicki
2001-06-25 16:50 supermount Sam Halliday
2001-06-26  0:30 ` supermount Steve Kieu
2001-06-30  5:17   ` supermount John Silva
2001-06-25 16:44 supermount Sam Halliday
2001-07-07  1:43 ` supermount Dj_RzulF

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=42E3F474.90104@spymac.com \
    --to=zhilla@spymac.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