#1000daysofcode — Public Fediverse posts

@mff @nixCraft

@mff @nixCraft

'vim'

without any file name is all you need to type in your Bash to see the welcome screen of vim.
Bram Molenaar who created vim on the Commodore Amiga, even tells how you can support Children in Uganda, if you bother to read the help file in its initial headers. The information was updated, for as far as I know, until his departure of life.

I'm currently on mobile otherwise I would have put up in a screenshot

#vim #VimMasterRace #BramMolenaar #Amiga #C64 #bash #sh #zsh #ksh #csh #tsh #freeBSD  #100DaysOfCode #1000DaysOfCode #POSIX #Programming #Patch #RetroComputing #UNIX #History

If you haven't done so yet and you are playing with Open Source Operating Systems, read this article about the BSD family

it is very enlightening, and worth every minute of reading it

#bash #sh #zsh #ksh #csh #tsh #freeBSD  #100DaysOfCode #1000DaysOfCode #POSIX #Programming #Patch #UNIX #History

https://it-notes.dragas.net/2025/03/23/osday-2025-why-choose-bsd-in-2025/

@samurro

The fact that you take on the time to react is a Plus. The fact that you have taken the time to read up on the article of Stefano is another Plus.

Any reaction is a good reaction.

Contrary to certain people on certain sections of the internet, I cannot be offended by anything that I read upon in a reaction towards me on the internet.

You put an interesting Twist on it which I have looked up on also.
Technology should not move on for the fact of moving on.

Software should not be dropped just because other software has been developed and works well if the previous software is good solid and **stable**

Contrary to what you may believe, it has nothing to do with being a greybeard or not. It has more to do with the fact that you should not, as a distribution maintenance team, drop a command set, which has no negatives in comparison with the new one, especially not if the established command set does not take a significant amount of space in comparison with a new one.

The beauty of OpenSource computing is that many different points of view can concurrently exist without sending any negative energy towards each other

Just look for example at Gnome and KDE. In the beginning I could use both because both Gnome and KDE were easily modified. When Gnome went a different direction I dropped using it. However there were still many hundreds of thousands of people who liked the way Gnome went
Just as there were also many hundreds of thousands of people who loved the way that KDE kept going.

Now we are decades further and the Smart Ones under us realize that Gnome needs KDE to exist and visa versa.

That's The Beauty and The Power of Open Source.

Have a good day My Man

#bash #sh #zsh #ksh #csh #tsh #freeBSD  #100DaysOfCode #1000DaysOfCode #POSIX #Programming #Patch #RetroComputing #UNIX #History

When I need docs I do

