1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 09.01.2012 01:34, Dale wrote: |
5 |
> Howdy, |
6 |
> |
7 |
> I'm about to upgrade my kernel. Do I have to update the init |
8 |
> thingy too or should it work without updating with each kernel |
9 |
> upgrade? I would be going from a 3.1.5 to a 3.2.0-r1. |
10 |
> |
11 |
> While I am at it, I version my bzImages. Can I version my init |
12 |
> thinys too? Have one for each version of kernel in other words? |
13 |
> That would be assuming I need to have it updated as asked above. |
14 |
> |
15 |
> Thanks. |
16 |
> |
17 |
> Dale |
18 |
> |
19 |
> :-) :-) |
20 |
> |
21 |
> |
22 |
Hi Dale, |
23 |
|
24 |
You can use your old "init thingy" if you don't need any modules |
25 |
inside it. The other stuff normally doesn't change. |
26 |
Since most setups use modules, you could experience troubles... |
27 |
|
28 |
The other way would be - as you already proposed - to create an "init |
29 |
thingy" per kernel, eg initramfs-3.2.0-r1. |
30 |
If you use grub2 the grub2-mkconfig script searches for these |
31 |
(matching the name for your kernel image) and normally it works out of |
32 |
the box. |
33 |
FOr grub legacy (and lilo, i assume) you would need to make matching |
34 |
entries manually. |
35 |
|
36 |
With kind regards, |
37 |
|
38 |
Hinnerk |
39 |
-----BEGIN PGP SIGNATURE----- |
40 |
Version: GnuPG v2.0.18 (GNU/Linux) |
41 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
42 |
|
43 |
iQEcBAEBAgAGBQJPCj4LAAoJEJwwOFaNFkYcA80IAIuYdR8nBiEKdZnUj5TyT/Oz |
44 |
/oYdw7Kn8bwqsMvBMF8WhEbQlwzy/W/7QaMhU1MOUjFHHHkcFkNe6240gfkbhEEg |
45 |
J52xj2vsUeT9YjgWEcrhmbFjZi3QNa9NxqVqpEXTFotfKcrX5ym0wdWQ7sW5VhHZ |
46 |
a4TNtoTu/Kt0pCjyi9ex9j3s1iJKxGG3vwJPrPwT3cc7+1adOE53rgpwjl9avklD |
47 |
IL72XmhDrii/C3Im78TqrqBZ1fjjRgEmzwGmdBp2Hduk7w5iEW5dXh4nGq/4+8Xi |
48 |
C1/o+y8acC1+IXRJBbAGMSoVdkmU9difo33CtnjMyjwPjHpkq16TWGj0w12eD8s= |
49 |
=lP1r |
50 |
-----END PGP SIGNATURE----- |