Date: Thu, 19 Feb 1998 21:31:29 -0600 From: Dan Nelson <dnelson@emsphone.com> To: Robert Withrow <witr@rwwa.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: Info file annoyance Message-ID: <19980219213129.39005@emsphone.com> In-Reply-To: <199802192321.SAA00958@spooky.rwwa.com>; from "Robert Withrow" on Thu Feb 19 18:21:20 GMT 1998 References: <199802192321.SAA00958@spooky.rwwa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Feb 19), Robert Withrow said: > There is /usr/local/info and there is /usr/share/info. > > One has broken-out infofiles and one has compressed, one-piece info > files. > > Each has a different dir file (and the /usr/share/info one doesn't > work due to the compressed files, at least for me). > > Is there any chance this can be sorted out for 2.2.6 so that info > could be more usefull? Like: > > - One directory that gets to all info files, and > - Uncompressed files (if that is required for reading them). > > Thanks! Hmm. I don't see any of your problems (tested on -stable and -current). When I type info, what I see is the concatenation of usr/share/info/dir and /usr/local/info/dir. If I happen to pick an info entry that has been compressed, "gunzip < file.info.gz ..." flashes on the status line, then the uncompressed info file pops up. /usr/local/info files are probably split and uncompressed to make sure that they can be read on the lowest-common-denominator machine; a DOS PC with 640k of memory. FreeBSD can read large compressed info files, so the ones that come with the system (in /usr/share/info) take advantage of that. It's a good idea to keep base and user-compiled programs separate, anyway. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980219213129.39005>