aftermath

[hugme]

Ok, so I have been working on my computer trying to get it up, I was not sure what happened at first because the harddrive seemed to be working fine, however the CDrom is dead. I got FreeBSD installed, X installed and working on all 5 monitors. I still couldn't get windowmaker installed so I started using Enlightenment. I HATE enlightenment, can you believe 21meg of memory, PER HEAD!!! this is a 5 head box, so 105 meg of memory is being used just to run the fucking windowmanager.I started really playing with it and figured out how I cound get windowmaker working, just force it to run on each head seperatly and it worked!! I just checked it, winodmaker takes up 4 meg of memory.. E is just a fucking hog

This got me thinking, if I can control direction like that, what is to stop me from running multiple windowmanagers... so now I am running E on 3 screens and windowmaker on 2. just wanted to see if I could do it. I can... in the mits of all of this I found out this drive is about gone, when I am doing heavy reads and writes it will lock the entire machine up. so it looks like I am going to need a new harddrive... grrrr I don't know how I am going to swing that one. I will look through my stuff, maybe I can put several drives in this box and do a software stripe.. hmmm

anyway, I am going to write help files for how you do all this crap sometime in the future... it's a pretty cool setup. there are some bugs I am going to have to work out, like the windowmaker boxes and the freaky thing E is doing where it opens your program in the wrong window.

either way, it's 4:40 in the morning, I am off to bed....nite!!

Comments

e opening in wrong window

[tgrey.livejournal.com]

just a thought on that enlightenment. try moving it to the desktop you want it on, then "remember" it's desktop...

Re: e opening in wrong window

[hugs.livejournal.com]

that's not the problem. with xinerama I have found that it's best to 'direct' each windowmanager to where it needs to be, with enlightenment even if you direct it it still tries to take over the other heads, it will drop an error on heads that are not running E and it will run E automaticly on any head you don't have a windowmanager pointed to. (this is a pain in the ass) if a primary head takes over a secoundary head when you go to run something on the secoundary if you don't direct it it will run on the primary.

are you confused yet? I am the one who had to figure this shit out and try and fix it... right now I am not running E at all, it is too much of a memory hog and it's too hard to control. I feel like I am working with windows.