Description of problem:   
When init isn't a found, the following message is produced: 
kernel panic: No init found.  Try passing init = option to kernel. 
 
In most cases, passing the 'init=' option to the kernel won't fix 
the problem, because its not just init missing, its the whole disk. 
I teach RHCEs for Red Hat and notice even experienced users can 
become confused by this message. 
 
How reproducible:   
Always   
   
Steps to Reproduce:   
1.Have a situation where the kernel cannot find init. 
     
Actual results:   
The user is asked to use the 'init=' option. It would be useful to 
suggest they check the bootloader and filesystem table as well, as 
problems here are often the source of this problem. 
   
Expected results:   
Something that indicated other likely sources of the problem. 
 
How does the following sound: 
 
kernel panic: Couldn't find init on the specified device. Try 
checking: 
* Bootloader configuration refers to the correct device. 
* The filesystem table (/etc/fstab) is correct 
* Filesystem labelling, if used, is correct 
* /sbin/init (or the file specified with 'init=' option) exists on 
the correct disk. 
 
Or maybe something better. Discuss :^).