no floppy dir in /media ?

[Larry tb]

I made a mistake :-/
I wrote that
 >>I often work at shell,
 >>and so... Here is my problem :

I write "shell" for "text-mode" :-[

 From text-mode, you are okay that user have to create a dir to mount 
his /dev/fd0, 'cause there is no graphical way :
Have a look at this :
[ i am within TEST-MODE only ! ]

[root at ws044 ~]# gnome-mount -d /dev/fd0
gnome-mount 0.4
X display not available - using text-based operation.
Mounted /dev/fd0 at "/media/floppy"
[root at ws044 ~]# gnome-umount -d /dev/fd0
gnome-mount 0.4
X display not available - using text-based operation.
Unmounted /dev/fd0.
[root at ws044 ~]#


[root at ws044 ~]# mount /dev/fd0 /media/floppy
mount: mount point /media/floppy does not exist
[root at ws044 ~]#

So it seems that gnome-mount cant work because there is no graphical 
mode (of course !) but mounted works succefully .

In this condition, that great :)

larry


Michal Jaegermann wrote:
> On Mon, Mar 13, 2006 at 08:50:24AM +0100, Larry tb wrote:
> 
>>The problem i had, was to guess this new command. I often work at shell, 
>>and so... Here is my problem :
>>root at ws044 ~]# mount /dev/fd0 /media/floppy
>>mount: mount point /media/floppy does not exist
>>[root at ws044 ~]#
>>
>>Of course the possibility/necessity is to create a /media/floppy, or 
>>even /mnt/floppy. BUT within fc4 it was auto created during installation.
> 
> 
> There is no /media/floppy because 'gnome-mount/gnome-umount' creates
> and deletes these mount points and if you happen to have
> /media/floppy, regardless if currently in use or not, then it will
> be _not_ reused and /media/floppy-1, and if the last one is stuck
> for whatever reason then /media/floppy-2 will show up and so on.
> 
> I do not like very much that design as, among other things, it is
> obviously lacking in robustnes.  If anything goes wrong you are
> ending up with a mess in /media/ which only root can clean up even
> if non-root processes were responsible for it.  This is the next
> thing which requires "special handling" if you try to have /
> read-only.  Old user habits and lessons learned were not taken in a
> consideration too.  Moreover you have to substitute your best guess
> for a documentation.  But at the moment things are like they are.
> 
>    Mcihal
>