"Steven M. Bellovin" <smb%cs.columbia.edu@localhost> writes: > Second -- what should the return code be? Right now, it passes back > EBUSY, which doesn't seem right per errno(2). Looking at that man > page, there are a few that (to my eye) are a bit more appropriate, but > they're still stretching the actual meaning of the error code. EAGAIN, > perhaps? Perhaps EACCESS, because the point of the switch is to have something that can't be overriden in software. EROFS might work - doesn't quite fit but also won't be confused with something else for network setup.
Description: PGP signature