David Rusling writes:
> > >I'm using init/inittab etc to start up the system. Unfortunately, init
> > >wants to create files and my file system is read only (very read only).
> > >So, for example, it cannot create /dev/initctl and it gets upset. I'm
> > >also seeing some shared library wierdnesses and so I've moved to
> > >a staticly built image. Oh, and the serial driver is half written.
> > >
> > >OK, the question. Is there a brain dead easy init that I can use to
> > >get the system off its knees. I guess the answer is to use a command
> >
> > Sounds like your best bet is to get the source to sysvinit and chop out the
> > bits you don't want. What sort of problem did you have with shared libraries?
I think I wrote this before, but can't remember (too long ago, too much been
happening, and I've been out on business up to Preston)...
If init is trying to create /dev/initctl and such like, it sounds like
something is going very wrong. Since the root filesystem is normally
mounted read only when any Linux system comes up, init can't create
/dev/initctl immediately, or indeed write to any part of the filesystem.
When do you get this error?
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/~rmk/armlinux.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
