2.6.4-linode1-1um
You shoud make the dir /sys
It is used to store some of the things that used to be in /proc under 2.4
Adam
8 Replies
sysfs /sys sysfs defaults 0 0
In its dying moments my lish console had the following to say:
NET: Registered protocol family 1
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
ip6_tables: (C) 2000-2002 Netfilter core team
NET: Registered protocol family 17
NET: Registered protocol family 15
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
Initializing software serial port version 1
Using anticipatory io scheduler
/dev/ubd/disc0: unknown partition table
/dev/ubd/disc1: unknown partition table
Initializing stdio console driver
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
INIT: version 2.85 booting
INIT: Entering runlevel: 2
INIT: Id "0" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel</davem@redhat.com></greearb@candelatech.com>
The two lines that read "unknown partition table" are particularly suspect. Has anyone tried 2.6.4 and got the same results?
@adamgent:
Those of you who want to check out the new 2.6.4 kernel available, which can be run even if the host is on 2.4
You shoud make the dir /sys
It is used to store some of the things that used to be in /proc under 2.4
Adam
Additionally, you need to have udev and module-init-tools installed. These two items are usually not shipped distributions by default. (Newer ones will have it.)
Bill Clinton
@Bill Clinton:
Additionally, you need to have udev and module-init-tools installed. These two items are usually not shipped distributions by default. (Newer ones will have it.)
Bill Clinton
This is wrong. You don't need udev or module-init-tools (especially since modules are disabled).
I'm working on a "guide" to help transition to 2.6
-Chris
Google-happy, I found this great post -
2.[123456].*)
Also, caker pointed out that you should
apt-get install dhcp3-client
to fix in the correct manner (once you have your network back).
Background, to help others searching for an answer:
The migration to a new host upgraded my debian small distro's kernel to latest 2.6 (2.6.21.1), and the network did not come up.
Doing a ifdown eth0; ifup eth0
yielded an "Unrecognized kernel version" error.
I did the above edit and ifup eth0
no longer complains. Haven't yet rebooted to be 100% sure.
- Barrie
Very old Debian deployments (two or three years old) need to "apt-get install dhcp3-client". I'm pretty sure if you've ever ran apt-get update, apt-get upgrade in the past few years you would have pulled this in already.
-Chris