-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
from the bash manpage:
/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
On Thu, Nov 23, 2006 at 12:30:09PM +0100, Klaus Ethgen wrote:
> For this feature there are several scripts and tools around which use
> this feature. Moreover if you want to make a net boot image where you
> need to contact a other host easy there is no way to do this with debian
> Linux so I have
On Thu, Nov 23, 2006 at 12:30:09PM +0100, Klaus Ethgen wrote:
> Hi all,
>
> from the bash manpage:
> /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
>
On 2006-11-23, Klaus Ethgen wrote:
>
> Hi all,
>
> from the bash manpage:
> /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 op
Hi Klaus,
> >from the bash manpage:
> /dev/tcp/host/port
> /dev/udp/host/port
This has been discussed several times [1][2], and the outcome was every time
that this should not be a feature of the shell, but of more specialized
tools like nc. Use those or recompile your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/23/06 07:09, Jan C. Nordholz wrote:
> Hi Klaus,
>
>> >from the bash manpage:
>> /dev/tcp/host/port
>> /dev/udp/host/port
>
> This has been discussed several times [1][2], and the outcome was every time
> that this sh
Am Donnerstag 23 November 2006 16:42 schrieb Ron Johnson:
> What's the real problem with /dev/{tcp|udp}?
# ls /dev/udp /dev/tcp
ls: /dev/udp: No such file or directory
ls: /dev/tcp: No such file or directory
The chosen method of integration is practical non-sense.
What happens if /dev/tcp is pres
On Thu, 23 Nov 2006 09:42:50 -0600
Ron Johnson <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/23/06 07:09, Jan C. Nordholz wrote:
> > Hi Klaus,
> >
> >> >from the bash manpage:
> >> /dev/tcp/host/port
> >> /dev/udp/host/port
> >
On Thu, Nov 23, 2006 at 02:09:33PM +0100, Jan C. Nordholz wrote:
> Hi Klaus,
>
> > >from the bash manpage:
> > /dev/tcp/host/port
> > /dev/udp/host/port
>
> This has been discussed several times [1][2], and the outcome was every time
> that this should not be a feature
On Thu, Nov 23, 2006 at 22:54:59 +0100, Javier Fernández-Sanguino Peña wrote:
> Then the manpage should be ammended and those things removed. It does not
> make sense to disable things and ship a manpage that implies that they do
> work.
>
Did you look at the bash manpage?
NOTE: Bash, as
Le Thu, Nov 23, 2006 at 02:09:33PM +0100, Jan C. Nordholz a écrit :
> Hi Klaus,
>
> > >from the bash manpage:
> > /dev/tcp/host/port
> > /dev/udp/host/port
>
> This has been discussed several times [1][2], and the outcome was every time
> that this should not be a feat
> "Charles" == Charles Plessy <[EMAIL PROTECTED]> writes:
Charles> I found the following additional discussions in my
Charles> crystal ball:
Charles> http://lists.debian.org/debian-user/2008/09/msg00087.html
Charles> http://lists.debian.org/debian-user/2010/02/msg00295.html
S
On Thu, Nov 23, 2006 at 11:02:15PM +0100, Julien Cristau wrote:
> On Thu, Nov 23, 2006 at 22:54:59 +0100, Javier Fernández-Sanguino Peña wrote:
>
> > Then the manpage should be ammended and those things removed. It does not
> > make sense to disable things and ship a manpage that implies that they
On Thu, Nov 23, 2006 at 09:42:50AM -0600, Ron Johnson wrote:
> What's the real problem with /dev/{tcp|udp}?
My issue with it is having phantom files that only exist in
one shell on the system, could clash with real files
(although that is more or less totally unlikely). I think
that having the she
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/24/06 06:06, Jon Dowland wrote:
> On Thu, Nov 23, 2006 at 09:42:50AM -0600, Ron Johnson wrote:
>> What's the real problem with /dev/{tcp|udp}?
>
> My issue with it is having phantom files that only exist in
> one shell on the system, could clash
On Fri, Nov 24, 2006 at 08:25:27AM -0600, Ron Johnson wrote:
> On 11/24/06 06:06, Jon Dowland wrote:
> > I think that having the shell re-implement netcat to be
> > a violation of "do one thing and do it well".
>
> Hmmm. A large, complicated shell like bash broke that
> stricture long ago, no?
A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/24/06 11:54, Jon Dowland wrote:
> On Fri, Nov 24, 2006 at 08:25:27AM -0600, Ron Johnson wrote:
>> On 11/24/06 06:06, Jon Dowland wrote:
>>> I think that having the shell re-implement netcat to be
>>> a violation of "do one thing and do it well".
On Fri, Nov 24, 2006 at 12:06:09PM +, Jon Dowland wrote:
> I've never came across a script on debian or elsewhere that required
> this functionality enabled. Indeed I'm horrified to find this feature
> enabled on RHEL boxes.
FWIW, ksh93 (as packaged in Debian) has this functionality enabled.
On Fri, 2006-11-24 at 13:12 -0600, Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/24/06 11:54, Jon Dowland wrote:
> > On Fri, Nov 24, 2006 at 08:25:27AM -0600, Ron Johnson wrote:
> >> On 11/24/06 06:06, Jon Dowland wrote:
> >>> I think that having the shell re-imple
On Thu, Nov 23, 2006 at 05:03:13PM +0100, Hendrik Sattler wrote:
# ls /dev/udp /dev/tcp
ls: /dev/udp: No such file or directory
ls: /dev/tcp: No such file or directory
The chosen method of integration is practical non-sense.
What happens if /dev/tcp is present and a character device?
That's mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/06 00:46, Greg Folkert wrote:
> On Fri, 2006-11-24 at 13:12 -0600, Ron Johnson wrote:
>>
>> On 11/24/06 11:54, Jon Dowland wrote:
>>> On Fri, Nov 24, 2006 at 08:25:27AM -0600, Ron Johnson wrote:
On 11/24/06 06:06, Jon Dowland wrote:
[snip
21 matches
Mail list logo
