| 1 |
On 06/30/2016 05:38 AM, Michał Górny wrote: |
| 2 |
> Hello, everyone. |
| 3 |
> |
| 4 |
> Back in 2011 I started a project called eclean-kernel. The idea was |
| 5 |
> pretty simple -- to have a tool that would clean the old kernels for |
| 6 |
> me since their install is not controlled by the package manager. This |
| 7 |
> little project of mine seems to have gained a lot of popularity. |
| 8 |
> |
| 9 |
> Sadly, over time a lot of people had trouble with it. Aside to minor |
| 10 |
> Python problems, eclean-kernel proved too simple to handle multitude of |
| 11 |
> user systems with varying /boot layouts. In fact, even I don't use it |
| 12 |
> on all of my systems since it doesn't handle them properly. |
| 13 |
> |
| 14 |
> After being buried in another set of bug reports, I'd like to |
| 15 |
> officially ask Gentoo developers and users for help. I think it's |
| 16 |
> impossible to solve most of the bugs reported so far in the current |
| 17 |
> program design. Therefore, I'd like to rewrite it in a more flexible |
| 18 |
> manner. |
| 19 |
> |
| 20 |
> For this reason, I would like to ask you to provide me with |
| 21 |
> different /boot layouts you may have, had or seen. Basically, the idea |
| 22 |
> is to collect as many different layouts as necessary, and use that to |
| 23 |
> design eclean-kernel in a way making it possible to easily configure it |
| 24 |
> to handle proper variant -- or even possibly make it capable of |
| 25 |
> autoconfiguration. |
| 26 |
> |
| 27 |
> So if you have some time, please reply to this thread with |
| 28 |
> a specific /boot layout that you think needs to be handled, with |
| 29 |
> as much helpful information as possible -- including possible |
| 30 |
> distinctive features and pitfalls. |
| 31 |
> |
| 32 |
> Thanks in advance. |
| 33 |
> |
| 34 |
I'm not sure if this is the info you're looking for, but I'll give it a |
| 35 |
shot: |
| 36 |
|
| 37 |
I have grub-static installed to /boot/. I like to organize my kernels |
| 38 |
with the filenames as linux-${version}-gentoo-${buildno}. So my first |
| 39 |
build of 4.5.0, for example, would be 'linux-4.5.0-gentoo-1'. It has all |
| 40 |
the info I need for reference should something go awry. |
| 41 |
|
| 42 |
I have three symlinks: current, last, backup |
| 43 |
|
| 44 |
I wrote scripts that will update those symlinks for me, which makes the |
| 45 |
process of kernel management pretty painless. Now that I'm thinking |
| 46 |
about it, it could be simple in my case to simply clean any kernel that |
| 47 |
wasn't linked to. |
| 48 |
|
| 49 |
My /boot/: |
| 50 |
|
| 51 |
grub |
| 52 |
lost+found |
| 53 |
backup -> linux-4.4.1-gentoo-2 |
| 54 |
boot |
| 55 |
current -> linux-4.4.6-gentoo-1 |
| 56 |
initrd |
| 57 |
last -> linux-4.4.1-gentoo-3 |
| 58 |
linux-4.4.1-gentoo-2 |
| 59 |
linux-4.4.1-gentoo-3 |
| 60 |
linux-4.4.6-gentoo-1 |
| 61 |
-- |
| 62 |
Daniel Campbell - Gentoo Developer |
| 63 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
| 64 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
Archives