Date: Mon, 23 Oct 2000 21:30:16 +0200 From: Szilveszter Adam <sziszi@petra.hos.u-szeged.hu> To: Kenneth W Cochran <kwc@world.std.com> Cc: freebsd-stable@freebsd.org Subject: Re: Old 4.0-R binaries remaining in 4.1.1-S Message-ID: <20001023213016.A9377@petra.hos.u-szeged.hu> In-Reply-To: <200010231430.KAA21816@world.std.com>; from kwc@world.std.com on Mon, Oct 23, 2000 at 10:30:32AM -0400 References: <200010230328.XAA16342@world.std.com> <200010231430.KAA21816@world.std.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! Apologies that I can only answer now: This evening we had an extensive network outage which caused most of the country to be cut-off from the main Internet backbone and the situation was made even worse by the fact that today is a national holiday. If your questions were already answered, please ignore this message and excuse me for the inconvenience. On Mon, Oct 23, 2000 at 10:30:32AM -0400, Kenneth W Cochran wrote: > Ok, so what "maintains" the manpage tree? The /usr/share/man and the perl man trees are rewritten by the installworld target. Since make world does not deal with ports, /usr/local/share/man is untouched. > What directories does "make installworld" update/maintain? It updates /bin, /sbin, /usr/bin, /usr/sbin, /usr/lib /usr/libdata/perl /usr/share (not the docs) /usr/libexec to name the most important. More importantly, it will not touch /usr/ports, and the whole of /usr/local and /etc. > How "safe" is it to remove things in /usr/share/man? Obviously, man pages for non-existent programs are not needed. But be relaxed... the worst thing that happens is that the man page is gone. You get it back the next time you do a make installworld. > Will "make installworld" "refresh" that heirarchy? Yes. > And how about /usr/share/man/cat*? No. It contains pages you either got with your initial install or pages you already viewed since last installworld. No need to touch it. > Hmmm, some kind of documentation would be *nice*. I'll start: > "make buildworld" compiles & builds the things in /usr/src & > outputs the resulting compiled/linked/built "things(?)" to It is not "things":-) Let's be more specific. It is object files. Installworld does the putting-into-place operation. It was separated, because buildworld is now safe to do in multi-user since it will not touch the running system while installworld certainly will. > /usr/obj. In other words, "make buildworld" builds /usr/obj > from /usr/src. Yes. > Ok, now, how about "installworld?" I know it does /bin, > /usr/bin, /sbin and /usr/sbin, & I've watched it do things in > man*, but I still have no "definitive list." See above for the most important ones. If you are very curious, just use script(1) to capture your installworld and follow in the log, what happens and how. Logging is also a good way of easily finding out and sharing with others if something fails. Hope this helps! -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001023213016.A9377>