Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!uunet!mcsun!ukc!edcastle!mfg
From: mfg@castle.ed.ac.uk (M Gordon)
Newsgroups: comp.sys.amiga.tech
Subject: Which directories must be present to boot?
Message-ID: <5962@castle.ed.ac.uk>
Date: 28 Aug 90 08:25:48 GMT
Organization: Edinburgh University Electrical Engineering
Lines: 18

While renaming things to see if the layout of my filesystem could be made to
look more like a UNIX system I discovered a (to my mind) bizarre fact about 
the boot process. If sys:c and sys:libs are not present the boot will start
the drive motor and then hang. If I create sys:c and sys:libs as empty 
directories my startup file is read and I can assign libs: and c: to their
correct places. I can understand the boot not working if sys:s cannot be found
but why does it need sys:c and sys:libs (these are empty directories so I know
it doesn't need to load anything from them before reading the startup file).
Can someone who knows more about what happens at boot time explain what's 
going on?

advaTHANKSnce

-- 
							 _   _   _    _   _	
Michael Gordon - mfg@castle.ed.ac.uk OR ee.ed.ac.uk	| |_| |_| |__| |_| |   
							| . . . .      . . |    
I spilt spot remover on my dog and now he's gone! 	|_________|~~|_____|