udev wants inotify

I was a little surprised when I jumped from Crux 2.5 to 2.6 on the Thinkpad, and suddenly the machine wouldn’t boot.

Luckily, this time there was plenty of information to tell me what the problem was. udev, which I only hold in mild estimation anyway, was complaining that the kernel lacked inotify support, and had stopped the boot process.

Ordinarily, udev (now in it’s 146th incarnation, I guess) just spits out a message on boot, about its generalized unhappiness at the lack of inotify. I build kernels without inotify or dnotify, just because … well, because.

So in the interest of keeping udev from having a nervous breakdown and impeding the otherwise pleasant experience of using my Thinkpad, I quickly booted to a live environment, rebuilt the kernel with inotify support, and went back to what I was doing.

Easier done than said.

1 thought on “udev wants inotify

  1. Pingback: Stale NFS file handle errors « Motho ke motho ka botho

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s