WSL1 unfortunately introduces a wonderful new problem of file permissions. Every file on the Windows filesystem NTFS has a set of permissions managed by the filesystem. Every NTFS file that WSL knows about (if mounted with -o metadata) acquires a completely parallel set of file permissions that "mirror" the NTFS permissions but can get out of sync. All sorts of fun results: "With network file systems, DrvFs does not set the correct Linux permissions bits on a file; instead, all files are reported with full access (0777) and the only way to determine if you can actually access the file is by attempting to open it.". This will be fixed by WSL2 which will have an entirely separate filesystem, a Virtual Hardware Disk (VHD). Which will introduce a quite different set of interesting problems. +
WSL1 unfortunately introduces a wonderful new problem of file permissions. Every file on the Windows filesystem NTFS has a set of permissions managed by the filesystem. Every NTFS file that WSL knows about (if mounted with -o metadata) acquires a completely parallel set of file permissions that are fundamentally different things and are never in sync in any sense. All sorts of fun results. This will be fixed by WSL2 (expected May 2020) which will have an entirely separate filesystem, a Virtual Hardware Disk (VHD). Which will introduce a quite different set of interesting problems.
If you are disturbed by the instructions to produce an entirely different key for WSL1 to use when your PC already has a perfectly good PuTTy key installed on the server, then you are right. It is inelegant. But it works, the instructions are shorter and there are fewer things that go wrong. If you are terribly offended by that then you can set your PC up to use one key shared between WSL and normal-Windows as described in this October 2019 article. (Don't set up a password on the key because then you don't need to install keychain.) But beware, this sort of thing goes out of date quite rapidly and WSL2 is looming. diff --git a/handbook/essentials.html b/handbook/essentials.html index 609c38c8b..80c3de8f9 100644 --- a/handbook/essentials.html +++ b/handbook/essentials.html @@ -114,7 +114,7 @@ devise new routes to reach them.
To regenerate the most recent version which contains the cave entrances discovered during expo you will need to ask someone who is competent in logging into the server and running scripts. -
The data is in the version control system repository :loser: in +
The data is in the version control system repository :loser: in
loser/gpx/diff --git a/handbook/gpxupload.html b/handbook/gpxupload.html index 1c4010030..4188171f8 100644 --- a/handbook/gpxupload.html +++ b/handbook/gpxupload.html @@ -86,7 +86,7 @@ to something recognisable such as 'top-camp-to-toilet-grike.gpx' (all lower case GPX data is stored in two places.
GPS tracks are voluminous and we also get a lot of repetition diff --git a/handbook/survey/drawup.htm b/handbook/survey/drawup.htm index 5914479f9..969cd2fbb 100644 --- a/handbook/survey/drawup.htm +++ b/handbook/survey/drawup.htm @@ -66,7 +66,7 @@ as the scanned notes, i.e. (for wallet #19) you would put them in:
The tunnel (or therion) files should NOT stored in the same folder as the scanned notes. They will eventually be uploaded to the version control repository -drawings +drawings but for a first attempt store them on the expo laptop in /home/expo/drawings/{cavenumber}. Look at what is in there already and ask someone whcih directory to put them in. It will probably be a folder like this: /home/expo/drawings/264-and-258/toimport/ . diff --git a/handbook/survey/getin.htm b/handbook/survey/getin.htm index 4d0ada717..3e700d292 100644 --- a/handbook/survey/getin.htm +++ b/handbook/survey/getin.htm @@ -35,7 +35,7 @@ on the expo laptop. These instructions assume that you are using the expo laptop that you are typing it in on the expo laptop. (You can do it fom your own laptop if you have been initiated into the deep magic of the ":loser:" repository of the distributed version control system - see the -list of repositories. +list of repositories.
Now you have been typing this on the expo laptop, and before you let someone else use the laptop you need to find a nerd to do the deep magic to add your -file to the version control repository "loser". Watching the nerd do this is +file to the version control repository "loser". Watching the nerd do this is usually your first initiation into learning how to do it yourself.