Dick,
I used sudo actually. I have following output:
slog@G780:~$ sudo apt-get install x11-common
[sudo] password for slog:
Reading package lists... Done
Building dependency tree
Reading state information... Done
x11-common is already the newest version.
x11-common set to manually installed.
The following package was automatically installed and is no longer required:
os-prober
Use 'apt-get autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 53 not upgraded.
It seems as I have X11 installed already.
Please, try to build Unicon with graphics. What result you will get?
I used "make X-Configure name=x86_64_linux" to configure.
22.09.2016, 17:18, "Richard H. McCullough" <r...@pioneerca.com>:
Sergy,You must use sudo for apt-get.This completed with no errors for me:sudo apt-get install x11-common
Dick McCullough
From: slogic...@yandex.ru
To: rhmccullo...@outlook.com; unicon-group@lists.sourceforge.net
Date: Thu, 22 Sep 2016 16:12:11 +0300
Subject: Re: [Unicon-group] Bash on Ubuntu on Windows
Dick,Thank you for such useful comments.Do you know how to install X11 binaries on Win10? I discovered that to run X11 application from bash you need to instal Xming server from sourceforge. That's working, really. But when I try to build Unicon with graphics "make X-Configure" says that X11 libraries and headers are missed. "apt-get install x11-common" doesn't install anything due to some access error. So, now I can use bash only for pre-builded graphical Ubuntu applications.Sergey22.09.2016, 14:45, "Richard H. McCullough" <rhmccullo...@outlook.com>:A few comments which you may find useful.1. Windows Subsystem for Linux is a beta version, only available in Windows 10 version 1607 and later.2. The current version does not allow you to execute Windows .exe files.You can access any Windows files via /mnt/c/, limited by Windows permissions.3. The Windows Bash command (C:/Windows/System32/bash.exe) is a little different fromthe Ubuntu bash command (/bin/bash)."bash.exe ~" opens the Bash window in your Ubuntu home directory (e.g. /home/rhm)"bash.exe ~ --login" also executes your .profile or .bash_profile4. ssh from a remote machine will put you in your Windows home directory (e.g. C:/Users/rhm)running the Windows shell (cmd.exe).Executing "/windows/system32/bash.exe ~ --login" then works as described above.If your SSH Server services disappear, you need to rerun the enable WSL command in PowerShell.
Dick McCullough
------------------------------------------------------------------------------
_______________________________________________ Unicon-group mailing list Unicon-group@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unicon-group