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_PREPARE(3)						   BSD Library Functions Manual 					    MAC_PREPARE(3)

NAME
mac_prepare, mac_prepare_type, mac_prepare_file_label, mac_prepare_ifnet_label, mac_prepare_process_label -- allocate appropriate storage for mac_t SYNOPSIS
#include <sys/mac.h> int mac_prepare(mac_t *mac, const char *elements); int mac_prepare_type(mac_t *mac, const char *name); int mac_prepare_file_label(mac_t *mac); int mac_prepare_ifnet_label(mac_t *mac); int mac_prepare_process_label(mac_t *mac); DESCRIPTION
The mac_prepare family of functions allocates the appropriate amount of storage and initializes *mac for use by mac_get(3). When the result- ing label is passed into the mac_get(3) functions, the kernel will attempt to fill in the label elements specified when the label was pre- pared. Elements are specified in a nul-terminated string, using commas to delimit fields. Element names may be prefixed with the '?' char- acter to indicate that a failure by the kernel to retrieve that element should not be considered fatal. The mac_prepare() function accepts a list of policy names as a parameter, and allocates the storage to fit those label elements accordingly. The remaining functions in the family make use of system defaults defined in mac.conf(5) instead of an explicit elements argument, deriving the default from the specified object type. mac_prepare_type() allocates the storage to fit an object label of the type specified by the name argument. The mac_prepare_file_label(), mac_prepare_ifnet_label(), and mac_prepare_process_label() functions are equivalent to invocations of mac_prepare_type() with arguments of "file", "ifnet", and "process" respectively. RETURN VALUES
Upon successful completion, the value 0 is returned; otherwise the value -1 is returned and the global variable errno is set to indicate the error. SEE ALSO
mac(3), mac_free(3), mac_get(3), mac_is_present(3), mac_set(3), mac(4), mac.conf(5), maclabel(7) 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. Support for generic object types first appeared in FreeBSD 5.2. BSD
August 22, 2003 BSD
All times are GMT -4. The time now is 02:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy