Enabling Apple Intelligence on macOS 15.1 (Sequoia) Developer Beta

This is a really weird edge case that I came across at work. After an update to Windows subsystem for Linux (WSL) I was no longer able to use my Cisco AnyConnect VPN connection to connect to any of the infrastructure I manage.

WSL (112) ERROR: CreateProcessParseCommon:782: Failed to translate

Currently, the only method that I have to use a WSL Virtual Machine (VM) is to use this great third party script so that my VM knows how to actually use a network. I do with Microsoft had an easier way to do this, WSL has no network connectivity once connected to a VPN. 🤦🏻‍♂️

At any rate, all of these weird tech issues aside with how I choose to SSH into the systems I manage at work, this is how you correct the error WSL (112) ERROR: CreateProcessParseCommon:782: Failed to translate when attempting to use a WSL VM on a VPN Connection. You will need to edit the .profile folder in your home directory (/home/your_userneame_here) and add the following line to the end of the file.

wsl.exe -d wsl-vpnkit --cd /app service wsl-vpnkit start

To apply the fix, power cycle your WSL VM with your method of choice. I hope this helps and same you time having to search all over the Internet or watch a Youtube “tutorial” what wastes your time. If you have any questions, etc. hit me up via one of the methods on my contact page. Thanks for stopping by! 🙂

---------- On Red Hat Linux ---------- 
$ cat /etc/redhat-release

---------- On CentOS Linux ---------- 
$ cat /etc/centos-release

---------- On Fedora Linux ---------- 
$ cat /etc/fedora-release

---------- On Debian Linux ---------- 
$ cat /etc/debian_version

---------- On Ubuntu and Linux Mint ---------- 
$ cat /etc/lsb-release

---------- On Gentoo Linux ---------- 
$ cat /etc/gentoo-release

---------- On SuSE Linux ---------- 
$ cat /etc/SuSE-release

AS you can see this various depending on on which form of the original Linux Operating System so I usually end up searching for this as it is not something that I use day to day in my professional or work life. I hope it makes somees’s day that much easier. 🙂

Some of these are pretty basic and some are a bit more advanced and/or obscure in my opinion. I hope they are also useful to others out there. Please not that files names and file paths are just made up examples and might not fit what you are attempting to accomplish.

• cd – change directory
• Carl + c – cancels the currently running foreground operation
• pod – s/how your current fill file path
• cp /path/to/file.txt /path/to/your/new/file.txt – copy a file from one location to another location
• move (rename) a file from one location to another location – mv file1.txt file1.back.txt
• show the tail end of a file with any new additions that are written to the file – tail -f /var/log/messages.log
• determine if a node is online – ping duck.com
• determine the network route to a given node – trace route duck.com
• perform a DNS lookup on a given address – nslookup duck.com
•  show xx number of lines at the tail end of a file – Show the tail end of a file with any additions – tail -f /var/log/messages
• run a shell script – bash shellscript.sh OR sh shellscript.sh
• check drive mappings for the currently mounted file system – do -h
• change to another system user – su username
• easy way to change to the root user if you have sudo level access – sudo -i

I keep having to look this up so I might as well save myself some time. 😉

• From the UNRAID Web UI stop the RAID array under Main > Array Options > Stop Array.
• When the UI reloaded go to Settings > Docker.
  • You should now be able to change the size of the array in GB.
• Click the Save button.
• Start the RAID array back up.

If you use the popular Homebrew package manager on MacOS you are very familar with running something similar to this command on a regular basis.

brew update && brew upgrade && brew cleanup

this type of command informs Homebrew to update it’s list of package versions, locate any that need to be updated, and clean up any left over files generated by there processes. If you remember to run this all the time then it is a pretty quick command, but if like me, you forget to do this for weeks or months at a time it can start to take quite some time to finish it’s maintenance.

Yesterday, I was looking into ways to automate this process through adding the command to Cron or to have Cron run a shell script or apple script file with the commands in it. After some quick searching on my search engine of choice, Kagi, I found a great Github project called Homebrew Autoupdate.

The project describes itself thusly.

An easy, convenient way to automatically update Homebrew.

This script will run brew update in the background once every 24 hours (by default) until explicitly told to stop, utilising launchd.

brew upgrade and brew cleanup can also be handled automatically, but are optional flags.

Notifications are enabled by default using a new, code-signed, universal AppleScript applet.

https://github.com/DomT4/homebrew-autoupdate

If you decide to install this project every morning you can look forward to notifications like this.

Do you already use this project? If you tried it, what did you think? Hit me up on Mastodon or my Contact page so we can discuss it or you can ask me any questions you might have.

In my day job I recently came across a much easier was to deal with file and/or directory permissions on Linux based systems. Typically, to determine the permissions of a file or directory you would use the ls command with various potions appended to the end of the command and to change the same file or directory’s permissions you would use the chmod command. As I recently discovered the chmod is also able to clone or copy permissions as well as manually set them.

To lustrate what I ma talking about let’s create a hypothetically example where we have two files with the following permissions.

$ ls -l file*
-rwxr-xr--. 1 lrendek lrendek 0 Apr  7 14:39 file1
-rw-rw-r--. 1 lrendek lrendek 0 Apr  7 14:40 file2

If we wanted to copy the permissions from file 1 onto file2 we would run the following option appended to the chmod command.

$ chmod --reference=file1 file2

As we can see the permissions for file2 have been cloned from file1.

$ ls -l file*
-rwxr-xr--. 1 lrendek lrendek 0 Apr  7 14:39 file1
-rwxr-xr--. 1 lrendek lrendek 0 Apr  7 14:40 file2

If we extend this example further we can also clone the permissions of a directory as well!

$ ls -ld dir*
d--x--x--x. 2 lrendek lrendek 40 Apr  7 14:52 dir1
drwxrwxr-x. 2 lrendek lrendek 40 Apr  7 14:52 dir2
$ chmod --reference=dir1 dir2
$ ls -ld dir*
d--x--x--x. 2 lrendek lrendek 40 Apr  7 14:52 dir1
d--x--x--x. 2 lrendek lrendek 40 Apr  7 14:52 dir2

I had a little bit of an issue finding this but stubbled across this site that provided me with the syntax and examples. Although, I am making this entry mainly for myself but I also hoping that this post will make another Sys. Admin. Job easier. Uf you have any questions, comments, etc. please feel free to contact me on my Contact page or on Twitter.