Removing Old Kernels

[Karl F. Larsen]

Werner Schram wrote:
> Karl F. Larsen wrote:
>> Leonard Chatagnier wrote:
>>   
>>> Bret Busby wrote:
>>>     
>>>> On Fri, 11 Dec 2009, Tom H wrote:
>>>>
>>>>    
>>>>       
>>>>> Date: Fri, 11 Dec 2009 15:09:14 +0100
>>>>> From: Tom H<tomh0665 at gmail.com>
>>>>> Reply-To: "Ubuntu user technical support, not for general discussions"
>>>>>      <ubuntu-users at lists.ubuntu.com>
>>>>> To: ubuntu-users at lists.ubuntu.com
>>>>> Subject: Re: Removing Old Kernels
>>>>>
>>>>>      
>>>>>         
>>>>>> There was a feature in ubuntu some time in the earlier releases where in
>>>>>> there used to be only a specific copies of kernels maintained. The older
>>>>>> one's would get deleted once the updates were applied. Not sure if its
>>>>>> there in the current versions of ubuntu 9.10
>>>>>>        
>>>>>>           
>>>>> You can add a "howmany=X" line to menu.lst to limit the number of
>>>>> kernels that grub1's update-grub adds to menu.lst.
>>>>>
>>>>> Based on
>>>>> http://www.mail-archive.com/grub-devel@gnu.org/msg13049.html
>>>>> it is unlikely to be added by the grub developers. It seems to have
>>>>> been a Debian/Ubuntu customization. I do not have a grub1 install to
>>>>> look at its update-grub script but I remember it to consist of more
>>>>> than the grub2 update-grub script, which is a one-line grub-mkconfig
>>>>> invocation.
>>>>>
>>>>>
>>>>>      
>>>>>         
>>>> Please advse of the path for menu.lst .
>>>>
>>>> Thank you in anticipation.
>>>>    
>>>>       
>>> Unless I misunderstand you request, menu.lst is in folder /boot/grub when using
>>>
>>> grub1.  For grub2, menu.lst is replaced by grub.cfg in the same folder.
>>>
>>>
>>>     
>> 	That is not the end of the story. How do you change grub.cfg? 
>> Menu.lst you just edited with gedit, simple. Editing grub.cfg 
>> is NOT SIMPLE!
>>
>>   
> If you type gedit /boot/grub.cfg, and read the first 5 lines, you see 
> that they clearly state that you shouldn't edit this file, but edit 
> /etc/default/grub and use grub-mkconfig. Grub-mkconfig automatically 
> detects available kernels and initrd's, and creates your config 
> accordingly. Which is actually a lot easier than grub1.
> 
> Werner
> 
> 
	Exactly. I did that once with sudo grubmkconfig and it ran 
but didn't allow me to make any changes! It just ran through 
grub. I need to know how to make windows the first thing to 
boot. Easy on menu.lst but can't see a way with grub-mkconfig.

73 Karl


-- 

	Karl F. Larsen, AKA K5DI
	Linux User
	#450462   http://counter.li.org.
         Key ID = 3951B48D