20 Nov
2024
20 Nov
'24
12:59 p.m.
On Sereda 20 Lystopad 7532 13:42:20 Dr. Nikolaus Klepp via tde-users wrote:
Anno domini 2024 Wed, 20 Nov 12:40:33 +0200
Roman Savochenko via tde-users scripsit:
That is not about "manpower", the first, but about limiting udisks features and
without proper
informing in dialogues about used mounting parameters and mechanisms. And to add that, I
need up to
one hour, but prove that is a problem, it seems there will be one day and more.
The second, that is about positioning TDE as "with a primary goal of retaining the
function and form
of traditional desktop computers.", which means of the software working on
"traditional" HW where
this software appeared, but of course the "two standards way" brought KDE3 to
breaking such
possibility by cmake, tqtinterface and including new code with anchoring it to new
interfaces
without saving the old compatibility, so for Debian 7 the last is 14.0.10, for Debian 8 is
14.0.13,
for Debian 9 is 14.1.0. That is, for new versions we must start to throw out the old HW
also as for
MancurtoScoft (MS)! The authoritarian development conception-process causes to I am
patching this
only for myself (and my users), also as CD-RW icons, playing DVD in Kaffeine and so on,
after
breaking those by the "local authority".
And the third, the FDC controllers were still appeared on MB 2010 year old! :)
On Sereda 20 Lystopad 7532 09:26:14 Andrew
Randrianasulu wrote:
Investing manpower into a problem that may for some users exist on ancient
hardware is not a sane way to do when manpower is limited. If said users
think it's worth their time then they should just make the changes and
submit a patch. That said, I just found a single 3.5" floppy disk in the
stack of archived software - needless to say that the last floppy drive
left over 20 jears ago. So if anybody needs it for the ancient floppy
drives just drop me note. ср, 20 нояб. 2024 г., 09:21 Roman Savochenko via
tde-users <
users(a)trinitydesktop.org>gt;:
I think for that just can be used the present CheckBox "Use default mount
option", which means as force using udisks at TRUE, with this default
parameters in /etc/fstab at presence, and use custom parameters from that
dialogue at FALSE. Also with overriding by direct mount at an entry
presence, with hidding the dialogue parameters as nonsenses and/or
writing here about taking from /etc/fstab by mount. On Sereda 20 Lystopad 7532 01:43:47 deloptes via
tde-users wrote:
> Roman Savochenko via tde-users wrote:
> > I know that.
>
> Well, I don't know. I would just use the default options. I would
> also
not
> 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!!!
In this case, I hope just one additional checkbox "prefer udisk(2) over
fstab" will cover this use case?