trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: September 2012

Re: [trinity-devel] TDEHW Summary

From: Darrell Anderson <humanreadable@...>
Date: Sun, 2 Sep 2012 10:28:00 -0700 (PDT)
> Patched in GIT hash b18416d.

I'll test.

> > Missing features:
> >
> > Generic Mount Options:
> >   Quiet
> > Filesystem Specific Mount Options:
> >   Flushed IO
> >   Mount as user
> >   Short names
>
> Unfortunately those options are disabled on purpose due to
> limitations in pmount.  Reading the man page (http://pwet.fr/man/linux/commandes/pmount)
> for pmount reveals no way to set those options; if someone
> bugs the upstream pmount project and they make those options
> available, those options can be reenabled in TDE with a few lines of code.

What do users lose with those missing options?

How about having TDEHW migrate those settings to the new mediamanagerrc groups and gray/ghost the options in the dialog? That way users would see that the settings were migrated but not supported under TDEHW.

More TDEHW related information:

I see the following messages in my xsession log:

=================================================
trying to create local folder /opt/trinity/share/config/tdehw: Permission denied

TQSocketNotifier: Invalid socket specified
TQSocketNotifier: Internal error
TQSocketNotifier: Invalid socket specified
TQSocketNotifier: Internal error

[FIXME] UNCLASSIFIED DEVICE name: i2c-2 type: (null) subsystem: i2c-dev driver: (null) [Node Path: /dev/i2c-2] [Syspath: /sys/devices/pci0000:00/0000:00:03.0/0000:01:00.0/i2c-2/i2c-dev/i2c-2] [14f1:8852]

[FIXME] UNCLASSIFIED DEVICE name: i2c-3 type: (null) subsystem: i2c-dev driver: (null) [Node Path: /dev/i2c-3] [Syspath: /sys/devices/pci0000:00/0000:00:03.0/0000:01:00.0/i2c-3/i2c-dev/i2c-3] [14f1:8852]

[FIXME] UNCLASSIFIED DEVICE name: i2c-4 type: (null) subsystem: i2c-dev driver: (null) [Node Path: /dev/i2c-4] [Syspath: /sys/devices/pci0000:00/0000:00:03.0/0000:01:00.0/i2c-4/i2c-dev/i2c-4] [14f1:8852]

[FIXME] UNCLASSIFIED DEVICE name: i2c-5 type: (null) subsystem: i2c-dev driver: (null) [Node Path: /dev/i2c-5] [Syspath: /sys/devices/pci0000:00/0000:00:05.0/i2c-5/i2c-dev/i2c-5] [10de:0240]

[FIXME] UNCLASSIFIED DEVICE name: i2c-6 type: (null) subsystem: i2c-dev driver: (null) [Node Path: /dev/i2c-6] [Syspath: /sys/devices/pci0000:00/0000:00:05.0/i2c-6/i2c-dev/i2c-6] [10de:0240]

[FIXME] UNCLASSIFIED DEVICE name: i2c-0 type: (null) subsystem: i2c-dev driver: (null) [Node Path: /dev/i2c-0] [Syspath: /sys/devices/pci0000:00/0000:00:0a.1/i2c-0/i2c-dev/i2c-0] [10de:0264]

[FIXME] UNCLASSIFIED DEVICE name: i2c-1 type: (null) subsystem: i2c-dev driver: (null) [Node Path: /dev/i2c-1] [Syspath: /sys/devices/pci0000:00/0000:00:0a.1/i2c-1/i2c-dev/i2c-1] [10de:0264]
=================================================

The first message is self-explanatory. Yet seems TDEHW should be trying to create the file in $TDEHOME/share/config and not $TDEDIR/share/config. Curious, I started TDE as root in the hopes of seeing what this directory might look like. The directory is created through the kcontrol module, but there were no files in the directory after being created.

I don't know what the TQSocketNotifier messages are about, if related to TDEHW. If not related they probably should be investigated and resolved anyway.

I suspect the FIXME messages are on the TDEHW to-do list?


Darrell