From: "Peter Moulding" <pmoulding@tedis.com.au>
To: <cygwin@cygwin.com>
Subject: RE: Where is iostat?
Date: Tue, 30 Apr 2002 21:17:00 -0000 [thread overview]
Message-ID: <001301c1f0b9$0d616ff0$8c00a8c0@herbert.tedis.com.au> (raw)
In-Reply-To: <4.3.1.2.20020430215455.02c91500@pop.ma.ultranet.com>
Hello Larry,
There are a lot of packages to search. I looked in cygwin.com/packages
and searched everyone that looked like a system or utility package plus
a random assortment of other packages.
Because iostat was listed in the source, I assumed it would be compiled
somewhere. I did not find anything saying there are things supplied in
source but not binary. Thank you for telling me that.
I use Cygwin to make NT and Windows 2000 machines similar to Linux and
Unix boxes so people trained on Unix can administer a mixture of servers
without having to learn new skills. It is the equivalent of installing
Samba on a Unix server so the Unix server will fit in to a mixed
environment. I am finding out that some of the Unix commands do
different things on each version of Unix and even when they perform the
same function, they may have different, incompatible options and
completely different display contents. Getting the commands to work on
something as standard as NT should be easier than working with a
'standard' operating system that has 35* different standards.
Hopefully one day the POSIX standard will be improved so a large number
of Unix commands will be included in NT and it's descendents. Hopefully
the standard will specify both the command options and the command
output format so the command will work the same on all versions of Linux
and Unix.
Until perfection happens, I just wrap a PHP script around the Unix
command to produce a standard result that looks the same and works the
same on every OS. If Cygwin does no have iostat but does have something
else displaying the same information, I can run up an iostat command in
PHP.
Thank you for explaining the difference between the source and the
package contents.
Peter
*I did some work for a Unix services company that had 35 different Unix
distributions to support before they started supporting Linux.
-----Original Message-----
From: Larry Hall (RFK Partners, Inc) [mailto:lhall@rfk.com]
Sent: Wednesday, 1 May 2002 12:04 PM
To: pmoulding@tedis.com.au; cygwin@cygwin.com
Subject: RE: Where is iostat?
Peter,
I think David was pointing you to the FAQ so that you would find
http://cygwin.com/packages/. This is the way to find out what packages
are in Cygwin. It's also the way to search the packages for strings of
interest, in this case, iostat. Is this what you did? I'm guessing
not,
though I'm a bit surprised that you somehow missed it. What threw you
off?
Anyway, iostat only shows up in 1 package, cygwin-1.3.10-1-src. This is
not a tool but rather the source implementation from newlib (i.e. the
Cygwin C library). This should tell you that you can stop downloading
packages and settle with the notion that iostat is not available in the
current packages.
Sorry.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
838 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
At 08:16 PM 4/30/2002, Peter Moulding wrote:
>Hello David,
>Neither page mentions iostat. Lots of programs are bundled in to
>packages where the package description mentions only a few or none of
>the enclosed programs.
>
>I found iostat listed in a Cygwin Web page a few days ago but did not
>bookmark the page. The page listed a directory structure that did not
>match anything in Cygwin and none of the path components matched
package
>names.
>
>That leaves me with one entry on the Cygwin site that mentioned an
>iostat.h file but nothing in the download. Through trial and error, I
>currently have 182 Mb of Cygwin installed, over 12,000 files, but still
>no iostat. Surely there must be an easier way. There must be a file
that
>lists the contents of packages.
>
>Peter
>
>-----Original Message-----
>From: David Starks-Browning [mailto:starksb@ebi.ac.uk]
>Sent: Tuesday, 30 April 2002 6:58 PM
>To: pmoulding@tedis.com.au
>Cc: cygwin@cygwin.com
>Subject: Where is iostat?
>
>On Tuesday 30 Apr 02, Peter Moulding writes:
> > I cannot find iostat and some other commands in Cygwin. How do you
>find
> > out which package contains a command?
>
>Read the Cygwin FAQ entry "Which packages should I download?". Or
>find "Package Listing" on the Cygwin home page.
>
>Not too hard, really.
>
>David
>
>
>--
>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/
--
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/
next prev parent reply other threads:[~2002-05-01 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 19:54 Peter Moulding
2002-04-30 3:11 ` David Starks-Browning
2002-04-30 20:17 ` Peter Moulding
2002-04-30 20:51 ` Larry Hall (RFK Partners, Inc)
2002-04-30 21:17 ` Peter Moulding [this message]
2002-05-01 6:17 ` Larry Hall (RFK Partners, Inc)
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='001301c1f0b9$0d616ff0$8c00a8c0@herbert.tedis.com.au' \
--to=pmoulding@tedis.com.au \
--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).