home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!ukma!rsg1.er.usgs.gov!darwin.sura.net!convex!news.utdallas.edu!ramesh
- From: ramesh@utdallas.edu (R. Ramesh)
- Subject: 14 char limit and 32 file limit.
- Message-ID: <BxMpCF.GF1@utdallas.edu>
- Sender: usenet@utdallas.edu
- Nntp-Posting-Host: ramesh.utdallas.edu
- Reply-To: ramesh@utdallas.edu
- Organization: The University of Texas at Dallas, ACC
- Date: Fri, 13 Nov 1992 00:29:03 GMT
- Lines: 21
-
- Until now I never really had any serious problem with limit of 32 on open
- files and limit of 14 on filenames (except for aesthetic dissatisfaction). But
- yesterday I had to spend good one hour trying to find a nonexisting bug
- in xdvi and MakeTexPK. I xdvi'ed a file containing my paper. Well this needed
- lcirclew10.300pk which I didn't have so MakeTeXPK fired and tried to make
- that font. First metafont made lcirclew10.300gf and gftopk was called. Because
- of 14char limit gftopk lcirclew10.300gf lcirclew10.300pk failed as it opened
- its input as output and truncated the file (so it found unexpected eof). This
- took 1/2hr. Next Xdvi could not find cmm7.300pk when dvips could (in the
- very same directory). Another half an hour and xdvi -l lists 28 files before
- failing on cmmi7.300pk (with stdin stdout stderr and the dvi file itself this
- totals 32 files).
-
- With MakeTexPK the fault is with kernel (can be removed with efs)
- with xdvi fault is with xdvi itself as it should differentiate between ENOENT
- and EMFILE error.
-
- I thought I would share this so that it saves couple of hours of some one
- else's time.
-
- Ramesh
-