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:
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.