I'd say we should open it wide- with the new hard drives coming out, all top level DNS servers should have 10 TB of space- and anybody who wants to can start a new TLD company
- Hard drives still cost money. - High performance computers still cost money. - Colocation and bandwidth still cost money. - Admins still cost money. - Redundant backup schemes still cost money. - 24x7x365.25 high availability still costs money.
Why should another company finance this for you?
The tree structure does work. It just doesn't work when: a) You do not want to pay for it or b) When someone else has the name you want.
And in those cases, you are just sweet out of luck. Try convincing your local office space rental to let you have an office and signage for free because there is so much office space around, and it really doesn't cost that much anyway. If you get free office space for life let me know, I obviously need to move my own business headquarters.
Did you know that Snake Oil is highly corrosive! In the future, as many as 10 out of 10 individuals could be semi-permanently scarred for a few years out of their life. Worse than that, Snake Oil is so pervasive, it COULD be on your property _right now_.
What a lot of corporate officers such as yourself do not know is that your typical indemnification insurance WILL NOT COVER SNAKE OIL BURNS! I 100% guarantee this. Ask your insurance, IT'S TRUE!
I am prepared today to offer you a 100% non-refundable insurance policy with a USD$1,000,000,000 (1 BILLION!) payout for the very SMALL premium amount of $1,000,000.
Ask yourself this: Are you prepared to let your company go bankrupt because you passed up this opportunity. Do the right thing, protect yourself, your employees and your company from Snake Oil burns.
For a limited time only, I am also willing to offer you the chance to resell this WONDERFUL investment on to your fellow corporate officers. Just send me a $1,000 signup fee, and you can become a registered agent. YOU TOO can sign other people up, and YOU KEEP THEIR SIGN UP FEE!
Act now, I am only offering these GREAT deals for a limited time.
Send email to buy@snakeoilinsurance.com to buy insurance and someone will call you back within 30 seconds GUARANTEED. We can activate the premium RIGHT AWAY as soon as your money order is received.
Send email to signup@snakeoilinsurance.com to sign up for our reselling program. After we secure funds, we will IMMEDIATELY send your reseller kit that contains all you need for step 1 of our FANTASTIC reseller program.
But in a world with choices, this kind of exposure should maybe impact yours, don't you think?
Absolutely.
When you are talking about using Microsoft software, you're paying every step of the way. You pay for the software, for the support, for the upgrades. You pay for everything. In return, you get the right to run software that is probably about as good as most of your other choices.
If someone chooses to accept that as their lot, then they should be prepared to keep the records required to ensure they can prove they are in compliance with their licensing agreements.
Personally, I do not think I could make the decision to use Microsoft software in a business and accept that fate. It is important to note, however, that this does not grant me the right to say "It's not possible to maintain these records!". It means I get to say "I am not able to maintain these records, and I should have chosen from amongst the alternatives..". That there is a rather large difference betwen the two statements should be obvious.
Like you said: In a world with choices, this kind of exposure should impact my choice.
Companies keep tax records for decades even though they only have to keep them for three years. Individuals keep their bank statements and purchase receipts for tax purposes. Why should you treat your software purchases any different if you know there is the possibility of an audit when you buy the software?
Saying that this is an impossible practice is like saying that surviving an IRS audit is not possible. If you are well prepared, were honest in the first place and have kept all your documents in order then you have nothing to fear.
On the other hand, if you skip a beat on any of those three things...
The thing with couterfeiting is that you don't have to make a perfect copy. In fact, very far from perfect would often be good enough. The reason is that you do not have to convince a currency expert that your copy is legit every time you use a counterfeit. You just have to convince the local convenience store clerk that your bill is real. And that's usually some 17 year old kid, by no means an expect.
Slight correction: A mars watch means it's easy to look at the time and think "2 martian hours until we can talk to the lander - time to go to work in 3 minutes, 15 seconds"
1 martian hour is equal to earth time: 01h 01m 37.5s
>>> What can be perhaps >>> the most annoying >>> thing on usenet and in >>> email, even more >>> annoying than >>> top posting? >> Bottom >> posting. > Why can > bottom posting > be such an > annoying > thing?
Because (usually) to find out what the final outcome is you have to go all the way to the bottom of the message to see what has been added. For some reason, most people do not remove the unnecessary cruft in previous emails, just moving to the bottom and adding their own information. Pretty soon, a single email is 5 pages long before you even get to the new content.
Admittedly, this is a problem with the poster, and not the post method, but it is just as annoying as top posting, and if you are following a thread, even more annoying, since you would have known what was going on even if they *were* top posting.
I usually do append my own post at the bottom of the original message... but to me, bottom posting without removing cruft is even more annoying than top posting.
It's no problem. The M179's are pretty much PVR-250's. You install the driver, it loads for both, and then you use/dev/video0 for one, and/dev/video1 for the other. Any calls you make to test_ioctl you have to add -d/dev/video[01] to so that they apply to that particular card.
It's really very simple... although I found the -d part not documented in any of the tutorials, but still, a quick query to #ivtv-dev on freenet cleared things up.
MythTV is not *THAT* hard to set up. I see people on the mailing list complaining about it all the time. And usually, the reply that gets them fixed is a pointer to the appropriate place in the documentation.
I have about six months work in my MythTV box, and I only got the parts a few weeks ago. I subscribed to the mailing list for about five months before I even attempted to start the project because I had heard stories of how horrendous it was to install. I printed out a hard copy of the documentation, and two different installation tutorials. Even after that, I read through all that about three times over.
Preparation is everything, I have found. You cant expect to have something of TiVo quality without putting in a lot of work your self. You have to remember that TiVo has employed a lot of people for a long time to get where it is, and it is very far from perfect as well.
About the best thing you can do to help yourself is to subscribe to the mailing list and learn from other peoples mistakes. Here's a hint in case you didn't already get it: The #1 mistake is not reading the documentation, which lists every dependancy that you need to fulfill.
If I were to be completely honest with myself, I would be forced to concede that nobody should ever build a MythTV machine because they think it will be cheaper. It probably wont be. In fact, 99.999% of the time if you are making a dedicated box it will not be. But if someone is looking for something they can change, something they can upgrade, something for a hobby, then THAT is the person who should use MythTV.
Personally, I don't regret a single minute that I've put into my MythTV box. If I did, I think I would have to question why I was doing it in the first place. IMHO, saving money is not a good enough reason.
Disclaimer: I did save money when I built my MythTV box. I managed to find a quiet dual proc PIII 633 for $100 and two AverMedia M179's for $50 a piece. That, after trying not to buy a PVR-250 for several months. Patience is indeed a virtue. Luckily, what I lack in patience I also lack in fiscal terms too.
I wasn't really trying to rant against debian, I guess... Redhat is no better with regards to that particular problem, I just knew my way around it better and had a better configuration guide to work from. I agree wholeheartedly with your synopsis of installing from source.
Apparently at the time i was doing a dist-upgrade (from a fresh install each time) there were libc updates in unstable that caused me all my grief.
You can't roll it back once its in place... which is one of my minor problems with.deb's. They know the version and they know which is latest. This is great so long as nothing goes wrong, but when it does, they flat-out refuse to let you install something older, which was my primary problem. I don't know if rpm is also affected by this... I've never wanted to rollback an rpm installation.
I must have net-installed about 20 times those few weeks, they never got the libc update fixed during that period, and I couldn't install the software I wanted in stable, so I went to redhat where rpms were available for the stock install.
If I ever go back to debian (and it could very well happen... redhat takes a *long* time to boot up even with a large percentage of services disabled) then I'll be sure to try out what you said.
First, some background. I've been using Linux on and off for about 5 years. I started off on Slackware, and in the middle I've been through SuSE, RedHat Linux 9.0, RedHat Linux 2.1 AS, and Mandrake.
I chose to try out debian about a month back. And sometimes, when I was compiling different programs, I would be missing a binary. So I would have to search google for the binary, then find the package it was in. After that, I would have to chance around trying to find the package name apt was referring to it as.
Now I know that I don't read documentation and the man pages enough. I've been told that apt-get and its associated programs have the things command line options needed to do all that without cracking open a web browser, if you read into the man pages far enough. And that was the kicker. If you read into the apt-get man pages far enough to find out that you should be reading the apt-cache man page and then read it far enough to find the appropriate command to search for the binary to find the package name.
You might say that I should have been using apt-get to get that software package originally. I'd agree, too. But to do that, you'd have to upgrade to testing, and have it not break when you did a dist-upgrade... and that seemed to be nigh on impossible when I was trying.
This kind of problem is not unique to apt. No matter what package delivery system you have, you need to have some kind of identifier with every package. Perhaps the search tools should be more obvious and easy to use?
That said, I've never used synaptic or aptitude... just the command line utilities.
For what its worth, I ended up uninstalling Debian. I was too much trouble for the guys in #debian on freenode to handle, and I couldn't solve my problems on my own. Redhat is now sitting on that particular box, and running very nicely.
Your view of the situation is flawed. Higher aircraft speed does not result in higher airport throughput; there is more involved in this equation than just the number of airplanes ready to land... number of runways, number of traffic controllers, amount of available airspace, number of terminals, baggage handling facilities... Obviously some of these matter more than others, but aircraft speed is not the primary bottle neck.
you better hope you win that battle... it's a LONG wait before someone can pick you up, ships are still very slow moving vehicles =)
This is of course assuming that the recon was not deployed until you were deployed, which would be insane, but consider this... what's the point of instant deployment if you still have to wait until the ships are almost there before you can deploy those "instant" troops?
Slashdot Mirror
I'd say we should open it wide- with the new hard drives coming out, all top level DNS servers should have 10 TB of space- and anybody who wants to can start a new TLD company
- Hard drives still cost money.
- High performance computers still cost money.
- Colocation and bandwidth still cost money.
- Admins still cost money.
- Redundant backup schemes still cost money.
- 24x7x365.25 high availability still costs money.
Why should another company finance this for you?
The tree structure does work. It just doesn't work when:
a) You do not want to pay for it
or
b) When someone else has the name you want.
And in those cases, you are just sweet out of luck. Try convincing your local office space rental to let you have an office and signage for free because there is so much office space around, and it really doesn't cost that much anyway. If you get free office space for life let me know, I obviously need to move my own business headquarters.
Yeah, all for the low price of your arm, leg and first born.
What were we talking about again? Oh, at that price, it must be gasoline!
Hey actually... that's a pretty good price right now for gasoline. Where are you getting your gasoline?
I have to pay a lung, a kidney and my first born. It was pretty horrific for the first gallon... can't wait to get the second gallon.
(By the way, where the hell is JPEG2000?)
Lost. Buried from head to toe in patents and license requirements. Honestly, I doubt it will ever be found.
AAAaaaaaaaaah!!!!!!!
Did you know that Snake Oil is highly corrosive! In the future, as many as 10 out of 10 individuals could be semi-permanently scarred for a few years out of their life. Worse than that, Snake Oil is so pervasive, it COULD be on your property _right now_.
What a lot of corporate officers such as yourself do not know is that your typical indemnification insurance WILL NOT COVER SNAKE OIL BURNS! I 100% guarantee this. Ask your insurance, IT'S TRUE!
I am prepared today to offer you a 100% non-refundable insurance policy with a USD$1,000,000,000 (1 BILLION!) payout for the very SMALL premium amount of $1,000,000.
Ask yourself this: Are you prepared to let your company go bankrupt because you passed up this opportunity. Do the right thing, protect yourself, your employees and your company from Snake Oil burns.
For a limited time only, I am also willing to offer you the chance to resell this WONDERFUL investment on to your fellow corporate officers. Just send me a $1,000 signup fee, and you can become a registered agent. YOU TOO can sign other people up, and YOU KEEP THEIR SIGN UP FEE!
Act now, I am only offering these GREAT deals for a limited time.
Send email to buy@snakeoilinsurance.com to buy insurance and someone will call you back within 30 seconds GUARANTEED. We can activate the premium RIGHT AWAY as soon as your money order is received.
Send email to signup@snakeoilinsurance.com to sign up for our reselling program. After we secure funds, we will IMMEDIATELY send your reseller kit that contains all you need for step 1 of our FANTASTIC reseller program.
Obviously the parent poster could afford it. At WalMart.
Get out into the sunlight and take off your tin-foil hat. Not all RFID is evil.
<Grammar Nazi>And learn to spell. No buts. Just do it</Grammar Nazi>
Go ahead, mod me down. I've got Karma to burn.
There's something just a little ironic about calling "Visual Basic for Applications" full power =)
It's astonishing that you can do anything useful in it, let alone write a virus in it.
But in a world with choices, this kind of exposure should maybe impact yours, don't you think?
Absolutely.
When you are talking about using Microsoft software, you're paying every step of the way. You pay for the software, for the support, for the upgrades. You pay for everything. In return, you get the right to run software that is probably about as good as most of your other choices.
If someone chooses to accept that as their lot, then they should be prepared to keep the records required to ensure they can prove they are in compliance with their licensing agreements.
Personally, I do not think I could make the decision to use Microsoft software in a business and accept that fate. It is important to note, however, that this does not grant me the right to say "It's not possible to maintain these records!". It means I get to say "I am not able to maintain these records, and I should have chosen from amongst the alternatives..". That there is a rather large difference betwen the two statements should be obvious.
Like you said: In a world with choices, this kind of exposure should impact my choice.
What is so hard about keeping boxes and receipts?
Companies keep tax records for decades even though they only have to keep them for three years. Individuals keep their bank statements and purchase receipts for tax purposes. Why should you treat your software purchases any different if you know there is the possibility of an audit when you buy the software?
Saying that this is an impossible practice is like saying that surviving an IRS audit is not possible. If you are well prepared, were honest in the first place and have kept all your documents in order then you have nothing to fear.
On the other hand, if you skip a beat on any of those three things...
and we LIKED it!
Sorry. There's always a chorus of people every time you hear that. Had to help.
The thing with couterfeiting is that you don't have to make a perfect copy. In fact, very far from perfect would often be good enough. The reason is that you do not have to convince a currency expert that your copy is legit every time you use a counterfeit. You just have to convince the local convenience store clerk that your bill is real. And that's usually some 17 year old kid, by no means an expect.
Hope this helps.
Slight correction:
A mars watch means it's easy to look at the time and think "2 martian hours until we can talk to the lander - time to go to work in 3 minutes, 15 seconds"
1 martian hour is equal to earth time: 01h 01m 37.5s
Real geeks don't have wives, they have palms. Ergo, you still do not qualify. Nice try though.
>>> What can be perhaps
>>> the most annoying
>>> thing on usenet and in
>>> email, even more
>>> annoying than
>>> top posting?
>> Bottom
>> posting.
> Why can
> bottom posting
> be such an
> annoying
> thing?
Because (usually) to find out what the final outcome is you have to go all the way to the bottom of the message to see what has been added. For some reason, most people do not remove the unnecessary cruft in previous emails, just moving to the bottom and adding their own information. Pretty soon, a single email is 5 pages long before you even get to the new content.
Admittedly, this is a problem with the poster, and not the post method, but it is just as annoying as top posting, and if you are following a thread, even more annoying, since you would have known what was going on even if they *were* top posting.
I usually do append my own post at the bottom of the original message... but to me, bottom posting without removing cruft is even more annoying than top posting.
YMMV.
It's no problem. The M179's are pretty much PVR-250's. You install the driver, it loads for both, and then you use /dev/video0 for one, and /dev/video1 for the other. Any calls you make to test_ioctl you have to add -d /dev/video[01] to so that they apply to that particular card.
It's really very simple... although I found the -d part not documented in any of the tutorials, but still, a quick query to #ivtv-dev on freenet cleared things up.
Seriously... what is your problem?
MythTV is not *THAT* hard to set up. I see people on the mailing list complaining about it all the time. And usually, the reply that gets them fixed is a pointer to the appropriate place in the documentation.
I have about six months work in my MythTV box, and I only got the parts a few weeks ago. I subscribed to the mailing list for about five months before I even attempted to start the project because I had heard stories of how horrendous it was to install. I printed out a hard copy of the documentation, and two different installation tutorials. Even after that, I read through all that about three times over.
Preparation is everything, I have found. You cant expect to have something of TiVo quality without putting in a lot of work your self. You have to remember that TiVo has employed a lot of people for a long time to get where it is, and it is very far from perfect as well.
About the best thing you can do to help yourself is to subscribe to the mailing list and learn from other peoples mistakes. Here's a hint in case you didn't already get it: The #1 mistake is not reading the documentation, which lists every dependancy that you need to fulfill.
If I were to be completely honest with myself, I would be forced to concede that nobody should ever build a MythTV machine because they think it will be cheaper. It probably wont be. In fact, 99.999% of the time if you are making a dedicated box it will not be. But if someone is looking for something they can change, something they can upgrade, something for a hobby, then THAT is the person who should use MythTV.
Personally, I don't regret a single minute that I've put into my MythTV box. If I did, I think I would have to question why I was doing it in the first place. IMHO, saving money is not a good enough reason.
Disclaimer: I did save money when I built my MythTV box. I managed to find a quiet dual proc PIII 633 for $100 and two AverMedia M179's for $50 a piece. That, after trying not to buy a PVR-250 for several months. Patience is indeed a virtue. Luckily, what I lack in patience I also lack in fiscal terms too.
Thanks, I appreciate your insight.
.deb's. They know the version and they know which is latest. This is great so long as nothing goes wrong, but when it does, they flat-out refuse to let you install something older, which was my primary problem. I don't know if rpm is also affected by this... I've never wanted to rollback an rpm installation.
I wasn't really trying to rant against debian, I guess... Redhat is no better with regards to that particular problem, I just knew my way around it better and had a better configuration guide to work from. I agree wholeheartedly with your synopsis of installing from source.
Apparently at the time i was doing a dist-upgrade (from a fresh install each time) there were libc updates in unstable that caused me all my grief.
You can't roll it back once its in place... which is one of my minor problems with
I must have net-installed about 20 times those few weeks, they never got the libc update fixed during that period, and I couldn't install the software I wanted in stable, so I went to redhat where rpms were available for the stock install.
If I ever go back to debian (and it could very well happen... redhat takes a *long* time to boot up even with a large percentage of services disabled) then I'll be sure to try out what you said.
First, some background.
I've been using Linux on and off for about 5 years. I started off on Slackware, and in the middle I've been through SuSE, RedHat Linux 9.0, RedHat Linux 2.1 AS, and Mandrake.
I chose to try out debian about a month back. And sometimes, when I was compiling different programs, I would be missing a binary. So I would have to search google for the binary, then find the package it was in. After that, I would have to chance around trying to find the package name apt was referring to it as.
Now I know that I don't read documentation and the man pages enough. I've been told that apt-get and its associated programs have the things command line options needed to do all that without cracking open a web browser, if you read into the man pages far enough. And that was the kicker. If you read into the apt-get man pages far enough to find out that you should be reading the apt-cache man page and then read it far enough to find the appropriate command to search for the binary to find the package name.
You might say that I should have been using apt-get to get that software package originally. I'd agree, too. But to do that, you'd have to upgrade to testing, and have it not break when you did a dist-upgrade... and that seemed to be nigh on impossible when I was trying.
This kind of problem is not unique to apt. No matter what package delivery system you have, you need to have some kind of identifier with every package. Perhaps the search tools should be more obvious and easy to use?
That said, I've never used synaptic or aptitude... just the command line utilities.
For what its worth, I ended up uninstalling Debian. I was too much trouble for the guys in #debian on freenode to handle, and I couldn't solve my problems on my own. Redhat is now sitting on that particular box, and running very nicely.
Cock-bite
I'm shocked! Shocked! To find that gambling is going on here...
By the look of comments so far, there seem to be quite a few people with malfunctioning sarcasm sensors today.
So, for the sensor deprived: Wrap the entire text in a <SARCASM> tag, and you'll be able to enjoy it much more fully.
wee bit smaller? You're looking at it the wrong way...
It's a lot smaller. As in half the size.
12cm^2 = 12cm x 12cm = 144
17cm^2 = 17cm x 17cm = 289
To me, 50% reduction in total board size is more than just a wee bit. Personally I find it pretty impressive.
Via does. It's the EPIA-CL. When the mini-itx link comes back online, scroll down the page and you'll find it.
Your view of the situation is flawed. Higher aircraft speed does not result in higher airport throughput; there is more involved in this equation than just the number of airplanes ready to land... number of runways, number of traffic controllers, amount of available airspace, number of terminals, baggage handling facilities... Obviously some of these matter more than others, but aircraft speed is not the primary bottle neck.
HTH
you better hope you win that battle... it's a LONG wait before someone can pick you up, ships are still very slow moving vehicles =)
This is of course assuming that the recon was not deployed until you were deployed, which would be insane, but consider this... what's the point of instant deployment if you still have to wait until the ships are almost there before you can deploy those "instant" troops?