GusException
Thursday, March 20, 2008
MonoDevelop on Windows
At last, I have the ideal environment, ready for every day use. First, my big problem with my job: I use my laptop to work, and there are very specific software from my work that runs on Windows, and is very heavy, so if I don't want to be frequently stuck, waiting for my disk to stop swapping, had better not to try any virtualization for my job's software. So, I partitioned my machine, Gentoo + Windows. Well, it worked for a while, but soon I realized that I couldn't stay in Gentoo for long tasks, like updating the portage, or even worse: synching, emerging world to see that for any reason lots and lots of packages will require recompilation. That was simply not possible, my job requires immediate attention sometimes, so I left my Gentoo installation unbooted from some time ago. Now of course, it is missing lots of updates and my Gentoo will be usable until an entire weekend downloading and compiling things. Dual booting was a bad decision: after long time of fine-tuning Gentoo and hard work to have all things I need configured in Linux, I don't use it. And now I have a lot of disk space wasted.
In the meantime, I'm testing andLinux, a pretty good integration concept for those who are stuck in Windows for any reason. I don't know well the internals, but it goes something like this: It runs a colinux kernel as a service in Windows, so its not a black-isolated-box concept like the other virtual machines. It shares resources with the host system, then, it is a rather small footprint kernel, which boots in just some seconds.
I've not done any benchmark testing, but for desktop applications it is pretty fast, I don't notice that they are in fact, in separated kernels. I sense it performs just as the real linux kernel :-) And the best of all: You can see and use application windows from both operating systems, as if both were hosted in the same operating system. Obligated screenshot:
In the image, MonoDevelop with a basic demo running. Behind is my Windows Explorer, altough it is wearing an Ubuntu Theme, however it is still noticeable.
For the files, andLinux makes a file, into which are the system files and programs. By now I've not moved my home directory to the real partition I have created for gentoo, but it will be very convenient. I think it may make sense, to expose that files through samba to Windows. I've seen an ext2 driver for Windows once that worked very well, however, it's not a good idea to work on files in the back of one file system driver, being the Windows one the affected, or the Linux one. Anyway, the damage will finally be in the data. The rule of thumb is not to mount the same file system in two kernels for read/write. Exposing the real file system through samba may be fine, unless it proves the contrary.
In the meantime, I'm testing andLinux, a pretty good integration concept for those who are stuck in Windows for any reason. I don't know well the internals, but it goes something like this: It runs a colinux kernel as a service in Windows, so its not a black-isolated-box concept like the other virtual machines. It shares resources with the host system, then, it is a rather small footprint kernel, which boots in just some seconds.
I've not done any benchmark testing, but for desktop applications it is pretty fast, I don't notice that they are in fact, in separated kernels. I sense it performs just as the real linux kernel :-) And the best of all: You can see and use application windows from both operating systems, as if both were hosted in the same operating system. Obligated screenshot:
In the image, MonoDevelop with a basic demo running. Behind is my Windows Explorer, altough it is wearing an Ubuntu Theme, however it is still noticeable.
For the files, andLinux makes a file, into which are the system files and programs. By now I've not moved my home directory to the real partition I have created for gentoo, but it will be very convenient. I think it may make sense, to expose that files through samba to Windows. I've seen an ext2 driver for Windows once that worked very well, however, it's not a good idea to work on files in the back of one file system driver, being the Windows one the affected, or the Linux one. Anyway, the damage will finally be in the data. The rule of thumb is not to mount the same file system in two kernels for read/write. Exposing the real file system through samba may be fine, unless it proves the contrary.
Labels: mono, monodevelop, windows
¶ 2:20 AM
Saturday, March 01, 2008
twittool preview
¶ 5:04 AM
Twitter is becoming a chat, and I don't like to lose messages because high-loads of messages, or because I stopped following people. The web is no more practical for the tons of twitts. Twitter with GTalk keeps flashing all the day and I can't (and don't want to) keep track of every message.
So I'm writing a tool called twittool for helping me out at ordering the Twitter mess. Screenshot:
¶ 5:04 AM
