In the olden days, tar would not check things as carefully as it does today. I've zeroed out many a tarball and ruined many source, err destination?, directories, by not being on the ball and mistakenly switching -c and -x at an inopportune time, or putting the directory before the tar filename, or forgetting the slash, or some other such silliness. C and X are even right next to each other on the keyboard, so it'a an easy typo to make late at night.
As for why the LCDs are in a television set of a hospital: perhaps for realism, but probably because LCDs, being smaller, obstruct the field-of-view a lot less, making the set look and feel more open.
They also look nicer and more techy, and the image is solid, so you get to avoid shooting a lot of flicker.
In short, nobody can improve on your property and use those improvements to their exclusive benefit. Any improvements must necessarily benefit everybody. period.
Not if you keep those improvements to yourself and not release it to anyone. You can make some kick ass propriatary changes to the Linux kernel, and as long as you don't release the binary you can keep your changes private.
Yes, but hardware makers often segregate their markets artificially. It's the same hardware, but depending on what software is loaded different functionality is enabled. It's cheaper to anufacture things that way.
If detailed specs, or sources, were published, it would make it trivial for people to buy the cheap version, load the high-end software on it, and avoid the price tag.
I see you've never bought a TV series DVD before. In every case that I've seen they come with 4 episodes per DVD. How do you get 300MB per episode? That's pathetic, even a 42 minute 300MB DivX would look like crap. MPEG2 uses much higher bitrates than that. Last time I ripped a DVD (for personal use of course) it was 24 Season 2, and each episode was almost 2GB.
So the math is:
48 * 4 = 192
This is more than sufficient, and allows for some extras and special features.
Yeah, whatever. No matter where they are shooting, bit name stars and directors still make the same money. Maybe there's the problem?
If someone gets paid USD50/hour shooting in the US, same job position will probably pay CDN50/hour shooting in Canada, and AUS50/hour shooting in Australia. The difference is in the exchange rate. This is applied to wages, equipment of all kinds, food, rent and permits, etc.
You can't have it both ways. You can't complain that it is cheaper to make movies in Canada and Australia, and then come here on vacation because your dollar goes so much further in these 'bumfuck' countries.
Bottom line is, this functionality does not belong in DNS. It is up to the individual applications to do what they think is best when a user tries to communicate with an invalid host. IRC and FTP connections fail. Web browsers display a search page. Email bounces (albeit with a usually cryptic message). And who's to say that what DNS will suggest is even remotely applicable to the protocol and application at hand?
DNS is a basic underlying protocol. It doesn't need to be saddled with this extra, mostly useless, functionality.
DNS is not a search engine. DNS look ups are final, authoritative and precise. The host and/or record type you're looking for either exists, or it doesn't. You want a search engine, go to Google. Maybe Google will come up with a DNS search widget? But this functionality does NOT belong in DNS.
Since people don't bother carrying all their cards with them (how can I, I just have a money clip with a work id/proxy access card, driver's license, bank/cash card, and a credit card (just to fill out the slots)), you can simply give your phone number when they ask if you have the card. At my store (Satfeway) there is no 1-1 relationship between cards and phone number. I discovered that by using my phone number all my purchases go to someone else's savings card account. I guess if we can pool all the purchases we'll get a better discount?
Hmm, ok, so it's a matter of format? Same difference. It still doesn't give you the right to get it for free. If you don't like the format Kellogs is using to package and sell their corn flakes, you don't cut the box in half and walk out with it without paying.
I have no moral problem with making something that a company won't sell me.
So take your own advice and MAKE it. You're not making it yourself, you're taking somebody else's for free. Again, a company is not obligated by law to make a service or product available to you, available for a price you agree on, and in a manner and format you find acceptable. You don't like what and how they're selling, you don't buy it.
I always wondered about that... what happens when you do that? Is there some sort of feedback to tell you this trick worked, or do you have to guess when it's safe to let go the shift key?
I the case of broken CDs, it's not quite that black and white.
These CDs have a data track, which has an autorun file on it. The autorun starts a silent installer that quietly installs some shitty DRM music player on your computer to play the WMA files. At least the CD that I put in on my work machine did that. At home, of course, I disable autorun on all the drives.
My ISP (a national telco) pays about $0.50/GB in transit fees for residential traffic. You calculate it out.
Currently, there is no profit in residential DSL. Two or three years ago you could expect reasonable subscribers to start turning profit after 2-3 years. With the recent price cuts (cuts into margins) and higher demand (lots and lots of expensive new equipment and infrastructure) means that DSL is a losing proposition on any scale, especially if you intend to compete with, say, cable pricing. All the money to be made will be in future services and bundling. Cable companies have been doing this since day one. Phone companies will also, since they can offer phone service, VoIP, data and, in the near future, video.
There are a lot of things people with heart problems are physically capable of doing that will kill them. When the heartbeat generator fails, he has to work extra hard, and that is why he collapses, all the extra strain of his heart.
Why?! I think it's a great practice. My phone company itemizes my bill, listing all the taxes and fees they have to pay. People bitch all the time about how the phone company is ripping them off, not realizing that like 25-30% of their bill goes directly to the government.
I think your gasoline bill should list all the taxes too. They now comprise, what, 60% of the price of gas at the pump?
Along the same lines, I also think the government should send you an income tax bill once a month, and everyone should be writing a big check equivalent to 3-4 months salary to pay it.
I don't see any problems with this. If the government requires a company to pay a special new tax, what do you propose the company do? Swallow the cost? They already have their margins. They can't just raise prices for no apparent reason. I think this is a great solution. You can raise the price to cover your costs and maintain margin, inform customers of what is going on, and point the blame at the government, because that's right where it belongs.
Transparency is a great thing. It shows how much things really cost, and why. If my phone bill goes up $2/month, with the money going to the government and me not seeing any phone service benefits, I want to know why, and I'd want to be reminded every month.
A well designed worm (or a virus for that matter) can pop up an important looking window saying something bad has happened on the system, please supply the root password to fix it. Haw many casual Linux users (if there are an?) do you think would fall for that? When you're running KDE or Gnome as a regular user, you'll get prompted for the root password when performing many system-type tasks. A smart worm could even wait for you to click on something before popping up, so that it doesn't appear as if it came out of nowhere.
No system is immune by design. Stupid or careless users are always crafty enough to bypass even the best security.
The root DNS registry operator may not themselves be a DNS registrar
You seem to be confused with the terms. There is no such thing as a DNS Registrar. There are Root DNS Server Operators and there are Domain Registrars. You can't register DNS.
I think what you're getting at is that neither a domain registrar nor a TLD zone operator should run a root DNS server. And I would agree with that. I would go even further, and say that the three entities should be separated. Right now, Verisign runs a domain registry, controls the.com and.net TLDs, AND has a root DNS server.
I see this suggestion every time the issue of handing over logs comes up.
In a general case, this won't happen. You need to keep logs around. For abuse resolution and tracking down offenders. If you bill per hour for dialup access, you need to keep radius logs. If you charge for IP services, you need to keep logs around to you can figure out who to charge. Anything related to billing you need to keep around for at least a month (and usually 2 or 3) to bill and audit properly, and to handle billing disputes. What do you do when you get rid of access logs after 3 days, and a month later your customer calls you up and says wtf is this charge on my bill?
Slashdot Mirror
But don't worry, so will spammers.
When you get the 'slow down cowboy...2 minutes' page, you can reload it to post your reply, the whole thing is still there in a hidden form.
In the olden days, tar would not check things as carefully as it does today. I've zeroed out many a tarball and ruined many source, err destination?, directories, by not being on the ball and mistakenly switching -c and -x at an inopportune time, or putting the directory before the tar filename, or forgetting the slash, or some other such silliness. C and X are even right next to each other on the keyboard, so it'a an easy typo to make late at night.
They also look nicer and more techy, and the image is solid, so you get to avoid shooting a lot of flicker.
I have to wonder how you're able to buy Word just by itself.
BTW, Amazon lists Office XP Pro for $380.
Not if you keep those improvements to yourself and not release it to anyone. You can make some kick ass propriatary changes to the Linux kernel, and as long as you don't release the binary you can keep your changes private.
Yes, but hardware makers often segregate their markets artificially. It's the same hardware, but depending on what software is loaded different functionality is enabled. It's cheaper to anufacture things that way.
If detailed specs, or sources, were published, it would make it trivial for people to buy the cheap version, load the high-end software on it, and avoid the price tag.
I see you've never bought a TV series DVD before. In every case that I've seen they come with 4 episodes per DVD. How do you get 300MB per episode? That's pathetic, even a 42 minute 300MB DivX would look like crap. MPEG2 uses much higher bitrates than that. Last time I ripped a DVD (for personal use of course) it was 24 Season 2, and each episode was almost 2GB.
So the math is:
48 * 4 = 192
This is more than sufficient, and allows for some extras and special features.
Well well, that's a revealing slip. Maybe they shouldn't be making money, they should be making movies enough people want to (pay to) see.
Yeah, whatever. No matter where they are shooting, bit name stars and directors still make the same money. Maybe there's the problem?
If someone gets paid USD50/hour shooting in the US, same job position will probably pay CDN50/hour shooting in Canada, and AUS50/hour shooting in Australia. The difference is in the exchange rate. This is applied to wages, equipment of all kinds, food, rent and permits, etc.
You can't have it both ways. You can't complain that it is cheaper to make movies in Canada and Australia, and then come here on vacation because your dollar goes so much further in these 'bumfuck' countries.
Bottom line is, this functionality does not belong in DNS. It is up to the individual applications to do what they think is best when a user tries to communicate with an invalid host. IRC and FTP connections fail. Web browsers display a search page. Email bounces (albeit with a usually cryptic message). And who's to say that what DNS will suggest is even remotely applicable to the protocol and application at hand?
DNS is a basic underlying protocol. It doesn't need to be saddled with this extra, mostly useless, functionality.
DNS is not a search engine. DNS look ups are final, authoritative and precise. The host and/or record type you're looking for either exists, or it doesn't. You want a search engine, go to Google. Maybe Google will come up with a DNS search widget? But this functionality does NOT belong in DNS.
Since people don't bother carrying all their cards with them (how can I, I just have a money clip with a work id/proxy access card, driver's license, bank/cash card, and a credit card (just to fill out the slots)), you can simply give your phone number when they ask if you have the card. At my store (Satfeway) there is no 1-1 relationship between cards and phone number. I discovered that by using my phone number all my purchases go to someone else's savings card account. I guess if we can pool all the purchases we'll get a better discount?
I have no moral problem with making something that a company won't sell me.
So take your own advice and MAKE it. You're not making it yourself, you're taking somebody else's for free. Again, a company is not obligated by law to make a service or product available to you, available for a price you agree on, and in a manner and format you find acceptable. You don't like what and how they're selling, you don't buy it.
I always wondered about that... what happens when you do that? Is there some sort of feedback to tell you this trick worked, or do you have to guess when it's safe to let go the shift key?
I the case of broken CDs, it's not quite that black and white.
These CDs have a data track, which has an autorun file on it. The autorun starts a silent installer that quietly installs some shitty DRM music player on your computer to play the WMA files. At least the CD that I put in on my work machine did that. At home, of course, I disable autorun on all the drives.
My ISP (a national telco) pays about $0.50/GB in transit fees for residential traffic. You calculate it out.
Currently, there is no profit in residential DSL. Two or three years ago you could expect reasonable subscribers to start turning profit after 2-3 years. With the recent price cuts (cuts into margins) and higher demand (lots and lots of expensive new equipment and infrastructure) means that DSL is a losing proposition on any scale, especially if you intend to compete with, say, cable pricing. All the money to be made will be in future services and bundling. Cable companies have been doing this since day one. Phone companies will also, since they can offer phone service, VoIP, data and, in the near future, video.
I have an even better idea. Load up the article and search the text for 'RFID'. Finally my ass...
There are a lot of things people with heart problems are physically capable of doing that will kill them. When the heartbeat generator fails, he has to work extra hard, and that is why he collapses, all the extra strain of his heart.
Well, I guess they weren't the same speed then, were they?
And it's Pentium 4, not Pentium IV.
Why?! I think it's a great practice. My phone company itemizes my bill, listing all the taxes and fees they have to pay. People bitch all the time about how the phone company is ripping them off, not realizing that like 25-30% of their bill goes directly to the government.
I think your gasoline bill should list all the taxes too. They now comprise, what, 60% of the price of gas at the pump?
Along the same lines, I also think the government should send you an income tax bill once a month, and everyone should be writing a big check equivalent to 3-4 months salary to pay it.
I don't see any problems with this. If the government requires a company to pay a special new tax, what do you propose the company do? Swallow the cost? They already have their margins. They can't just raise prices for no apparent reason. I think this is a great solution. You can raise the price to cover your costs and maintain margin, inform customers of what is going on, and point the blame at the government, because that's right where it belongs.
Transparency is a great thing. It shows how much things really cost, and why. If my phone bill goes up $2/month, with the money going to the government and me not seeing any phone service benefits, I want to know why, and I'd want to be reminded every month.
A well designed worm (or a virus for that matter) can pop up an important looking window saying something bad has happened on the system, please supply the root password to fix it. Haw many casual Linux users (if there are an?) do you think would fall for that? When you're running KDE or Gnome as a regular user, you'll get prompted for the root password when performing many system-type tasks. A smart worm could even wait for you to click on something before popping up, so that it doesn't appear as if it came out of nowhere.
No system is immune by design. Stupid or careless users are always crafty enough to bypass even the best security.
You seem to be confused with the terms. There is no such thing as a DNS Registrar. There are Root DNS Server Operators and there are Domain Registrars. You can't register DNS.
I think what you're getting at is that neither a domain registrar nor a TLD zone operator should run a root DNS server. And I would agree with that. I would go even further, and say that the three entities should be separated. Right now, Verisign runs a domain registry, controls the .com and .net TLDs, AND has a root DNS server.
Sure they'd take it, but are they willing to do what it takes to use it?
I see this suggestion every time the issue of handing over logs comes up.
In a general case, this won't happen. You need to keep logs around. For abuse resolution and tracking down offenders. If you bill per hour for dialup access, you need to keep radius logs. If you charge for IP services, you need to keep logs around to you can figure out who to charge. Anything related to billing you need to keep around for at least a month (and usually 2 or 3) to bill and audit properly, and to handle billing disputes. What do you do when you get rid of access logs after 3 days, and a month later your customer calls you up and says wtf is this charge on my bill?