Red Hat Bugzilla – Bug 627832
[RFE] guestfish should print outputs in a suitable base (eg. octal for modes)
Last modified: 2015-09-27 22:25:22 EDT
Clone to RHEL 6 to ensure it will get fixed in 6.1.
+++ This bug was initially created as a clone of Bug #583242 +++
+++ This bug was initially created as a clone of Bug #582891 +++
Description of problem:
1. umask should return the current umask when called with no parameter, and should set the umask when it is called with a parameter. It can only return the previous umask but not the current umask. Or There should be a separate cmd to provide this feature(like " mount"/"mounts")
2. the return value should be more human readable.
The return value now is just calculate the oct bit value, which is very confused.
current return value is 18 for mode 022, instead of "022" or "0022"
022->000 010 010->2^1+2^4->18
Version-Release number of selected component (if applicable):
libguestfs-1.0.85-1.fc12.3.x86_64, latest git version
Steps to Reproduce:
--- Additional comment from firstname.lastname@example.org on 2010-04-17 17:36:15 EDT ---
Fix posted upstream:
Setting version to 6.1.
This will be fixed by a rebase (bug 613593).
Fixed by the rebase.
QA verified this bug with libguestfs-1.7.17-12.el6.x86_64 and
><fs> umask 0022
><fs> umask 0024
So change this bug to VERIFIED.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Some guestfish commands print integer results. In some cases, namely for file permissions, the natural radix for these results is octal. Instead, guestfish returned decimal integer results for commands such as umask. This has been corrected, and guestfish commands that return integers now return them in the natural radix for that number.
This is OK, thanks.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.