Recreating discontinued menu items from Cracker Barrel

I have spent the last week or so being very confused on how to enable the macOS 15.1 Beta onto my M2 MacBook Air. I finally stumbled across the method and it made sense once I found it but it was not very intuitive. There are now two separate macOS 15 beta channels and you will need to open System Settings and navigate to General > Software update > Beta Updates. You will need to choose macOS Sequoia 15.1 Developer beta by clicking on the i symbol to the right.

Once you have selected the new beta channel you Mac should download the update and install it. Once you have installed the update and logged back in you will not immediately have the limited set of Apple Intelligence features. Apple has made them opt-in in order to not bog down their new Private Cloud Compute infrastructure that they are building out. To join the waitlist you will need to open System Settings once again and navigate to the Siri section there is a new Apple Intelligence & Siri section. You will need to select the Join Apple Intelligence Waitlist… button to proceed.

Get past the marketing dialog.

You are now on the waitlist and you should see a preparing dialog.

It took around fifteen minutes for this to happen and you should see the dialog change to enable Apple Intelligence and you should see a notification informing you that the feature is ready to be enabled. I am assuming that somewhere behind the scenes something regarding Apple’s Private Cloud Compute is being created for your device.

Now, you will see a few short dialogs giving you a brief overview of the current Apple Intelligence features.

You are now up and running with Apple Intelligence. It is very much early days and only a very small set of features are available with more to come in the next few months.

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

Recently WordPress has updated their WYSIWYG editor to Gutenberg which is absolutely fantastic!  The only issue thus far is that when editing or updating a post within WordPress you see is the following.

This prevents the auto save and publish functions from working.  WordPress and Cloudflare are working on the issue and have a workaround in place.   The fix involves disabling two rules in the WordPress rules set in the Web Application Firewall settings in your Cloudflare account.

1. Once you are logged in click on the domain that you need to edit.
2. Click on Firewall from the top menu.
3. Scroll down to the section titled IP Firewall Button.
   1. Click the button to the left titled Web Application Firewall.
4. Look for the section titled Package: Cloudflare Rule Set.
   1. Click Rule Details.
5. Scroll down to the section titled Cloudflare WordPress and click the link.
6. Click on page 4 from the pagination at the bottom of the section.
7. Look for the rules WP0025A and WP0025A.
   
8. On the far right side of the section under the Mode heading you will see a drop down list.
9. Choose disable for both rules.
10. You should see a green par across the bottom of the screen indicating that the settings are saved.
11. Click the Close button.
12. Go back to your WordPress Admin area and try to edit a post.

Unfortunately this workaround has never worked for me even after Gutenberg was updated and Cloudflare pushed out patches on their end.  As a last resort I had to whitelist my IP from the Firewall Events section of the Firewall page.

Now I am once again able to edit posts and whatnot in WordPress!

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.

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.

---------- 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. 🙂