summaryrefslogtreecommitdiff
path: root/net
diff options
context:
space:
mode:
authorrodent <rodent@pkgsrc.org>2013-04-07 20:49:31 +0000
committerrodent <rodent@pkgsrc.org>2013-04-07 20:49:31 +0000
commit56d0e89eec7a65cd783aaecd29fefde7b20f7a96 (patch)
tree79de035a23bbb285c8713b492fa4fa499634f7f8 /net
parent836f824b7f7339847cc2cb57f6c10401a6122132 (diff)
downloadpkgsrc-56d0e89eec7a65cd783aaecd29fefde7b20f7a96.tar.gz
Edited DESCR in the case of:
File too long (should be no more than 24 lines). Line too long (should be no more than 80 characters). Trailing empty lines. Trailing white-space. Trucated the long files as best as possible while preserving the most info contained in them.
Diffstat (limited to 'net')
-rw-r--r--net/adns/DESCR4
-rw-r--r--net/ether2dns/DESCR2
-rw-r--r--net/kdenetwork4/DESCR1
-rw-r--r--net/kftpgrabber/DESCR6
-rw-r--r--net/mDNSResponder/DESCR17
-rw-r--r--net/wide-dhcpv6/DESCR22
6 files changed, 16 insertions, 36 deletions
diff --git a/net/adns/DESCR b/net/adns/DESCR
index c1b923fbe43..9925a8b165d 100644
--- a/net/adns/DESCR
+++ b/net/adns/DESCR
@@ -21,6 +21,4 @@ library. The adns library has the following features:
environment variables (for setuid programs), disable hostname
syntax sanity checks to return arbitrary data, override or ignore
resolv.conf in favour of supplied configuration, etc.
-* Believed to be correct ! For example, will correctly back off to
- TCP in case of long replies or queries, or to other nameservers if
- several are available. It has sensible handling of bad responses etc.
+...and more!
diff --git a/net/ether2dns/DESCR b/net/ether2dns/DESCR
index 4cb8e39636e..1359b1089f3 100644
--- a/net/ether2dns/DESCR
+++ b/net/ether2dns/DESCR
@@ -1,4 +1,4 @@
-This is a quickie used by me to create IPv6 DNS entries for our
+This is a quickie used by me to create IPv6 DNS entries for our
machines assuming stateless address auto-configuration.
Input format is standard /etc/ethers format.
diff --git a/net/kdenetwork4/DESCR b/net/kdenetwork4/DESCR
index 987d7e7cb84..3925384c65f 100644
--- a/net/kdenetwork4/DESCR
+++ b/net/kdenetwork4/DESCR
@@ -9,4 +9,3 @@ standard KDE environment:
* KPPP: dialer and front end for pppd
* KRDC: a client for Desktop Sharing
* Krfb: Desktop Sharing server, allow others to access your desktop via VNC
-
diff --git a/net/kftpgrabber/DESCR b/net/kftpgrabber/DESCR
index 6085b84f8fd..e7a6e3174c5 100644
--- a/net/kftpgrabber/DESCR
+++ b/net/kftpgrabber/DESCR
@@ -21,8 +21,4 @@ Here are some of the features:
- Encrypted bookmark support (password can be saved to KWallet)
- Distributed FTP support (PRET)
- SSCN and CPSV support
- - Skiplist
- - ZeroConf (aka. Rendezvous) support for local site discovery
- - Bookmark sharing with Kopete contacts (KDE >= 3.3)
- - Bookmark import plugins
- - Support for SFTP protocol [experimental]
+...and more!
diff --git a/net/mDNSResponder/DESCR b/net/mDNSResponder/DESCR
index 33481f81181..e23abd5927a 100644
--- a/net/mDNSResponder/DESCR
+++ b/net/mDNSResponder/DESCR
@@ -1,10 +1,8 @@
-The mDNSResponder project is a component of Bonjour,
-Apple's ease-of-use IP networking initiative:
-<http://developer.apple.com/bonjour/>
+The mDNSResponder project is a component of Bonjour, Apple's ease-of-use IP
+networking initiative: <http://developer.apple.com/bonjour/>
-Apple's Bonjour software derives from the ongoing standardization
-work of the IETF Zero Configuration Networking Working Group:
-<http://zeroconf.org/>
+Apple's Bonjour software derives from the ongoing standardization work of the
+IETF Zero Configuration Networking Working Group: <http://zeroconf.org/>
The Zeroconf Working Group has identified three requirements for Zero
Configuration Networking:
@@ -23,10 +21,3 @@ Requirement 3 is met by DNS Service Discovery (DNS-SD).
Self-assigned link-local address capability has been available since
1998, when it first appeared in Windows '98 and in Mac OS 8.5.
Implementations for other platforms also exist.
-
-The mDNSResponder project allows us to meet requirements 2 and 3.
-It provides the ability for the user to identify hosts using names
-instead of dotted-decimal IP addresses, even if the user doesn't have a
-conventional DNS server set up. It also provides the ability for the
-user to discover what services are being advertised on the network,
-without having to know about them in advance, or configure the machines.
diff --git a/net/wide-dhcpv6/DESCR b/net/wide-dhcpv6/DESCR
index 314ce9fb2e8..2c77c0667e9 100644
--- a/net/wide-dhcpv6/DESCR
+++ b/net/wide-dhcpv6/DESCR
@@ -1,28 +1,24 @@
-WIDE-DHCPv6 is an open-source implementation of Dynamic Host
-Configuration Protocol for IPv6 (DHCPv6) developed by the KAME
-project.
+WIDE-DHCPv6 is an open-source implementation of Dynamic Host Configuration
+Protocol for IPv6 (DHCPv6) developed by the KAME project.
The implementation mainly conforms to the following standards:
- RFC3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
- RFC3319: Dynamic Host Configuration Protocol (DHCPv6) Options
for Session Initiation Protocol (SIP) Servers
-- RFC3633: IPv6 Prefix Options for Dynamic Host Configuration
- Protocol (DHCP)
+- RFC3633: IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP)
- RFC3646: DNS Configuration options for Dynamic Host
Configuration Protocol for IPv6 (DHCPv6)
-- RFC4075: Simple Network Time Protocol (SNTP) Configuration
- Option for DHCPv6
+- RFC4075: Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6
- RFC4242: Information Refresh Time Option for Dynamic Host
Configuration Protocol for IPv6 (DHCPv6)
-All the components of the main protocol are provided, i.e.,
-DHCPv6 clients, servers, and relay agents.
+All the components of the main protocol are provided, i.e., DHCPv6 clients,
+servers, and relay agents. Supported message types are as follows:
-Supported message types are as follows:
Solicit, Advertise, Request, Renew, Rebind, Release, Reply,
Information-request, Relay-forward and Relay-reply.
-Note that the current implementation does not support IPv6
-temporary address allocation by DHCPv6, and there is no plan to
-implement that feature at the moment.
+Note that the current implementation does not support IPv6 temporary address
+allocation by DHCPv6, and there is no plan to implement that feature at the
+moment.