[Novice] Few simple questions on DOC.

[Riipinen Petri]

Great response time...;)

Well, I'd just like to continue with some follow-up questions below. But I
must say that your answers cleared a lot of confusion in my head already
and I'm pretty confident to continue.

> The DiskOnChip driver on the M-Systems website is a different driver. It's
> binary-only, so if you're going to distribute the box you're making, it's
> illegal to link it into the kernel, and it's dubious even whether it's
> legal to use it as a module.

Ok, I'm perfectly happy to forget it then.

> The code in 2.4.7 is slightly out of date - you should update to the latest
> code from CVS which has a couple of useful bug fixes in it.

Are the fixes in 2.4.9? I could just as well update my kernel source tree
anyway and forget 2.4.7 completely, nothing in particular is forcing me to
stay on 2.4.7.

> If you just write the kernel to the beginning of the device, what's going
> to load it? The bootsector built into the kernel is old, probably broken,
> and only designed for use on floppies - I don't think it'll do the job.

Well, hmm... Ok, I assumed that the bootsector included in bzImage works
just as well as it does with floppies and hd. Well, I was really thinking
that I could save some space by not using Lilo/Grub but maybe that's not
worth it then.

And would you recommend Lilo over Grub?

> JFFS doesn't work on it yet.

So ext2 is the most practical choise currently?

Would there be any problems if the user shuts down the SBC when my
application is still writing some data file onto the DOC? I guess those
will be dealt with on boot.

Thanks!

- Petri