[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
On Mon, May 22, 2017 at 08:35:39AM -0400, Julio Merino wrote:
> On Sun, May 21, 2017 at 7:39 PM, Johnny C. Lam <jlam%netbsd.org@localhost> wrote:
> > On Sun, May 21, 2017 at 05:04:19PM -0500, Jason Bacon wrote:
> >> Is sysutils/sysupgrade still supported? It looks like the package hasn't
> >> been upgraded in a few years, although it's recommended here:
> >> https://www.netbsd.org/docs/guide/en/chap-upgrading.html
> > Yes, it should still work.
> Yup, it does work. I use it routinely.
> >> Trying to run this:
> >> sysupgrade auto 'ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-7.1/amd64'
> >> Ends in this:
> >> sysupgrade: E: Failed to fetch ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-7.1/amd64/binary/kernel/netbsd-AUTOUPDATE.gz
> > It looks like sysupgrade tried to automatically discover your kernel
> > config name, and determined it to be "AUTOUPDATE". Is that correct?
> > You can run "config -x | head -1" to see. You can explicitly set
> > the kernel to use as part of the auto-update with:
> > sysupgrade -o KERNEL=GENERIC auto <releasedir>
> I wonder what should sysupgrade do when it detects a custom kernel
> that is not available in the given repository. Fail as it does now?
> Ignore the kernel upgrade? Or maybe the user should be the one
> explicitly saying "UPDATE_KERNEL=no" or something similar when they
> have explicitly compiled their own kernel, because sysupgrade cannot
> deal with this.
I think just having better warning messages would be enough in this
situation. Replacing a custom kernel with a GENERIC kernel may leave a
system unbootable, which is undesirable. If sysupgrade detects a kernel
not found in the repository location, I'm fine with having it do that
check early on, and then stopping with a warning.
Johnny C. Lam
Main Index |
Thread Index |