x2go-dev

x2go-dev@lists.x2go.org

1 participants
5399 discussions

Re: [X2go-dev] X2go-dev Digest, Vol 21, Issue 36
by brian mullan 02 Oct '10

02 Oct '10

I just read about this. Google has introduced and open sourced a new image format to help speed up the performance of websites called W*ebP*. - *WebP has a 40% improvement over JPEG and WebP was designed to improve the compression offered by JPEG*. - Google has created a site<http://code.google.com/speed/webp/gallery.html>for Web developers and users to assess the performance of WebP. - The images presented at the site show WebP side-by-side with JPEG images. The WebP images are 40 to 50 percent trimmer in bytes but look the same to the human eye. - *WebP is based on Google's VP8 codec that they also open-sourced recently. * VP8 is part of the heart of HTML 5's video capability. - To trim down file size for WebP, Google used an image compressor based on the VP8 codec that Google open-sourced in May 2010. My question for x2go developers is Could WebP (or VP8 codec itself) be implemented at both the x2go-server and the x2go-client and *possibly get a substantial improvement* in video performance ?? Currently x2go as most NX oriented solutions (Freenx, NoMachine NX) typically use JPEG for compression. But it seems to me that WebP could be implemented and as it is reported to be 40% more efficient than JPEG... less bytes means less network traffic and usually better/faster performance. Brian Mullan

2 1

Python X2go rewrite from scratch, first drafts available online
by Mike Gabriel 01 Oct '10

01 Oct '10

Hi there, I would like to make you aware of the API documentation of the completely from scratch rewritten Python X2go library, now published under GPLv3. http://packages.das-netzwerkteam.de/doc/python-x2go/ There is a German project page on our website (we are thinking of translating the site into English, sorry for now for those who cannot read German): http://das-netzwerkteam.de/site/?q=node/71 The current Python X2go development can be followed at: https://svn.das-netzwerkteam.de/websvn/listing.php?repname=nwt-projects&pat… There are packages for Ubuntu Lucid available in our APT repository: deb http://packages.das-netzwerkteam.de/ubuntu lucid main Available packages are: python-x2go (incl. non-lucid dependencies like python-greenlet, python-gevent) pyhoca-cli python-x2go package notes: -------------------------- With Python X2go you will also need the x2goclient package from the X2go repository installed (because of nxproxy binary). Python X2go requires Python v2.6 or greater. NOTE: at this very moment I realize, that the example files in the package have not been adapted to the current API... this will come in a couple of days, so stay tuned... pyhoca-cli package notes: ------------------------- PyHoca-cli will become an X2go Client implemented in Python. Currently there is only graphics support available (no sound, no printing, no sshfs, no...). But it works on my Ubuntu lucid systems and maybe also on yours. After installation try pyhoca-cli --help or ,,man pyhoca-cli'' for further information. As you might guess... Python X2go is far away from being anything like unstable, testing or stable. It is purely experimental and actually freshly born. If you have ideas, feedbacks, bugs, patches, please let me know... AND: Do not even think about using Python X2go in productive scenarios during the next year or so. Developing stable software takes time!!! I'll be happy if any of you wishes to contribute. light+love, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 mail: m.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

change of mailing list rules / additional mailing lists / git repostitory
by Heinz-M. Graesing 30 Sep '10

30 Sep '10

