I don't know if it means that it would become available in the proposed updates for intrepid or not. I don't enable that repo. Also, I think we all got notified that a guy testing the new udev in jaunty still has this problem with libsensors. Since I have 3 machines with this issue I have implemented what i think Peter Cordes was hinting at by modifying /etc/init.d/checkroot.sh for the time being:
after:
#
# Remove /lib/init/rw/rootdev if we created it.
#
rm -f /lib/init/rw/rootdev
I don't know if it means that it would become available in the proposed updates for intrepid or not. I don't enable that repo. Also, I think we all got notified that a guy testing the new udev in jaunty still has this problem with libsensors. Since I have 3 machines with this issue I have implemented what i think Peter Cordes was hinting at by modifying /etc/init. d/checkroot. sh for the time being:
after: rw/rootdev if we created it. rw/rootdev
#
# Remove /lib/init/
#
rm -f /lib/init/
added:
echo "UDEV /dev/.static/dev REMOUNT RW HACK"
mount -o remount,rw /dev /dev/.static/dev
after reboot: by-uuid/ 8a22bb23- 7295-4efc- 9d0a-a0b6c25dba 27 / ext3 rw,relatime, errors= remount- ro,data= ordered 0 0 by-uuid/ 8a22bb23- 7295-4efc- 9d0a-a0b6c25dba 27 /dev/.static/dev ext3 rw,errors= remount- ro,data= ordered 0 0 noexec, gid=5,mode= 620 0 0
$ cat /proc/mounts |grep /dev
udev /dev tmpfs rw,mode=755 0 0
/dev/disk/
/dev/disk/
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,
hopefully this is sane and sets aside the symptom long enough for things to get sorted out the way they should be