Studying for Comptia Linux+ where can I practice Sysvinit?

mihailolja · 09-22-2018, 04:49 AM

Hello,

I can't seem to find a definitive answer as to which distro(s) still use Sysvinit and the exam has quite a few questions on this area.

Can anyone recommend a distro for this purpose?

Many thanks

Mihailo

berndbausch · 09-22-2018, 05:21 AM

Quote:

Originally Posted by mihailolja

Hello,

I can't seem to find a definitive answer as to which distro(s) still use Sysvinit and the exam has quite a few questions on this area.

Can anyone recommend a distro for this purpose?

Many thanks

Mihailo

Centos 6.x still seems to be available.

Honest Abe · 09-22-2018, 06:47 AM

Or, using distrowatch's search function -

https://distrowatch.com/search.php?o...=Active#simple

hazel · 09-22-2018, 06:50 AM

AntiX, Devuan, Crux and Slackware come to mind. There are plenty of others.

lougavulin · 09-22-2018, 07:24 AM

Quote:

Originally Posted by hazel

AntiX, Devuan, Crux and Slackware come to mind. There are plenty of others.

For Slackware I won't call its init system a SysV init system. Slackware is pretty good to learn and study things, but be careful with what is SysV and what is not.

hazel · 09-22-2018, 07:32 AM

You're right. Slackware is closer to bsdinit. As is Crux. But there is a close family resemblance between bsdinit and sysvinit. If you can understand one, you understand the other. Systemd, whether you approve of it or not, is a different kind of animal altogether.

mihailolja · 09-22-2018, 08:23 AM

Great to see so much self-less help offered!

Best Regards

Mihailo

onebuck · 09-23-2018, 10:23 AM

Hi,

Quote:

Originally Posted by hazel

You're right. Slackware is closer to bsdinit. As is Crux. But there is a close family resemblance between bsdinit and sysvinit. If you can understand one, you understand the other. Systemd, whether you approve of it or not, is a different kind of animal altogether.

I beg to differ, Slackware uses SysV

Quote:

From http://www.bilbos-stekkie.com/slack_init/en/init.html
Whoha, shock!. It says: "Used by the sysv-compatible init process". And this is Slackware?
Yes this is Slackware, and Slackware uses Sys V init. Just for kicks, lets have a look at the Slackware package description:

Quote:

From http://www.bilbos-stekkie.com/slack_init/en/init.html
bilbo@bilbo:~$ head -n 14 /var/log/packages/sysvinit-2.84-i386-18 PACKAGE NAME: sysvinit-2.84-i386-18 COMPRESSED PACKAGE SIZE: 232 K UNCOMPRESSED PACKAGE SIZE: 560 K PACKAGE LOCATION: /var/log/mount/slackware/a/sysvinit-2.84-i386-18.tgz PACKAGE DESCRIPTION: sysvinit: sysvinit (init, the parent of all processes) sysvinit: sysvinit: System V style init programs by Miquel van Smoorenburg that control sysvinit: the booting and shutdown of your system. These support a number of sysvinit: system runlevels, each with a specific set of utilities spawned. sysvinit: For example, the normal system runlevel is 3, which starts agetty sysvinit: on virtual consoles tty1 - tty6. Runlevel 4 starts xdm. sysvinit: Runlevel 0 shuts the system down. sysvinit: bilbo@bilbo:~$

Quote:

From http://www.bilbos-stekkie.com/slack_init/en/init.html
So let nobody ever tell you that Slackware does not use Sys V init. It just uses it in a "BSD style".

I totally agree with the author and could not word it any better.
Hope this helps.
Have fun & enjoy!

lougavulin · 09-23-2018, 12:04 PM

Quote:

Originally Posted by onebuck

Hi,

I beg to differ, Slackware uses SysVI totally agree with the author and could not word it any better.
Hope this helps.
Have fun & enjoy!

Quote:

Yes this is Slackware, and Slackware uses Sys V init.

Yes, you can use SysV init scripts. But the default init which runs is not SysV.

/etc/rc.d/rc.X directories are empty.

And, now :

Code:

cat /var/lib/pkgtools/packages/sysvinit-scripts-2.1-noarch-20
PACKAGE NAME:     sysvinit-scripts-2.1-noarch-20
PACKAGE DESCRIPTION:
sysvinit-scripts: sysvinit-scripts (the basic scripts used to boot your machine)
sysvinit-scripts:
sysvinit-scripts: These are the Slackware boot scripts, which are needed to start the
sysvinit-scripts: machine. Sysvinit looks for these in /etc/rc.d/.
sysvinit-scripts:

There is a init system which runs by default and is specific to Slackware. And if needed you can add and run SysV script because Slackware manage to be compatible with.

onebuck · 09-23-2018, 04:35 PM

Hi,

Maybe you should look at;

Quote:

From /etc/rc.d/rc.sysvinit

# rc.sysvinit This file provides basic compatibility with SystemV style
# startup scripts. The SystemV style init system places
# start/stop scripts for each runlevel into directories such as
# /etc/rc.d/rc3.d/ (for runlevel 3) instead of starting them
# from /etc/rc.d/rc.M. This makes for a lot more init scripts,
# and a more complicated execution path to follow through if
# something goes wrong. For this reason, Slackware has always
# used the traditional BSD style init script layout.
#
# However, many binary packages exist that install SystemV
# init scripts. With rc.sysvinit in place, most well-written
# startup scripts will work. This is primarily intended to
# support commercial software, though, and probably shouldn't
# be considered bug free.
#
# Written by Patrick Volkerding <volkerdi@slackware.com>, 1999
# from an example by Miquel van Smoorenburg <miquels@cistron.nl>.

Hope this helps.
Have fun & enjoy!

lougavulin · 09-23-2018, 06:51 PM

Quote:

Originally Posted by onebuck

Hi,

Maybe you should look at; Hope this helps.
Have fun & enjoy!

I have to say I had a hard time to understand where you wanted to go with this.

So, you see it as a true init SystemV because rc.sysvinit is provided and enable to use systemV script ?

Well, I think it is more like a compatibility thing to support systemV script (which was the init for Red Hat and main commercials distributions before SystemD) and making commercial software use easier.

As Patrick wrote it :

Quote:

# rc.sysvinit This file provides basic compatibility with SystemV style
# startup scripts.
[...] For this reason, Slackware has always
# used the traditional BSD style init script layout.
[...] This is primarily intended to
# support commercial software

I never said you could not use SysV scripts, you can. There is the SysV functions script into init.d to use them. But the purpose is not to have a SysV init, it is just to provide compatibility. From my understanding, Patrick don't like SystemV init :

Quote:

This makes for a lot more init scripts,
# and a more complicated execution path to follow through if
# something goes wrong.

So I guess, let's agree to disagree !

too

deepclutch · 09-29-2018, 12:21 AM

Devuan ASCII may be a good choice, for a SysV init based distro. Defaults to runlevel 2, unlike RedHat/Fedora's which used to have rulevel 5 as default.