Like every other person I am from time to time compelled to list the directory structure from a certain point int the filesystem. I do so with
find /path/in/fs/ and this yields something like:
/path/in/fs/subfolder1 /path/in/fs/subfolder1/file1 /path/in/fs/subfolder1/subfolder2/yetanothefile /path/in/fs/subfolder1/subfolder2/yetanothefile2 /path/in/fs/subfolder1/subfolder2/yetanothefile3 /path/in/fs/subfolder1/file2
in a way this saves me from endless iterations of
Now I wanted to list the directory structure in the
/sys/class path and I think it falls short. The next two commands show the odd behavior:
- (1) using the
root@freak:/sys/class/hwmon# ls hwmon0 hwmon1 hwmon2 root@freak:/sys/class/hwmon# cd hwmon0 root@freak:/sys/class/hwmon/hwmon0# ls name power subsystem temp1_crit temp1_input uevent
- (2) using the said
findcommand at the same place
root@freak:/sys/class/hwmon# find . . ./hwmon0 ./hwmon1 ./hwmon2
As you can see it seems to me that
find does not show me everything, which I find an odd and suprising behavior.
Now I know that stuff below /sys/ is somehow special. Still it all works the
ls way. Somebody has an answer why this happens and better even how I can make find not overlook the content in ./hwmon0 ./hwmon1 ... etc for instance?