Are the BSDs dying? Post: 303012179

Sponsored Content

The Lounge What is on Your Mind? Are the BSDs dying? Post 303012179 by dodona on Wednesday 31st of January 2018 09:17:22 AM

01-31-2018

Registered User

Are the BSDs dying?

Quote:

The open source Berkeley Software Distribution (BSD) versions of UNIX suffer from a lack of eyeballs on their code, and that hurts their security

Source

a quick google search making clear that this isn't really new, and if we look at our bsd Forum we see that its the only operation systems forum with the last comment dated to June last year, whereas all the others have more recent comments.
One comment dated to 2014 is exactly what I think of this issue:

Quote:

Linux is developed by many companies, individuals, and institutions on constant basis, so the quality of the code and capabilities of Linux generally surpass every OS out there minus some very specialized ones a la z/os specifically designed to work on mainframes. Nowadays, all is see is how feature A from Linux is going to get ported to BSD, never the other way around, which suggests that all BSD projects are dead or dying of they have completely stagnated.

Source

Beside windows, there will be only linux in a near future.

These 2 Users Gave Thanks to dodona For This Post:

dodona

View Public Profile for dodona

Find all posts by dodona

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

protocols

PROTOCOLS(5)						      BSD File Formats Manual						      PROTOCOLS(5)

NAME

     protocols -- protocol name data base

DESCRIPTION

     The protocols file contains information regarding the known protocols used in the DARPA Internet.	For each protocol a single line should be
     present with the following information:

	   official protocol name
	   protocol number
	   aliases

     Items are separated by any number of blanks and/or tab characters.  A ``#'' indicates the beginning of a comment; characters up to the end of
     the line are not interpreted by routines which search the file.

     Protocol names may contain any printable character other than a field delimiter, newline, or comment character.

INTERACTION WITH DIRECTORY SERVICES

     Processes generally find protocol records using one of the getprotoent(3) family of functions.  On Mac OS X, these functions interact with
     the DirectoryService(8) daemon, which reads the /etc/protocols file as well as searching other directory information services to determine
     protocol name and number information.

FILES

     /etc/protocols

SEE ALSO

     getprotoent(3), DirectoryService(8)

HISTORY

     The protocols file format appeared in 4.2BSD.

4.2 Berkeley Distribution					   June 5, 1993 					 4.2 Berkeley Distribution