Date: Thu, 05 Jun 1997 13:21:01 -0600 From: Warner Losh <imp@village.org> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Michael Smith <msmith@atrad.adelaide.edu.au>, asami@cs.berkeley.edu, ache@nagual.pp.ru, bde@zeta.org.au, cvs-all@freebsd.org, cvs-committers@freebsd.org, cvs-etc@freebsd.org Subject: Re: cvs commit: src/etc/mtree BSD.include.dist Message-ID: <E0wZi5l-00030o-00@rover.village.org> In-Reply-To: Your message of "Wed, 04 Jun 1997 17:41:21 PDT." <10130.865471281@time.cdrom.com> References: <10130.865471281@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <10130.865471281@time.cdrom.com> "Jordan K. Hubbard" writes: : > Wasn't the whole idea behind this linking stuff to keep the <sys/*> : > etc files theoretically in sync with the current kernel so that : > rebuilding kernel-dependant tools was relatively straightforward? : : Yes, it was. However, I think that syncronization is an admirable : goal which would nonetheless be better achieved in other ways. :) That's what make install is for. Or the make includes variant of make install. Besides, it introduces some interesting security problems. If my account is compromized, and I own the header files, the intruder can then insert arbitrary code into all or nearly programs on the system. If the include files are installed properly, then this can't happen. I always do a 'cvs diff -u -r HEAD' before doing a make install, before you say what about... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0wZi5l-00030o-00>