Talk:Mdev

stuart's guide to migrating
I've written a guide to migrating a modern baselayout-2 system to mdev, here:

https://blog.stuart.shelton.me/archives/891

Feel free to integrate the details.

-- stuart

Firmware loading
What is the state of firmware loading with mdev? We're going to drop udev dependency from firmwares soon, so the 'sanity check' here won't catch them anymore. We'd like our users to avoid having broken systems by that, so we'd appreciate any tips on how to proceed. Michał Górny 21:33, 23 August 2012 (UTC)


 * I'm not up to speed with mdev, but as things stand now udev is a runtime dependency for the firmwares to work, so unless you have another (tested) way to make them work, you can't drop the dependency from firmware ebuilds. — yngwin (wiki admin) (talk) 07:46, 24 August 2012 (UTC)

(Don't worry about the "DEPRECATED"s.)
Err, users should worry about them. Deprecated things may get removed in a future version, and will get removed someday. Michał Górny 21:45, 23 August 2012 (UTC)

Is it just a matter of selecting the correct blob?

 * I was dealing with the video system on my laptop, which reminded me of this question. As I mentioned in the "ATI/AMD binary blobs" section...

This means that after emerging radeon-ucode, I have to clean out all but one blob from /lib64/firmware/radeon. I.e. I have to manually select the correct blob, because udev isn't around to do so. If that's the extent of the problem, then it's not major. Yes, the user/admin has to do a little bit of extra work, but it's their choice to take this path. --Walter Dnes 23:11, 12 October 2012 (UTC)
 * if there are multiple blobs in the source directory, the system needs udev to identify the correct blob to load
 * if there is only 1 blob, it loads automatically

/sbin/linuxrc
I am running mdev without /sbin/linuxrc script and without the additional linux boot entry init=/sbin/linuxrc. If someone could test it to migrate to mdev skipping this step. Needle (talk) 14:54, 18 May 2013 (UTC)