<>--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KOD
On Thu, May 7, 2009 at 5:46 AM, Kshitij Shah wrote:
> Could you provide me some pointers on how to launch one audio server per
> session ?
What I would do is create an additional listening tcp port per session
(random number, which is populated into the pulse_server env value).
This port would be
Dear Developers,
I would like to package a recent CVS checkout version of xrdp for our
distibution called Pardus. Here are my questions:
1) As the 4.0.1 version does not have any configure script and I need
to patch it heavily to take our distribution's packaging and
compilation parameters, I can
> I have looked at xrdp and it seems like the solution I need - a way to
> use thin clients (typically Damn Small Linux on old hardware) to connect
> to a server that can provide a couple of users a newer OS (such as
> OpenSUSE 11). However, it seems like the project is dead in the water,
> since
<>--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KOD
Emre Erenoglu wrote, On 05/07/2009 03:46 PM:
2) cvs version configures and compiles fine after bootstrap, however,
there are some problems:
2.1) If you give a --prefix parameter to configure script, like
--prefix=/usr , then the compiled binaries try to look in /usr/etc for
config files and
On Thu, May 7, 2009 at 11:44 PM, Mads Kiilerich wrote:
> Emre Erenoglu wrote, On 05/07/2009 03:46 PM:
>>
>> 2) cvs version configures and compiles fine after bootstrap, however,
>> there are some problems:
>> 2.1) If you give a --prefix parameter to configure script, like
>> --prefix=/usr , t
On Fri, May 8, 2009 at 12:06 AM, Mads Kiilerich wrote:
> Emre Erenoglu wrote, On 05/07/2009 11:51 PM:
>>
>> Yes, I've done the same. However, even with suse patches and 0.4.1
>> version, an ordinary configure, make and make install still can't find
>> the libvnc.so, unless I put:
>> lib=libvnc.so
