Not sure why all good engineers seems to be women. I was talking once to a woman who works for Facebook and was involved with PHP, what's her name? She made sense. I don't know. On Mon, 28 Sep 2015, Linda Walsh wrote:
Since it was a Dell machine that was BIOS licensed, Windows came up and thought it wasn't licensed, until I went to the system info page -- when it refreshed the license through the BIOS and re-activated.
BIOS licenses, right! That's how my root kit works :P. You seem to know a lot. Like, a lot lot but I guess I'm just a novice here. Maybe I should go back to school, start over with life and go to primary school again ;-). First attempt fails. Try again.
But new cygwin-64 tools run native and run just fine from a win7-64 repair console, so maintenance that much easier now.
Do you mean you run them from your harddrive after setting up path?
It's not linux, but the unix tools available on linux OR on cygwin64 -- which you can run under win7's repair console.
Buh. Cygwin or not cygwin, I never really liked that. I used GnuWin32 tools but I can't say I have ever really used cygwin, even when I had it installed. Stuff didn't work. I don't know why. I think I had trouble with e.g. slashes in filenames (backslashes). A think I tried to do in cygwin just wouldn't work whereas in Linux it was or would have been easy and flawless. I gave up.
I think pipes (named pipes as well) should in some way remain or be the way of interprocess communciation as well. No matter how it should be implemented, the pipe should be the future.
Not always ideal if you are using multiple processes -- even in linux, it's not possible to do 2-way communication over a pipe -- (pair of pipes, yes, but you can't easily setup 2-way communication between processes in standard shell or bash).
I'm not sure. In principle the concept of a pipe extends beyond one-way and can be multiplexed and all that. I've never done any multi-process or IPC communication myself. Let's say my experience is limited to doing these things in Java with threads. But that's not, that's hardly something you can just create in a short time. Java is not exactly suited for scripting. I also have no perl experience which makes it a bit hard. Cool how you design stuff. I like your designs, but then I already knew that kinda in advance that I would, because I / we agree on so many things. I will need to find out at some point how these things are being done. For now the only machine I use for flac -> mp3 has one core :P :P :P :P (is VPS).
It would have been really painful to try to do that with pipes alone, since they only buffer ~8k/pipe -- would have been alot of overhead in process switching.
Muh, you know 30x as much as I do. I feel... rather jealous really :) hahas. Damn, I thought I would have been more experienced by now. Things didn't really go as intended. That's why I will start over :p :). I can't live with this jealousy all the time.
Shell is good for many things... wrote a first snap-shot generator in shell... but it wasn't fun to maintain or extend, so it went to perl... still not that fun to extend, but at least it was more reliable. Shell doesn't do as good a job handling signals -- especially in bash4.3 where user-signal handlers stopped being asynchronous and are now only handled upon pressing a key in an input line (piss-poor design for use in automation to require user key-presses in order to handle async events (like signals)).
Heh, good to know. I would have writtein it in Java or Python but then I don't even know how these thigns (well, Java) would be able to communicate with "a system". Anyway, thanks for the message. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org