Sponsored Content
Full Discussion: Are the BSDs dying?
The Lounge What is on Your Mind? Are the BSDs dying? Post 303012191 by drysdalk on Wednesday 31st of January 2018 12:16:50 PM
Old 01-31-2018
Hi,

Functionally-speaking, you're absolutely correct of course - you couldn't with a straight face call an iPad a UNIX workstation. But kernel-wise at least I believe iOS is UNIX underneath, as it runs a variant of the same Darwin/XNU kernel that macOS uses. So very strictly/technically/legally speaking, I believe iOS still counts as UNIX, but not in any actually useful real-world sense, no.
This User Gave Thanks to drysdalk 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
EXIT(2) 							System Calls Manual							   EXIT(2)

NAME
exit, _exit - terminate a process SYNOPSIS
void _exit(int status) DESCRIPTION
_exit terminates a process with the following consequences: All of the descriptors 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. If the parent process of the calling process is executing a wait or is interested in the SIGCHLD signal (Minix-vmd), then it is notified of the calling process's termination and the low-order eight bits of status are made available to it; see wait(2). The parent process ID of all of the calling process's existing child processes are also set to 1. This means that the initializa- tion process (see intro(2)) inherits each of these processes as well. Most C programs call the library routine exit(3), which performs cleanup actions in the standard I/O library before calling _exit. RETURN VALUE
This call never returns. SEE ALSO
fork(2), sigaction(2), wait(2), exit(3). 4th Berkeley Distribution May 22, 1986 EXIT(2)
All times are GMT -4. The time now is 12:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy