Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
PostPosted: Mon Dec 10, 2012 4:07 pm 
Offline
Senior Member

Joined: Wed May 13, 2009 1:32 pm
Posts: 737
Location: Italy
As title.

I need to choose if use the 3.6.5 kernel from Linode or use the builtin kernel from CentOS.

What do you suggest and why?

I would like to use the latest from linode but how can a 3.6.5 kernel work on a distro that is far behind this kernel?

Any suggestions will be appreciated, obviously please explain the reason of the suggestions.

Thanks.


Top
   
PostPosted: Tue Dec 11, 2012 12:36 pm 
Offline
Senior Member
User avatar

Joined: Tue May 26, 2009 3:29 pm
Posts: 1691
Location: Montreal, QC
Stick with the Linode-provided kernel unless you have a specific reason or need to use a custom kernel from your distro. Linode keeps the kernel up to date with what they know works with their platform, so unless you have something that doesn't work because of the kernel version, or some kernel feature you're missing, it's best to stick with what they provide.


Top
   
PostPosted: Tue Dec 11, 2012 5:54 pm 
Offline
Senior Member

Joined: Wed May 13, 2009 1:32 pm
Posts: 737
Location: Italy
thanks for sharing your opinion.
in any case I just want to give a try...

is there someone running CentOS 6.3 who tried the script from this page?
http://library.linode.com/custom-instan ... h_centos-5


Top
   
PostPosted: Wed Dec 12, 2012 4:31 pm 
Offline
Senior Member

Joined: Wed May 13, 2009 1:32 pm
Posts: 737
Location: Italy
Ok I have booted the CentOS kernel, cool it works well...
One things...

how can I set my boot to show services that is starting.

Do you know the dear old boot screen that show,
iptables: Applying firewall rules: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0:
Determining IP information for eth0... done.
[ OK ]
Starting system logger: [ OK ]
Starting system message bus: [ OK ]
Retrigger failed udev events[ OK ]
Starting snmpd: netlink: 12 bytes leftover after parsing attributes.
[ OK ]
Starting snmptrapd: [ OK ]
Starting sshd: [ OK ]
Starting mysqld: [ OK ]
Starting Dovecot Imap: [ OK ]
Starting postfix: [ OK ]
Starting mailgraph: [ OK ]
Starting httpd: [ OK ]
Starting crond: [ OK ]
Starting squid: .[ OK ]
Starting fail2ban: [ OK ]
Starting atd: [ OK ]

etc.

When my centos boot I can't see any information on the services that is starting.
this is my grub.conf

cat /boot/grub/grub.conf

# 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)
# kernel /boot/vmlinuz-version ro root=/dev/xvda
# initrd /boot/initrd-version.img
#boot=/dev/xvda
default=0
timeout=5
title CentOS (2.6.21-279.14.1.el6)
root (hd0)
kernel /boot/vmlinuz-2.6.32-279.14.1.el6.x86_64 root=/dev/xvda
initrd /boot/initramfs-2.6.32-279.14.1.el6.x86_64.img


Any idea?
Thanks.


Top
   
PostPosted: Thu Dec 13, 2012 1:25 pm 
Offline
Senior Member
User avatar

Joined: Tue Apr 13, 2004 6:54 pm
Posts: 833
You may need to add something like
xencons=tty console=tty1 console=hvc0
to the "kernel" line

For reference, the linode provided kernel boots with these options:
root=/dev/xvda xencons=tty console=tty1 console=hvc0 nosep nodevfs ramdisk_size=32768 ip_conntrack.hashsize=8192 nf_conntrack.hashsize=8192 ro


("cat /proc/cmdline")

_________________
Rgds
Stephen
(Linux user since kernel version 0.11)


Top
   
PostPosted: Thu Dec 13, 2012 3:21 pm 
Offline
Senior Member

Joined: Wed May 13, 2009 1:32 pm
Posts: 737
Location: Italy
sweh wrote:
You may need to add something like
xencons=tty console=tty1 console=hvc0
to the "kernel" line

For reference, the linode provided kernel boots with these options:
root=/dev/xvda xencons=tty console=tty1 console=hvc0 nosep nodevfs ramdisk_size=32768 ip_conntrack.hashsize=8192 nf_conntrack.hashsize=8192 ro


("cat /proc/cmdline")



you catched it!!! great.
what this "nosep nodevfs ramdisk_size=32768" stand for?
shoudl I add this parameter too?


Top
   
PostPosted: Thu Dec 13, 2012 8:33 pm 
Offline
Senior Member
User avatar

Joined: Tue Apr 13, 2004 6:54 pm
Posts: 833
You shouldn't need those; standard "real" Centos installs don't need them and you'll be running the real Centos kernel. You only need the console stuff 'cos you're not using a real video display.

_________________
Rgds

Stephen

(Linux user since kernel version 0.11)


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: hjohnson57 and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group