| 1 |
On Thu, 30 Jun 2016 14:38:26 +0200 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
> So if you have some time, please reply to this thread with |
| 4 |
> a specific /boot layout that you think needs to be handled, with |
| 5 |
> as much helpful information as possible -- including possible |
| 6 |
> distinctive features and pitfalls. |
| 7 |
> |
| 8 |
|
| 9 |
All of our systems have this: |
| 10 |
/boot/${KV}/{vmlinuz,initramfs,System.map,perf,config}-${KV} |
| 11 |
|
| 12 |
With these symlinks |
| 13 |
/boot/vmlinuz -> ${KV}/vmlinuz-${KV} |
| 14 |
/boot/initramfs -> ${KV}/initramfs-${KV} |
| 15 |
/boot/config -> ${KV}/config-${KV} |
| 16 |
/boot/System.map -> ${KV}/System.map-${KV} |
| 17 |
|
| 18 |
Some systems also have: |
| 19 |
/boot/${KV}/vmlinux-${KV} |
| 20 |
|
| 21 |
/boot/vmlinux -> ${KV}/vmlinux-${KV} |
| 22 |
|
| 23 |
When updating to a new kernel, we generally unpack a tarball |
| 24 |
containing the new kernel to /boot and update the symlinks to point to |
| 25 |
the new versions. All files related to a kernel are in that kernel's |
| 26 |
directory, which makes cleanup somewhat easier. |
| 27 |
|
| 28 |
The values of KV look like one of these: |
| 29 |
4.4.14-vanilla-base-1 |
| 30 |
4.4.14-gentoo-r1-base-1 |
| 31 |
4.7.0-rc5-vanilla-base-1 |
| 32 |
4.7.0-rc5-vanilla-base-1+ |
| 33 |
4.7.0-rc5-vanilla-base-1-00254-g1a0a02d |
| 34 |
|
| 35 |
Mostly, it's a version, sources version, configuration type and |
| 36 |
version. These are generated via setting CONFIG_LOCALVERSION, and |
| 37 |
whatever else gets spit out by the build system. |
Archives