Sponsored Content
Full Discussion: Are the BSDs dying?
The Lounge What is on Your Mind? Are the BSDs dying? Post 303012217 by Corona688 on Wednesday 31st of January 2018 05:33:47 PM
Old 01-31-2018
Has it ever been wildly popular? It's been influential but that's not the same thing.

Much of that influence is from the BSD license. You can take anything you want, if you attribute (or, apparently, even when you don't.) Bits and pieces of it have ended up in everything.

I suspect it will remain what it's always been: A "reference implementation" for a standard system and kernel which you can build your own products out of.
These 2 Users 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
VOP_SETEXTATTR(9)					   BSD Kernel Developer's Manual					 VOP_SETEXTATTR(9)

NAME
VOP_SETEXTATTR -- set named extended attribute for a vnode SYNOPSIS
#include <sys/param.h> #include <sys/vnode.h> #include <sys/extattr.h> int VOP_SETEXTATTR(struct vnode *vp, int attrnamespace, const char *name, struct uio *uio, struct ucred *cred, struct thread *td); DESCRIPTION
This vnode call may be used to set specific named extended attribute for a file or directory. Its arguments are: vp The vnode of the file or directory. attrnamespace Integer constant indicating which extended attribute namespace the attribute name is present in. name Pointer to a null-terminated character string containing the attribute name. uio The location of the data to be read or written. cred The user credentials to use in authorizing the request. td The thread setting the extended attribute. The uio structure is used in a manner similar to the argument of the same name in VOP_WRITE(9). However, as extended attributes provide a strict "name=value" semantic, non-zero offsets will be rejected. The uio pointer may be NULL to indicate that the specified extended attribute should be deleted. The cred pointer may be NULL to indicate that access control checks are not to be performed, if possible. This cred setting might be used to allow the kernel to authorize extended attribute changes that the active process might not be permitted to make. Extended attribute semantics may vary by file system implementing the call. More information on extended attributes may be found in extattr(9). LOCKS
The vnode will be locked on entry and should remain locked on return. RETURN VALUES
If the extended attribute is successfully set, then zero is returned. Otherwise, an appropriate error code is returned. ERRORS
[EACCES] The the caller does not have the appropriate privilege. [ENXIO] The request was not valid in this file system for the specified vnode and attribute name. [ENOMEM] Insufficient memory available to fulfill request [EFAULT] The uio structure refers to an invalid userspace address. [EINVAL] The name, namespace, or uio argument is invalid. [EOPNOTSUPP] The file system does not support VOP_SETEXTATTR(). [ENOSPC] The file system is out of space. [EROFS] The file system is read-only. SEE ALSO
extattr(9), vnode(9), VOP_GETEXTATTR(9), VOP_LISTEXTATTR(9) AUTHORS
This manual page was written by Robert Watson. BSD
December 23, 1999 BSD
All times are GMT -4. The time now is 10:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy