Sponsored Content
The Lounge What is on Your Mind? Is M$ safer than UN*X(-LIKE)?? Post 302210764 by Smiling Dragon on Tuesday 1st of July 2008 11:13:41 PM
Old 07-02-2008
There's malware out there for mac and linux. Don't get too cocky there Smilie
 

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

Nuclear Elephant iPhone Wipe making your iPhone Safer for Resale

For those with the iPhones here might read up how to wipe your personal data off the phone before reselling or trade-in. ;) source: Nuclear Elephant: iPhone Wipe June 1, 2008: Making your iPhone Safe for Resale Since my posts regarding the iPhone restore mode being insufficient for wiping... (0 Replies)
Discussion started by: sparcguy
0 Replies

2. UNIX for Dummies Questions & Answers

# /UNIX.org file deleting is safer or not

Hi All, Please tell me the use of # /Unix.org file it has reserved a huge disk space, I want to know is it safer to truncate or delete. Thanks - Rukshan.:) (1 Reply)
Discussion started by: rukshan4u2c
1 Replies

3. UNIX for Advanced & Expert Users

Why is editing a file by renaming the new one safer?

Hello: I've been reading about ways to edit files from the command line, and I've found two websites which state that the following is the safest way to edit a file: command original > new mv new originalThat is, renaming the newer file to the previous one. This is what the websites I mentioned... (8 Replies)
Discussion started by: Cacializ
8 Replies
MAC_FREE(3)						   BSD Library Functions Manual 					       MAC_FREE(3)

NAME
mac_free -- free MAC label LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <sys/mac.h> int mac_free(mac_t label); DESCRIPTION
The mac_free() function frees the storage allocated to contain a mac_t. RETURN VALUES
The mac_free() function always returns 0. WARNING: see the notes in the BUGS section regarding the use of this function. SEE ALSO
mac(3), mac_get(3), mac_prepare(3), mac_set(3), mac_text(3), posix1e(3), mac(4), mac(9) STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion of the draft continues on the cross-platform POSIX.1e implementation mailing list. To join this list, see the FreeBSD POSIX.1e implementation page for more information. HISTORY
Support for Mandatory Access Control was introduced in FreeBSD 5.0 as part of the TrustedBSD Project. BUGS
POSIX.1e specifies that mac_free() will be used to free text strings created using mac_to_text(3). Because mac_t is a complex structure in the TrustedBSD implementation, mac_free() is specific to mac_3, and must not be used to free the character strings returned from mac_to_text(). Doing so may result in undefined behavior. BSD
December 21, 2001 BSD
All times are GMT -4. The time now is 01:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy