Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Dec 2011 11:00:53 -0500
From:      Robert Huff <roberthuff@rcn.com>
To:        tundra@tundraware.com
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Perl Upgrade And Mailscanner Woes
Message-ID:  <20210.693.113141.63472@jerusalem.litteratus.org>
In-Reply-To: <4EF1FD94.10805@tundraware.com>
References:  <4EF1F44A.5000303@tundraware.com> <4EF1FB24.10005@infracaninophile.co.uk> <4EF1FD94.10805@tundraware.com>

next in thread | previous in thread | raw e-mail | index | archive | help

Tim Daneliuk writes:

>  > Are you sure you are using perl-after-upgrade correctly?  You do
>  > understand that just running:
>  >
>  >     # perl-after-upgrade
>  >
>  > doesn't actually modify anything on disk: instead it shows you what
>  > needs to be done.  To actually effect the change you need to run:
>  >
>  >     # perl-after-upgrade -f
>  
>  
>  Aha!  And the lights go on ...  Nevermind.

	No, not "nevermind".  While this seems like "upgrading for
dummies", there are enough of them out there <waves> this _really_
needs to go in the upgrade message.


			Robert Huff




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