I am using wsjt-x (latest version) in Mint Linux. Works beautifully. However, when I go to upload the .ADI file to QRZ, it's not accessible. I have to use file manager to navigate to /.local/share/wsjt-x, find the .ADI file, copy it to desktop. Then go upload where it is easily found. Why does wsjt-x have to store the .ADI file in an inaccessible place? Is there a way to set it so it simply saves it to a folder/location of my choice?

On Nov 25, 2022, at 2:45 PM, Martin G0HDB <marting0hdb@...> wrote:

On Thu, Nov 24, 2022 at 05:24 PM, w1av wrote:

I am using wsjt-x (latest version) in Mint Linux. Works beautifully. However,
when I go to upload the .ADI file to QRZ, it's not accessible. I have to use
file manager to navigate to /.local/share/wsjt-x, find the .ADI file, copy it
to desktop. Then go upload where it is easily found. Why does wsjt-x have to
store the .ADI file in an inaccessible place? Is there a way to set it so it
simply saves it to a folder/location of my choice?

I'm a very long way from being a Linux expert but there appears to be an equivalent command to the 'mklink' command in Windows which I use to create a 'directory junction' between the default Windows folder where WSJT-X stores its 'stuff' including the wsjtx_log.adi log file and another more easily accessible folder, which in my case is on a different drive.

The exact mklink command I use is:

mklink /J "C:\Users\<username>\AppData\Local\WSJT-X" "E:\WSJT-X\User Data"

This creates a junction between the default folder that WSJT-X uses and the location on my E: drive. WSJT-X continues to read from and write to the default location but in reality all the files etc are actually stored on the E: drive and are more accessible.

A quick search reveals the 'ln' command in Linux; it's apparently used to create symbolic links that can be between folders. Perhaps someone more versed in Linux can provide more specific information on how to create a 'junction' between /.local/share/wsjt-x and another folder elsewhere.

73
--
Martin G0HDB

On Nov 26, 2022, at 8:08 AM, David Herring via groups.io <david.n5dch@...> wrote:

In linux and UNIX, the ln command can be used to create both soft (symbolic) links and hard links. On the surface, it would look like the linux hard link would be roughly the equivalent of a junction in windows. However, linux does not permit the hard linking of directories. At least not for users. It has the potential to create infinite loops (through accident, stupidity or abuse) in the filesystem which can render the system unusable.

So the way to safely achieve the same thing would be to use the mount command.

Where olddir is the directory where the files are that you want to access from somewhere else, and newdir is the somewhere else (the new place where you will access the contents of olddir)...

Create a new empty directory, or use an existing one but make sure it is empty:
# mkdir newdir

Then from the command line, execute the mount:
# mount —bind oldir newdir

At this point, you should be able to access the content of olddir from newdir.

To make this a permanent mount, you could edit the /etc/fstab (or equiv on your distribution if different) and add the following line:

/olddir /newdir none bind

Then every time you boot up, newdir will be mounted to olddir automatically.

All of this is a general guide. You may have to tinker around with it to make it work in your specific instance and flavor of linux, but in general this is how you would do it.

Now, having said all that, I question why it is is even necessary (obviously other than for convenience). IIRC, the origin of this query was because you could not access olddir directly from wsjt-x, correct? I would focus on solving that. If it’s a permissions problem, for example, then this mount trick still might not solve it for you. If it’s a matter of not being able to access some dot directory (e.g. .mystuff), then you may need to read up on your distro’s file manager and configure it to unhide hidden files.

GL!

73,
Dave - N5DCH

On Nov 25, 2022, at 2:45 PM, Martin G0HDB <marting0hdb@...> wrote:

On Thu, Nov 24, 2022 at 05:24 PM, w1av wrote:

I am using wsjt-x (latest version) in Mint Linux. Works beautifully. However,
when I go to upload the .ADI file to QRZ, it's not accessible. I have to use
file manager to navigate to /.local/share/wsjt-x, find the .ADI file, copy it
to desktop. Then go upload where it is easily found. Why does wsjt-x have to
store the .ADI file in an inaccessible place? Is there a way to set it so it
simply saves it to a folder/location of my choice?

I'm a very long way from being a Linux expert but there appears to be an equivalent command to the 'mklink' command in Windows which I use to create a 'directory junction' between the default Windows folder where WSJT-X stores its 'stuff' including the wsjtx_log.adi log file and another more easily accessible folder, which in my case is on a different drive.

The exact mklink command I use is:

mklink /J "C:\Users\<username>\AppData\Local\WSJT-X" "E:\WSJT-X\User Data"

This creates a junction between the default folder that WSJT-X uses and the location on my E: drive. WSJT-X continues to read from and write to the default location but in reality all the files etc are actually stored on the E: drive and are more accessible.

A quick search reveals the 'ln' command in Linux; it's apparently used to create symbolic links that can be between folders. Perhaps someone more versed in Linux can provide more specific information on how to create a 'junction' between /.local/share/wsjt-x and another folder elsewhere.

73
--
Martin G0HDB