Are the BSDs dying? Post: 303012227

Sponsored Content

The Lounge What is on Your Mind? Are the BSDs dying? Post 303012227 by Neo on Wednesday 31st of January 2018 11:15:49 PM

02-01-2018

Administrator

There is nothing "dead" about BSD. BSD lives in the heart and soul of MacOS, and MacOS is a very popular computer operating system. All software changes over time, and BSD is no exception and BSD changed the heart of the MacOS forever:

Reference:

BSD Overview

Quote:

BSD Overview

The BSD portion of the OS X kernel is derived primarily from FreeBSD, a version of 4.4BSD that offers advanced networking, performance, security, and compatibility features. BSD variants in general are derived (sometimes indirectly) from 4.4BSD-Lite Release 2 from the Computer Systems Research Group (CSRG) at the University of California at Berkeley. BSD provides many advanced features, including the following:

Preemptive multitasking with dynamic priority adjustment. Smooth and fair sharing of the computer between applications and users is ensured, even under the heaviest of loads.

Multiuser access. Many people can use an OS X system simultaneously for a variety of things. This means, for example, that system peripherals such as printers and disk drives are properly shared between all users on the system or the network and that individual resource limits can be placed on users or groups of users, protecting critical system resources from overuse.

Strong TCP/IP networking with support for industry standards such as SLIP, PPP, and NFS. OS X can interoperate easily with other systems as well as act as an enterprise server, providing vital functions such as NFS (remote file access) and email services, or Internet services such as HTTP, FTP, routing, and firewall (security) services.
Memory protection. Applications cannot interfere with each other. One application crashing does not affect others in any way.

Virtual memory and dynamic memory allocation. Applications with large appetites for memory are satisfied while still maintaining interactive response to users. With the virtual memory system in OS X, each application has access to its own 4 GB memory address space; this should satisfy even the most memory-hungry applications.
Support for kernel threads based on Mach threads. User-level threading packages are implemented on top of kernel threads. Each kernel thread is an independently scheduled entity. When a thread from a user process blocks in a system call, other threads from the same process can continue to execute on that or other processors. By default, a process in the conventional sense has one thread, the main thread. A user process can use the POSIX thread API to create other user threads.

SMP support. Support is included for computers with multiple CPUs.

Source code. Developers gain the greatest degree of control over the BSD programming environment because source is included.

Many of the POSIX APIs.

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

7 More Discussions You Might Find Interesting

1. Ubuntu

Internet dying in Debian?

For some reason after a while my internet connection dies. I just moved on to Debian from Ubuntu and I can't find the dhclient-program to reconfigure dhcp. Pretty new to *nix's. ONe thing I noticed while rebooting (do get my connection back) is that it configures dhcp and says: reconfigure (or...

2. IP Networking

network connection dying after an uptime of a day or two days

hie guys I am running fedora 6 on remote machines which are connecting to my server. The remote machines connect through one machine (more like my router) to the server. The problem i am having is that the remote machines are suppose to be reporting in real time mode to the server. Most of these...

3. Boot Loaders

EFI on BSDs problem

Hi, at time I have some problems installing a BSD system on my GPT disk... Thing is, I don't understand why support for the EFI seems to be so hard. Neither FreeBSD nor NetBSD nor OpenBSD seem to be able to install on GPT disks. They all misconceive the hard disk would use an MBR and the DOS...

4. Programming

Java application dying randomly

Hi, (First post, please be gental!) I have a java app that I am running on unix (centos) But it keeps dying randomly. The times seem random from anything between 3 hours and 3 days. I have a cronjob running to restart it when ever it dies but I would rather this happened less often. ...

5. Shell Programming and Scripting

Expect script cronjob running but dying prematurely

I have an Ubuntu machine that I'd like to update automatically. I've written an expect script to run the aptitude package manager and update my packages. Essentially it does: aptitude update && aptitude upgrade while answering "yes" at the appropriate time. It works quite nicely when run...

6. Shell Programming and Scripting

Utilities not dying after script run

Hi folks, Friendly router geek wanting to be a programmer here... So I worked with another guy here and came up with this to capture Unix admin data: #!/bin/ksh # # # Set Default Paths # PATH=/usr/apps/client/bin:$PATH; export PATH...

7. Red Hat

Snmpd dying on centos7.1

Hello All, SNMPD dying after 2 mins once it started. Here is the configuration Oct 12 04:43:00 localhost systemd: Starting Simple Network Management Protocol (SNMP) Daemon.... Oct 12 04:43:00 localhost snmpd: dlopen failed: /usr/lib64/libcmaX64.so: cannot open shared object file: No such...

LEARN ABOUT OSX

pthread_key_create

PTHREAD_KEY_CREATE(3)					   BSD Library Functions Manual 				     PTHREAD_KEY_CREATE(3)

NAME

     pthread_key_create -- thread-specific data key creation

SYNOPSIS

     #include <pthread.h>

     int
     pthread_key_create(pthread_key_t *key, void (*destructor)(void *));

DESCRIPTION

     The pthread_key_create() function creates a thread-specific data key that is visible to all threads in the process.  Key values provided by
     pthread_key_create() are opaque objects, used to locate thread-specific data.  Although the same key value may be used by different threads,
     the values bound to the key by pthread_setspecific() are maintained on a per-thread basis and persist for the life of the calling thread.

     Upon key creation, the value NULL is associated with the new key in all active threads.  Upon thread creation, the value NULL is associated
     with all defined keys in the new thread.

     An optional destructor function may be associated with each key value.  If a key value has a non-NULL destructor function pointer, and the
     thread has a non-NULL value associated with the key at the time of thread exit, then the key value is set to NULL and the destructor function
     is called with the previous key value as its argument.  The order of destructor calls at thread exit is unspecified.

     If, after all the destructors have been called for all non-NULL values with associated destructors, there are still some non-NULL values with
     associated destructors, then the process is repeated.  If, after at least [PTHREAD_DESTRUCTOR_ITERATIONS] iterations of destructor calls for
     outstanding non-NULL values, there are still some non-NULL values with associated destructors, the implementation stops calling destructors.

RETURN VALUES

     If successful, the pthread_key_create() function will store the newly created key value at the location specified by key and returns zero.
     Otherwise, an error number will be returned to indicate the error.

ERRORS

     pthread_key_create() will fail if:

     [EAGAIN]		The system lacked the necessary resources to create another thread-specific data key, or the system-imposed limit on the
			total number of keys per process [PTHREAD_KEYS_MAX] would be exceeded.

     [ENOMEM]		Insufficient memory exists to create the key.

SEE ALSO

     pthread_getspecific(3), pthread_key_delete(3), pthread_setspecific(3)

STANDARDS

     pthread_key_create() conforms to ISO/IEC 9945-1:1996 (``POSIX.1'').

BSD
								   April 4, 1996							       BSD