LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


View Poll Results: Resemblance / Preference
SysV / SysV 4 8.70%
SysV / BSD 2 4.35%
BSD / BSD 26 56.52%
BSD / SysV 14 30.43%
Voters: 46. You may not vote on this poll

Reply
  Search this Thread
Old 08-28-2018, 03:26 AM   #16
bassplayer69
Member
 
Registered: Jul 2007
Location: In a van down by the river...
Distribution: Linux Mint 19.1 & Slackware64-Current
Posts: 222

Rep: Reputation: 50

I selected BSD/SysV since all the years I spent working with Unixware was sysV.
 
Old 08-28-2018, 04:18 AM   #17
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,270
Blog Entries: 1

Rep: Reputation: Disabled
Truly I don't know. For me seems questions are not precise. Do OP means 'init' script - script which is marked as 'do not touch at any circumstances' - so I don't even tried to look carefully what is inside. If this is the case: I don't know where the init script comes from, UNIX or BSD. Or OP means scripts put in /etc/rc.d/. Running levels. etc. OpenBSD as I remember is using sysctl command to run or stop service. In Slackware I'm just switching chmod +/- rc.'service' to enable or disable the service. I don't know maybe that solution is just as well very unique to Slackware. Where this comes from? Good question to ask the creator of Slackware.
 
Old 08-28-2018, 06:51 AM   #18
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,727

Rep: Reputation: 740Reputation: 740Reputation: 740Reputation: 740Reputation: 740Reputation: 740Reputation: 740
excellent keynote from the last BSDCan2018
http://www.bsdcan.org/2018/schedule/events/927.en.html
I hope that Slackware deves have half an hour to invest and watch this
 
Old 08-28-2018, 09:02 AM   #19
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,592

Rep: Reputation: Disabled
Just a friendly reminder.

Quote:
Originally Posted by TommyC7 View Post
Let's not derail this thread into another discussion about systemd, please. That's not what I asked for.
To stay on-topic I think its somewhat misleading to consider the Slackware init as a BSD or sysv init. Its very possible to run Slackware without a single sysv init script and while you can draw comparisons between /etc/rc.d/ and various BSD styled inits they aren't really the same thing and the similarities are mostly superficial. Personally I think the Slackware init is of a higher quality than the init in an OS like Freebsd.
 
Old 08-28-2018, 04:23 PM   #20
ChuangTzu
Senior Member
 
Registered: May 2015
Location: Where ever needed
Distribution: Slackware/Salix while testing others
Posts: 1,290

Rep: Reputation: 1181Reputation: 1181Reputation: 1181Reputation: 1181Reputation: 1181Reputation: 1181Reputation: 1181Reputation: 1181Reputation: 1181
Poll is not accurate, choices are not clear. As mentioned already there are more than one BSD init, Slackware is BSD like init, did not see that option.
 
1 members found this post helpful.
Old 08-28-2018, 05:46 PM   #21
TommyC7
Member
 
Registered: Mar 2012
Distribution: Slackware, CentOS, OpenBSD, FreeBSD
Posts: 502

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ChuangTzu View Post
Poll is not accurate, choices are not clear. As mentioned already there are more than one BSD init
As previously stated on the first page:

Quote:
Originally Posted by TommyC7 View Post
... something like what the Wikipedia page describes for newer versions of {Net,Free}BSD (which, in my opinion, is similar to Slackware's organization of it).
Quote:
..., Slackware is BSD like init, did not see that option.
As previously stated on the first post:

Quote:
1. Which do you think Slackware's init system more closely represents (SysV or BSD)?

2. Which do you prefer?

The answer to #1 is the first option in the poll, and the answer to #2 is the second option in the poll, hence the 4 options.
So we know your answer to #1 at least (i.e. if you do choose to vote, options 3 or 4 are what you'd probably pick).
 
Old 08-29-2018, 03:01 PM   #22
ChuangTzu
Senior Member
 
Registered: May 2015
Location: Where ever needed
Distribution: Slackware/Salix while testing others
Posts: 1,290

Rep: Reputation: 1181Reputation: 1181Reputation: 1181Reputation: 1181Reputation: 1181Reputation: 1181Reputation: 1181Reputation: 1181Reputation: 1181
Other: BSD like init.
 
Old 08-29-2018, 08:17 PM   #23
gus3
Member
 
Registered: Jun 2014
Distribution: Slackware (x86 and ARM)
Posts: 154

Rep: Reputation: Disabled
What about a "no preference" option?

Slackware's heritage for init is clearly BSD, with an added framework for external packages that expect SysV-style init support. However, support has grown over the years for separate scripts for particular services, e.g. MariaDB, ntpd, network, containers, mail routing. It doesn't use the "service start/stop/status/restart" lingo from SysV, but it's still in the same vein of "a little work now saves lots of work later."

I've learned to use both frameworks, and I see the validity in both approaches, so I don't really have a preference.
 
Old 09-01-2018, 02:47 AM   #24
elcore
Member
 
Registered: Sep 2014
Distribution: Slackware
Posts: 590

Rep: Reputation: Disabled
Quote:
Originally Posted by a4z View Post
excellent keynote from the last BSDCan2018
http://www.bsdcan.org/2018/schedule/events/927.en.html
I hope that Slackware deves have half an hour to invest and watch this
I watched this keynote on the tube, it's mostly about attempting to port systemd features into FreeBSD (which has a huge repository of similar attempts already).
It's probably not going to happen on NetBSD anytime soon. And Slackware already has a fork which integrates it, so if it comes down to that; it will most certainly have one which disintegrates it.

Additionally, I don't think injecting an exploitable layer between kernel and userspace is a good idea, but it's good to have options for those in need.
 
1 members found this post helpful.
Old 09-01-2018, 06:36 AM   #25
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,194

Rep: Reputation: 538Reputation: 538Reputation: 538Reputation: 538Reputation: 538Reputation: 538
They say the Slackware uses a BSD-style init... but, having experimented with many of the *BSDs, my thought is that they're not even close.

IMNSHO, Slackware's init is what a BSD-style init could be if it grew up.

If you do this in stock Slackware:
Code:
# chmod +x /etc/rc.d/rc.sysvinit
you will have the ability to install packages that require SysV init, and they will properly work along side the already installed "BSD-style" scripts with no further intervention.

That is a truly great feature of Slackware.

For software that needs an init script, it is not easy to package "BSD-style" init scripts. On the other hand, it is trivially easy to do so with SysV init style scripts. All you need are a couple of symlinks, and it works with no further intervention. No need to manually edit anything; just put the right file in the right place and it works.

I don't believe Slackware's init is as easily defined as many people seem to believe it is. It is a "hybrid" system built for convenience from common sense.

So, my answer to the OP is:

https://i.imgur.com/s4eamxv.jpg

Last edited by rkelsen; 09-01-2018 at 06:43 AM.
 
2 members found this post helpful.
Old 09-01-2018, 08:16 AM   #26
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 2,875
Blog Entries: 7

Rep: Reputation: 1501Reputation: 1501Reputation: 1501Reputation: 1501Reputation: 1501Reputation: 1501Reputation: 1501Reputation: 1501Reputation: 1501Reputation: 1501Reputation: 1501
Don't know a lot about Slackware but I understand that it uses BSD init. When it comes to preferences, I say BSD every time. It boots much faster and it uses a few simple scripts, not a battery of complex ones. Sysv init requires a whole directory of links for each run level, whereas bsd init requires only one script file per run level. I use bsd init on my LFS system, although that's not what the book recommends. And my Crux system uses it too.
 
1 members found this post helpful.
Old 09-01-2018, 08:35 AM   #27
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,483

Rep: Reputation: 916Reputation: 916Reputation: 916Reputation: 916Reputation: 916Reputation: 916Reputation: 916Reputation: 916
Thanks rkelsen.

Much more eloquently expressed than my reply on this thread.

If Slackware did not provide a hybrid system, I couldn't use it without a lot of scary and fragile kludges because I am a long time VMWare User and VMWare expects a SysV Init System.

Thanks again.

-- kjh( Poll: does a pomegranate more closely represent an apple or an orange ? )
 
Old 09-01-2018, 09:16 AM   #28
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 1,543
Blog Entries: 2

Rep: Reputation: 360Reputation: 360Reputation: 360Reputation: 360
i voted sysV/sysV wrongfully
Slackware uses the most convenient init system I encountered yet
 
Old 09-01-2018, 01:44 PM   #29
TommyC7
Member
 
Registered: Mar 2012
Distribution: Slackware, CentOS, OpenBSD, FreeBSD
Posts: 502

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by SCerovec View Post
i voted sysV/sysV wrongfully
Slackware uses the most convenient init system I encountered yet
Noted. So what should I mark you down for?

Quote:
Originally Posted by rkelsen View Post
I don't believe Slackware's init is as easily defined as many people seem to believe it is. It is a "hybrid" system built for convenience from common sense.

So, my answer to the OP is:

https://i.imgur.com/s4eamxv.jpg
There are 2 questions and I can't tell which one you're attempting to answer with that image.

If that image is supposed to answer the first, then as previously stated in response to kjhambrick:

Quote:
Originally Posted by TommyC7 View Post
This is why the question was:

Quote:
Which do you think Slackware's init system more closely represents (SysV or BSD)?
and not

"Which do you think Slackware's init system is?"

Last edited by TommyC7; 09-01-2018 at 01:46 PM.
 
Old 09-01-2018, 03:28 PM   #30
smaclennan
LQ Newbie
 
Registered: May 2010
Location: Ottawa, Canada
Distribution: slackware
Posts: 26
Blog Entries: 2

Rep: Reputation: 10
I voted bsd/sysv. I consider Slackware to be BSD oriented. It has run levels but, at least on my system, they are empty.

I slightly prefer sysv since you just drop an rc file in place and it is automagically run at boot time. I find with Slackware/BSD I have to put too much in rc.local.

But this is just a quibble. I am perfectly happy with the Slackware init system... unlike some others that Shall Not Be Named.
 
  


Reply

Tags
bsd, init, sysv


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
SysV versuses BSD-Style Artimus Linux - General 18 03-02-2016 04:16 AM
BSD-style and sysv init systems Mitt Green Linux - Software 10 01-24-2016 11:42 AM
PostgreSQL SysV-style init for boot - password? maw269 Linux - Software 0 07-19-2013 06:45 PM
LFS 6.7 - Problem, populating /dev with a BSD-style init jimmy_page_89 Linux From Scratch 3 09-26-2010 02:52 AM
How to use the BSD style init scripts in /etc/rc.d jmbrink26 Slackware 8 09-06-2006 09:32 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:25 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration