On 11/9/18 6:45 PM, Darrick J. Wong wrote: > From: Darrick J. Wong <darrick.wong@xxxxxxxxxx> > > Most of the commands listed under "OTHER COMMANDS" apply to files or > filesystems. Create two new sections for that and populate them > appropriately. > > Here's what moves: > > fsmap: moves from file io commands to filesystem commands > utimes: moves from file io commands to file commands > >>From the OTHER COMMANDS section: > > lsattr/chattr: moves to file commands > flink: moves to file commands > stat/statx: moves to file commands > lsproj/chproj: moves to file commands > parent: moves to file commands > [gs]et_encpolicy: moves to file io commands > freeze/thaw: move to filesystem commands > inject: move to filesystem commands > resblks: move to filesystem commands > shutdown: move to filesystem commands > statfs: move to filesystem commands > label: move to filesystem commands Thank you for getting this better organized. Of course, I have some questions. :) What does "FILE COMMANDS" vs. "FILE I/O COMMANDS" mean, exactly? I ask because for example bmap & fiemap are still under FILE IO but they... really don't do file IO. What's your intended distinction with these new sections? Thanks, -Eric
