Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!cs.mu.OZ.AU!summer
From: summer@ee.mu.OZ.AU (Mark Summerfield)
Subject: File System Problem
Message-ID: <9313109.20413@mulga.cs.mu.OZ.AU>
Sender: news@cs.mu.OZ.AU
Organization: Dept of Electrical & Electronic Engineering, University of Melbourne
Date: Mon, 10 May 1993 23:09:12 GMT
Lines: 33
I experienced a strange bug this morning, which I think is probably a file
system problem. I also suspect it's a known problem (i.e. a "feature" :-)
but I'd like to be enlightened.
Here's the situation (I'm working with 386BSD 0.1 + pk 0.2.2, and the original
compiler and stuff):
I'm compiling a library I'm working on. The source files and the header
files are all in the current directory. However, so that programs using
the library can have access to the header files, there are also symlinks
to some of the headers in $HOME/include. -I$HOME/include is used for
all compilation.
If a source file uses #include "header.h" (so that the header is accessed
directly in the current directory) everything is OK. However, if I use
#include <header.h> the symlink in $HOME/include is referred to (at least,
I assume that's the difference). This seems to cause the contents of the
header file to be destroyed and replaced with junk. This happens even if
I don't have write access to the file enabled. The directory entry is
unchanged by this process -- only the contents are trashed. It doesn't
happen *every* time, just most of the time.
Anybody know why?
Mark.
--------------------------------------------------------
Mark Summerfield, Photonics Research Laboratory
Department of Electrical and Electronic Engineering, University of Melbourne
ACSnet[AARN/Internet]: summer@ee.mu.oz[.au]
--------------------------------------------------------
library, n., a place with a large number of people, a slightly larger number
of books, and a very small number of photocopiers, of which at any given
time at least 50% will be out of order.