From owner-freebsd-bugs Mon Jul 1 4:17: 6 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BDB537B400 for ; Mon, 1 Jul 2002 04:17:03 -0700 (PDT) Received: from south.nanolink.com (south.nanolink.com [217.75.134.10]) by mx1.FreeBSD.org (Postfix) with SMTP id F37BE43E31 for ; Mon, 1 Jul 2002 04:17:00 -0700 (PDT) (envelope-from roam@ringlet.net) Received: (qmail 72204 invoked by uid 85); 1 Jul 2002 11:29:10 -0000 Received: from unknown (HELO straylight.ringlet.net) (212.116.140.125) by south.nanolink.com with SMTP; 1 Jul 2002 11:29:05 -0000 Received: (qmail 6323 invoked by uid 1000); 1 Jul 2002 11:15:24 -0000 Date: Mon, 1 Jul 2002 14:15:24 +0300 From: Peter Pentchev To: Dan Lukes Cc: Brooks Davis , Andy Farkas , freebsd-bugs@FreeBSD.ORG Subject: Re: bin/39868: cleaning sbin/dump code from warnings Message-ID: <20020701111524.GA376@straylight.oblivion.bg> Mail-Followup-To: Dan Lukes , Brooks Davis , Andy Farkas , freebsd-bugs@FreeBSD.ORG References: <200206270110.g5R1A4QO001789@freefall.freebsd.org> <20020628100307.A26852@Odin.AC.HMC.Edu> <3D1CE029.4020106@obluda.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline In-Reply-To: <3D1CE029.4020106@obluda.cz> User-Agent: Mutt/1.5.1i X-Virus-Scanned: by Nik's Monitoring Daemon (AMaViS perl-11d ) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 29, 2002 at 12:16:09AM +0200, Dan Lukes wrote: > Brooks Davis wrote: >=20 >=20 > >We don't commit directly to stable without significant cause and in > >most cases fixing warnings in programs that work isn't. Certaintly I > >would encourage anyone doing warnings fixes in current to merge these > >patches as appropriate to both current and stable. For that matter, > >maybe Dan want's go really get his hands dirty and try current once DP2 > >comes out in July. It's shaping up pretty nicly IMO. >=20 > I have dual-CPU machine. I'm not ready for current until SMPng is=20 > working, but I don't know current status of current about it ... >=20 > My machine didn't boot with 5.0-current (but I tried it about 9=20 > month ago) >=20 > I can't maintain separate developper-only machine which isn't usable=20 > for regular work also. There is always the possibility of building an uniprocessor kernel for running -CURRENT; granted, you might lose some performance (about 50% of it :), but you will be able to track -CURRENT nonetheless. Moreover, most of the time SMPng is quite stable, barring short intervals of at most a couple of days right after a large-scale change; those do not happen very often, though. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 because I didn't think of a good beginning of it. --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9IDnM7Ri2jRYZRVMRAiKbAJ4k6wzTm6hsA010DjFLQ8okpc02SQCeJ/Df 5qCGrrnBugBZYEAyEC1LQwo= =0ALK -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message