From owner-freebsd-sparc Wed Jan 19 8:55:17 2000 Delivered-To: freebsd-sparc@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 958E415370 for ; Wed, 19 Jan 2000 08:55:05 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id JAA11749; Wed, 19 Jan 2000 09:18:22 -0800 (PST) Date: Wed, 19 Jan 2000 09:18:22 -0800 From: Alfred Perlstein To: Lyndon Griffin Cc: freebsd-sparc@FreeBSD.ORG Subject: Re: Sparc Port -- sounds good to me Message-ID: <20000119091822.U8736@fw.wintelcom.net> References: <200001191159.GAA03673@bg-tc-ppp596.monmouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from lgriffin@bsd4us.org on Wed, Jan 19, 2000 at 07:29:35AM -0500 Sender: owner-freebsd-sparc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Lyndon Griffin [000119 04:57] wrote: > > > > Should we start with OpenBSD and begin with the userland stuff first > > to see how much ports over easily? > > Even a better idea, I think someone here already suggested it... It would > be nice if it works. Porting over userland may be able to be accomplished > independently of the actual kernel and hardware coding, by using a NetBSD > or OpenBSD base system. > > While porting the kernel may be the most difficult, porting the userland > will certainly be tedious - once something is ported, it will need to > track current with the rest of the "real" distribution, otherwise we'll > end up duplicating our efforts when the kernel work is ready for merging > into current. > > > Me - I *love* FreeBSD. There's not a lot of chance that I'll cease work > when we merge into -current... Maybe Jordan will step in and correct me > here, but just getting to the goal is only half the trip - once we merge, > we'll have to keep on going. There's no magical code fairy that takes > over maintenance of the port once we become part of the distribution. > Somebody (hopefully more than one person) has to keep the port up to date > with new features, kernel changes, new drivers, etc. etc. What I'm trying > to get at, without being too heavy, is that I sincerely hope that people > that will commit to do the work now are also committing to do the work in > the future. > As the guy who promised to start working on the sparc port but never got around to do anything... for my sins I'll provide an ongoing merge effort and I assume that when some promise is shown people whom I'm proxying commits for will eventually be given cvs access, although that's not for me to decide, just recommend. good luck, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message