[X2Go-User] USB forwarding documentation

Seth Galitzer sgsax at ksu.edu
Mon Nov 20 23:42:04 CET 2017


I've been trying for a couple of weeks now to build a TCE image that 
this actually works on. I applied your new script to my latest attempt 
today and finally discovered that the libfreerdp-plugins-standard 
package is not actually getting installed in the chroot image. As a 
result, while the USB flash drive is getting correctly mounted in the 
expected location, when I run my RDP connection, I do not see the share 
presented by the tsclient host.

I traced the log during the build process and it looks like the package 
is getting properly added, but when I boot the image and look at the 
installed packages, it is not actually there. I'm not seeing any errors 
or where it is getting removed before the squashfs image is rolled. 
Here's an excerpt:

$ grep freerdp-plugins build.log
   libfreerdp-plugins-standard libfreerdp-primitives1.1 libfreerdp-rail1.1
Get:411 http://security.debian.org/ jessie/updates/main 
libfreerdp-plugins-standard i386 
1.1.0~git20140921.1.440916e+dfsg1-4+deb8u1 [236 kB]
Selecting previously unselected package libfreerdp-plugins-standard:i386.
Preparing to unpack 
.../libfreerdp-plugins-standard_1.1.0~git20140921.1.440916e+dfsg1-4+deb8u1_i386.deb 
...
Unpacking libfreerdp-plugins-standard:i386 
(1.1.0~git20140921.1.440916e+dfsg1-4+deb8u1) ...
Setting up libfreerdp-plugins-standard:i386 
(1.1.0~git20140921.1.440916e+dfsg1-4+deb8u1) ...
libfreerdp-plugins-standard is already the newest version.

If I try "dpkg -l|grep freerdp-plugins" on the booted client, I don't 
get any results. Not even a package in "rc" state". If I grep for 
freerdp, I get the rest of the packages requested in the overlay list.

I should note that I'm using a very lightly-patched x2goclient v4.1.1.1 
in this build and a slightly modified version of 
2900-x2go-thinclientconfig from the chroot overlay, but I don't think 
these are related to this build issue. I will double-check the latter to 
make sure.

Any thoughts as to what might be causing this or possible work-arounds this?

Thanks.
Seth

On 11/20/2017 08:24 AM, Stefan Baur wrote:
> Am 07.11.2017 um 23:56 schrieb Seth Galitzer:
>> On 11/07/2017 03:49 PM, Stefan Baur wrote:
>>> Am 07.11.2017 um 21:41 schrieb Seth Galitzer:
>>>> I'm calling xfreerdp from TCE to connect directly to the RDP server.
>>>> I've been trying to find the right cli options for xfreerdp to use for
>>>> this, but documentation is pretty light on this and I have yet to find
>>>> something that works.
>>>>
>>>> If I run dmesg on the thin client device from within the TCE desktop, I
>>>> can see that my flash drive is recognized, but it's not getting mounted.
>>>> That sounds like a udev issue within debian, but I was hoping somebody
>>>> on the list had already solved this problem.
>>>
>>> So your actually have two problems:
>>> 1) getting the automounter to mount your flash drive.
>>
>> I've found two ways to do this so far:
>> A) Install usbmount package (https://usbmount.alioth.debian.org/). I've
>> tested this and it works, but needs some tweaking to produce a
>> reliable/duplicatable mount point. This claims to work for vfat, ext*
>> and hfs.
>>
>> B) Configure udev to use pmount when a USB storage device is detected
>> (https://unix.stackexchange.com/a/124060). I haven't tested this yet,
>> but if the above option works, I'm guessing this is the manual
>> implementation of it, so it should work.
> I have updated the X2Go-automounter script.
> Assuming you are using the build instructions at
> <https://wiki.x2go.org/doku.php/doc:howto:tce>, especially
> <https://wiki.x2go.org/doku.php/doc:howto:tce#live-patching_the_build>,
> you should now be able to automatically mount VFAT, NTFS, HFS, HPFS out
> of the box (as previously mentioned, under
> /media/vendor_model/partitiondevice). Once my further changes (currently
> only stored locally on my computer) make it to the git repos, you will
> also be able to access ext* filesystems, albeit in read-only mode only.
> 
> So neither usbmount nor udev/pmount should be necessary.
> If automounting still fails for you without them, please provide more
> info about your setup.
> 
> Kind Regards,
> Stefan Baur
> 


-- 
Seth Galitzer
Systems Coordinator
Computer Science Department
Kansas State University
http://www.cs.ksu.edu/~sgsax
sgsax at ksu.edu
785-532-7790


More information about the x2go-user mailing list