Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
10-29-2013, 08:05 PM
|
#16
|
Senior Member
Registered: May 2010
Location: Chicago Metro
Distribution: Arch, Gentoo, Slackware
Posts: 1,690
|
Quote:
Originally Posted by volkerdi
the choice will be whatever will be likely to cause the least future trouble
|
As it should be.
|
|
|
10-29-2013, 08:33 PM
|
#17
|
Member
Registered: Mar 2002
Location: 127.0.0.1
Distribution: Slackware and OpenBSD
Posts: 740
Rep: 
|
Quote:
Originally Posted by volkerdi
Let's not have another one of those threads, OK? Save it for when we switch to systemd. 
|
Haha. :-)
All I'll say is that if, and that's a big IF, the time comes when Slackware has to switch to systemd, I'm sure it will be implemented in the sanest and stablest way possible. I trust Patrick and the whole team to make the right decisions in things like that so I'm not that concerned about it.
|
|
1 members found this post helpful.
|
10-29-2013, 08:56 PM
|
#18
|
Member
Registered: Nov 2009
Location: Kansas, USA
Distribution: Slackware64-15.0
Posts: 865
|
Quote:
Originally Posted by TobiSGD
Just nitpicking, Slackware uses SystemV init with BSD style scripts.
|
I thought that was the other way around, with /etc/rc.d being the main way to start up scripts, and SysV wrappers for when a piece of software requires it.
|
|
|
10-29-2013, 08:59 PM
|
#19
|
Moderator
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
|
Quote:
Originally Posted by Richard Cranium
I think it's "Sometimes help stops no pills"
|
It's a German proverb. It translates to "Sometimes pills don't help" and means that sometimes there is nothing one can do to prevent something.
Well, we will see what the future brings, but Patrick is right, let's not start another systemd thread.
|
|
|
10-29-2013, 11:06 PM
|
#20
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
The good thing is Slackware's BSD-SysV hybrid system simply works. Both BSD and SysV init scripts can be used equally which is good on all accounts.
As long as udev can be extracted from systemd nothing will probably change.
|
|
|
10-29-2013, 11:22 PM
|
#21
|
Member
Registered: Sep 2011
Location: Christchurch NZ
Distribution: Debian, DebianDog
Posts: 125
Rep:
|
Could I ask have you ever tried Manjaro Linux my understanding is that is rock stable and updates don't break and you can enjoy Arch without the breakage.
|
|
|
10-30-2013, 02:33 AM
|
#22
|
LQ Newbie
Registered: Sep 2013
Posts: 23
Rep: 
|
Quote:
Originally Posted by darry1966
Could I ask have you ever tried Manjaro Linux my understanding is that is rock stable and updates don't break and you can enjoy Arch without the breakage.
|
I used arch and tried manjaro. As far as I can tell, manjaro "is" arch outdated by some weeks (which potentially leads to some security problems). This can be useful mostly to check if arch users are having problems with the updates since the Manjaro team is small so it's unlikely that they can fix/find more bugs then the arch team (so manjaro's devs have more information when it comes to push the packages for their users).
Anyway, from my experience, most of the breakage come from the AUR and don't know how manjaro can help there.
Last edited by grothen; 10-30-2013 at 02:35 AM.
|
|
|
10-30-2013, 02:54 AM
|
#23
|
Senior Member
Registered: Feb 2011
Location: Australia
Distribution: Debian Wheezy, Jessie, Sid/Experimental, playing with LFS.
Posts: 2,900
|
Quote:
Originally Posted by chess
MATE is a fork of the old GNOME 2.x desktop environment started by the Linux Mint folks.
|
No Cinnamon was started by Clem from Mint and it is a fork of Gnome 3. MATE was started by Perberos who uses Arch from memory. The other founders of MATE use various systems with only Clem being Mint.
|
|
|
10-30-2013, 04:16 AM
|
#24
|
LQ Veteran
Registered: May 2008
Posts: 7,131
|
Quote:
Originally Posted by mattallmill
I thought that was the other way around, with /etc/rc.d being the main way to start up scripts, and SysV wrappers for when a piece of software requires it.
|
- SysV init executable and /etc/inittab.
- SysV style rc.<service> files that take start/stop/restart arguments.
- BSD style sequential rc script (rc.S/rc.M) instead of SysV runlevel directories and S00xxxxxxx/K00xxxxxxx symlinks.
IMO it's very sensible approach building on the good aspects of both systems.
P.S. Slackware does implement S00nnnnnn/K00nnnnn style runlevel directories, it's just that no one uses them and they're usually empty.
Last edited by GazL; 10-30-2013 at 04:20 AM.
|
|
|
10-30-2013, 06:48 AM
|
#25
|
Moderator
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
|
Quote:
Originally Posted by GazL
P.S. Slackware does implement S00nnnnnn/K00nnnnn style runlevel directories, it's just that no one uses them and they're usually empty.
|
They are only there to support third party software, you need them for example for VMware Player and other software that does not support Slackware's init style (Virtualbox for example does that out of the box even with their binary installer).
|
|
|
10-30-2013, 07:30 AM
|
#26
|
Member
Registered: Dec 2009
Distribution: Slackware
Posts: 229
Original Poster
Rep:
|
Thanks for the responses guys. I'm happy to be coming back sysvinit as I'm far more familiar with it, but I think at some point in the not-to-distant-future, something is going to have to give. But that's a bridge we'll cross when we get to it.
Slackpkg+ looks really interesting, I'll definitely be make use of that.
GRUB2 for UEFI was a surprise, I thought we all didn't like GRUB. Ah well, makes no difference to me. Hopefully my motherboard will decide to co-operate this time around.
Quick Edit: I have not heard of or tried Manjaro, sorry. I'm more than happy to be back with Slackware, but perhaps I'll stick it in a VM sometime and give it a spin.
Last edited by spudgunner; 10-30-2013 at 07:35 AM.
Reason: Didn't see page 2 of the thread
|
|
|
10-30-2013, 07:52 AM
|
#27
|
Member
Registered: Nov 2009
Location: Kansas, USA
Distribution: Slackware64-15.0
Posts: 865
|
Quote:
Originally Posted by GazL
- SysV init executable and /etc/inittab.
- SysV style rc.<service> files that take start/stop/restart arguments.
- BSD style sequential rc script (rc.S/rc.M) instead of SysV runlevel directories and S00xxxxxxx/K00xxxxxxx symlinks.
IMO it's very sensible approach building on the good aspects of both systems.
P.S. Slackware does implement S00nnnnnn/K00nnnnn style runlevel directories, it's just that no one uses them and they're usually empty.
|
OK. I'm pretty happy with the way it works, GazL. Never did like the SysV init, and sure as hell don't like systemd.
|
|
|
11-03-2013, 01:16 PM
|
#28
|
MLED Founder
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453
|
Quote:
Originally Posted by TobiSGD
That is not sure at all, there has to be a decision from the Tech Committee first if there will be a switch to Upstart or systemd (I hope that they will use Upstart) and even then the switch will be not in Jessie but at the earliest in Jessie+1.
|
Momentum seems to be there:
http://thread.gmane.org/gmane.linux....eneral/187624/
|
|
|
11-03-2013, 03:05 PM
|
#29
|
Moderator
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
|
Quote:
Originally Posted by kikinovak
|
Oh, of course, I follow that discussion, I maintain a few Debian machines and am quite interested in the outcome. For now, systemd fans advocate systemd, Ubuntu people advocate Upstart, some people try to bring OpenRC in the mix, but at this point it seems to be pretty open which one they choose. Even LP thinks that it is a good idea to comment on that, with his usual "do it my way or you are wrong, we will be the future solution anyways" nonsense: https://plus.google.com/115547683951...ts/8RmiAQsW9qf
I for one still think that Debian should go for Upstart or OpenRC, so that there remains a counterweight to the systemd/CoreOS stuff.
|
|
|
11-03-2013, 03:53 PM
|
#30
|
MLED Founder
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453
|
Quote:
Originally Posted by TobiSGD
|
I just read through most of that thread. Jesus, can't someone run a bus over that, erm, project?
|
|
|
All times are GMT -5. The time now is 03:15 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|