From owner-freebsd-current@FreeBSD.ORG Sat Oct 30 22:51:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D2F016A4D3 for ; Sat, 30 Oct 2004 22:51:06 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 0145443D54 for ; Sat, 30 Oct 2004 22:51:05 +0000 (GMT) (envelope-from Emanuel.Strobl@gmx.net) Received: (qmail 29993 invoked by uid 65534); 30 Oct 2004 22:51:03 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp011) with SMTP; 31 Oct 2004 00:51:03 +0200 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org Date: Sun, 31 Oct 2004 00:51:00 +0200 User-Agent: KMail/1.7 References: <200410290741.i9T7f8DW095035@pooker.samsco.org> <200410302346.18306.Emanuel.Strobl@gmx.net> <4184181A.303@freebsd.org> In-Reply-To: <4184181A.303@freebsd.org> X-OS: FreeBSD X-Birthday: 10/06/72 X-Address: Munich, 80686 X-Tel: +49 89 18947781 X-CelPhone: +49 173 9967781 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1776405.FJLrClHDXu"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200410310051.02937.Emanuel.Strobl@gmx.net> cc: re@freebsd.org cc: Scott Long cc: current@freebsd.org Subject: Re: 5.3-RELEASE TODO X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Oct 2004 22:51:06 -0000 --nextPart1776405.FJLrClHDXu Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Sonntag, 31. Oktober 2004 00:39 schrieb Scott Long: > Emanuel Strobl wrote: > > Am Freitag, 29. Oktober 2004 09:41 schrieb Scott Long: > >>This is an automated weekly mailing of the FreeBSD 5.3 open issues list. > >>The live version of this list is available at: > >> > >> http://www.FreeBSD.org/releases/5.3R/todo.html > >> > >>Automated mailing of this list will continue through the release of > >>FreeBSD 5.3 > >> > >> > >> FreeBSD 5.3 Open Issues [...] > > What about misc/72895, i386/73251 and misc/72896? The latter is not that > > critical but GEOM_GPT really has edges on i386 which aren't suitable for > > -stable! Removing GEOM_GPT from GENERIC would be one solution IMO, fixi= ng > > of course was even better, but I can't help. > > And then there's kern/71355 which has been closed without any > > improovement. The opposite: I can confirm that this also applies to the > > sil3114 chipset when the BIOS (of the PCI Card (Dawicontrol DC-154))) is > > enabled (so booting from it is possible) and two drives are set up as > > mirror! > > > > -Harry > > 72895 is indeed serious, but it doesn't prevent a normal install so long > and you specifically avoid the problem. Unfortunately there are no > patches attached to this PR, so it's hard for us to evaluate how hard it > would be to fix it. I probably should have landed on the TODO list a > long time ago, and I'll make sure it gets on the 5.3 TODO list. But > again it's not a show-stopper because it doesn't prevent a normal > install from succeeding. > > 73251 is strange. No one that I've seen can possibly imagine why ACPI > would affect GPT. But again, GPT is not the normal way to install and > boot an i386. While I know of a few Intel systems that have EFI and GPT > for i386, MBR partitioning still works. > > 72896 is another GPT one, and again GPT is just not the predominate way > to deal with i386. I'd really like to see these fixed for 5.4. > > So I don't want to discount your concern, but given the very small user > base that is concerned about GPT, it's hard to justify delaying the > release further for these bugs. Ok, it sounds sensible, but the please remove GEOM-GPT from the GENRIC i386= =20 kernel. Because, like you see, it doesn't make sense and prevents users fro= m=20 mysterious errors. If someone makes his custom GPT kernel he knows what he= =20 does but GEOM_GPT in GENERIC is no good idea (like I alreade posted on=20 =2Dcurrent) Thanks, =2DHarry P.S. I'm also specially interestend in the GPT/ACPI issue but regrettably I= 'm=20 no kernel hacker so I can't help much > > Scott > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --nextPart1776405.FJLrClHDXu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBhBrWBylq0S4AzzwRAuYDAJ4xKZJsToroWk2/9VuTk5dzJGwJRwCfVSOI 2VBzFkGIgxuCBPg5O8aSbOg= =aXCo -----END PGP SIGNATURE----- --nextPart1776405.FJLrClHDXu--