sn't mean you can use it.
Your motherboard and BIOS also need to be aware of it, and enable it.
--
Christopher Vance
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Wrong mailing list - if you don't already know really basic C, you
ain't a hacker.
Try .
--
Christopher Vance
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
.
I agree. Please.
OpenBSD's standard sh is a well-maintained pdksh, and is really nice -
significantly nicer than the pdksh version in ports, and much nicer
than the bash that got foisted on me at my last job or the csh I got
stuck with many jobs before that.
--
Christopher
ompiled about a week ago, and my kernel on
Monday.
--
Christopher Vance
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
as root
open file to write/update
downgrade/reopen file to readonly
mark remove on close
setuid non-root
Or you could call it a future unlink.
I'm sure there are holes in it, and I won't claim to have tried
On Thu, Oct 30, 2003 at 03:45:24AM -0800, Terry Lambert wrote:
Christopher Vance wrote:
You can already mark a fd 'close on exec'.
May I suggest a different feature: the ability to mark an open file
(not just its fd) 'remove on close', with permission checked at mark
time ra
6 matches
Mail list logo