Michele Calgaro via tde-users wrote:
So whether we follow fstab or let udisks handle the
device, in the end the
results should be the same, unless I miss something.
So we are again at square 1 :)
I did not have to read all of the documentation - very busy week. I read at
one place that it merges the fstab and the udsisks config and handles the
mounting.
But if this is so as you describe it, then there is something missing in the
whole picture.
I go back one step to the first post by Roman
> Access is controlled by udisks or from /etc/fstab!
:)
>
> And udisks directly mounts floppy only in RO.
>
Here obviously he did not take time to do proper udisks config for floppy
devices, which would obviously overwrite the default fstab ... or if it is
correct that the issue was in Debian7 it could be that this was older
version of udisks or something back then
> And when you write a record about floppy in
/etc/fstab, TDE uses direct
> mounting by call mount for it, and that is wrong work also for userspace.
>
It seems to me he is unhappy that floppy was mounting RO (I assume the issue
is here, because default entry in fstab created by debian or so or default
mount options for floppy somewhere in the linux distro). So he disables the
code in TDE, so that udisks can pick up and mount the floppy RW.
> Then I just disabled the direct mounting at a
record in /etc/fstab, so
> TDE is using udisks for that and udisks reads /etc/fstab and mounts RW
> in userspace correctly in this way.
I can just conclude that the problem was/is in the fstab mount options for
floppy for whatever reason. Thus TDE code is just fine and the claims made
by Roman incl. the hack-patch is invalid.
If my understanding is wrong, we have to organize a debugging session with
vanilla TDE to reproduce the problem.
Meanwhile Roman can build or install vanilla TDE without his patch and check
if the issue is still there. Roman, you can also provide some log
information if you play the cooperative game.
BR