Hello list members, After the latest developments on the list, we've received a lot of complaints about the how this list is being used. Tobias - a member of Linux4Afrika - offered his help to improve the communication of this project. Please have a look at www.linux4afrika.de. Linux4Afrika still offers the best x2go tutorials on the net. We also got help through Mike Gabriel (a member of the x2go-dev list -> das-netzwerkteam.de ). Thank you very much! From now on we'll change some rules of communication on this project: 1. x2go-dev list the x2go-dev list is reserved for all development topics. There will be no discussion on topics like "organisational criticism" or "personal preferences". 2. x2go-user list The x2go-user list is reserved for all user topics. Please also avoid topics like "organisational criticism" or "personal preferences". On the x2go-user list people may ask their questions on setting up working x2go environments, share their problems when using the x2goclient etc. This list will be co-moderated by Tobias. Please use acurate mail subjects and don't discuss "Off Topic" . 3. x2go-announcements list there will be a new group called "x2go-announcements" too. This group is READ ONLY. On this group announcements will be made. When ever it's possible we will connect the information with a DATE so you can use it for your concepts. We will do our best to give you timelines and time frames whenever possible. If we realize that plans and actions get delayed, we will inform you as soon as we know about it, so that you can adopt your own schedules. We hope to meet your requirements with this change. Please, make sure that you subscribe to the x2go-announcements list to benefit from this. 4. the GIT repository In the future we will change our workflow as follows. We (Alex and Heinz) will use an internal GIT repository for drafts, collecting new ideas, internal testing, etc. This will be our sandbox, we do not want to bother you with that. We will also push our work to a public GIT repository in regular, sensible intervals. This will always be the latest functional x2go code available (HEAD). This shall give the online community convenient access to our work. As some of you have suggested, we will fill the GIT master branch with the x2go core components. The community, however, will have access to custom GIT branches), to work on their own blend. This will enable us to cooperate and benefit from each others' work. With the master branch of the public GIT repository, it might naturally occur that pushed code is not the most stable, sometimes not even in testing state. To give us all some orientation, we will mark stable revisions of the public GIT master branch by tagging versions that are ready for testing. All untagged revisions may probably fail in your setup and exist only for your insight. The public GIT (in terms of hosting and servers) is to be located in Germany and our objective is that it will not offend German laws regarding privacy protection. Ideally this should be a neutral space, so it is not bound to any company/person. We personally prefer Berlios GIT, because many people working with x2go already are Berlios members. We will help to build up this public GIT and it should be the only space where people can find contributions. (We rather ask you to join in on our Berlios GIT, than setting up a repository of your own). The GIT Feature of our Berlios is already activated. It is planned to publish the GIT with the help of Mike Gabriel - who is indeed a great help and truly a member of our new "internet related community". x2go has 3 mayor user groups. This might not be clear to everyone. The communication channels of the first two groups are personal contact, regular meetings, phone conferences, etc. and of course e-mail as well. Most of these people are listening to this list, only some of them are posting contributions from time to time. That is namely people around the Linux4Africa project and people around Skolelinux. Both groups have been using x2go intensively for quite a while and we are always keen on keeping x2go compatible to their setups and environments. The newest and third community is the online community of x2go. Mostly people, we have never met and maybe will never meet in person. The individual demands of this group are much different from the first two groups. This group has very specific needs and we would like to take care of them. Again I have to thank you (the community) for the idea of the groups and the GIT as it was taken out of the history of our mailing list. The lists will be made available in the next days. As soon as the Berlios team has activate them, you are invited to subscribe. Further announcements will be made on the regarding mailing list: # x2go-announcement https://lists.berlios.de/mailman/listinfo/x2go-announcement If you would like to discuss the usage of x2go, please join: # x2go-user https://lists.berlios.de/mailman/listinfo/x2go-user For technical topics regarding the development of x2go, please join: # x2go-dev https://lists.berlios.de/mailman/listinfo/x2go-dev best regards, Alex and Heinz

2 1

x2goclient (3.01-13) unstable; urgency=low
by Heinz-M. Graesing 29 Sep '10

29 Sep '10

Dear x2go users, visiting with your browser the url http://www.x2go.org/deb/pool-untested/x2goclient/ you'll find a untested version of x2goclient for windows (The changes only effect the windows version of x2goclient). This is the most recent version we are working on and it will solve some reported problems with x2goclient. This is an untested state of this software and it is not meant for productive usage. It is not usable as plugin at all at the moment. The Changelog: * workaround for "Full Screen" mode in windows * support for clipboard in windows The URL for BINARY download: http://www.x2go.org/deb/pool-untested/x2goclient/x2goclient-3.01-13-setup.e… The URL for SOURCE download: http://www.x2go.org/deb/pool-untested/x2goclient/x2goclient_3.01-13.tar.gz Again: this is a snapshot of our development work. Don't use it in productive environments. best regards, Alex and Heinz

