Bug 137224 - option to remove old kernel upon successful reboot
Summary: option to remove old kernel upon successful reboot
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: up2date
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bret McMillan
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-26 19:38 UTC by Florian Effenberger
Modified: 2007-11-30 22:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-29 15:06:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Florian Effenberger 2004-10-26 19:38:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3)
Gecko/20040913 Firefox/0.10.1

Description of problem:
I would like to see an option to remove old kernel upon successful
reboot. Otherwise, I always have to remove old kernels manually.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. xxxxxxxx
2.
3.
    

Additional info:

Comment 1 Dave Jones 2004-10-26 22:38:33 UTC
this would be better done in up2date / yum.



Comment 2 Matthew Miller 2006-07-10 21:18:55 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!


Comment 3 John Thacker 2006-10-29 15:06:36 UTC
Closing per lack of response to previous comment.  If this still occurs on FC3
or FC4 and is a security issue, please assign to Fedora Legacy and the
appropriate version.  The bug could also be filed against RHEL if it is relevant
there.

up2date has been replaced by pirut and pup in FC5 and FC6, the still fully
supported versions of Fedora Core, so this bug will not be fixed unless it is a
security issue.


Note You need to log in before you can comment on or make changes to this bug.