Red Hat Bugzilla – Bug 583554
[FEAT] mknod-mode command is needed to set mode explicitly
Last modified: 2010-05-20 20:31:06 EDT
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):
Steps to Reproduce:
I've decided not to do this. The reason is that 'mknod-mode' would
be needlessly inconsistent with 'mkdir-mode'. The latter is affected
However, I have updated the documentation to note the effects of
umask and how to avoid them:
libguestfs-1.2.3-1.el5 has been submitted as an update for Fedora EPEL 5.
libguestfs-1.2.3-1.fc13 has been submitted as an update for Fedora 13.
libguestfs-1.2.3-1.fc12.6 has been submitted as an update for Fedora 12.
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.