DebianThis forum is for the discussion of Debian Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi, glad to know it worked. I'm not sure why udev isn't automatically updated when executing 'apt-get upgrade'. I've realized that 'apt-get -u upgrade' doesn't upgrade all the packages available for upgrade (I issued the command a few days ago and my KDE is still the previous version, so I'll have to upgrade it manually with apt-get). If you're using Etch too, that might be the source of the problem because Etch is the testing version (not stable yet). Anyway, don't forget to upgrade udev the next time you upgrade your system... just to avoid this problem to happen again.
this might help.
i had the same problem when i upgraded from a 2.6.8 kernel to 2.6.15 kernel. my sata harddrive had shown up as a hda1 with 2.6.8 kernel and sda1 with 2.6.15 kernel. so you might try editing the grub entry before booting. in the grub menu highlight the 2.6.16 entry and type 'e' to edit it.
I'm having the same problem.. but i can't solve it
i'm not able to put the machine to work anymore
i tryed to install udev with chroot command at knoppix .. unsucessfully, it reports it can't configure it (because of not acessing /dev/null )
i tryed the debian CD in rescue mode.. even so. it doesn't allow to install stuff properly (reports that detects chroot mode and doesn't allow to proceed)
i thought about install a 2.4 kernel, because it won't use the udev stuff (i'm not sure.. but) .. anyway it wont let me to install it..
all i got now is dispair!!!!
the machine is a web server and i made an upgrade in order to solve dependencies because i got to install the latest mono package.... then something bad occured and the system invited me to run
.. cool to do in just installed small systems,, tedious and dangerous in large systems
as u can figure. i can't let the server being down .. even if it is for development only... few, but important users
here it goes... obviously there's something kinky about udev + debian.. or not .. is not safe to manage the udev while running the 2.6 kernel, so it wont let mess with it while the kernel is running ... good old policy of debian unfortunately this is a tricky problem... in order to keep stability, we loose compatibility (udev is not upgraded along the other packages) .. now what? debian has this problem because it is a very flexible system... other distros don't have this problems... but also don't have this level of manipulation.. play dirt.. get dirt ... in a beautiful way (debian way)
if u got problems, u must boot with a 2.4.X kernel... or perhaps a previous to 2.6.12 kernel. udev is used by kernels >= 2.6.12.
after booting, with aptitude purge udev, purge 2.6.x kernel
once again with aptitude, install 2.6 kernel .. it will install udev to satisfy dependencies
reboot the machine with the brand new kernel
I had this problem on a friends computer that I had just installed Etch on. While I was away, he used the auto-update function, which I would never do, but I don't know if that was related to the issue or not.
I always leave 2 complete kernels on the system. At that point, I had the default etch 2.6.15-486, and the "proper" 2.6.15-k7 kernels. When it locked up, I booted using the ~-486 kernel, did an aptitude remove --purge on the ~-k8 kernel ... went to Sid and got the 2.6.17-k7 kernel, installed it (included udev), problem solved.
I think Etch users should get the 2.6.17 kernel anyway, because my understanding is, that's the one Debian is aiming at for Etch-stable.
I tried to upgrade udev, but it sayed it was already the latest version.
Then I did apt-cache show udev wich learned me udev conflicted with initramfs-tools. That is exactly the package where the initrd is built with! Googled for replacement and there it is.