From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: hostname command
Date: Mon, 11 Oct 2010 14:28:00 -0000 [thread overview]
Message-ID: <4CB31EEC.3050605@redhat.com> (raw)
In-Reply-To: <7E93C5822639AC4B917B413898A805AAA431EA7FAC@ADM-EXMBX0CD.adm.c.sdu.dk>
On 10/09/2010 12:15 AM, Hans Jørgen Aagaard Jensen wrote:
> Hi
>
> "hostname" in cygwin does not accept the normal unix/linux options as "-f", "-d", etc.
That's correct - cygwin's hostname(1) comes from coreutils, which does
not support all the options that some other hostname(1) implementations
provide.
> We are using "hostname -f" when compiling our quantum chemistry package Dirac,
Which is inherently non-portable - you'll have to update your package to
be prepared for the fact that -f might not work on all systems.
> I would therefore appreciate if someone would implement at least the "-f" option of the hostname command,
If you want it in coreutils, then propose it upstream to the
bug-coreutils AT gnu DOT org list. Otherwise, if you are proposing that
the cygwin distro use a different hostname(1) implementation than what
is provided by coreutils, then please propose a new package for that
implementation, and coordinate on cygwin-apps about transitioning
hostname from coreutils over to the new package.
> PS. the builtin hostname in bash just ignore options. I am referring to /bin/hostname.exe.
Bash does not have a builtin hostname. When you type hostname in bash,
you ARE using /bin/hostname, which is currently from coreutils.
--
Eric Blake eblake@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2010-10-11 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 6:15 Hans Jørgen Aagaard Jensen
2010-10-11 14:28 ` Eric Blake [this message]
2010-10-11 16:01 ` Charles Wilson
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=4CB31EEC.3050605@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).