public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Robinow, David" <drobinow@dayton.adroit.com>
To: cygwin@cygwin.com
Subject: RE: how to find utilities? is there a hostid command?
Date: Wed, 17 Jul 2002 12:03:00 -0000	[thread overview]
Message-ID: <80575AFA5F0DD31197CE00805F650D767B2260@wilber.adroit.com> (raw)

> From: Ralf Hauser [mailto:ralfhauser@gmx.ch]
> Subject: how to find utilities? is there a hostid command?
> 
> Apparently, a man page for hostid.1 already exists since 2001.
> My questions therefore are:
> 1) Is the corresponding command available within cygwin? If 
> so, in which
> part?
  No.
> 2) How can I find out whether some tools/commands are available under
> cygwin in a deterministic way without downloading and installing
> everything? E.g. the website http://cygwin.com/ doesn't 
> appear to have a search function for this purpose.
 I'm surprised by this last statement.  The link to "find a package or file
in the cygwin release" is rather prominently displayed at http://cygwin.com.
How did you miss this?
  The link sends you to http://cygwin.com/packages/ which lets you query.
You should then find that hostid.c exists in the sh-utils packages.  It's
not immediately clear why there's no hostid.exe.
 The answer is that configure flunks the test for "gethostid" and thus
doesn't build it.  I have no idea if there's a reason why "gethostid" is not
implemented.  If this interests you, you might search the mailing list
archives.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2002-07-17 17:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 12:03 Robinow, David [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-17 11:33 Keen Wayne A Contr AFRL/MNGG
2002-07-17 11:08 Vince Hoffman
2002-07-17 10:31 Ralf Hauser

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=80575AFA5F0DD31197CE00805F650D767B2260@wilber.adroit.com \
    --to=drobinow@dayton.adroit.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).