Considering BSD

Tags

bsd

Operating Systems BSD Considering BSD

01-25-2009

Registered User

1, 0

Join Date: Jan 2009

Last Activity: 25 January 2009, 1:08 PM EST

Posts: 1

Thanks Given: 0

Thanked 0 Times in 0 Posts

Considering BSD

Hello! I am new to these forums, so please forgive me if I am posting this in the wrong section.

I am considering BSD as a Desktop operating system. I am a Linux user; but I would not consider myself technical at all. Would BSD be a good choice as a Desktop OS? What would some common issues be? What are the pros and cons of BSD over Linux? What are the similarities? Also, which BSD distribution would be best to use? I hear lots of good things about FreeBSD.

Thanks

MichaelPerkele

View Public Profile for MichaelPerkele

Find all posts by MichaelPerkele

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. BSD

for linux and BSD users interested in Unix system V/bsd

for all you unix/linux interested heres an online book for free that covers the basics of BSD SysV Unix commands and applications . giving the average linux user a perspective on the differences in context of the two operating systems and for BSD users covers material as a refernce guide. ...

LEARN ABOUT FREEBSD

cr_cansee

CR_CANSEE(9)						   BSD Kernel Developer's Manual					      CR_CANSEE(9)

NAME

     cr_cansee -- determine visibility of objects given their user credentials

SYNOPSIS

     #include <sys/param.h>
     #include <sys/systm.h>
     #include <sys/ucred.h>

     int
     cr_cansee(struct ucred *u1, struct ucred *u2);

DESCRIPTION

     This function determines the visibility of objects in the kernel based on the real user IDs and group IDs in the credentials u1 and u2 asso-
     ciated with them.

     The visibility of objects is influenced by the sysctl(8) variables security.bsd.see_other_gids and security.bsd.see_other_uids, as per the
     description in cr_seeothergids(9) and cr_seeotheruids(9) respectively.

RETURN VALUES

     This function returns zero if the object with credential u1 can ``see'' the object with credential u2, or ESRCH otherwise.

ERRORS

     [ESRCH]		The object with credential u1 cannot ``see'' the object with credential u2.

     [ESRCH]		The object with credential u1 has been jailed and the object with credential u2 does not belong to the same jail as u1.

     [ESRCH]		The MAC subsystem denied visibility.

SEE ALSO

     cr_seeothergids(9), cr_seeotheruids(9), mac(9), p_cansee(9)

BSD
								 November 19, 2006							       BSD

BSD