All,
I recently pushed a new (alpha quality) backend for the media:/ kioslave which uses udev/pmount and therefore does not rely on HAL. I encourage developers here to try it out!
Please report failures to this list, not to the bugtracker, as it has not been tested much beyond mounting simple flash drives. Encryption support is buggy, but repairing it is my next task.
Rhis will NOT be made default for R14.0 due to the vast array of hardware that it still needs to be tested on, but if your distribution no longer works with HAL it may be better than nothing even in this alpha form.
To enable it, pass the -DWITH_TDEHWLIB="on" option to tdebase CMake.
Enjoy!
Tim
I recently pushed a new (alpha quality) backend for the media:/ kioslave which uses udev/pmount and therefore does not rely on HAL. I encourage developers here to try it out!
Please report failures to this list, not to the bugtracker, as it has not been tested much beyond mounting simple flash drives. Encryption support is buggy, but repairing it is my next task.
Rhis will NOT be made default for R14.0 due to the vast array of hardware that it still needs to be tested on, but if your distribution no longer works with HAL it may be better than nothing even in this alpha form.
To enable it, pass the -DWITH_TDEHWLIB="on" option to tdebase CMake.
Enjoy!
Thanks for your hard work Tim. I know this is a big move and much needed.
Do you have a test plan to help us begin testing? Not to test the compiling but to test usability.
For systems that don't have hal the test probably is straightforward: Initiate device changes and verify the device icons and popup dialog appears.
What about those systems still supporting and installing hal? Do we temporarily disable the service? How does disabling hal interact with udev?
If we temporarily disable hal for testing, device recognition should work in TDE, but won't work outside that environment because no hal replacement mechanism yet exists. Does that affect testing in any manner?
If WITH_TDEHWLIB=ON, does that interfere with the hal/udev or work with those services?
Hence, the question about a test plan. A test plan will help us test methodically.
Darrell
I recently pushed a new (alpha quality) backend for the media:/ kioslave which uses udev/pmount and therefore does not rely on HAL. I encourage developers here to try it out!
Please report failures to this list, not to the bugtracker, as it has not been tested much beyond mounting simple flash drives. Encryption support is buggy, but repairing it is my next task.
Rhis will NOT be made default for R14.0 due to the vast array of hardware that it still needs to be tested on, but if your distribution no longer works with HAL it may be better than nothing even in this alpha form.
To enable it, pass the -DWITH_TDEHWLIB="on" option to tdebase CMake.
Enjoy!
Thanks for your hard work Tim. I know this is a big move and much needed.
Do you have a test plan to help us begin testing? Not to test the compiling but to test usability.
For systems that don't have hal the test probably is straightforward: Initiate device changes and verify the device icons and popup dialog appears.
What about those systems still supporting and installing hal? Do we temporarily disable the service? How does disabling hal interact with udev?
udev is always active. Compiling tdebase with the option I provided disables all media:/ kioslave ties to HAL, so no extra measures need to be taken to test the new backend.
If we temporarily disable hal for testing, device recognition should work in TDE, but won't work outside that environment because no hal replacement mechanism yet exists. Does that affect testing in any manner?
If WITH_TDEHWLIB=ON, does that interfere with the hal/udev or work with those services?
It works with udev, but disables the ability for the media:/ kioslave to use HAL.
Hence, the question about a test plan. A test plan will help us test methodically.
Sorry, I don't really have one--perhaps as the new backend approaches beta quality I can draft one up. If I forget feel free to remind me. :-)
Tim
On Mar 31, 2012, at 23:12, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
I recently pushed a new (alpha quality) backend for the media:/ kioslave which uses udev/pmount and therefore does not rely on HAL. I encourage developers here to try it out!
Please report failures to this list, not to the bugtracker, as it has not been tested much beyond mounting simple flash drives. Encryption support is buggy, but repairing it is my next task.
Rhis will NOT be made default for R14.0 due to the vast array of hardware that it still needs to be tested on, but if your distribution no longer works with HAL it may be better than nothing even in this alpha form.
To enable it, pass the -DWITH_TDEHWLIB="on" option to tdebase CMake.
Enjoy!
Thanks for your hard work Tim. I know this is a big move and much needed.
Do you have a test plan to help us begin testing? Not to test the compiling but to test usability.
For systems that don't have hal the test probably is straightforward: Initiate device changes and verify the device icons and popup dialog appears.
What about those systems still supporting and installing hal? Do we temporarily disable the service? How does disabling hal interact with udev?
udev is always active. Compiling tdebase with the option I provided disables all media:/ kioslave ties to HAL, so no extra measures need to be taken to test the new backend.
If we temporarily disable hal for testing, device recognition should work in TDE, but won't work outside that environment because no hal replacement mechanism yet exists. Does that affect testing in any manner?
If WITH_TDEHWLIB=ON, does that interfere with the hal/udev or work with those services?
It works with udev, but disables the ability for the media:/ kioslave to use HAL.
Hence, the question about a test plan. A test plan will help us test methodically.
Sorry, I don't really have one--perhaps as the new backend approaches beta quality I can draft one up. If I forget feel free to remind me. :-)
meeting_topics++;
-- later daze.
I recently pushed a new (alpha quality) backend for the media:/ kioslave which uses udev/pmount and therefore does not rely on HAL. I encourage developers here to try it out!
Tim, FYI:
While rebuilding tdebase for another reason, I forgot to set -DWITH_TDEHWLIB=OFF. The build failed with this:
In file included from /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:19: /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.h:37:32: error: tdehardwaredevices.h: No such file or directory In file included from /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:19: /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.h:85: error: 'TDEStorageDevice' has not been declared /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.h:92: error: 'TDEStorageDevice' has not been declared /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.h:99: error: 'TDEStorageDevice' has not been declared /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.h:102: error: 'TDEGenericDevice' has not been declared /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.h:103: error: 'TDEGenericDevice' has not been declared /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.h:104: error: 'TDEGenericDevice' has not been declared /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.h:119: error: 'TDEStorageDevice' has not been declared /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp: In constructor 'TDEBackend::TDEBackend(MediaList&, TQObject*)': /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:55: error: 'TDEHardwareDevices' was not declared in this scope /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:55: error: 'hwdevices' was not declared in this scope /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:55: error: 'hardwareDevices' is not a member of 'KGlobal' /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp: In destructor 'virtual TDEBackend::~TDEBackend()': /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:70: error: 'TDEHardwareDevices' was not declared in this scope /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:70: error: 'hwdevices' was not declared in this scope /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:70: error: 'hardwareDevices' is not a member of 'KGlobal' /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:71: error: 'TDEGenericHardwareList' was not declared in this scope /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:71: error: expected ';' before 'hwlist' /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:72: error: 'TDEGenericDevice' was not declared in this scope /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:72: error: 'hwdevice' was not declared in this scope /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:73: error: 'hwlist' was not declared in this scope /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:74: error: 'TDEGenericDeviceType' has not been declared /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:75: error: 'TDEStorageDevice' was not declared in this scope /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:75: error: 'sdevice' was not declared in this scope /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:75: error: expected type-specifier before 'TDEStorageDevice' /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:75: error: expected '>' before 'TDEStorageDevice' /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:75: error: expected '(' before 'TDEStorageDevice' /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:75: error: expected primary-expression before '>' token /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:75: error: expected ')' before ';' token /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp: At global scope: /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:81: error: variable or field 'AddDeviceHandler' declared void /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:81: error: 'TDEGenericDevice' was not declared in this scope /dev/shm/tdebase/kioslave/media/mediamanager/tdehardwarebackend.cpp:81: error: 'device' was not declared in this scope make[2]: *** [kioslave/media/mediamanager/CMakeFiles/kded_mediamanager-module.dir/tdehardwarebackend.cpp.o] Error 1
Darrell
I recently pushed a new (alpha quality) backend for the media:/ kioslave which uses udev/pmount and therefore does not rely on HAL. I encourage developers here to try it out!
Tim, FYI:
While rebuilding tdebase for another reason, I forgot to set -DWITH_TDEHWLIB=OFF. The build failed with this:
<snip>
I set the WITH_TDEHWLIB default setting to OFF in GIT hash ccc23cb; it should not have been enabled by default.
The build failure is probably related to the fact that the new backend relies on a rather large and new library in tdelibs--you would need to rebuild and reinstall tdelibs before the new backend will build in tdebase.
Tim
Timothy Pearson <kb9vqf@...> writes:
All,
I recently pushed a new (alpha quality) backend for the media:/ kioslave which uses udev/pmount and therefore does not rely on HAL. I encourage developers here to try it out!
Please report failures to this list, not to the bugtracker, as it has not been tested much beyond mounting simple flash drives. Encryption support is buggy, but repairing it is my next task.
Rhis will NOT be made default for R14.0 due to the vast array of hardware that it still needs to be tested on, but if your distribution no longer works with HAL it may be better than nothing even in this alpha form.
To enable it, pass the -DWITH_TDEHWLIB="on" option to tdebase CMake.
Enjoy!
Tim
I built Trinity without HAL and udev (165) seems to be working. tdebase would not build with udev-181. One bug is that all loop devices are showing up under kioslave media:/ which is bad for me since our distro is based on modules mounted on loopback. I have a rules file in: /etc/udev/rules.d/10-local.rules containing: KERNEL=="loop*", ENV{UDISKS_PRESENTATION_HIDE}="1"
but this makes no difference.
Jay
Timothy Pearson <kb9vqf@...> writes:
All,
I recently pushed a new (alpha quality) backend for the media:/ kioslave which uses udev/pmount and therefore does not rely on HAL. I encourage developers here to try it out!
Please report failures to this list, not to the bugtracker, as it has not been tested much beyond mounting simple flash drives. Encryption support is buggy, but repairing it is my next task.
Rhis will NOT be made default for R14.0 due to the vast array of hardware that it still needs to be tested on, but if your distribution no longer works with HAL it may be better than nothing even in this alpha form.
To enable it, pass the -DWITH_TDEHWLIB="on" option to tdebase CMake.
Enjoy!
Tim
I built Trinity without HAL and udev (165) seems to be working. tdebase would not build with udev-181. One bug is that all loop devices are showing up under kioslave media:/ which is bad for me since our distro is based on modules mounted on loopback. I have a rules file in: /etc/udev/rules.d/10-local.rules containing: KERNEL=="loop*", ENV{UDISKS_PRESENTATION_HIDE}="1"
but this makes no difference.
Jay
TDE does not parse udisks/udev configuration files, but you can override its device classifier through a currently undocumented mechanism which involves adding a distro-specific .hwclass file to ${DATA_INSTALL_DIR}/tdehwlib/deviceclasses.
The .hwclass files operate by matching all conditions in the [Conditions] section; if a match is found the device is classified according to the rules in the [DeviceType] section. Look at http://git.trinitydesktop.org/cgit/tdelibs/tree/tdecore/hwlibdata/classrules... for an example file which is used to classify floppy drives.
I have not tested this, but it should get you started:
hide-loop-devices.hwclass
[Conditions] SUBSYSTEM=block DRIVER=loop
[DeviceType] GENTYPE=System
Tim