Not very autofs specific. Ignore the rest if not interested...
[EMAIL PROTECTED]
>I concur with that approach....also works for "if ain't broke, don't touch it"
>and also works for "it's all messed and broken, you fix it instead
>of complaining....applies really well to the other operating system users"
Hmm, I'm not that fluent in english but I guess you agree with Linus
et al. That's fine. Of course, not many companies in this business
would agree with that, for obvious reasons.
>which docs are outdated ??
Are you kidding? I was messing round in the kernel yesterday to try
and figure out how copy-on-write in fork is implemented and the
details of the page table handling. The comments in the code are
_very_ sparse, and had references to files that haven't existed in
Linux for many years. The MMU support in general isn't documented
anywhere but in the LDP and they plainly state that they are outdated
and that you should buy one of the three kernel books that exist. And
the books explain how it works in general (when the books were written
that is, and Linux changes a lot faster than the books are printed),
but that I already know. The details of the implementation is only
documented in the source, as source, and is probably understood by a
handful of people on this entire planet. This perhaps works fine for
that handful of people, but I think it kind of defeats the meaning of
open source. Some comments in, or outside, the code might open it up
for a couple of dozen more developers. Of course if you are Linus and
still want to filter every bit changed in the kernel, you might want
to keep the changes to an absolute minimum and, other then not giving
away the source, removing the comments in the fairly obfuscated code
probably does the trick just fine...
To bring this back to autofs, I just checked the source and well, some
comments and documentation wouldn't hurt, would it hpa? Excellent work
otherwise, of course. Don't want to put down the effort and result of
the people doing this stuff...
Well, there are pros and cons to absolutely everything. All I really
know is that after a couple of days of digging in the memory handling
in the kernel all I want to say is,
char l,i;;main(k){for(l;k=i["]^k[k]^i[i]++i["];read('/'/'/',i+++"*5>+?480m{oKK\
\211\221",-('-'-'-'-k),-k));}read(j,i,k){l=+' '+(k-((*(char*)i)-(j<<(j<<j<<j\
)+(j&(k|j)))));write(i<<j<<j&j,(int)(int)(&l)|(l&~l),(&j,j<<j>>(j&j)),j&j&&j);}
/ronny
