Fixed a y2k bug, several typos, and removes absolute pathnames for
utilities execuded by eftd.sh
This commit is contained in:
parent
eb97c719cb
commit
1a5d75e557
|
@ -1,4 +1,4 @@
|
|||
/* $Id: CHANGES,v 1.8 1999/10/11 21:22:23 he Exp $
|
||||
/* $Id: CHANGES,v 1.9 2000/01/26 20:11:33 he Exp $
|
||||
# Change log for eftp4Linux
|
||||
#
|
||||
# [new] means 'new feature added'
|
||||
|
@ -18,6 +18,15 @@
|
|||
#
|
||||
|
||||
$Log: CHANGES,v $
|
||||
Revision 1.9 2000/01/26 20:11:33 he
|
||||
Fixed a y2k bug, several typos, and removes absolute pathnames for
|
||||
utilities execuded by eftd.sh
|
||||
|
||||
- [fix] fileheader.c: fixed y2k bug (cosmetic, only
|
||||
affected display output of eftp's xdir command).
|
||||
- [chg] eftd.sh.in: utility programs are now located using the
|
||||
standard search PATH rather than by absolute path name.
|
||||
|
||||
Revision 1.8 1999/10/11 21:22:23 he
|
||||
more isdn4k-utils install changes
|
||||
|
||||
|
|
|
@ -65,7 +65,7 @@ make modules_install
|
|||
"make modules_install" is recommended after compilation.
|
||||
|
||||
If your Linux-Distribution comes with a 2.2.x kernel pre-installed, you can
|
||||
additionally do a `make install'. If not, not, you still could do so,
|
||||
additionally do a `make install'. If not, you still could do so,
|
||||
but be aware that this might possibly overwrite your old 2.0.36+
|
||||
kernel which might cause some problems with other parts of your
|
||||
Linux distribution. Therefor, with an old linux distribution, it
|
||||
|
@ -98,13 +98,13 @@ isdn4k-utils
|
|||
|
||||
You need a recent isdnctrl utility (and maybe the loopctrl binary if
|
||||
you want to test locally with the isdnloop driver).
|
||||
You need isdn4k-utils-3.0beta2.tar.gz or newer.
|
||||
You need at least isdn4k-utils-3.0beta2.tar.gz or newer.
|
||||
|
||||
The utilities must be compiled against the 2.2.x
|
||||
kernel headers. The location of that kernel can be set from the
|
||||
isdn4k-utils configuration menu.
|
||||
|
||||
The 3.0beta2 package is availabe from ftp.isdn4linux.de
|
||||
The recent isdn4k-utils package is availabe from ftp.isdn4linux.de.
|
||||
|
||||
|
||||
x25_utils
|
||||
|
@ -142,7 +142,7 @@ in the 'Code maturity level options' menu). People who install
|
|||
eftp4linux for the first time can safely say 'y' to all eurofile
|
||||
config options. After configuration, do a 'make';
|
||||
|
||||
(Execptions: people needing to be paranoid about security might
|
||||
(Exceptions: people needing to be paranoid about security might
|
||||
say 'n' to 'install eftp suid root'. People who already installed
|
||||
a former version of eftp4linux and have installed modified versions
|
||||
of eftp4linux config files might choose to disable overwriting
|
||||
|
@ -159,20 +159,12 @@ non-standard default locations of certain files, you can edit
|
|||
the configure script and change the values of the CONFIG_* variables
|
||||
before.
|
||||
|
||||
The eftd.sh script currently locates certain utilites (e.g. isdnctrl)
|
||||
by full path name. The full path name is figured out at configurataion
|
||||
time. The locations searched for are
|
||||
/usr/local/sbin:/usr/local/bin:/usr/sbin:/sbin:/usr/bin:/bin. If you have
|
||||
installed utilities at an unsusual location, you might want to edit the
|
||||
./configure script before.
|
||||
If you have multiple utility versions installed, make sure that the
|
||||
utility found first is the one just compiled as above (against the
|
||||
(patched) 2.2 kernel header files).
|
||||
|
||||
The directory where the isdn configuration files are located is
|
||||
assumed to be /etc/isdn. If this is not true for your installation,
|
||||
either create that directory or set the environment variable
|
||||
CONFIG_I4LCONFDIR to an alternative directory prior to compilation.
|
||||
(this is usually done automatically if you configure eftp4linuyx my
|
||||
means of the isdn4k-utils config menu).
|
||||
|
||||
As I could not test with all compiler/libc/distribution combinations,
|
||||
maybe I missed something. If configuration should fail or some files
|
||||
|
@ -251,12 +243,22 @@ You can stop EUROFILE service again by
|
|||
|
||||
eftd.sh stop
|
||||
|
||||
The eftd.sh script locates the eftd binary from the
|
||||
installation directory. If you have not done a 'make install' yet
|
||||
and want to test eftd before, you can tell the script to load
|
||||
eftd diretcly from the eftp4linux compilation tree by setting the
|
||||
environment variable EFTD_SH_SRC to a non-empty value before executing
|
||||
the script
|
||||
|
||||
The eftd.sh script locates the eftd binary (as well as all other
|
||||
utility programs) from the stardard PATH environment variable.
|
||||
Thus, make sure that eftd's installation directory (as configured
|
||||
in the isdn4k-utils config menu) is in your PATH environment variable.
|
||||
If you have not done a 'make install' yet and want to test eftd
|
||||
before, just prepend the source directory of eftd to the PATH
|
||||
environment variable.
|
||||
|
||||
People who want to start eftd at boot time from sysvinit and have
|
||||
installed eftd at an unusual location also need to make sure that
|
||||
the PATH as seen by sysvinit contains the appropriate directory
|
||||
|
||||
If you have multiple utility versions installed, make sure that the
|
||||
utility found first is the one just compiled as above (against the
|
||||
[patched] 2.2 kernel header files).
|
||||
|
||||
|
||||
|
||||
|
@ -288,22 +290,3 @@ where USER is your unix login name on your machine and enter your login
|
|||
password when prompted. For this to work, you need the x25_route
|
||||
program from the x25_utils installed and you also must have compiled and
|
||||
installed the isdnloop driver kernel module and the loopctrl utility.
|
||||
|
||||
|
||||
There is also an old script "eftp.sh" (this needs to be started from the
|
||||
root user, but the script does a 'cd /tmp' and changes the uid before
|
||||
the client is executed)
|
||||
|
||||
eftp.sh ISDN_NUMBER [USER/PASSWD]
|
||||
|
||||
in order to start an EUROFILE client and connect to a remote eft server.
|
||||
|
||||
Note that typing the password on the command line is not safe if
|
||||
your system is shared with other users who might spoof your password
|
||||
with the ps command. It also leaves traces in your command history file.
|
||||
|
||||
The old script supports connecting to your own server on top of the
|
||||
isdnloop driver (no paying isdn connection involved) by
|
||||
|
||||
eftp.sh localhost [USER/PASSWD]
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
$Id: README,v 1.6 1999/10/24 21:35:42 he Exp $
|
||||
$Id: README,v 1.7 2000/01/26 20:11:33 he Exp $
|
||||
|
||||
README file for eftp4linux
|
||||
==========================
|
||||
|
@ -119,8 +119,8 @@ In addition to the files contained in this distribution, you will need
|
|||
loopctrl, if you want to test locally by means of the isdnloop driver).
|
||||
The isdn4k-utils-3.0beta2.tar.gz. (or newer) are fine.
|
||||
|
||||
isdnctrl.c must be compiled against 2.1.x kernel header files.
|
||||
The 3.0beta2 package is availabe from ftp.franken.de
|
||||
isdnctrl.c must be compiled against 2.2.x kernel header files.
|
||||
The most recent isdn4k-utils package is availabe from ftp.isdn4linux.de
|
||||
|
||||
You can also use an even newer isdn4k-util snapshot from isdn4linux
|
||||
CVS server. See the isdn4linux FAQ for info about this.
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
$Id: FAQ,v 1.3 1999/08/28 16:35:05 he Exp $
|
||||
$Id: FAQ,v 1.4 2000/01/26 20:11:33 he Exp $
|
||||
|
||||
QUESTION: How can I control the amount of debugging output?
|
||||
=========
|
||||
|
@ -26,8 +26,8 @@ QUESTION: I don't want anonymous users to dial in without a MSN
|
|||
If a client without a MSN dials in, the ISDN number 0 is assumed.
|
||||
With the line "guestservers 1* 2* 3* 4* 5* 6* 7* 8* 9*" in
|
||||
/etc/isdn/eftaccess connections with ISDN numbers beginning with
|
||||
"0" are refused. Don't forget the option "-a" for eftd to make him
|
||||
the file /etc/isdn/eftaccess used.
|
||||
"0" are refused. Don't forget the option "-a" for eftd to let is use
|
||||
the file /etc/isdn/eftaccess.
|
||||
(What's about international connections then? Do they begin with "0"?
|
||||
I dont'n know, never had one...)
|
||||
|
||||
|
@ -67,9 +67,6 @@ x25trace) is activated, additional computation time is required.
|
|||
If certain protocol parameters (in particular X.25 or eurofile window
|
||||
sizes of one) are in effect, transfer speed might also decrease.
|
||||
Other additional delays, such as waiting for disk or NFS IO or
|
||||
waiting for beeing schedules on a heavy loaded system, might also
|
||||
waiting for beeing scheduled on a heavily loaded system, might also
|
||||
decrease the transfer speed.
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
$Id: design.txt,v 1.1 1999/06/30 16:51:01 he Exp $
|
||||
$Id: design.txt,v 1.2 2000/01/26 20:11:33 he Exp $
|
||||
|
||||
This document is to briefly intruduce the EUROFILE protocol stack
|
||||
and to document the design of the eftp4linux EUROFILE implementation.
|
||||
|
@ -37,8 +37,8 @@ This document serves two purposes:
|
|||
with EFT related protocols and (isdn4)linux internals you can goto 3.0
|
||||
right away and submit your comments.
|
||||
|
||||
- It also givea an introduction on EFT, and ideas how it was
|
||||
implemented in linux. Since it took quite some time for me
|
||||
- It also gives an introduction on EFT, and ideas how it was
|
||||
implemented in Linux. Since it took quite some time for me
|
||||
to gather all the information related to EFT, I decided to write an
|
||||
introduction as the initial task of the linux EFT project. That
|
||||
introduction was also a good base for documentation.
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
#!/bin/sh
|
||||
# @configure_input@
|
||||
#
|
||||
# generated from $Id: eftd.sh.in,v 1.6 1999/10/08 16:25:35 he Exp $
|
||||
# generated from $Id: eftd.sh.in,v 1.7 2000/01/26 20:11:34 he Exp $
|
||||
#
|
||||
# Henner Eisen 1998
|
||||
#
|
||||
|
@ -15,10 +15,6 @@
|
|||
# This script can be called from sysvinit, but be sure that the common
|
||||
# isdn setup below is done before.
|
||||
#
|
||||
# By default, the script executes the eftd binary from the installation
|
||||
# directory @SBINDIR@/. However, if the environment variable $EFTD_SH_SRC
|
||||
# is set to a non-empty value, it loads the binary directly from the
|
||||
# eftp4linux source directory @EFT_TOPDIR@/src/eftd/
|
||||
#
|
||||
# READ and EDIT this script before using it!
|
||||
#
|
||||
|
@ -41,32 +37,21 @@
|
|||
|
||||
# Location of a recent isdnctrl binary that supports the x25 features
|
||||
#
|
||||
ISDNCTRL=@ISDNCTRL@
|
||||
ISDNCTRL=isdnctrl
|
||||
|
||||
# Location of the loopctrl binary from the isdn4k-util package
|
||||
#
|
||||
LOOPCTRL=@LOOPCTRL@
|
||||
INSMOD=@INSMOD@
|
||||
EFTD_BIN_SRC=@EFT_TOPDIR@/src/eftd/eftd
|
||||
EFTD_BIN_INSTALL=@SBINDIR@/eftd
|
||||
|
||||
if [ -z "$EFTD_SH_SRC" ]; then
|
||||
EFTD_BIN=$EFTD_BIN_INSTALL
|
||||
else
|
||||
EFTD_BIN=$EFTD_BIN_SRC
|
||||
fi
|
||||
|
||||
LOOPCTRL=loopctrl
|
||||
INSMOD=insmod
|
||||
EFTD_BIN=eftd
|
||||
|
||||
# Where to put the eftd-pid-file? Default is /var/run/eftd.pid.
|
||||
EFTD_PIDFILE=@RUNDIR@/eftd.pid
|
||||
|
||||
X25TRACE_PIDFILE=@RUNDIR@/x25trace.pid
|
||||
|
||||
#KHOME=/home/kernel
|
||||
#X25UTIL=$KHOME/util/x25/x25-utils-2.1.20
|
||||
#X25TRACE=$X25UTIL/trace/x25trace
|
||||
X25TRACE=@X25TRACE@
|
||||
X25ROUTE=@X25ROUTE@
|
||||
X25TRACE=x25trace
|
||||
X25ROUTE=x25route
|
||||
|
||||
|
||||
# The MSN (without your local area code) where eftd shall listen for
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
/* $Id: fileheader.c,v 1.2 1999/10/06 18:16:22 he Exp $ */
|
||||
/* $Id: fileheader.c,v 1.3 2000/01/26 20:11:34 he Exp $ */
|
||||
/*
|
||||
Copyright 1998 by Henner Eisen
|
||||
|
||||
|
@ -214,17 +214,28 @@ oflow:
|
|||
* Parse an ETS 300-075 file header encoded time string and return
|
||||
* the equivalent unix epoche time_t type;
|
||||
*
|
||||
* FIXME: (or better fix ETS protocol :-) this is not y2k safe due to
|
||||
* limititations in ETSI protocol.
|
||||
*/
|
||||
static time_t fh2timet(unsigned char *ts, int len){
|
||||
int tmp;
|
||||
struct tm t={0,0,0,0,0,0,0,0,0,0};
|
||||
/*
|
||||
* FIXME: (or better fix ETS protocol :-) this is not y2k safe due to
|
||||
* limititations in ETSI protocol.
|
||||
*
|
||||
* The window boundary is chosen arbitrarily because I
|
||||
* currently don't know of any official ETSI recommendation.
|
||||
*
|
||||
* This should be changed as soon as an official value
|
||||
* agreed among all EUROFILE implementors is recommended.
|
||||
*/
|
||||
int y2k_wrap=70;
|
||||
|
||||
if(len>1){
|
||||
tmp = 10*(ts[0]-'0') + (ts[1]-'0');
|
||||
ts +=2;
|
||||
len-=2;
|
||||
/* y2k compatibilty hack */
|
||||
if( tmp < y2k_wrap ) tmp += 100;
|
||||
t.tm_year = tmp;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue