[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: systemd-shim to be removed?



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 10/02/2014 at 07:24 AM, Rusi Mody wrote:

> On Thursday, October 2, 2014 2:30:02 PM UTC+5:30, Andrei POPESCU 
> wrote:
> 
>> On Mi, 01 oct 14, 19:08:37, Rusi Mody wrote:
>> 
>>> Looking up the documentation of the package, I see: 
>>> ------------- Description: shim for systemd This package
>>> emulates the systemd function that are required to run the
>>> systemd helpers without using the init service -------------- 
>>> To me, a non-expert user, what sense does this make? Is 2 lines
>>> normal documentation for an apt package?
> 
>> 2 lines of long description for a package is not unheard of, but
>> it does seem suboptimal. Care to suggest an improved wording?
> 
> Heh! Yes Ive done my share of filing bug-reports and doc-bugs sure 
> are good to file. However Ive very little clue about the subject so
> I dont know what to suggest.
> 
> In any case my point is more systemic than it may appear: systemd 
> (from a ordinary user perspective) is hardly a single package:
> 
> - there is some constellation of packages that makes up a
> systemd-ed debian

I'll note that this is actually a good thing, and in fact doesn't go far
enough. Avoiding (parts of) systemd would be much easier if packages
which depend on one part of it but not on (logically-unrelated) others
could express that dependency explicitly, rather than having to depend
on a single package which provides multiple parts all together.

> The above is the static view.
> 
> The dynamic view -- the upgradation path -- is even harder because 
> things (apt) can break unexpectedly. A recent example of mine was 
> that udev and systemd had gone out of sync and so my networking
> was broken. So until Michael Biebel explained it to me (countering
> others giving wrong explanations) I did not know that udev had
> something to with systemd.

The only thing that udev has to do with systemd, AFAIK, is that the
people who became the systemd developers took over udev from the
original (kernel-team-related) developers, with said developers'
blessing, and then decided to integrate it into their broader project
rather than keeping it standalone.

There are arguments for why it makes sense to have that integration -
but it wasn't always there, it (therefore demonstrably) isn't strictly
necessary, and there are also arguments to be made for why it should not
exist.

- -- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJULVUMAAoJEASpNY00KDJrTMIP/3GzGpHBasY5f/dQvnwTKVth
KIxDXvqbthKLlch68u459hhQDa8K0vvju6ovuL39chlyJG44qUNAmQYBmgiHJtuq
aLbzWuE0P58OOymWfFmgUeXteVNwzVaLeVgXqNrZ3pYqVPUjpGh61GZuaWUSB2aY
ITp1SDpZocIlxy8ftSgVEuEQXPMckfYoQuiaAMvab5gXJ9S8XCKSXrF2LyLGX442
GkFxYyYTkhIBoSkdIOeFPSmGheDsSqLQMuJ9+e2AIQufIt8ajjGQn3nedCCc9RcG
hIrHELHcqdkSfyXjacUlYhOon/978EN1Wf7069FdakPtMb/7L4FBNv2/issUIrri
aQvY0em838DCUe45Lu4Z5bZCmglPUnL2GyvjEYyJLfLvBotSMAhqaZD6DaIq0U6s
6aFTUjHFkChAw68WzPYF5ub+8wY1tfvtTvrwIcikLCwhemA9QQNWWGWyMjp06fh9
YfmcRwwWCcOmiSwhvotXd+XUvqvZJ4WoXMUPrE0aX2p2NDcQ7ITl7BRmINNxOjx1
7cAoaLTxkoFvXX0gwaozWJc32clkadDMWdui7Gkl/dm1AjPKZb9yPzDCbF/sQ2JU
WDeTQlzl/udsdRAeMk+vIBdEnsL9VEyUo9NC2nBUCHjRApcBAyOWGQD6qXJK4G8O
Z/IOWSC8/aUhOhCh8BUq
=8UCv
-----END PGP SIGNATURE-----


Reply to: