i have updated from debian lenny to debian squeeze,

 

installed a new (custom) kernel to run vservers.

 

for some reason grub keeps booting the old kernel (i do not have console access, only ssh)

 

, it should boot Linux 2.6.32-5-vserver-amd64 but it boots Linux 2.6.18-6-vserver-amd64…

when rebooting after installing the first time, the system hung, and i rebooted and the old kernel was loaded i guess, how to reset?

 

anyone knows?

 

Thanks in advance!

 

 

-(~:#)-> cat /boot/grub/grub.cfg

#

# DO NOT EDIT THIS FILE

#

# It is automatically generated by grub-mkconfig using templates

# from /etc/grub.d and settings from /etc/default/grub

#

 

### BEGIN /etc/grub.d/00_header ###

if [ -s $prefix/grubenv ]; then

load_env

fi

set default="0"

if [ "${prev_saved_entry}" ]; then

set saved_entry="${prev_saved_entry}"

save_env saved_entry

set prev_saved_entry=

save_env prev_saved_entry

set boot_once=true

fi

 

function savedefault {

if [ -z "${boot_once}" ]; then

saved_entry="${chosen}"

save_env saved_entry

fi

}

 

function load_video {

insmod vbe

insmod vga

insmod video_bochs

insmod video_cirrus

}

 

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

if loadfont /usr/share/grub/unicode.pf2 ; then

set gfxmode=640x480

load_video

insmod gfxterm

fi

terminal_output gfxterm

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

set locale_dir=($root)/boot/grub/locale

set lang=en

insmod gettext

set timeout=5

### END /etc/grub.d/00_header ###

 

### BEGIN /etc/grub.d/05_debian_theme ###

set menu_color_normal=cyan/blue

set menu_color_highlight=white/blue

### END /etc/grub.d/05_debian_theme ###

 

### BEGIN /etc/grub.d/10_linux ###

menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-vserver-amd64' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.32-5-vserver-amd64 ...'

linux /boot/vmlinuz-2.6.32-5-vserver-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro quiet

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.32-5-vserver-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-vserver-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.32-5-vserver-amd64 ...'

linux /boot/vmlinuz-2.6.32-5-vserver-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro single

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.32-5-vserver-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.32-5-amd64 ...'

linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro quiet

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.32-5-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.32-5-amd64 ...'

linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro single

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.32-5-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.26-2-amd64' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.26-2-amd64 ...'

linux /boot/vmlinuz-2.6.26-2-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro quiet

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.26-2-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.26-2-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.26-2-amd64 ...'

linux /boot/vmlinuz-2.6.26-2-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro single

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.26-2-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.18-6-vserver-amd64' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.18-6-vserver-amd64 ...'

linux /boot/vmlinuz-2.6.18-6-vserver-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro quiet

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.18-6-vserver-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.18-6-vserver-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.18-6-vserver-amd64 ...'

linux /boot/vmlinuz-2.6.18-6-vserver-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro single

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.18-6-vserver-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.18-6-amd64' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.18-6-amd64 ...'

linux /boot/vmlinuz-2.6.18-6-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro quiet

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.18-6-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.18-6-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.18-6-amd64 ...'

linux /boot/vmlinuz-2.6.18-6-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro single

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.18-6-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.18-5-amd64' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.18-5-amd64 ...'

linux /boot/vmlinuz-2.6.18-5-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro quiet

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.18-5-amd64

}

menuentry 'Debian GNU/Linux, with Linux 2.6.18-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {

insmod part_msdos

insmod ext2

set root='(hd0,msdos2)'

search --no-floppy --fs-uuid --set 6cbed369-7638-4094-9b47-7e57d102ec5a

echo 'Loading Linux 2.6.18-5-amd64 ...'

linux /boot/vmlinuz-2.6.18-5-amd64 root=UUID=6cbed369-7638-4094-9b47-7e57d102ec5a ro single

echo 'Loading initial ramdisk ...'

initrd /boot/initrd.img-2.6.18-5-amd64

}

### END /etc/grub.d/10_linux ###

 

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

 

### BEGIN /etc/grub.d/30_os-prober ###

### END /etc/grub.d/30_os-prober ###

 

### BEGIN /etc/grub.d/40_custom ###

# This file provides an easy way to add custom menu entries. Simply type the

# menu entries you want to add after this comment. Be careful not to change

# the 'exec tail' line above.

### END /etc/grub.d/40_custom ###

 

### BEGIN /etc/grub.d/41_custom ###

if [ -f $prefix/custom.cfg ]; then

source $prefix/custom.cfg;

fi

### END /etc/grub.d/41_custom ###

A while back I set my server time to the right time how they showed it here . I checked some logs and seem like the logs are all one hour off.

