On 13 December 2010 03:17, David C. Rankin
wrote:
> I guess what I don't know is whether simply copying the existing files
> in the
> manner set out below will screw up any hard-coded links to the old kernel file
> names. (like any links in the copied System.map26-dcr that still point to t
On 12/12/2010 02:51 AM, < wrote:>
> On 12 December 2010 11:39, David C. Rankin
> wrote:
>> On 12/11/2010 09:34 PM, David C. Rankin wrote:
>>> mkinitcpio -k 2.6.35-dcr \
>>> -c /etc/mkinitcpio.conf \
>>> -g /boot/kernel26-dcr.img
>>>
>>> mkinitcpio -k 2.6.35-dcr \
>>> -c /etc/mkinitcpio.conf \
>>>
On 12 December 2010 11:39, David C. Rankin
wrote:
> On 12/11/2010 09:34 PM, David C. Rankin wrote:
>> mkinitcpio -k 2.6.35-dcr \
>> -c /etc/mkinitcpio.conf \
>> -g /boot/kernel26-dcr.img
>>
>> mkinitcpio -k 2.6.35-dcr \
>> -c /etc/mkinitcpio.conf \
>> -g /boot/kernel26-dcr-fallback.img \
>> -S aut
On 12/11/2010 09:34 PM, David C. Rankin wrote:
> mkinitcpio -k 2.6.35-dcr \
> -c /etc/mkinitcpio.conf \
> -g /boot/kernel26-dcr.img
>
> mkinitcpio -k 2.6.35-dcr \
> -c /etc/mkinitcpio.conf \
> -g /boot/kernel26-dcr-fallback.img \
> -S autodetect
Of course that should be 2.6.36-dcr
--
David C. R
Guys,
I want to keep the current kernel while I upgrade to 2.6.36-2 and where
I
confused is how to use mkinitcpio to do this. What I think I can do to preserve
the current kernel as 2.6.36-dcr is:
(1) cp -a /lib/modules/2.6.36-ARCH /lib/modules/2.6.36-dcr
(2)
mkinitcpio -k 2.6.35-dcr \
5 matches
Mail list logo