Hide Forgot
Description of problem: tunegfs2 is a tune2fs work-a-like for GFS2. It should probably be located in the same directory. tune2fs is located in /sbin tunegfs2 is located in /usr/sbin tunegfs2 doesn't depend on any libraries in /usr so it could be moved to /sbin. [root@buzz-02 sbin]# ldd /usr/sbin/tunegfs2 linux-vdso.so.1 => (0x00007fff3f5ff000) libc.so.6 => /lib64/libc.so.6 (0x00000031c9400000) /lib64/ld-linux-x86-64.so.2 (0x00000031c8c00000) Version-Release number of selected component (if applicable): gfs2-utils-3.0.12.1-5.el6.x86_64 How reproducible: Every time Steps to Reproduce: 1. which tunegfs2 2. 3. Actual results: # which tunegfs2 /usr/sbin/tunegfs2 Expected results: # which tunegfs2 /sbin/tunegfs2 Additional info:
Well, the FHS says: /sbin contains binaries essential for booting, restoring, recovering, and/or repairing the system in addition to the binaries in /bin. [18] Programs executed after /usr is known to be mounted (when there are no problems) are generally placed into /usr/sbin. So bearing in mind that tunegfs2 shouldn't be needed for mounting the fs or recovering it, and we don't support gfs2 on root anyway, I'm not sure that this is a bug. I know we could move it, but I'm not convinced that it is in the wrong place, even if tune2fs is in /sbin.
I'm closing this as not a bug based on comment #2, if you think this is incorrect, then please reopen.