On Sunday, July 8, 2001, at 06:01  pm, Matthew Theobalds wrote:

>
> On Sunday, July 8, 2001, at 05:44  pm, Frederick Bruckman wrote:
>
>> On Sun, 8 Jul 2001, Matthew Theobalds wrote:
>>
>>> gellum:/sys/arch/mac68k/conf# config gellum
>>> ../../../../arch/m68k/conf/files.m68k:1: cannot open
>>> ../../../../conf/files for reading: No such file or directory
>>>
>>> I get this error even if I do the other method of creating a directory
>>> and renaming the "gellum" file to CONFIG.
>>>
>>> I am clearly missing the directory which is named conf, and with a 
>>> file
>>> named files in it.
>>
>> It's in the sys.tgz tarball in the -current and -release layouts, or
>> in the syssrc.tgz tarball in the official releases, and also with
>> "cvs co -P -d src", or "cvs co -P -d syssrc". Evidently, you've used
>> some other method of getting the sources?
>
> Just occurred to me, I can get just this directory by doing:
>
> 	cvs -P syssrc/sys/conf
>
> from within /usr, right?
>
> (Though I'd check before I try it, then break something even more than 
> now.)

I realised my error and did:

	cvs checkout -P syssrc/sys/conf

then moved the resulting conf directory to /usr/src, which means that 
"/usr/src" now contains: "conf" "sys" "usr.sbin"

So it's definitely there.

Now, I do this:

gellum:/sys/arch/mac68k/conf# config gellum
../../../../arch/m68k/conf/files.m68k:1: cannot open 
../../../../conf/files for reading: No such file or directory

gellum:/sys/arch/mac68k/conf# ls ../../../../conf
CVS                 files               newvers_stand.sh    param.c
defines             newvers.sh          osrelease.sh

Is that really possible?

Very strange indeed.

Regards,

Matthew