m...@linux.it (Marco d'Itri) writes:
> On May 12, David Kalnischkies <kalnischkies+deb...@gmail.com> wrote:
>
>> Good that i am not a developer so i can say crap and ask afterwards
>> for pointers to a documentation which tells me why udev can't e.g.
>> Breaks: linux-image-686 (<< x), linux-image-amd64 (<< x), ?
> *Breaks* may work, dependencies are not acceptable.
> Are there any objections from anybody to trying this?
The only affect I see this will have is that an installed linux-image meta
package will be updated. That might get a new kernel installed or not.
But how does that change anything for the system? It does not mean the
new kernel will be used at all. It does not mean older kernel images
will be removed. It does not change the kernel the system is currently
running. It in no way means udev will actually work.
>> As far as i understand i need for a successful boot udev and a kernel without
>> that option enabled. This doesn't imply to me that i need to install it in
> Also for a working system. There have been enough changes that the old
> udev will not like the new configuration files and will probably not
> work much, so the system must be rebooted ASAP after upgrading
> kernel+udev.
This really reminds me of the Windows world: You have moved your
mouse. This change will only take affect after a reboot. Reboot now?
When will you (meaning upstream) finally stabilize the udev api or allow
for transitions?
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
