06-17-2008
Suggest to not divide *BSD into different churches.
There are less variants than Linux distros, and most traffic is not *BSD specific, but rather Xorg, applications or shell specific.
These threads you already have.
Suggest posters just specify the OS they are running on, current (specify) or release (number).
Many *BSD users multiboot UNIXes, *BSDs, Windows, OSX, ... aware of heterogenous networks.
Other people who can't dual boot, or startx, ... well ... this is not OS specific.
Unless there is a need to,
if it ain't broke, why fix it?
4 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
The Members Only Forum sub-heading has a spelling mistake. It should read visible. (1 Reply)
Discussion started by: dangral
1 Replies
2. Shell Programming and Scripting
The UNIX and Linux Forums have a number of active members that have published books or papers related to shell programming and scripting. You can check out their publications here:
Link Removed
Please note, as you can imagine, our forum experts can be quite busy! You will get a response... (0 Replies)
Discussion started by: Neo
0 Replies
3. What is on Your Mind?
Dear All,
Thank you for your support. As promised I have upgrade features for unix.com forum VIP members as follows:
Who's Online Permissions
Can View IP Addresses
Can View Detailed Location Info for Users
Can View Detailed Location Info of Users Who Visit Bad / No Permission... (0 Replies)
Discussion started by: Neo
0 Replies
4. What is on Your Mind?
Hi!
Any Spanish speaking forum members?
If so, please reply!
Thanks! (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT LINUX
cr_seeotheruids
CR_SEEOTHERUIDS(9) BSD Kernel Developer's Manual CR_SEEOTHERUIDS(9)
NAME
cr_seeotheruids -- determine visibility of objects given their user credentials
SYNOPSIS
int
cr_seeotheruids(struct ucred *u1, struct ucred *u2);
DESCRIPTION
This function determines the visibility of objects in the kernel based on the real user IDs in the credentials u1 and u2 associated with
them.
The visibility of objects is influenced by the sysctl(8) variable security.bsd.see_other_uids. If this variable is non-zero then all objects
in the kernel are visible to each other irrespective of their user IDs. If this variable is zero then the object with credentials u2 is vis-
ible to the object with credentials u1 if either u1 is the super-user credential, or if u1 and u2 have the same real user ID.
SYSCTL VARIABLES
security.bsd.see_other_uids
Must be non-zero if objects with unprivileged credentials are to be able to see each other.
RETURN VALUES
This function returns zero if the object with credential u1 can ``see'' the object with credential u2, or ESRCH otherwise.
SEE ALSO
cr_seeothergids(9), p_candebug(9)
BSD
November 11, 2003 BSD