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

Reply
 
Search this Thread
Old 11-05-2013, 04:19 PM   #16
Darth Vader
Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 598

Rep: Reputation: 109Reputation: 109

Then, we pass to SystemD? When?

Last edited by Darth Vader; 11-05-2013 at 04:21 PM.
 
Old 11-05-2013, 06:15 PM   #17
narz
Member
 
Registered: May 2007
Location: US
Distribution: slackware
Posts: 184

Rep: Reputation: 35
These first two accounts didn't go so well for you buddy. Third time's a charm.
 
Old 11-05-2013, 06:16 PM   #18
unSpawn
Moderator
 
Registered: May 2001
Posts: 27,003
Blog Entries: 54

Rep: Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757Reputation: 2757
Quote:
Originally Posted by jtsn View Post
Another one trolling with a fake account
Do show me the evidence for that accusation.
 
1 members found this post helpful.
Old 11-05-2013, 06:24 PM   #19
GazL
Senior Member
 
Registered: May 2008
Posts: 3,328

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
sysvinit is just fine as it is. What could use a little work is Slackware's rc.* scripts. While they're still doing their job, over the years, as new things have come along and old things have gone away, there's been a tweak here, and a tweak there, and it's starting to show a little. IMO they could do with a bit of a spring clean.

I'm currently working on rc.S/rc.M here for my own gratification and to fill a little time while we're in this lull waiting for 14.1. Mostly it's re-ordering the sections into a sequence that seems a little more logical to me, but also doing the odd bit of code cleanup and optimisation where I can. No idea whether anyone else will be interested in the end result, but it keeps me occupied.
 
1 members found this post helpful.
Old 11-05-2013, 08:27 PM   #20
Ongbuntu
Member
 
Registered: Aug 2013
Distribution: slackware
Posts: 79

Rep: Reputation: 8
Quote:
Originally Posted by Daedalos View Post
Complaining will get you no where.
I think the intentions of your post is great.

But I would like to point out that complaining, with much negativity attached to it, does work. And it works in ways beyond our wildest imagination.

Just to quote a few examples,
1. Obama's health care bill was a result of many complains and negative sentiments from the people who used to be at the mercy of the heatlhcare system.
2. countless politicians have to step down because from unsurmountable complains from the people.
3. I bought a car because my wife kept complaining about the poor quality public transport systems that we used to use everyday.

I could go on and on, but you get my point. I know it's counter-intuitive that a seemingly useless act like complaining can generate enormous impetus to steer things in certain direction.

Hence, the question is not whether we should or should not be complaining, but rather, are we complaining enough for the right cause.
 
2 members found this post helpful.
Old 11-05-2013, 08:31 PM   #21
Ongbuntu
Member
 
Registered: Aug 2013
Distribution: slackware
Posts: 79

Rep: Reputation: 8
Quote:
Originally Posted by unSpawn View Post
Do show me the evidence for that accusation.
The account is not fake. Otherwise, it would be impossible to make a post. But the trolling....
 
Old 11-05-2013, 09:24 PM   #22
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,443

Rep: Reputation: 409Reputation: 409Reputation: 409Reputation: 409Reputation: 409
Quote:
Originally Posted by Ongbuntu View Post
1. Obama's health care bill was a result of many complains and negative sentiments from the people who used to be at the mercy of the heatlhcare system.
Given that has turned out to be a first-order disaster, you probably should have chosen another example.

Plus it's rather politically charged in the US, which creates a new possibility of a flame war.
 
Old 11-05-2013, 10:04 PM   #23
Ongbuntu
Member
 
Registered: Aug 2013
Distribution: slackware
Posts: 79

Rep: Reputation: 8
Quote:
Originally Posted by Richard Cranium View Post
Given that has turned out to be a first-order disaster, you probably should have chosen another example.

Plus it's rather politically charged in the US, which creates a new possibility of a flame war.
You are probably right, sir
 
Old 11-05-2013, 10:22 PM   #24
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, Slackware-14.1, PCBSD-10.0
Posts: 2,898
Blog Entries: 15

Rep: Reputation: 745Reputation: 745Reputation: 745Reputation: 745Reputation: 745Reputation: 745Reputation: 745
SysVInit doesn't need to be replaced. Neither does BSDInit.

OpenRC and RunIt both can be used to expand the capabilities of Upstart, SysVinit, and BSDInit without outright replacing them, even though it can.

Then again, there are at least a dozen or more INIT systems out there that either replace or supplement sysvinit, we could effective debate their usage until Linux gets a Cow as their mascot.

RunIt
s6
daemontools
OpenRC
Upstart
launchd (currently Mac OSX 10.4 or later only)
SystemStarter (previously used Mac OSX init system prior to 10.4)
Service Management Facility (used in Solaris)
Bootscripts (used by GoboLinux)
Mudur (Pardus Linux's init system)
initng
eINIT
perp
BusyBox-init
procd (OpenWRT's init)
minit

So yes, there are plenty of init systems and supplement systems that can work with or replace sysvinit.

So until Linux gets the cow as it's official mascot, pick and choose your own poison, and go with it.

Last edited by ReaperX7; 11-05-2013 at 10:23 PM.
 
1 members found this post helpful.
Old 11-05-2013, 10:56 PM   #25
Daedalos
LQ Newbie
 
Registered: Nov 2013
Location: Kansas
Distribution: Slackware 14.1 64bit Multi-lib
Posts: 22

Original Poster
Rep: Reputation: Disabled
I am not a troll.

I am also not competent enough to give any advice
on what or where to begin with what I have suggested.


All I know is there are a ton of very competent linux
guru's on this board, and that if they wanted to they
could just about do anything.

So instead of just being pissed or upset about systemd
isn't it more proactive to take what is already in place
and make it more advanced? Or as suggested previous to clean up or
make more efficient?

That is all I was suggesting. A course of action.

If you call that trolling then so be it.

If you do not like something that is going to happen
then work to change it.

That is all I was aiming at.

No more no less.

Last edited by Daedalos; 11-05-2013 at 10:59 PM.
 
Old 11-05-2013, 11:15 PM   #26
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, Slackware-14.1, PCBSD-10.0
Posts: 2,898
Blog Entries: 15

Rep: Reputation: 745Reputation: 745Reputation: 745Reputation: 745Reputation: 745Reputation: 745Reputation: 745
Quote:
Originally Posted by Daedalos View Post
So instead of just being pissed or upset about systemd
isn't it more proactive to take what is already in place
and make it more advanced? Or as suggested previous to clean up or
make more efficient?
Actually we have said that. SysVInit and BSDInit already have several programs that can be used in conjunction with them. Most deal with daemon service management and extra measures to help with keeping the system running, management of logs, supervision, etc.

Read these pages and see what we're talking about, or trying to anyway.

http://smarden.org/runit/

http://cr.yp.to/daemontools.html

http://untroubled.org/daemontools-encore/

http://b0llix.net/perp/

http://www.skarnet.org/software/s6/

But no, sysvinit and bsdinit are both fine as they are. SysVInit is in maintenance mode only as no further developments are required at this time. It's only been developed on to make sure it works with new architectures like x86_64 as of recent.

Unless you mean re-develop sysvinit to accept plugin style features, then you're talking to the wrong people, and should be discussing this with the sysvinit maintainers.

Last edited by ReaperX7; 11-05-2013 at 11:18 PM.
 
2 members found this post helpful.
Old 11-05-2013, 11:16 PM   #27
Daedalos
LQ Newbie
 
Registered: Nov 2013
Location: Kansas
Distribution: Slackware 14.1 64bit Multi-lib
Posts: 22

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ReaperX7 View Post
Actually we have said that. SysVInit and BSDInit already have several programs that can be used in conjunction with them. Most deal with daemon service management and extra measures to help with keeping the system running, management of logs, supervision, etc.

Read these pages and see what we're talking about, or trying to anyway.

http://smarden.org/runit/

http://cr.yp.to/daemontools.html

http://untroubled.org/daemontools-encore/

http://b0llix.net/perp/

http://www.skarnet.org/software/s6/

But no, sysvinit and bsdinit are both fine as they are. SysVInit is in maintenance mode only as no further developments are required at this time. It's only been developed on to make sure it works with new architectures like x86_64 as of recent.
Sure makes a person wonder why someone would reinvent the wheel then.

I will read up on it more.

Thanks.
 
Old 11-05-2013, 11:31 PM   #28
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, Slackware-14.1, PCBSD-10.0
Posts: 2,898
Blog Entries: 15

Rep: Reputation: 745Reputation: 745Reputation: 745Reputation: 745Reputation: 745Reputation: 745Reputation: 745
Lennart is just as we said in another post.

He's a wanna-be chef who wants to stir the soup pot, but instead of just stirring, he adds an onion when the recipe doesn't call for an onion, nor does it need an onion, then waddles away blaming the other chefs the soup is foul and needs to be remade with his recipe because he's an all-knowing genius.

There are plenty of distributions that have no plans to switch to systemd. Just because Patrick said "when we switch", is still a question of "if and when". Trust me, Patrick isn't going to just drop this on us like a bad idea, throw us to the wolfs with beef strips around our necks, and whip out the video camera just to see who gets mauled first.

Patrick's implementation of systemd will more than likely be so clean, balanced, and user-friendly, we might not even notice he switched us at all.

Truth be told, I'd wish the Linux Foundation and Linus Torvalds would just get pissed off enough to where he personally gives udev the axe completely. No more udev, no more systemd, and no more Lennart.
 
3 members found this post helpful.
Old 11-06-2013, 01:40 AM   #29
dugan
Senior Member
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 4,572

Rep: Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394
Quote:
Originally Posted by Richard Cranium View Post
Plus it's rather politically charged in the US, which creates a new possibility of a flame war.
I'm actually finding it hard to imagine an issue more politically charged than SystemD right now.

(I kid)
 
1 members found this post helpful.
Old 11-06-2013, 09:04 AM   #30
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,443

Rep: Reputation: 409Reputation: 409Reputation: 409Reputation: 409Reputation: 409
Quote:
Originally Posted by dugan View Post
I'm actually finding it hard to imagine an issue more politically charged than SystemD right now.
Heh.
 
  


Reply


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
Debian To Replace SysVinit, Switch To Systemd Or Upstart jeremy Linux - News 0 10-28-2013 02:03 PM
SysVinit vs OpenRC vs systemd vs other init system cristi92b Linux - Newbie 2 01-07-2013 03:02 AM
What are the advantages/disadvantages of using systemd versus sysvinit? ReaperX7 Linux - General 11 10-22-2012 10:22 AM
LXer: Debian testing a systemd-to-sysvinit converter LXer Syndicated Linux News 0 08-20-2012 05:20 PM
[SOLVED] Timeout of mount /home directory during boot (systemd and sysvinit) JZL240I-U Linux - Software 3 12-22-2011 11:02 AM


All times are GMT -5. The time now is 03:02 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration