> > > exist, what does this do and should this file be writable (which won't
> > be
> > > possible with a read only file system!)?
> >
> > Eventually you are going to need a ram disk.
> [<Simon Wood>]
> Why ???
> I agree that in a 'PC' type environment you will need disk storage, but
> there are many applications for ELKS that will not...
>
> In this specific case 'init' would need to create a RAM disk for /var before
> it continued booting - seems a suspect way of doing it to me.
Then you will need to do hacking otherwise - unix tools tend to assume disk
scratch space exists.
> And on this line in whinging 'clock' talks directly to hardware (which in my
> case doesn't exist!) - it should be through a clock driver!
No. The clock driver itself would take up valuable permanent space in the
kernel. It means you need the right clock binary for the hardware but it
saves you kernel space. Linux 386 is a bit different but on an 8086 its best
in luser space
> > .S files should go via the C pre processor. .s files dont
> [<Simon Wood>]
> Yep I get the concept, but I can't get it to work :-(, how are the config
> #DEF's passed through Makefile to gcc?? (they certainly don't appear if you
> do 'gcc -dD').
It should be including the config header file.
