Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Dec 1998 01:38:52 +0100
From:      Eivind Eklund <eivind@FreeBSD.ORG>
To:        Mike Smith <mike@smith.net.au>
Cc:        alpha@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG
Subject:   Re: cvs commit: src/share/mk bsd.kern.mk src/sys/alpha/conf Makefile.alpha
Message-ID:  <19981221013852.B10676@follo.net>
In-Reply-To: <199812202341.PAA47553@dingo.cdrom.com>; from Mike Smith on Sun, Dec 20, 1998 at 03:41:57PM -0800
References:  <19981220234419.A9903@follo.net> <199812202341.PAA47553@dingo.cdrom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> > bus/				# Bus-specific code
> > 	eisa/
> > 		dev/		# Devices for this bus
> > 			<types>	# Type specifiers for drivers
> 
> This isn't even learning from our current mistakes.  (cf. everything in 
> sys/pci that frontends for stuff in sys/i386/isa)

This was intended for the front end stuff and drivers that are by
nature tied to a specific bus.  Usually, the parts here should just
set up any magic bus-spaces or similar, and call things in /dev/.

> > This is just a very quick attempt at a hierarchially based layout; I'm
> > sure there are lots of possible improvements.
> 
> The current drive is to tear the kernel into modules wherever possible; 
> ultimately the kernel core will remain, and everything else will be 
> modules.  So:
> 
> boot				as current /sys/boot
> 	...
> compile
> 	i386			not convinced of the requirement for
> 		...		arch subdirs here.
> 	alpha
> 		...
> 	modules
> 		...

Not convinced of the requirement for sys/compile.  For a fully
functional build system, architecture is only one of the relevant
axes, the others being the options used.

Apart from that, I have no problem with your suggested layout except
that it lack detail in a number of areas.

> > > (Any ideas on how to get enough people to agree on change?)
> > 
> > Not a clue.
> 
> Almost impossible, unless you can sell them on losing the CVS history.

We'd use repository copies, of course.

If we are going to do a rearrangement, we should do it just before we
create a new release tag.  (I was thinking that with 3.0 released
right now was the worst time possible, and was going to attempt to
squash the discussion, but it really is the best - RELENG_2_2 is on
end-of-life, and RELENG_3_0 isn't put down yet).

Eivind.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981221013852.B10676>