Not sure if this is hashing over old ground, but here is some info
which was forwarded to me about DOC support / Loadable Modules / GPL etc.
> Fireplug (http://www.fireplug.net) has made the DiskOnChip driver into a
loadable module. This
> overcomes the GPL problem of M-System's current driver. The guy in
charge there is: Richard C. Pitt,
> President/CEO ([EMAIL PROTECTED]).
>
> The ThinLinux disk for it is at:
> http://gateway.fireplug.net/M-Systems/
>
> The matching ThinLinux release is at:
> http://gateway.fireplug.net/ThinLinux
>
> Instructions and quick start info is at:
> http://www.thinlinux.org
>
Also there is some interesting DOC information at:
http://www.linuxdevices.com/forum/ in the FAQ area
I think it might be useful to partition the DOC and mount a RO partition
containing the core Linux fs and have a separate RW partition for temp. data
/
state variables. This might go a long way toward eliminating fs corruption
when the systems are power cycled without dismount.
Regards,
Alex Lennon
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED]
Sent: 22 March 2000 18:05
To: Wolfgang Denk
Cc: Bud Wilbur; Warren Postma; [EMAIL PROTECTED]
Subject: Re: any embedded linux distros support disk on chip?
Actually, I don't think you can legally distribute a product that is
already linked to the DOC code. Of course, I do need to throw out the
standard disclaimer that I am not a lawyer. But my understanding from
reading the GPL license is that one can distribute the whole product setup
under the GPL, or one can distribute the seperated items with only the GPL
appltying to the portions already GPLed.
I would guess the way arround this is to have some automated process which
links in the properiatary code at install time. That would appear to be
what is going on with the Lineo distribution as described by others. The
system gets put together on the fly based on the options you choose. Ion
that manner the DOC code would remain seperate until it hit your site. Of
course that would never be a stated reason for doing it that way. The
stated reason would surely be that it allows more flexibility and smaller
code size.
Kirk Wood
[EMAIL PROTECTED]
------------------
Your fly might be open (but don't check it just now).
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
