So what you're saying is that the war didn't cost us that much, so don't worry about it. Oh, and W should get credit for ending a war that shouldn't have been started in the first place. Got it.
Assuming you were in the military in Iraq, thank you for your service. But don't think that makes you right.
Aside from my brother, a cousin, and a few friends going over there for a year and the amount of money I (and eventually my daughter) will pay to cover the loans we got from the Chinese over it, sure, it didn't affect me at all.
Oh, and all the money we'll pay to cover wounded vets for the next 50+ years.
Interesting, but I think the act of hiring an employee would wind up costing more than a $3000 credit. You have to pay for headhunters, placements in various online and in-print locations, time spent interviewing, HR time, any kinds of bonuses you want to pay, etc.
Smaller companies probably don't pay as much, so it's more worthwhile to them to get the $3k credit.
You can always track his campaign promises. As of right now, 7 are kept, 1 stalled, 14 in the works, and no status on 488. Not a bad start after 3 days.
I have a BlackBerry Curve (business) and RAZR (personal) that both charge via USB. I've never had a problem getting either to charge under Linux, but doing so from Windows requires installing the Mororola/RIM drivers first.
I just make my life easy and stick with Linux.
Tethering with the Curve is pretty simple over bluetooth, though not as simple as the USB WWAN dongle that's available now.
We were running as CGI to debug problems between Apache and mongrel. Turned out it was the rails app causing our grief, but that led into my debugging issues. I had almost nothing in log files to tell me what was going on.
But strace was a big help when I tried to run as CGI. The problem was not log/ and tmp/, but more like rails (or ruby) doing over 20k file lookups all over the system looking for various files. On a local disk, that can be pretty quick. Over NFS, that large number of searches really bogs down. There's no reason for all those searches, especially when you should be able to set the locations as options.
I'm more frustrated over the notion that the developers keep changing their requirements. Their development time may be fast, but building the systems to handle their code isn't, especially when we have to toss out the previous 2-3 months worth of work because some new shiny shiny came out, the developers are asking for it, and it's brand new code that barely works. Then you go through the same exercise 2-3 months later.
Sure I know mongrel, but that knowledge is useless now. I don't mean to sound bitter or angry, but more seasoned (if undesirable by coders) languages like PHP/Pyhton/Perl are easily understood and work well for what they do. For us to integrate those into our hosting environment is a no-brainer. Even application servers like tomcat and jboss are easier to set up now as well.
Then again, that's why I'm a sysadmin and not a coder.
What exactly are you trying to debug? As for deploying new versions, It's dead simple to bundle rails with the application, and then all you are doing is an application deploy.
I'm trying to track down problems that the coders are having. We're not sure if the problem is in the RoR end or the Apache/mongrel end.
Why were you running as a CGI in the first place? Did you do any research before hand? I don't understand how you would do any reading about ruby without stumbling across it's relative slowness, and then you tried to add another layer to the process? And then you add NFS for good measure?
Rails is optimised for developer productivity, not for raw execution speed. As a sysadmin, you need to run it with either a pack of mongrels or phusion passenger. If you're debugging for more than 15 minutes per deployment, you need to get your developers to write some more unit tests.
Why as CGI? Like I said above, we're trying to debug problems. The response that Rails developers have to problems is pretty poor. And to add to that. mongrel isn't being developed anymore (from what I'm told), and mod_rails is the new hotness. Running separate servers for each RoR app just won't cut it - there's too much that requires interaction between the developer and sysadmin to get it working quickly.
It may be easy to write and deploy, but as a sysadmin that builds the systems that run RoR apps, it stinks.
There's little to no debugging, we've gone through four different ways to run RoR apps, and there are new versions every few weeks.
For real fun, try running a Rails app where it's deployed to an NFS filesystem and then try to run the app via CGI. You can see how well it's 'optimized'.
The DRM that's associated with iTunes is quite generous to us consumers:
- burn to CD (and re-rip as MP3) - up to 5 computers can be licensed at a time - move licenses from system to system (not like @#$^#$% bioshock) - easy transfer to iPods (or other MP3 players if you burn to CD)
Is it DRM? Yeah. Is it better than getting just MP3? No, I'll get some songs from Amazon because it's MP3 only. But for what it does and how I can use it, I'm happy with it.
I wrote three Linux books (one of which was reviewed here on/.) plus two Computer Based Training CDs. Though the last one was released about 6 years ago, I have a few thoughts for you that I hope are helpful.
Back when I did my first book, there wasn't much other than Word. I wound up writing most of it in vi. It sucked for me writing it and for my publisher to turn it into something that was ready to be published. For my second book, I had a collaborator and we wound up doing most of the work in Word since there weren't many adequate tools for Linux. We had one file per chapter and used the revisions to track what each of us did. The third book (and the two CBTs I did) followed that, though I think I did use what is now OpenOffice to write some and then save it in.doc format. The.doc format was the only format my publisher accepted that I wanted to use - I could have used TeX, but chose not to. In those cases, I did use CVS, but only to store the changing binary versions of files. I seem to recall that in every case, I could just send my publisher a list of words I wanted in the index and they'd build it for me.
If I were to write a new book, I'd do it in DocBook/XML. It's really great at abstracting presentation from content, and tools like OpenOffice can export as DocBook for you. Check with your publisher and see if they'll take it. If you're interested, there's a lot of useful information on DocBook in the LDP Author Guide, which I started writing years ago.
I think the important things aren't the tools, but more how you approach writing. You'll be doing this over a long period of time and you'll have to write a lot of pages. You need to be really disciplined to write N pages per day so that you don't get behind the curve and realize that you need to write 50 pages in the next two days before it's due.
I took care of this in a similar way that I write code. I started by listing the chapters I wanted to do, which was part of the proposal. I then started breaking down each chapter into smaller and smaller sections until I knew what I wanted to put in each paragraph, then start writing paragraphs. It really helps you focus on a few things instead of having to work on an entire chapter at once.
So because noone ever gets hurt on the job anymore, we should get rid of OSHA.
Because the credit markets are doing fine by themselves, we should remove the regulations that prevent them from completely screwing up the economy, right?
Then the drone should have said "I don't have 10.4.8 on my list. Is it leopard?". The drone should have asked a manager to add in equivalency options, so the list would read "10.4.x/Leopard".
I used to work tech support (I still do in a way). In the previous job, we had drones who didn't know SunOS from Solaris. If they had a question about an OS level, we answered it and then made sure that the question wouldn't come to us again by documenting it somewhere easy to find.
Normally I'd agree with you, but ability to trample on other frequencies has always been around. The FCC comes down pretty hard on manufacturers that are out of spec (hence the reason why just about every electrical device sold in the US is tested to FCC specs).
Re:IT boss=human filter for stupidity @ higher lev
on
Fire Your IT Boss
·
· Score: 1, Insightful
Wish I had mod points. Instead, I'll use my low-low ID to say that you're absolutely correct.
Slashdot Mirror
Nice dealing in absolutes there. Why don't you actually read the opinion piece and try to understand what it means and then spout your nonsense?
So what you're saying is that the war didn't cost us that much, so don't worry about it. Oh, and W should get credit for ending a war that shouldn't have been started in the first place. Got it.
Assuming you were in the military in Iraq, thank you for your service. But don't think that makes you right.
Aside from my brother, a cousin, and a few friends going over there for a year and the amount of money I (and eventually my daughter) will pay to cover the loans we got from the Chinese over it, sure, it didn't affect me at all.
Oh, and all the money we'll pay to cover wounded vets for the next 50+ years.
And the increased hatred towards the US.
Yup. Didn't affect me at all.
Interesting, but I think the act of hiring an employee would wind up costing more than a $3000 credit. You have to pay for headhunters, placements in various online and in-print locations, time spent interviewing, HR time, any kinds of bonuses you want to pay, etc.
Smaller companies probably don't pay as much, so it's more worthwhile to them to get the $3k credit.
You can always track his campaign promises. As of right now, 7 are kept, 1 stalled, 14 in the works, and no status on 488. Not a bad start after 3 days.
Let me second this. I my desktop/laptop systems that run Ubuntu, but all my servers are running Debian.
Verizon has at least one phone (Blackberry 8830) that works on both CDMA and GSM.
I have a BlackBerry Curve (business) and RAZR (personal) that both charge via USB. I've never had a problem getting either to charge under Linux, but doing so from Windows requires installing the Mororola/RIM drivers first.
I just make my life easy and stick with Linux.
Tethering with the Curve is pretty simple over bluetooth, though not as simple as the USB WWAN dongle that's available now.
Go read my other comments where I explain what I was doing, why, and why the performance was so terrible.
Perl CGI doesn't have this problem, nor does python.
We were running as CGI to debug problems between Apache and mongrel. Turned out it was the rails app causing our grief, but that led into my debugging issues. I had almost nothing in log files to tell me what was going on.
But strace was a big help when I tried to run as CGI. The problem was not log/ and tmp/, but more like rails (or ruby) doing over 20k file lookups all over the system looking for various files. On a local disk, that can be pretty quick. Over NFS, that large number of searches really bogs down. There's no reason for all those searches, especially when you should be able to set the locations as options.
I'm more frustrated over the notion that the developers keep changing their requirements. Their development time may be fast, but building the systems to handle their code isn't, especially when we have to toss out the previous 2-3 months worth of work because some new shiny shiny came out, the developers are asking for it, and it's brand new code that barely works. Then you go through the same exercise 2-3 months later.
Sure I know mongrel, but that knowledge is useless now. I don't mean to sound bitter or angry, but more seasoned (if undesirable by coders) languages like PHP/Pyhton/Perl are easily understood and work well for what they do. For us to integrate those into our hosting environment is a no-brainer. Even application servers like tomcat and jboss are easier to set up now as well.
Then again, that's why I'm a sysadmin and not a coder.
What exactly are you trying to debug? As for deploying new versions, It's dead simple to bundle rails with the application, and then all you are doing is an application deploy.
I'm trying to track down problems that the coders are having. We're not sure if the problem is in the RoR end or the Apache/mongrel end.
Why were you running as a CGI in the first place? Did you do any research before hand? I don't understand how you would do any reading about ruby without stumbling across it's relative slowness, and then you tried to add another layer to the process? And then you add NFS for good measure?
Rails is optimised for developer productivity, not for raw execution speed. As a sysadmin, you need to run it with either a pack of mongrels or phusion passenger. If you're debugging for more than 15 minutes per deployment, you need to get your developers to write some more unit tests.
Why as CGI? Like I said above, we're trying to debug problems. The response that Rails developers have to problems is pretty poor. And to add to that. mongrel isn't being developed anymore (from what I'm told), and mod_rails is the new hotness. Running separate servers for each RoR app just won't cut it - there's too much that requires interaction between the developer and sysadmin to get it working quickly.
It may be easy to write and deploy, but as a sysadmin that builds the systems that run RoR apps, it stinks.
There's little to no debugging, we've gone through four different ways to run RoR apps, and there are new versions every few weeks.
For real fun, try running a Rails app where it's deployed to an NFS filesystem and then try to run the app via CGI. You can see how well it's 'optimized'.
The DRM that's associated with iTunes is quite generous to us consumers:
- burn to CD (and re-rip as MP3)
- up to 5 computers can be licensed at a time
- move licenses from system to system (not like @#$^#$% bioshock)
- easy transfer to iPods (or other MP3 players if you burn to CD)
Is it DRM? Yeah. Is it better than getting just MP3? No, I'll get some songs from Amazon because it's MP3 only. But for what it does and how I can use it, I'm happy with it.
I wrote three Linux books (one of which was reviewed here on /.) plus two Computer Based Training CDs. Though the last one was released about 6 years ago, I have a few thoughts for you that I hope are helpful.
Back when I did my first book, there wasn't much other than Word. I wound up writing most of it in vi. It sucked for me writing it and for my publisher to turn it into something that was ready to be published. For my second book, I had a collaborator and we wound up doing most of the work in Word since there weren't many adequate tools for Linux. We had one file per chapter and used the revisions to track what each of us did. The third book (and the two CBTs I did) followed that, though I think I did use what is now OpenOffice to write some and then save it in .doc format. The .doc format was the only format my publisher accepted that I wanted to use - I could have used TeX, but chose not to. In those cases, I did use CVS, but only to store the changing binary versions of files. I seem to recall that in every case, I could just send my publisher a list of words I wanted in the index and they'd build it for me.
If I were to write a new book, I'd do it in DocBook/XML. It's really great at abstracting presentation from content, and tools like OpenOffice can export as DocBook for you. Check with your publisher and see if they'll take it. If you're interested, there's a lot of useful information on DocBook in the LDP Author Guide, which I started writing years ago.
I think the important things aren't the tools, but more how you approach writing. You'll be doing this over a long period of time and you'll have to write a lot of pages. You need to be really disciplined to write N pages per day so that you don't get behind the curve and realize that you need to write 50 pages in the next two days before it's due.
I took care of this in a similar way that I write code. I started by listing the chapters I wanted to do, which was part of the proposal. I then started breaking down each chapter into smaller and smaller sections until I knew what I wanted to put in each paragraph, then start writing paragraphs. It really helps you focus on a few things instead of having to work on an entire chapter at once.
Good luck with your book.
So because noone ever gets hurt on the job anymore, we should get rid of OSHA.
Because the credit markets are doing fine by themselves, we should remove the regulations that prevent them from completely screwing up the economy, right?
n00b
/etc/passwd and /etc/shadow are two great reasons to encrypt /
Then the drone should have said "I don't have 10.4.8 on my list. Is it leopard?". The drone should have asked a manager to add in equivalency options, so the list would read "10.4.x/Leopard".
I used to work tech support (I still do in a way). In the previous job, we had drones who didn't know SunOS from Solaris. If they had a question about an OS level, we answered it and then made sure that the question wouldn't come to us again by documenting it somewhere easy to find.
Got me beat, but not by much.
Guild Wars is even cheaper (pay for the software, no recurring fees). I've been playing it for about 3-ish years off and on and still enjoy it.
Service guarantees citizenship. Would you like to know more?
Ghostbusters.
Duh.
Product placement, advertising in other media (print, radio, internet), and more targeted advertising.
Normally I'd agree with you, but ability to trample on other frequencies has always been around. The FCC comes down pretty hard on manufacturers that are out of spec (hence the reason why just about every electrical device sold in the US is tested to FCC specs).
Wish I had mod points. Instead, I'll use my low-low ID to say that you're absolutely correct.