From: Alexander G. <ale...@gm...> - 2005-02-10 15:16:01
|
Hi, as Mr. Krull kindly replied, it appears that w2k supports hardlinks, and perhaps I shall be able to do this setup using just cygwin tools and an ntfs partition. I was so excited to play with colinux, anyway. I tried 0.6.1 with a debian root image, managed to install ubunto on top of it, even compiled kde-3.4beta, this colinux project rocks! > quite sure the technology is able to pass muster. There is the issue > of network performance (I'm sure you've tested this), but this may not Network performance is not an issue. Rsyncing during night time over 10mbit ethernet. > Since your talking about using an ext3 partition for coLinux to access > that your considering using cofs? There has been some notes of cofs > causing data corruption booting directly from ext3 drives, but I am > unsure of general data corruption due to use. The safer solution > (IMHO) would be to use the files on an ntfs drive. I intended to use one of colinux images with a debian root file system, as a boot media and to mount the big raw partion additionally, (perhaps this cofs is the way? got to read the wiki for that). But if you suggest a file - a file it will be! > Again, I would strongly urge that coLinux not be used in a mission > critical environment and a real linux machine would be a much better I know few people, really excited to be able to extend the functionalities of their remote domain controlers with colinux :)) > option! It appears that you are doing almost that anyway (with Cygwin > and now coLinux), so why not just get a Linux machine and work from > there? Budget issues. But this w2k machine is available(it serves as a terminal server at this remote location) and I have the option of adding additional service to it. I will try using just cygwin and ntfs. Best regards A. Georgiev |