This is exactly what the RIAA is claiming P2P file sharing is doing to artists. Using an an artist's copyrighted material without paying for the privelidge of that use.
Seems amazingly clear to me - a "textbook" example of what the RIAA is trying to prevent.
MS has already won; every copy of I.E. 5.5 and 6.0 use Microsoft's search by default. Even finding were to reset your search preferences is a challenge.
As proof of how effective this tactic is, I'd like to offer that a number of my co-workers (knowledge workers, but not particularly computer literate) Just assume that the IE search returns the best set of results for thier needs. Several of them never even try other search engines any more.
IANAL, but I wouldn't think it does directly. The files on a Samba volume are stored in the file system format of the server, ext3/JFS for example. The client software is the actual OS of the client PC, usually a Windows 9x variant.
The end result is that you (typically) have a Windows 9x PC reading its local file system or attached device (the FAT/FAT32 access) and sending and retreiving data through the network stack(s) to the server where the data is translated and stored as etc3/JFS or similar.
The only way Samba could be affected is if it bypassed the kernel and file system software to access a pluged in device directly. I'm pretty sure that code doesn't exist within the boundaries of the project.
How will DRM email respond to being opened in 'nix clients? Also, since I assume the "document viewer" will be a Windows program, will it run under WINE (or some such)?
The answers to these questions would be interesting. Office 2003 may well make using 'nix desktops in a MS 2003 shop more dificult. It may also keep Office 2003 out of existing mixed environments.
Anytime you have fanatical idealism without objective questioning of the movement's goals from within, you have a dangerous combination.
Fortunately, I don't believe the Open Source and Free Software movements fit the above model. There are too many people involved with too many different sets of goals. If all Open Source and Free Software projects were controlled by a single individual (they are not), and that individual had a fanatical agenda, I would be much more concerned.
Unfortunately, Rob Enderle (the author) seems to believe that every loud, rude noise is a gunshot.
I'm a long time Mandrake user who loaded 8.2 on my (home) server; it's been solid so I've left it running.
With the 9.2 comming out, I figured it was time to upgrade. Interestingly, when I went to find all those spiffy docs pages that I used to set up and configure my 8.2 set-up it turns out they are now all "hidden" behind the walls of the pay-to-play "club" website.
This really bothers me; it seems completely opposit of what the open source movement is about. Convoluted really - "Have a free bottle of beer, but we'll charge you for sitting and talking with your friends..." or perhaps "Here's the source code, but I have to charge you to talk about it..." I can respect the need for MandrakeSoft to make money, but I can say this hasn't increased my desire to become a club member. It's just so.. slimy..
Even Mirosoft lets users access their technical info database without cost.
Um.. yeah. I can't think of anything buy or use on a regular basis that I'm paying less for now than I was a year ago (Except perhaps free software, once adjusted for inflation).
Even though I've had the same cell phone service package for the last 5+ years it seems to get more expensive every year - new fees (and taxes). If you call and ask your carier what they are for you usually get really vage answers or an "I don't know", too.
I do agree that this will open up competition and ultimately hellp keep overall pricing lower, though.
I've been wanting to change carriers for about 2 years now, but keeping the old line active for a year (with a my new number is message) isn't appealing to me. Many of the people who have my number are important to me, but infrequent callers.
Your IP portability comparision is bunk - there is already a layer between an IP and a domain name - DNS. It provides for the portability of domain names. The proposed regulation esentially ensures that your phone number becomes as portable as a domain name is now. That makes sense to me; both your domain name and your phone number are how other "end users" reach you.
That's exactly on target! A good example of this is a project I was asked to become involved with a couple of years ago. The client needed a small, not-too complex database to track and report on customers going through a training program that included a social services component.
When I was first asked into the project I was shown a "waterfall" application that another firm had developed for them that was over budget and significantly failed to meet the business need. I was asked to re-estimate the project and determine between saving and scrapping the failed code. Considering the falied app only aligned with about 30% of the specified need, we chose to dump the app.
Of course by now alarm bells are going off inside my brain (how can a vendor land that far off target, etc.) and I start to do some digging. It turns out that the vendor they selected was fairly inexperienced, but more importantly the product had been produced using an estimate of about 1/4 the cost estimated by a far more experienced firm, and much closer to my own expectations. Even further digging turned up that the client didn't even have a firm grip on the details of internal the process they were trying to automate. Process changes and adjustments were ongoing, and asside from a few key elements, virtually everything else was subject to "interpretive need"; meaning the rule was whatever best suited the audience or need at the moment.
Of course the new client was hoping I could find a magic wand and produce their project while meeting the unrealistic proposal of the less expensive vendor in this environment. Eventually I was able to develop a product that met the bulk of their need; but it was done with the understanding that until they clearly defined their needs, development and adjustments would need to be ongoing.
The project has been ongoing for almost 2 years now, and meets about 95% of the business needs. About 35% of the development has been part time, as we have figured out what they really want (and need). The remaining needs have been defined and are being developed for as they define the busniess rules.
The point to all this being that many times the client doesn't understand their own needs well enough to provide a spec that can be developed to. If you can't understand the problem fully, it's tough to produce an estimate for a solution.
I've seen plenty of methodologies that say something similiar to "at point X you can estimate to Y hours (or dollars), +/-100%"; that may be true, but it's a tough sell. In the world of small business, most customers would call that "bunk".
I agree with where you are going, but only up to a point. My most responsible users have the Outlook preview window turned off, don't open attachments from senders they don't know, if they think it might be legitimate email know to right-click and scan first, ask about (or forward a copy) of any suspicious emails received, etc. They also don't install spy/add/mal-ware, 3 different IM clients and whatever "cool" new download is making the rounds. And they behave like that in Windows. Preventing "bad" users from doing this simply takes locking down and pre-configuring their desktop and apps. It's not really any harder to do under Windown than it is under 'nix. I will agree that Windows should default into a more secure configuration, however. The same can be said of most Windows software, too.
My point was, while there will be technical differences in how a virus infection plays out in a 'nix environment, the same people are likely cause the same problems. The only reliable way to prevent those problems is to remove user privileges; that can be largely accomplished in Windows as easily as it can be in 'nix. The problem is that many organizations (mine included) don't really want to have user PCs locked down that tightly; it forces a call to IT every time a user needs to change their workstation environment. Giving them SU wouldn't help; they'd use it to install the things they do now in Windows without it.
If a PC does become infected, I can completely re-load a workstation in 30 to 45 minutes, unattended, with apps and all. It only requires a few initial keystrokes; just wipe and reload. Even the user's desktop, shortcuts, documents, etc. will be restored. This minimizes the overall impact of an infected PC. Unfortunately there is no perfect way to prevent virus infections and other exploits. Just keep the defs and patches up to date, scan everything, try to make sure you are only running minimum needed services, and your keep firewall tight.
The end result is that I believe that against a specific "new" attack, I'm no better or worse off than anyone else. Given comparable user control of the target PC, a shiny new 'nix exploit would be just as likely to land (ignoring all the 'nix flavor variation issues) as a shiny new Windows exploit would, given the same user base. The 'nix flavor issue is essentially security through obscurity; it works, but I don't consider it a reliable core strategy. How many organizations with centrally managed 'nix desktops officially support more than one 'nix desktop flavor in house?
The subject line above pretty much covers all of the article's "social engineering" blah blah. As an IS/IT manager I can assure you that no amount of click boxes, pop-up warnings, etc. will prevent some users from doing "bad things" (tm).
As for the author's technical reasons; please see above. Most of the people who click and/or view every e-mail they shouldn't are also the ones who install every bit of spy/add/mal-ware, etc. onto their PCs, and run as root. PCs are just so easy to use that way.
Right now most of those users wouldn't even dream of trying to wrestle with a 'nix variant; nothing "just works". Once stuff really does "just work" they'll be able to commit all of their same bad behaviors quickly and easily in a shiny new OS.
Some will find that the limitation will relate to having an older version of Mandrake Linux, unintentionally, I'm sure. The available Bit Torrent RPMs for ML will not install on older versions (ML 9.1 or older) without slogging through dependency upgrades.
Enough already - we all know the RIAA is wrong!
on
The Effect of Pirated CDs
·
· Score: 3, Insightful
A simple, real world example is me. I don't download MP3s to fill my music collection, but I did used to download a few to check our new bands recomended by friends. Those usually led to me buying new CDs. I used to buy quite a few more CDs than I do now. To be honest, over the last 3 years: broadcast radio has gone into the toilet (no new music & lousy selection), CD prices have gone up (they were already expensive), money is much tighter than it used to be, and my life has changed; I'm now more likely to spend money on my house/cars/kids/etc. than the overpriced CDs I would have bought a few years ago. Another big FYI; my parents are also buying fewer vinyl albums and tapes than they did 20 years ago! My kids are buying fewer CDs than I did tapes at their age; but they're not downloading either. My oldest daughter actually listens to much of the stuff I do - stuff released 10 years ago. Her thoughts are the same; there is very little good new music hitting the stores.
Would the modchip view be changed if the PS/2 was successfully argued to be a full fledged computer? IANAL, and have no idea what the legality of this might bring; but I'm pretty sure Dell doesn't have the right to limit what software you run...
While mass automation may give us the time to inovate, it will all be for naught unless the current trends in IP law change.
I predict within the next years virtually every bit of "new" or common knowledge will be locked down by big money and IP law. Inovate and get sued!
Perhaps we'll all end up reading Slashdot archives:)
Slashdot Mirror
This is exactly what the RIAA is claiming P2P file sharing is doing to artists. Using an an artist's copyrighted material without paying for the privelidge of that use.
Seems amazingly clear to me - a "textbook" example of what the RIAA is trying to prevent.
All the enviro problems of regular PCs + the added damage of un-needed wood siding. Great...
Makes a sick sort of sense to me - SCO looses, then you sue them for whatever IBM & RedHad leve as leftovers...
Oh wait, there might not be anything left...
MS has already won; every copy of I.E. 5.5 and 6.0 use Microsoft's search by default. Even finding were to reset your search preferences is a challenge.
As proof of how effective this tactic is, I'd like to offer that a number of my co-workers (knowledge workers, but not particularly computer literate) Just assume that the IE search returns the best set of results for thier needs. Several of them never even try other search engines any more.
IANAL, but I wouldn't think it does directly. The files on a Samba volume are stored in the file system format of the server, ext3/JFS for example. The client software is the actual OS of the client PC, usually a Windows 9x variant. The end result is that you (typically) have a Windows 9x PC reading its local file system or attached device (the FAT/FAT32 access) and sending and retreiving data through the network stack(s) to the server where the data is translated and stored as etc3/JFS or similar. The only way Samba could be affected is if it bypassed the kernel and file system software to access a pluged in device directly. I'm pretty sure that code doesn't exist within the boundaries of the project.
How will DRM email respond to being opened in 'nix clients? Also, since I assume the "document viewer" will be a Windows program, will it run under WINE (or some such)?
The answers to these questions would be interesting. Office 2003 may well make using 'nix desktops in a MS 2003 shop more dificult. It may also keep Office 2003 out of existing mixed environments.
Anytime you have fanatical idealism without objective questioning of the movement's goals from within, you have a dangerous combination.
Fortunately, I don't believe the Open Source and Free Software movements fit the above model. There are too many people involved with too many different sets of goals. If all Open Source and Free Software projects were controlled by a single individual (they are not), and that individual had a fanatical agenda, I would be much more concerned.
Unfortunately, Rob Enderle (the author) seems to believe that every loud, rude noise is a gunshot.
I'm a long time Mandrake user who loaded 8.2 on my (home) server; it's been solid so I've left it running.
With the 9.2 comming out, I figured it was time to upgrade. Interestingly, when I went to find all those spiffy docs pages that I used to set up and configure my 8.2 set-up it turns out they are now all "hidden" behind the walls of the pay-to-play "club" website.
This really bothers me; it seems completely opposit of what the open source movement is about. Convoluted really - "Have a free bottle of beer, but we'll charge you for sitting and talking with your friends..." or perhaps "Here's the source code, but I have to charge you to talk about it..." I can respect the need for MandrakeSoft to make money, but I can say this hasn't increased my desire to become a club member. It's just so .. slimy ..
Even Mirosoft lets users access their technical info database without cost.
Um .. yeah. I can't think of anything buy or use on a regular basis that I'm paying less for now than I was a year ago (Except perhaps free software, once adjusted for inflation).
Even though I've had the same cell phone service package for the last 5+ years it seems to get more expensive every year - new fees (and taxes). If you call and ask your carier what they are for you usually get really vage answers or an "I don't know", too.
I do agree that this will open up competition and ultimately hellp keep overall pricing lower, though.
I've been wanting to change carriers for about 2 years now, but keeping the old line active for a year (with a my new number is message) isn't appealing to me. Many of the people who have my number are important to me, but infrequent callers.
Your IP portability comparision is bunk - there is already a layer between an IP and a domain name - DNS. It provides for the portability of domain names. The proposed regulation esentially ensures that your phone number becomes as portable as a domain name is now. That makes sense to me; both your domain name and your phone number are how other "end users" reach you.
II don't download music; I buy it from used CD stores! And if you pay cash they never ask for your license...
When I was first asked into the project I was shown a "waterfall" application that another firm had developed for them that was over budget and significantly failed to meet the business need. I was asked to re-estimate the project and determine between saving and scrapping the failed code. Considering the falied app only aligned with about 30% of the specified need, we chose to dump the app.
Of course by now alarm bells are going off inside my brain (how can a vendor land that far off target, etc.) and I start to do some digging. It turns out that the vendor they selected was fairly inexperienced, but more importantly the product had been produced using an estimate of about 1/4 the cost estimated by a far more experienced firm, and much closer to my own expectations. Even further digging turned up that the client didn't even have a firm grip on the details of internal the process they were trying to automate. Process changes and adjustments were ongoing, and asside from a few key elements, virtually everything else was subject to "interpretive need"; meaning the rule was whatever best suited the audience or need at the moment.
Of course the new client was hoping I could find a magic wand and produce their project while meeting the unrealistic proposal of the less expensive vendor in this environment. Eventually I was able to develop a product that met the bulk of their need; but it was done with the understanding that until they clearly defined their needs, development and adjustments would need to be ongoing.
The project has been ongoing for almost 2 years now, and meets about 95% of the business needs. About 35% of the development has been part time, as we have figured out what they really want (and need). The remaining needs have been defined and are being developed for as they define the busniess rules.
The point to all this being that many times the client doesn't understand their own needs well enough to provide a spec that can be developed to. If you can't understand the problem fully, it's tough to produce an estimate for a solution.
I've seen plenty of methodologies that say something similiar to "at point X you can estimate to Y hours (or dollars), +/-100%"; that may be true, but it's a tough sell. In the world of small business, most customers would call that "bunk".
I agree with where you are going, but only up to a point. My most responsible users have the Outlook preview window turned off, don't open attachments from senders they don't know, if they think it might be legitimate email know to right-click and scan first, ask about (or forward a copy) of any suspicious emails received, etc. They also don't install spy/add/mal-ware, 3 different IM clients and whatever "cool" new download is making the rounds. And they behave like that in Windows. Preventing "bad" users from doing this simply takes locking down and pre-configuring their desktop and apps. It's not really any harder to do under Windown than it is under 'nix. I will agree that Windows should default into a more secure configuration, however. The same can be said of most Windows software, too.
My point was, while there will be technical differences in how a virus infection plays out in a 'nix environment, the same people are likely cause the same problems. The only reliable way to prevent those problems is to remove user privileges; that can be largely accomplished in Windows as easily as it can be in 'nix. The problem is that many organizations (mine included) don't really want to have user PCs locked down that tightly; it forces a call to IT every time a user needs to change their workstation environment. Giving them SU wouldn't help; they'd use it to install the things they do now in Windows without it.
If a PC does become infected, I can completely re-load a workstation in 30 to 45 minutes, unattended, with apps and all. It only requires a few initial keystrokes; just wipe and reload. Even the user's desktop, shortcuts, documents, etc. will be restored. This minimizes the overall impact of an infected PC. Unfortunately there is no perfect way to prevent virus infections and other exploits. Just keep the defs and patches up to date, scan everything, try to make sure you are only running minimum needed services, and your keep firewall tight.
The end result is that I believe that against a specific "new" attack, I'm no better or worse off than anyone else. Given comparable user control of the target PC, a shiny new 'nix exploit would be just as likely to land (ignoring all the 'nix flavor variation issues) as a shiny new Windows exploit would, given the same user base. The 'nix flavor issue is essentially security through obscurity; it works, but I don't consider it a reliable core strategy. How many organizations with centrally managed 'nix desktops officially support more than one 'nix desktop flavor in house?
The subject line above pretty much covers all of the article's "social engineering" blah blah. As an IS/IT manager I can assure you that no amount of click boxes, pop-up warnings, etc. will prevent some users from doing "bad things" (tm).
As for the author's technical reasons; please see above. Most of the people who click and/or view every e-mail they shouldn't are also the ones who install every bit of spy/add/mal-ware, etc. onto their PCs, and run as root. PCs are just so easy to use that way.
Right now most of those users wouldn't even dream of trying to wrestle with a 'nix variant; nothing "just works". Once stuff really does "just work" they'll be able to commit all of their same bad behaviors quickly and easily in a shiny new OS.
Some will find that the limitation will relate to having an older version of Mandrake Linux, unintentionally, I'm sure. The available Bit Torrent RPMs for ML will not install on older versions (ML 9.1 or older) without slogging through dependency upgrades.
A simple, real world example is me. I don't download MP3s to fill my music collection, but I did used to download a few to check our new bands recomended by friends. Those usually led to me buying new CDs. I used to buy quite a few more CDs than I do now. To be honest, over the last 3 years: broadcast radio has gone into the toilet (no new music & lousy selection), CD prices have gone up (they were already expensive), money is much tighter than it used to be, and my life has changed; I'm now more likely to spend money on my house/cars/kids/etc. than the overpriced CDs I would have bought a few years ago. Another big FYI; my parents are also buying fewer vinyl albums and tapes than they did 20 years ago! My kids are buying fewer CDs than I did tapes at their age; but they're not downloading either. My oldest daughter actually listens to much of the stuff I do - stuff released 10 years ago. Her thoughts are the same; there is very little good new music hitting the stores.
Would the modchip view be changed if the PS/2 was successfully argued to be a full fledged computer? IANAL, and have no idea what the legality of this might bring; but I'm pretty sure Dell doesn't have the right to limit what software you run...
Why not requre all DRM'd content to be distributed as "Leased" instead of "Owned"? IANAL but wouldn't this more closely fit the DRM model?
While mass automation may give us the time to inovate, it will all be for naught unless the current trends in IP law change. I predict within the next years virtually every bit of "new" or common knowledge will be locked down by big money and IP law. Inovate and get sued! Perhaps we'll all end up reading Slashdot archives :)