Bug 583554
| Summary: | [FEAT] mknod-mode command is needed to set mode explicitly | ||
|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | Yufang Zhang <yuzhang> |
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | unspecified | CC: | mbooth, virt-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-04-19 19:57:04 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I've decided not to do this. The reason is that 'mknod-mode' would be needlessly inconsistent with 'mkdir-mode'. The latter is affected by umask. However, I have updated the documentation to note the effects of umask and how to avoid them: http://git.annexia.org/?p=libguestfs.git;a=commitdiff;h=c2a8efc548d6f997049cbb3d63bab360b0d946b6 libguestfs-1.2.3-1.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/libguestfs-1.2.3-1.el5 libguestfs-1.2.3-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/libguestfs-1.2.3-1.fc13 libguestfs-1.2.3-1.fc12.6 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/libguestfs-1.2.3-1.fc12.6 libguestfs-1.2.3-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: Currently, mode is affected by umask when we create a new device file via mknod(mknod-b, mknod-c or mkfifo). Thus the mode we set in mknod is not the real mode of the device file. So we need a mknod-mode command, by which the mode we set is not affected by umask. Version-Release number of selected component (if applicable): ><fs> version major: 1 minor: 0 release: 85 extra: How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: