You *can* work with data type sizes larger than your CPU's word size in software. For example, if you need to add/subtract 128 bit integers, it is not terribly difficult to do -- it just takes multiple instructions and using the carry-out/overflow bit on you adder. Don't think that a hardware 'improvement' will magically fix software. It is just convenient to use 32 bit numbers as they can be operated on in a single instruction on most modern architectures.
Also, increasing the width of your CPU datapath is not something that can be pushed up forever. A simple 256 bit adder would require at least 768 inputs/outputs. At some point it becomes a lot more efficient to change your approach!
The graphics on my machine worked perfectly with Xfree86. Xorg is the problem.
Don't be so quick to blame Xorg. It is more than likely to be a 'problem' with the fallback configuration Ubuntu uses. Last time I had graphics driver issues under Windows it defaulted to 640x480 or something.
This is Sweden's national standards body's vote we are talking about here, not the ISO. The national bodies vote on what they put in the ISO's voting process.
I don't think 'make' has improved: all make really does is run build instructions if timestamps on the input files have changed. What you probably mean is the GNU Build System (automake, autoconf, libtool, gettext, etc.) which create input files for make.
You will find similar language in most EULA too.
From the GPLv3:
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. From the Windows XP Home EULA:
16. DISCLAIMER OF WARRANTIES. The Limited Warranty that appears above is the only express warranty made to you and is provided in lieu of any other express warranties or similar obligations (if any) created by any advertising, documentation, packaging, or other communications. Except for the Limited Warranty and to the maximum extent permitted by applicable law, Microsoft and its suppliers provide the Software and support services (if any) AS IS AND WITH ALL FAULTS, and hereby disclaim all other warranties and conditions, whether express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of reliability or availability, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of negligence, all with regard to the Software, and the provision of or failure to provide support or other services, information, software, and related content through the Software or otherwise arising out of the use of the Software. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THE SOFTWARE.
17. EXCLUSION OF INCIDENTAL, CONSEQUENTIAL AND CERTAIN OTHER DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS OR CONFIDENTIAL OR OTHER INFORMATION, FOR BUSINESS INTERRUPTION, FOR PERSONAL INJURY, FOR LOSS OF PRIVACY, FOR FAILURE TO MEET ANY DUTY INCLUDING OF GOOD FAITH OR OF REASONABLE CARE, FOR NEGLIGENCE, AND FOR ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING OUT OF OR IN ANY WAY RELATED TO THE USE OF OR INABILITY TO USE THE SOFTWARE, THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT OR OTHER SERVICES, INFORMATON, SOFTWARE, AND RELATED CONTENT THROUGH THE SOFTWARE OR OTHERWISE ARISING OUT OF THE USE OF THE SOFTWARE, OR OTHERWISE UNDER OR IN CONNECTION WITH ANY PROVISION OF THIS EULA, EVEN IN THE EVENT OF THE FAULT, TORT (INCLUDING NEGLIGENCE), MISREPRESENTATION, STRICT LIABILITY, BREACH OF CONTRACT OR BREACH OF WARRANTY OF MICROSOFT OR ANY SUPPLIER, AND EVEN IF MICROSOFT OR ANY SUPPLIER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Probably the biggest issues I ever had with Webmin were its configuration programs messing up any by-hand configuration you have done for those programs. Admittedly I have not used Webmin for a few years, so it could have improved a lot in that respect since then.
Actually, Hurd is currently based on Mach; almost all of its drivers are in the kernel. Minix 3 is a fairly good example of an operating system that puts all of its drivers in userspace.
Kernel mode or "Ring 0" (on Intel and similar systems) means that the program can execute any instruction, change any CPU settings, access all memory and IO devices. [This is bad for running arbitrary and possibly poorly written code!]
The examples you gave with Flash etc. are a completely different situation.
Firefox probably isn't the ideal browser for an embedded device; as much as everyone loves it. Gecko's architecture is very bloated. There are smaller browsers available that would do the job much better... KHTML (if its still called that) for example.
-- Sam
I know this is flamebait; but for the record the Gnome project DO have a web browser (Epiphany) which uses the Gecko engine, but native Gtk/Gnome widgets. Last time I used it, it was smaller and faster than the full blown Firefox (at least in terms of UI-response); had all the main features you would expect from a web browser and integrated with the Gnome desktop quite nicely.
-- Sam
It refuses to be distributed _with_ software that isnt as free or more free than the GPL. Not to troll or nitpick too much but it is perfectly acceptable (and clarified in the license) to distribute a piece of GPL'ed software along side a proprietary application.
You cannot make a derivative work (modifying the program, adding to the program, linking against the program as a shared or static library etc.) that isn't as free or more free than the GPL.
If my microwave, car or stove contained powerful, general purpose computers; then I would like to have the option of changing the software on them; or at least extending it to best suit my needs or wants.
If any such device makes use of free software under licenses such as the GPL; and the software is replaceable (i.e. not stored in ROM), then the recipient of such software should have the freedoms 'guaranteed' by the license restricted in such ways. If the manufacturer of the device wishes to maintain power over what software the recipient can run on it; then they should not use software that was conveyed to them under a license that requires further recipients of the software to receive the same freedoms the distributors were granted.
The no-root thing is really simple: the root account in the basic install mode just doesn't have a password set (effectively disabling interactive logins to the account).
If you want a root account back, `sudo passwd root` will set a root password, allowing you to login. Alternatively if you just want a root shell, `sudo -i` will open one.
From the GPLv2:
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. From the GPLv3:
Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
Of course, QT is one of those "few things" that are GPLv2 only. You cannot distribute a GPLv3 only KDE program. If you believe in the GPLv3 and want to use it, KDE is not an option. Cut the FUD, the license hasn't been released yet. There is nothing stopping Trolltech from licensing Qt under the GPLv3 when it is released
Perhaps it would be more appropriate to call them UNIX/GNU tools. It's not as if much of this stuff was invented by RMS and GNU developers. But it was all written by GNU contributors; the implementations share no code with the 'original' UNIX counterparts. Also the quality and coding standards of GNU software is often a lot higher than the 'original' UNIX counterparts.
From my brief experience trying Ogre3D and Irrlicht; Ogre3D seems the better designed (from a software engineering view), however it seemed to have issues with my Intel GMA950 on GNU/Linux so it wasn't suitable for my purposes. Irrlicht worked nicely but its documentation left a lot to be desired in places.
If you want to do unusual stuff with your graphics engine; using Ogre or Irrlicht will require you to learn quite a lot about the inner workings of the engine, and in many cases will be more work than if you had a purpose built engine.
That was from my limited experience with them anyway.
-- Sam
Slashdot Mirror
Is that what you kids call it these days.
You *can* work with data type sizes larger than your CPU's word size in software. For example, if you need to add/subtract 128 bit integers, it is not terribly difficult to do -- it just takes multiple instructions and using the carry-out/overflow bit on you adder. Don't think that a hardware 'improvement' will magically fix software. It is just convenient to use 32 bit numbers as they can be operated on in a single instruction on most modern architectures. Also, increasing the width of your CPU datapath is not something that can be pushed up forever. A simple 256 bit adder would require at least 768 inputs/outputs. At some point it becomes a lot more efficient to change your approach!
This thread is really turning into a synergy of collaboration that can really be leveraged to further out business!
Drivers :)
tar-gzip with a description file :)
Don't be so quick to blame Xorg. It is more than likely to be a 'problem' with the fallback configuration Ubuntu uses. Last time I had graphics driver issues under Windows it defaulted to 640x480 or something.
This is Sweden's national standards body's vote we are talking about here, not the ISO. The national bodies vote on what they put in the ISO's voting process.
I don't think 'make' has improved: all make really does is run build instructions if timestamps on the input files have changed. What you probably mean is the GNU Build System (automake, autoconf, libtool, gettext, etc.) which create input files for make.
-- Splitting hairs
From the GPLv3: THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. From the Windows XP Home EULA: 16. DISCLAIMER OF WARRANTIES. The Limited Warranty that appears above is the only express warranty made to you and is provided in lieu of any other express warranties or similar obligations (if any) created by any advertising, documentation, packaging, or other communications. Except for the Limited Warranty and to the maximum extent permitted by applicable law, Microsoft and its suppliers provide the Software and support services (if any) AS IS AND WITH ALL FAULTS, and hereby disclaim all other warranties and conditions, whether express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of reliability or availability, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of negligence, all with regard to the Software, and the provision of or failure to provide support or other services, information, software, and related content through the Software or otherwise arising out of the use of the Software. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THE SOFTWARE.
17. EXCLUSION OF INCIDENTAL, CONSEQUENTIAL AND CERTAIN OTHER DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS OR CONFIDENTIAL OR OTHER INFORMATION, FOR BUSINESS INTERRUPTION, FOR PERSONAL INJURY, FOR LOSS OF PRIVACY, FOR FAILURE TO MEET ANY DUTY INCLUDING OF GOOD FAITH OR OF REASONABLE CARE, FOR NEGLIGENCE, AND FOR ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING OUT OF OR IN ANY WAY RELATED TO THE USE OF OR INABILITY TO USE THE SOFTWARE, THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT OR OTHER SERVICES, INFORMATON, SOFTWARE, AND RELATED CONTENT THROUGH THE SOFTWARE OR OTHERWISE ARISING OUT OF THE USE OF THE SOFTWARE, OR OTHERWISE UNDER OR IN CONNECTION WITH ANY PROVISION OF THIS EULA, EVEN IN THE EVENT OF THE FAULT, TORT (INCLUDING NEGLIGENCE), MISREPRESENTATION, STRICT LIABILITY, BREACH OF CONTRACT OR BREACH OF WARRANTY OF MICROSOFT OR ANY SUPPLIER, AND EVEN IF MICROSOFT OR ANY SUPPLIER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Probably the biggest issues I ever had with Webmin were its configuration programs messing up any by-hand configuration you have done for those programs. Admittedly I have not used Webmin for a few years, so it could have improved a lot in that respect since then.
Actually, Hurd is currently based on Mach; almost all of its drivers are in the kernel. Minix 3 is a fairly good example of an operating system that puts all of its drivers in userspace.
-- Sam
Kernel mode or "Ring 0" (on Intel and similar systems) means that the program can execute any instruction, change any CPU settings, access all memory and IO devices. [This is bad for running arbitrary and possibly poorly written code!]
The examples you gave with Flash etc. are a completely different situation.
-- Sam
Firefox probably isn't the ideal browser for an embedded device; as much as everyone loves it. Gecko's architecture is very bloated. There are smaller browsers available that would do the job much better... KHTML (if its still called that) for example. -- Sam
I know this is flamebait; but for the record the Gnome project DO have a web browser (Epiphany) which uses the Gecko engine, but native Gtk/Gnome widgets. Last time I used it, it was smaller and faster than the full blown Firefox (at least in terms of UI-response); had all the main features you would expect from a web browser and integrated with the Gnome desktop quite nicely. -- Sam
You cannot make a derivative work (modifying the program, adding to the program, linking against the program as a shared or static library etc.) that isn't as free or more free than the GPL.
If my microwave, car or stove contained powerful, general purpose computers; then I would like to have the option of changing the software on them; or at least extending it to best suit my needs or wants.
If any such device makes use of free software under licenses such as the GPL; and the software is replaceable (i.e. not stored in ROM), then the recipient of such software should have the freedoms 'guaranteed' by the license restricted in such ways. If the manufacturer of the device wishes to maintain power over what software the recipient can run on it; then they should not use software that was conveyed to them under a license that requires further recipients of the software to receive the same freedoms the distributors were granted.
The no-root thing is really simple: the root account in the basic install mode just doesn't have a password set (effectively disabling interactive logins to the account). If you want a root account back, `sudo passwd root` will set a root password, allowing you to login. Alternatively if you just want a root shell, `sudo -i` will open one.
Projects are under no obligation to accept the "zealot's" GPLv3 code.
Perhaps bias against the fact it is an Apple product, or AAC...
From my brief experience trying Ogre3D and Irrlicht; Ogre3D seems the better designed (from a software engineering view), however it seemed to have issues with my Intel GMA950 on GNU/Linux so it wasn't suitable for my purposes. Irrlicht worked nicely but its documentation left a lot to be desired in places. If you want to do unusual stuff with your graphics engine; using Ogre or Irrlicht will require you to learn quite a lot about the inner workings of the engine, and in many cases will be more work than if you had a purpose built engine. That was from my limited experience with them anyway. -- Sam