DragonFly kernel List (threaded) for 2008-02
er_reader.dragonflybsd.org> <47b34981$0$856$415eb37d@crater_reader.dragonflybsd.org> <email@example.com> <47b35e26$0$848$415eb37d@crater_reader.dragonflybsd.org> <firstname.lastname@example.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
X-Trace: 1202976706 crater_reader.dragonflybsd.org 854 188.8.131.52
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:12137
Yury Tarasievich wrote:
> On Wed, 13 Feb 2008 23:16:20 +0200, Bill Hacker <email@example.com> wrote:
>> Steve O'Hara-Smith wrote:
>>> Bill Hacker <firstname.lastname@example.org> wrote:
>> Mind - there is more to it than just the rm or the globbing issue.
>> The larger picture is a new set of predictable CLI tools for
>> large/heavily populated fs that can be safely called from <wherever> -
>> GUI's included.
> Bill, won't it be more productive if you sketched at least the crude outline of specification of what you envision and published it on dfly wiki?
In retrospect - certainly - and I'll try to make the time within the
next week or so to do just that.
I have to admit, that as is the case with most 'long ago and far away'
[former ] old-fart] coders, I had - as is now obvious - come to take the
'convenience' of the good work done by so many others for granted, and
had lost track of these sort of limitations long since.
Mea Culpa - I had no wish to start a distracting side trip.
That said, I remain surprised that others haven't already said, and
sooner, rather than later, words to the effect:
'Yes, historical reasons quite aside, these common and frequently needed
tools can too often be more arcane than they need to be'.
Simon's (eventual) code snippet the most concrete step - and, to date,
also the most objectively delivered - graciously sans commentary he
must have had to bite his keyboard to resist ...