That makes sense.
Ok, I think it is better to keep the older kernel because I do need some stable stuff.On Sat, Sep 24, 2016 at 10:34 PM, Gavin Flower <GavinFlower@xxxxxxxxxxxxxxxxx> wrote:
On 25/09/16 14:31, Adam Williamson wrote:
On Sat, 2016-09-24 at 18:55 -0500, Bowen Wang wrote:
Thanks! I am currently working on learning xkb. I will post my way if itThis is normal, but don't worry, it won't keep growing forever :) The
can work.
I know the Rawhide is not very stable, but it provides the cutting-edge
features and software.
There is another issue I just found:
I download the image of Rawhide 20160923 version, then I upgraded my system
today. When restarted the laptop again, there seems to be another grub
entry. How can I delete the old one? There are 3 entries in my grub list
totally, the last is a rescue mode entry.
Can you tell me how to delete the old one?
default Fedora config is to keep three kernels installed at once. This
is a safety measure to ensure that if you update to a kernel that
doesn't work, you can still boot with one of the older kernels. Once
you have three kernels installed, you'll find Fedora will start
removing the oldest kernel when installing a new kernel.
If you really just want to have one kernel installed at a time you can
configure this, I think, but I'd have to look up how. I really
recommend sticking with the default, though, it's a helpful safety
measure.
One time about 12 years ago I had a kernel update that had a bug which prevented me connecting to the modem, I was able to reboot to the previous kernel & continue as before. I raised a bug report, & the next kernel I downloaded had that bug fixed.
So Yes, it is good to keep a few previous kernels around just in case ...
Cheers,
Gavin
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@lists.fedoraproject.org
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx