Somewhat long #Unix #Unix50 toot
The OS I use daily is turning 50, depending on how you define its start. #Unix50
On #Unix's 40th birthday, the IEEE's Spectrum magazine told of its start like this: https://web.archive.org/web/20190228090043/https://spectrum.ieee.org/computing/software/the-strange-birth-and-long-life-of-unix/0
The 50th anniversary of Unix is particularly reminding me of my age because I was born within days of its manual's first edition: https://www.bell-labs.com/usr/dmr/www/1stEdman.html
Thankfully, *that* anniversary is still 2 years off. :p
"Unix at 50: How the OS that powered smartphones started from failure": https://arstechnica.com/gadgets/2019/08/unix-at-50-it-starts-with-a-mainframe-a-gator-and-three-dedicated-researchers/
Huh. Following the boot splash instructions in the #FreeBSD Handbook https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-splash.html burned me because, for whatever reason, my PC starts up at 1920x1080, not vesa, before the boot menu. I think it kernel-panicked because it kept rebooting.
To boot successfully again, I had to get a loader prompt (option 3) & type:
disable-module vesa
boot
pictured: my computer den
https://www.youtube.com/watch?v=a6yZq6liDeM
Last night, I stayed up entirely too late writing a howto for something pretty neat: How to add site search to a static website.
https://thornton2.com/net/search-howto.html
I tried to cover a few ways and link to good pages on two I think are neat but can't use.
Apple MacOS rant
This therapeutic video is 13 years old now. It's still pretty good at calming me down about modern Mac stuff. https://www.youtube.com/watch?v=GWxC8ezE4Dk
Apple MacOS rant
#Unix & #Linux: Can kill just about any kind of process & shuts down when you tell it to.
#Windows: Tasks can stop themselves from being ended, especially tasks not responding. But ending them to shut down? No problem, mate! Shutting dow--UPDATE TIEM!
#MacOS: "Hold my beer." (Gives you a spinning beachball.)
And that tripped me up in some subtle ways. I actually needed `ENV=/home/arielmt/.shrc` instead, and to source it on cronjob lines. Now all my jobs are working properly & my crontab looks nice and neat. I updated the page I posted earlier because it was wrong. Double oops.
It turns out I needed `SHELL=/bin/sh` and `ENV=$HOME/.shrc` in my crontab and `PATH=` statements in my .shrc file. Oops.
I just had to figure out why a shellscript working perfectly was refusing to do anything, even quit, as a cronjob. I knew the cron environment was a bit different, but I didn't realize how much, or how to troubleshoot it effectively. Fixed: https://thornton2.com/unix/freebsd/simulate-cron-env.html
Boost this if you see your kink:
Girls
Being gay for girls
Cuddling girls
Holding hands with girls
Talking about doing things with girls
Kissing girls
Loving girls
Thinking about girls
All girls
Just girls
Girls
Going out on dates with girls
Chatting with girls
Spending time together with girls
Being friends with girls
Being girls
Nobody will know which one >.<
✨ Kind 'Net Help Desk fairy by day. ✨
✨ Weird & furry Unix fairy by night. ✨
✨ Sometimes a retrocomputer fairy. ✨
✨ Pays the ComputerFairi.es bills. ✨
✨ Sparkly✨shellscript✨princess. ✨
✨ Age: Mere days younger than ✨
✨ the Intel 4004 & Unix 1st Edition. ✨
✨ Follow requests welcome. ✨
✨
✨