Date: Tue, 10 Feb 2015 09:19:59 +0000 From: David Chisnall <theraven@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: svn-src-projects@freebsd.org, Baptiste Daroussin <bapt@freebsd.org>, src-committers@freebsd.org Subject: Re: svn commit: r278447 - projects/release-pkg/release/packages/kernel Message-ID: <71EFE329-6A63-4A2A-9083-BEED15991F4C@FreeBSD.org> In-Reply-To: <54D8E5CD.8050304@FreeBSD.org> References: <201502091025.t19APxwK057568@svn.freebsd.org> <2379227.vPTf1TCfaA@ralph.baldwin.cx> <20150209161830.GH29891@ivaldir.etoilebsd.net> <54D8E5CD.8050304@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9 Feb 2015, at 16:52, John Baldwin <jhb@FreeBSD.org> wrote: >=20 > Hmm, it might be nice to choose it at runtime. Maybe I want to use > GENERIC as the main kernel so I want it at /boot/kernel, maybe I wnat = to > install the "official" FreeBSD GENERIC kernel as /boot/kernel.GENERIC = so > I'd like to be able to override the "prefix" as it were. Similarly, I > might want to install a test kernel package to /boot/test so I can use > it with nextboot without changing the machine's default kernel. In = the > case of the kernel all the bits live in one directory, so if you allow > the directory to be fungible during install that should be doable. I > can't think of other things besides the kernel that have this sort of > behavior. Would it work to have each kernel install as a unique name (e.g. = KERNEL.GENERIC-11.1r6) and a symlink that's updated to point to the most = recently installed one? I can think of a few other ports where you want = to have multiple versions installed with a suffix like this and would = ideally like the same behaviour (e.g. the llvm ports, where you might = need llvm33 installed for some dependency and llvm35 installed because = it's the latest, but would quite like symlinks from clang -> clang35 and = so on). The only issue that I can see with this approach is that you'd need to = make sure that you eventually removed old kernels if you didn't want = /boot to become full and it's not clear what the trigger should be = (remove the old one after successful boot of the new one? Perhaps we'd = want the ability to clear the old one's installed-by-user flag so that a = future pkg autoremove would delete it if it's a normal upgrade - this = might be a sensible default for anything where old and new versions = don't conflict with each other). =20 David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?71EFE329-6A63-4A2A-9083-BEED15991F4C>