Summary: | Changed group ownerhip of "host" /dev files when using chroot to install | ||
---|---|---|---|
Product: | [OLD] Docs-user | Reporter: | Johannes Niess <johannes_niess> |
Component: | Gentoo Linux x86 Installation Guide | Assignee: | Gentoo Release Team <releng> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Johannes Niess
2003-12-21 03:47:46 UTC
uhh, what did you do in order to achieve this ? changing permissions inside of a chroot shouldnt affect the host system ... I believe that is due to the bind-mounting of /dev to /mnt/gentoo/dev. If you don't bind-mount the /dev to /mnt/gentoo/dev, you somethimes get "/dev/null: permission denied" or "/dev/null: device or resource not found" as we have seen on the Knoppix installations. I don't know how to solve this... I don't like fuzzy information like "Some installation media require you to bind-mount /dev, others don't". This is a real problem it also occured on my system. After an step1 install I was not any longer able to use a console as user or play a sound. A good solution would be to make sure that no script changes permissions of /dev until the first run of gentoo. I really hate it that my clean /dev system is now compromissed. did you bind mount your /dev? If so, there is really no reason to do so. closing since there has been no response and it seems that the bug was caused by an improper bind-mount. |