From mboxrd@z Thu Jan 1 00:00:00 1970 From: random832@fastmail.com (Random832) Date: Fri, 24 Mar 2017 01:14:49 -0400 Subject: [TUHS] Were all of you.. Hippies? In-Reply-To: References: <20170320214858.TIJoR%steffen@sdaoden.eu> <009301d2a1c9$cb604c70$6220e550$@ronnatalie.com> <20170321202839.GG21805@naleco.com> <20170324001832.GA13511@naleco.com> <20170324002754.GW23802@mcvoy.com> Message-ID: <1490332489.2836059.921835720.2069930C@webmail.messagingengine.com> On Thu, Mar 23, 2017, at 21:03, ron minnich wrote: > In Unix, resources have names. They are visible in a name space, > organized > into directories. The names can be enumerated by opening and reading a > directory. Information about them can be determined with stat. Their > contents can be read by open and read. They can be changed with open and > write. And if each resource has a directory (possibly organized in a multiple-level hierarchy) containing several files that describe attributes of that resource, what are you to do when you want to print a report listing a summary of some information about those resources, one per line? And of course the information in these files is numeric - surely you don't expect the database of descriptions to be compiled into the kernel. So the tool has to go and fetch those too.