> What has been interesting is that when we formed the Group and made the > mission statement, our target was BSD system administration. Yet > everywhere we go and have a BOF or talk to users, the programming topic > always comes up.
Howdy all. Long time lurker, first time caller. I think there's an important point in the heart of what Piotr (Rybicki) was saying. Perhaps we don't need to go so far as to test whether BSD admins know about a variety of system calls, but it may be worthwhile to test at a slightly higher level. That is, questions that answer: * What ARE system calls? * What system calls might relate to I/O operations? * What happens when a process forks? (What system call is involved? duh) * What system calls might relate to file descriptors? * What's the difference between and fork and an exec? * What system calls are involved in network operations? * How are semaphores used in interprocess communication? * What is a context switch? Basically, you'd be trying to see if the administrator could wrap their hands around ktrace and use it effectively. There's also a better chance that the administrator will understand what he or she is looking at under top, iostat, sockstat, netstat, etc. There's a bunch of entry-level and 2nd year university C stuff here, and it may not be very BSD specific either. Perhaps questions about ktrace itself may be more effective. -Yanek. _______________________________________________ BSDCert mailing list [email protected] http://lists.nycbug.org/mailman/listinfo/bsdcert
