The whole argument about software piracy is driving the world crazy. If Microsoft are serious about the elimination of piracy of their licensed software here are a few pointers they might consider:
1) Demand that all governments institute extremely severe penalties for every instance of copyright or license violation. At least that will ensure that the subject gets taken more seriously. (I can't advocate the death penalty, but something close to it would help make a resounding statement.)
Also, show zero mercy, otherwise the message will not be strong enough! (PS: The RIAA and MPAA should take hint also to help educate the public that use of proprietary copyrighted material is a VERY serious matter. Eliminate any concept or form of "fair use" - there is no room for it in a DRM locked up world.) It is only reasonable to make the consumer aware that organizations that pursue such controls really do not want customers, they want prisoners. Prisoners have no rights! It is time to come out of the woods and into the clear!
2) Eliminate the bundling of Microsoft products from all computer sales.
Microsoft should insist that the consumer must obtain duly licensed software (operating system and applications) and must comply with well published and clearly presented licensing terms. The current practice of bundling MS Windows with laptops and desktop systems is a source of endless confusion for the consumer. Microsoft are the primary cause of end-user confusion.
The purchase of a bundled system requires the consumer (or user) to enter into a compulsory contract (EULA) with a third-party who is NOT involved in the purchase transaction between the purchaser and the supplier of the hardware (laptop or desktop system). This is a patently unjust business practice because the user is coerced into a contract with a company that interferes with the purchase transaction between buyer and seller. Separating out the purchase of an operating system would clearly separate the business and licensing transactions, and thus will create greater awareness of the responsibility to comply with licensing terms.
3) Governments should insist that under freedom of information conditions all consumers must be made aware of the alternatives they can choose from when faced with a need to select an operating system and application software. The consumer should be made aware of the existence of free software so that the consumer is not coerced into an unnecessary financial or legally oppressive relationship.
4) Microsoft should educate their users that the original license to use a product they supplied applies only to the originally supplied product. In other words, all modifications made to the operating system, or to application software, as a result of a maintenance process is a sub-license of the original license and can not be severed from the original license. Please help loyal Microsoft users to keep the consumer honest.
Too often IT people are approached by someone who received a second-hand computer from which the original purchaser had erased the MS Windows operating system, but left the activation key sticker on the machine, only to be asked to install some version (any version) of MS Windows because they do not have original installation media, and yet believe that the activation key sticker is a license to any version of Windows since they can not use the computer without an operating system installed.
Microsoft, please help us to eliminate these myths! Why should Microsoft's loyal supporters make themselves out to be the bad guys? Gentlemen, the confusion does not belong to those of us who respect licensing terms. Most open source software advocates are zealous to ensure that the terms of use of open source software are fully complied with. With the right leadership from Microsoft they can be just as zealous to help educate Microsoft's customers of the importance of compliance with Micrsoft's EULAs. After all, this would be only reasonable. Right?
The OSC was formed to get around UK government procurement constraints. This initiative provides a way for members to win business opportunities using open source software in UK government areas.
Members ofthe OSC are all small open source consultants and contractors. The purpose of getting organized is to get proprietary vendors out and get open source into government IT projects.
I know the OSC launch is not perfect, they are working against many negative barriers. How about some support instead a put-down. You are kicking your friends in the teeth with the rants against them so far!
The biggest obstacle you face is not one of basic Linux familiarization, that can indeed be picked up through hands-on self-managed at-home training. There are many good books that can guide you in the basics, but the big obstacle is always TIME!
You will find that the demands to migrate Windows systems to Linux will outstrip your time. You need to pick up chilli-hot pointers to get basic services established in an instant.
For example: MS Windows has wizards and GUI tools to help get DHCP server, DNS server, file and print, etc. configured. Each requires only a limited amount oof back0ground information (IP Address, network mask, domain name, IP range for DHCP, upstream DNS server, gateway address, etc.) With Linux, no matter which distribution, you have to learn to use an editor (that is unlike anything you have ever used in Windows NT)and then manually configure each control file (dhcpd.conf, named.conf and so on) and if you get one dot wrong - your server will not work.
Samba is a bear to configure. Setting up a PDC and a BDC requires LDAP. Installation and configuration of LDAP requires more than transient knowledge! Then you have to install and configure a set of control scripts that interface between the Windows world (client requests) and the Linux OS. Again, this is not for the faint at heart average MS Windows network administrator who already feels out of his depth just having to deal with Linux.
If I were you, I'd check out the Samba web site, download the Samba-3 by Example book (can be purchased from Amazon.Com also) and use the networking examples it presents. You can download this book from: http://www.samba.org/samba/docs/Samba-Guide.pdf
The above book fully documents a wide range of MS Windows networks and includes all configuration files you may need for: 1. DHCP serving, Dynamic DNS, Samba, Firewall, CUPS (printing), etc. It is not perfect, but a good start.
You might also check out the Freedom Technology Center (see http://www.freedomtechnologycenter.org)for hands-on training courses they offer.
There is a wide range of potential training you can buy. Look for sources that run custom hand-on training. This is your best option to get yourself up to speed.
John T.
jht@samba.org
Re:So, Where is Samba-3 By Example?
on
Samba 3 By Example
·
· Score: 4, Informative
Guys,
I committed the entire text of the book to the public samba-docs code tree on April 5th. We are having some difficulty in building the PDF file on the Samba build system. This will be resolved as soon as possible.
We are committed to open information about open source software. Please be a little patient with us, you will get your candy soon.
Slashdot Mirror
The whole argument about software piracy is driving the world crazy. If Microsoft are serious about the elimination of piracy of their licensed software here are a few pointers they might consider:
1) Demand that all governments institute extremely severe penalties for every instance of copyright or license violation. At least that will ensure that the subject gets taken more seriously. (I can't advocate the death penalty, but something close to it would help make a resounding statement.)
Also, show zero mercy, otherwise the message will not be strong enough! (PS: The RIAA and MPAA should take hint also to help educate the public that use of proprietary copyrighted material is a VERY serious matter. Eliminate any concept or form of "fair use" - there is no room for it in a DRM locked up world.) It is only reasonable to make the consumer aware that organizations that pursue such controls really do not want customers, they want prisoners. Prisoners have no rights! It is time to come out of the woods and into the clear!
2) Eliminate the bundling of Microsoft products from all computer sales.
Microsoft should insist that the consumer must obtain duly licensed software (operating system and applications) and must comply with well published and clearly presented licensing terms. The current practice of bundling MS Windows with laptops and desktop systems is a source of endless confusion for the consumer. Microsoft are the primary cause of end-user confusion.
The purchase of a bundled system requires the consumer (or user) to enter into a compulsory contract (EULA) with a third-party who is NOT involved in the purchase transaction between the purchaser and the supplier of the hardware (laptop or desktop system). This is a patently unjust business practice because the user is coerced into a contract with a company that interferes with the purchase transaction between buyer and seller. Separating out the purchase of an operating system would clearly separate the business and licensing transactions, and thus will create greater awareness of the responsibility to comply with licensing terms.
3) Governments should insist that under freedom of information conditions all consumers must be made aware of the alternatives they can choose from when faced with a need to select an operating system and application software. The consumer should be made aware of the existence of free software so that the consumer is not coerced into an unnecessary financial or legally oppressive relationship.
4) Microsoft should educate their users that the original license to use a product they supplied applies only to the originally supplied product. In other words, all modifications made to the operating system, or to application software, as a result of a maintenance process is a sub-license of the original license and can not be severed from the original license. Please help loyal Microsoft users to keep the consumer honest.
Too often IT people are approached by someone who received a second-hand computer from which the original purchaser had erased the MS Windows operating system, but left the activation key sticker on the machine, only to be asked to install some version (any version) of MS Windows because they do not have original installation media, and yet believe that the activation key sticker is a license to any version of Windows since they can not use the computer without an operating system installed.
Microsoft, please help us to eliminate these myths! Why should Microsoft's loyal supporters make themselves out to be the bad guys? Gentlemen, the confusion does not belong to those of us who respect licensing terms. Most open source software advocates are zealous to ensure that the terms of use of open source software are fully complied with. With the right leadership from Microsoft they can be just as zealous to help educate Microsoft's customers of the importance of compliance with Micrsoft's EULAs. After all, this would be only reasonable. Right?
- A Concerned Licensing Advocate
Hey I want to take you up on your offer. A game of golf will do me good. :-)
- John T.
The OSC was formed to get around UK government procurement constraints. This initiative provides a way for members to win business opportunities using open source software in UK government areas.
Members ofthe OSC are all small open source consultants and contractors. The purpose of getting organized is to get proprietary vendors out and get open source into government IT projects.
I know the OSC launch is not perfect, they are working against many negative barriers. How about some support instead a put-down. You are kicking your friends in the teeth with the rants against them so far!
The biggest obstacle you face is not one of basic Linux familiarization, that can indeed be picked up through hands-on self-managed at-home training. There are many good books that can guide you in the basics, but the big obstacle is always TIME!
You will find that the demands to migrate Windows systems to Linux will outstrip your time. You need to pick up chilli-hot pointers to get basic services established in an instant.
For example: MS Windows has wizards and GUI tools to help get DHCP server, DNS server, file and print, etc. configured. Each requires only a limited amount oof back0ground information (IP Address, network mask, domain name, IP range for DHCP, upstream DNS server, gateway address, etc.) With Linux, no matter which distribution, you have to learn to use an editor (that is unlike anything you have ever used in Windows NT)and then manually configure each control file (dhcpd.conf, named.conf and so on) and if you get one dot wrong - your server will not work.
Samba is a bear to configure. Setting up a PDC and a BDC requires LDAP. Installation and configuration of LDAP requires more than transient knowledge! Then you have to install and configure a set of control scripts that interface between the Windows world (client requests) and the Linux OS. Again, this is not for the faint at heart average MS Windows network administrator who already feels out of his depth just having to deal with Linux.
If I were you, I'd check out the Samba web site, download the Samba-3 by Example book (can be purchased from Amazon.Com also) and use the networking examples it presents. You can download this book from: http://www.samba.org/samba/docs/Samba-Guide.pdf
The above book fully documents a wide range of MS Windows networks and includes all configuration files you may need for: 1. DHCP serving, Dynamic DNS, Samba, Firewall, CUPS (printing), etc. It is not perfect, but a good start.
You might also check out the Freedom Technology Center (see http://www.freedomtechnologycenter.org)for hands-on training courses they offer.
There is a wide range of potential training you can buy. Look for sources that run custom hand-on training. This is your best option to get yourself up to speed.
John T. jht@samba.org
Guys,
I committed the entire text of the book to the public samba-docs code tree on April 5th. We are having some difficulty in building the PDF file on the Samba build system. This will be resolved as soon as possible.
We are committed to open information about open source software. Please be a little patient with us, you will get your candy soon.
Cheers,
John T.