First, Thanks for the warning. I have not 'd-u'ed in the last two days. So I haven't had to fix this.
Next, Can or should I put on hold udev until initscripts and udev are resolved, or is this counter-productive or unadvisable.
Thak you in advance,
Rick

DeepDayze

Post subject: RE: Re: New udev [and /run] Posted: 06.04.2011, 13:56

Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline

Can we rollback to udev in testing till the issue is resolved. The fixed package does not solve the problem

clubex

Post subject:Posted: 06.04.2011, 13:59

Joined: 2010-09-11
Posts: 98

Status: Offline

see also the base-files bug

#621036 - base-files creates an unuseable /run, breaking udev and the whole system

perhaps aptosid team can repackage the testing versions of these packages in the fixes repo to make it easier for people to fix their systems?

That would be nice.

I can dist-upgrade my netbook via ethernet, and I just did. So I have udev 167-1+c0.aptosid.1 installed. But, no keyboard and no mouse in init 5, and no wireless. Using Alt-SysRq R S E, I can exit the KDM greeter, and then log in to the tty1 and work with ethernet only. I guess we're waiting ....

DeepDayze

Post subject:Posted: 06.04.2011, 14:59

Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline

OK, I downgraded base-files, udev, libudev0, libgudev to the versions in testing and my laptop works fine again. Also removed the /run directory in init 1 to be safe before going to init 5. Will hold off on dist-upgrades till it is safe to do so again after its confirmed that udev and base-files packages are fixed.

snvv

Post subject:Posted: 06.04.2011, 16:12

Joined: 2010-09-13
Posts: 329

Status: Offline

I downgraded udev from testing and now mouse and keyboard work without problem.

clubex

Post subject:Posted: 06.04.2011, 16:53

Joined: 2010-09-11
Posts: 98

Status: Offline

An explanation for the new /run directory from the systemd maintainer.