`man command'

When I pressed F1 in a gui program it did the following

* Request a helper running in my DE to parse a html page
* Ask the helper to open my default html parser
* __Without asking me__ the helper opened a __massive browser__ ravaging ram just to show me what I could find with
`man command`
* I wonder why instead the Ui program did not do the following

* request a helper open a (ba)sh
* parse >man command to the helper
* have the helper display the manpage in the sh

The results would be
* Much less resources used
* No assumption on my current internet connection would be made
* That method has worked for 60 years

<IRC>
/m shakes head and looks at the massive browser showing the equivalence of a manpage
</IRC>

@altbot

🖋️ #bash #sh #zsh #ksh #csh #qBittorrent #torrent #manpage #man1 #F1 #F1Help #WomenWhoCode #640daysofcode #301daysofcode #730daysofcode #100DaysOfCode #1000DaysOfCode #Linux #POSIX #Programming #DEVCommunity #RetroComputing

https://github.com/qbittorrent/qBittorrent/wiki/Frequently-Asked-Questions

Still reading the lengthy article regarding SystemD on Wikipedia this is another interesting excerpt

In April 2014, Linus Torvalds expressed reservations about the attitude of Kay Sievers, a key systemd developer, toward users and bug reports in regard to modifications to the Linux kernel submitted by Sievers. In late April 2014, a campaign to boycott systemd was launched, with a website listing various reasons against its adoption.

#bash #sh #zsh #ksh #csh #tsh #freeBSD #100DaysOfCode #1000DaysOfCode #POSIX #Programming #Patch #RetroComputing #UNIX #History #SystemD

@duncan_bayne

I started to dislike SystemD more and more, as I saw that most distributions were putting hooks for SystemD in case a user would want to switch to it and started with one of the other options initially, on that particular installation.
With the hooks in place that process usually goes seamlessly.

In my proud opinion, if you don't want to use SystemD, nothing of it should ever be on your system

Now I can easily achieve that by just building my Linux from scratch, and I'm not talking about the Linux from scratch distribution, I'm talking about the way I did it when Linux was initially pushed into alt.binaries.Unix many decades ago.

All variants of *BSD have made sure that all the commands which could break, like the ifconfig commands suite we're simply fixed!

But this is the the dilemma that you will get, when the kernel is just built for itself and it's not a coherent part of the base Operating System.

What you get in practice is that your kernel wants to move a certain way, while the userland software wants to move in a different way

That kind of friction would kill a human corpus. On Linux systems and servers it literally breaks things in an unexpected manner, something that you cannot afford when you're running a database where you get two million calls an hour. A database that runs in high availability with just one other VM as a concurrent live backup

#bash #sh #zsh #ksh #csh #tsh #freeBSD #100DaysOfCode #1000DaysOfCode #POSIX #Programming #Patch #RetroComputing #UNIX #History

I did not know that SystemD created such a fuzz & FUD in the Debian community, that people resigned their positions in the Year 2014, because it was impossible to maintain with SystemD, there there was such an amount of friction within the FOSS community that regular maintenance became impossible, heavy stress levels were triggered for these Atma's!

https://en.wikipedia.org/wiki/Systemd?wprov=sfla1

#bash #sh #zsh #ksh #csh #tsh #freeBSD #100DaysOfCode #1000DaysOfCode #POSIX #Programming #Patch #RetroComputing #UNIX #History

/3

Mind you that I'm not saying that new command should not be developed, on a contrary; what I am saying, is that if for whatever reason, certain things change, you need to make sure that the older commands still work properly, because they are in our muscle memory
Those of us, the greybeards, have commands in our muscle memory, remember that

And for those of you who do not know,

Most of the systems that are running the internet, are built, installed and maintained, by us, the greybeards!

They are not built the young ones, who are barely 20 years old, who do not know the difference between a compiler and a debugger!

/3

#bash #sh #zsh #ksh #csh #tsh #freeBSD #100DaysOfCode #1000DaysOfCode #POSIX #Programming #Patch #RetroComputing #UNIX #History

SystemD has so much going on, that I shall suffice by pointing you to the article. The words of Stefano need no more addition towards the subject of systemd.

On my systems I avoid Systemd like the plague. Now read that three times out loud...

If you want to know more about Systemd in detail, just go and read the many different good documents on the internet, please do not use Google to search for them use anything else, DuckDuckGo does it much better.

This is one example where you learn what the Systemd stands for

Repeating Stefano's words: why was it needed? Everything worked perfectly fine before Systemd came in, there was no reason for its existence.

I have included the Wikipedia article; take your Time to at least glance at it, because the writers have tried to give a Balanced View of the Pro and the cons of Systemd

https://en.wikipedia.org/wiki/Systemd?wprov=sfla1

/2

#bash #sh #zsh #ksh #csh #tsh #freeBSD #100DaysOfCode #1000DaysOfCode #POSIX #Programming #Patch #RetroComputing #UNIX #History

In this post Stefano teaches you why he moves many of his servers from Linux to freeBSD.

Here is some background History of Mine:

Because I have been using Linux ever since the pre-alpha days, I know many things about the operating system that most other users do not. There was no other way to install the operating system in the beginning, than to compile the kernel on another operating system, to hex edit a boot sector, then boot to see if your kernel would actually properly spawn on your machine. In the beginning the hex editing was done on the floppy disk you could not boot from the hard drive.

From that point, you had to go back to the foreign operating system, compile the rest that you needed for minimum functionality, then put them in a convoluted manner on the file system which was then Minix.
It was normal in that period where you first installed Linux to do not just everything yourself, but to know what to do otherwise you would never get the functioning operating system.
In the end you would also compile GCC in that foreign operating system, because there was no way for you to do it in Linux with a compiler you did not have yet {chicken egg dilemma}
Only after GCC was compiled, were you able to do Native compiling in Linux on the Minix file system.

It is exactly this manner of thinking, that is still bothering Linux distributions today. Somewhere there are people who still think, that there are many users who want to Tinker with the operating system, when they just want to go from one major version to the next.

This manner of thinking breaks things when you need to upgrade from minor to Major version.

One thing that has always bothered me, is that a simple major update from the operating system from one person to the next can **still*" literally break things in unexpected ways, because of the way that Upstream handles certain commands.
For no good reasons commands like ifconfig where depreciated, the other example's also like arp.

Ifconfig has been in Unix Forever.

Ifconfig is in muscle memory of hundreds of thousands of system operators. Ifconfig is a specialized command which does only one thing and it does it in a perfect manner and it has been doing it ever since UNIX existed.
It's still baffles me that I need to separately install the ifcommands, before I can work on a Linux system today, and that's with any any distribution

This is just one of the examples of why it is wrong to change commands on the fly, depreciating another set of commands, without giving the people the choice, at the beginning, to include it with the installation of the distribution

The IP Command is a good one, nice modern with colour output, ifconfig is still a very good command, nice, **stable** decades old, leave it be!

These are the major things, that often bring system operators to seek operating systems, where stability is first, where updates from minor to minor version go smoothly, and updates from minor to Major versions usually also go smoothly and where don't disappear 🫥 or are depreciated for trivial reasons.

/1

#bash #sh #zsh #ksh #csh #tsh #freeBSD #100DaysOfCode #1000DaysOfCode #POSIX #Programming #Patch #RetroComputing #UNIX #History

https://it-notes.dragas.net/2022/01/24/why-were-migrating-many-of-our-servers-from-linux-to-freebsd/