Blaisorblade <[EMAIL PROTECTED]> writes: >> but how hard can it >> be? > > That's a lie, face it... it _is_ hard. Being a very smart programmer helps, > but as you say documentation is lacking, so you become able to write good > code when you're able to face lack of documentation.
I meant that, it is not, of itself, difficult. It's only finding the information that is the problem. You don't have to be a super-genius to write kernel code. > Wait - I think this specific case does not need any work with dentries, it is > different from the crash I described. I was giving generic suggestions - > afterwards I looked at sys_getdents and found that this one was easier. > Finish this patch this way and it can be (IMHO) accepted with interest > (after "impedence matching" with kernel standards - codingStyle et similar > things). You mean finish it with vfs_readdir. I'll have a look. > Mconsole exec would also be useful for this, if it could return output - > maybe > redirecting to dev/console would do that (to test) or it could maybe be added > easily, now. Sure. It would be better the have the information in proc though. -- Nic Ferrier http://www.tapsellferrier.co.uk for all your tapsell ferrier needs ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
