20 Nov
2024
20 Nov
'24
7:26 a.m.
ср, 20 нояб. 2024 г., 09:21 Roman Savochenko via tde-users <
users(a)trinitydesktop.org>gt;:
On Sereda 20 Lystopad 7532 01:43:47 deloptes via
tde-users wrote:
In this case, I hope just one additional checkbox "prefer udisk(2) over
fstab" will cover this use case?
Roman Savochenko via tde-users wrote:
not
I know that.
Well, I don't know. I
would just use the default options. I would also use /media, because media is used by the system
to automatically mount
devices (I guess it is true for udisks2).
There is no problem with options here, since they are accepted correctly,
there is a problem with
missing options to control user of the mounted disk folder. And that
missing is not the problem
also of tdestoragedevice.cpp in processing the mounting options, due to
udisks doesn't allow
neither user, owner, uid or mask options.
My understanding of your problem is that you
create an entry in fstab and
use udisks in the same time. The entry in fstab causes TDE to read this
entry and omit udisks. Udisks does not need an entry in fstab anyway. So
it
looks to me TDE has the correct precedence and
this must be right.
udisks can use /etc/fstab options to customize own behaviour and that is a
single solution for FD
without fixing udisks itself. And most solutions in Internet about
treating that behaviour of
udisks mean same appending an entry for FD to /etc/fstab, and TDE here
tricks you starting use
mount directly!
udisks2 also can use /etc/fstab, and mediamanager.cpp wrongly overrides
this feature!!!
Regards, Roman
____________________________________________________
tde-users mailing list -- users(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt…