Am 23.01.19 um 10:40 schrieb Stroganov Roman:
> Why I show consideration for it?
> If during one session the user used many different usb disks, then it will
> have many not working links on a desktop (garbage) and in / home/media/. It
> will mislead him...
I agree with you there. Feedback from
I checked at myself at the test stand as removal of usb drive works
After disconnection of usb disk from the thin client
Console of the thin client:
ls /media/
Data_Treveler
After remove usb drive the directory for mount automatically was not
removed...
We go on the server. We see the link
Am 22.01.19 um 16:02 schrieb Stefan Baur:
> Ah, I think I understand.
> I will talk to the developers about this.
> My guess is that maybe there is no way to pass the information along to
> the server that the flash disk (with this particular name) has been
> removed, so it only shows the contents
Am 22.01.19 um 15:46 schrieb Stroganov Roman:
> You are right. I use the translator.
> The description of a problem in my native language is lower
>
> При подключении usb диска к тонкому клиенту на нем создается каталог для ее
> монтирования (например /media/Kingston) Эта же директория
You are right. I use the translator.
The description of a problem in my native language is lower
При подключении usb диска к тонкому клиенту на нем создается каталог для ее
монтирования (например /media/Kingston) Эта же директория пробрасывается на
сервер x2go и там доступна.
При отключении usb
Am 22.01.19 um 14:29 schrieb Stroganov Roman:
> usb drive are mounted well. Russian is displayed correctly both on the thin
> client and on the server. To work with objects with the Russian names
> became possible.
> Thanks a lot for the help!
You're welcome! Also, debugging this publicly on the
Yes, that that went not so. Checksum of my patch was another.
I applied yours. Checksum coincided.
usb drive are mounted well. Russian is displayed correctly both on the thin
client and on the server. To work with objects with the Russian names
became possible.
Thanks a lot for the help!
But me
Am 22.01.19 um 12:00 schrieb Stroganov Roman:
> If I carry out ./x2gousbpatch && ./x2gobuild2 2>&1 | tee logfile that the
> patch is downloaded with github. This is not what it is necessary for me.
> I change in ./patch/includes.chroot/usr/lib/x2go/tce/x2gousbmount a line
> elsif (system("mount
If I carry out ./x2gousbpatch && ./x2gobuild2 2>&1 | tee logfile that the
patch is downloaded with github. This is not what it is necessary for me.
I change in ./patch/includes.chroot/usr/lib/x2go/tce/x2gousbmount a line
elsif (system("mount -tvfat $dev /media/$name/$ldev -o
Am 21.01.19 um 16:00 schrieb Stefan Baur:
> My guess is that FAT32 (to be more precise: the vfat mount module)
> doesn't support UTF-8 out of the box, and/or you're using some regional
> charset (KOI8-R, maybe?) instead of UTF-8. On a system that expects
> UTF-8, this will cause confusion ...
Am 21.01.19 um 15:14 schrieb Stroganov Roman:
> I will share the observations:
> I have 2 identical usb drive. One ntfs, other fat32. On both I create a
> directory "Новая папка" (new folder) and "новый файл.txt" (new file.txt)
> We connect both and we watch contents after mount in the console of
I will share the observations:
I have 2 identical usb drive. One ntfs, other fat32. On both I create a
directory "Новая папка" (new folder) and "новый файл.txt" (new file.txt)
We connect both and we watch contents after mount in the console of the
thin client:
ls /media/ntfs_drive/
Новая Папка
Am 21.01.19 um 13:06 schrieb Stefan Baur:
> Am 21.01.19 um 12:45 schrieb Stroganov Roman:
>
> Well, I'm glad we got the connection issues solved ...
>
>
>> Forwarding directory /home/user/Документы from simple linux (not the thin
>> client) forwards empty directories. If I forward a directory
Am 21.01.19 um 12:45 schrieb Stroganov Roman:
Well, I'm glad we got the connection issues solved ...
> Forwarding directory /home/user/Документы from simple linux (not the thin
> client) forwards empty directories. If I forward a directory in Latin, it
> forwards it, but everything is farther
Am 18.01.19 um 15:51 schrieb Stroganov Roman:
> I repeated build image for the thin client.
> Now from the console of the thin client of
> md5sum/usr/lib/x2go/tce/x2gousbmount gives correctly
> 4ce1acefdfa39bef3755d55a6a22b673
> Usb drive is mounted in / media/Data_Treveler/sda1 and I see its
I repeated build image for the thin client.
Now from the console of the thin client of
md5sum/usr/lib/x2go/tce/x2gousbmount gives correctly
4ce1acefdfa39bef3755d55a6a22b673
Usb drive is mounted in / media/Data_Treveler/sda1 and I see its contents
there, but how to me now to see it on the server?
I
Am 18.01.19 um 11:57 schrieb Stroganov Roman:
> ls -la /usr/lib/x2go/tce/x2gousbmount
> -rwxr-xr-x 1 root root 12886 Янв 16 19:17 /usr/lib/x2go/tce/x2gousbmount
>
> md5sum /usr/lib/x2go/tce/x2gousbmount
> a6959f1f1de425ea26d8076d21b84b3e /usr/lib/x2go/tce/x2gousbmount
Hmm, that's not the
ls -la /usr/lib/x2go/tce/x2gousbmount
-rwxr-xr-x 1 root root 12886 Янв 16 19:17 /usr/lib/x2go/tce/x2gousbmount
md5sum /usr/lib/x2go/tce/x2gousbmount
a6959f1f1de425ea26d8076d21b84b3e /usr/lib/x2go/tce/x2gousbmount
fdisk -l
-bash fdisk: Command not found
grep usbmount /var/log/syslog
empty line
Am 17.01.19 um 20:41 schrieb Stroganov Roman:
> I made
> mount | tee mountbefore
> mount | tee mountafter
> diff mountbefore mountafter
> Blank line
>
> If flash disk is inserted into consoles of the thin client when to gather
> lsblk I see
>
> sda 30G disk
> sda1 30G part
>
> But there
Am 17.01.19 um 20:41 schrieb Stroganov Roman:
> I made
> mount | tee mountbefore
> mount | tee mountafter
> diff mountbefore mountafter
> Blank line
>
> If flash disk is inserted into consoles of the thin client when to gather
> lsblk I see
>
> sda 30G disk
> sda1 30G part
>
> But there
I made
mount | tee mountbefore
mount | tee mountafter
diff mountbefore mountafter
Blank line
If flash disk is inserted into consoles of the thin client when to gather
lsblk I see
sda 30G disk
sda1 30G part
But there are no mount points. I can make
sudo mkdir /mnt/1
sudo mount /dev/sda1
Hi Roman!
Am 17.01.19 um 14:08 schrieb Stroganov Roman:
> On points:
> At me on the xfce server
>
> Sound:
> The sound earned. audioout=list helped to see the correct name of the
> alsa_card.pci-_00_1b.0|output:analog-stereo sound card But a sound
> every time of mute. It is necessary to
On points:
At me on the xfce server
Sound:
The sound earned. audioout=list helped to see the correct name of the
alsa_card.pci-_00_1b.0|output:analog-stereo sound card But a sound
every time of mute. It is necessary to include it.
Usb disks:
I tried 3 usb flash drive. On all there is a file
Am 17.01.19 um 09:48 schrieb Stroganov Roman:
> From this what checked:
> tcpprint - works (checked for kyocera fs-1300d, but I think any printers
> which work with linux will work)
This is raw TCP/IP, so the make and model of printer doesn't matter.
In fact, you could hook up a cheap GDI printer
Yes. It really works! Thanks!
Speed of work of graphics very good. Delays not considerably absolutely.
For tests I started full-screen video. Under equal conditions traffic of
x11forwarding (ltsp) =95-140 Mb/s, x2go=17-22 Mb/s. It very cool. The fact
that I wanted!
>From this what checked:
Am 16.01.19 um 18:35 schrieb Stefan Baur:
> Am 16.01.19 um 16:10 schrieb Stefan Baur:
>> Am 16.01.19 um 13:56 schrieb Stroganov Roman:
>>
>>> On the thin client I see the console localhost login text:
>>> Sometimes it is very quickly visible some blue screen and again the console.
> I just
Am 16.01.19 um 16:10 schrieb Stefan Baur:
> Am 16.01.19 um 13:56 schrieb Stroganov Roman:
>
>> On the thin client I see the console localhost login text:
>> Sometimes it is very quickly visible some blue screen and again the console.
I just encountered a similar issue on a test build. I'm not
Am 16.01.19 um 13:56 schrieb Stroganov Roman:
> On the thin client I see the console localhost login text:
> Sometimes it is very quickly visible some blue screen and again the console.
This is an indication that your X session is starting up, but crashing.
I suggest you log in as
Unfortunately at me not to receive the thin client to the x2go server...
On the thin client I see the console localhost login text:
Sometimes it is very quickly visible some blue screen and again the console.
I have a computer about Linux and x2go the client. From it I am well
connected to the
Am 16.01.19 um 08:49 schrieb Stroganov Roman:
> cat /etc/debian_version
> 9.6
Ah, you're using a newer version of Debian than the one I recommended.
Maybe that's causing your issue with the exported variables not showing
up (though it should not ...).
> Your Haque seems it turned out. Assembly
Bingo!
I downloaded pxelinux.0 C of the website syslinux, renamed the x2go-vmlinuz
files into vmlinuz, x2go-initrd.img in initrd.img, made simlink and loading
of the thin client began.
Now on the thin client I see the console "localhost login:"
Sometimes it is very quickly visible some blue screen
cat /etc/debian_version
9.6
uname -a
Linux tce 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64
GNU/Linux
dpkg -l | grep live-build
ii live-build1:20170213
all Live System Build Components
dpkg -l | grep bash
ii bash 4.4-5
amd64
I am a pity
In the previous letter of deduglog there was not all
Here debuglog contents completely:
grep results:
# Select ONE of the following LBX2GO_ARCH lines and comment out the others
export LBX2GO_ARCH='-a amd64 -k amd64'
# export LBX2GO_ARCH='-a i386 -k 686-pae'
# export
You were right! *d*ash was by default used
I added #!/bin/bash in the beginning of all three scripts. Further carried
out everything as root
After start of scripts I receive the message:
root@tce:~/builddir# ./x2goconfig && ./x2gousbpatch && ./x2gobuild 2>&1 |
tee logfile
One or more of the
Am 14.01.19 um 11:21 schrieb Stroganov Roman:
> Thank you that you help me.
> Now I began new installation on debian stretch on yours instructions.
> After start of scripts I receive the message:
>
> root@tce:~/builddir# ./x2goconfig && ./x2gousbpatch && ./x2gobuild 2&1
> | tee logfile
> One or
Thank you that you help me.
Now I began new installation on debian stretch on yours instructions.
After start of scripts I receive the message:
root@tce:~/builddir# ./x2goconfig && ./x2gousbpatch && ./x2gobuild 2&1
| tee logfile
One or more of the following variables is unset:
LBX2GO_ARCH: ''
Thank you that you help me.
Now I began new installation on debian stretch on yours instructions.
After start of scripts I receive the message:
root@tce:~/builddir# ./x2goconfig && ./x2gousbpatch && ./x2gobuild 2&1
| tee logfile
One or more of the following variables is unset:
LBX2GO_ARCH: ''
Am 13.01.19 um 22:15 schrieb Stroganov Roman:
> I have several thin clients who 512 MB have RAM. At the others 1 GB and
> more. If I correctly understood x2go tce-live it is loading of FAT clients?
I don't know what you mean by this. The main difference between
TCE-Classic and TCE-Live is that
I have several thin clients who 512 MB have RAM. At the others 1 GB and
more. If I correctly understood x2go tce-live it is loading of FAT clients?
Their start pudt long? I plan about 15-20 clients only in local network.
The network is very stable. Use of nfs is quite possible.
I would like to
39 matches
Mail list logo
