Hi there,
After some more research, I have realized that the L-Bus protocol
is very similar to what I need. It is tailored for handling block device-related
hardware events on the clients, but I guess it could to extended by
adding new message types for BlueZ events.
Is somebody interested in imp
Andrew Ziem wrote:
> After upgrading Fedora Core 6 to Fedora 8, my DISPLAY environment variable
> is always an IP address instead of a FQDN (station001.example.net). The
> change breaks login my scripts.
>
> Is there a way to change DISPLAY back to the FQDN? What program sets
> DISPLAY?
>
>
He
On Thu, 22 Nov 2007, SZABO Zsolt wrote:
> I run ltsp5 on debian etch and now I am trying to configure sound.
Finally, the sound seems to work now. I am trying to summarize it:
SERVER side setup:
# aptitude install pulseaudio pulseaudio-esound-compat pulseaudio-utils \
padevchoo
I run ltsp5 on debian etch and now I am trying to configure sound.
I would like to test the client whether the alsa modules are OK. So,
here are some output from the client:
# lsmod |grep snd
snd_ali545120492 4
snd_ac97_codec 82848 1 snd_ali5451
snd_ac97_bus2432
Hi there!
I am maintaining a system with LTPS thin-client terminals,
which are running X locally, and remote gnome sessions
on the server. (This works pretty good.)
I would like to configure BlueZ on the clients, so
that they can use local Bluetooth devices.
I can install the necessary software
I run to this - I'm not using none of these two models - I'm just curious.
"Koolu is working with Ubuntu (Canonical) to complete the testing and
certification of Koolu units with the Gutsy upgrade to Ubuntu 7.10.
Until that testing is complete, we are advising all Koolu customers NOT to
upgrad
Dňa St 14. November 2007 Marek Greško napísal:
> Hello,
>
> I have an unusual problem.
>
> I used to use ltsp 4 kernels with modified script init in initrd to boot
> fedora on diskless machines and run it from nfs (thick client - only nfs
> root but also usable as thin client). I was quiet happy us
