Date: Mon, 17 Jan 2000 23:29:06 +0100 From: Wilko Bulte <wilko@yedi.iaf.nl> To: Seigo Tanimura <tanimura@r.dl.itc.u-tokyo.ac.jp> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/release/texts/alpha HARDWARE.TXT src/release/texts/i386 HARDWARE.TXT Message-ID: <20000117232905.C5824@yedi.iaf.nl> In-Reply-To: <14466.56531.14048.11700X@rina.r.dl.itc.u-tokyo.ac.jp>; from tanimura@r.dl.itc.u-tokyo.ac.jp on Mon, Jan 17, 2000 at 06:11:47PM %2B0900 References: <200001150625.WAA20461@freefall.freebsd.org> <20000115110114.A53766@yedi.iaf.nl> <14466.56531.14048.11700X@rina.r.dl.itc.u-tokyo.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 17, 2000 at 06:11:47PM +0900, Seigo Tanimura wrote:
> On Sat, 15 Jan 2000 11:01:14 +0100,
> Wilko Bulte <wilko@yedi.iaf.nl> said:
>
> Wilko> Wouldn't it be better to have a shared HARDWARE.TXT for both currently
> Wilko> supported architectures (moved to release/texts) and a port-specific
> Wilko> one in release/texts/[i386,alpha]? I'm currently writing a ALPHAHW.TXT
> Wilko> that I think fits in this picture.
>
> When it comes to reading the HARDWARE.TXTs, it may be a trouble to
> read two separate files. Why don't we have the arch-independent and
> arch-specific HARDWARE.TXTs and generate only one note from them for
> each architecture?
You mean something like:
cat HARDWARE.TXT <platform>/HARDWARE.TXT > ${FD}/HARDWARE.TXT ?
Can be done.. hmm. Jordan told me the file better keep the name HARDWARE.TXT
or sysinstall needs adaptations. Which is undesirable for something like
this.
Will I be shot if I propose the following:
- (mostly) remove the section "2. Supported configurations" from both
i386/alpha RELNOTES.TXT and insert a pointer to the HARDWARE.TXT file?
This keeps all supported h/w stuff in one file (HARDWARE.TXT) and reduces
the chance that things go out of sync.
- move the i386/HARDWARE.TXT to release/texts (so one level down)
and take that as the starting point for the 'generic' HARDWARE.TXT
With i386 being the leading port of FreeBSD this can be taken as the
reference, reducing the need to completely overhaul the HARDWARE.TXT
This file then will be the master file in which all new supported hardware
is listed.
- create a alpha/HARDWARE.TXT which contains the specifics for the
specific platform. So, this file contains the things that are not supported
on alpha, and the Alpha hardware overview I wrote over the last couple of
weeks (currently named release/alpha/ALPHAHW.TXT)
- change release/Makefile to concat the HARDWARE.TXT files and put them in
the right release-areas.
Wilko
--
Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project
WWW : http://www.tcja.nl http://www.freebsd.org
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?20000117232905.C5824>