You can check the version of a Debian package (dpkg) on a Linux system using the command dpkg -s pkgName where pkgName is the name of the package. If you wish to check on whether an upgrade is available for the package, you should first update your local package index to ensure your system knows about the latest versions available in the repositories with the sudo apt update command. If updates are available you will see something like 19 packages can be upgraded. Run 'apt list --upgradable' to see them.

If you want to see whether an update is available for a particular dpkg package, e.g., winetricks, you can use the command apt-cache policy pkgName. Because dpkg manages local .deb files and doesn't directly check remote repositories, you need to use APT, which is the frontend for dpkg to compare the installed version against what is available in the repositories.

alice@Wonderland:~$ apt-cache policy winetricks
winetricks:
  Installed: 20250102-1build1
  Candidate: 20250102-1build1
  Version table:
 *** 20250102-1build1 500
        500 http://us.archive.ubuntu.com/ubuntu resolute/universe amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu resolute/universe i386 Packages
        100 /var/lib/dpkg/status
alice@Wonderland:~$

The Installed and Candidate lines indicate whether an update is available.

• Installed: The version currently running on your system.
• Candidate: The highest version available in the repositories that your system is ready to install.

If the Candidate version is newer (higher) than the Installed version, an update is available. If the version is the same then a newer version is not available.

Alternatively, you can use the command apt list --upgradable pkgName to check on whether an update is available for a single package. If it returns the package name, an update is available. If it returns nothing, the package is already up-to-date.

alice@Wonderland:~$ apt list --upgradable winetricks
alice@Wonderland:~$

To see a list of all packages that you can upgrade, you can use apt list --upgradable.

[ More Info ]

[/os/unix/linux/utilities/package] permanent link

When Deluge is run on a system running the Microsoft Windows operating system, it stores the location it uses for the incoming port number(s) in a configuration file, core.conf under the user's %APPDATA%\deluge directory. The %APPDATA% environment variable usually expands to something like the following, where YourUserName is the user name for the relevant Windows account:

C:\Users\YourUsername\AppData\Roaming\deluge\core.conf

Note: You can see the value for %APPDATA% by issuing the command echo %APPDATA% in a command prompt window. The %APPDATA% directory is a hidden directory, but you can see the contents of the Deluge configuration directory in the Windows file manager even if you haven't turned on the display of hidden folders by putting %APPDATA%\deluge in the address field in the file manager. You can then right-click on the file and choose to open it with the Windows Notepad. You can also access the directory by pressing the Win + R keys.

By default, Deluge uses a random network port or the 6881-6889 range (frequently defaulting to 6881 in many setups like Docker). You can check or change the exact active incoming port when Deluge is running under Preferences → Network. If you open the configuration file in a text editor, such as Windows Notepad, you will see something similar to the following:

"listen_ports": [6881, 6891], "random_port": false

• listen_ports — The incoming port range. If both numbers are the same, Deluge uses a single configured port.
• random_port — If true, Deluge selects a port randomly at startup; the configured range may not reflect the active port. If false, it uses the configured listen_ports range.

If you need to change the port before starting Deluge, e.g., to match an incoming port provided by a VPN provider, you can change the values. E.g., if you wanted Deluge to use port 39755, you could put the following entries in the file and then start Deluge:

    "listen_ports": [
        39755,
        39755
    ],
    "listen_random_port": null,
    "listen_reuse_port": true,

Note: If you need the actual port Deluge is listening on right now, rather than its saved setting, check Deluge's Preferences → Network → Incoming Ports. With random port selection enabled, the active port can differ from the saved value if you haven't restarted Deluge after updating the port number.

When you start Deluge, you can see if there are incoming connections to that port using the netstat command. E.g., netstat -an | find "39755".

