SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hitest, your comments made me think of something. If it were inevitable that Slackware couldn't avoid The Crawling Chaos any further, it would be the end of an era not only for Slackware but for the Linux desktop in general.
It would essentially be a tragedy. It would mean that the disease had crept so far into the ecosystem that it had become inseparable from that ecosystem to the point whereby curing it would mean killing its host. I know that many of us have, in the past, discussed which OS we would move to in such a scenario but, on reflection, I think that we would be duty-bound to move to *BSD since migrating back into Linux-land would be giving the contagion further organisms to infect and convert. More heads for an increasingly-powerful hydra.
I don't actually think we're at that point yet, but it's a very important option for consideration. Does convenience matter that much to us - or should we brave a bit more research to stand up for our ethics? If there are people here who already use *BSD, then that's great. I personally do not. But as Slackware users, such learning curves should present us with little drama. Why are we even here otherwise?
Last edited by Lysander666; 07-11-2019 at 05:08 AM.
I do not foresee Slackware forcibly adopting the init system that shall not be named. There's simply no need for it.
Perhaps we will have to adopt elogind which (just like eudev) is a piece of the S**D code that can be used standalone, but even elogind is currently only required if Slackware were to adopt KDE Plasma 5 *and* would add Wayland at the same time.
I still hope that ConsoleKit2's implementation of the 'login1' protocol will be finalized one day, so that other software like KWin and SDDM can incorporate CK2 as an alternative login1 provider to elogind.
If there are people here who already use *BSD, then that's great. I personally do not. But as Slackware users, such learning curves should present us with little drama.
I've used OpenBSD since 2011(version 5.0). Like Slackware OpenBSD is simple, elegant, and robust. OpenBSD has exceptional documentation and a wonderful community(just like Slackware).
I've used OpenBSD since 2011(version 5.0). Like Slackware OpenBSD is simple, elegant, and robust. OpenBSD has exceptional documentation and a wonderful community(just like Slackware).
How about the project leader? I've heard... stuff...
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by Lysander666
hitest, your comments made me think of something. If it were inevitable that Slackware couldn't avoid The Crawling Chaos any further, it would be the end of an era not only for Slackware but for the Linux desktop in general.
It would essentially be a tragedy. It would mean that the disease had crept so far into the ecosystem that it had become inseparable from that ecosystem to the point whereby curing it would mean killing its host. I know that many of us have, in the past, discussed which OS we would move to in such a scenario but, on reflection, I think that we would be duty-bound to move to *BSD since migrating back into Linux-land would be giving the contagion further organisms to infect and convert. More heads for an increasingly-powerful hydra.
I don't actually think we're at that point yet, but it's a very important option for consideration. Does convenience matter that much to us - or should we brave a bit more research to stand up for our ethics? If there are people here who already use *BSD, then that's great. I personally do not. But as Slackware users, such learning curves should present us with little drama. Why are we even here otherwise?
Today I learned that the guy who made reiserfs is doing time for murder. Damn, I missed a lot of news in grad school.
Yes, it esssentially meant the end of the kernel developers supporting reiserfs version 4, the implementation in the kernel has stayed at 3.x
Quote:
FORMAT specifies the format for the new filesystem. Choose format 3.5 or 3.6. If none is specified mkreiserfs will create format 3.6 if running kernel is 2.4 or higher, and format 3.5 if kernel 2.2 is running, and will refuse creation under all other kernels.
(from the man page for 'mkreiserfs', for the '--format FORMAT' option)
Although work has been done on reiserfs 4, it hasn't been incorporated into the mainline kernel
Quote:
Namesys considered ReiserFS (now occasionally referred to as Reiser3) stable and feature-complete and, with the exception of security updates and critical bug fixes, ceased development on it to concentrate on its successor, Reiser4. Namesys went out of business in 2008 after Reiser's conviction for murder.
(from the wikipedia page for reiserfs)
and
Quote:
Reiser4 is a computer file system, successor to the ReiserFS file system, developed from scratch by Namesys and sponsored by DARPA as well as Linspire. Reiser4 was named after its former lead developer Hans Reiser. As of 2018, the Reiser4 patch set is still being maintained, but according to Phoronix, it is unlikely to be merged into mainline Linux without corporate backing.
...
I think that we would be duty-bound to move to *BSD since migrating back into Linux-land would be giving the contagion further organisms to infect and convert.
...
Careful observers might have noticed that CRUX is much more BSD-like than Slackware. And it looks like that at least in theory it has better chances to survive.
in the past, discussed which OS we would move to in such a scenario but, on reflection, I think that we would be duty-bound to move to *BSD since migrating back into Linux-land would be giving the contagion further organisms to infect and convert.
If Slackware ultimately doesn’t work out, then the GNU Guix System Distribution might be an option for those of us with compatible hardware.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by ivandi
Careful observers might have noticed that CRUX is much more BSD-like than Slackware. And it looks like that at least in theory it has better chances to survive.
Cheers
Oh ivandi, that was quite a chuckle, lacked originality but I chuckled nonetheless.
And now I read the entire Wikipedia page on Hans Reiser. Creepy stuff.
I know, right? Damn. I just read this little tidbit:
Quote:
Ramon was trained in military interviewing techniques and claimed that Nina lied to him when he confronted her about inexplicably fast shrinking reserves of Namesys
I'm so not going to complain about my in-laws. Wow.
I'll deviate from the discussion line for a little bit. Since the company I work for is using Debian only, I had to ponder with the new Debian 10 (Buster) release. It was pleasing to see that Slackware 14.2 still had slightly newer software in some cases and only slightly older in other cases. Overall, I would say, they are about equal! Quite a nice find to go into happy birthday thread, won't you say?
Oh ivandi, that was quite a chuckle, lacked originality but I chuckled nonetheless.
Well, British humour has always been a disaster
Careful observers might have noticed that Pat had been overworked lately. Pushing completely broken packages in current is a clear sign that those packages haven't been tested at all. It looks like the BDFL development model has reached its limits.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
