Considering BSD


 
Thread Tools Search this Thread
Operating Systems BSD Considering BSD
# 1  
Old 01-25-2009
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 Smilie
Login or Register to Ask a Question

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. ... (0 Replies)
Discussion started by: moxxx68
0 Replies
Login or Register to Ask a Question
GETPROGNAME(3)						   BSD Library Functions Manual 					    GETPROGNAME(3)

NAME
getprogname, setprogname -- get or set the program name LIBRARY
Utility functions from BSD systems (libbsd, -lbsd) SYNOPSIS
#include <bsd/stdlib.h> const char * getprogname(void); void setprogname(const char *progname); DESCRIPTION
The getprogname() and setprogname() functions manipulate the name of the current program. They are used by error-reporting routines to pro- duce consistent output. The getprogname() function returns the name of the program. If the name has not been set yet, it will return NULL. The setprogname() function sets the name of the program to be the last component of the progname argument. Since a pointer to the given string is kept as the program name, it should not be modified for the rest of the program's lifetime. In FreeBSD, the name of the program is set by the start-up code that is run before main(); thus, running setprogname() is not necessary. Programs that desire maximum portability should still call it; on another operating system, these functions may be implemented in a portabil- ity library. Calling setprogname() allows the aforementioned library to learn the program name without modifications to the start-up code. SEE ALSO
err(3), setproctitle(3) HISTORY
These functions first appeared in NetBSD 1.6, and made their way into FreeBSD 4.4. BSD
May 1, 2001 BSD