Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #15230 > unrolled thread

Re: [PATCH] Fix \H: Use getaddrinfo to get full hostname

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH] Fix \H: Use getaddrinfo to get full hostname Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-24 11:32 -0400

#15230 — Re: [PATCH] Fix \H: Use getaddrinfo to get full hostname

On Wed, Jul 24, 2019 at 05:23:27PM +0200, Thomas Deutschmann wrote:
> On 2019-07-24 16:46, Greg Wooledge wrote:
> >> I hope you are not talking about putting FQDN into a file which is
> >> expecting hostname only...
> > 
> > Yes, many people do precisely that.  They configure their systems
> > so the "hostname" command returns an FQDN, as I showed above.  (Not
> > my design, not my choice.)
> 
> I consider this as misconfiguration. :(
> 
> I can't believe that we somehow encourage people to either do something
> wrong (put FQDN where just non-FQDN is expected and bypass DNS
> mechanism) or use $(hostname -f) in PS1 when they want FQDN.

Your perspective is too limited.  Linux-based systems are very popular,
but they're not the entire Unix world.

# hostname -f
# hostname
-f
# hostname minea.eeg.ccf.org
# 


Personally, I don't like hostname returning a FQDN, but many other
people *do*.  It's common.  When I work on a system that's set that
way, I leave it set that way.

It's so common that bash has two different PS1 escape sequences to
handle it.  Has had them for decades, as far as I know.

There is nothing "wrong" about this configuration.  I don't like it,
and you clearly don't like it, but our opinions only matter to us.

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web