Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 17 Nov 2007 17:05:20 +0100
From:      Jan Henrik Sylvester <me@janh.de>
To:        Colin Percival <cperciva@freebsd.org>
Cc:        stable-list freebsd <freebsd-stable@freebsd.org>
Subject:   Re: freebsd-update 6.2-R -> 6.3-B1 rollback failed
Message-ID:  <473F1140.9040705@janh.de>
In-Reply-To: <473F0939.9050800@freebsd.org>
References:  <473B5D10.1070109@janh.de> <473BD54F.9050808@freebsd.org> <473C1FD1.70001@janh.de> <473DA6B5.10107@freebsd.org> <473EF438.5090004@janh.de> <473F0939.9050800@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Colin Percival wrote:
> Depending on the UpdateIfUnmodified option in freebsd-update.conf, it will
> either update files to "clean" new versions or print a warning message and
> not touch them.
> 
> There's also an IgnorePaths directive which you can use to tell FreeBSD
> Update not to touch some files (even if they haven't been modified locally).
> 
> FreeBSD Update will never produce mangled files as a result of applying a
> bsdiff patch to the wrong file -- it checks file hashes before and after
> applying patches and gracefully falls back to downloading complete files
> if it can't generate a file via patching.

If freebsd-update allowed an 'upgrade' to the version already installed, 
one could (mis)use it as a tool to repair a 'broken' system... (probably 
a naive idea.)

Jan Henrik



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