This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Running GCC as root


>>>>> "Ian" == Ian Lance Taylor <ian@airs.com> writes:

 >> $ grep unlink gas/*.c gas/as.c: unlink (out_file_name);
 >> gas/messages.c: unlink (out_file_name); $
 >> 
 >> The second call is the "funny" one I've mentioned -- if you have a
 >> look there, you'll know what I mean.

 Ian> I think both calls are correct, actually, although perhaps they
 Ian> shouldn't unlink devices.

Of course they shouldn't unlink devices.  What possible reason would
any normal program have for unlinking devices?

If I wanted /dev/null to go away, I'd use "rm /dev/null".  But if a
program accepts /dev/null as an file argument, that can only ever mean
"discard all output bits" or "read nothing on input" -- NEVER "unlink
/dev/null if you feel like it".

	  paul


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]