Summary: | virtual/dev-manager ebuild not 'seeing' virtual/udev | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex Masidlover <amasidlover> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Emerge info |
Description
Alex Masidlover
2013-02-26 08:52:44 UTC
Created attachment 340154 [details]
Emerge info
non-OpenVZ kernel 2.6.32 has DEVTMPFS support and works with =sys-fs/udev-197* but OpenVZ for some reason have disabled this option from the kernel source,
supposedly this kernel option is not compatible with OpenVZ.
How did you mask new udev? Did you remember to mask both, the package and the virtual?
/etc/portage/package.mask:
>=sys-fs/udev-197
>=virtual/udev-197
And there are plenty of packages in tree already requiring at least >=197, like sys-apps/hwids when USE="udev" is enabled, sys-fs/udisks always, and some more... you have to selectively figure this out, mostly by hand :P
needless to say staying with 171 is a dead end
I only had the virtual package masked. I have now masked sys-fs/udev-197 as well and dev-manager is now satisfied... Thank you! Not sure what status to set on this bug; its certainly not obvious to me why adding an additional package mask suddenly solves the problem - there is no way I would have guessed to do that and I'm not really a Gentoo/Linux beginner. As for sticking with udev-171; I'm hoping that we'll see an OpenVZ 3.X kernel sometime later this year, otherwise I'll have to switch away from udev. |