Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jul 2004 10:57:24 +0300
From:      Giorgos Keramidas <keramida@freebsd.org>
To:        pura life CR <puralifecr@hotmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Daily FreeBSD updates (was: Re: priority on rc script caused panic)
Message-ID:  <20040720075724.GA85244@orion.daedalusnetworks.priv>
In-Reply-To: <BAY22-F39cj4PPRE3Iv00054336@hotmail.com>
References:  <BAY22-F39cj4PPRE3Iv00054336@hotmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2004-07-19 10:58, pura life CR <puralifecr@hotmail.com> wrote:
>Giorgos Keramidas <keramida@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).

I don't think that this can be called "overloading" the CVSup servers.

If you *do* think that it's an overkill, perhaps you should explain why
you think this is so and why the tests I'm privately doing of -CURRENT
are so completely and utterly worthless that they're considered
overkill, overload or anything else similarly redundant :-P

> Also, why to make all the source tree if you just get few modifications
> per day? It would be wise to know what part or the tree was updated and
> just compile it or let the whole compilation for later.

Because this is the recommended way of building everything to see how it
fits together.  The "make buildworld" target is what the end-user will
see when they try to build FreeBSD 5.X one day.  If this is broken, a
full build is going to catch it very quickly.

There are times -- i.e. when I'm preparing patches to a particular part
of the source tree -- that I build only parts using the Makefiles of the
proper SUBDIRs.  These are special purpose builds though and I know when
or why I'm doing a partial build.

> If you want to see your machine working at 100% cpu, learn prolog.

Spare me the irony, please.  I don't need it.  The list doesn't need it.

I was trying to contribute to the thread in a positive manner, showing
an example of commands that can be used to bring a FreeBSD system from
single user mode up to the point where all the disks are mounted and
real work can be done.  If you have nothing positive to add to the
discussion or you haven't spotted something wrong in what I wrote and
feel like correcting me, I'd be glad if you didn't make bad-tempered
jokes about it all.

Regards,

Giorgos



PS:     I would appreciate it very much if you posted in plain text and
        not in the HTML-only format that Hotmail defaults to.  Thanks...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040720075724.GA85244>