service auth {
disable = no
socket_type     = stream
wait            = no
user            = ident
cps             = 4096 10
instances       = UNLIMITED
server          = /usr/sbin/in.authd
server_args     = -t60 –xerror –os -E
}

#1. How hard is to add ‘vi’/'vim’ into default base? I do not understand the discrimination here. While other questionable editors are bundled in (ie. emacs, a shitty vi clone known as ‘elvis’, pico, joe, maybe more?), yet it is too much to ask for a _standard editor to be included_.

#2. /etc/rc.d/ is a mess. That’s ok, I don’t have to deal with it much, but I do have to add additional IP’s from time to time… Now, if you are able to add 4 identical comments to rc.inet1.conf about how to handle multiple hardware interfaces – would it really be so fucking hard to add a comment for how to handle aliases? If the hardware interface definitions are there, it’d be hard to argue as to why not add yet another comment/example on how to do an alias. Such things are trivial of course, and if you scroll to the bottom of the config, most will pick up on the fact that you can use IFNAME[1]=ethX:X syntax, but really, should adding an alias require you to verify on google whether that’s the proper syntax for the config?

While I have many wonderful memories of running Slackware as my first Linux distro in 1998 or 1999 – messing with AT commands, trying to get my modem to work; getting xfree86 to work with my video card and many, many more – there is nevertheless a point in time where you grow up, get a job in IT and do not wish to waste time getting something trivial to work. That is the case with you, Slackware. It’s time to retire.

Love,

Your Blog

P.S. Kayla loves you always.