This article is the first of a four-part series on building your own NAS on FreeBSD. This series will cover:

1. Selecting a storage drive interface that meets your capacity and performance requirements both now and into the future.
2. Why it makes sense to build your own NAS using FreeBSD rather than installing a NAS distribution (even a FreeBSD-based one). We’ll also discuss which configuration and tuning settings are needed.
3. The nitty-gritty on sharing: configuring NFS, Samba, and iSCSI shares.
4. Software maintenance and monitoring your NAS. //

https://klarasystems.com/articles/part-2-tuning-your-freebsd-configuration-for-your-nas/

https://klarasystems.com/articles/part-3-building-your-own-freebsd-based-nas-with-zfs/

 find . -iname "foo*" | while read f
 do
     # ... loop body
 done

Alternate:

 $ for x in *; do echo "file: '${x}'"; done

or

  for x in * 
  do 
      echo "file: '${x}'"
  done

Most of us wish we had more than 24 hours in a day to get everything done and actually breathe. What if each day gave us more than double that time? If it wasn’t for a phenomenon that put the lengthening of Earth’s days on pause billions of years ago, that would have probably happened.

Earth has not always had 24-hour days. There were fewer than 10 hours in a day when the Moon first came into being around 4.5 billion years ago, but they have grown longer as lunar tidal forces gradually slowed Earth’s rotation. But there was a long period when days didn’t grow at all. Astrophysicists have now found that, from 2 billion to 600 million years ago, days were about 19.5 hours because several tidal forces canceled each other out and kept Earth rotating at the same speed for over a billion years. If that had never happened, our present days might be over 65 hours long.

“The fact that the day is 24 hours long…is not a coincidence,” the research team said in a study recently published in Science Advances.

https://www.science.org/doi/10.1126/sciadv.add2499

Many times when writing Shell scripts, you may find yourself in a situation where you need to perform an action based on whether a file exists or not.

In Bash, you can use the test command to check whether a file exists and determine the type of the file.
The test command takes one of the following syntax forms:

 test EXPRESSION
 [ EXPRESSION ]
 [[ EXPRESSION ]]

If you want your script to be portable, you should prefer using the old test [ command, which is available on all POSIX shells. The new upgraded version of the test command [[ (double brackets) is supported on most modern systems using Bash, Zsh, and Ksh as a default shell.

Clive Robinson • July 5, 2023 12:46 PM

@ Bruce, ALL,

Re : Descent into chaos and noise.

“A recent paper showed that using AI generated text to train another AI invariably “causes irreversible defects.””

As I’ve indicated before that is to be expected when you understand how these neural network based systems work.

There is not the space on this blog to go through the maths and the effort to make formula via UTF-8 glyphs is beyond most mortal flesh and blood can stand.

So an analogy instead[1]…

We know that various things like gongs, wine glasses, bottles and certain types of edges can cause musical notes, due to the build up and loss of energy in resonators.

The thing is appart from the repeyative banging on the gong, all of these resonators gain their energy from near random chaotic input.

You can see this with the wet finger on the wine glass rim. If you move your finger too quickly or too slowely then the body of the glass does not resonate. You can calculate the best speed fairly simply, but it’s even simpler just to get a little practice in. //

Well those nueral networks kind of work that way. You give them a stochastic –random– source and the network in effect resonates –parrots– to it which produces the ouput. Whole musical phrases and entire tunes can be held in the weights.

The weights come about by feeding in tunes and finding the errors and feeding the errors back to adjust the weights.

The point is the network can become “tuned” to a type of music or even just a composer. Which means the filter selects out of the random stream characteristics that match the type of music or the composer.

But each output from the network has differences, to the original music based on residual errors in the system. Yes it sounds to us like the type of music or in the style of the composer, but it’s different by those errors.

Feed that error laden output in as training data and the errors will build up over each iteration, as you would expect.

It’s like the “photocopy of the photocopy” or the “boot-leg tape of the boot-leg tape” each generation adds more noise that changes the network.