Terminus should really be included. It's non-intrusive, and like any other font, it can be deleted for others that don't want to use it. But c'mon, who doesn't use it?

md5deep. It's a really simple recursive md5 program. It's available from SBo and doesn't seem to have any dependencies.

1 members found this post helpful.

In Cisco routers, you are able to over-ride the default mac address of the interfaces. (see https://learningnetwork.cisco.com/thread/2869)

(I have used Cisco Router 881)

Also true of every version of Windows since at least NT 3.5.

... and every Linux distro with ifconfig ...

(ifconfig ethX hw ether xx:xx:xx:xx:xx:xx)
(assuming the card will do it)

WOOT! Thank you Pat!

1 members found this post helpful.

rxvt-unicode, sawfish, mpd+mpc, maybe bitlbee. That would save me some compiling, but not a big deal.

I'd like to see grub2 offered along with lilo. I'd also like to see KDE split in to a core package, and smaller extra packages with the rest of the software.

1 members found this post helpful.

FYI, Network Manager was added to -current prior to the release of Slackware 14

I hope that helps!

Kindest regards,

.

Syslinux as bootloader replacing lilo, no need for grub.

Most of all PAM and systemd though. I think its about time.

Don't hold your breath.

9 members found this post helpful.

I appreciate the reply. For PAM the reasons are pretty much known, but what is the problem with systemd? You can't even compare it to the mess sysvinit is. Systemd is well thought, robust and solves actual problems.
Yes it doesn't work on anything but Linux, but last i checked Slackware didn't either.
Have you (not just Pat but Slackware people in general) tried recent versions of it?

/me holds nose and points to suitable thread for this stale and smelly troll bait http://www.linuxquestions.org/questi...ystemd-885228/

Funny, my take is the exact opposite of yours.

Like what? Try a search for "systemd crashing" and tell me again about how robust it is. I've been using Linux almost forever, and init has never crashed.

That's an odd argument. As far as I know, adding systemd wouldn't help Slackware work on a non-Linux OS.

Anyway, we use plenty of things that are closely tied to the kernel and don't work on non-Linux operating systems, so that is not the rationale here. It's more like, if we're going to be dropping core functionality with years of careful evolution, it had better be a clear improvement. It doesn't take very much time on Google to see that not everyone is happy with systemd. And I'd guess that the usual Slackware user would be even less happy with it than the usual user of (insert other distro here). The benchmarks I've seen don't show an improvement in boot time (the opposite, actually), and users and developers alike have complained that it lacks the flexibility of shell scripts, that it is harder to create a systemd unit than to modify a shell script, and that it can easily lead to race conditions as processes start. It is far from simple, and it tries to do too much. It actually has to create sockets for services that haven't started yet in order to paper over the issues with things that haven't started up yet. And sysvinit as implemented in Slackware is a mess? Spare me.

I have. Didn't care for it, and wouldn't want to have to support it. If you like it, there are a whole lot of distributions that use it, and I realize that we can't be everything to everybody. As long it is remains optional, I plan to avoid it. Unfortunately, the folks in charge of it seem to force it upon us, and everyone else. A healthy open source ecosystem respects diversity, and doesn't try to railroad everyone into being exactly the same. Without choices, you cannot choose a solution that fits your needs. That's not what we want, is it?

22 members found this post helpful.

Thanks again for taking the time to reply Pat.
I couldn't get many results, but i agree sysvinit is more reliable



I can think of some that could use improvements offhand.
The bluetooth one that doesn't even show up on the installer and is -x by default.
Then there is the wireless/networking situation. Slackware still ships rc scripts that afaict are completely useless today.
Not to mention that due to some coming from upstream etc as well as being written by different people don't carry a consistent coding style.
At least using systemd would mean *actual* 0 maintenance for init scripts by downstream and consistency in them.

On my fresh install, rc.bluetooth is not -x.

It is still possible to use them. Some people do.

My friend, few things from upstream are so golden as to require zero maintenance. I'm guessing you haven't read as many SRPM changelogs as I have... getting a systemd unit right is far from a trivial task.

3 members found this post helpful.