Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.os.linux.slackware > #35696
| From | Lew Pitcher <lew.pitcher@digitalfreehold.ca> |
|---|---|
| Newsgroups | alt.os.linux.slackware |
| Subject | Re: SysVinit vs BSDinit |
| Date | 2026-07-09 15:46 +0000 |
| Organization | The Pitcher Digital Freehold |
| Message-ID | <112ofov$ccum$4@dont-email.me> (permalink) |
| References | <112o9as$ee8h$1@dont-email.me> <112oe09$fr1i$1@dont-email.me> |
On Thu, 09 Jul 2026 15:16:25 +0000, Rich wrote: > Marco Moock <mm@dorfdsl.de> wrote: >> Hello! >> >> The package sysvinit-scripts provides the init scripts, but they are not >> located in /etc/init.d, but in /etc/rc.d, like FreeBSD does. >> >> Some people say Slackware provides SysVinit, some BSD-like init. >> >> What are the differences here? >> >> IIRC FreeBSD does not have run levels. > > In addition to what Lew posted, one other big difference is that > traditional SYSV init script styling has the scripts linked as an ugly > forest of symlinks beneath /etc/rc.d/rc?.d/ directories pointing to the > actual scripts, with the names of the symlinks defining the order in > which each is executed. Each "script" in effect being little more than > a small "function" in a larger program. > > BSD style init has the scripts as actual scripts (i.e., multiple > functions inside each script file), which execute each other as they go > along as needed, but without the symlink forest indirection to have to > parse through to figure out what is, or is not, executed. As you can tell, I've not had much experience with a true SysV init system. I had forgot about the symlink forest; my only real experience was on an IP04 linux-based PSTN&VoIP telephony device, which used the SysV style symlink forest quite extensively. -- Lew Pitcher "In Skills We Trust" Not LLM output - I'm just like this.
Back to alt.os.linux.slackware | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
SysVinit vs BSDinit Marco Moock <mm@dorfdsl.de> - 2026-07-09 15:56 +0200
Re: SysVinit vs BSDinit Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2026-07-09 14:25 +0000
Re: SysVinit vs BSDinit Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2026-07-09 14:27 +0000
Re: SysVinit vs BSDinit Rich <rich@example.invalid> - 2026-07-09 15:16 +0000
Re: SysVinit vs BSDinit Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2026-07-09 15:46 +0000
Re: SysVinit vs BSDinit Marco Moock <mm@dorfdsl.de> - 2026-07-10 07:01 +0200
Re: SysVinit vs BSDinit jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-07-10 13:16 -0400
Re: SysVinit vs BSDinit Rich <rich@example.invalid> - 2026-07-11 01:22 +0000
Re: SysVinit vs BSDinit Marco Moock <mm@dorfdsl.de> - 2026-07-11 07:26 +0200
Re: SysVinit vs BSDinit John McCue <jmclnx@gmail.com.invalid> - 2026-07-11 15:16 +0000
Re: SysVinit vs BSDinit Mike Small <smallm@panix.com> - 2026-07-23 13:27 -0400
Re: SysVinit vs BSDinit John McCue <jmclnx@gmail.com.invalid> - 2026-07-23 23:36 +0000
Re: SysVinit vs BSDinit steve g <Sgonedes1977@gmail.com> - 2026-08-06 18:45 -0400
Re: SysVinit vs BSDinit Marco Moock <mm@dorfdsl.de> - 2026-08-07 07:16 +0200
Re: SysVinit vs BSDinit Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2026-08-10 05:43 +0000
Re: SysVinit vs BSDinit Rich <rich@example.invalid> - 2026-08-10 22:14 +0000
Re: SysVinit vs BSDinit Mike Small <smallm@panix.com> - 2026-08-15 00:15 -0400
Re: SysVinit vs BSDinit Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2026-08-16 11:06 +0000
csiph-web