2 1

Compiling X2goclient on Ubuntu ARM
by Jo-Erlend Schinstad 27 Sep '10

27 Sep '10

I have an IGEPv2 board which I'd like to test x2goclient on. I've installed Ubuntu Maverick ARM on it, but I couldn't find any binary packages for it, so I thought I'd compile it myself. However, I only received error messages. I was hoping someone could provide some instructions on how to compile on this platform? TIA, Jo-Erlend Schinstad

2 2

Git Repo
by Matthew Macdonald-Wallace 25 Sep '10

25 Sep '10

Hi all, I realise I'm very new to the community, however I'd be happy to check in the latest sources to my github repos and share from there? Let me know if you are happy for me to do this. Kind regards, Matt

3 3

Hello dead project...
by Eli K. 24 Sep '10

24 Sep '10

I just wan't to be fair comment the things that going on here. Dear project, whats going on here is business strategy. Somebody wants to earn money or wants to have good reputation and needs influence on the tool he is using - at best not influence but control. This is needed to proof customers or what ever you address that you are the only competence. It is always esier to show the world failures of people, but in this way it was showing failures AND developing something better. I too wanted to get control here and I've began to work on my own fork. And I've caused trouble to existing project. I bet this project is dead even if you don't know now. The failures of the project was: No awareness of trademarks, no awareness of fast reacting and wrong marketing. If you want to keep control you should develop such things as company - not as project. To give you a last chance - you can keep your little domain. It will be wanted soon by sombody else - so make your homework... ...this time... Congratulations to the new way - I bet with contributions a fork will grow faster and better. Here my thoughts about how this would be better: * Don't spend time on own clients - integrate your work into existing clients like krd, tsclient, vinagre,... * Have every functionality as a module so that somebody can use SMB and others SSHFS or WEBDAV * As Plugin you should only make a google native client project. This is much better than every Plugin and Googles Browser even runs on phones - and you don't even need to compile it especially. I bet this can be soon done with python too. * Face the future - there will only be google and ubuntu - javacript and python. Your work is to be compared with spice and nx4!!! so long...

12 31

Hardware SSH acceleration
by Dimitris Anogiatis 24 Sep '10

24 Sep '10

Dear List, Does anyone know of any advantages from installing a hardware ssh (or crypto) accelleration device on a server machine running x2go? For example I've tried to tweak my SSH server but despite some improvements in responsiveness video playback (I tried a youtube video) is still choppy. Would a device like that help or does x2go's design not allow it to benefit from such an enhancement? I'm using my x2go client from a remote location using wifi and not in a LAN. Regards, Dimitris

6 9

Re: [X2go-dev] headless client with pyx2go
by Dick Kniep 23 Sep '10

23 Sep '10

Hi Mike and list, We are seasoned python developers and thus very capable in assisting in the build of pyx2go client. We could fund some of the development, but we prefer to assist in the development ourselves, because that way we have some influence in the development and also in the speed of the development. That is also why I asked for documentation. If you have started a project for this, we would be happy to participate. So if you have an svn server or something and could give me read/write access we would definitely help. But...... We do need some information on the architecture that we would use. We have looked at the way information is exchanged with the server and I start to understand some of it, but a lot is still blurry. So PLEASE give me some insight in the architecture and what component implements which part. Dick Kniep Lindix BV tel. 036-5215580 mob. 06-50991858 -----Oorspronkelijk bericht----- Van: Mike Gabriel <m.gabriel(a)das-netzwerkteam.de> Verzonden: wo 22-09-10 03:16:36 Aan: x2go-dev(a)lists.berlios.de; Onderwerp: Re: [X2go-dev] headless client with pyx2go > Hey Dick, > > On Di 21 Sep 2010 15:18:12 CEST Dick Kniep wrote: > > > Hi list, > > > > We want to develop a headless client in python using pyx2go. > > > > The application should have the following features: > > > > 1. All parameters except for the password should come from a profile > > stored in the users home directory > > 2. The user should have the possibility to enter the password, the > > username and the server, where the username and the server should be > > retrieved from the profile > > 3. The client should support clientside printing as the x2go client > > 4. The home directory (or another directory) on the clientside > > should be mounted with fuse on the serverside > > 5. The client should start XMing with all appropriate parameters > > 6. It should be possible to start an application from the server > > side by starting a file. So if a file called test.doc exists and > > that file is started, MS-Word should start. > > 7. The profile should be maintained by a separate program (nice gui > > application) > > > > We've got the demo.py running. However when it ends, the session is > > terminated correctly, but a thread remains active. Probably the > > thread should be joined with the mainprogram. > > > > Could anyone help us with documentation on the use of fuse and the > > way commands are passed from client to server vice-versa? > > Just last weekend I (with Jörgs great help) I have started working on > such a headless client implementation. > > The working title for the project is pyx2go-cli and once there is some > stability within it, it will be available with Jörgs python-x2go > library on GitHub. There will also be Debian/Ubuntu packages available. > > If you have the possibility of funding such development work (and > thus, speed it up), I (and probably also Jörg) will be happy to > provide you with support and code. > > Best, > Mike Gabriel > > -- > > DAS-NETZWERKTEAM > mike gabriel, dorfstr. 27, 24245 barmissen > fon: +49 (4302) 281418, fax: +49 (4302) 281419 > > mail: m.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de > > freeBusy: > https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x… > _______________________________________________ > X2go-dev mailing list > X2go-dev(a)lists.berlios.de > https://lists.berlios.de/mailman/listinfo/x2go-dev > > !DSPAM:4c9958f438085362964316! > >

3 3

BKO and USB over IP
by brian mullan 23 Sep '10

23 Sep '10

Speaking of Thin Clients... Although this is not directly related to the Thin Client thread it is something I was impressed with. Boot Kernel Organization (BKO) <http://boot.kernel.org/> BKO is based on a REALLY SMALL linux ... about 1 Megabyte. It can be installed onto just 1 small partition of a USB, CD (or floppy if you have one). Its sole purpose is to boot and provide you with a simple GUI menu system (see pictures on the site) where you can select which OS you want to boot and then *BKO uses HTTPFS to download and boot that OS* for you. NOTE: on their website their list of supported OS and OS version is very outdated. When you actually do this you will see Ubuntu 10.04 desktop and server, you will also see newer versions of fedora as well as other linux distributions. I've started using this with virtual machines. I download the CD ISO and then use that to create a KVM virtual machine instance using that .ISO file. Why? Well I use that 1 KVM VM instance to launch any new VM instance I might need. Since it is only 1 Megabyte in size it boots nearly immediately. I select which Linux distribution I want, what version and the BKO then downloads the selected OS and boots it. It has worked great so far. Off of the BKO FAQ you should note: BKO is based on HTTPFS and it uses only valid HTTP requests. It means, if you have HTTP access, you can boot with BKO. Only problem that may occur is if you are behind HTTP proxy. We plan to add support for HTTP proxy in near future. Stay tuned till then. It is expected that you can use *Public DNS* system as BKO is configured to use Public dns servers instead of the servers provided by user or DHCP. We will be soon fixing this problem. Till then, you are expected to have public DNS access. That 2nd paragraph *I think may be outdated* as I believe you can now install the BKO "server" locally instead of using the BKO.org servers to download from. If you install your own BKO server locally then you "could" install all of the OS's you work with on it. Then you could use your own BKO to select *and more importantly boot a pre-configured OS* !!! I haven't checked but I am wondering if a Windows OS could be booted using BKO as well? I'm thinking you could have something like a preconfigured Ubuntu (or fedora etc) desktop with x2go client configurations and applications already installed and then just use the BKO and their GPXE to boot the clients. I haven't gotten as far as looking into installing it locally so my current workaround is to use BKO to boot then I use the python based Fabric library to automagically provision the OS with x2go, the apps I want etc. Fabric is really simple to use and lets you execute remote commands via scripts so you can for instance install x2go server or client very easily.. After the Fabric script is done my virtual machine has the OS of my choice with all the apps and x2go installed. Another interesting technology I discovered lately and tried out is USB over IP. Perhaps this could be incorporated into a future feature for x2go server & client ??? How To Set Up A USB-Over-IP Server And Client With Ubuntu 10.04 Version 1.0 Author: Falko Timme <ft [at] falkotimme [dot] com> <http://twitter.com/falko> Follow me on Twitter <http://twitter.com/falko> Last edited 01/18/2010 This tutorial shows how to set up a USB-over-IP server with Ubuntu 10.04 as well as a USB-over-IP client (also running Ubuntu 10.04). The USB/IP Project<http://usbip.sourceforge.net/>aims to develop a general USB device sharing system over IP network. To share USB devices between computers with their full functionality, USB/IP encapsulates "USB I/O messages" into TCP/IP payloads and transmits them between computers. USB-over-IP can be useful for virtual machines, for example, that don't have access to the host system's hardware - USB-over-IP allows virtual machines to use remote USB devices. I do not issue any guarantee that this will work for you! 1 Preliminary Note This tutorial is based on AliRezaTaleghani's tutorial How To Modify Your Gnu/Linux Box To Serve As A USB Over IP Server<http://www.howtoforge.com/how-to-modify-your-gnu-linux-box-to-serve-as-a-us…>, but I've adjusted it for Ubuntu 10.04 (server and client). If you want to use a Windows client, please take a look at AliRezaTaleghani's tutorial - that part is still the same. In this tutorial I use the server server1.example.com with the IP address 192.168.0.100 and the client client1.example.com with the IP address 192.168.0.101, both running Ubuntu 10.04. These settings might differ for you, so you have to replace them where appropriate. 2 Installing And Using USB/IP On The Server server1: We can install usbip as follows: aptitude install usbip Afterwards we load the usbip kernel modules: modprobe usbip modprobe usbip_common_mod To check if they really got loaded, run: lsmod | grep usbip The output should be similar to this one: root@server1:~# lsmod | grep usbip usbip 15124 0 usbip_common_mod 13605 1 usbip root@server1:~# To make sure that both modules get loaded automatically whenever you boot the system, you can add them to /etc/modules: vi /etc/modules [...] usbip usbip_common_mod Now we can start the usbip daemon: usbipd -D root@server1:~# usbipd -D Bind usbip.ko to a usb device to be exportable! root@server1:~# Now attach a USB device that you want to export to the server - I'm using a SanDisk USB flash drive here. Execute the command lsusb to find the corresponding Vendor/Device ID which is in the form of: Bus XXX Device YYY: ID VendorID:DeviceID The output on my server is as follows: root@server1:~# lsusb Bus 001 Device 002: ID 0781:5151 SanDisk Corp. Cruzer Micro Flash Drive Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub root@server1:~# The Vendor/Device ID of my SanDisk USB flash drive is 0781:5151. Now run usbip_bind_driver --list The output on my server is as follows: root@server1:~# usbip_bind_driver --list List USB devices - busid 1-1 (0781:5151) 1-1:1.0 -> usb-storage root@server1:~# As you see, the Vendor/Device ID of my SanDisk USB flash drive (0781:5151) corresponds to the BUSID 1-1. We need this BUSID to attach the USB device to the server: usbip_bind_driver --usbip 1-1 root@server1:~# usbip_bind_driver --usbip 1-1 ** (process:765): DEBUG: 1-1:1.0 -> usb-storage ** (process:765): DEBUG: unbinding interface ** (process:765): DEBUG: write "add 1-1" to /sys/bus/usb/drivers/usbip/match_busid ** Message: bind 1-1 to usbip, complete! root@server1:~# That's it, we can now use the SanDisk USB flash drive on a remote usbipclient. BTW, if you run... netstat -tap ... you should see that the usbip daemon is listening on port 3240 so please make sure that this port isn't blocked by your firewall: root@server1:~# netstat -tap Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 *:ssh *:* LISTEN 537/sshd tcp 0 0 *:3240 *:* LISTEN 762/usbipd tcp 0 52 server1.example.com:ssh 192.168.0.199:4024 ESTABLISHED 667/0 tcp6 0 0 [::]:ssh [::]:* LISTEN 537/sshd root@server1:~# Copyright © 2010 Falko Timme All Rights Reserved. How To Set Up A USB-Over-IP Server And Client With Ubuntu 10.04 - Part 2 3 Installing And Using USB/IP On The Client client1: We must install usbip on the client as well: aptitude install usbip Afterwards we load the vhci-hcd kernel module: modprobe vhci-hcd To check if it really got loaded, run: lsmod | grep vhci_hcd The output should be similar to this one: root@client1:~# lsmod | grep vhci_hcd vhci_hcd 19800 0 usbip_common_mod 13605 1 vhci_hcd root@client1:~# To make sure that the module gets loaded automatically whenever you boot the system, you can add it to /etc/modules: vi /etc/modules [...] vhci-hcd Now connect to the usbip server and get a list of available USB devices: usbip -l 192.168.0.100 (192.168.0.100 is the IP address of the usbip server.) You should find the SanDisk USB flash drive in the output (BUSID 1-1): root@client1:~# usbip -l 192.168.0.100 - 192.168.0.100 1-1: SanDisk Corp. : Cruzer Micro Flash Drive (0781:5151) : /sys/devices/pci0000:00/0000:00:07.2/usb1/1-1 : (Defined at Interface level) (00/00/00) : 0 - Mass Storage / SCSI / Bulk (Zip) (08/06/50) root@client1:~# To attach that device to the client, run: usbip -a 192.168.0.100 1-1 root@client1:~# usbip -a 192.168.0.100 1-1 8 ports available port 0 attached root@client1:~# Now run... lsusb ... and you should find the remote USB device in the output on the client: root@client1:~# lsusb Bus 001 Device 002: ID 0781:5151 SanDisk Corp. Cruzer Micro 256/512MB Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@client1:~# You can now use the remote USB device as if it was a local USB device (e.g. mount it, format it, write to it, read form it, etc.). 4 Detaching A Remote USB Device A remote USB device can be detached as follows: client1: Run... usbip --port ... to find out the port that the remote USB device uses on the client - in this case it's port 00: root@client1:~# usbip --port 8 ports available Port 00: <Port in Use> at High Speed(480Mbps) SanDisk Corp. : Cruzer Micro 256/512MB Flash Drive (0781:5151) 1-1 -> usbip://192.168.0.100:3240/1-1 (remote devid 00010002 (bus/dev 001/002)) 1-1:1.0 used by usb-storage /sys/class/bsg/1:0:0:0/device /sys/class/scsi_device/1:0:0:0/device /sys/class/scsi_disk/1:0:0:0/device /sys/class/scsi_host/host1/device /sys/class/usb_endpoint/usbdev1.4_ep02/device /sys/class/usb_endpoint/usbdev1.4_ep81/device /sys/block/sdb/device Port 01: <Port Available> Port 02: <Port Available> Port 03: <Port Available> Port 04: <Port Available> Port 05: <Port Available> Port 06: <Port Available> Port 07: <Port Available> root@client1:~# We need the port number to detach the device: usbip -d 00 root@client1:~# usbip -d 00 8 ports available port 0 detached root@client1:~# On the server, we use the BUSID (1-1) to bind the USB device to the local system (the --other switch binds the device to the local system so that it is not available over the network anymore): server1: usbip_bind_driver --other 1-1 root@server1:~# usbip_bind_driver --other 1-1 ** (process:7333): DEBUG: write "del 1-1" to /sys/bus/usb/drivers/usbip/match_busid ** Message: bind 1-1 to other drivers than usbip, complete! root@server1:~# Now go back to the client and check if the remote USB device is still available: client1: lsusb If all goes well, it shouldn't be listed anymore: root@client1:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@client1:~# 5 Links - USB/IP Project: http://usbip.sourceforge.net/ - Ubuntu: http://www.ubuntu.com/ Copyright © 2010 Falko Timme All Rights Reserved.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev