LWN.net Logo

Poettering: The Biggest Myths

Poettering: The Biggest Myths

Posted Feb 4, 2013 21:03 UTC (Mon) by anselm (subscriber, #2796)
In reply to: Poettering: The Biggest Myths by mgb
Parent article: Poettering: The Biggest Myths

Read the effing documentation already. A convenient link has been provided to you earlier in this thread.

  • This is not a systemd issue in any way, shape, or form. It is a udev issue. Systemd and udev share maintainers but this is as far as it goes. There are people on System V init who have similar problems with naming their NICs, and they can solve them by installing the appropriate version of udev (out of the systemd tarball) without actually having to move to systemd.
  • Nobody prevents you from staying with eth0 etc. even under the new udev. How to achieve this is documented in excruciating detail in the documentation mentioned earlier. It is very easy.

We understand that you're not so hot on systemd. However your position would be that much more tenable if you had actual valid criticisms informed by facts. Judging from your last few postings this does not appear to be the case.


(Log in to post comments)

Poettering: The Biggest Myths

Posted Feb 4, 2013 21:10 UTC (Mon) by dlang (✭ supporter ✭, #313) [Link]

you must have missed the memo where the maintainers merged the projects and have made it so that you can't build udev independently of systemd

Yes, the problems he is describing started off as udev problems, but they are now systemd problems

Poettering: The Biggest Myths

Posted Feb 4, 2013 21:21 UTC (Mon) by anselm (subscriber, #2796) [Link]

You don't need to install systemd in order to install udev. If you start from sources you have to build both but it is perfectly possible to install (or package for installation) udev without anything from systemd.

This has all been explained to death here already.

Poettering: The Biggest Myths

Posted Feb 4, 2013 21:23 UTC (Mon) by raven667 (subscriber, #5198) [Link]

They do share build infrastructure but you can run them independently so running udev doesn't imply running systemd. You're not going to get some kind of systemd cooties from building the shared components you don't end up needing if you just want udev. 8-)

Poettering: The Biggest Myths

Posted Feb 6, 2013 5:35 UTC (Wed) by spaetz (subscriber, #32870) [Link]

> This is not a systemd issue in any way, shape, or form. It is a udev issue. Systemd and udev share maintainers but this is as far as it goes.

Not leaning in on the pro/contra discussion, but this is an exaggeration by far. The announcement (http://lwn.net/Articles/490413/) makes it clear that they "merge the udev sources into the systemd source tree."

To me that indicates strongly that systemd and udev are more than two independent tarballs that can be version mix-and-matched and just happen to have the same maintainers.

Poettering: The Biggest Myths

Posted Feb 6, 2013 12:05 UTC (Wed) by HelloWorld (guest, #56129) [Link]

> Not leaning in on the pro/contra discussion, but this is an exaggeration by far.
No, it's not. udev does the interface naming stuff and systemd has nothing at all to do with it.

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds