[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    RE: Bug#2469: KFM allows 'umount'ing a fs which it is in
From:       David Faure <David.Faure () cramersystems ! com>
Date:       2000-01-07 13:34:23
[Download RAW message or body]

Even more, I often keep a kfm(konqueror) window open on /mnt/floppy, 
unmount the floppy, put another one, mount it (with RMB) and press F5.

I wouldn't want this to be turned into an error message telling me I have
to close the window first.

Closing the bug, it seems we agreed it's not really one.

--
David Faure
faure@kde.org - KDE developer
david@mandrakesoft.com - Mandrake
david.faure@cramersystems.com - Cramer Systems



> -----Original Message-----
> From: Rob Cronan [mailto:cronan@m-psi.com]
> Sent: Thursday, January 06, 2000 7:13 PM
> To: David Faure; 'Dawit Alemayehu'; '2469@bugs.kde.org'
> Subject: RE: Bug#2469: KFM allows 'umount'ing a fs which it is in
> 
> 
> I'm sorry, I did not see the list of addresses on Dawit's 
> original message.
>  I'm appending my reply here.  Sounds like a little 
> discussion about to
> occur on this subject.  Included are 1) what response is 
> appropriate and 2)
> consistency between 'like' actions regardless of user preference for
> executing them.
> 
> David, I do agree with you about the philosophy of doing what the user
> wants (within reason and maybe with warning messages where necessary).
> This brings up another subject dear to me:  The necessity (or 
> default) to
> be root to perform so many system functionalities.  I am very 
> interested in
> bringing Linux to the desktop user and the home user in a 
> standalone mode.
> The root requirement is a hinderance (IMHO) to this scenario 
> today.  I hope
> to discuss this subject at great lengths with many in the 
> Linux community.
> 
> Keep up the great work!
> 
> Regards,
> 
> Rob Cronan
> 
> 
> *************************  My reply to Dawit  
> *******************************
> Hi Dawit,
> 
> I reported this as much because I saw a discrepancy between 
> two different
> modes of operation that seemed to me should give the same result and I
> wanted to report it to find let someone more knowledgable 
> know and help
> determine whether it's a bug or not.  So, here goes a little more
> explanation and my thoughts
> 
> Examine the case where you have 2 terminals.  In one, you 
> mount a floppy
> with 'mount /dev/fd0'.  In the other you cd to /mnt/floppy and do a
> directory listing.  You hear the floppy energize and you get 
> the correct
> floppy contents listed.  Now go back to the first terminal and try to
> 'umount /dev/fd0'.  I get an error message about the device 
> being busy and
> no umount action is taken.  This seems to be good behavior since you
> wouldn't want to detach something from the fs that is still in use.
> 
> Now, examine the case where you have a terminal and KFM in 
> use.  Start with
> a clean slate (i.e. unmounted floppy).  In the terminal you 
> perform the
> same mount as above.  Now in KFM you ask it to navigate to 
> and list the
> contents of /mnt/floppy.  It does so correctly.  Now KFM is 
> (as I see it)
> essentially 'cd'ed to /mnt/floppy and as such, it seems that 
> it should have
> the floppy fs in a busy state.  However, when you now go back to the
> terminal and perform the same umount as above, you get no 
> errors and umount
> successfully unmounts the fs.
> 
> This seemed odd to me.  I would think that you'd want KFM or any gui
> interface to work similarly to the terminal operation when it 
> is doing like
> things.  Would you agree?  If not, let me know where my logic 
> is wrong.
> 
> As far as KFM telling the mount utility that it is in any 
> particular mount
> point, I'm not sure how that works yet.  However it does work 
> somehow with
> the 2 terminal scenario.  I'm guessing then, that there's a 
> way for KFM to
> have the same effect.
> 
> I enjoy this kind of effort greatly and am working towards 
> getting more and
> more involved with the Linux efforts.  So I'm definitely interested in
> making Linux the best so that it is a viable, and pervasive 
> OS.  Sell short
> Microsoft stock!
> 
> Regards,
> 
> Rob Cronan
> 
> 
> 
> 
> At 09:05 AM 01/06/2000 -0000, David Faure wrote:
> >Dawit, I think you misunderstood the problem.
> >
> >As he says, if you use 'cd' it "locks" the partition and prevents
> >from unmounting. BUT if you use kfm to navigate into the cd, 
> it doesn't
> >lock the partition.
> >
> >I'm not sure it should, though. Unmounting (even with the 
> icon) shouldn't
> >fail even if there is a window open, IMO. The user asked for 
> unmount, give
> >him unmount.
> >Why forbid it ?
> >
> >--
> >David Faure
> >faure@kde.org - KDE developer
> >david@mandrakesoft.com - Mandrake
> >david.faure@cramersystems.com - Cramer Systems
> >
> >
> >
> >> -----Original Message-----
> >> From: Dawit Alemayehu [mailto:adawit@earthlink.net]
> >> Sent: Thursday, January 06, 2000 4:53 AM
> >> To: Rob Cronan; 2469@bugs.kde.org
> >> Subject: Bug#2469: KFM allows 'umount'ing a fs which it is in
> >> 
> >> 
> >> On Wed, 05 Jan 2000, Rob Cronan wrote:
> >> > Package: KFM
> >> > Version: 1.167.2.11
> >> > 
> >> >   Mount a floppy or cdrom from a terminal.  Open a KFM 
> >> session and navigate
> >> > to either one (/mnt/floppy or /mnt/cdrom in my case).  KFM 
> >> displays the
> >> > contents of the fs.  While still in this directory, a 
> >> command in a terminal
> >> > to 'umount' the fs which KFM is in, completes successfully. 
> >>  KFM should
> >> > operate in such a way that the umount command fails in the 
> >> same way that it
> >> > fails when a 'cd /mnt/...' in a terminal window would cause 
> >> it to fail.
> >> 
> >> Hmmm... I did not completely understand the problem here.  
> >> Are you stating that
> >> (un)mounting devices to local directories while kfm is  
> >> currently showing those
> >> directories is wrong as is the case in a terminal/console ??? 
> >>  If so, consider
> >> this.  The mount points are nothing special.  They are just regular
> >> files or directories if you will.  So kfm and the shell can 
> >> navigate to these
> >> points without them being mounted in the first place.  Now 
> >> try the following: 
> >> cd into /mnt/cdrom or /mnt/floppy in a terminal and mount it. 
> >>  Then attempt to
> >> display its content with ls.  What do you get ??  Garbage.  
> >> It tells you the
> >> files that should be present are not while listing their 
> >> names correctly.  You
> >> have to cd out and back again to get it to display correctly. 
> >>  In kfm, if you
> >> mount and umount from the console, you would need to refresh 
> >> the display by
> >> pressing F5.  However, if you mount/umount from a device lnk 
> >> in your desktop it
> >> will be automatically updated.  So I fail to see how kfm's 
> >> handling is a bug
> >> while the terminal's is not ??  Moreover, how is kfm supposed 
> >> to tell the mount
> >> utility that it is in the mount point ?
> >> 
> >> >   In my system, I have "users" priveledge to mount and 
> >> unmount the floppy
> >> > and cdrom.  In the scenario that I described above, I was 
> >> executing the
> >> > steps as a user and not as root.
> >> 
> >> This has nothing to do with kfm.  Your priviledges are set in 
> >> /etc/fstab. 
> >> Perhaps I am mis-understanding what you are saying ... ?  
> >> Please elaborate
> >> where the problem is in this case ???  
> >> 
> >> Regards,
> >> Dawit A.
> >> 
> >> 
> >
> >
> 

[prev in list] [next in list] [prev in thread] [next in thread]