PMIP3 wiki

User Tools

Site Tools

You are here: index » other » win10_wsl_1
other:win10_wsl_1

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
other:win10wsl [2020/08/21 16:36] – [Configuration (in your local Linux account)] jypeterother:win10wsl [2022/08/08 18:02] – [Installing an X server] Moved and improved the X server stuff to a new page jypeter
Line 9: Line 9:
 The user can choose to install Linux using WSL1 or WSL2. Check the [[https://docs.microsoft.com/en-us/windows/wsl/compare-versions|differences between WSL1 and WSL2]] before choosing</note> The user can choose to install Linux using WSL1 or WSL2. Check the [[https://docs.microsoft.com/en-us/windows/wsl/compare-versions|differences between WSL1 and WSL2]] before choosing</note>
  
-Read just the top of the [[https://docs.microsoft.com/en-us/windows/wsl/about|Windows Subsystem for Linux Documentation]] for a quick **WSL** description on the Microsoft site+ 
 +===== What is WSL ? ===== 
 + 
 +Useful reading: 
 +  * Have a look at the beginning of the [[https://docs.microsoft.com/en-us/windows/wsl/about|Windows Subsystem for Linux Documentation]] for a quick **WSL** description on the Microsoft site 
 +  * Read [[https://wiki.ubuntu.com/WSL|What is WSL]] on the Ubuntu site 
 +    * There is more useful information on the //WSL@Ubuntu page//, you can read the rest later
  
 In a few words, WSL is not Linux, it's more a way to [[https://blogs.msdn.microsoft.com/wsl/2016/06/15/wsl-file-system-support/|share files between Windows and Linux]] (it's OK to skip this rather technical link!). [[https://docs.microsoft.com/en-us/windows/wsl/faq#are-files-in-the-linux-drive-different-from-the-mounted-windows-drive|Files under the Linux root (i.e. /) are controlled by WSL which mimics Linux specific behavior [...follow the link for details...]]]. That's why you need //to activate WSL **and then install a Linux distribution**//. In a few words, WSL is not Linux, it's more a way to [[https://blogs.msdn.microsoft.com/wsl/2016/06/15/wsl-file-system-support/|share files between Windows and Linux]] (it's OK to skip this rather technical link!). [[https://docs.microsoft.com/en-us/windows/wsl/faq#are-files-in-the-linux-drive-different-from-the-mounted-windows-drive|Files under the Linux root (i.e. /) are controlled by WSL which mimics Linux specific behavior [...follow the link for details...]]]. That's why you need //to activate WSL **and then install a Linux distribution**//.
Line 75: Line 81:
  
 There are several ways to open a default terminal: There are several ways to open a default terminal:
-  * select //Ubuntu// from the ''Start'' menu +  * Select //Ubuntu// from the ''Start'' menu 
-  * click on the //Ubuntu// icon on the task bar+  * Click on the //Ubuntu// icon on the task bar
     * if you don't have a //Ubuntu// icon on the task bar yet: right-click on the //Ubuntu// icon (in the ''Start'' menu) -> More -> Pin to the task bar     * if you don't have a //Ubuntu// icon on the task bar yet: right-click on the //Ubuntu// icon (in the ''Start'' menu) -> More -> Pin to the task bar
     * to open more terminals: right-click on the //Ubuntu// icon on the task bar -> Ubuntu     * to open more terminals: right-click on the //Ubuntu// icon on the task bar -> Ubuntu
-  * type ''ubuntu''+<Enter> or ''wsl''+''<Enter>'' in the (Cortana) Search field on the task bar+  * Type ''ubuntu''+<Enter> or ''wsl''+''<Enter>'' in the (Cortana) Search field on the task bar
  
 == Copy/paste in the default terminal == == Copy/paste in the default terminal ==
Line 92: Line 98:
 === The WSLtty terminal === === The WSLtty terminal ===
  
-<note tip>This is the recommended (by JYP) option for now</note>+<note tip> 
 +  * This is the recommended (by JYP) option for now 
 + 
 +  * If you can't open a terminal after Windows upgrades from WSL to WSL v2, get and install the latest version of WSLtty ! 
 +</note>
  
 [[https://github.com/mintty/wsltty|WSLtty]] allows you to use the efficient //Mintty// as a terminal for WSL. **You do not need to have an //X server// running to use it!** [[https://github.com/mintty/wsltty|WSLtty]] allows you to use the efficient //Mintty// as a terminal for WSL. **You do not need to have an //X server// running to use it!**
  
   * Download and execute the latest [[https://github.com/mintty/wsltty/releases|64bit installer]] (the most recent ''wsltty-*-install-x86_64.exe'' file)   * Download and execute the latest [[https://github.com/mintty/wsltty/releases|64bit installer]] (the most recent ''wsltty-*-install-x86_64.exe'' file)
-  * You will then have different ways to start a terminal: +  * After installing, you will get several ways to open a terminal: 
-    * //WSL terminal// shorcut on the desktop +    * Double-click on the ''WSL terminal'' icon on the desktop 
-    * //Ubuntu terminal// and //WSL Terminal// in the ''Start'' menu +    * ''U''=>''Ubuntu terminal'' and ''W''=>''WSL Terminal'' in the ''Start'' menu 
-  * Open a terminal and right-click in it to discover/use the options +      * There is also a ''W''=>''WSLtty'' folder, than you don't really need 
-    * More options with CTRL+right-click+  * Open a terminal and right-click in it to check the available options 
 +    * You can access even more options with CTRL+right-click
     * You can cycle between the open WSLtty terminals with CTRL+Tab and Shift+CTRL+Tab     * You can cycle between the open WSLtty terminals with CTRL+Tab and Shift+CTRL+Tab
   *  [[https://github.com/mintty/mintty/wiki|Technical stuff]] (on the Mintty wiki)   *  [[https://github.com/mintty/mintty/wiki|Technical stuff]] (on the Mintty wiki)
Line 107: Line 118:
 === The new Windows Terminal === === The new Windows Terminal ===
  
-Microsoft is working on a powerful replacement of the old ''cmd'' terminal, but it still needs to be improved ([[https://devblogs.microsoft.com/commandline/windows-terminal-preview-v0-8-release/|Windows Terminal Preview v0.8 Release]])+Microsoft is working on a powerful replacement of the old ''cmd'' terminal! Check [[https://github.com/microsoft/terminal|Windows Terminal, Console and Command-Line @ github]]
  
-You can install it from the Microsoft Store: search //Windows Terminal (Preview)//+Note: the //Windows Terminal// looks really promising, but will be nice when there is a GUI for editing the options (rather the editing a //json// file with a text editor...) and a way to select //xterm-style// copy-pasting. See [[https://github.com/microsoft/terminal/issues/7646|Feature request: add xterm-style select/copy/paste options]]
  
-[[https://github.com/microsoft/terminal|Windows terminal @ github]]+  * [[https://aka.ms/terminal|Getting the Windows Terminal from the Microsoft Store]] 
 +  * [[https://docs.microsoft.com/en-us/windows/terminal/|Documentation]]
  
 === Terminals started from Linux === === Terminals started from Linux ===
Line 293: Line 305:
 ==== Installing an X server ==== ==== Installing an X server ====
  
-<WRAP center round tip 60%> +Read the [[other:x_conf|Installing and configuring an X server]] page
-The //X server// will allow you to display graphical windows (i.e. //X windows//) from remote servers or from your local WSL+Ubuntu +
-</WRAP> +
- +
- +
-<WRAP center round important 60%> +
-After the X server is installed and running, some graphical applications and images (or the text displayed by those applications) may appear blurry. This is due to some servers or some Linux applications not handling high resolution (//HiDPI//) screens correctly +
- +
-X410 has several options for this (see [[https://token2shell.com/howto/x410/running-x410-on-hidpi-screens/|Running X410 on HiDPI Screens]]) but it may also work correctly with non commercial applications +
-</WRAP> +
- +
-=== Installing VcXrsv === +
- +
-<note tip>VcXrsv is pre-installed on the LSCE computers!</note> +
- +
-Type: <wrap em>free</wrap> +
- +
-Download the installer from [[https://sourceforge.net/projects/vcxsrv/|VcXrsv]] and install VcXrsv. +
- +
-== VcXrsv Configuration == +
- +
-You need to configure VcXrsv to work in //multiple windows// mode. The following steps will show you how to create a shortcut on your desktop to start VcXrsv in this appropriate mode +
- +
-  * Start //Xlaunch//: ''Start'' => ''VcXrsv'' => ''Xlaunch'' +
-  * Check ''Multiple windows'' (the default choice) then ''Next'' +
-  * Check ''Start no client'' then ''Next'' +
-  * Keep the default ''Clipboard'' settigs, uncheck ''Native opengl'' (not sure about that) then ''Next'' +
-  * Click on ''Save configuration'' and save an ''X_Server.xlaunch'' configuration file on your Desktop, then ''Terminate''. You should now have a new ''X_Server'' icon/shortcut on your Desktop +
-  * Click on the new ''X_Server'' icon, and check that an ''X'' icon appears in the right side of the taskbar (you may have to look for it in the //Display hidden icons// pull-up menu) +
-    * Note: you can right-click on the ''X'' icon and select ''Exit...'' if you need to quit the X server +
-  * Note: if you notice later that the content of some displayed //X windows// appear **blurry**, see if you can [[other:win10misc#vcxsrv_x_server|fix the compatibility settings]], or try to use **x410**. +
-  * You are now **ready**, if you only need VcXrsv to display graphical windows from remote servers +
- +
-  * The following steps allow you to test the X server in a **local** WSL+Ubuntu terminal. **Do not set the DISPLAY variable yourself when you are connected to a remote server with ''ssh''!** +
-    * Open a **local** terminal (in WSL+Ubuntu) +
-    * Type ''export DISPLAY=localhost:0.0'' +
-    * Type ''xterm'' and check that a new //xterm// terminal appears +
- +
- +
-=== Installing x410 === +
- +
-Type: <wrap em>commercial</wrap> +
- +
-[[https://token2shell.com/x410/|x410]] is a low cost commercial X server that can be directly installed from the [[https://www.microsoft.com/store/apps/9nlp712zmn9q|Microsoft store]]. Once installed, it will be automatically updated by the Microsoft Store application. +
- +
-**Starting, configuring and exiting X410**: you can start X410 by clicking on it in the Windows Start Menu, or choose to [[https://token2shell.com/howto/x410/automatically-start-x410-on-login/|Automatically Start X410 on Login]] +
-  * Note: nothing actually happens when you start X410, as it is just waiting to display graphics! You will just get a new **X** icon in the //hidden// icons of the taskbar. +
-  * You can configure (and exit) X410 by right clicking on its **X** icon +
- +
-=== Installing MobaXterm === +
- +
-Type: <wrap em>commercial</wrap> +
- +
-Available at [[https://mobaxterm.mobatek.net/|MobaXterm]], not tested. This seems to be more than just an X server, and may be an overkill if you just need an X server+
  
 ==== Configuration (in your local Linux account) ==== ==== Configuration (in your local Linux account) ====
Line 392: Line 351:
 ===== Updating WSL and ubuntu ===== ===== Updating WSL and ubuntu =====
  
-<note tip>You don't have to worry about this if you have just installed WSL+Ubuntu!</note>+<note tip>You don't have to worry about the //Upgrade// section if you have just installed WSL+Ubuntu, because you are already using the latest Ubuntu stable release!</note>
 ==== WSL ==== ==== WSL ====
  
-WSL is automatically updated when Windows 10 is updated+**Nothing to do!** WSL is automatically updated, provided you have **enabled** the [[other:win10maintain#updating_microsoft_office|Get updates for other Microsoft products]] option
  
 [[https://docs.microsoft.com/en-us/windows/wsl/wsl-config#managing-multiple-linux-distributions| WSL command line options]] [[https://docs.microsoft.com/en-us/windows/wsl/wsl-config#managing-multiple-linux-distributions| WSL command line options]]
Line 423: Line 382:
 578 /mnt/h/Scratch/jyp/pkg_190221.txt</code> 578 /mnt/h/Scratch/jyp/pkg_190221.txt</code>
  
 +==== Upgrading ubuntu ====
  
 +<WRAP center round tip 60%>
 +You can skip this section if you have just installed ubuntu, since you are already running the latest stable release available
 +</WRAP>
 +
 +
 +The **updates** are for maintaining the same version of ubuntu (e.g. you go from version ''18.04.2'' to ''18.04.5''), while **upgrades** are for going from one major version to the next (e.g ''16.xx'' => ''18.xx'' => ''20.xx''). We try to only use the stable major releases, that have an even version number.
 +
 +We use the **LTS versions** (//Long Time Support//) to ensure even more stability, which means that we will get updates of a given major release for quite some time after the next major release is available, so it is not mandatory to updgrade ubuntu if you are still receiving updates for the release you use
 +
 +There should not be any risk, but it may be a good idea to [[other:win10wsl#creating_a_backup_of_the_linux_running_in_wsl|create a backup]] of your current ubuntu before upgrading it!
 +
 +Use ''sudo'' for each command below, or just become root by using ''sudo su -''
 +
 +  * before the Linux upgrade:
 +    * [[other:win10wsl#creating_a_backup_of_the_linux_running_in_wsl|create a backup]]
 +    * Check how much space is left on ''C:''
 +    * make sure you have a network connection
 +    * read the official WSL [[https://devblogs.microsoft.com/commandline/upgrading-ubuntu/#upgrading-your-distribution|Upgrading your distribution]] instructions
 +
 +  * Launch the upgrade with the ''do-release-upgrade'' command and follow the instructions
 +    * if you get a //There is no development version of an LTS available// message, use ''do-release-upgrade -d''
 +    * if you get a //Please install all available updates for your release before upgrading// message, use ''apt-get dist-upgrade'' and then try ''do-release-upgrade -d'' again (see [[https://www.liquidweb.com/kb/troubleshooting-please-install-available-updates-release-upgrading/|How to Solve the Upgrade Ubuntu Install Updates Error]])
 +    * if you get ''sleep: cannot read realtime clock: Invalid argument'' error, temporarily replace the ''sleep'' binary with an executable empty file. Do not forget to restore the original sleep command after the upgrade!!
 +      * <code># sleep 1
 +sleep: cannot read realtime clock: Invalid argument
 +# mv /bin/sleep /bin/sleep.back
 +# ls -l /bin/sleep.back
 +-rwxr-xr-x 1 root root 35000 Jan 18  2018 /bin/sleep.back
 +# touch /bin/sleep
 +# chmod +x /bin/sleep
 +# sleep 1
 +#</code>
 +      * Note: you may have to use the //empty sleep command trick// again, if the sleep command itself is updated and breaks the upgrading process again. Do not forget to restore the original sleep command after the upgrade!!\\ <code>[...]
 +Restarting services possibly affected by the upgrade:
 +  cron: stopping...sleep: cannot read realtime clock: Invalid argument
 +dpkg: error processing package libpam0g:amd64 (--configure):
 + installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1
 +E: Sub-process /usr/bin/dpkg returned an error code (1)
 +# ls -l /bin/sleep
 +-rwxr-xr-x 1 root root 39256 Sep  5  2019 /bin/sleep
 +# mv /bin/sleep /bin/sleep.back2
 +# touch /bin/sleep
 +# chmod +x /bin/sleep
 +# </code>
 +    * see also [[https://www.how2shout.com/how-to/how-to-upgrade-ubuntu-18-04-lts-to-20-04-lts-on-wsl-windows-10.html|How to Upgrade Ubuntu 18.04 LTS to 20.04 LTS on WSL (Windows 10)]]
 +    * Do not forget to restore the correct ''sleep'' executable, if you had to move it
 +      * <code># ls -l /bin/sleep*
 +-rwxr-xr-x 1 root root     0 Aug 23 23:57 /bin/sleep
 +-rwxr-xr-x 1 root root 35000 Jan 18  2018 /bin/sleep.back
 +-rwxr-xr-x 1 root root 39256 Sep  5  2019 /bin/sleep.back2
 +# cp -p /bin/sleep.back2 /bin/sleep
 +# ls -l /bin/sleep*
 +-rwxr-xr-x 1 root root 39256 Sep  5  2019 /bin/sleep
 +-rwxr-xr-x 1 root root 35000 Jan 18  2018 /bin/sleep.back
 +-rwxr-xr-x 1 root root 39256 Sep  5  2019 /bin/sleep.back2</code>
 +
 +
 +==== Cleaning up things ====
 +
 + * [[https://linoxide.com/how-to-clear-apt-cache/|How to Clear Apt Cache]]
 ===== Advanced configuration ===== ===== Advanced configuration =====
  
Line 651: Line 671:
 ==== Rebooting WSL ==== ==== Rebooting WSL ====
  
-It is not possible to reboot WSL like a regular Linux computer+It is not possible to **stop or reboot WSL** like a regular Linux computer
   * ''shutdown -r now'' will generate an error message   * ''shutdown -r now'' will generate an error message
-  * WSL keeps on running even when all the terminals are closed+  * WSL keeps on running even when all the Linux terminals are closed
  
-Rebooting the Windows computer will of course reboot WSL but it's useful to be able to just reboot WSL: +Shutting down or rebooting the Windows computer will of course stop WSL but it's useful to be able to just stop/restart WSL in order to: 
-  * to force WSL to recognize new disk drives and make them available as ''/mnt/<new_drive_letter'' +  * force WSL to **recognize new disk drives** and make them available as ''/mnt/<new_drive_letter'' 
-  * to force WSL to recognize drives that were still encrypted when the first terminal was started+  * force WSL to recognize drives that were still encrypted when the first WSL terminal was opened
  
-WSL can be rebooted by using either one of the following methods ​(the first is the easiest!). Warning: ​all the terminals and processes ​will be closed/​killed! +WSL can be stopped the following way. Warning: ​all the open terminals and running processes ​will be terminated! 
-  * from a //Windows PowerShell// (no need to run as administrator):\\ type ''wsl %%--%%terminate Ubuntu'' +  * from a Windows terminal (''cmd'', ''PowerShell'', ... no need to run as administrator): 
-  * from the //Services// tab of the Task manager or the //Services// program (launch ''services.msc'') +    * Get the name of the installed (and running) Linux: **''wsl %%--%%list %%--%%verbose''** 
-    * Right-click on the ''LxssManager'' service and select //Restart// +    * Stop //this instance// of Linux (e.g. if it is named //Ubuntu//): **''wsl %%--%%terminate Ubuntu''** 
-  * from a //Powershell// in admin mode (right-click on the Windows //Start// button) +    * or Stop //all// the currently running Linux distributions: **''wsl %%--%%shutdown''**
-    * Type ''Get-Service LxssManager | Restart-Service''+
  
-Source: google ''wsl lxssmanager'' ([[https://www.how2shout.com/how-to/how-to-reboot-wsl-windows-subsystem-linux-in-windows-10.html|most usable answer]]) 
  
 ==== Creating a backup of the Linux running in WSL ==== ==== Creating a backup of the Linux running in WSL ====
  
 There are several types of WSL related directories that you may want to back up: There are several types of WSL related directories that you may want to back up:
-  * <wrap hi>Your Linux //home// directory</wrap> (''/home/<your_login>''), or some specific sub-directories of the //Ubuntu// running in WSL (sub-directories of ''/''): all these files are located in a [[other:win10wsl#location_of_the_files|hidden sub-directory of you Windows directory]], and the best way to save them is probably to **create a tar file from Linux**, and put this tar file in a specific Windows folder+ 
 +  * <wrap hi>Your Linux //home// directory</wrap> (''/home/<your_login>''), or some specific sub-directories of the //Ubuntu// running in WSL (sub-directories of ''/''): all these files are located in a [[other:win10wsl#location_of_the_files|hidden sub-directory of you Windows directory]], and the best way to save them is probably to **create a tar file from Linux**, and put this tar file in a specific Windows //WSL backup folder// (we will use below the directory ''/mnt/c/Scratch/<your_login>'' or ''c:\Scratch\<your_login>'')
     * <code bash>$ cd /home     * <code bash>$ cd /home
-# $ du -sh <your_login>+
 $ du -sh $USER $ du -sh $USER
 232K    <your_login> 232K    <your_login>
-# $ tar cfz /mnt/c/Scratch/<your_login>/<your_login>_home_<some_date>.tgz <your_login>+ 
 +# We assume below that there is an existing /mnt/c/Scratch/<your_login>/ directory 
 +# It's a WINDOWS directory C:\Scratch\<your_login>
 $ tar cfz /mnt/c/Scratch/$USER/${USER}_home_`date +%y%m%d_%H%M`.tgz $USER $ tar cfz /mnt/c/Scratch/$USER/${USER}_home_`date +%y%m%d_%H%M`.tgz $USER
-</code>+ 
 +# Check the size of the new (and existing old) backup(s) 
 +$ ls -ltr /mnt/c/Scratch/$USER/${USER}_*.tgz 
 +81K Jan 21  2020 /mnt/c/Scratch/<your_login>/<your_login>_home_200121.tgz 
 +93K Aug 22  2020 /mnt/c/Scratch/<your_login>/<your_login>_home_200822_1151.tgz 
 +95K Feb 24 12:09 /mnt/c/Scratch/<your_login>/<your_login>_home_210224_1209.tgz</code> 
   * <wrap hi>Regular Windows folders</wrap> where you store data used by WSL: you can use ''tar'' in a Linux terminal, as above, or use any usual way of backing up Windows files (drag and drop, some specific [[other:win10apps#backup_software|backup software]])   * <wrap hi>Regular Windows folders</wrap> where you store data used by WSL: you can use ''tar'' in a Linux terminal, as above, or use any usual way of backing up Windows files (drag and drop, some specific [[other:win10apps#backup_software|backup software]])
 +
   * <wrap hi>The **full** Linux/Ubuntu installation</wrap> running in WSL (based on [[https://docs.microsoft.com/en-us/windows/wsl/faq#how-can-i-back-up-my-wsl-distros-or-move-them-from-one-drive-to-another|How can I back up my WSL distros?]]). The following steps will save the full installation in a tar file, that can be used later for restoring the full installation (//restoration// not tested yet)   * <wrap hi>The **full** Linux/Ubuntu installation</wrap> running in WSL (based on [[https://docs.microsoft.com/en-us/windows/wsl/faq#how-can-i-back-up-my-wsl-distros-or-move-them-from-one-drive-to-another|How can I back up my WSL distros?]]). The following steps will save the full installation in a tar file, that can be used later for restoring the full installation (//restoration// not tested yet)
-    * Open a Windows terminal (preferably a //PowerShell// if you need easy copy/paste) +    * Open a **Windows terminal** (preferably a //PowerShell// if you need easy copy/paste)\\ The //Windows// terminal is where you will type the ''wsl'' commands shown below 
-    * Determine the name of the current Linux installation used in WSL+    * Determine the name of the current Linux installation used in WSL (and see if it is running, and using //WSL 1// or //WSL 2//)
       * <code>> wsl --list --all       * <code>> wsl --list --all
-Distributions du sous-système Windows pour Linux : +Distributions du sous-système Windows pour Linux : 
-Ubuntu (par défaut)</code>+Ubuntu (par défaut) 
 + 
 +> wsl --list --verbose 
 +  NAME      STATE           VERSION 
 +* Ubuntu    Running         1</code>
     * [[other:win10wsl#rebooting_wsl|Stop WSL+Linux]]     * [[other:win10wsl#rebooting_wsl|Stop WSL+Linux]]
-    * Export the current Linux to a tar file: ''wsl %%--%%export Ubuntu C:\Scratch\<your_login>\<your_login>_ubuntu-full_<some_date>.tar'' +      * <code>> wsl --list --verbose 
-    * You can optionally open a new terminal (this will start again WSL+Ubuntu) to get some information about the created file (size and number of saved files/directories), and compress it to save some space+  NAME      STATE           VERSION 
 +* Ubuntu    Running         1 
 + 
 +> wsl --shutdown 
 + 
 +> wsl --list --verbose 
 +  NAME      STATE           VERSION 
 +* Ubuntu    Stopped         1</code> 
 +    * Export the current Linux to a //tar// file: 
 +      * <code> > wsl --export Ubuntu C:\Scratch\<your_login>\<your_login>_ubuntu-<ubuntu_version>-full_<some_date>.tar</code> 
 +    * You can optionally open a new terminal (this will start again WSL+Ubuntu) to get some information about the created file (size and number of saved files/directories), and compress it in order to save some disk space
       * <code>$ cd /mnt/c/Scratch/<your_login>       * <code>$ cd /mnt/c/Scratch/<your_login>
-$ ls -lh <your_login>_ubuntu-full_200514.tar + 
-2.6G May 14 16:29 <your_login>_ubuntu-full_200514.tar +$ ls -ltrh *ubuntu*tar* 
-$ tar tvf <your_login>_ubuntu-full_200514.tar | wc -l +976M Jan 21  2020 <your_login>_200121.tar.gz 
-105600 +2.8G Aug 22  2020 <your_login>-16.04-full_200822.tar 
-$ gzip <your_login>_ubuntu-full_200514.tar +3.4G Feb 24 14:06 <your_login>-20-04-1-full_210224.tar 
-$ ls -lh <your_login>_ubuntu-full_200514.tar.gz + 
-976M May 14 16:29 +# Determine the number of files/directories in the backup 
 +$ tar tvf <your_login>-20-04-1-full_210224.tar | wc -l 
 +112711 
 + 
 +$ gzip *ubuntu*.tar 
 + 
 +$ ls -ltrh *ubuntu*tar* 
 +976M Jan 21  2020 <your_login>_200121.tar.gz 
 +1.2G Aug 22  2020 <your_login>-16.04-full_200822.tar.gz 
 +1.8G Feb 24 14:06 <your_login>-20-04-1-full_210224.tar.gz
 </code> </code>
  
Line 722: Line 773:
   * Find how to unregister Ubuntu on the [[https://docs.microsoft.com/en-us/windows/wsl/wsl-config|Manage and configure Windows Subsystem for Linux]] page   * Find how to unregister Ubuntu on the [[https://docs.microsoft.com/en-us/windows/wsl/wsl-config|Manage and configure Windows Subsystem for Linux]] page
   * and then disable WSL???   * and then disable WSL???
 +
 +===== Miscellaneous =====
 +
 +  * Determining from **inside** the running Linux if you are using WSL (or another type of virtual machine)\\ <code>$ systemd-detect-virt
 +wsl</code>
 +
 ===== Other WSL resources and links ===== ===== Other WSL resources and links =====
  
other/win10_wsl_1.txt · Last modified: 2022/08/12 14:25 by jypeter
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki