Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Sep 2019 12:00:12 -0400 (EDT)
From:      doug@fledge.watson.org
To:        Polytropon <freebsd@edvax.de>
Cc:        Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>, freebsd-questions@freebsd.org
Subject:   Re: Where is the info viewer?
Message-ID:  <alpine.BSF.2.20.1909111123160.59741@fledge.watson.org>
In-Reply-To: <20190911160926.5b3549c3.freebsd@edvax.de>
References:  <20190910070033.GA29721@admin.sibptus.ru> <alpine.BSF.2.20.1909102030500.59741@fledge.watson.org> <20190911041439.9ba45e18.freebsd@edvax.de> <10971217-3072-cfee-785d-3748e9879a2f@gmail.com> <20190911110708.95a9b3f8.freebsd@edvax.de> <44ftl3hrdf.fsf@be-well.ilk.org> <20190911160926.5b3549c3.freebsd@edvax.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 11 Sep 2019, Polytropon wrote:

> On Wed, 11 Sep 2019 09:52:44 -0400, Lowell Gilbert wrote:
>> Polytropon <freebsd@edvax.de> writes:
>>
>>> On a fresh install of FreeBSD 12.0 amd64, I installed something via pkg,
>>> and then used "man <something>", which complained that I need to install
>>> groff. I did that - and the manpage could be read. I'm just mentioning
>>> this because I've never seen this before...
>>
>> Historically, man(1) was essentially "nroff -man" under the covers.
>
> Older FreeBSD versions came with /usr/bin/groff - similar problem
> as with info, except that _some_ manpages were available without
> installing 3rd party software (probably already processed and
> rendered, and in that form part of the default installation).
>
> I've also been using groff to turn man entries into PDF files. :-)

Now that's clever. I'll bet you can read and modify /etc/termcap :)

>From another email in this thread:

> It's like how tools like dig and bind disappeared from the base system. They 
> are now in ports and can be installed optionally. However, if a documentation 
> file is still part of the OS, and installed along with the tools comprising 
> the OS, the corresponding reader (!) should also be part of the OS. Or at 
> least a placeholder, which could be a script that simply echo "This tool is no 
> longer part of FreeBSD, please install this or that.", exit 0. :-)


My thought on texinfo was that this was a bit different than when nslookup, dig, 
and bind were removed from the base. To the level I use drill it has the same 
syntax as dig, nslookup functions can [mostly??] be done with host. Bind is, 
well, bind. Here we remove the tool needed to read a set of files from the base 
but leave the files. I suspect there will be a lot of this when sendmail is 
removed from the base.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1909111123160.59741>