Skip to contentSkip to conversation

boot.log (2)

DISCUSSION Jan Willem Stumpel 2 participants 3 messages Jun 27, 2003 – Jun 28, 2003

lore
Share & tools
lore
#0 lore raw

Found my missing boot.log by doing an strace:

strace -omytest -f -e trace=file dosemu

In mytest there is a line

594 open("/tmp/dosemu.qvalfr/boot.log",
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 3

So boot.log is somewhere in /tmp, not in ~/.dosemu -- and it *disappears* when (x)dosemu terminates. That's why I couldn't find it; I can see it in another VC/xterm only while (x)dosemu is still running.

Any idea what could cause this?

Regards, Jan

#1 lore raw
Quoted 9 lines · Jan Willem Stumpel

Found my missing boot.log by doing an strace:

strace -omytest -f -e trace=file dosemu

In mytest there is a line

594 open("/tmp/dosemu.qvalfr/boot.log",
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 3

Quoted 6 lines

So boot.log is somewhere in /tmp, not in ~/.dosemu -- and it *disappears* when (x)dosemu terminates. That's why I couldn't find it; I can see it in another VC/xterm only while (x)dosemu is still running.

Any idea what could cause this?

are you sure that you're not using Debian's dosemu script (ie. /usr/bin/dosemu installed by Debian)? It does:

workdir=$(mktemp -u ${TMPDIR:-/tmp}/dosemu.XXXXXX | tr A-Z a-z)
...
LOG=$workdir/boot.log

which explains what you get. If you use DOSEMU 1.1.x you should be using the supplied dosemu script (which make install puts in /usr/local/bin/ by default)

Bart

#2 lore raw
Quoted 2 lines · Bart Oldeman

are you sure that you're not using Debian's dosemu script (ie. /usr/bin/dosemu installed by Debian)?

Many thanks, this was it. I had a sort of mixed system running which worked in the past but not now. I've now completely undebianized it (I hope).

I've still not got the sound back in Wolf3d (although it works in everything else). Any suggestions welcome. At least I can now produce boot.logs...

Regards, Jan