From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <775b8d190604041510h368f22aen31067a6e7333c8cc@mail.gmail.com> Date: Wed, 5 Apr 2006 08:10:47 +1000 From: "Bruce Ellis" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] netcat, the only stdin/stdout redirector to tcp/udp conns? In-Reply-To: <4432E333.7070106@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4432C4EA.10204@gmail.com> <4432CA60.6010009@asgaard.homelinux.org> <20060404194312.GA11874@imsa.edu> <4432E333.7070106@gmail.com> Topicbox-Message-UUID: 2eabd6a2-ead1-11e9-9d60-3106f5b1d025 bless bash. that's a disgusting hack. brucee On 4/5/06, Llu=EDs Batlle i Rossell wrote: > Paul Hebble wrote: > > /dev/tcp/host/port > > If host is a valid hostname or Internet > > address, and port is an integer port number > > or service name, bash attempts to open a TCP > > connection to the corresponding socket. > > /dev/udp/host/port > > If host is a valid hostname or Internet > > address, and port is an integer port number > > or service name, bash attempts to open a UDP > > connection to the corresponding socket. > And any other proposal for a listen? I think 'gawk' won't work fine as a > listener, specially for binary files (I'd like not to uuencode/uudecode > the transmission, although it went through my head). > Thanks! > > >