Sponsored Content
Full Discussion: Are the BSDs dying?
The Lounge What is on Your Mind? Are the BSDs dying? Post 303012247 by dodona on Thursday 1st of February 2018 05:14:38 AM
Old 02-01-2018
Quote:
Originally Posted by Corona688
Has it ever been wildly popular? It's been influential but that's not the same thing.
.
see the BSD of the late 70ths/80ths has a lot more to do with *NIX as we know it today than AT&T who adopted a lot from BSD for System III and V. TCP,Internet, virtual memory, video terminal, vi/ex, reliable signals, job control and even printer queues, just to name a few, are all genuine BSD inventions.
 

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
LPC(8)							    BSD System Manager's Manual 						    LPC(8)

NAME
lpc -- line printer control program SYNOPSIS
lpc [command [argument ...]] DESCRIPTION
lpc is used by the system administrator to control the operation of the line printer system. For each line printer configured in /etc/printcap, lpc may be used to: o disable or enable a printer, o disable or enable a printer's spooling queue, o rearrange the order of jobs in a spooling queue, o find the status of printers, and their associated spooling queues and printer daemons. Without any arguments, lpc will prompt for commands from the standard input. If arguments are supplied, lpc interprets the first argument as a command and the remaining arguments as parameters to the command. The standard input may be redirected causing lpc to read commands from file. Commands may be abbreviated; the following is the list of recognized commands. ? [command ...] help [command ...] Print a short description of each command specified in the argument list, or, if no argument is given, a list of the recognized com- mands. abort { all | printer } Terminate an active spooling daemon on the local host immediately and then disable printing (preventing new daemons from being started by lpr(1)) for the specified printers. clean { all | printer } Remove any temporary files, data files, and control files that cannot be printed (i.e., do not form a complete printer job) from the specified printer queue(s) on the local machine. disable { all | printer } Turn the specified printer queues off. This prevents new printer jobs from being entered into the queue by lpr(1). down { all | printer } message ... Turn the specified printer queue off, disable printing and put message in the printer status file. The message doesn't need to be quoted, the remaining arguments are treated like echo(1). This is normally used to take a printer down and let others know why lpq(1) will indicate the printer is down and print the status message. enable { all | printer } Enable spooling on the local queue for the listed printers. This will allow lpr(1) to put new jobs in the spool queue. exit quit Exit from lpc. restart { all | printer } Attempt to start a new printer daemon. This is useful when some abnormal condition causes the daemon to die unexpectedly, leaving jobs in the queue. lpq(1) will report that there is no daemon present when this condition occurs. If the user is the super-user, try to abort the current daemon first (i.e., kill and restart a stuck daemon). start { all | printer } Enable printing and start a spooling daemon for the listed printers. status { all | printer } Display the status of daemons and queues on the local machine. stop { all | printer } Stop a spooling daemon after the current job completes and disable printing. topq printer [ jobnum ... ] [ user ... ] Place the jobs in the order listed at the top of the printer queue. up { all | printer } Enable everything and start a new printer daemon. Undoes the effects of down. FILES
/etc/printcap printer description file /var/spool/output/* spool directories /var/spool/output/*/lock lock file for queue control DIAGNOSTICS
?Ambiguous command abbreviation matches more than one command ?Invalid command no match was found ?Privileged command you must be a member of group "operator" or root to execute this command SEE ALSO
lpq(1), lpr(1), lprm(1), printcap(5), lpd(8) HISTORY
The lpc command appeared in 4.2BSD. BSD
April 28, 1995 BSD
All times are GMT -4. The time now is 06:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy