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 MOJAVE

_exit

EXIT(2) 						      BSD System Calls Manual							   EXIT(2)

NAME

     _exit -- terminate the calling process

SYNOPSIS

     #include <unistd.h>

     void
     _exit(int status);

DESCRIPTION

     The _exit() function terminates a process, with the following consequences:

     o	 All of the descriptors that were open in the calling process are closed.  This may entail delays; for example, waiting for output to
	 drain.  A process in this state may not be killed, as it is already dying.

     o	 If the parent process of the calling process has an outstanding wait call or catches the SIGCHLD signal, it is notified of the calling
	 process's termination; the status is set as defined by wait(2).

     o	 The parent process-ID of all of the calling process's existing child processes are set to 1; the initialization process (see the DEFINI-
	 TIONS section of intro(2)) inherits each of these processes.

     o	 If the termination of the process causes any process group to become orphaned (usually because the parents of all members of the group
	 have now exited; see ``orphaned process group'' in intro(2)), and if any member of the orphaned group is stopped, the SIGHUP signal and
	 the SIGCONT signal are sent to all members of the newly-orphaned process group.

     o	 If the process is a controlling process (see intro(2)), the SIGHUP signal is sent to the foreground process group of the controlling ter-
	 minal.  All current access to the controlling terminal is revoked.

     Most C programs call the library routine exit(3), which flushes buffers, closes streams, unlinks temporary files, etc., before calling
     _exit().

RETURN VALUE

     _exit() can never return.

SEE ALSO

     fork(2), sigaction(2), wait(2), exit(3)

STANDARDS

     The _exit function is defined by IEEE Std 1003.1-1988 (``POSIX.1'').

4th Berkeley Distribution					   June 4, 1993 					 4th Berkeley Distribution