In message <[EMAIL PROTECTED]>, you w rote: >2008/8/10 Thomas Adam <[EMAIL PROTECTED]>: >> http://edulinux.homeunix.org/~n6tadam/fvwm2rc-ronald
Did you send me mail with this link before now?? I must have mised it entirely for some reason. >So I am curious to know if this is OK -- or not. Some feedback from >you, Ronald, if not from common courtesy would be the least you could >do. Um... I apologize. I got seriously side-tracked. I've had more hardware problems, in addition to the ones that caused me to go and buy a new machine and try to install a fresh(er) version of FreeBSD on it at the same time (and then update all of my other stuff, including fvwm). But really, I have no excuse other than the fact that I just didn't feel that I had the time right now to learn what I needed to learn to make a go of things with fvwm2. (The good news is that it's terrifically sophisticated. The bad news is that it's terrifically sophisticated. :-) So anyway, I felt the need to get on to doing other things... like the suddenly critical task of upgrading, at long last, to BIND9 so as to avoid the widely predicted instant and horrible death... and so I put this (fvwm upgrade) on the back burner and just installed fvwm 1.24 on FreeBSD 7.0. I even had to tweek a few things in order to get even that to work, but all is essentially back to normal for me now. I did learn a few things in the process, and my old .fvwmrc file has in fact been tweeked by me a fair amount now. (I never really knew much about what was going on in there, but now I do have a better understanding, especially on the topic of why the startup of sub-thingies should really be done in the .fvwmrc file and _not_in my .xinitrc file.) Anyway, thank you, everybody, for all of the e-mails you sent about my attempt at upgrading. I really did save them all in my inbox with the hopes of getting back to that project someday. But you know the old saying... life is what happens while you are making other plans. (I really need an assistant here who could do the care and feeding of all of my machines and the routine software upgrades. Sigh. But I have no money for that, and it's just me, so I'm stuck trying to juggle every- thing.)
