Edit - Unix & Linux Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Thanks for clarifying the doubt. But what are the initrd and kernel entries? The boot will happen from the same place always right? So, how can the different versions of initd or kernel make sure that the system can boot properly in case of any failure?

Ramesh
– Ramesh

2013-10-16 16:05:38 +00:00
Commented Oct 16, 2013 at 16:05
1

+1 IMO it's a good idea to just leave the old entries; less hassle, greater saftey, and the updater will remove them after a while (I think on fedora it keeps the last three). They're harmless and they may be useful, e.g., in determining if a problem is caused by a kernel update. Stuff like that may not be noticeable right away, so it is hard to say definitively, "everything with the system is fine...".

goldilocks
– goldilocks

2013-10-16 16:32:42 +00:00
Commented Oct 16, 2013 at 16:32
3

@Ramesh: There are several reasons you might boot an alternate kernel: 1. The kernel file you normally boot got corrupted. 2. You have some multi-CPU problem, so you boot the uniprocessor (UP) kernel. 3. A new kernel you got via yum update contains a new bug, so you have to roll back to the old kernel.

Warren Young
– Warren Young

2013-10-16 16:37:18 +00:00
Commented Oct 16, 2013 at 16:37
It's hard to explain briefly. You may want to check out the Wikipedia entry for GRUB to understand what exactly is happening. In a nutshell, "the boot" is happening in "different places" with those different places being the different vmlinuz, initrd, etc. GRUB locates these files and loads them accordingly. Windows has a similar process.

tamarintech
– tamarintech

2013-10-16 21:08:23 +00:00
Commented Oct 16, 2013 at 21:08

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »