public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Mo DeJong <mdejong@cygnus.com>
To: insight@sourceware.cygnus.com
Subject: Re: Manual for insight?
Date: Fri, 26 May 2000 20:57:00 -0000	[thread overview]
Message-ID: <Pine.SOL.3.91.1000526205226.22871B-100000@cse.cygnus.com> (raw)
In-Reply-To: <392E6F7A.373EA85E@firetalk.com>

On Fri, 26 May 2000, Keith Seitz wrote:

> Ole W Saastad wrote:
> > 
> > Does there exist a manual for insight ?
> > 
> > If yes where can I download it ?
> > 
> 
> I know that Cygnus sends something out to customers, but I don't think
> it's generally available anywhere. Insight does have a rather extensive
> online help system, though. If you click Help->Topics, you can access
> this system. There's a lot in there, and I have always attempted to keep
> it synched with the releases.
> 
> In any case, it should be a good start for learning what Insight can do.
> If there are any questions that the online docs don't answer, you can
> always post them here! :-)
> 
> Keith
> -- 
> Why chat when you can Firetalk?
> Firetalk ID: Keith (10320)
> www.firetalk.com


The most up to date "free docs" would seem to be the ones
shipped as part of the EDK (Embedded Dev Kit). Insight is
a big part of the EDK tool suite, so there are insight
docs in the html and pdf rpms.

ftp://ftp.redhat.com/pub/redhat/edk
ftp://ftp.redhat.com/pub/redhat/edk/edk-html-1.0-1.i386.rpm
ftp://ftp.redhat.com/pub/redhat/edk/edk-pdf-1.0-1.i386.rpm

Of course, these Insight docs are mixed in with some
embedded info in the Getting Started Guide.

I hope that helps
Mo Dejong
Red Hat Inc.

      reply	other threads:[~2000-05-26 20:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-25 23:33 Ole W Saastad
2000-05-26  5:35 ` Keith Seitz
2000-05-26 20:57   ` Mo DeJong [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=Pine.SOL.3.91.1000526205226.22871B-100000@cse.cygnus.com \
    --to=mdejong@cygnus.com \
    --cc=insight@sourceware.cygnus.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).