Nice post!

Some one help me for learning linux?
https://www.thinkerlinux.com/

Sorry, I did not see your comment until now,

Thanks for the congrats.

It was such a thrill having my first LFS system boot properly.

and where is the list of ranks? It also seemed to have changed and I'm just wondering how many posts it takes for each. According to one person posting, I'd have a different rank by some old version. I'd also wondered if a 'senior member' was over a certain age, but apparently it's just a rank of number of posts.

Yeah, I did pick up on that sentiment in your blog post =)

As a long-time OpenBSD convert, I'm not really feeling any threat from systemd, but to see a FreeBSD dev discuss it as if it were the best thing since sliced bread is a bit...concerning. Not that I think Theo would ever willingly accept systemd madness into OpenBSD, though.

If ever systemd does happen to overwhelm the remaining open source operating systems out there, I'll probably retire to a remote mountain top to raise chickens and goats and never look back lol.

Not just you, sir! I for one am glad that the BSDs remain a final fallback position, should the remaining Linux distributions fall to the enemy.

For the moment, however, the situation seems fairly static. Roughly 70 Linux distributions (about 25%) do not use systemd and show no signs of starting. http://without-systemd.org/wiki/inde...ithout_systemd

The systemd team tried to make more advances by weaponizing some software dependencies. First they tried deprecating the netlink device interface for a systemd-specific interface, but device driver developers are an unruly crowd of cats and shunned the new interface. Then they tried to introduce a systemd dependency to the kernel itself with kdbus/BUS1, but the Linux devs repeatedly rejected these patches.

Either of these moves, if successful, would have swept most of the resistance into the systemd fold. But they failed, so they declared victory and pretend it's fait accompli.

So the lines of battle have remained static for a while, but who knows when they might start up again on a new front.

If the worst happens, many of us will be glad to find final refuge with the BSDs.

Softpedia 181126: GNU/Linux developer Arne Exton has made a new distro for the tiny Raspberry Pi single-board computers, this time based on the popular openSUSE Tumbleweed operating system and the lightweight Xfce desktop environment

"Meet EXTON OpSuS Rpi, a variant of Arne Exton's old EXTON OpSuS Tumbleweed distribution optimized for Raspberry Pi devices. It's a "remaster” of the official OpenSuSE Tumbleweed ISO image for Raspberry Pi 3 Model B+, using the Xfce desktop environment by default and all the necessary packages for daily use.

"I did it mostly because it’s fun," said Arne Exton in today's announcement. "My version [EXTON OpSuS Rpi] has one big advantage though since you can enjoy sound. Good if you like YouTube, for example. I’ve also added some “necessary” packages and prevented installations of all KDE packages.""

READ MORE: https://news.softpedia.com/news/you-...p-523984.shtml

"If Nagios hits up a service immediately or soon after system start and starts the service, then why did we bother deferring the service start in the first place?"

This is a classic example of dis-jointed design (which is prevalent in Linux, but not so much in the BSD's). We have some feature that solves some problem, yet, the problem doesn't really exist on a higher level of the architecture. Ironically, one of the goals of systemd was to reduce the disjointed manner in which Linux distros operate.

Personally, I would love to see systemd and the logic underlying it staying as far away from the BSD's as possible, but that's just me =)

Bah .. 676 views here on LQ, but only 61 of you clicked through to the actual article. Next time I'll paste a copy of the entire article into LQ, not just the link.

Update - CPAN modules have proven an unruly collection of software. It took a lot of stops and starts and more manual intervention than I would like, but I finally managed to test almost all of CPAN on -current.

Conclusion: perl-v5.18.0 looks pretty good!

None of the problems I encountered with any CPAN module seemed to be attributable to faults in perl.

When Slackware next updates perl, I'll be wanting to re-run the tests, but first I'd like to improve my test harness so that it requires less manual intervention.

The test harness will become an integral part of Slackhammer as well.