C:\Users\Jill>netstat -an | find "39755"
  TCP    10.164.7.152:39755     0.0.0.0:0              LISTENING
  TCP    10.164.7.152:39755     10.43.22.249:64621     TIME_WAIT
  TCP    10.164.7.152:39755     10.157.104.168:49659   TIME_WAIT
  TCP    10.164.7.152:39755     10.157.104.168:57171   TIME_WAIT
  TCP    10.164.7.152:39755     10.169.234.135:49738   TIME_WAIT
  TCP    10.164.7.152:39755     10.169.234.135:55102   TIME_WAIT
  TCP    10.164.7.152:39755     10.175.210.63:50713    TIME_WAIT
  TCP    10.164.7.152:39755     10.194.155.52:14534    SYN_RECEIVED
  TCP    10.164.7.152:54686     178.93.201.240:39755   SYN_SENT
  TCP    127.0.0.1:39755        0.0.0.0:0              LISTENING
  TCP    192.168.1.7:39755      0.0.0.0:0              LISTENING
  UDP    10.162.7.159:39755     *:*
  UDP    127.0.0.1:39755        *:*
  UDP    192.168.1.7:39755      *:*

C:\Users\Jill>

References:

1. Deluge FAQ
   Deluge
2. Deluge User Guide
   Deluge

[/network/p2p] permanent link

I wasn't certain of the version of an application developed for Microsoft Linux that was installed on an Ubuntu Linux system. The wrestool utility is one application that runs on Linux systems that can be used to list or extract resources in binary files developed for Microsoft Windows systems. The utility is part of the icoutils package, which can be installed with the command sudo apt install icoutils. I needed to determine the version of StreamFab which was installed with Bottles. I was able to do so with the command wrestool -x --raw --type=version ~/.var/app/com.usebottles.bottles/data/bottles/bottles/StreamFab/drive_c/Program\ Files/StreamFab/StreamFab/StreamFab64.exe (use a backslash before any space in the directory path or filename).

alice@Wonderland:~$ wrestool -x --raw --type=version ~/.var/app/com.usebottles.bottles/data/bottles/bottles/StreamFab/drive_c/Program\ Files/StreamFab/StreamFab/StreamFab64.exe
4VS_VERSION_INFO���hStringFileInfoD040904E4JCompanyNameDVDFab Software Inc.<
FileDescriptionStreamFabFileVersion7.0.5.24
InternalNameStreamFab�7LegalCopyrightCopyright (c) 2019-2026 DVDFab.cn All Rights Reserved.DOriginalFilenameStreamFab.exe4
ProductNameStreamFabProductVersion7.0.5.2DVarFileInfo$Translation	�

The command showed the version of StreamFab was 7.0.5.2. Once you have installed the icoutils Debian package, you can see details on the package with dpkg -s icoutils.

[ More Info ]

[/os/unix/linux/utilities/file] permanent link

Bottles allows one to run applications developed for the Microsoft Windows operating system (OS) on Linux systems. I had created bottle for the desktop version of Comic Collector from CLZ. But as I had installed the Movie Collector and Book Collector desktop programs for managing our movie and book collections in a .wine-collectorz Wine prefix on an Ubuntu Linux system, I decided to remove the Comic Collector bottle and reinstall the software in the .wine-collectorz prefix instead. To remove a Wine bottle, you can take the following steps.

1. Open the Bottles application and select the bottle you wish to remove by clicking on it.
2. With the relevant bottle displayed, click on the column of 3 dots near the top, right side of the window.
3. Select Delete Bottle from the pull down menu
4. When asked for confirmation for the deletion, click on Delete.

The bottle will then be removed from the list of bottles. You can confirm that the directory associated with the bottle is gone by checking the ~/.var/app/com.usebottles.bottles/data/bottles/bottles/ directory.

[ More Info ]

[/os/unix/linux/bottles] permanent link

Method 1: Using Computer Management — Graphical User Interface (GUI)

