Bug 62364
| Summary: | Misleading information in the handbook | ||
|---|---|---|---|
| Product: | Documentation | Reporter: | John Duncan <agley> |
| Component: | Books & Articles | Assignee: | freebsd-doc (Nobody) <doc> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
John Duncan
2004-02-04 21:30:24 UTC
Responsible Changed From-To: freebsd-bugs->freebsd-docs Documentation PR Responsible Changed From-To: freebsd-docs->freebsd-doc Use the canonical form. John Duncan wrote:
Section 11.4.1.3 of the handbook suggests using /dev/fd/3 to capture Ghostscript output. This device is no longer
present on FreeBSD by default and when I tried to install it using fdescfs Ghostscript could not access it. This
could put off new users.
It could, indeed. However, I don't find any reference to /dev/fd/3 in
the handbook.
There is no usage other than in the printing chapter, which at the
present time
is chapter 9. Maybe your doc tree is out of date, or the situation has
changed and
not been noted in response to your PR?
% pwd
/usr/doc/en_US.ISO8859-1/books/handbook
% ll .. | grep handbook
drwxr-xr-x 19 root wheel 3072 Aug 25 16:32 arch-handbook/
drwxr-xr-x 13 root wheel 2560 Aug 25 16:32 developers-handbook/
drwxr-xr-x 33 root wheel 8704 Aug 31 21:26 handbook/
drwxr-xr-x 3 root wheel 3072 Aug 31 21:27 porters-handbook/
% grep /fd/ *
pgpkeys-developers.html:W4tUdPq/fd/u54L7tUTo4lK7Os6JVwR3AfBtnyVR41j4QAu0yRW0JokCHAQTAQIA
printing-advanced.html:class="FILENAME">.dvi</tt> so using <tt
class="FILENAME">/dev/fd/0</tt> for standard
printing-advanced.html:class="FILENAME">/dev/fd/0</tt>, thereby forcing
<tt class="COMMAND">dvilj2p</tt> to read
printing-advanced.html:ln -s /dev/fd/0 hpdf$$.dvi || fatal "Cannot
symlink /dev/fd/0"
Perhaps this can be closed?
Kevin Kinsey
On Tue, Oct 19, 2004 at 05:20:26AM +0000, Kevin D. Kinsey, DaleCo, S.P. wrote: > The following reply was made to PR docs/62364; it has been noted by GNATS. > > From: "Kevin D. Kinsey, DaleCo, S.P." <kdk@daleco.biz> > To: freebsd-gnats-submit@FreeBSD.org, agley@optusnet.com.au > Cc: > Subject: Re: docs/62364: Misleading information in the handbook > Date: Tue, 19 Oct 2004 00:14:26 -0500 > > John Duncan wrote: > > Section 11.4.1.3 of the handbook suggests using /dev/fd/3 to capture Ghostscript output. This device is no longer > present on FreeBSD by default and when I tried to install it using fdescfs Ghostscript could not access it. This > could put off new users. > % grep /fd/ * > pgpkeys-developers.html:W4tUdPq/fd/u54L7tUTo4lK7Os6JVwR3AfBtnyVR41j4QAu0yRW0JokCHAQTAQIA > printing-advanced.html:class="FILENAME">.dvi</tt> so using <tt > class="FILENAME">/dev/fd/0</tt> for standard > printing-advanced.html:class="FILENAME">/dev/fd/0</tt>, thereby forcing > <tt class="COMMAND">dvilj2p</tt> to read > printing-advanced.html:ln -s /dev/fd/0 hpdf$$.dvi || fatal "Cannot > symlink /dev/fd/0" > > Perhaps this can be closed? Well there's a /dev/fd/0 there which suffers from the same problem. Ceri -- State Changed From-To: open->closed Kevin D. Kinsey's statement that this was no longer a problem since there are no references to /dev/fd/3 was correct; devfs provides /dev/fd/[0-2] anyway so my objection falls down. |
