[5651] in SIPB bug reports
Re: LaTeX
daemon@ATHENA.MIT.EDU (Jered J Floyd)
Mon Nov 20 11:06:50 1995
Date: Mon, 20 Nov 1995 11:06:20 -0500
From: Jered J Floyd <jered@MIT.EDU>
To: bert@MIT.EDU, bug-sipb@MIT.EDU
First, let me apologize for the tone of my previous message. I wasn't
in a particularly good mood at the time and probably shouldn't have been
composing bug mail.
Regarding xdvi, does that mean that nobody has used xdvi since it had
last been installed? Or had they just not used it on documents with those
fonts? Anyhow, thanks for fixing this.
The TeX problem is more confusing. I compared the straces on two machines,
and they are nearly identical except for:
<<<<<<<
write(1, "This is TeX, Version 3.1415 (C v".., 44This is TeX, Version 3.1415 (C version 6.1)
) = 44
access("./latex.fmt", 04) = -1 (No such file or directory)
stat("/mit/newtex/arch/linux/lib/texmf".., 0xbffff380) = -1 (No such file or directory)
stat("/mit/tex/arch/linux/lib/texmf", 0xbffff380) = -1 (No such file or directory)
write(1, "I can't find the default format ".., 38I can't find the default format file!
) = 38
exit(1) = ?
=======
write(1, "This is TeX, Version 3.1415 (C v".., 44This is TeX, Version 3.1415 (C version 6.1)
) = 44
access("./latex.fmt", 04) = -1 (No such file or directory)
stat("/mit/newtex/arch/i386_linux1/lib".., {dev 1 ff ino 383844359 mode 040700 nlink 2 uid 16256 gid 101 size 2048 ...}) = 0
access("/mit/newtex/arch/i386_linux1/lib".., 04) = 0
stat("/mit/newtex/arch/i386_linux1/lib".., {dev 1 ff ino 383844438 mode 0100644 nlink 1 uid 16256 gid 101 size 502864 ...}) = 0
open("/mit/newtex/arch/i386_linux1/l
<And continues successfully>
>>>>>>>
Both machines have sysnames of 'i386_linux1', and machtypes of 'linux'.
However, the machtype on keesh is an actual binary that responds appropriately
to the different options (I think -S is being used), which the machtype I
have is:
#!/bin/sh
echo linux
exit 0
I'm not certain when this changed, but it would appear that this may be a
problem with many linux systems. Yet another argument for a Linux syspack?
Anyhow, I'm fixing this on machines that I find this borkenness on, sorry
to bother you about that.
--Jered
