| Summary: | start deprecating devfs compat names (/dev/{loop,md,ram}/#) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | SpanKY <vapier> |
| Component: | [OLD] Core system | Assignee: | udev maintainers <udev-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | n-roeser |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 371059 | ||
| Bug Blocks: | |||
|
Description
SpanKY
2009-05-11 04:02:07 UTC
Fine with me. Does the subject has a typo? I think you want to say to remove /dev/loop/0 that is the devfs compat name. If I understand you correctly, you mean deleting the first three rules out of 40-gentoo.rules: # old devfs path, removing this could break systems # Bug 195839 KERNEL=="md[0-9]*", SYMLINK+="md/%n" KERNEL=="loop[0-9]*", SYMLINK+="loop/%n" KERNEL=="ram[0-9]*", SYMLINK+="rd/%n" yes, deleting those first few lines in the gentoo file is what i mean How to progress on this bug? Should we just remove the rules in udev-141-r1 and add some ewarn to pkg_postinst, or do we need some longer deprecation period (how to announce it then - maybe some news item). create a USE flag "devfs-compat", default it to on, and then add a warning to pkg_postinst when USE=devfs-compat once that version moves into stable, we delete it from the latest unstable version and let things trickle down Added in udev-141-r1. Maybe some native speaker can improve the ewarn message. this breaks losetup -f, see bug #269359 uups, I meant bug #338766 it looks like this bug is done, at least for 197-r3 and above (current stable) vapier: please doublecheck if you have time |