The one in January being 2024-W01 and the one in December 2025-W01.
🤓
(Hmmm, my printed LaTeX calendar using tikz-kalender gets it wrong or uses different week definitions. It shows next week as 53. 🤔)
The one in January being 2024-W01 and the one in December 2025-W01.
🤓
(Hmmm, my printed LaTeX calendar using tikz-kalender gets it wrong or uses different week definitions. It shows next week as 53. 🤔)
The one in January being 2024-W01 and the one in December 2025-W01.
🤓
(Hmmm, my printed LaTeX calendar using tikz-kalender gets it wrong or uses different week definitions. It shows next week as 53. 🤔)
The one in January being 2024-W01 and the one in December 2025-W01.
🤓
(Hmmm, my printed LaTeX calendar using tikz-kalender gets it wrong or uses different week definitions. It shows next week as 53. 🤔)
fisherman.
fisherman.
/bin/sh
/bin/sh
zsh on macOS, or do you change it to, say, bash?
$ diff -Ndru <(restic snapshots | grep minio | awk '{ print $1 }' | sort -u) <(restic snapshots | grep minio | awk '{ print $1 }' | xargs -I{} restic forget -n {} | grep -E '\\{.*\\}' | sed -e 's/{//g;s/}//g' | sort -u) | tee | wc -l; echo $?
0
0
$ diff -Ndru <(restic snapshots | grep minio | awk '{ print $1 }' | sort -u) <(restic snapshots | grep minio | awk '{ print $1 }' | xargs -I{} restic forget -n {} | grep -E '\{.*\}' | sed -e 's/{//g;s/}//g' | sort -u) | tee | wc -l; echo $?
0
0
$ diff -Ndru <(restic snapshots | grep minio | awk '{ print $1 }' | sort -u) <(restic snapshots | grep minio | awk '{ print $1 }' | xargs -I{} restic forget -n {} | grep -E '\{.*\}' | sed -e 's/{//g;s/}//g' | sort -u) | tee | wc -l; echo $?
0
0
Yeah, glossy screens are straight from hell. :-D What's this spooky wind chime background music?
Anyway, have great fun learning more and experimenting with this low level stuff!
#catsoftwtxt
/https://baldo.cat/media/photos/IMG_3102.jpeg) #catsoftwtxt
#catsoftwtxt
jenny; that’s, it’s “jenny”, not “Janny”. You missed how to reply to others, and how to find those who “follow” you, which will require to mention the current extensions.
> So, just a hobby. It won't be big and professional like GNU, then?
Ha! 😅 No, that certainly won’t happen this time. 🥴
(What an exciting time that was when there were *new* operating systems. 🤔)
> So, just a hobby. It won't be big and professional like GNU, then?
Ha! 😅 No, that certainly won’t happen this time. 🥴
(What an exciting time that was when there were *new* operating systems. 🤔)
> So, just a hobby. It won't be big and professional like GNU, then?
Ha! 😅 No, that certainly won’t happen this time. 🥴
(What an exciting time that was when there were *new* operating systems. 🤔)
> So, just a hobby. It won't be big and professional like GNU, then?
Ha! 😅 No, that certainly won’t happen this time. 🥴
(What an exciting time that was when there were *new* operating systems. 🤔)
/https://duque-terron.cat/media/photos/terron.jpg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/baldo.jpg) #catsoftwtxt
#catsoftwtxt
I don’t plan on making that code public. This is purely a learning project for myself. I think going for real-mode 8086 + BIOS is a good idea as a *first step*. I am well aware that this isn’t going anywhere – but now I’ve gained some experience and learned a ton of stuff, so maybe 32 bit or even 64 bit mode might be doable in the future? We’ll see.
It provides a syscall interface, can launch processes, read/write files (in a very simple filesystem).
Here’s a video where I run it natively on my old Dell Inspiron 6400 laptop (and Warp 3 later in the video, because why not):
https://movq.de/v/893daaa548/los86-p133-warp3.mp4
(Sorry for the skewed video. It’s a glossy display and super hard to film this.)
It starts with the laptop’s boot menu and then boots into the kernel and launches a shell as PID 1. From there, I can launch other processes (anything I enter is a new process, except for the exit at the end) and they return the shell afterwards.
And a screenshot running in QEMU:
I don’t plan on making that code public. This is purely a learning project for myself. I think going for real-mode 8086 + BIOS is a good idea as a *first step*. I am well aware that this isn’t going anywhere – but now I’ve gained some experience and learned a ton of stuff, so maybe 32 bit or even 64 bit mode might be doable in the future? We’ll see.
It provides a syscall interface, can launch processes, read/write files (in a very simple filesystem).
Here’s a video where I run it natively on my old Dell Inspiron 6400 laptop (and Warp 3 later in the video, because why not):
https://movq.de/v/893daaa548/los86-p133-warp3.mp4
(Sorry for the skewed video. It’s a glossy display and super hard to film this.)
It starts with the laptop’s boot menu and then boots into the kernel and launches a shell as PID 1. From there, I can launch other processes (anything I enter is a new process, except for the exit at the end) and they return the shell afterwards.
And a screenshot running in QEMU:
I don’t plan on making that code public. This is purely a learning project for myself. I think going for real-mode 8086 + BIOS is a good idea as a *first step*. I am well aware that this isn’t going anywhere – but now I’ve gained some experience and learned a ton of stuff, so maybe 32 bit or even 64 bit mode might be doable in the future? We’ll see.
It provides a syscall interface, can launch processes, read/write files (in a very simple filesystem).
Here’s a video where I run it natively on my old Dell Inspiron 6400 laptop (and Warp 3 later in the video, because why not):
https://movq.de/v/893daaa548/los86-p133-warp3.mp4
(Sorry for the skewed video. It’s a glossy display and super hard to film this.)
It starts with the laptop’s boot menu and then boots into the kernel and launches a shell as PID 1. From there, I can launch other processes (anything I enter is a new process, except for the exit at the end) and they return the shell afterwards.
And a screenshot running in QEMU:
I don’t plan on making that code public. This is purely a learning project for myself. I think going for real-mode 8086 + BIOS is a good idea as a *first step*. I am well aware that this isn’t going anywhere – but now I’ve gained some experience and learned a ton of stuff, so maybe 32 bit or even 64 bit mode might be doable in the future? We’ll see.
It provides a syscall interface, can launch processes, read/write files (in a very simple filesystem).
Here’s a video where I run it natively on my old Dell Inspiron 6400 laptop (and Warp 3 later in the video, because why not):
https://movq.de/v/893daaa548/los86-p133-warp3.mp4
(Sorry for the skewed video. It’s a glossy display and super hard to film this.)
It starts with the laptop’s boot menu and then boots into the kernel and launches a shell as PID 1. From there, I can launch other processes (anything I enter is a new process, except for the exit at the end) and they return the shell afterwards.
And a screenshot running in QEMU:
beautiful day out. the holiday distance classic was today too it turns out so plenty of runners to run with on the way back in. did pretty much 5km intervals. did not realize it but could have possibly broke my PB in the half marathon... oh well, great run!
#running
beautiful day out. the holiday distance classic was today too it turns out so plenty of runners to run with on the way back in. did pretty much 5km intervals. did not realize it but could have possibly broke my PB in the half marathon... oh well, great run!
#running
beautiful day out. the holiday distance classic was today too it turns out so plenty of runners to run with on the way back in. did pretty much 5km intervals. did not realize it but could have possibly broke my PB in the half marathon... oh well, great run!
#running
https://movq.de/v/a6dc0491a9/s.png
https://movq.de/v/a6dc0491a9/s.png
https://movq.de/v/a6dc0491a9/s.png
https://movq.de/v/a6dc0491a9/s.png
> Early on, I was thinking about WAN IP address changes as well but it hasn't happened in ~2.5 years with this ISP.
You mean to say you have the same public IP all the time? For 2.5 years now? Without paying extra? 🤔~
> Early on, I was thinking about WAN IP address changes as well but it hasn't happened in ~2.5 years with this ISP.
You mean to say you have the same public IP all the time? For 2.5 years now? Without paying extra? 🤔~
> Early on, I was thinking about WAN IP address changes as well but it hasn't happened in ~2.5 years with this ISP.
You mean to say you have the same public IP all the time? For 2.5 years now? Without paying extra? 🤔~
> Early on, I was thinking about WAN IP address changes as well but it hasn't happened in ~2.5 years with this ISP.
You mean to say you have the same public IP all the time? For 2.5 years now? Without paying extra? 🤔~