fc in the f2c package

ash internal). The second of these is easily fixed (thanks to PMM) but the first and third make me wonder if it should just be removed (and people encouraged to use fort77 which solves the problem in a much more powerful and elegant way). Any comments? Alan Bain -- To UNSUBSCRIBE, email to [EM

Bug#4384: gcc_2.7.2.1-1.deb & g77_0.5.18-2.deb incompatible

I'm planning to do a new release of g77 which will include the gcc source to try and solve this problem. The idea was suggested to me by Joost. The fundamental problem is that g77 requires gcc to be g77 aware, and this changes with the versions of gcc. At the moment I'm not in the best position

Bootfile locations for rbootd?

Rbootd is a remote boot daemon for HP workstations and needs to have a hardcoded directory for storage of the boot file which is served to the workstations (say SYS_UBOOT -- the NetBSD loader). Previously this lived in /export/hp/root but I was thinking this isn't really in line with the FSSTD. W