Date: Wed, 10 Jun 1998 02:12:28 -0300 (EST) From: Joao Carlos Mendes Luis <jonny@jonny.eng.br> To: rkw@dataplex.net (Richard Wackerbarth) Cc: lcremean@tidalwave.net, jkh@time.cdrom.com, stuart@internationalschool.co.uk, eivind@yes.no, gibbs@plutotech.com, stable@FreeBSD.ORG Subject: Re: Matt Behrens: Re: kernel compile problem Message-ID: <199806100512.CAA08890@roma.coe.ufrj.br> In-Reply-To: <l0313030bb19d53ec5ce7@[208.2.87.10]> from Richard Wackerbarth at "Jun 5, 98 06:42:00 am"
next in thread | previous in thread | raw e-mail | index | archive | help
#define quoting(Richard Wackerbarth) // >The more I look at this problem, the more i think that bundling config in // >the /usr/src/sys area instead of /usr/sbin makes more sense. /usr/sbin is a // >bad place for it anyway--it's really only meant for use on the kernel, at // >least in FreeBSD. It could be like /usr/src/sys/whatever/config... // // I disagree. It is not a part of the kernel. It is a tool used to generate // the kernel. Therefore, it's only useful with the kernel sources. // Should we move "gcc", "yacc", "perl", ... into the kernel space just // because (if) // they are used to build the kernel? I think that the answer is obviously "No". The big diference is that config can not be used to compile userland programs. Although Eivind talked about userland source configuration, config will still be only a source tree tool, I think. There's no need to have config around in /usr/sbin. // >PS: Even if people don't like the idea of moving it to /usr/src/sys, // >including it in the CVS and CVSup src-sys modules would work, since it would // >keep matching versions of config together. This would help, at least. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro 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?199806100512.CAA08890>