1. Press the Windows key plus the X key (or you can press the Windows key plus the R key, type compmgmt.msc and press Enter.
2. In the left pane of the window, expand System Tools, then Shared Folders, and then select Shares. A list of all the active shared folders, their paths, and share names will appear in the right pane.

   

Method 2: Using Powershell

1. Open the Start menu, or use the Windows key and R, type PowerShell, and press Enter. Then type the command Get-SmbShare and press Enter. The command displays a table of all server message block (SMB) shares currently active on your machine.If you only want to see the directory path for a particular sharename, you can use a command such as Get-Smbshare -Name sharename where sharename is the relevant sharename. E.g., if the directory E:\Downloads was shared using the sharename Downloads.

   PS C:\> Get-SMBShare -Name Downloads
   
   Name      ScopeName Path         Description
   ----      --------- ----         -----------
   Downloads *         E:\Downloads
   
   
   PS C:\>

Method 3: Using Command Prompt

1. Open the File Explorer, which you can do by pressing the Windows key and E.
2. Click in the address bar field at the top of the File Explorer window.
3. Type \\localhost or \\127.0.0.1 and press Enter to see your computer's own shared directories over the network. The localhost name is a hostname that refers to the local system which is equivalent to the local loopback address of 127.0.0.1.

[/os/windows/network] permanent link

1. Update the package lists

   Open a terminal window and fetch the latest information about available updates from the remote repositories:

   sudo apt update

2. List packages with available updates

   List every installed package that has a newer version ready to install:

   apt list --upgradable

3. Simulate the update (optional)

   Perform a dry run to see exactly which packages will be upgraded or installed without making any actual system changes:

   sudo apt upgrade -s

4. Apply the updates

   Upgrade all available packages to their latest versions:

   sudo apt upgrade

   To automatically perform distribution upgrades that may add or remove dependencies to complete the update, use sudo apt dist-upgrade or sudo apt full-upgrade instead.

[/os/unix/linux/ubuntu] permanent link

1. Mount the SMB Share on Your Host OS

   Open a terminal window Mount the Windows network share to a local directory on your machine using cifs-utils.

   sudo mkdir -p /mnt/WINSHARE
   sudo mount -t cifs //IP_OR_HOSTNAME/SHARE_NAME /mnt/winshare -o username=USERNAME
   

   Subsitute the name you wish to use for the mount point for WINSHARE, the IP address or hostname for IP_OR_HOSTNAME, the name of the share on the remote computer for SHARE_NAME, and the relevant username for USERNAME. E.g.:

   alice@Wonderland:~$ sudo mkdir -p /mnt/borras_public
   [sudo: authenticate] Password:               
   ailce@Wonderland:~$ sudo mount -t cifs //borras/public /mnt/borras_public -o username=alice
   Password for alice@//borras/public: 
   alice@Wonderland:~$
   

   Verify access by checking if the files appear:

   ls /mnt/winshare

2. Open Wine Configuration

   Launch the Wine configuration utility from the terminal window.

   winecfg

   (If using a specific prefix, issue the command WINEPREFIX=/path/to/prefix winecfg, instead).

3. Add a New Drive Letter

   Select the Drives tab at the top of the winecfg window.

   • Click the Add... button at the bottom.
   • Select an available drive letter (e.g. Z:) from the drop-down menu and click OK.
4. Link the Drive to the Mount Point

   With your new drive letter selected in the list:

   • Locate the Target: input field near the bottom.
   • Enter the path where you mounted the share (e.g., /mnt/winshare) or click Browse... to select it.
   • (Optional) Click Show Advanced and set the drive Type to Network drive.
5. Apply and Test

   To verify the mapping was successful, open Wine's file manager:

   wine winefile

   Your mapped drive letter should now be visible and accessible under My Computer.

[/os/unix/linux/wine] permanent link

You can share a folder on an Ubuntu Linux system with Windows systems using Server Message Block (SMB) by installing Samba, a free and open-source software package. If Samba isn't installed, you can install it as a Debian package with the following commands:

You can verify that the Samba service is running with the command sudo systemctl status smbd; you should see "active (running)".

alice@Wonderland:~$ sudo systemctl status smbd
● smbd.service - Samba SMB Daemon
     Loaded: loaded (/usr/lib/systemd/system/smbd.service; enabled; preset: ena>
     Active: active (running) since Sat 2026-09-12 17:09:53 EDT; 4min 16s ago
 Invocation: 4c72abe09deb445d91cb063be76afc0b
       Docs: man:smbd(8)
             man:samba(7)
             man:smb.conf(5)
   Main PID: 540371 (smbd)
     Status: "smbd: ready to serve connections..."
      Tasks: 3 (limit: 151234)
     Memory: 10M (peak: 11.1M)
        CPU: 161ms
     CGroup: /system.slice/smbd.service
             ├─540371 /usr/sbin/smbd --foreground --no-process-group
             ├─540388 "smbd: notifyd" .
             └─540389 "smbd: cleanupd "

Sep 12 17:09:52 Wonderland systemd[1]: Starting smbd.service - Samba SMB Daemon...
Sep 12 17:09:53 Wonderland update-apparmor-samba-profile[540361]: grep: /etc/appa>
Sep 12 17:09:53 Wonderland update-apparmor-samba-profile[540367]: diff: /etc/appa>
Sep 12 17:09:53 Wonderland systemd[1]: Started smbd.service - Samba SMB Daemon.
alice@Wonderland:~$

Once Samba is installed, you will need to edit the Samba configuration file, smb.conf, to define the shared folder.

[ More Info ]

[/os/unix/linux/network/samba] permanent link

1. On the Nintendo switch, select Nintendo eShop from the menu.
2. When you are presented with a QR code, sccan it and use it to sign into your account at account.nintendo.com.
3. Select Enter Code and enter the download code.
4. After the code is confirmed, select Redeem.

1. Disney Dreamlight Valley: How to Enable Cloud Saves for Cross-Progression
   By: Greysun Morales
   Date: September 6, 2022

[/gaming/nintendo] permanent link

You can view the drive letter mappings used by a Wine prefix from a command-line interface (CLI) on a Linux system by opening a terminal window and entering the command ls -l ~/wineprefix/dosdevices/ where wineprefix is the relevant Wine prefix. E.g., ls -l ~/.wine-collectorz/dosdevices/, if the Wine prefix is .wine-collectorz. I can limit the output to just drive mappings with ls -l ~/.wine-collectorz/dosdevices | grep "[a-z]:" | grep -E '/dev/|/run/media', which pipes the output of the ls through two grep commands. The first looks for lines that have a drive letter, i.e., one of the lowercase letters a through z followed by a colon, e.g., c:, while the second then looks for those lines that have either "/dev/" or "/run/media" in them.

alice@Wonderland:~$ ls -l ~/.wine-collectorz/dosdevices | grep "[a-z]:" | grep -E '/dev/|/run/media'
lrwxrwxrwx 1 alice alice  8 May  4 16:29 d:: -> /dev/sdc
lrwxrwxrwx+1 alice alice  8 May  4 16:29 e:: -> /dev/sr0
lrwxrwxrwx 1 alice alice  8 May  4 16:29 f:: -> /dev/sdd
lrwxrwxrwx 1 alice alice  8 May  4 16:29 g:: -> /dev/sde
lrwxrwxrwx 1 alice alice  8 May  4 16:29 h:: -> /dev/sdf
lrwxrwxrwx 1 alice alice  9 May  4 16:29 i:: -> /dev/sdi1
lrwxrwxrwx 1 alice alice  8 May  4 16:29 j:: -> /dev/sdg
lrwxrwxrwx 1 alice alice  8 May  4 16:29 k:: -> /dev/sdh
lrwxrwxrwx 1 alice alice  9 May  4 16:29 l:: -> /dev/sdg1
lrwxrwxrwx 1 alice alice  8 May  4 16:29 m:: -> /dev/sdi
lrwxrwxrwx 1 alice alice 43 Aug 26 17:47 n: -> /run/media/alice/MS 3
lrwxrwxrwx 1 alice alice  9 May  4 16:29 n:: -> /dev/sdg2
lrwxrwxrwx 1 alice alice  8 May  4 16:29 o:: -> /dev/sdj
lrwxrwxrwx 1 alice alice 47 Sep  3 19:49 p: -> /run/media/alice/Nifler
lrwxrwxrwx 1 alice alice  9 May  4 16:29 p:: -> /dev/sde1
lrwxrwxrwx 1 alice alice  9 May  4 16:29 q:: -> /dev/sde2
lrwxrwxrwx 1 alice alice  9 May  4 16:29 r:: -> /dev/sdc1
lrwxrwxrwx 1 alice alice 43 Jun 27 11:29 s: -> /run/media/alice/MS 2
lrwxrwxrwx 1 alice alice  9 May  4 16:29 s:: -> /dev/sdc2
lrwxrwxrwx 1 alice alice  9 May  4 16:29 t:: -> /dev/sdj1
lrwxrwxrwx 1 alice alice  9 May  4 16:29 u:: -> /dev/sdh1
lrwxrwxrwx 1 alice alice  9 May  4 16:29 v:: -> /dev/sdh2
lrwxrwxrwx 1 alice alice 48 Aug 26 17:47 w: -> /run/media/alice/Willow
lrwxrwxrwx 1 alice alice  9 May  4 16:29 w:: -> /dev/sdf1
lrwxrwxrwx 1 alice alice  9 May  4 16:29 x:: -> /dev/sdd1
lrwxrwxrwx 1 alice alice 43 Jun 27 11:29 y: -> /run/media/alice/MS 1
lrwxrwxrwx 1 alice alice  9 May  4 16:29 y:: -> /dev/sdd2
alice@Wonderland:~$ 

I can use the lsblk -o name,mountpoint,label,size to see the connection between the device designations and the labels on drives.

alice@Wonderland:~$ lsblk -o name,mountpoint,label,size
NAME                        MOUNTPOINT                         LABEL        SIZE
loop0                       /snap/canonical-livepatch/406                  13.5M
loop1                                                                     201.3M
loop2                       /snap/celluloid/322                            21.9M
loop3                       /snap/cups/1238                                47.9M
loop4                       /snap/bare/5                                      4K
loop5                       /snap/chromium-ffmpeg/112                       8.3M
<text snipped>
sda                                                                          20T
├─sda1                                                                       16M
└─sda2                      /run/media/alice MS 4          20T
sdb                                                                        29.3G
└─sdb1                      /run/media/alice             29.3G
sdc                                                                        14.6T
├─sdc1                                                                      499M
├─sdc2                                                                      128M
├─sdc3                      /run/media/alice Windows     14.5T
└─sdc4                                                         Recovery    74.5G
sdd                                                                          20T
├─sdd1                                                                       16M
└─sdd2                      /run/media/alice MS Working    20T
sde                                                                        14.6T
└─sde1                      /run/media/alice Nifler      14.6T
sdf                                                                         4.5T
└─sdf1                      /run/media/alice Oak          4.5T
sdg                                                                        18.2T
├─sdg1                                                         EFI          200M
└─sdg2                      /run/media/alice MS 3        18.2T
sdh                                                                        25.5T
├─sdh1                                                         EFI          200M
└─sdh2                                                         MS 2        25.5T
sdi                                                                        25.5T
├─sdi1                                                         EFI          200M
└─sdi2                      /run/media/alice MS 1        25.5T
sdk                                                                        18.2T
├─sdk1                                                         EFI          200M
└─sdk2                      /run/media/alice YouTube     18.2T
sr0                                                                         4.1G
nvme0n1                                                                     1.8T
├─nvme0n1p1                 /boot/efi                                         1G
├─nvme0n1p2                 /boot                                             2G
└─nvme0n1p3                                                                 1.8T
  └─dm_crypt-0                                                              1.8T
    └─ubuntu--vg-ubuntu--lv /                                               1.8T
alice@Wonderland:~$

You can use the Wine Configuration Tool for a graphical user interface (GUI) view of drive mappings by using a command like WINEPREFIX=$HOME/.wine-collectorz winecfg.

alice@Wonderland:~$ WINEPREFIX=$HOME/.wine-collectorz winecfg
alice@Wonderland:~$

References:

1. How do I list Wine drive letter mappings?
   By: Rovanion
   Date: February 27, 2023
   Stack Exchange - Unix & Linux

Related

1. Creating and using a Wine prefix on an Ubuntu Linux system
   Date: July 31, 2026

[/os/unix/linux/wine] permanent link