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 ...

["Thomas E. Spanjaard" <tgen@xxxxxxxxxxxxx>]

Matthew Dillon wrote:
> :Matthew Dillon wrote:
> :>   sys/<ARCH>/conf/<KERNEL> -> sys/config/<KERNEL>
> :Wouldn't sys/arch/<ARCH>/conf/<KERNEL> be better? Otherwise, why here?
>     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.

I think you mean AMD64 over IA64, but do you intend to introduce 
GENERIC.IA32, GENERIC.x86-64, GENERIC.IA64, GENERIC.PowerPC64, 
GENERIC.POWER64 etc? Because you obviously can't use the same config 
file for multiple archs unless you intend to introduce some sort of 
conditionals in the config(8) syntax.

Cheers,
--
        Thomas E. Spanjaard
        tgen@xxxxxxxxxxxxx

Attachment: signature.asc
Description: OpenPGP digital signature