[osol-discuss] Project: Writing code for closed binaries

[Vivek Joshi]

Hello Team,

Greetings!

Is it a good idea to write our own code for the closed binaries like od,
kill etc. Here's the detailed list (as found at belenix.org),

   1. usr/bin/test
   2. usr/bin/printf
   3. usr/bin/iconv
   4. usr/bin/wait
   5. usr/bin/elfsign
   6. usr/bin/bg
   7. usr/bin/type
   8. usr/bin/cd
   9. usr/bin/getopts
  10. usr/bin/tr
  11. usr/bin/alias
  12. usr/bin/pax
  13. usr/bin/umask
  14. usr/bin/fg
  15. usr/bin/od
  16. usr/bin/read
  17. usr/bin/ulimit
  18. usr/bin/jobs
  19. usr/bin/hash
  20. usr/bin/sed
  21. usr/bin/fc
  22. usr/bin/unalias
  23. usr/bin/tail
  24. usr/bin/kill
  25. usr/bin/patch

Motivation? :
A few CS engineering students of third/final year had shown their interest
in working on opensolaris projects. IMO, implementing these utilities
shouldn't be a difficult task. They just need to look at man page for specs
and write C code adhering to the manuals. Though, it's NOT that simple but
it's a good start. What do you say?

Queries :
- Is it a good/feasible project we should implement in opensolaris?
- If yes, is anyone already working on the same?


Thanks!
Vivek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/opensolaris-discuss/attachments/20070302/9a8ebadf/attachment.html>