[NBLUG/talk] Need help with booting Linux system

[Todd Cary]

Scott -

Again thank you for the assistance, and my delays in getting back 
is due to being "in the field" frequently.

I can afford to have the server down for a period of time since 
it is mainly for FTP, testing PHP and displaying images for clients.

Do I include the EL in the symbolic link as in
vmlinuz -> vmlinuz-2.6.9-100.EL

Todd

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to 
this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/hdc
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.9-100.EL)
     root (hd0,0)
     kernel /vmlinuz-2.6.9-100.EL ro 
root=/dev/VolGroup00/LogVol00 rhgb quiet
     initrd /initrd-2.6.9-100.EL.img

Todd

On 3/17/2011 12:01 AM, Scott Doty wrote:
> On 03/16/2011 04:58 PM, Todd Cary wrote:
>> Scott -
>>
>> Yup...I was not paying attention to the link syntax - I do 
>> know better :-).
>>
>> On the advice of others in the Centos forum, I did the following:
>>
>> rpm -Uvh --replacepkgs --replacefiles 
>> kernel-2.6.9-100.EL.i686.rpm 
>> redhat-logos-1.1.26-1.centos4.4.noarch.rpm grub-0.95-3.8.i386.rpm
>>
>> So now I have the following in the /boot/ directory:
>>
>> drwxr-xr-x   5 root root     9216 Mar  9 10:31 .
>> drwxr-xr-x  24 root root     4096 Jan 24 08:34 ..
>> -rw-r--r--   1 root root    51676 Feb 17 22:41 
>> config-2.6.9-100.EL
>> drwxr-xr-x   2 root root     1024 Mar  9 10:31 grub
>> -rw-r--r--   1 root root   444812 May  5  2007 
>> grub-0.95-3.8.i386.rpm
>> -rw-r--r--   1 root root  1343054 Mar  9 10:29
>> initrd-2.6.9-100.EL.img
>> -rw-r--r--   1 root root 13409764 Feb 18 06:25
>> kernel-2.6.9-100.EL.i686.rpm
>> drwx------   2 root root    12288 Jan 12  2007 lost+found
>> -rw-r--r--   1 root root     9371 Aug 12  2006 message
>> -rw-r--r--   1 root root     9371 Aug 12  2006 message.ja
>> -rw-r--r--   1 root root  7919724 Aug 13  2006
>> redhat-logos-1.1.26-1.centos4.4.noarch.rpm
>> -rw-r--r--   1 root root    67797 Feb 17 22:41
>> symvers-2.6.9-100.EL.gz
>> -rw-r--r--   1 root root   770652 Feb 17 22:41
>> System.map-2.6.9-100.EL
>> drwx------   2 root root     9216 Mar  9 10:03 .Trash-root
>> -rw-r--r--   1 root root  1538264 Feb 17 22:41 
>> vmlinuz-2.6.9-100.EL
>>
>> I am not sure of what to have the symbolic link for vmlinuz 
>> point to; vmlinuz-2.6.9-100???
>>
>
> That looks correct.  but check grub.conf to make sure the 
> kernel file you're trying to boot is the correct one.
>
> Also, remember that it will look a little funny, if you have a 
> separate /boot partition -- the filenames will be in the "root" 
> directory, like this:
>
> title Fedora (2.6.35.10-74.fc14.x86_64)
>     root (hd0,0)
>     kernel /vmlinuz-2.6.35.10-74.fc14.x86_64 ro 
> root=UUID=69effc7d-ef6e-4982-9bdc-2f3bea9e056e rhgb quiet 
> SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us selinux=0
>     initrd /initramfs-2.6.35.10-74.fc14.x86_64.img
>
> It's the kernel line I'm referring to, it will be 
> "/vmlinuz-..." instead of "/boot/vmlinuz-..." -- but _only_ if 
> /boot is a separate partition.
>
> Quick question -- if it _doesn't_ boot, can you afford for this 
> system to be down until it can be fixed?
>
>  -Scott
>
>
> _______________________________________________
> talk mailing list
> talk at nblug.org
> http://nblug.org/cgi-bin/mailman/listinfo/talk
>
>

-- 
Ariste Software
Petaluma, CA 94952

http://www.aristesoftware.com