The company laid off half the team which increased the work load of those left. Our oncall was horrible, you were guaranteed to be woken up and work on weekends. With less staff oncall was more frequent. Senior Leadership refused to spend money or allocate time to fix the root causes of the issues.
It's like we're all saying "Open source is a good thing", and he's now picking up that banner, saying "Unless it's completely open and completely free in every possible sense of the word, it's wrong"
That's the same thing he's been saying since the beginning. Remember that the OSS movement came from his FSF.
I'm not saying he's right, only that your statement is not based on facts.
Take a look at John Ringo. He co-wrote a series with David Weber called The Empire of Man.It's an excellent series that is currently on it's 3rd book and continuing. Ringo's current solo series, Legacy of the Aldenata, is also very good. In fact if your a Sluggy Freelance fan then you reallly should pick this series up as it has several references to sluggy in it.
John Ringo may not have written much yet but so far everything he has written has keep me glued to it from cover to cover stopping only for the usual (beer, bathroom, food).
The biggest question I have about this is how can they prove that the person whose name is on the From: actually sent the e-mail?
We all know just how insecure e-mail really is and how easy it is to forge an e-mail, so how can these e-mails stand up as evidence. I can see some justification in if the headers show the e-mail coming from that person's workstation's IP connecting to ${CORPORATE_MAIL_SERVER}, but even this is not 100% proof that it came from ${PERSON}.
Yes there is it's:
set mbox=""
A quick browsing through the stock mutt rc file would have shown you this.
>but people won't switch from Pine to mutt >readily if they have to configure mutt by hand >first.
Umm, I eould think that most || all here who use *NIX do so because of the control it allows. Isn't part of that control gowing through conf && rc files configuring things just the way we want them?
Slashdot Mirror
The company laid off half the team which increased the work load of those left.
Our oncall was horrible, you were guaranteed to be woken up and work on weekends.
With less staff oncall was more frequent.
Senior Leadership refused to spend money or allocate time to fix the root causes of the issues.
It's like we're all saying "Open source is a good thing", and he's now picking up that banner, saying "Unless it's completely open and completely free in every possible sense of the word, it's wrong" That's the same thing he's been saying since the beginning. Remember that the OSS movement came from his FSF. I'm not saying he's right, only that your statement is not based on facts.
Why not just call us Computer Janitors. That's really what we are.
We clean up everyone elses mistakes/crap.
John Ringo may not have written much yet but so far everything he has written has keep me glued to it from cover to cover stopping only for the usual (beer, bathroom, food).
The biggest question I have about this is how can they prove that the person whose name is on the From: actually sent the e-mail?
We all know just how insecure e-mail really is and how easy it is to forge an e-mail, so how can these e-mails stand up as evidence. I can see some justification in if the headers show the e-mail coming from that person's workstation's IP connecting to ${CORPORATE_MAIL_SERVER}, but even this is not 100% proof that it came from ${PERSON}.
I like my job, but I hate the company I work for.
Yes there is it's: set mbox="" A quick browsing through the stock mutt rc file would have shown you this. >but people won't switch from Pine to mutt >readily if they have to configure mutt by hand >first. Umm, I eould think that most || all here who use *NIX do so because of the control it allows. Isn't part of that control gowing through conf && rc files configuring things just the way we want them?
http://elian.sucks.azagthoth-reborn.com