uubp(1c) [debian man page]

uubp(1C)																  uubp(1C)

NAME

       uubp - Unix-to-Unix beer protocol

SYNOPSIS

       uubp [-acefghlqy] site

DESCRIPTION

       Uubp  allows the user to transfer beer, ale, or other fermented grain beverages between network sites. Using TCP/IP (telecommunication pro-
       tocol for imbibing pilsners), uubp encodes beer from a local file system into packets suitable for  FTP	(fermentation  transfer  protocol)
       delivery at a remote IP site.

       Example:

       % uubp -c"AMBER" -f0.7 -y0 -q2 198.137.240.100

       The  preceding  example	sends  two six-packs (-q2) of amber ale (-c"AMBER") with a fizziness quotient of 70%, brewed using yeast of type 0
       (saccharomyces cerevisiae) to PI address 198.137.240.100, which is the IP address of the White House.

RESTRICTIONS

       Both source and destination sites must be running uubp-daemon.  In addition, local restriction exist in many areas for  the  transportation
       alkohol across state lines. The Electronic Frontier Foundation is currently involved in litigation to ensure the ability to distribute beer
       through the uubp protocol according to the 21st Amendment. To support the SIG of EFF devoted to this cause, join  the  Homebrewers  of  the
       Electronic  Frontier  Engaged  in  Winning  Electronic  Independence  and  Zeroing  Establishment  Nonsense  (HEFEWEIZEN),  or send mail to
       hefeweizen@eff.eff.org. Be sure to include the entire text of this manual page.

NOTES

       Have a homebrew!

							      Communication Commands							  uubp(1C)

UDP(4P) 																   UDP(4P)

NAME

       udp - Internet User Datagram Protocol

SYNOPSIS

       #include <sys/socket.h>
       #include <netinet/in.h>

       s = socket(AF_INET, SOCK_DGRAM, 0);

DESCRIPTION

       UDP  is	a  simple, unreliable datagram protocol which is used to support the SOCK_DGRAM abstraction for the Internet protocol family.  UDP
       sockets are connectionless, and are normally used with the sendto and recvfrom calls, though the connect(2) call may also be  used  to  fix
       the destination for future packets (in which case the recv(2) or read(2) and send(2) or write(2) system calls may be used).

       UDP  address  formats  are  identical to those used by TCP. In particular UDP provides a port identifier in addition to the normal Internet
       address format.	Note that the UDP port space is separate from the TCP port space (i.e. a UDP port may not be "connected" to a  TCP  port).
       In  addition  broadcast	packets  may be sent (assuming the underlying network supports this) by using a reserved "broadcast address"; this
       address is network interface dependent.

       Options at the IP transport level may be used with UDP; see ip(4P).

DIAGNOSTICS

       A socket operation may fail with one of the following errors returned:

       [EISCONN]      when trying to establish a connection on a socket which already has one, or when trying to send a datagram with the destina-
		      tion address specified and the socket is already connected;

       [ENOTCONN]     when trying to send a datagram, but no destination address is specified, and the socket hasn't been connected;

       [ENOBUFS]      when the system runs out of memory for an internal data structure;

       [EADDRINUSE]   when an attempt is made to create a socket with a port which has already been allocated;

       [EADDRNOTAVAIL]
		      when an attempt is made to create a socket with a network address for which no network interface exists.

SEE ALSO

       getsockopt(2), recv(2), send(2), socket(2), intro(4N), inet(4F), ip(4P)

4.2 Berkeley Distribution					   May 16, 1986 							   UDP(4P)