David Nicol <[EMAIL PROTECTED]> writes: > > One other possibility, if you're feeling masochistic, is to simply build the > > thing yourself, the old-fashioned way. That is, with pipe(2), fork(2), > > dup2(2), open(2), etc. Not needed here, but if you're doing something totally > > unique, sometimes it's the way to go. > > are you suggesting some kind of wrapper program, like nohup, that would > discard stdout, redirect stderr to stdout, and exec its args?
Nope. What I'm suggesting would be basically reimplementing that popen3 thing (whatever it's called in Perl) in terms of lower level system calls. If you look in the perl source, you'll probably see a bunch of those calls. Either that, or calls to popen(3) or system(3), in which case you can look in the libc source for the lower level calls. It's pretty tedious stuff, but interesting if you want to know how this all really works. -- Our local university offers a three hour course, College Algebra, which covers "elementary algebra, solution of equations, functions, exponential and logarithmic functions, inequalities, systems of linear equations, equations of second degree and their graphs, binomial theorem, complex numbers, and polynomials". They also offer a three hour course which covers Office 2000. Does this mean that Office is as simple to learn as College Algebra?
