Gentoo Archives: gentoo-amd64

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-amd64@l.g.o
Subject: [gentoo-amd64] Re: Boycott Systemd
Date: Mon, 22 Sep 2014 20:24:55
Message-Id: pan$ac534$3b3abde0$e9e04042$4fa6a67a@cox.net
In Reply to: Re: [gentoo-amd64] Boycott Systemd by Frank Peters
1 Frank Peters posted on Mon, 22 Sep 2014 14:41:14 -0400 as excerpted:
2
3 > Good design is highly flexible and configurable with little assumption
4 > made on the nature or needs of the user.
5 >
6 > Let's consider a simple program to display digital images. A good
7 > program design will not only contain built-in routines to accommodate
8 > the standard image formats but will also provide non-specific raster
9 > buffers to allow a user to view unconventional or even non-existent
10 > formats. A good program design will also make no assumptions about the
11 > nature of the image data but rather allow the user to create any needed
12 > specifications. A professional program thus allows both standard
13 > conventions but keeps the overall capability unrestricted and open
14 > ended.
15 >
16 > As best as I can understand (I am not an expert in systems programming)
17 > under Torvalds the Linux OS conforms to such professional design goals.
18
19 /The/ Linux OS? There is no such single entity.
20
21 There is /the/ Linux kernel. There are all sorts of OSs designed and
22 deployed for all sorts of different usage, using that kernel. Linus
23 controls the kernel, and had a hand in developing a few relatively
24 insignificant userspace bits that run on that kernel and some subset of
25 available userspace OS platforms, but he doesn't control userspace, and
26 AFAIK, has no interest in doing so.
27
28 By raw number of deployments out there "The Linux OS" would have to refer
29 to Android. But systemd isn't part of the Android Linux OS/platform, nor
30 does Android have much to do with the gentoo of the list on which this
31 discussion is taking place, so that doesn't make sense in the context of
32 this thread.
33
34 In the context of this thread, one might make an educated guess that what
35 you refer to as "The Linux OS" would be what is technically known as
36 GNU/Linux, the GNU libc and various development tools, etc, that run on
37 top of it and the Linux kernel, and on which most common Linux
38 distributions other than android, including gentoo, base themselves.
39
40 And while individual bits of that platform may have happened to conform
41 to your description in the past, there's no reason other bits included in
42 the most common implementations of that platform in the future have to
43 continue to do so. That's fine, however, as it's all FLOSS, and devs and
44 users are free to develop and use what works for them best, forking off
45 of the most common solution where they find it worth their while to do
46 so. If /enough/ people do so, then the most common solution will switch
47 to a different one as a result.
48
49 Which at a slightly different level is what we've already seen happen
50 with Android. Enough people found it useful that it's now the most
51 common, rather more so than GNU/Linux. But the same GNU/Linux ecosystem
52 and its many variants that was around before, still continues to exist,
53 as enough people with the skills to continue to continue development,
54 continue to find it useful enough to do just that, continue development.
55
56 Which is exactly the situation non-systemd GNU/Linux looks to be headed
57 for as well. The systemd variant appears to be fast becoming the most
58 common, but at least at this point, there's enough interest in the
59 continued existence and development of non-systemd variants, that they
60 continue to exist and will continue to do so for the foreseeable future,
61 as well.
62
63 --
64 Duncan - List replies preferred. No HTML msgs.
65 "Every nonfree program has a lord, a master --
66 and if you use the program, he is your master." Richard Stallman