its worse. the static msg.msg is useless, its never set anywhere. the
interface of system() makes no sense. its only used for running "outside"
and the parent proc doesnt need the fd to /dev/null, it could as well just
open it in the child like:

close(0); open("/dev/null", OREAD);

the caller goes at some lengths queueing processes waiting for the remount
to complete, but does it in two levels. thers a sleep and a qlock.
limitation on the number of processes that can be queued on a qlock()?

also, when fork() returns -1, it kills the parent.

the whole thing about remounting /net.alt seems wrong. it probably fixed
some issue at the labs with /net.alt being imported from some other machine
that kept rebooting or something.

after spending 5 minutes writing the code fixing all these issues mentiond
above, i'll just throw it all away and delete the whole remounting logic
for /net.alt in 9front.

--
cinap

Reply via email to