LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
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 03-10-2021, 05:05 AM   #196
NonNonBa
Member
 
Registered: Aug 2010
Distribution: Slackware
Posts: 192

Rep: Reputation: Disabled

Quote:
Originally Posted by hitest View Post
I don't run stable, I run Slackware64-current. However, I suspect that there are some trusty old servers out there that are running 14.1.
I agree they might be trusty, but it has however far more to do with the environment they run in — for example, strictly on a LAN – than with how up-to-date they are. Beyond that, "so far so good" is not a very strong security policy.
 
Old 03-10-2021, 05:22 AM   #197
ZhaoLin1457
Senior Member
 
Registered: Jan 2018
Posts: 1,051

Rep: Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266
Quote:
Originally Posted by SCerovec View Post
Slackware already is "more like" BSD among all other GNU/Linux distros.
Umm, what?

In what sense is Slackware "more like" BSDs?

As init system? If yes, when happened this?

Please take a look there:

https://www.netbsd.org/docs/guide/en/chap-rc.html
Code:
NetBSD uses individual scripts for controlling services, similar to what System V does, but without runlevels. This chapter is an overview of the rc.d system and its configuration.
If you do not known yet, the BSDs has one single runlevel, contrary to Slackware, which like any other Linux OS, has 6 (six).

And how applies to Slackware the rc.order as dependencies resolution for init scripts?

https://wiki.netbsd.org/guide/rc/

https://man.netbsd.org/rcorder.8

Code:
     rcorder is designed to print out a dependency ordering of a set of inter-
     dependent files.  Typically it is used to find an execution sequence for
     a set of shell scripts in which certain files must be executed before
     others.

     Each file passed to rcorder should be annotated with special lines (which
     look like comments to the shell) which indicate the dependencies the
     files have upon certain points in the sequence, known as ``conditions'',
     and which indicate, for each file, which ``conditions'' may be expected
     to be filled by that file.

     Within each file, a block containing a series of ``REQUIRE'',
     ``PROVIDE'', ``BEFORE'' and ``KEYWORD'' lines should appear.  The format
     of the lines is rigid.  Each line must begin with a single ``#'', fol-
     lowed by a single space, followed by ``PROVIDE:'', ``REQUIRE:'',
     ``BEFORE:'', or ``KEYWORD:''.  No deviation is permitted.  Each depen-
     dency line is then followed by a series of conditions, separated by
     whitespace.  Multiple ``PROVIDE'', ``REQUIRE'', ``BEFORE'' and
     ``KEYWORD'' lines may appear, but all such lines must appear in a
     sequence without any intervening lines, as once a line that does not fol-
     low the format is reached, parsing stops.
If you do not known yet, the BSDs uses dependency ordering for their init scripts, contrary to Slackware where the init scripts order is hard coded on the main scripts.

I tell you those things as someone who used for many years the NetBSD and FreeBSD.

They have nothing to do with the Slackware init system more than they have with SysV init.

At least today, the Slackware is not that BSD-like, as the legends says.

Before to ask rhetorically why I use exclusively Slackware today, permit me to explain that just happened.

Almost a year ago, a power outrage (while a tempest) fried all electronic devices from my house. Starting from computers ending with the TVs and fridge. I have bought 4 computers, for my wife and my 3 boys (I have 16 years old triplets) and so on. Up to brand new air conditioners, fridge and TVs.

When I finished this shopping spree, I had moneys enough to buy for myself a SD-card. Which was pure luck, as I had this mini-PC which I use today, on those times being in storage. Slackware happened to be more versatile as for my experience, to be installed quickly on this SD-card.

And on this almost one year, I have discovered that I do not need more, for myself, than a Linux OS on SD-card. Just for browsing the Internet, nothing more.

I am not an open-source activist or systemd hatter. Neither I am a Linux Guru.

Last edited by ZhaoLin1457; 03-10-2021 at 05:44 AM.
 
4 members found this post helpful.
Old 03-10-2021, 05:50 AM   #198
hazel
LQ Guru
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 7,682
Blog Entries: 19

Rep: Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492
I see the Slackware init process as intermediate between BSD and SysV. Yes, there are nominally 6 levels because it's Linux, but they aren't much used in practice. In a proper sysV initialisation, clusters of symbolic links in the /etc/rc.d/rc.N directories launch or kill the scripts required for level N. Slackware has those directories, in case packages want to put stuff into them, but they aren't normally used. Instead you have a single script for system initialisation, another for a multiuser boot and another for shutdown/reboot. That looks like a BSD to me.

What NetBSD does reminds me very much of the old-style Debian. When Debian used sysVinit, it had this thing called "concurrent makefile booting" which worked just like that.

Last edited by hazel; 03-10-2021 at 05:52 AM.
 
Old 03-10-2021, 05:56 AM   #199
ZhaoLin1457
Senior Member
 
Registered: Jan 2018
Posts: 1,051

Rep: Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266
Quote:
Originally Posted by hazel View Post
I see the Slackware init process as intermediate between BSD and SysV. Yes, there are nominally 6 levels because it's Linux, but they aren't much used in practice. In a proper sysV initialisation, clusters of symbolic links in the /etc/rc.d/rc.N directories launch or kill the scripts required for level N. Slackware has those directories, in case packages want to put stuff into them, but they aren't normally used. Instead you have a single script for system initialisation, another for a multiuser boot and another for shutdown/reboot. That looks like a BSD to me.

What NetBSD does looks very much like old-style Debian to me. When Debian used sysVinit, it had this thing called "concurrent makefile booting" which worked just like that.
All BSDs uses rc.order and this dependency order for the init scripts, it is not specific for NetBSD.

The Slackware lacks this feature, having the order hardcoded on the main scripts, like I said.

And if you wonder how looks a BSD rc script, it's like this:
Code:
	#!/bin/sh
	#
	# $NetBSD: moused,v 1.1 2001/10/29 23:25:01 augustss Exp $
	#

 	# PROVIDE: moused
	# REQUIRE: DAEMON

	. /etc/rc.subr

 	name="moused"
	rcvar=$name
	command="/usr/sbin/${name}"

 	load_rc_config $name
	run_rc_command "$1"
More details there: https://www.linux.com/news/daemon-wr...ds-rcd-system/

So, this example script would be something like /etc/rc.d/rc.gpm, but please tell me: what it have in common with Slackware and its init scripts?

As someone who used for years two BSD distributions, I believe that Slackware init system is just a flavor of SysV init, which has nothing in common with the BSDs and their init scripts.

Last edited by ZhaoLin1457; 03-10-2021 at 06:10 AM.
 
2 members found this post helpful.
Old 03-10-2021, 06:29 AM   #200
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 4,474
Blog Entries: 7

Rep: Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573
Quote:
Originally Posted by ZhaoLin1457 View Post
As someone who used for years two BSD distributions, I believe that Slackware init system is just a flavor of SysV init, which has nothing in common with the BSDs and their init scripts.
It's not even that. Slackware's init is quite unique. There are no others like it. You are correct in your statements. It's nothing like any of the BSDs.
 
2 members found this post helpful.
Old 03-12-2021, 03:28 AM   #201
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 4,474
Blog Entries: 7

Rep: Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573
Quote:
Originally Posted by hazel View Post
In fact, people who don't know an awful lot about Linux can do a full Slackware install and they'll have a good-tempered stable system that will do everything they want and never throw a tantrum during an update (as Debian distros sometimes do). What's wrong with that?
Furthermore, it has some of the best commentary/hints/pointers exactly where you need them in the config files. You don't get that with many other distros.

On that front, Slackware is easily the most newb-friendly. Try explaining systemd unit files to a Linux newbie, versus telling them to add something to /etc/rc.d/rc.local.
 
1 members found this post helpful.
Old 03-12-2021, 04:09 AM   #202
hazel
LQ Guru
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 7,682
Blog Entries: 19

Rep: Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492
Quote:
Originally Posted by rkelsen View Post
On that front, Slackware is easily the most newb-friendly. Try explaining systemd unit files to a Linux newbie, versus telling them to add something to /etc/rc.d/rc.local.
I don't think the installer is particularly newbie-friendly. No graphics and you have to do your own partitioning. Or is that different if you install from DVD?

Also I don't think most newbies feel happy about being told to edit configuration files by hand. It's not the way they've been brought up. Remember most of our generation are familiar with command line because they have used it in office work, or administering servers, or else they've used DOS on home systems.

Actually I quite like the systemd unit files (shock! horror!). I find them easy to understand and well documented. There's a lot of things about systemd that I hate, but the way it's configured isn't one of them. The problem with init scripts is that they have to be very complex to deal reliably with all the variation between systems, and trying to edit them when you don't fully understand the logic is really difficult. I must admit that I don't meddle with them, and I do know a bit about bash scripting.

Last edited by hazel; 03-12-2021 at 04:10 AM.
 
1 members found this post helpful.
Old 03-12-2021, 06:44 AM   #203
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 4,474
Blog Entries: 7

Rep: Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573Reputation: 2573
Quote:
Originally Posted by hazel View Post
I don't think the installer is particularly newbie-friendly. No graphics and you have to do your own partitioning.
Of course I was referring to newbies who are not afraid of the CLI and are keen to learn.
 
Old 03-12-2021, 09:36 AM   #204
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,480
Blog Entries: 2

Rep: Reputation: 986Reputation: 986Reputation: 986Reputation: 986Reputation: 986Reputation: 986Reputation: 986Reputation: 986
Imagine the day Slackware ships with an touch-screen friendly installer
 
Old 03-13-2021, 03:54 AM   #205
NonNonBa
Member
 
Registered: Aug 2010
Distribution: Slackware
Posts: 192

Rep: Reputation: Disabled
Quote:
Originally Posted by hazel View Post
Actually I quite like the systemd unit files (shock! horror!). I find them easy to understand and well documented. There's a lot of things about systemd that I hate, but the way it's configured isn't one of them. The problem with init scripts is that they have to be very complex to deal reliably with all the variation between systems, and trying to edit them when you don't fully understand the logic is really difficult. I must admit that I don't meddle with them, and I do know a bit about bash scripting.
It's true with things like OpenRC, about which I understand someone could say "I can fix it!" — whatever you might think about the fix — but far less with Slackware. Its init is maybe not as flexible as you could expect, but it has the great quality of clarity.
 
Old 03-13-2021, 04:24 AM   #206
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,811

Rep: Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447
Quote:
Originally Posted by hazel View Post
I don't think the installer is particularly newbie-friendly. No graphics and you have to do your own partitioning. Or is that different if you install from DVD?
AFAIK with the exception of the LiveSlak "usb2hdd" script, any invocation of "setup" from any media results in exactly the same process. I actually prefer partitioning ahead of time outside any installer. That way I can label the partitions I intend to use and make note of exactly where I want everything to go. It seems an important lesson in the Six Ps Process.

Recently I've seen some newbies complain that they feel lost outside of a typical GUI installer, but I must confess my feelings are polar opposite. All I need to know is what is proposed to install and where and that information is often obscured or even lacking in some GUI installers. I find the Slackware installer to be clear and simple.
 
4 members found this post helpful.
Old 03-13-2021, 04:34 AM   #207
hazel
LQ Guru
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 7,682
Blog Entries: 19

Rep: Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492
Quote:
Originally Posted by enorbet View Post
I actually prefer partitioning ahead of time outside any installer. That way I can label the partitions I intend to use and make note of exactly where I want everything to go. It seems an important lesson in the Six Ps Process.

Recently I've seen some newbies complain that they feel lost outside of a typical GUI installer, but I must confess my feelings are polar opposite. All I need to know is what is proposed to install and where and that information is often obscured or even lacking in some GUI installers. I find the Slackware installer to be clear and simple.
I think a lot of Slackware users feel like that. But I don't expect most Linux newbies would understand it at all. Not after a lifetime of using Windows. Like I said, it's a generational thing.

Last edited by hazel; 03-13-2021 at 04:37 AM.
 
Old 03-13-2021, 04:35 AM   #208
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,455

Rep: Reputation: 2353Reputation: 2353Reputation: 2353Reputation: 2353Reputation: 2353Reputation: 2353Reputation: 2353Reputation: 2353Reputation: 2353Reputation: 2353Reputation: 2353
On the installer, I think it's an age thing. People who were kids in the millenium only use ½ of linux - the GUI. People fromn before that are comfortable with the other ½. It's not linux that's at issue at all. Give them Dos, and they'd want to start windows. I was very much a tty console jockey until I increased the font size. Now I prefer the gui terminals for the longer history.
 
1 members found this post helpful.
Old 03-13-2021, 04:42 AM   #209
hazel
LQ Guru
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 7,682
Blog Entries: 19

Rep: Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492Reputation: 4492
Quote:
Originally Posted by business_kid View Post
Now I prefer the gui terminals for the longer history.
You just wait till you try the new consoles! They don't scroll back at all. The new kernels don't support that any more. So it's not a question of longer history, it's a question of having any history at all.

I'm really annoyed about this. It's not Pat's fault obviously, but I'm annoyed with the kernel people. This was part of the Linux way of working and they suddenly pulled the rug out from under our feet.
 
3 members found this post helpful.
Old 03-13-2021, 04:49 AM   #210
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,811

Rep: Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447Reputation: 4447
Are you guys talking about bash history? If so I'm happy to report that Konsole is unchanged for me with up-to-the-day Current and Plasma5. My Up and Dowen arrows still scroll through a huge archive of used commands. I'd just like an easy way to eliminate duplication.

BTW I'm running 5.10.22 kernel.
 
1 members found this post helpful.
  


Reply



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
Slackware 14.2 SCIM input issue: cannot imput alpha letters(half-width) using scim, no fast searching for XFCE FileManager kcynice Slackware 0 07-21-2016 03:45 AM
LXer: K3b 2.0 Alpha Preview - First Alpha of the KDE4 Port Is Out LXer Syndicated Linux News 0 04-26-2009 05:30 PM
LXer: Mozilla Firefox 3.0 Alpha 1 (Deer Park Alpha 2) LXer Syndicated Linux News 0 04-09-2006 08:21 PM
Alpha RedHat Linux Network problem syxxpac023 Linux - Networking 0 09-07-2001 09:05 AM
Compaq Transfers Alpha to Intel jeremy General 2 07-16-2001 08:29 AM

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

All times are GMT -5. The time now is 10:53 PM.

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
Open Source Consulting | Domain Registration