From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] rfc: /etc/hostname on gentoo
Date: Wed, 24 Aug 2016 11:49:42 -0400 [thread overview]
Message-ID: <CAJ0EP41_eJtgeU+OapX3m2QM7MH_b9S8NhYA4pML4WY3+d8aRQ@mail.gmail.com> (raw)
In-Reply-To: <45fe53a7-626f-62af-398c-2397aedb3064@gentoo.org>
On Wed, Aug 24, 2016 at 7:42 AM, Michael Orlitzky <mjo@gentoo.org> wrote:
> On 08/24/2016 07:37 AM, Daniel Campbell wrote:
>>
>> I imagine _someone_ out there wants it, otherwise we wouldn't be
>> discussing it.
>
> The thread started out proposing it as a solution to a docker problem
> that, it turns out, isn't a problem. Why are we still trying to fixing
> something that isn't broken? Maybe I'm losing it, but nowhere in the
> whole thread has anyone given a single reason why this might be useful.
You're right that the orignal purpose of the change has been debunked.
So, starting over: one real benefit would be cross-compatibility with
systemd. It's one less thing people would need to reconfigure when
migrating to/from openrc.
And before anyone starts an argument about it, I don't care what your
opinion on systemd is. I'm just throwing this out there as an actual
benefit of adding support for /etc/hostname to openrc.
next prev parent reply other threads:[~2016-08-24 15:50 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 15:58 [gentoo-dev] rfc: /etc/hostname on gentoo William Hubbs
2016-08-22 16:11 ` M. J. Everitt
2016-08-22 16:39 ` Rich Freeman
2016-08-22 17:03 ` William Hubbs
2016-08-22 17:32 ` Rich Freeman
2016-08-22 17:28 ` Michael Orlitzky
2016-08-22 17:51 ` Sven Vermeulen
2016-08-22 18:29 ` Rich Freeman
2016-08-23 19:59 ` Marc Schiffbauer
2016-08-22 17:37 ` Matthew Thode
2016-08-22 17:51 ` Matthew Thode
2016-08-22 19:18 ` Dirkjan Ochtman
2016-08-22 19:28 ` Hans de Graaff
2016-08-22 20:01 ` William Hubbs
2016-08-22 22:09 ` William Hubbs
2016-08-23 6:39 ` Daniel Campbell
2016-08-23 7:01 ` Christian Kniep
2016-08-23 12:33 ` Michael Orlitzky
2016-08-23 10:01 ` Rich Freeman
2016-08-23 12:26 ` Christian Kniep
2016-08-23 18:45 ` Rich Freeman
2016-08-23 19:57 ` William Hubbs
2016-08-23 20:25 ` Rich Freeman
2016-08-23 21:22 ` William Hubbs
2016-08-24 6:52 ` Christian Kniep
2016-08-24 6:56 ` Christian Kniep
2016-08-24 10:46 ` Rich Freeman
2016-08-24 7:12 ` Daniel Campbell
2016-08-24 11:17 ` Michael Orlitzky
2016-08-24 11:37 ` Daniel Campbell
2016-08-24 11:42 ` Michael Orlitzky
2016-08-24 12:40 ` Rich Freeman
2016-08-24 15:49 ` Mike Gilbert [this message]
2016-08-24 16:06 ` Michael Orlitzky
2016-08-24 16:22 ` Zac Medico
2016-08-24 16:33 ` Michael Orlitzky
2016-08-24 16:42 ` Zac Medico
2016-08-24 19:23 ` Consus
2016-08-24 22:43 ` Cédric Krier
2016-08-28 6:30 ` Daniel Campbell
2016-08-28 6:48 ` Michał Górny
2016-08-28 7:24 ` Daniel Campbell
2016-08-28 6:57 ` M. J. Everitt
2016-08-28 8:10 ` Zac Medico
2016-08-28 12:34 ` Patrick Lauer
2016-08-28 14:16 ` Rich Freeman
2016-08-28 14:21 ` Michał Górny
2016-08-28 15:29 ` Patrick Lauer
2016-08-28 15:54 ` Rich Freeman
2016-08-25 4:11 ` [gentoo-dev] " Duncan
2016-08-25 12:50 ` Mike Gilbert
2016-08-25 13:42 ` Rich Freeman
2016-08-24 8:02 ` Martin Vaeth
2016-08-23 12:17 ` [gentoo-dev] " Michael Orlitzky
2016-08-28 18:15 ` William Hubbs
2016-08-31 21:24 ` Daniel Campbell
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=CAJ0EP41_eJtgeU+OapX3m2QM7MH_b9S8NhYA4pML4WY3+d8aRQ@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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