1 |
Am Thu, 21 May 2015 09:36:28 +0000 (UTC) |
2 |
schrieb Duncan <1i5t5.duncan@×××.net>: |
3 |
|
4 |
> Rich Freeman posted on Wed, 20 May 2015 07:22:39 -0400 as excerpted: |
5 |
[...] |
6 |
> So while systemd's failure to have a decent stable/unstable releases |
7 |
> policy, as well as the continued featuritis, continues to bother me, |
8 |
> because gentoo /does/ keep older versions around for awhile (and because |
9 |
> being gentoo, if old versions are removed from the tree, I can always |
10 |
> dredge the old version from the installed package database or from my |
11 |
> binpkgs, and put it in my overlay), it's not the problem it might |
12 |
> otherwise be. In fact, this whole incident actually supports that... |
13 |
> because it's gentoo, I actually /have/ 218 (and older versions) still |
14 |
> available to me, despite the fact that 219 is current-latest ~arch. |
15 |
> |
16 |
> So in reality systemd hasn't been any worse than openrc was for me, and |
17 |
> in a number of ways (including documented config, real speed, cross- |
18 |
> distro standardization so google's more effective, /and/ not signficantly |
19 |
> more and possibly less show-stopping bugs than openrc), it has actually |
20 |
> been better, /despite/ the lack of a coherent stable/unstable release |
21 |
> plan. |
22 |
|
23 |
I agree, though I've only used two systemd releases till now (216 and 218). |
24 |
|
25 |
[...] |
26 |
> 2) (larger philosophical/practical context): Back in 2001/2002 when I |
27 |
> got serious about and switched to Linux, I read a couple books, but I |
28 |
> actually got my practical hands-on shell experience by rewriting several |
29 |
> of the Mandrake init-scripts, including the core sysinitrc (or whatever |
30 |
> it was called, that was nearly a decade and a half again, after all!). |
31 |
> |
32 |
> I can't believe I was the only one. |
33 |
> |
34 |
> As a result, one of the nagging fears I have about systemd, despite all |
35 |
> the improvements I believe it does bring, is that this early gateway to |
36 |
> practical shell knowledge and experience is literally disappearing before |
37 |
> our eyes, and people trying to become Linux CLI/shell literate today are |
38 |
> going to have a much harder time than people of my Linux generation did, |
39 |
> because there's far less shell scripting actually available for them to |
40 |
> work on, and it's far less prominently placed, making it much harder to |
41 |
> simply stumble upon, as I basically did. |
42 |
|
43 |
I don't know... I learned basically all of my shell scripting from trying to |
44 |
solve problems I was seeing and simply because I wanted to try out something. |
45 |
I didn't touch init scripts until I had to (for work), and by then OpenRC |
46 |
supported its own declarative style (see openrc-run(8)), so the amount of |
47 |
shell *scripting* involved was minimal (and then we switched that computer to |
48 |
Fedora, and hence to systemd). |
49 |
|
50 |
Anyway, it seems to me that "scratching your own itch" was the more basic |
51 |
motivation you had for learning shell scripting via init scripts. |
52 |
|
53 |
> Between that, and the transparency of a shell-based system init that |
54 |
> they're losing as well, today's newbies may well find it far harder to |
55 |
> get in as deeply, as quickly, as I did, and the wonders of system bootup |
56 |
> may as a result remain as practically opaque to them as an MS Windows |
57 |
> boot. |
58 |
|
59 |
I would argue that in this case people at least have the source code. But more |
60 |
importantly, the *principal* of what happens is still not very different: |
61 |
commands get executed with particular arguments and a particular environment. |
62 |
For me, personally, the latter is the least transparent, I suppose, but then |
63 |
again, "systemd show" shows you all the properties of a unit, which (in |
64 |
combination with the systemd documentation) gives you pretty much all of the |
65 |
information you need to learn what *exactly* is going on. |
66 |
|
67 |
(Of course, this is just me trying to show an alternative view point, not |
68 |
trying to make it look like this isn't a potential issue, even though from my |
69 |
perspective it isn't.) |
70 |
|
71 |
[...] |
72 |
|
73 |
-- |
74 |
Marc Joliet |
75 |
-- |
76 |
"People who think they know everything really annoy those of us who know we |
77 |
don't" - Bjarne Stroustrup |