1 |
Just to give kudos, I would not be able to keep my system tidy without |
2 |
eclean-kernel. It takes care of lots of stuff portage does not. |
3 |
|
4 |
On Fri, Jul 1, 2016 at 10:58 AM, Guilherme Amadio <amadio@g.o> wrote: |
5 |
|
6 |
> On Thu, Jun 30, 2016 at 02:38:26PM +0200, Michał Górny wrote: |
7 |
> > So if you have some time, please reply to this thread with |
8 |
> > a specific /boot layout that you think needs to be handled, with |
9 |
> > as much helpful information as possible -- including possible |
10 |
> > distinctive features and pitfalls. |
11 |
> |
12 |
> Looks like not too many people are booting kernels like me, so |
13 |
> I'm going to add my crude setup to the pile :) |
14 |
> |
15 |
> I compile most stuff into the kernel (at least enough so I don't |
16 |
> need to use an initrd/initramfs to mount / or /usr). I do not use a boot |
17 |
> loader either, I use CONFIG_EFI_STUB=y and compile in the command |
18 |
> line arguments to avoid trouble. Then, I use efibootmgr to boot the |
19 |
> kernel at /boot/EFI/Gentoo/bootx64.efi |
20 |
> |
21 |
> I usually keep several kernels in the same directory with a version |
22 |
> suffix (e.g. bootx64-4.6.2.efi, etc) and overwrite the bootx64.efi |
23 |
> file with whatever kernel I want to boot with cp bootx64{-4.x.x,}.efi |
24 |
> |
25 |
> I keep a few older kernels around in case I screw up the configuration |
26 |
> of a new one (usually video drivers), but for the most part, that's it. |
27 |
> |
28 |
> My compiled kernel command line is also pretty simple: |
29 |
> |
30 |
> quiet console=tty1 root=/dev/sda4 init=/usr/lib/systemd/systemd |
31 |
> |
32 |
> I never really though about writing scripts to manage this, since it's |
33 |
> quite a simple setup, but having tools to manage it would be nice. |
34 |
> |
35 |
> Just think about supporting a simple EFI/UEFI setup, I would say, in |
36 |
> addition to the more common setups using a boot loader. |
37 |
> |
38 |
> Cheers, |
39 |
> —Guilherme |
40 |
> |
41 |
> |
42 |
> |