Date: Tue, 10 Feb 2015 10:29:50 +0100 From: Baptiste Daroussin <bapt@freebsd.org> To: David Chisnall <theraven@FreeBSD.org> Cc: svn-src-projects@freebsd.org, src-committers@freebsd.org, John Baldwin <jhb@FreeBSD.org> Subject: Re: svn commit: r278447 - projects/release-pkg/release/packages/kernel Message-ID: <20150210092950.GQ29891@ivaldir.etoilebsd.net> In-Reply-To: <71EFE329-6A63-4A2A-9083-BEED15991F4C@FreeBSD.org> References: <201502091025.t19APxwK057568@svn.freebsd.org> <2379227.vPTf1TCfaA@ralph.baldwin.cx> <20150209161830.GH29891@ivaldir.etoilebsd.net> <54D8E5CD.8050304@FreeBSD.org> <71EFE329-6A63-4A2A-9083-BEED15991F4C@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--fu8LepSeDvpxVgv6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 10, 2015 at 09:19:59AM +0000, David Chisnall wrote: > 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. >=20 > Would it work to have each kernel install as a unique name (e.g. KERNEL.G= ENERIC-11.1r6) and a symlink that's updated to point to the most recently i= nstalled one? I can think of a few other ports where you want to have mult= iple 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). >=20 > The only issue that I can see with this approach is that you'd need to ma= ke 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 defaul= t for anything where old and new versions don't conflict with each other). = =20 Yes it will work Best regards, Bapt --fu8LepSeDvpxVgv6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlTZz44ACgkQ8kTtMUmk6EzqdwCfY1LJEuMdSCzqHemn9L+dYxBJ NFYAoLQbbWiLbvrna/CkhV+EUKUAOAm8 =EUci -----END PGP SIGNATURE----- --fu8LepSeDvpxVgv6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150210092950.GQ29891>