February 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [Q] getting the IP address of my machine in lisp ? 26 years, 1 month

SL Baur

Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes in xemacs-beta(a)xemacs.org: > On Linux, why not look at /proc/net/dev? It only tells part of the story? Under Linux 2.0 I see interfaces and statistics, but no IP numbers.

1 participants
0 comments

Re: $PATH bug? 26 years, 1 month

Michael Sperber

>>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: >>>>> "Kyle" == Kyle Jones <kyle_jones(a)wonderworks.com> writes: Kyle> Martin Buchholz writes: >>> They used to live in the same directory, and the old code worked. I >>> veto changing PATH, since this is a user-controlled variable that we >>> should avoid changing if at all possible. Kyle> I don't see how we're going to avoid changing it and still have Kyle> packaged executables be able to execute other packaged executables. Kyle> We're talking about modifying PATH for subprocesses of XEmacs. Kyle> Adding package lib-src directories to PATH makes sense in this Kyle> context, just as modifying TERM makes sense in the content of M-x Kyle> shell and M-x terminal-emulator. I can't see how a package Kyle> author would solve the configuration problem that will Kyle> result if PATH isn't modified. Martin> Sure we could have another way. For example, we could adopt another Martin> environment variable EMACSPACKAGEBINPATH, and our scripts can invoke Martin> other executables using the careful idiom Martin> PATH="${PATH:-/usr/bin:/bin}${EMACSPACKAGEBINPATH:+:$EMACSPACKAGEBINPATH}" other_executable Martin> Do we actually have a documented standard about where in the package Martin> hierarchy executables should go? Martin is absolutely right. In fact, there was a thread on this very same question quite a while ago which sort of died. In fact, the package binaries should not even be appended to EXEC-PATH. If a package wants a binary, it should know what directory to look in, rather than looking in a semi-random global path which might actually include another binary with the same name in front of it. mmencode is a prominent example, where we've avoided problems in the past merely by virtue of the fact that Metamail hasn't changed recently. I intend to hack this in the next Great Path Overhaul which I'll get to once 21.0 is out. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

cygwin current-time problems fixed in latest snapshot 26 years, 1 month

Andy Piper

I've verified that current-time works with the latest cygwin 21.0 snapshot: ftp://sourceware.cygnus.com/pub/cygwin/snapshots/cygwin1-19990216.dll.gz Its probably fixed in earlier snapshots but I haven't bothered to find out. andy

1 participants
0 comments

Re: [Q] getting the IP address of my machine in lisp ? 26 years, 1 month

SL Baur

Glynn Clements <glynn(a)sensei.co.uk> writes in xemacs-beta(a)xemacs.org: > Didier Verna wrote: Glynn> There isn't a system address; addresses are associated with individual Glynn> network interfaces. `(interface-address IFNAME)' would be more Glynn> meaningful. >> >> Or a list of these maybe? At first I thought we could use the call to >> gethostbyname already done in init_system_name, but it doesn't give you >> information on the interface names, right ? > Right. And it will only give you what's listed in the DNS (or NIS, > /etc/hosts etc). It's conceivable that a host has addresses which > aren't listed in any of these. Right. Getting all the IP#s a host is known by is black magic at best. >> Maybe we should just use the output of ifconfig ? (that's what >> ipconfig does in net-utils, I think). > How standard is the format of ifconfig's output? It's not. It's changed radically on Linux in the last few months for that matter. It used to be the default was to list all IP aliases and now it isn't. There also isn't a standard calling convention for it -- `ifconfig' with no parameters fails with a usage message on DEC OSF for example. > OTOH, does anyone know how standard the SIOCGIFCONF and SIOCGIFADDR > ioctl()s are? That might be the best place to start. At least you can detect their presence or absence with configure. > Also, what about IPv6 addresses (or even IPX, DECnet, AppleTalk, ...)? IPv6 numbers are a different size. DECnet uses small integers for node numbers. I don't know about IPX or AppleTalk.

2 participants
1 comments

Re: [Q] getting the IP address of my machine in lisp ? 26 years, 1 month

