Red Hat Bugzilla – Bug 582548
[mknod] umask shouldn't take effect when mode is set explicitly
Last modified: 2010-05-20 20:31:01 EDT
Description of problem:
Trying to create a new device file via mknod-b(block device file) or mknod-c(char device), the permission of the newly created file is not correctly by mknod.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a new device file via mknod-b
><fs> mknod-b 0770 8 1 /dev/sdg
2. Check the permission of the device file
><fs> ll /dev/sdg
brwxr-x--- 1 root root 8, 1 Apr 15 09:46 /sysroot/dev/sdg
The permission is not set correctly.
Permission is set correctly.
For char file, the permission is also not set correctly.
><fs> mknod-c 0770 5 1 /dev/char
><fs> ll /dev/char
crwxr-x--- 1 root root 5, 1 Apr 15 09:50 /sysroot/dev/char
This is expected. For the default umask is 022.
Reopen this bug for it it unreasonable for umask to take effect when mode has been set explicitly.
(In reply to comment #2)
> Reopen this bug for it it unreasonable for umask to take effect when mode has
> been set explicitly.
I think we need a 'mknod-mode' command.
We cannot change this (it's ABI).
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.