|
|
Sponsored Content
Operating Systems
Linux
Fedora
Newby: How to actually update software?!
Post 302868777 by sas on Monday 28th of October 2013 06:37:25 PM
10-28-2013
Thanks a bunch!
I love the Synaptic software (or shd I say "package"
), thanks for leading me down the path to a package manager Bakunin!
What if a package isn't available using apt-get? Then what? Untar and pray tar doesn't get all over the OS (ok bad joke...)...?
I love the Synaptic software (or shd I say "package"
), thanks for leading me down the path to a package manager Bakunin!What if a package isn't available using apt-get? Then what? Untar and pray tar doesn't get all over the OS (ok bad joke...)...?
|
|
3 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am new to using nawk. When I put the following line in script file test1.awk
I get the results:
{ print NR, length($0),NF}
>nawk -f test1.awk head.txt
1 63 5
2 2622 188
3 2166 155
4 3192 228
5 2679 192
.....
but if I modify the test1.awk file to look like this:
BEGIN {FS = ","}... (2 Replies)
Discussion started by: placroix1
2 Replies
2. OS X (Apple)
I need a script that gets the output of softwareupdate -al on each machine (the list of available updates) and reports how many updates are needed in total by all the machines on the network, and the results to 4 different recipients.
i.e.
total patches required = 12
hostname1 =4 patch(es)... (1 Reply)
Discussion started by: glev2005
1 Replies
3. SuSE
Hi,
In SUSE linux, it looks like that I can update the package using YAST or install the package from source. So, which way works better? Also, if i install the package of new version. Do i need to remove/delete the old version package, or I just need to change my environments and keep the old... (0 Replies)
Discussion started by: jianma
0 Replies
LEARN ABOUT OSX
net::server::proto::unix
Net::Server::Proto::UNIX(3) User Contributed Perl Documentation Net::Server::Proto::UNIX(3) NAME
Net::Server::Proto::UNIX - Net::Server UNIX protocol. SYNOPSIS
See Net::Server::Proto. DESCRIPTION
Protocol module for Net::Server. This module implements the UNIX SOCK_STREAM socket type. See Net::Server::Proto. Any sockets created during startup will be chown'ed to the user and group specified in the starup arguments. PARAMETERS
The following paramaters may be specified in addition to normal command line parameters for a Net::Server. See Net::Server for more information on reading arguments. unix_type Can be either SOCK_STREAM or SOCK_DGRAM (default is SOCK_STREAM). This can also be passed on the port line (see Net::Server::Proto). However, this method is deprecated. If you want SOCK_STREAM - just use proto UNIX without any other arguments. If you'd like SOCK_DGRAM, use the new proto UNIXDGRAM. METHODS
NS_unix_path/NS_unix_type In addition to the standard NS_ methods of Net::Server::Proto classes, the UNIX types also have legacy calls to NS_unix_path and NS_unix_type. Since version 2.000, NS_unix_path is simply an alias to NS_port. NS_unix_type is now redundant with NS_proto. These methods were missing between version 2.000 and 2.003 but have been returned as legacy bridges. QUICK PARAMETER LIST
Key Value Default # deprecated UNIX socket parameters unix_type (SOCK_STREAM|SOCK_DGRAM) SOCK_STREAM port "filename" undef # more recent usage port "filename / UNIX" port "filename / UNIXDGRAM" LICENCE
Distributed under the same terms as Net::Server perl v5.16.2 2012-06-06 Net::Server::Proto::UNIX(3)