02-02-2018
I have zero experience with BSD(s), but i've heard all the praises for their network stack.
Haven't tested it in real world, and development in linux is moving light speed so perhaps it is not the case anymore.
The victory of linux over unix(es) is perhaps a victory for consumers having cheap (free) operating system, but i do not see it as a good thing for IT in general.
Domination of one product and philosophy, regardless if it's open and free is still a bad thing.
As my older colleagues say, system admins will remember the good old days where servers were made to last, programs coded with care and implemented per standards.
Regards
Peasant.
7 More Discussions You Might Find Interesting
1. Ubuntu
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... (1 Reply)
Discussion started by: riwa
1 Replies
2. IP Networking
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... (2 Replies)
Discussion started by: no3more
2 Replies
3. Boot Loaders
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... (6 Replies)
Discussion started by: Blackbird
6 Replies
4. Programming
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.
... (2 Replies)
Discussion started by: sm9ai
2 Replies
5. Shell Programming and Scripting
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... (4 Replies)
Discussion started by: CluelessPerson
4 Replies
6. Shell Programming and Scripting
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... (4 Replies)
Discussion started by: Marc G
4 Replies
7. Red Hat
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... (1 Reply)
Discussion started by: shekar777
1 Replies
LEARN ABOUT OSX
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