Daily FreeBSD updates (was: Re: priority on rc script caused
panic)
Steve Bertrand
iaccounts at ibctech.ca
Tue Jul 20 11:06:49 PDT 2004
>
> >From: Giorgos Keramidas <keramida at freebsd.org>
> >To: pura life CR <puralifecr at hotmail.com>
> >CC: freebsd-questions at freebsd.org
> >Subject: Daily FreeBSD updates (was: Re: priority on rc script caused
> panic)
> >Date: Tue, 20 Jul 2004 10:57:24 +0300
> >
> >On 2004-07-19 10:58, pura life CR <puralifecr at hotmail.com> wrote:
> > >Giorgos Keramidas <keramida at freebsd.org> wrote:
> > >> I regularly (almost daily) upgrade my CURRENT installation and
> the
> > >> set of commands I use when the single user shell fires up is:
> > >>
> > >> adjkerntz -i # allow system time updates to work
> > >> swapon -a # enable all swap partitions
> > >> fsck -p # check any filesystems that need it
> > >> mount -u / # remount root fs as read-write
> > >> mount /usr # mount /usr as read-write
> > >>
> > >> cd /usr/src # upgrade sequence
> > >> make installworld # - // -
> > >> mergemaster # - // -
> > >
> > > This should not be done.
> > >
> > > You dont really need to upgrade daily, you are just overloading
> freebsd
> > > cvsup servers.
> >
> >That's not true...
> >
> >I'm running FreeBSD 5.2-CURRENT. Keeping a local CVS mirror which is
> >updated once a day and test build/run on my machine is the least I
> can
> >do to help in testing the -CURRENT branch. The mirror I use is the
> one
> >that is closest to me (cvsup2.gr.freebsd.org).
>
> [snip]
>
> My comment is still applicable. If you just run a cvs mirror,
> just fetch the source code. You dont need to test to know whether if
> compiles or not. I think noone really helps to freebsd by compiling
> the source code every day looking for errors.
Maybe I'm way off here because I do not do any such testing as Giorgos
suggests, but how are the developers supposed to supply patches for
problems if -CURRENT builds are in fact not built, and build-errors not
found?
I would think that it would be easier to mirror the tree, and build
daily/weekly etc to find build errors than it would be to review the
source code line-for-line to find the bugs.
> It is better to test and
> contribute code.
How do you suggest testing without building? I believe that Giorgos is
suggesting that *is* what he is doing...building, locating bugs, fixing
(contributing/committing code).
Could someone with more experience clarify this? This is quite a confusing
thread.
Steve
>
>
> _________________________________________________________________
>
> MSN Amor [1]Busca tu ½ naranja
>
> References
>
> 1. http://g.msn.com/8HMBES/2752??PS=47575
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
>
More information about the freebsd-questions
mailing list