First of all if your running database servers in a production environment any competent engineer would have a UPS in place on each power supply connected to a different circuit.
This avoids the scenario of data not getting written due to a power failure.
If your running database servers in a production environment any competent engineer would be running stable software which would avoid 99% of crashes.
EXT3 is not a replacement for a UPS or using stable software.
So a lawyer with limited control of the company except unrestricted settlement rights still could take the place of an executive.
It strikes me that it's a fairly simple task to tell the lawyer... 'if you think we'll lose do whatever you can to drop the case without setting a precedent, if the judge rules in favor of the client , if we win get as much money as possible.
each record company plaintiff is ordered to produce an 'officer' of the corporation, or a 'managing agent' of the corporation, who has corporate, decision-making, 'power.'
Couldn't they simply grant one of their lawyers these privileges with certain restrictions meet the requirements and keep going on as per usual?
That said this would obviously not be a wise decision if the lawyers aren't acting in the best interest of their client.
I guess I'm not an average user... I have five email addresses that I actively use depending on the purpose of the email.
1. Alias (xous) - used for random internet stuff. 2. Real Name - used for personal email 3. Business 1 email (self-explanatory) 4. Business 2 email (self-explanatory) 5. Business 3 email (self-explanatory)
I really don't see the point of writing code to emulate an exchange server when Microsoft is just going to break it again anyway.
Why not write a open standard for calendar and scheduling interchange and take a decent FOSS client (e.g. thunderbird) and extend it to work with that protocol?
If you really want outlook capability it should be written as a gateway to the open standard protocol.
Why the hell don't they just do it already.
If nothing bad happens everything will be fine. If something bad happens there is a good chance we won't be around long enough to realize they screwed up.
Not exactly win-win but hell, I like a good gamble.
Why is this marked as troll?
Any one with a $70 embedded PC, high amperage relay, and a temperature probe could do this in a few hours.
This would only be interesting if a) all fridges used a standardized negotiation protocol b) it was extended to all high usage appliances.
Inheritance like any regular person would.
Even if you went back a few hundred years and completely removed royalty it is very likely that her family would still be considerably well off.
This is pretty much all that is left of her power.
These days a monarch is nothing more than a figurehead who dances for the public. Not a job I'd want.
This is true but perhaps I'm not understanding the full importance of precise time keeping in respect to the air traffic control application.
Is this used to provide accurate location information?
This solution is practically useless as when a sufficient number of hosts use a non-standard port they will simply use port scans.
As a systems administrator that has to deal with morons constantly locking themselves out of their servers due to using random ports and other silly techniques I find this to be an extremely stupid idea.
-1 points for suggesting people change their ssh port to a non-standard port. There is a reason we have standards.
Real solution: use Public Key Authentication or at least require strong passwords.
It's a play on the three in four accounts compromised.
Accounts not compromised: 1 in 4
1/4 = 25%
He is implying that they were compromised because they were running something that was not Linux.
Hehe,
I bought a Logitech Trackman Marble Wheel back in 2000 and it wore out last year. Searched for a few months and ended up paying $60 for a similar one.
Good Mouse.
They can/decide/ not to use those servers but your forgetting that people are lazy.
Current resolver implementations are shipped with a root hints file that uses ICANN's servers. This also wouldn't prevent anyone from just using ICANN's anyway. (Unless they actively blocked connections to those servers)
I wrote a script that automatically logs onto all my IM accounts and email accounts and says:
"xous has not reset death timer in 72 hours. Attempts to contact him have failed assuming deceased."
Originally, it also initiated another script of mine that began purging and secure erasing my file server. After setting it off a few times and having to restore from encrypted backups during drinking binges I decided to increase the timer to two weeks.
I wonder if it's over kill?
He probably means /
Hi,
First of all if your running database servers in a production environment any competent engineer would have a UPS in place on each power supply connected to a different circuit.
This avoids the scenario of data not getting written due to a power failure.
If your running database servers in a production environment any competent engineer would be running stable software which would avoid 99% of crashes.
EXT3 is not a replacement for a UPS or using stable software.
So a lawyer with limited control of the company except unrestricted settlement rights still could take the place of an executive.
It strikes me that it's a fairly simple task to tell the lawyer... 'if you think we'll lose do whatever you can to drop the case without setting a precedent, if the judge rules in favor of the client , if we win get as much money as possible.
each record company plaintiff is ordered to produce an 'officer' of the corporation, or a 'managing agent' of the corporation, who has corporate, decision-making, 'power.'
Couldn't they simply grant one of their lawyers these privileges with certain restrictions meet the requirements and keep going on as per usual?
That said this would obviously not be a wise decision if the lawyers aren't acting in the best interest of their client.
Well... he did ask for FOSS.
I'm surprised this isn't marked as troll.
"He happened to be in training for managment at the time, and was reading a book he'd bought for himself."
I assumed this to be a book on management... although it might explain why he was fired if he was training for management by reading the Hobbit.
Hi,
I guess I'm not an average user... I have five email addresses that I actively use depending on the purpose of the email.
1. Alias (xous) - used for random internet stuff.
2. Real Name - used for personal email
3. Business 1 email (self-explanatory)
4. Business 2 email (self-explanatory)
5. Business 3 email (self-explanatory)
There are A few failures on the network design part that you need to acknowledge:
People are idiots. If there are free points (and even if there aren't in some cases) people are going to plug in stuff.
Unused ports should be disabled (shutdown). This requires someone with half a brain to connect devices.
This is standard operating procedure.
Spanning tree was not enabled which caused your loop.
This is standard operating procedure.
Learn from your mistakes don't blame them on user stupidity as you can only control your own actions.
Sounds like someone doesn't know how to configure their switches properly.
It was a joke. Laugh.
They did about 30 years ago. Nobody switched.
I really don't see the point of writing code to emulate an exchange server when Microsoft is just going to break it again anyway. Why not write a open standard for calendar and scheduling interchange and take a decent FOSS client (e.g. thunderbird) and extend it to work with that protocol? If you really want outlook capability it should be written as a gateway to the open standard protocol.
Why the hell don't they just do it already. If nothing bad happens everything will be fine. If something bad happens there is a good chance we won't be around long enough to realize they screwed up. Not exactly win-win but hell, I like a good gamble.
Why is this marked as troll? Any one with a $70 embedded PC, high amperage relay, and a temperature probe could do this in a few hours. This would only be interesting if a) all fridges used a standardized negotiation protocol b) it was extended to all high usage appliances.
This shouldn't even be suggested. Buy a bloody ATS. http://en.wikipedia.org/wiki/Transfer_switch
Inheritance like any regular person would. Even if you went back a few hundred years and completely removed royalty it is very likely that her family would still be considerably well off.
This is pretty much all that is left of her power. These days a monarch is nothing more than a figurehead who dances for the public. Not a job I'd want.
This is true but perhaps I'm not understanding the full importance of precise time keeping in respect to the air traffic control application. Is this used to provide accurate location information?
Then switch to a stable time scale: http://en.wikipedia.org/wiki/International_Atomic_Time
Haven't they heard of NTP? http://en.wikipedia.org/wiki/Network_Time_Protocol
This solution is practically useless as when a sufficient number of hosts use a non-standard port they will simply use port scans. As a systems administrator that has to deal with morons constantly locking themselves out of their servers due to using random ports and other silly techniques I find this to be an extremely stupid idea. -1 points for suggesting people change their ssh port to a non-standard port. There is a reason we have standards. Real solution: use Public Key Authentication or at least require strong passwords.
It's a play on the three in four accounts compromised.
Accounts not compromised: 1 in 4
1/4 = 25%
He is implying that they were compromised because they were running something that was not Linux.
Hehe, I bought a Logitech Trackman Marble Wheel back in 2000 and it wore out last year. Searched for a few months and ended up paying $60 for a similar one. Good Mouse.
They can /decide/ not to use those servers but your forgetting that people are lazy.
Current resolver implementations are shipped with a root hints file that uses ICANN's servers. This also wouldn't prevent anyone from just using ICANN's anyway. (Unless they actively blocked connections to those servers)
I wrote a script that automatically logs onto all my IM accounts and email accounts and says: "xous has not reset death timer in 72 hours. Attempts to contact him have failed assuming deceased." Originally, it also initiated another script of mine that began purging and secure erasing my file server. After setting it off a few times and having to restore from encrypted backups during drinking binges I decided to increase the timer to two weeks. I wonder if it's over kill?