mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: poma <pomidorabelisima@gmail.com>
To: systemd Mailing List <systemd-devel@lists.freedesktop.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Community support for Fedora users 
	<users@lists.fedoraproject.org>,
	Tom Horsley <horsley1953@gmail.com>
Subject: Re: [...] "How does the new naming scheme look like, precisely?"
Date: Wed, 15 Mar 2017 09:36:00 +0100	[thread overview]
Message-ID: <3bb2a438-fe86-57f6-5374-420e574bf147@gmail.com> (raw)
In-Reply-To: <20170314121641.735405a6@zooty>

On 14.03.2017 17:16, Tom Horsley wrote:
> And the consistent names change every single time some
> developer decides he just has to rewrite the algorithm
> to make it better, or systemd decides to engluph yet
> another component and not be backward compatible, or
> a kernel developer gets a new motherboard where the
> scheme doesn't work and his fix has the side effect
> of changing the names on thousands of existing systems, etc.
> 
> There have been at least 3 different "immutable" name
> schemes in the short time the whole concept has existed.
> 
> I finally decided to eradicate it and go back to eth0
> and friends because it was infinitely more reliable than
> having to discover yet another naming scheme in every damn
> release.
> 
> Now my only problem will be that they'll probably keep changing
> the name of the kernel option to disable it :-).
> 

This sounds quite disturbing,
can someone from the systemd and kernel campus comment here,
as Tom claims, whether these are the facts?

           reply	other threads:[~2017-03-15  8:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20170314121641.735405a6@zooty>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3bb2a438-fe86-57f6-5374-420e574bf147@gmail.com \
    --to=pomidorabelisima@gmail.com \
    --cc=horsley1953@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=systemd-devel@lists.freedesktop.org \
    --cc=users@lists.fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®