From owner-freebsd-stable  Sun Aug  6  4:42: 3 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from osiris.ipform.ru (osiris.ipform.ru [212.158.165.98])
	by hub.freebsd.org (Postfix) with ESMTP id DFC5637BB51
	for <freebsd-stable@freebsd.org>; Sun,  6 Aug 2000 04:41:57 -0700 (PDT)
	(envelope-from matrix@ipform.ru)
Received: from wp2 (wp2 [192.168.0.12])
	by osiris.ipform.ru (8.9.3/8.9.3) with SMTP id PAA00358
	for <freebsd-stable@freebsd.org>; Sun, 6 Aug 2000 15:42:18 +0400 (MSD)
	(envelope-from matrix@ipform.ru)
Message-ID: <002801bfff9a$ce73b840$0c00a8c0@ipform.ru>
From: "Artem Koutchine" <matrix@ipform.ru>
To: <freebsd-stable@freebsd.org>
Subject: Safe upgrading via cvsup
Date: Sun, 6 Aug 2000 15:38:12 +0400
Organization: IP Form
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi!

Here is what i run into when doing the last cvsup
for 4.1-stable.

I ususally do
cvsup upgrade-stable
make buildworld
make buildkernel KERNEL=THIS
make installkernel
reboot
make installworld
mergemaster

That works 100% of the time.

I have a lot of machines in the office and users upgrade them the same way
and one co-location mchines pretty far away, which is also upgraded this
way, but
remotely. This always worked.

But today i figureed that after reboot the firewall utility does not work
anymore and
to make it work i need to to installworld, but on remote machines i would
not be
able to to so, because firewall is closed already. Thanks God i always to
upgrade
localy and it if workd upgrade the remote one.

To avoid the problem i would need to recompile the remote kernel with option
where firewall is open by default or maybe change the order of updage (e.g.
installkernel, installworld,
reboot).

So, the issue is NOTIFICATION OF CHANGES. /usr/src/UPGRADE, if you look at
it, says nothing about
this very imprtant change. I think developers whoudl decument all changes
somewhere, so i could
look through them before upgrading.

The questions are:
1) Can i do installkernel, installworld, reboot exactly in this order? I
think it could failed because
the old kernel is still workding and some of the program will fail to work
with the old kernel. Is there
way out?

2) How safe is it to upgrade a remote machine via cvsup remotely?

Thanks,
Artem





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message