After having read what horrors people experienced when they upgrade their Hugo binaries, I made sure that I've kept the version that I used to make my test site & also consequently use *that* version to continue to teach myself a higher level of fluency in the markdown language

`hugo version`
hugo v0.140.2-aae02ca612a02e085c08366a9c9279f4abb39d94+extended linux/amd64 BuildDate=2024-12-30T15:01:53Z VendorInfo=gohugoio

#bash #sh #zsh #ksh #csh #Hugo #Linux #POSIX #FOSS #100daysofCode #640DaysOfCode #1024DaysOfCode #programming

The screencap shows a text editor window with a dark background and white text. The title bar at the top of the window displays several tabs, including "draft = true," "title = 'Eightpost'," and others like "mc-a," "cafe," "RemAD," "Azureus," "Banagado," "Poderoso," and "CMOS." The main content area of the window contains a Markdown document with various formatting examples.

The document includes:

A code block with text separated by CR/LF and embraced with code version including end braces.

A bullet list with items such as "just a little list," "with bullets," "simple and easy," and "asterisk away."

A numeric list with items like "numeric list," "no its an ordered list see https://www.markdownguide.org/basic-syntax/," "just type period," "1. indents also possible!," "2. clean and smooth," "4. very smooth and easy," "5. Even songs can be inserted," and "6. Johnny be good."

The bottom right corner of the window shows the cursor position (12, 20) and the word "Bot."

Ovis2-8B

🌱 Energy used: 0.247 Wh

**Dendrobatus Azureus** @Dendrobatus_Azureus@bsd.cafe · Apr 12

Apr 12

Dendrobatus Azureus @Dendrobatus_Azureus@bsd.cafe

$ alias 'rm = rm -i'

This is a standard alias in all my POSIX installations
I use it to curb accidental removal incidents of important and large directory trees

#bash #sh #zsh #ksh #csh #freeBSD #Linux #POSIX #FOSS #100daysofCode #640DaysOfCode #1024DaysOfCode #programming

**Dendrobatus Azureus** @Dendrobatus_Azureus@bsd.cafe · Feb 13 *

Feb 13 *

Dendrobatus Azureus @Dendrobatus_Azureus@bsd.cafe

Do you remember me talking about this wonderful article? the one where you are taught in detail with source snippets how Linux goes bye-bye when it goes to sleep?
The article has so much in-depth details that it takes a lot of time, considerable inteligencia & knowledge to process. Contrary to others I will not only say it, I will explicitly state it is fascinating and a heavy read.

Take your time to process the article; it's worth learning this in depth, in miniatures detail, all the way down to the sources, so you know what goes on, when the power management or your Linux powered VM, or Linux powered Hardware machine, goes down, hard, inexplicable:

To you it will become explainable!

#bash #sh #zsh #ksh #csh #tsh #PowerManagement #sleep #hibernate #Linux #POSIX #FOSS #100daysofCode #640DaysOfCode #1024DaysOfCode #programming #GCC #gplusplus #gdb

https://tookmund.com/2024/09/hibernation-preparation

The code snippet is from the file "kernel/power/main.c:688". It defines a static function named "decode_state" that takes a "con" argument. Inside the function, there are preprocessor directives using "#ifdef CONFIG_SUSPEND". It declares variables "state" of type "suspend_state_t", a character pointer "p", and an integer "len". The code uses "memchr" to find a newline character in a buffer and calculates the length. There's a comment "/* Check hibernation first. */" and an if statement that checks the length and a string prefix, potentially returning "PM_SUSPEND_MAX". Another "#ifdef CONFIG_SUSPEND" section includes a for loop that iterates through suspend states, comparing labels and lengths, and potentially returning the "state". Finally, the function returns "PM_SUSPEND_ON". Below the code, there's a comment stating: "Could we have figured this out just via function names? Sure, but this way we".

**Dendrobatus Azureus** @Dendrobatus_Azureus@bsd.cafe · Feb 11 *

Feb 11 *

Dendrobatus Azureus @Dendrobatus_Azureus@bsd.cafe

I'm one of those individuals who just started reading the manual of golang from beginning to end

I'm a serious as your next heart attack. Please don't get one

So I want to pick up a golang again because I only sat and read the manual, just for fun, just like I did when I was sitting and reading the manual for the Yamaha RD400 two stroke, decades ago, one of the most powerful street legal engines that Yamaha made in the 2-stroke version.

One thing I can tell you about that bike

IMHO, the Yamaha RD400 two stroke, is one of the most beautiful bikes that Yamaha has ever created

The RD400 two-stroke by Yamaha is one of the most wonderful two-stroke engines the Yamaha has put on a frame made it street legal so we could ride it without being a racer.

The only caveat is that you had to ride it on a circuit anyway

The Yamaha RD400 could go 360 km/h easily, without even Breaking The 12000 RPM Barrier. The bike could do 16,000 RPM with the proper mechanical motifications made by many powerfull race Brands. Doe K&N and Kerker ring a bell?

It's with the same dedication that I read the manual of golang, from bottom to bottom, top to top, side to side and diagonal to diagonal.

Then my workstation died

Let's take 60 seconds of silence for the death of my workstation.

I didn't mourn its death, but I stopped playing with golang.

Now I'm back, playing again with golang!

No who says programming isn't Fun

#bash #sh #zsh #ksh #csh #golang #Linux #POSIX #FOSS #100daysofCode #640DaysOfCode #1024DaysOfCode #Alphabet #programming #MacOS

https://go.dev/

Recent searches

Search options

Administered by:

Server stats:

#1024daysofcode