From: Marcel Holtmann <marcel@holtmann.org>
To: Szymon Janc <szymon@janc.net.pl>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] hostname: Fallback to static hostname if pretty hostname is not set
Date: Thu, 07 Feb 2013 10:31:42 +0200 [thread overview]
Message-ID: <1360225902.15783.9.camel@aeonflux> (raw)
In-Reply-To: <3769291.6MmiuAcpF2@athlon>
Hi Syzmon,
> > I am also not convinced that we should bother with the static hostname
> > at all. I left this out on purpose. My thinking here was that if we do
> > not have a pretty hostname, then why bother with trying to make
> > something useful out of the hostname, it would be ugly or wrong anyway.
>
> Maybe not that fancy as pretty hostname but at least know to user(e.g for
> some reason my Fedora doesn't have pretty hostname set and falling back to
> static hostname makes adapter name somewhat reasonable).
> Also falling back to static hostname will allow hostname plugin to number
> adapters' names. Yet, maybe main.conf parsing should be fixed instead to
> properly substitute %h/%d as stated in comment. Currently name is simply set
> to string '%h-%d' in such case...
I actually want to get rid of main.conf for default installs. And you
might have seen this already. We do not install it anymore. The defaults
should work as good as possible. Goal is to actually create stateless
systems without requiring /etc.
Regards
Marcel
prev parent reply other threads:[~2013-02-07 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 21:10 [PATCH 1/2] hostname: Fallback to static hostname if pretty hostname is not set Szymon Janc
2013-02-05 21:10 ` [PATCH 2/2] adapter: Set default adapter id sooner Szymon Janc
2013-02-06 7:57 ` Marcel Holtmann
2013-02-06 19:54 ` Szymon Janc
2013-02-06 7:44 ` [PATCH 1/2] hostname: Fallback to static hostname if pretty hostname is not set Marcel Holtmann
2013-02-06 20:29 ` Szymon Janc
2013-02-07 8:31 ` Marcel Holtmann [this message]
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=1360225902.15783.9.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=szymon@janc.net.pl \
/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;
as well as URLs for NNTP newsgroup(s).