--nextPart1405941.pU4XPffSSS
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Wilhelm Meier wrote:
>If the user plugs-in a device, the local hald on the thin-client sends
>messages to the dbus of the thin-client, which are not recognized (there
> is no session). Now, one could make the new device of the thin-client
> available on the terminalserver, for instance via network-block-device.
> In this case it would be useful to inform the session on the
> terminalserver of the new device for the session.

Then you need to have this:
1) the thin-client's HAL detect the new device
2) that HAL take action and notify the terminalserver of availability of=20
that device
3) terminalserver and thin-client connect the device via network block=20
device
4) terminalserver's HAL detects the new network block device
5) terminalserver's HAL informs ONLY the user session that there is a new=20
device.

>This would require that the kde-session, e.g., listens to the
> session-bus, which is actually not the case, afaik. But I will ask the
> kde-people for kde4.

No. It requires a lot more work in HAL before anything even arrives to the=
=20
mediamanager in KDE or any other high-level interface.

>The LTSP-people do something similar, but without using hal/dbus I
> think.

That's steps 2 and 3 that I listed above. It doesn't have to be D-BUS, but=
=20
it could.

=2D-=20
Thiago Jos=E9 Macieira - thiago.macieira AT trolltech.com
Trolltech ASA - Sandakerveien 116, NO-0402 Oslo, Norway

--nextPart1405941.pU4XPffSSS
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQBEkAeNM/XwBW70U1gRAhWWAJ4jq3L7S/DMF10bnjORiFNP6V5LJgCglTrk
i4xTdQZNchsUtObMSVn3n5g=
=fqep
-----END PGP SIGNATURE-----

--nextPart1405941.pU4XPffSSS--