That seems to be a good initiative. I can check passwd, procps, psmisc if it is ok. /Karl
------------------------------------------------------------------------------- Karl Hammar Aspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57 S-742 94 Östhammar Professional Linux Solutions Sweden +46 70 511 97 84 (mobile) ------------------------------------------------------------------------------- On Tue, 31 Aug 1999, Ian Redfern wrote: > According to http://www.debian.org/y2k/ there are a number of packages (some > Debian-specific) that have nobody willing to state they are year 2000 > compliant. > > Over the weekend I took a look at the source of some of these packages in > slink (the web page seems to only cover hamm). Some of them contain no > executables (e.g. base-files), and many have no date/time-related code in > them. > > I can't see anything that could cause a year 2000 problem in the source of > the following: > > base-files-2.1.0 > base-passwd-2.0.3.3 > bsdutils-4.4.1.1 > debianutils-1.10 > fdflush-1.0.0 > hostname-2.04 > ld.so-1.9.10 > makedev-2.3.1 > modconf-0.2.26 > mount-2.8a > setserial-2.14 > sysklogd-1.3 > sysvinit-2.76 > update-1.3 > > I'm not competent to comment on the assembler in mbr-1.0.0, but a comment in > the code implies it might not be midnight compliant. > > This leaves dialog, dpkg, e2fs-progs, elvis-tiny, kbd, lilo, login, mawk, > modutils, ncurses3.4, passwd, procps, psmisc, syslinux, timezones, > util-linux and whiptail just in base. > > Now, Debian can't be in the business of warranty for Y2K problems (nor can > I!), but the web page could at least indicate if someone has looked at the > code to see if there will be a difficulty. And if there are any, then users > will need patches pretty soon. In particular, nobody else is going to put up > a Y2K statement about debianutils. > > Is anyone else interested in this? Red Hat has been funding black box > testing, but that's expensive and longwinded when you have the source. > > Ian Redfern ([EMAIL PROTECTED]). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
