OpenEuphoria

Re: OT: CoLinux revisited (was Re: Idea List: #0002)

• Posted by ags <eu at 531pi.co.nz> Feb 06, 2006
• 412 views

Al Getz wrote:
> Perhaps you can tell me what exactly gets corrupted when this problem
> occurs?  Matt had suggested that maybe the problem isnt as bad as it
> sounds so maybe you can explain what happens.  Does the whole drive
> get corrupted (ie the 'fat' record) or just *part* of the drive, or
> just one file that Linux uses, or what, (exactly) ?

Hi Al

It is just the file that (co)Linux uses.  As to how exactly it gets corrupted,
I used the word "scrambled" because even e2fsck can't repair it, and I have
seen e2fsck repair some badly corrupted drives due to power failures.

So yes, it is a file that gets 'corrupted' (in the sense that its contents are
no longer a valid file system image).  

eg:
Say coLinux is in C:\colinux, then colinux-daemon uses it's XML configuration
file to load C:\colinux\root_fs as its drive to boot from.

ie
<block_device index="0" path="\DosDevices\c:\coLinux\root_fs" enabled="true" />

It's that C:\colinux\root_fs file that gets corrupted.  No big loss, unless
you _don't_ have a backup of it   AND it more than likely won't happen if
you stay away from the cofs driver in the release versions :)

Anyway, I'm sure there are colinux forums somewhere.

Oooh, they released another stable version yesterday (6th Feb) 
"Lots of bug fixes"

Gary