DragonFly commits List (threaded) for 2006-10
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
Re: cvs commit: src/usr.sbin/config configvers.h main.c mkmakefile.c mkoptions.c src/sys Makefile src/sys/amd64/amd64 genassym.c src/sys/amd64/include acpica_machdep.h asm.h atomic.h bootinfo.h console.h coredump.h cpu.h cpufunc.h elf.h endian.h exec.h float.h ...
:Matthew Dillon wrote:
:> sys/<ARCH>/conf/<KERNEL> -> sys/config/<KERNEL>
:
:Wouldn't sys/arch/<ARCH>/conf/<KERNEL> be better? Otherwise, why here?
:
:Cheers,
:--
: Thomas E. Spanjaard
: tgen@xxxxxxxxxxxxx
I considered it, but it isn't very user friendly to have to
have your config files spread out all over the place. The most
likely scenario for a DragonFly user is going to be a couple of
configs for a virtual kernel architectures, a few for IA32 (UP and
SMP), and ultimately a few for IA64. I think it makes a lot more
sense for those files to be in one place. Also, having to specify
the machine architecture in the config file AND put the config file
in a special architecture-specific place is kinda redundant.
-Matt
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]