So instead of 12.30 it would show 11.30. So I decided I'd set the right timezone. I setup my clock like this:

 

vi /etc/sysconfig/clock

 

#ZONE="Europe/Amsterdam"

ZONE="GMT+1"

UTC=true

ARC=false

I rebooted. Didn't see a change

 

I also tried doing the following:

<strong>ln -sf /usr/share/zoneinfo/Europe/Amsterdam /etc/localtimeStill have the same problem. I tried #</strong>ZONE="Europe/Amsterdam"and replacing it by #ZONE="GMT+1" Didn't change anything either,still off by an hour. I'm kind of out ideas and everything I searchin google they all point towards these configuration options.

 

When I use date it always still shows:

 

Mon Nov 7 11:44:17 CET 2011

So I'm probably just missing one thing. Cuz CET is Central Eastern time and I need GMT. Will keep search but ideas to help me in the right direction are welcome

I have been on Linux for about 2 weeks now, and I am still a GIANT n00b. That's why I am on my Windows partition to write this topic. Anyways, I am looking for a way to link up multiple hard drives. I am looking at starting a server, so I have been researching tutorials on how to install Apache, PHP, nginx, and java. I was on a webpage recently, and I saw a complete server rack. I saw multiple hard drive cases, and I was thinking how do they link all those RAID drives together. As usual I used Google, and I got no results. So here's my question:

I made this post https://www.linux-noob.com/forums/index.php?/topic/4200-working-on-fail2ban/

I replied to it but I can't see my own reply. And Dave did too, when I click on the link in the

notification email I see it the reply. When I go via the the normal way http://linux-noob.com to forums

and look for the post I see nothing. Really strange. turned off proxy, cleared web browser history.

I got logwatch installed and working. I've also installed fail to ban and started the service. Still working on configuring it. I found out that I should be able to configure fail2ban to filter and ban per log. I found this in the fail2ban documention : at the bottom

Centos

<strong>Under CentOS / RedHat Enterprise Linux, httpd (Apache) is </strong><strong>not compiled with tcpwrappers support</strong><strong>. As a result the example in jail.conf called "apache-tcpwrapper" does not work since /etc/hosts.deny does not affe</strong>ct apache.

 

Mean that the filter [apache-tcpwrapper] won't work for me. So I did a bit of search and come across centos-fail2ban and seem they are using it there. So I'll just try to use it and configure it and see what the results are. But just strange two documentations saying two different things.

I've decided I want to build my own server and use it just as a server and for nothing else. That way I can just keep my desktop as a desktop and setup a home network and have my desktop running on a private network etc. Like I mentioned in my other post about wanting to proxy my internet traffic. I got two setups which aren't too expensive. I have put two systems together, one a a little different then the other. Just wanted your opinions.

 

 

*I removed the links cuz I found something better, see posts below here*

Please turn verify by admin on in general please. Those spammers are annoying the hell out of me. It's getting worse and worse [img]<___base_url___>//public/style_emoticons/default/sad.png[/img]

My proxy/webfilter is running great. Just thought it might be better to have it set for all devices connected on my internet network. So that I don't have to set it up mannually for every device. I have Linksys WRT160N, and I read that the standard linksys router software does not allow setting up a proxy. But that I need to use dd-wrt . I found an instruction on how to do it and it doesn't look that hard. But how smart is it to do. Cuz I always go by the saying for computer stuff: "don't fix what ain't broke" or I could buy a second network card, have my internet connection on it so that I could filter/proxy it and connect another router too it, and to the second router I could connect all my devices. or something like that? Not too great in networking. That acuatually sounds better if it is possible. Because I don't really like messing with router firmware if it's running fine.

 

So if I wanted to do it without messing with the firmware I would probably want to setup like this?

 

 

Downstairs(modem)-->router1--mypc(nic1)---proxy/filter-->mypc(nic2)--->router2(make this gateway for all connecting devices)

 

Does that sound correct? But I have no idea how I would be able to connect two nic's. would have to do some research on that.

 

http://www.alternate...Netwerkadapters

http://www.alternate...+LAN&l3=Routers

Here a topic to continue what started out here. It's more appropriate as a separate topic.

 

I changed the default ssh port in SL, and before it works you have to edited the iptables/firewall. I edited the firewall using system-config-firewall-tui

on Hybrid's advice and restarted the service. When connecting:

 

ssh -p 1234 user@ip

 

I still get connection refused. I did check the vi /etc/sysconfig/iptables

 

And it nicely made a new entry under port 22 mentioning my custom ssh port.

I was hoping this wouldn't happen but looks like this is the end of skype for linux users. Microsoft bought skype and now they are banning reverse engineering of the skype code.

Haven't used skype much, but it was a great app. I'll be looking for a good alternative.