Re: file

["christer solstrand johannessen" <csj@csj.no>]

> > just checked the /etc/magic, and it is, unfortunately, a plain
> > text file as you specified. darn. :/
> Better make sure that /etc/magic is the file that file(1) is
> reading.
>     # mv /etc/magic /etc/magic.save
>     # file
>     file: couldn't find any magic files!
> And then put it back:
>     # mv /etc/magic.save /etc/magic
> And also try
>     # file -m /etc/magic
> to specify the "magic" file to use.

done, with the same results as you got. when specifying

  # file -m /etc/magic

i got the same result as i did initially; same when i run it
with no parameters.

> Could you also try a
>
>     # ls -l /etc/magic

  # ls -l /etc/magic
  -r--r--r--    1 root     bin        391795 May 31 17:50 /etc/magic

> and what does
>
>     # head /etc/magic
>
> say?

  # head /etc/magic
  # Magic
  #       $OpenBSD: Header,v 1.5 1997/04/03 17:39:38 kstailey Exp $

  # Magic data for file(1) command.
  # Machine-genererated from src/usr.bin/file/magdir/*; edit there only!
  # Format is described in magic(files), where:
  # files is 4 on V7 and BSD, 4 on SV, and ?? in the SVID.

#-----------------------------------------------------------------------
-------
  # Localstuff:  file(1) magic for locally observed files
  #

> The other check to make, as posted by someone else, is to make
> sure you're running the right file(1):
>
>     # whence file
>     /usr/bin/file

  # which file
  /usr/bin/file

>     # head `whence file`
>     (garbage)

  # head `which file`

  P Uåì
       WVSu~ÁàD8£ìf^Ût&Äøj/Sè%£,bÄÀu
,bë@£,bÇEü`EüEüÀtÄôh`èÈÄìÿ5ìfWÿ6èPèÚOYXQÍQrøÿÿÿÿÃ/usr/libexec/ld.soNo
ld.so
  Failure reading ld.so
  Bad magic: ld.so
  Cannot map ld.so
  crt0: update /usr/libexec/ld.so
  ld.so failed
  Uåì,WVSÇ°e±jjh±jè,ÿÿÿ£eÄøÿu8xuǼeéÚj
  hÄjjèöþÿÿÄøjjèêþÿÿÄ j EàPÿ5ejèÔþÿÿÄøwjhÎjjè¼þÿÿÄøjjè°þÿÿÄ
Eà©ÿÿtfÁÁÈfÁf=


> > > Don't know how you managed to do that, though.
> > me neither... i built a "custom" generic kernel (reboot) and new
> > userland (reboot again), made a /home/newroot and applied the
> > appropriate changes to /etc, /var and /dev, and had another reboot.
> It does sound like something strange has happened with /etc.

yes... now that you mention that, i recall i had a problem with
/etc/syslog.conf being all garbage and had to be replaced after
i had upgraded from 3.1-stable to 3.1-current... think i'll try
and replace the /etc/magic file from a snapshot binary set, and
if that fails, i'll try another userland build.

> > then i went on holidays for a weekend, leaving the machine off
> > while i was away. no need for power consumption when the machine
> > can't be used. when i got back i left the fans disconnected, and
> > hit the on switch, monitor and keyboard attached, and the machine
> > beep'ed its joyful "I'M ALIVE!" boot beep. then i just turned it
> > off again, installed the new power unit, removed the fans from the
> > case and booted it again. it's been up for almost a week now, no
> > problems, except the file incident.
> >
> > do you see any clues here that i might have missed out of
frustration?
> >
> > dmesg available if necessary.
> I don't see that it could be a hardware related problem, except...
> is there a problem with your / partition?  How about fsck-ing /?

i've had no problems except for unclean unmounts when the machine
froze during the fans-in/fans-out test period, but i never switched
the machine off when there was any disk activity.

i even put it into single user mode to force a fsck just to be sure
that everything was shipshape, and it was. latest reports say that
the file systems are clean.

--
christer - csj@csj.no
"when i grow up, i'll be stable."