I'm fiddling about with a PCI based ARM system (Integrator, it's
just gone on sale). I'm booting a system with a ROMFS sat in flash
(with a simple device driver that can find the file system in flash and
read it's blocks).
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
shell, but I'd like a more viable longer term solution. Long term I'd
like to boot a system that uses a RAM disk for the writable files (eg
log files etc).
Any help appreciated.
Dave
ps PCI subsystem looks very good, it can find/recognise SCSI disks
and their partitions as well as a 21x4x ethernet device...
----------------------------------------------------------------------
David A Rusling Consulting Engineer
ARM Limited
Liberty House,
Moorbridge Road,
Maidenhead, SL6 8LT
Tel: UK-(0)1628-427754
Fax: UK-(0)1628-780551
e-mail: [EMAIL PROTECTED]
----------------------------------------------------------------------
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
