From: gboutwel <gbo...@pr...> - 2005-02-18 14:54:48
|
Tobias wrote: > I have a 25GB parition and I am able to boot colinux from it. > I had nearly no problem: "cp -ax / /mnt/partition" and starting > with the partition. The only thing that I forgot in the beginning: I did > not copy the /dev/*. Good to know. Maybe I'll remove the item from the wiki. Was any of your partitions logical partitions in the extended partition, where where they all primary partitions? > I use it every day for half a year now (8GB file-image). Since > two weeks ago I had nearly no problem. Since then, I have signs of memory > corruption: CoLinux´s ext3 Filesystem gets damaged, and the whole > Windows System goes crazy step by step. ext3 will get corrupt, especially if coLinux crashes or is shutdown improperly. While this would probably not normally happen, with coLinux/VMWare, etc we are a little at the mercy of when the host OS decides to write out to disk. If we crash or close improperly we could have a situation where the host doesn't get the stuff in memory that needed to go to disk out to disk (for various and lots of reasons). On ext3 that would cause corruption. You might try a better journaling filesystem (such as reiserfs or XFS) > At this point I tried the change from 0.6.1 to 0.6.2 and from a > file-based coLinux to a partition (without severe problems). But > now the ext3 Filesystem on the partition gets damaged. I will check my > hardware (memory and disk), but I think it´s a software problem. (Checking > the corrupted file-system repeatedly corrupted the Windows Host (e.g. > Mozilla had problems with scrolling and with displayin the menu...)). Extermely odd. WIndows Host should not be that affected by coLinux unless it's seriously crashing or causing reboots when being run. > This gave rise to the question: Now that I have the partition, > can´t I use it with real Linux (overcoming the 512 MB -memory limit of > colinux (my machine has 2GB))? Here I ran into problems: Probably because > the /etc/fstab has to be adopted, I could not mount the filesystem. Yes you can install real Linux on the partition, boot into it and have FULL access to all hardware, unlike coLinux which is very limited. Basically if you use 0.6.2, you use alias= in your XML Config file for block_devices to make coLinux treat cobd devices as if they where hd<whatever> or sd<whatever> devices. After you do that you'll probably still need to do 'profiles' to prevent some things from happening in coLinux, that you want happening when running real linux. See the Mailing List Archives for discussions of this stuff. Or maybe someone running an set-up like this can pitch in at this time. > Do you have any pointers on booting coLinux and linux from the > same partition? I just got a thread mailed from a friend. Perhaps this > helps. I could write a wiki page on that... Just the above, if you figure it out and get it working. It would benefit a lot of people if you'd write wiki page about it. George ---------------------------- Love to laugh? Good Clean Jokes at Praize http://www.praize.com/jokes/ |