Back in the day there was a game called TypeTrek that I think was the same idea. Text based graphics, though (I played it on an 8088 with an amber monitor).
My experience repairing high end video production equipment disagrees, and I see no reason why FM radio would be an exception.
If you live in the LA area you can see what I mean any day on the channel 7 news. They now have a helicopter equiped with HD cameras, and the quality difference is quite noticable, even through an SD signal.
I very much doubt that the difference isn't perceptable. The audience might not know any better, or they might not blame you, or they might not care, but I'm quite sure that if they listened to both in a "side by side" comparison that most would notice a difference.
By comparison, in the Linux world Novell forces you to purchase Red Carpet update service for the same feature, and I believe Red Hat does the same with RHEL.
And if they then ignore the customers choice, they aren't ready for the enterprise either.
But, for the record, you can uncheck updates you don't want in YOU just fine without Red Carpet.
These are small and medium sized businesses. Most of them don't have IT managers or CIOs. Most of them don't even have an IT guy. If they're lucky, they might have a "guy who knows some stuff", but in reallity most of them just buy whatever Staples has on sale and take it in to the closest computer shop when it finally collapses under the weight of all the viruses and malware it's accumulated.
It should come as no suprise that these companies haven't thought about switching, and the reasons for that are quite simple, and have absolutely nothing to do with the capabilities or qualities of Linux.
It's an alternative solution to the same problem the programmable VCR is aimed at: time-shifting TV shows.
The technology it uses to accomplish this is called Digital Disk Recording in the broadcasting world, and leverages Linux and commodity hardware (more technologies) to bring the price down to consumer level, and network technology to automate its scheduling.
Maybe the US won't wind up being the complete totalitarian militant theocracy it looks like they are aiming for but it's not the place it used be 15 to 25 years ago.
You're right, it isn't that same place it was, and the reason is that in that time (really, since the 1970's) the theocrats have found their power slowly slipping away.
The US today is less of a theocracy than it has ever been. The reason you hear so much noise from the theocrats today is because they're trying to hold back the tide. Back when they really had the power, they didn't have to make any noise about it.
Well, it's going to be/dev/ttyUSBsomething, and that depends entirely on your setup (eg other usb devices, and the whims of your hotplug system). Whatever it is, though, it will most likely at least be consistent.
Mine is/dev/ttyUSB1.
Now, I use kpilot on SuSE 9.1, and now 9.3, with an m505. IIRC, what I did when I got it was start at ttyUSB0 and work my way up until it worked (note that it won't actually see the device until you hit its hotsynch button). You may have to play with the speed settings too, I don't remember, but mine is set to the highest speed and works fine.
Last few things:
1) Whoever told you it would only work with/dev/pilot didn't know what they were talking about, though you could do that to make things clearer, especially several months down the road when you're trying to remember what you did (like I am now). It's entirely up to you.
2) Fedora may use different naming conventions for their usb ttys, I don't use it so I don't know. I'd start with/dev/ttyUSB*, and if it isn't there (or they don't exist), try/dev/USB*. Remember about the hotsynch button though, it won't work no matter what you do if you don't push the button.
But hey, if you don't think it's valid feel free to try it yourself.
you cant supress the truth forever.
The truth is that you'd have to be a fscking idiot to try and take on the GPL in court. That's obvious to anyone who's read it and has even a basic understanding of copyright law (clearly, this group does not include you).
Frequent temperature change can cause stress fractures in solder joints as well.
It may seem like it wouldn't make a difference at such a small scale, but you have to remember that the tolerances are proportionally tighter as well. Fine pitch parts and BGAs don't have a lot of solder holding them down, and a drive platter spinning at 7200 or 10k RPM with a read head flying a microscopic distance above it needs to have a very smooth ride.
Power-up is the most stressful time for your hardware, especially components with moving parts.
I had some test servers at my last job that were very reliable if you left them running, but when they did go down (like when we had some problems with our UPS. Ouch!) we'd have to smack them on the side to get the HDDs to spin up again.
A big part of the job was testing replacement drives for video servers (think $100k Tivo for a TV station). We found that, as they get older, 73GB Cheetah IVs start drawing a lot more power when they spin up, and we started getting a lot of failures with these drives. In all honesty it was really a problem with the design of the power supply for the RAID chassis we were using, but it only showed up with that one model.
I hate Microsoft because I love the Free Market, which requires competition to function properly. I hate Microsoft because they've acheived their postion through FUD attacks and overbearing force rather than by providing a superior product. I hate Microsoft because of their ruthless competitiveness and their refusal to play nice with the rest of the industry. I hate Microsoft because I do not believe that the ends justify the means.
He's not redistributing, he's installing it on multiple machines belonging to the purchasing entity.
Now, as for reading the FAQ, here's what I found:
Except for a few components provided by third parties (like Java) all the code in Red Hat products is open source and licensed under the GPL (or a similar license, such as the LGPL).
So, according to that, all code that's copyright Red Hat is GPL compatable.
Again, the subscription is for support, not the software itself.
Actually, I'm offended by your taking offense. His point is entirely valid, regardless of your feelings about any comparisons you imagine were made.
If you want a less inflamatory example, though, how about seatbelt laws? In California it's illegal to not where a seatbelt while riding in a car, but can you honestly argue that it's wrong? ("stupid" is not the same as "wrong" either, btw)
As for a discussion of rights, well, I have a natural right to use any idea I come in contact with in any way I see fit. The musician's (or other creator's) "right" to profit from that idea is a completely artificial construct, so I'm afraid you're ultimately on the losing side of that argument.
Now, having said that, I feel I should point out that I choose not to engage in copyright infringement, as I believe paying for things I like is the best way for me to get more of the sort of things I like. However, as a musician myself, I'm very much aware that the person I'm really paying is the middleman, and the reason I'm paying him is that he was kind enough to do the hard work for me (listening to thousands of bands that suck, and recording and distributing the few that don't, and finding a way to let me know about it).
Musicians don't make money from album sales, so any discussion of why copyright infringement is wrong based on a musician's right to eat is fundamentally flawed.
Your UID indicates that you've been around long enough to have read Courtney Love's unusually coherent speech on the subject from a few years ago. If you haven't, you really should.
And finally, artists don't stop creating just because they aren't making any money at it. You can be sure that anyone who tries to tell you so is a middlemen, trying to protect his profit stream, not an artist.
It isn't a license subscription, it's a support subscription.
Pay up for one system, like you say you plan to, and just install it anywhere else you need it from whatever media they give you. Just understand that you've only paid for support for one system.
Honestly, try reading the GPL before you ask stupid Linux licensing questions like this.
I think it was cut badly, and consequently hard to follow. I wouldn't have been able to follow it if I hadn't read the book. I don't believe a giant in-joke makes for a good movie, even when I'm in on it.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
Seems to my inexperienced legal eye that the GPL does, in fact, force me to give away my software for free.
You're suffering from BSA brainwashing, I think. You see, the GPL only deals with copyright as defined by law, and there is nothing in copyright law that supports the concept of a "license to use". The ONLY kind of license copyright law, and the GPL, deals with is a license to copy and distribute (aka publishing).
You can sell GPLed software for any price you like (within the bounds of law, anyway, so no "first-born" or "female virgin sex-slaves"), even if you didn't write it. What that clause means is that IF you find someone willing to pay your price you may not CHARGE EXTRA for the rights to republish said GPLed software.
Your mistake is in thinking that EULAs have any basis in copyright law. Again, there is no such thing in copyright law as an "end user license".
Slashdot Mirror
Back in the day there was a game called TypeTrek that I think was the same idea. Text based graphics, though (I played it on an 8088 with an amber monitor).
Googling for it turns up nothing useful, though.
My experience repairing high end video production equipment disagrees, and I see no reason why FM radio would be an exception.
If you live in the LA area you can see what I mean any day on the channel 7 news. They now have a helicopter equiped with HD cameras, and the quality difference is quite noticable, even through an SD signal.
I very much doubt that the difference isn't perceptable. The audience might not know any better, or they might not blame you, or they might not care, but I'm quite sure that if they listened to both in a "side by side" comparison that most would notice a difference.
Any quality loss is compounded, not hidden, by additional quality loss.
By comparison, in the Linux world Novell forces you to purchase Red Carpet update service for the same feature, and I believe Red Hat does the same with RHEL.
And if they then ignore the customers choice, they aren't ready for the enterprise either.
But, for the record, you can uncheck updates you don't want in YOU just fine without Red Carpet.
piloted, perhaps, by kittens.
I suppose that would make fapping in a time of war an act of treason...
These are small and medium sized businesses. Most of them don't have IT managers or CIOs. Most of them don't even have an IT guy. If they're lucky, they might have a "guy who knows some stuff", but in reallity most of them just buy whatever Staples has on sale and take it in to the closest computer shop when it finally collapses under the weight of all the viruses and malware it's accumulated.
It should come as no suprise that these companies haven't thought about switching, and the reasons for that are quite simple, and have absolutely nothing to do with the capabilities or qualities of Linux.
Except Tivo isn't a solution or a technology
Yes it is.
It's an alternative solution to the same problem the programmable VCR is aimed at: time-shifting TV shows.
The technology it uses to accomplish this is called Digital Disk Recording in the broadcasting world, and leverages Linux and commodity hardware (more technologies) to bring the price down to consumer level, and network technology to automate its scheduling.
Maybe the US won't wind up being the complete totalitarian militant theocracy it looks like they are aiming for but it's not the place it used be 15 to 25 years ago.
You're right, it isn't that same place it was, and the reason is that in that time (really, since the 1970's) the theocrats have found their power slowly slipping away.
The US today is less of a theocracy than it has ever been. The reason you hear so much noise from the theocrats today is because they're trying to hold back the tide. Back when they really had the power, they didn't have to make any noise about it.
Good to drink, but bad for keyboards. She takes out about one a year (one just last night, in fact.)
I would have just made the guilty party buy me a new one.
Easier for you, valuable lesson about respecting other peoples stuff for them, and the freqency of this happening would be dramatically reduced.
And if they don't have the money, make them work it off a minimum wage rates.
(And yes, I am a parent)
Except that if you do her, you're also doing an old man.
That might not be so bad. She'd certainly know what a man likes...
Well, it's going to be /dev/ttyUSBsomething, and that depends entirely on your setup (eg other usb devices, and the whims of your hotplug system). Whatever it is, though, it will most likely at least be consistent.
/dev/ttyUSB1.
/dev/pilot didn't know what they were talking about, though you could do that to make things clearer, especially several months down the road when you're trying to remember what you did (like I am now). It's entirely up to you.
/dev/ttyUSB*, and if it isn't there (or they don't exist), try /dev/USB*. Remember about the hotsynch button though, it won't work no matter what you do if you don't push the button.
Mine is
Now, I use kpilot on SuSE 9.1, and now 9.3, with an m505. IIRC, what I did when I got it was start at ttyUSB0 and work my way up until it worked (note that it won't actually see the device until you hit its hotsynch button). You may have to play with the speed settings too, I don't remember, but mine is set to the highest speed and works fine.
Last few things:
1) Whoever told you it would only work with
2) Fedora may use different naming conventions for their usb ttys, I don't use it so I don't know. I'd start with
who has been sued and lost ?
Sitecom, in a German court.
But hey, if you don't think it's valid feel free to try it yourself.
you cant supress the truth forever.
The truth is that you'd have to be a fscking idiot to try and take on the GPL in court. That's obvious to anyone who's read it and has even a basic understanding of copyright law (clearly, this group does not include you).
I just make sure to leave an empty slot above and below the drive for airflow. No need for dedicated fans, IMO.
I've been building machines for friends and family for almost 10 years now, and only had one drive fail.
Frequent temperature change can cause stress fractures in solder joints as well.
It may seem like it wouldn't make a difference at such a small scale, but you have to remember that the tolerances are proportionally tighter as well. Fine pitch parts and BGAs don't have a lot of solder holding them down, and a drive platter spinning at 7200 or 10k RPM with a read head flying a microscopic distance above it needs to have a very smooth ride.
Power-up is the most stressful time for your hardware, especially components with moving parts.
I had some test servers at my last job that were very reliable if you left them running, but when they did go down (like when we had some problems with our UPS. Ouch!) we'd have to smack them on the side to get the HDDs to spin up again.
A big part of the job was testing replacement drives for video servers (think $100k Tivo for a TV station). We found that, as they get older, 73GB Cheetah IVs start drawing a lot more power when they spin up, and we started getting a lot of failures with these drives. In all honesty it was really a problem with the design of the power supply for the RAID chassis we were using, but it only showed up with that one model.
I hate Microsoft because I love the Free Market, which requires competition to function properly. I hate Microsoft because they've acheived their postion through FUD attacks and overbearing force rather than by providing a superior product. I hate Microsoft because of their ruthless competitiveness and their refusal to play nice with the rest of the industry. I hate Microsoft because I do not believe that the ends justify the means.
He's not redistributing, he's installing it on multiple machines belonging to the purchasing entity.
Now, as for reading the FAQ, here's what I found:
Except for a few components provided by third parties (like Java) all the code in Red Hat products is open source and licensed under the GPL (or a similar license, such as the LGPL).
So, according to that, all code that's copyright Red Hat is GPL compatable.
Again, the subscription is for support, not the software itself.
Ah, yes. The two situations are exactly the same.
Oh, except for that on the hardware side there are several roughly equal competitors, while while the software side is essentially a monopoly.
But yeah, other than that, it's exactly the same!
He's been around long enough to know better.
What's more shocking, though, is that I was the first person to suggest that. I mean I was what, the 90th post?
Actually, I'm offended by your taking offense. His point is entirely valid, regardless of your feelings about any comparisons you imagine were made.
If you want a less inflamatory example, though, how about seatbelt laws? In California it's illegal to not where a seatbelt while riding in a car, but can you honestly argue that it's wrong? ("stupid" is not the same as "wrong" either, btw)
As for a discussion of rights, well, I have a natural right to use any idea I come in contact with in any way I see fit. The musician's (or other creator's) "right" to profit from that idea is a completely artificial construct, so I'm afraid you're ultimately on the losing side of that argument.
Now, having said that, I feel I should point out that I choose not to engage in copyright infringement, as I believe paying for things I like is the best way for me to get more of the sort of things I like. However, as a musician myself, I'm very much aware that the person I'm really paying is the middleman, and the reason I'm paying him is that he was kind enough to do the hard work for me (listening to thousands of bands that suck, and recording and distributing the few that don't, and finding a way to let me know about it).
Musicians don't make money from album sales, so any discussion of why copyright infringement is wrong based on a musician's right to eat is fundamentally flawed.
Your UID indicates that you've been around long enough to have read Courtney Love's unusually coherent speech on the subject from a few years ago. If you haven't, you really should.
And finally, artists don't stop creating just because they aren't making any money at it. You can be sure that anyone who tries to tell you so is a middlemen, trying to protect his profit stream, not an artist.
It isn't a license subscription, it's a support subscription.
Pay up for one system, like you say you plan to, and just install it anywhere else you need it from whatever media they give you. Just understand that you've only paid for support for one system.
Honestly, try reading the GPL before you ask stupid Linux licensing questions like this.
I think it was cut badly, and consequently hard to follow. I wouldn't have been able to follow it if I hadn't read the book. I don't believe a giant in-joke makes for a good movie, even when I'm in on it.
I'm hoping for a director's cut.
Section 2B of the GPL:
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
Seems to my inexperienced legal eye that the GPL does, in fact, force me to give away my software for free.
You're suffering from BSA brainwashing, I think. You see, the GPL only deals with copyright as defined by law, and there is nothing in copyright law that supports the concept of a "license to use". The ONLY kind of license copyright law, and the GPL, deals with is a license to copy and distribute (aka publishing).
You can sell GPLed software for any price you like (within the bounds of law, anyway, so no "first-born" or "female virgin sex-slaves"), even if you didn't write it. What that clause means is that IF you find someone willing to pay your price you may not CHARGE EXTRA for the rights to republish said GPLed software.
Your mistake is in thinking that EULAs have any basis in copyright law. Again, there is no such thing in copyright law as an "end user license".
Naturally, NOW would be the time I suddenly DON'T have modpoints.