However the witches as listed in the defrocked monk's witchfinder's manual never have. It was an excuse to sexually assault widows, murder them and take their stuff with half given to the state to allow the murder to be carried out. Funny how we went from a monk's fantasy of girls rubbing on broomsticks to Harry Potter and Quiddich.
And what's the excuse for still using Exchange 2003
The new version still does not deliver the promised features from ten years ago so why not keep the one with the bigger theoretical feature list:)
To be honest, the 2003 version is far less of a piece of shit than earlier ones. I did a bare metal recovery drill with an earlier version which demonstrated very clearly that it was a shambolic pile of barely communicating different programs as fragile as glass, slow as a dead dog, and only truly reliably backed up with just about all of it shut down. Open relay by default after one patch and some options were only available with registry hacks - it should never have been released in such a state. The only sane way to operate it for only 100 mailboxes was two servers (for when one went down, which happened every couple of weeks due to a memory leak, and for enough speed at peak times) and a real mail transfer agent in between it and the wild internet.
Still running Exchange 2003? Really? That's just straight negligence.
While I agree with that (even the name tells you what should be done with it - swap it with something else) you seem that have missed that "cutting waste" is the way people associated with government services get promoted. Improvements are seen as an unfair burden on the taxpayer. Oddly enough people who talk of "running government like a business" are the first to NOT run it like a business which would see upgrades as spending necessary funds to make improvements that drive better savings/profits in the long run. Instead they try to run it like a doomed business given to the idiot son of the founder of a business.
In the long run having people wait around for their computers instead of working becomes more of a burden to the taxpayer than an upgrade.
the fire left intact for seven hours the circuitry that responds to the satellite pings but nothing else
An inability of other communications systems to operate in no way implies that everything else is out. I suggest applying at least some thought instead of going for such all or nothing bullshit.
It requires a fire powerful enough to disable communications
The pilot does that by throwing breakers to isolate an electrical fire. Apparently that can be done very quickly.
while at the same time avoid detection by a multitude of fire/smoke detectos around the plane
We don't know either way if that was the case or not. All we know is nobody got on the radio to say anything about "a multitude of fire/smoke detectos".
From reading the timeline of events with QF32 after it lost an engine and a lot of control systems, it was some minutes after the engine blew up that they took time to radio in and that was with four pilots on board (two trainers there to do a flight review). They appear to have been a bit busy trying to work out how to stop the situation getting worse in the short term.
Personally I would not use swear words even in these circumstances
Sometimes if you don't then the message does not get through. "There is a 25mm deep crack in the weld that has opened up by 3mm" doesn't get taken seriously by some but "the weld is so fucking cracked that I can stick a fucking ruler into it" conveys the message in uncertain terms. Sadly that is from a real example. The first bit got excuses, fobbed off and "she'll be right" bullshit. The second got the work done again and done properly.
Have you missed Linus' on-going history of verbal abuse?
Go on - list the teapot storms for our entertainment. Do you want to start with the doctor recently turned coder that doesn't even run linux on his main machine that was told he should "eat his own dog food" (which means run his own stuff) before pushing alpha quality scheduling patched on people? That one seemed fair enough to me but I seem to remember you kicking up a fuss.
RedHat, Fedora, Debian, Ubuntu, and Arch have all gone to systemd
That is why I don't recommend such distros to others even though I use some myself. There are still teething problems. It's still not trivial to enable and disable some things on startup while on other systems it is trivial (eg. "ntsysv" on other/older distros covers pretty well everything in a very user friendly way).
One other interesting thing with gnome3 is that it has driven at least one vendor of X on MS Windows to an RDP based system just so that gnome3 stuff will work remotely. Keep that in mind when wayland fanboys use gnome3 applications as their strawman as to why X sucks (eg. gedit takes forever to startup - thus X sux even though plenty of other stuff takes a hell of a lot less time even on really old hardware).
You'd be better off helping to develop wayland to the point where debian or anyone else would consider going with it than hoping they decide to put in all the work to get it to a point where they could consider using it. Debian can't just pick it up "off the shelf" and use it as is. Until then why should they be interested? Take a look at the wayland mailing list and see how far it has to go before it's ready to go into a mainstream distro. Wayland seems to have a fanboy to developer ratio of about 10^6 to one. I suggest evening up the balance instead of just hoping that somebody will pick it up.
holy shit. the fact you think OSS software is even in the same league as Adobe apps is an indicator you are totally clueless.
Correct, such people must have missed things like Dmitry Sklyarov showing that a breakfast cereal code wheel style letter substitution method was used by Adobe as "encryption". Julius Caesar famously wrote a description of that method, that's how old and well know it is. OSS software in that league would get laughed at and not taken seriously at all.
So, really, it is not Windows that keeps people on Windows, it is application developers who haven't yet been sufficiently pressured by their publishers into increasing their install base.
Some application developers I've met don't yet know how to deal with 64bit and multiple cores, so yes, they are stuck in 1995:(
Unless you're talking about large business, then they'll be (and are) switching to Win7.
True, still switching. While you may think it insane that some application vendors are still taking their time porting to Win7 also consider that some still insist on using evil parallel port "security" dongles before you can run their stuff.
The specs for all recent switches I've seen will let you connect with a crossover cable as if it's a normal cable. However I don't think it's always the other way where a PC to PC connection will use a normal cable as a link and treat it like old machines connected via a crossover cable.
I'm sure you haven't seen a red boot on a cable in many years!
The crossover cable I've got it black with black boots - there was not an official standard followed of red boots that's just what the vendor of your cable used. There are still crossover cables listed from some online suppliers.
tx to rx anymore, it auto-negotiates that now
At the switch end almost always now. I'm not so sure about some of the low end stuff on motherboards for the other end.
I can see myself using a crossover cable again soon for 10Gb ethernet if it's needed, although the switches are starting to descend from insane prices.
Slashdot Mirror
However the witches as listed in the defrocked monk's witchfinder's manual never have. It was an excuse to sexually assault widows, murder them and take their stuff with half given to the state to allow the murder to be carried out. Funny how we went from a monk's fantasy of girls rubbing on broomsticks to Harry Potter and Quiddich.
Well played. See - that's so much more fun than trolling people about their choice of operating system or display environment.
I stand corrected. That was one busy minute.
The new version still does not deliver the promised features from ten years ago so why not keep the one with the bigger theoretical feature list :)
To be honest, the 2003 version is far less of a piece of shit than earlier ones. I did a bare metal recovery drill with an earlier version which demonstrated very clearly that it was a shambolic pile of barely communicating different programs as fragile as glass, slow as a dead dog, and only truly reliably backed up with just about all of it shut down. Open relay by default after one patch and some options were only available with registry hacks - it should never have been released in such a state. The only sane way to operate it for only 100 mailboxes was two servers (for when one went down, which happened every couple of weeks due to a memory leak, and for enough speed at peak times) and a real mail transfer agent in between it and the wild internet.
While I agree with that (even the name tells you what should be done with it - swap it with something else) you seem that have missed that "cutting waste" is the way people associated with government services get promoted. Improvements are seen as an unfair burden on the taxpayer.
Oddly enough people who talk of "running government like a business" are the first to NOT run it like a business which would see upgrades as spending necessary funds to make improvements that drive better savings/profits in the long run. Instead they try to run it like a doomed business given to the idiot son of the founder of a business.
In the long run having people wait around for their computers instead of working becomes more of a burden to the taxpayer than an upgrade.
Neither does the system that is being messed with, which I why I made the analogy in the first place!
An inability of other communications systems to operate in no way implies that everything else is out. I suggest applying at least some thought instead of going for such all or nothing bullshit.
The pilot does that by throwing breakers to isolate an electrical fire. Apparently that can be done very quickly.
We don't know either way if that was the case or not. All we know is nobody got on the radio to say anything about "a multitude of fire/smoke detectos".
From reading the timeline of events with QF32 after it lost an engine and a lot of control systems, it was some minutes after the engine blew up that they took time to radio in and that was with four pilots on board (two trainers there to do a flight review). They appear to have been a bit busy trying to work out how to stop the situation getting worse in the short term.
Or a fire and a divert to another airport that didn't make it.
Or some electrical breakers as in a procedure for containing an electrical fire.
It's showing that we are merely human and can lose track of a large aircraft despite modern technology.
Sometimes if you don't then the message does not get through.
"There is a 25mm deep crack in the weld that has opened up by 3mm" doesn't get taken seriously by some but "the weld is so fucking cracked that I can stick a fucking ruler into it" conveys the message in uncertain terms. Sadly that is from a real example. The first bit got excuses, fobbed off and "she'll be right" bullshit. The second got the work done again and done properly.
Go on - list the teapot storms for our entertainment. Do you want to start with the doctor recently turned coder that doesn't even run linux on his main machine that was told he should "eat his own dog food" (which means run his own stuff) before pushing alpha quality scheduling patched on people? That one seemed fair enough to me but I seem to remember you kicking up a fuss.
Don't know much about Linus do you?
That is why I don't recommend such distros to others even though I use some myself. There are still teething problems. It's still not trivial to enable and disable some things on startup while on other systems it is trivial (eg. "ntsysv" on other/older distros covers pretty well everything in a very user friendly way).
One other interesting thing with gnome3 is that it has driven at least one vendor of X on MS Windows to an RDP based system just so that gnome3 stuff will work remotely.
Keep that in mind when wayland fanboys use gnome3 applications as their strawman as to why X sucks (eg. gedit takes forever to startup - thus X sux even though plenty of other stuff takes a hell of a lot less time even on really old hardware).
You'd be better off helping to develop wayland to the point where debian or anyone else would consider going with it than hoping they decide to put in all the work to get it to a point where they could consider using it.
Debian can't just pick it up "off the shelf" and use it as is. Until then why should they be interested? Take a look at the wayland mailing list and see how far it has to go before it's ready to go into a mainstream distro.
Wayland seems to have a fanboy to developer ratio of about 10^6 to one. I suggest evening up the balance instead of just hoping that somebody will pick it up.
One person's "cutting corners" is another's "changing an unreasonable design choice made for trivial reasons to a reasonable one".
Yes, we get that you are bored and just want yet another petty argument. How about posting something interesting instead?
Correct, such people must have missed things like Dmitry Sklyarov showing that a breakfast cereal code wheel style letter substitution method was used by Adobe as "encryption". Julius Caesar famously wrote a description of that method, that's how old and well know it is.
OSS software in that league would get laughed at and not taken seriously at all.
Some application developers I've met don't yet know how to deal with 64bit and multiple cores, so yes, they are stuck in 1995 :(
True, still switching. While you may think it insane that some application vendors are still taking their time porting to Win7 also consider that some still insist on using evil parallel port "security" dongles before you can run their stuff.
It's just the equivalent of messing with the car stereo on other cars.
The specs for all recent switches I've seen will let you connect with a crossover cable as if it's a normal cable. However I don't think it's always the other way where a PC to PC connection will use a normal cable as a link and treat it like old machines connected via a crossover cable.
The crossover cable I've got it black with black boots - there was not an official standard followed of red boots that's just what the vendor of your cable used. There are still crossover cables listed from some online suppliers.
At the switch end almost always now. I'm not so sure about some of the low end stuff on motherboards for the other end.
I can see myself using a crossover cable again soon for 10Gb ethernet if it's needed, although the switches are starting to descend from insane prices.