Date: Wed, 05 Apr 2000 16:00:43 -0500 From: "Jeffrey J. Mountin" <jeff-ml@mountin.net> To: Brooks Davis <brooks@one-eyed-alien.net>, J McKitrick <jcm@freebsd-uk.eu.org> Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: ppp problems under 4.0-S Message-ID: <4.3.2.20000405153609.00b2c100@207.227.119.2> In-Reply-To: <20000405102339.A3267@orion.ac.hmc.edu> References: <20000405154542.C13658@dogma.freebsd-uk.eu.org> <38EAACEF.C573F72@ucdavis.edu> <38EA7621.48F887A5@ucdavis.edu> <20000405034833.A11271@dogma.freebsd-uk.eu.org> <38EAACEF.C573F72@ucdavis.edu> <20000405041046.B11271@dogma.freebsd-uk.eu.org> <4.3.2.20000405054845.00b83c20@207.227.119.2> <20000405154542.C13658@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:23 AM 4/5/00 -0700, Brooks Davis wrote: >On Wed, Apr 05, 2000 at 03:45:42PM +0100, J McKitrick wrote: > > On Wed, Apr 05, 2000 at 06:10:44AM -0500, Jeffrey J. Mountin wrote: > > > Sometimes it is worth while to run *before* building. Recent > additions to > > > make.conf are a good, recent example. Along the same line is updating > > > files in etc via mm and not rebuilding the rest of the system. Recent > > > changes in pccard.conf.sample as an example. Can they make a > difference, yes. > > > > What do you mean here? What changed in pccard.conf? > >In current, pccard.conf.sample was copied to /etc/defaults/pccard.conf. >A new include directive was added to pccardd so >/etc/defaults/pccard.conf reads /etc/pccard.conf for local overrides >like with rc.conf and defaults/rc.conf. Was referring to the re-ordering. The changes you mention have not been MFC'd (yet). A better example would have been the re-ordering in rc.network for entropy reasons and later sshd's keygen. At the time there were so many changes requiring a rebuild. If, however, they was the only changes, a simple merge would work just fine. When NO_X and NO_FORTRAN were added to make.conf I merged before the build. Not something done often, but I do keep track of changes. Waiting for NO_UUCP to MFC. 8-) My point is that you don't have to rebuild the entire system, should keep track of commits, and if your problem is more than 2 hours old, update source and try again. Saying 2 hours is a bit facetious. However, it is possible to only receive part of a large commit. Track your branch and *all* commits. Real simple to search and check for updates or fixes and the mail (usually) comes *before* you see the source on the servers. Brian is always busy working on PP and if you watch commits to -current, then your fix may just be an MFC away. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.20000405153609.00b2c100>