William M. Perry

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Before we wade into this morass, a question needs to be answered. Is > this worth doing? My opinion so far is that, no, it isn't. > > If it's worth doing, we should probably lift from sendmail's code that > initializes the 'w' class. sendmail is ported to a bunch of platforms > already, so I think a lot of effort would be saved The right way to solve this really depends on _what_ you want to do with the IP address. If you are going to send it across the wire to someone, getting it with ioctl's or ifconfig is completely bogus. You should create a socket, connect to the endpoint, and then do a getsockname(). This will allow things like socks or remote-winsock under windows to give you the correct information to work through the proxy. Didier, why do you want this information to begin with? -Bill P.

1 participants
0 comments

Re: [Q] getting the IP address of my machine in lisp ? 26 years, 1 month

William M. Perry

SL Baur <steve(a)xemacs.org> writes: > Glynn Clements <glynn(a)sensei.co.uk> writes in xemacs-beta(a)xemacs.org: > > > Didier Verna wrote: > Glynn> There isn't a system address; addresses are associated with individual > Glynn> network interfaces. `(interface-address IFNAME)' would be more > Glynn> meaningful. > >> > >> Or a list of these maybe? At first I thought we could use the call to > >> gethostbyname already done in init_system_name, but it doesn't give you > >> information on the interface names, right ? > > > Right. And it will only give you what's listed in the DNS (or NIS, > > /etc/hosts etc). It's conceivable that a host has addresses which > > aren't listed in any of these. > > Right. Getting all the IP#s a host is known by is black magic at > best. > > >> Maybe we should just use the output of ifconfig ? (that's what > >> ipconfig does in net-utils, I think). > > > How standard is the format of ifconfig's output? > > It's not. It's changed radically on Linux in the last few months for > that matter. It used to be the default was to list all IP aliases and > now it isn't. There also isn't a standard calling convention for it -- > `ifconfig' with no parameters fails with a usage message on DEC OSF for > example. 'netstat -i' is much more uniform across platforms. I used this in our perl admin tool for our server before just giving up and using C and ioctls, etc. -bp

2 participants
1 comments

Re: [Q] getting the IP address of my machine in lisp ? 26 years, 1 month

Didier Verna

Glynn Clements writes: Glynn> There isn't a system address; addresses are associated with individual Glynn> network interfaces. `(interface-address IFNAME)' would be more Glynn> meaningful. Or a list of these maybe? At first I thought we could use the call to gethostbyname already done in init_system_name, but it doesn't give you information on the interface names, right ? Maybe we should just use the output of ifconfig ? (that's what ipconfig does in net-utils, I think). -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

2 participants
1 comments

Re: [Q] getting the IP address of my machine in lisp ? 26 years, 1 month

Dmitry Yaitskov

Didier Verna <verna(a)inf.enst.fr> writes: > Glynn Clements writes: > > Glynn> There isn't a system address; addresses are associated with individual > Glynn> network interfaces. `(interface-address IFNAME)' would be more > Glynn> meaningful. > > Or a list of these maybe? At first I thought we could use the call to > gethostbyname already done in init_system_name, but it doesn't give you > information on the interface names, right ? > > Maybe we should just use the output of ifconfig ? (that's what > ipconfig does in net-utils, I think). There is no ifconfig on Windoze systems. There is (at least on NT) an ipconfig, but its output is certainly different from what ifconfig gives... -- Cheers, -Dima.

1 participants
0 comments

Re: [21.0b63] current-time-string is wrong!? 26 years, 1 month

Paul Stodghill

> On Thursday 18 Feb 99, Andy Piper writes: > > I suggest someone tries the latest snapshot dll (easy to pick up from > > sourceware.cygnus.com) first to see if its fixed already. > > > > andy > > I got the 15 Jan 99 snapshot cygwin1.dll. Date header and > display-time work fine now. (And I did eventually find a reference to > this on the cygwin mailing list, on 31 Dec 98.) > > Thanks for solving this for us, Andy. > > Regards, > David As you will (hopefully) see from the headers of this message, the latest cygwin1.dll snapshot fixed the problem for me, too. Thanks!

1 participants
0 comments

[Q] getting the IP address of my machine in lisp ? 26 years, 1 month

Didier Verna

Do we have this already ? If not I'd like to see a system-address function, just as there's a system-name one. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

2 participants
1 comments

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta February 1999