Re: runsocks (Was Re: gpib driver - does anybody use it?)
: Yeah, this doesn't comple for some reason as of about 1.0r4. The port just : doesn't bother trying to install it - no-one's cared enough to look at why : it's broken and how to fix it. It is broken because it assume too many implementation details about symbols being defined. A more accurate description would be that no one has cared enough to actually fix it. :-) This seems to me to be a perfect use for netgraph: a socks based interface in the kernel so that applications didn't need to be brutalized to work with socks. Hee hee hee... Would this be a transparent socksy? Terry Lambert te...@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: runsocks (Was Re: gpib driver - does anybody use it?)
In message pine.osf.4.05.9902101658550.21416-100...@mercury.physics.adelaide.edu.au Kris Kennaway writes: : runsocks works fine for me in socksifying the stuff I use it for : (FTP clients, simple TCP apps, etc). What are you having problems : with? I have verified that runsocks works with both a.out and elf binaries (but not both at the same time) with the most current port. It does not work for statically linked binaries. Anything outside of that are that isn't pilot error is a bug that I'd be interested in... Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: runsocks (Was Re: gpib driver - does anybody use it?)
In message 19990210135902.a7...@internal Andre Albsmeier writes: : Hmm, just finished my 3.1 upgrade, compiled socks and runsocks seems : to work now. The only thing that doesn't work is compiling the telnet : included with socks5: : : cc -I. -I../../include -I./../../include -O -pipe -DANDRE -D__USE_FIXED_PROTOTYPES__ -DHAVE_SETUPTERM -DSOCKS -DINCLUDE_PROTOTYPES -DKLUDGELINEMODE -DSOCKS -DINCLUDE_PROTOTYPES -o telnet authenc.o commands.o main.o network.o ring.o sys_bsd.o telnet.o terminal.o tn3270.o utilities.o -L../../lib -lsocks5 -lcrypt -lncurses -Llibtelnet -ltelnet : telnet.o: In function `gettermname': : telnet.o(.text+0x9f2): undefined reference to `ttytype' : *** Error code 1 (continuing) : `all' not remade because of errors. : : But this doesn't bother me because always I runsocks the FreeBSD telnet. : : Anyway, I will keep on experimenting on my home machine (where it failed : yesterday) and look what happened. Maybe it was just to late in the evening Ah yes. the telnet bug. I had forgotten about that one. I'll try to fix it shortly. In fact, most of the r utilities that socks creates could likely be better integrated with FreeBSD's commands. I'll look into how hard that would be. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: runsocks (Was Re: gpib driver - does anybody use it?)
In message pine.osf.4.05.9902120002140.29581-100...@mercury.physics.adelaide.edu.au Kris Kennaway writes: : Yeah, this doesn't comple for some reason as of about 1.0r4. The port just : doesn't bother trying to install it - no-one's cared enough to look at why : it's broken and how to fix it. It is broken because it assume too many implementation details about symbols being defined. A more accurate description would be that no one has cared enough to actually fix it. :-) Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: runsocks (Was Re: gpib driver - does anybody use it?)
On Tue, 16-Feb-1999 at 22:05:05 -0700, Warner Losh wrote: In message pine.osf.4.05.9902101658550.21416-100...@mercury.physics.adelaide.edu.au Kris Kennaway writes: : runsocks works fine for me in socksifying the stuff I use it for : (FTP clients, simple TCP apps, etc). What are you having problems : with? I have verified that runsocks works with both a.out and elf binaries (but not both at the same time) with the most current port. It does not work for statically linked binaries. Anything outside of that are that isn't pilot error is a bug that I'd be interested in... Must have been a pilot error. Now it's working (The first time, I did it very late at night :-)). -Andre Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: runsocks (Was Re: gpib driver - does anybody use it?)
On Wed, 10 Feb 1999, Andre Albsmeier wrote: Hmm, just finished my 3.1 upgrade, compiled socks and runsocks seems to work now. The only thing that doesn't work is compiling the telnet included with socks5: cc -I. -I../../include -I./../../include -O -pipe -DANDRE -D__USE_FIXED_PROTOTYPES__ -DHAVE_SETUPTERM -DSOCKS -DINCLUDE_PROTOTYPES -DKLUDGELINEMODE -DSOCKS -DINCLUDE_PROTOTYPES -o telnet authenc.o commands.o main.o network.o ring.o sys_bsd.o telnet.o terminal.o tn3270.o utilities.o -L../../lib -lsocks5 -lcrypt -lncurses -Llibtelnet -ltelnet telnet.o: In function `gettermname': telnet.o(.text+0x9f2): undefined reference to `ttytype' *** Error code 1 (continuing) `all' not remade because of errors. But this doesn't bother me because always I runsocks the FreeBSD telnet. Yeah, this doesn't comple for some reason as of about 1.0r4. The port just doesn't bother trying to install it - no-one's cared enough to look at why it's broken and how to fix it. Kris - (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: runsocks (Was Re: gpib driver - does anybody use it?)
On Fri, 12-Feb-1999 at 00:04:08 +1030, Kris Kennaway wrote: On Wed, 10 Feb 1999, Andre Albsmeier wrote: Hmm, just finished my 3.1 upgrade, compiled socks and runsocks seems to work now. The only thing that doesn't work is compiling the telnet included with socks5: cc -I. -I../../include -I./../../include -O -pipe -DANDRE -D__USE_FIXED_PROTOTYPES__ -DHAVE_SETUPTERM -DSOCKS -DINCLUDE_PROTOTYPES -DKLUDGELINEMODE -DSOCKS -DINCLUDE_PROTOTYPES -o telnet authenc.o commands.o main.o network.o ring.o sys_bsd.o telnet.o terminal.o tn3270.o utilities.o -L../../lib -lsocks5 -lcrypt -lncurses -Llibtelnet -ltelnet telnet.o: In function `gettermname': telnet.o(.text+0x9f2): undefined reference to `ttytype' *** Error code 1 (continuing) `all' not remade because of errors. But this doesn't bother me because always I runsocks the FreeBSD telnet. Yeah, this doesn't comple for some reason as of about 1.0r4. The port just doesn't bother trying to install it - no-one's cared enough to look at why it's broken and how to fix it. It works with 2.2.x. The problem has something to do with ncurses. In 2.2.x the termcap lib is found by configure. In 3.x, the ncurses is used, IIRC. With the termcap lib, ttytpe can be resolved; with ncurses not. BTW, runsocks works really. I think it was to late at night when I tried it the first time. Don't know what I did wrong ... -Andre Kris - To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: runsocks (Was Re: gpib driver - does anybody use it?)
On Wed, 10-Feb-1999 at 17:01:00 +1030, Kris Kennaway wrote: On Wed, 10 Feb 1999, Andre Albsmeier wrote: 2.2.x for a while. (I have problems using runsocks from the socks5 package, but yet haven't figured out if it's my fault). runsocks works fine for me in socksifying the stuff I use it for (FTP clients, simple TCP apps, etc). What are you having problems with? Hmm, just finished my 3.1 upgrade, compiled socks and runsocks seems to work now. The only thing that doesn't work is compiling the telnet included with socks5: cc -I. -I../../include -I./../../include -O -pipe -DANDRE -D__USE_FIXED_PROTOTYPES__ -DHAVE_SETUPTERM -DSOCKS -DINCLUDE_PROTOTYPES -DKLUDGELINEMODE -DSOCKS -DINCLUDE_PROTOTYPES -o telnet authenc.o commands.o main.o network.o ring.o sys_bsd.o telnet.o terminal.o tn3270.o utilities.o -L../../lib -lsocks5 -lcrypt -lncurses -Llibtelnet -ltelnet telnet.o: In function `gettermname': telnet.o(.text+0x9f2): undefined reference to `ttytype' *** Error code 1 (continuing) `all' not remade because of errors. But this doesn't bother me because always I runsocks the FreeBSD telnet. Anyway, I will keep on experimenting on my home machine (where it failed yesterday) and look what happened. Maybe it was just to late in the evening... Thanks, -Andre To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
runsocks (Was Re: gpib driver - does anybody use it?)
On Wed, 10 Feb 1999, Andre Albsmeier wrote: 2.2.x for a while. (I have problems using runsocks from the socks5 package, but yet haven't figured out if it's my fault). runsocks works fine for me in socksifying the stuff I use it for (FTP clients, simple TCP apps, etc). What are you having problems with? Kris - (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: runsocks (Was Re: gpib driver - does anybody use it?)
On Wed, 10-Feb-1999 at 17:01:00 +1030, Kris Kennaway wrote: On Wed, 10 Feb 1999, Andre Albsmeier wrote: 2.2.x for a while. (I have problems using runsocks from the socks5 package, but yet haven't figured out if it's my fault). runsocks works fine for me in socksifying the stuff I use it for (FTP clients, simple TCP apps, etc). What are you having problems with? interesting, very interesting :-) Please wait a little, I am about to set up a machine here at work with 3.x. I only did it at home before and I compiled socks5 and tried runsocks a got some problems. When I am ready here, I can tell you more. Thanks for your help, -Andre Kris - (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
