Sponsored Content
Full Discussion: Are the BSDs dying?
The Lounge What is on Your Mind? Are the BSDs dying? Post 303012188 by Corona688 on Wednesday 31st of January 2018 11:45:24 AM
Old 01-31-2018
Quote:
Originally Posted by drysdalk
And to play the real Devil's Advocate here, don't forget the most popular UNIX distros in the world in terms of number of installations and sites: iOS and macOS.
macos certainly, but ios? It took years for it to even become multitasking. I don't think it's an implementation of UNIX.
This User Gave Thanks to Corona688 For This Post:
 

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... (1 Reply)
Discussion started by: riwa
1 Replies

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... (2 Replies)
Discussion started by: no3more
2 Replies

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... (6 Replies)
Discussion started by: Blackbird
6 Replies

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. ... (2 Replies)
Discussion started by: sm9ai
2 Replies

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... (4 Replies)
Discussion started by: CluelessPerson
4 Replies

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... (4 Replies)
Discussion started by: Marc G
4 Replies

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... (1 Reply)
Discussion started by: shekar777
1 Replies
NUKE(8) 						      System Manager's Manual							   NUKE(8)

NAME
nuke - launch nuclear weapons at mapped USENET sites SYNOPSIS
/etc/nuke [-y yield] [-a height] [-hcm] sitename... DESCRIPTION
Nuke employs the `missile coordinate' fields in the USENET map database and Internet connections to a server interfaced with AUTOVON to lob nuclear weapons at other UNIX sites, specified by name. The default warhead is a single 25KT groundburst tac nuke; options support other combinations of warhead size, type and deployment. The -y option specifies a yield. The argument must be a number suffixed by K or M, for kiloton or megaton respectively. Yield arguments above 255M are quietly ignored. The -a option specifies an air-burst height in meters. The -h option specifies thermonuclear (hydrogen) weapons. The -c option specifies cobalt-jacketed warheads for permanent site interdiction. The -m option, useful with multiple-site nuke calls, invokes code which optimizes delivery using MIRVed warheads to minimize launches. In accordance with the normal UNIX design philosophy nuke does not prevent you from nuking yourself. FILES
/usr/lib/maps/* USENET map file database BUGS
If a target site has given only nearest-city coordinates in its map entry, incorrect targeting and significant collateral casualties may result. Heavy use of nuke may cause EMP effects which interfere with Internet service. NOTE
This command is restricted to super-users only. AUTHOR
Eric S. Raymond <esr@thyrsus.com> UNIX
13 October 1991 NUKE(8)
All times are GMT -4. The time now is 05:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy