From 73237de3761836016f67a10121ecc97a5d45cac4 Mon Sep 17 00:00:00 2001 From: Ulrich Drepper Date: Thu, 9 Apr 1998 10:14:17 +0000 Subject: Update. 1998-04-08 Andreas Schwab * configure.in: Add new option --enable-force-install. Substitute force_install. * config.make.in (force-install): Set from configure. * Makerules (force-install): New phony target. * Makeconfig (+force): New variable. * Makefile: Use it in dependency list of installation targets. * db/Makefile: Likewise. * db2/Makefile: Likewise. * elf/Makefile: Likewise. * hurd/Makefile: Likewise. * iconv/Makefile: Likewise. * iconvdata/Makefile: Likewise. * intl/Makefile: Likewise. * localedata/Makefile: Likewise. * login/Makefile: Likewise. * po/Makefile: Likewise. * sunrpc/Makefile: Likewise. * sysdeps/mach/hurd/Makefile: Likewise. * sysdeps/standalone/i386/force_cpu386/Makefile: Likewise. * sysdeps/unix/sysv/linux/Makefile: Likewise. * timezone/Makefile: Likewise. 1998-04-08 Andreas Schwab * sysdeps/unix/sysv/linux/getcwd.c: Use PATH_MAX as default alloc_size. Pass return value of getcwd syscall to realloc. 1998-04-08 Andreas Schwab * manual/socket.texi: Spelling fixes. 1998-04-08 Andreas Schwab * elf/dl-load.c (print_search_path): Remove unused variable. --- FAQ.in | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) (limited to 'FAQ.in') diff --git a/FAQ.in b/FAQ.in index aee939d..adda0fb 100644 --- a/FAQ.in +++ b/FAQ.in @@ -945,6 +945,31 @@ Also, make sure you have a suitably recent kernel. As of the 970401 snapshot, according to Philip Blundell , the required kernel version is at least 2.1.30. +?? When I set the timezone I'm by setting the TZ environment variable + to EST5EDT things go wrong since glibc computes the wrong time + from this information. + +{UD} The problem is that people still use the braindamaged POSIX +method to select the timezone using the TZ environment variable with a +format EST5EDT or whatever. People, read the POSIX standard, the +implemented behaviour is correct! What you see is in fact the result +of the decisions made while POSIX.1 was created. We've only +implemented the handling of TZ this way to be POSIX compliant. It is +not really meant to be used. + +The alternative approach to handle timezones which is implemented is +the correct one to use: use the timezone database. This avoids all +the problems the POSIX method has plus it is much easier to use. +Simply run the tzselect shell script, answer the question and use the +name printed in the end by making a symlink to +/usr/share/zoneinfo/NAME (NAME is the returned value from tzselect) +from the file /etc/localtime. That's all. You never again have to +worry. + +So, please avoid sending bug reports about time related problems if +you use the POSIX method and you have not verified something is really +broken by reading the POSIX standards. + Answers were given by: {UD} Ulrich Drepper, -- cgit v1.1