Hi Everyone, Forgive me if this question isn't specific to LTSP, but is there a way to restrict users, so that they can only be logged in once. Let me explain. I am the Director of Information Technology for Montana Harley-Davidson, and have switched our Missoula location (about 40 systems) over to an LTSP based system. It runs phenomenally well and I haven't had any major issues. However, the software that controls our inventory, accounting, POS and everything else "company based" is written specifically for Windows 2003 Server. I have setup each user account so that when they login, the printer is defaulted to the printer assigned to that area (i.e. parts, cashwrap, service, sales, etc.). Using rdesktop, the thin clients then connect to the Windows Server and run our company software. However, try as I might, I can't keep certain users from logging into one workstation and then logging out again before using a different workstation. So, the parts manager might login to his account at the parts counter and then leave it open, go into his office and login again as himself. This causes the default printer to be reset to his current location. Not only that, but I have informed all of the employees that they will be held directly responsible for any infractions that occur with their user account. In short, I need a way of forcing each user account be logged into the system only once at any given time. Any help or a nudge in the right direction would be greatly appreciated.
Regards, Tanner Bachman Director of Information Technology Montana Harley-Davidson 5106 East Harrier Missoula, MT 59808 Office: 406.721.2154 [EMAIL PROTECTED] www.mtharley.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, November 24, 2006 1:05 PM To: ltsp-discuss@lists.sourceforge.net Subject: Ltsp-discuss Digest, Vol 6, Issue 35 Send Ltsp-discuss mailing list submissions to ltsp-discuss@lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/ltsp-discuss or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of Ltsp-discuss digest..." Today's Topics: 1. Latency induced with LDM (Francis Giraldeau) 2. Re: localdev issues (sokol) 3. Re: localdev issues (Verner Kj?rsgaard) 4. Re: localdev issues (Roland Holder) 5. Re: localdev issues (Richard Bos) 6. Re: localdev issues (Verner Kj?rsgaard) 7. Re: localdev issues (Verner Kj?rsgaard) 8. Re: localdev issues (Kamchybek Jusupov) 9. Re: localdev issues (Gudmund Areskoug) 10. Re: Unable to play movies on Thin client with LTSP on Ubuntu Edgy ([SARL BIGORNO] Emmanuel Chevallier) 11. Re: localdev issues (Richard Bos) 12. Re: localdev issues (Scott Balneaves) ---------------------------------------------------------------------- Message: 1 Date: Thu, 23 Nov 2006 15:21:33 -0500 From: Francis Giraldeau <[EMAIL PROTECTED]> Subject: [Ltsp-discuss] Latency induced with LDM To: ltsp-discuss@lists.sourceforge.net Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; format=flowed; charset=ISO-8859-1 Hi, When using LDM, it seems that there is more latency than normal XDMCP with GDM, the windows are more sluglish and redrawing is slower, even on good terminal (PentiumII and brand new AMD geode). My hypothesis is that SSH encryption causes this behavior. I would like to mesure this induced latency, to see if there is a way to minimize it. Maybe there are parameters that affects this latency. Does anybody know a way to do mesure it? Does other people remark that behavior? Thanks and have a nice day, Francis Giraldeau ------------------------------ Message: 2 Date: Thu, 23 Nov 2006 21:24:36 +0100 From: sokol <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] localdev issues To: ltsp-discuss@lists.sourceforge.net Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Patrick Barber a ?crit : > Scott Balneaves wrote: > >> On Wed, Nov 22, 2006 at 07:14:31PM +0100, sokol wrote: >> >> >> >>> Nope sir, 32 bit is not a unique solution. We have here biOpteron >>> x86_64 server and in similar situation we compiled fuse and ltspfs >>> on this server and it works like a charm. >>> >>> >> Well, yes, if you compile LtspFS for 64 bit, then it should work as >> well. I was simply trying to save him the recompile. >> >> Scott >> >> >> > ok so with ltspFS compiled as 64bit and FUSE comiled as 64bit it > should work native 64bit? where is the source code for ltspFS I have > no problems recompiling, but is there more than just ltspFS that needs > to be recompiled? > Everything is explained in details on http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspFS In particular for ltspFS sources, you can read : > > > Installing ltspfs on your LTSP server: > > * Grab a copy of ltspfs. This is the bit that runs on the server: > > cd /usr/local/src > cvs -d :pserver:[EMAIL PROTECTED]:/usr/local/cvsroot checkout > ltspfs cd ltspfs ./configure make make install ------------------------------ Message: 3 Date: Thu, 23 Nov 2006 23:12:41 +0100 From: Verner Kj?rsgaard <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] localdev issues To: ltsp-discuss@lists.sourceforge.net Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed sokol skrev: > Patrick Barber a ?crit : > > >> Scott Balneaves wrote: >> >> >>> On Wed, Nov 22, 2006 at 07:14:31PM +0100, sokol wrote: >>> >>> >>> >>> >>>> Nope sir, 32 bit is not a unique solution. We have here biOpteron >>>> x86_64 server and in similar situation we compiled fuse and ltspfs >>>> on this server and it works like a charm. >>>> >>>> >>>> >>> Well, yes, if you compile LtspFS for 64 bit, then it should work as >>> well. I was simply trying to save him the recompile. >>> >>> Scott >>> >>> >>> >>> >> ok so with ltspFS compiled as 64bit and FUSE comiled as 64bit it >> should work native 64bit? where is the source code for ltspFS I have >> no problems recompiling, but is there more than just ltspFS that >> needs to be recompiled? >> >> > Everything is explained in details on > http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspFS > In particular for ltspFS sources, you can read : > >> Installing ltspfs on your LTSP server: >> >> * Grab a copy of ltspfs. This is the bit that runs on the server: >> >> cd /usr/local/src >> cvs -d :pserver:[EMAIL PROTECTED]:/usr/local/cvsroot checkout >> ltspfs cd ltspfs ./configure make make install >> > > > Hi list, - I apologize for this strange posting, it's partly a test to see if my mail works at all. I'm stranded in a hotel room with only Windows internet access. - Now, I too asked questions about getting LDA to work. I had it working on SuSE10/LTSP4.2u4, but could not, no matter what, get it working on SuSE92(64bit). To my HORROR today, I couldn't get it running on a brand new SuSE10 installation at a school. - I started over again, reading the wiki and the web :-) - The error was that uppon inserting a USB stick, I'd get an empty KINGSTON folder. I finally got it working - and this is my first short report of what I did. The SuSE10 runs on a dual 64bit machine, i.e. it's a 64 bit version. That's where the catch is. A test with ldd ltspfs gave that a libfuse.so.2.5.2 was missing. Indeed it was there, but not in the correct place. And, worse, it was a 64-bit thing. I understood from the wiki and the web that ltspfs is compiled against a 32bit fuse. So I did the unthinkable, I just copied a 32bit version of libfuse.so.2.5.2 from my laptop (SuSE10 also) into /usr/lib/ on the 64bit target machine. This gave me one error less, ldd ltspfs could now find everything. But still no luck. I then realized that my fuse installation was severely broken. So, I downloaded fuse 2.6 from sourceforge.net in source code. Compiled it with no swithes or anything directly on my SuSE10/64bit. Installed and remembered to modprobe fuse into the kernel. I then checked and rechecked the wiki and finally fired up a terminal, inserted a USB stick and BINGO!, there it was. Everything works just fine. I then proceeded with the code/patch/rpm from Gideon Romm (Work in Progress, wiki), the system that is meant to give you LDA in a full screen RPD session. I followed the instructions given from Gideon on the wiki - and BINGO again. Works just like breeze, USB stick to be seen just as described. If wanted by the list, I shall report deeper about what I did. Again, I do not have access to just about anything at this time - I don't even know if this mail will hit the list... Still THANK YOU to the LTSP people and to all on the list for their help in this matter. Today was a good day :-) Best regards, Verner ------------------------------ Message: 4 Date: Thu, 23 Nov 2006 23:22:42 +0100 From: Roland Holder <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] localdev issues To: ltsp-discuss@lists.sourceforge.net Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Verner! I'd be glad to see your solution descibed on the ltsp wiki. I'm moderating a german ltsp forum and a lot of questions about problems with 64 bit SuSE came there in the last few weeks. Thanks, Roland Verner Kj?rsgaard schrieb: > sokol skrev: >> Patrick Barber a ?crit : >> >> >>> Scott Balneaves wrote: >>> >>> >>>> On Wed, Nov 22, 2006 at 07:14:31PM +0100, sokol wrote: >>>> >>>> >>>> >>>> >>>>> Nope sir, 32 bit is not a unique solution. We have here biOpteron >>>>> x86_64 server and in similar situation we compiled fuse and ltspfs >>>>> on this server and it works like a charm. >>>>> >>>>> >>>>> >>>> Well, yes, if you compile LtspFS for 64 bit, then it should work as >>>> well. I was simply trying to save him the recompile. >>>> >>>> Scott >>>> >>>> >>>> >>>> >>> ok so with ltspFS compiled as 64bit and FUSE comiled as 64bit it >>> should work native 64bit? where is the source code for ltspFS I have >>> no problems recompiling, but is there more than just ltspFS that >>> needs to be recompiled? >>> >>> >> Everything is explained in details on >> http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspFS >> In particular for ltspFS sources, you can read : >> >>> Installing ltspfs on your LTSP server: >>> >>> * Grab a copy of ltspfs. This is the bit that runs on the server: >>> >>> cd /usr/local/src >>> cvs -d :pserver:[EMAIL PROTECTED]:/usr/local/cvsroot checkout >>> ltspfs cd ltspfs ./configure make make install >>> >> >> > Hi list, > > - I apologize for this strange posting, it's partly a test to see if > my mail works at all. I'm stranded in a hotel room with only Windows > internet access. > > - Now, I too asked questions about getting LDA to work. I had it > working on SuSE10/LTSP4.2u4, but could not, no matter what, get it > working on SuSE92(64bit). To my HORROR today, I couldn't get it > running on a brand new SuSE10 installation at a school. > - I started over again, reading the wiki and the web :-) > - The error was that uppon inserting a USB stick, I'd get an empty > KINGSTON folder. > > I finally got it working - and this is my first short report of what I did. > > The SuSE10 runs on a dual 64bit machine, i.e. it's a 64 bit version. > That's where the catch is. > > A test with ldd ltspfs gave that a libfuse.so.2.5.2 was missing. > Indeed it was there, but not in the correct place. And, worse, it was > a 64-bit thing. > I understood from the wiki and the web that ltspfs is compiled against > a 32bit fuse. > So I did the unthinkable, I just copied a 32bit version of > libfuse.so.2.5.2 from my laptop (SuSE10 also) into /usr/lib/ on the > 64bit target machine. > This gave me one error less, ldd ltspfs could now find everything. But > still no luck. > I then realized that my fuse installation was severely broken. So, I > downloaded fuse 2.6 from sourceforge.net in source code. Compiled it > with no swithes or anything directly on my SuSE10/64bit. Installed and > remembered to modprobe fuse into the kernel. > I then checked and rechecked the wiki and finally fired up a terminal, > inserted a USB stick and BINGO!, there it was. Everything works just fine. > > I then proceeded with the code/patch/rpm from Gideon Romm (Work in > Progress, wiki), the system that is meant to give you LDA in a full > screen RPD session. I followed the instructions given from Gideon on > the wiki - and BINGO again. Works just like breeze, USB stick to be > seen just as described. > > If wanted by the list, I shall report deeper about what I did. Again, > I do not have access to just about anything at this time - I don't > even know if this mail will hit the list... > > Still THANK YOU to the LTSP people and to all on the list for their > help in this matter. Today was a good day :-) > > Best regards, > Verner > > > > ---------------------------------------------------------------------- > --- Take Surveys. Earn Cash. Influence the Future of IT Join > SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys - and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEV > DEV > _____________________________________________________________________ > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > For additional LTSP help, try #ltsp channel on irc.freenode.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFFZh8y23ZOxtu/pP0RAjFiAJ4oMrazjPQ2hrEZ7R8w9z+4biSzdACgk54d rsH9W56KRBprPUd7Psq79rU= =NkLQ -----END PGP SIGNATURE----- ------------------------------ Message: 5 Date: Thu, 23 Nov 2006 23:24:50 +0100 From: Richard Bos <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] localdev issues To: ltsp-discuss@lists.sourceforge.net Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" Verner, Op donderdag 23 november 2006 23:12, schreef Verner Kj?rsgaard: > I then realized that my fuse installation was severely broken. So, I > downloaded fuse 2.6 from sourceforge.net in source code. Compiled it > with no swithes or anything directly on my SuSE10/64bit. can you test the server with the fuse rpm, that you can find on this link: http://ftp-1.gwdg.de/pub/opensuse/repositories/home:/cthiel1/SL-10.1/i586/ -- Richard Bos Without a home the journey is endless ------------------------------ Message: 6 Date: Thu, 23 Nov 2006 23:32:15 +0100 From: Verner Kj?rsgaard <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] localdev issues To: ltsp-discuss@lists.sourceforge.net Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Roland Holder skrev: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Verner! > > I'd be glad to see your solution descibed on the ltsp wiki. I'm > moderating a german ltsp forum and a lot of questions about problems > with 64 bit SuSE came there in the last few weeks. > > Thanks, Roland > > Verner Kj?rsgaard schrieb: > >> sokol skrev: >> >>> Patrick Barber a ?crit : >>> >>> >>> >>>> Scott Balneaves wrote: >>>> >>>> >>>> >>>>> On Wed, Nov 22, 2006 at 07:14:31PM +0100, sokol wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> Nope sir, 32 bit is not a unique solution. We have here biOpteron x86_64 >>>>>> server and in similar situation we compiled fuse and ltspfs >>>>>> on this server and it works like a charm. >>>>>> >>>>>> >>>>>> >>>>>> >>>>> Well, yes, if you compile LtspFS for 64 bit, then it should work as >>>>> well. I was simply trying to save him the recompile. >>>>> >>>>> Scott >>>>> >>>>> >>>>> >>>>> >>>>> >>>> ok so with ltspFS compiled as 64bit and FUSE comiled as 64bit it should >>>> work native 64bit? where is the source code for ltspFS I have no >>>> problems recompiling, but is there more than just ltspFS that needs to >>>> be recompiled? >>>> >>>> >>>> >>> Everything is explained in details on >>> http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspFS >>> In particular for ltspFS sources, you can read : >>> >>> >>>> Installing ltspfs on your LTSP server: >>>> >>>> * Grab a copy of ltspfs. This is the bit that runs on the server: >>>> >>>> cd /usr/local/src >>>> cvs -d :pserver:[EMAIL PROTECTED]:/usr/local/cvsroot checkout ltspfs >>>> cd ltspfs >>>> ./configure >>>> make >>>> make install >>>> >>>> >>> >>> >> Hi list, >> >> - I apologize for this strange posting, it's partly a test to see if my >> mail works at all. I'm stranded in a hotel room with only Windows >> internet access. >> >> - Now, I too asked questions about getting LDA to work. I had it working >> on SuSE10/LTSP4.2u4, but could not, no matter what, get it working on >> SuSE92(64bit). To my HORROR today, I couldn't get it running on a brand >> new SuSE10 installation at a school. >> - I started over again, reading the wiki and the web :-) >> - The error was that uppon inserting a USB stick, I'd get an empty >> KINGSTON folder. >> >> I finally got it working - and this is my first short report of what I did. >> >> The SuSE10 runs on a dual 64bit machine, i.e. it's a 64 bit version. >> That's where the catch is. >> >> A test with ldd ltspfs gave that a libfuse.so.2.5.2 was missing. Indeed >> it was there, but not in the correct place. And, worse, it was a 64-bit >> thing. >> I understood from the wiki and the web that ltspfs is compiled against a >> 32bit fuse. >> So I did the unthinkable, I just copied a 32bit version of >> libfuse.so.2.5.2 from my laptop (SuSE10 also) into /usr/lib/ on the >> 64bit target machine. >> This gave me one error less, ldd ltspfs could now find everything. But >> still no luck. >> I then realized that my fuse installation was severely broken. So, I >> downloaded fuse 2.6 from sourceforge.net in source code. Compiled it >> with no swithes or anything directly on my SuSE10/64bit. Installed and >> remembered to modprobe fuse into the kernel. >> I then checked and rechecked the wiki and finally fired up a terminal, >> inserted a USB stick and BINGO!, there it was. Everything works just fine. >> >> I then proceeded with the code/patch/rpm from Gideon Romm (Work in >> Progress, wiki), the system that is meant to give you LDA in a full >> screen RPD session. I followed the instructions given from Gideon on the >> wiki - and BINGO again. Works just like breeze, USB stick to be seen >> just as described. >> >> If wanted by the list, I shall report deeper about what I did. Again, I >> do not have access to just about anything at this time - I don't even >> know if this mail will hit the list... >> >> Still THANK YOU to the LTSP people and to all on the list for their help >> in this matter. Today was a good day :-) >> >> Best regards, >> Verner >> >> >> >> > Hi Roland, > Ok, so the mail made it to the list. Wiki; I'm a little reluctant about putting stuff on the wiki. First, I'm not really very good at formatting stuff,- to get it looking right. Secondly, and worse, I would just hate to put something on the wiki that was NOT correct. At the moment I feel a little like a blind hen that just found to grains... I need to clarify my mind and to make sure I'm not misleading people. One thing, though. On the wiki I read that the output of the terminal name "(trouble shooting) from step 4" should exactly match the display name and so forth. No, that is not entirely correct. It's enough if only the hostname is the very same, a FQDN is not needed. I think I'll hit the bed now. Best regards, Verner ------------------------------ Message: 7 Date: Thu, 23 Nov 2006 23:33:37 +0100 From: Verner Kj?rsgaard <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] localdev issues To: ltsp-discuss@lists.sourceforge.net Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Richard Bos skrev: > Verner, > > Op donderdag 23 november 2006 23:12, schreef Verner Kj?rsgaard: > >> I then realized that my fuse installation was severely broken. So, I >> downloaded fuse 2.6 from sourceforge.net in source code. Compiled it >> with no swithes or anything directly on my SuSE10/64bit. >> > > can you test the server with the fuse rpm, that you can find on this link: > http://ftp-1.gwdg.de/pub/opensuse/repositories/home:/cthiel1/SL-10.1/i586/ > > Hi Richard, yes, I'll see if I can get around to do that tomorrow. /Verner ------------------------------ Message: 8 Date: Fri, 24 Nov 2006 08:10:56 +0800 From: Kamchybek Jusupov <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] localdev issues To: ltsp-discuss@lists.sourceforge.net Cc: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=UTF-8 On Thu, 23 Nov 2006 23:12:41 +0100 / Verner Kj?rsgaard wrote: With a subject: Re: [Ltsp-discuss] localdev issues > The SuSE10 runs on a dual 64bit machine, i.e. it's a 64 bit version. > That's where the catch is. I had a similar situation with 64-bit Ubuntu installation. > A test with ldd ltspfs gave that a libfuse.so.2.5.2 was missing. > Indeed it was there, but not in the correct place. And, worse, it was > a 64-bit thing. > I understood from the wiki and the web that ltspfs is compiled > against a 32bit fuse. > So I did the unthinkable, I just copied a 32bit version of > libfuse.so.2.5.2 from my laptop (SuSE10 also) into /usr/lib/ on the > 64bit target machine. > This gave me one error less, ldd ltspfs could now find everything. > But still no luck. > I then realized that my fuse installation was severely broken. So, I > downloaded fuse 2.6 from sourceforge.net in source code. Compiled it > with no swithes or anything directly on my SuSE10/64bit. Installed > and remembered to modprobe fuse into the kernel. > I then checked and rechecked the wiki and finally fired up a > terminal, inserted a USB stick and BINGO!, there it was. Everything > works just fine. Well, with Ubuntu what I did was basically force installation of 32-bit fuse package with "apt-get" package manager. And after that everything just worked. > Still THANK YOU to the LTSP people and to all on the list for their > help in this matter. Today was a good day :-) Yes! Thank you guys for such a perfect job! -- Rgds, Kamchybek Jusupov Attitude is no substitude for competence... GPG Key: C565 2827 0858 ECFE 74D7 A556 7B09 59DA B6C8 FF8C ------------------------------ Message: 9 Date: Fri, 24 Nov 2006 09:42:37 +0100 From: Gudmund Areskoug <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] localdev issues To: LTSP <ltsp-discuss@lists.sourceforge.net> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 Hi Verner, Verner Kj?rsgaard wrote: > Hi list, > > - I apologize for this strange posting, it's partly a test to see if my > mail works at all. I'm stranded in a hotel room with only Windows > internet access. thanks for reminding me of an old "todo-wishlist" item of mine: making a road warrior "LTSP phone home" for USB or CD, to work on any OS. BR, Gudmund ------------------------------ Message: 10 Date: Fri, 24 Nov 2006 09:48:25 +0100 From: "[SARL BIGORNO] Emmanuel Chevallier" <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] Unable to play movies on Thin client with LTSP on Ubuntu Edgy To: ltsp-discuss@lists.sourceforge.net Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi, I will try this next month and post the results to the list. Thanks Udo, Emmanuel Udo P?tz a ?crit : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > [SARL BIGORNO] Emmanuel Chevallier schrieb: > >> Thanks Todd for your response, >> >> > Hi List > > >> I wiil try your method with multimedia players local apps and a vlc >> streaming from the server. >> My thinclient is not enough speed (CPU is Vortex86 approximatively >> Pentium Pro 200) to read a Divx directly by the network with local apps. >> > > You could do something like this: On the server (powerful) you convert > the video to some other format, for example nuppelvideo. That is a > little compressed but not too high so even the 200MHz thingy should > handle it. I could think of something like this: > server: mencoder -o - -ovc nuv your-video.some-format | netcat > <ip-thinclient> 3333 > client: netcat -l -p 3333 | mplayer - > You need mplayer/xine/vlc and netcat as a local app. I have a static > mplayer, a static netcat should be really easy. > Hope this helps > Udo > > >> Have a good day, >> Emmanuel >> >> > > - -- > i-nex Gesellschaft f?r linuxbasierte Netze mbH > > H?ttenstr. 7 > 52068 Aachen > Tel.: +49 241 18 94 100 > > URL : http://www.i-nex.de > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.3 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFFZHEC4OBS/SKjuEwRAuL5AJsFtKTJMLkTJ8HdZsEomKW/JK+r4wCgj16X > bDN78ZLowS2SPhFYNJ/+x+Y= > =6OLB > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _____________________________________________________________________ > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > For additional LTSP help, try #ltsp channel on irc.freenode.net > > ------------------------------ Message: 11 Date: Fri, 24 Nov 2006 20:19:42 +0100 From: Richard Bos <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] localdev issues To: ltsp-discuss@lists.sourceforge.net Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" Verner, Op donderdag 23 november 2006 23:32, schreef Verner Kj?rsgaard: > No, that is not entirely correct. It's enough if only > the hostname is the very same, a FQDN is not needed. please state so in the wiki. That a lot of people will enjoy your correction. It will be the same with your information. You need to put it in the wiki, so others are able to improve it with their findings/experience. You can always put a note before the text you put in. The formatting is not a big issue in a wiki, as that is done by the wiki engine ;) -- Richard Bos Without a home the journey is endless ------------------------------ Message: 12 Date: Fri, 24 Nov 2006 13:28:30 -0600 From: Scott Balneaves <[EMAIL PROTECTED]> Subject: Re: [Ltsp-discuss] localdev issues To: ltsp-discuss@lists.sourceforge.net Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=iso-8859-1 On Fri, Nov 24, 2006 at 08:19:42PM +0100, Richard Bos wrote: > Verner, > > Op donderdag 23 november 2006 23:32, schreef Verner Kj?rsgaard: > > No, that is not entirely correct. It's enough if only > > the hostname is the very same, a FQDN is not needed. > > please state so in the wiki. That a lot of people will enjoy your correction. > It will be the same with your information. You need to put it in the wiki, so > others are able to improve it with their findings/experience. You can always > put a note before the text you put in. The formatting is not a big issue in > a wiki, as that is done by the wiki engine ;) Things still stand, though. Hey have to match. As the fellow who wrote it, I know what the code does. If DISPLAY on the server looks like: foo.bar.baz:0.0 and the hostname on the client looks like: foo it won't work. If you're going to have FQDN on the server, then the DHCP server has to hand out FQDN's as well. It have to be the same in both places. Scott -- Scott L. Balneaves | "Let us endeavor so to live that when we come to die Systems Department | even the undertaker will be sorry." Legal Aid Manitoba | -- Mark Twain, "Pudd'nhead Wilson's Calendar" ------------------------------ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ------------------------------ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net End of Ltsp-discuss Digest, Vol 6, Issue 35 ******************************************* ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
