Open source is where every company programmer, consultant and techie can put their effort into a whole that is larger than the sum of its parts.
The programmers gets to do less work because there are other programmers to spread it out with -- more or less. It typically tends to work out where each programmer/company has their specific areas of interest and you have several of such prople working together to some degree.
You get free QA from others who want to use your software which is invaluable.
Sure many might say that the consultant will try to make it harder to use to keep their client base. But even though there are consultants like that, others will invariably have their own direction to make it easier. What sysadmin or company programmer wouldn't want fewer support calls they have to field?
I have been testing the 1.9.mXX releases (currently preparing for their first beta release) for a few weeks now, and most issues have been minor formatting changes, and a couple crashes here and there -- all of which have been reported. The one major issue I have come across is the problem where graphics are lost after saving changes to a document Issue 36459 where the fix has already been checked into 1.9.m64.
The pre-beta milestones have improved import/export filters, and many new features most people will like. It needs people to stomp on it in their worst way (ie, regular usage:). Does Open Office 1.9.mXX render a document differently than your other office suite (be it Word, Wordperfect, Works or etc)? Do your part:
o Create a seperate file with only the portion that changed from the other suite.
o Create a PDF of the document from the other suite.
o Create a PDF of the document from the latest development snapshot of OpenOffice (using the same pdf program if possible -- I use the Open Source PDFCreator which is a ghostscript front end).
o Zip the files (I use the Open Source 7-zip program)
o Report the issue (and create an account if you don't have one) with your best description of the problem with a step by step list of what actions need to be performed to reproduce the problem.
o Attach the zip file of the three files you created before.
The development code needs more people who are able to write bug reports -- that means don't install it on grandma's computer. If you think "it doesn't work" is a good bug report then please move to the next message, thanks.
Public key encryption might be a good way to secure a file that is being transmitted from one entity to another, but it completely subverts the P2P network where sharing files with multiple people is their entire purpose.
The problem is that if you attack the ones at the top (Don't vote for their tax increases or bond measures for more money or etc) they'll take the money from the low level workers you mention so they will go on strike in front of the media because their department had funding cuts. The end result is a guilt trip "think of the children!" for the people who don't believe in giving more money to beaurocrats.
So how do you go about getting the bad managers out at the top without them fucking everyone over in the process?
That may be so if you ask someone unfamiliar with Linux internals to do the porting. On the other hand, a lot of the ineternals, and especially the VFS is very well documented.
I would say that writing a mid-layer between the licensed journaling filesystem and the proprietary OS would be a good "get it working" first step. The later code factoring to integrate the two can come later. But consider changing the base OS instead of the licensed FS since you will want to be able to easily handle future updates of the licensed code.
Does anyone know what the story was about 2.0.23 or therabouts? It was supposed to be a release blunder on the level of any 2.4 earlier than 2.4.14, but I never cought the details.
I'm not discounting what you're saying, and your arguments have just added weight behind my argument.
"As the grandparent said, on the show they *routinely* use the liver temp. And they *always* note that it is approximate. And yes, 1-2 hours *is* significanty narrowed down[...]"
So you can narrow it down to hours on a few day old body with various means.
"Also, they routinly use other means to estimate the time of death from corpses that are very old - yes, even with maggots. One of the people on the show plays an entomologist, and he uses the types and amounts of insect puba casings and larva to estimate the time of death to within a few weeks if the corpse is months old, or to within a few days if it is weeks old.[...]"
And if it is several weeks/months old, they are only able to narrow down the time of death to a certain span of days.
That was my point, not to discount what is shown on CSI. I know next to nothing about forensics, and these arguments are great sources against the people who think "those shows just give too much information to the bad guys".
Businesses want a front end where your average tech dummy (think sales person or PHB) can change a form, move fields around to whatever order they want, and able to set the margins for printing on dead trees.
Firebird, MySQL, PostgreSQL are all back end database systems. They don't provide the front end that the end user is going to be starting on their desktop for pretty menus.
"Gaughan: If you look at MySQL's license it is commonly known as a duel license. It is essentially released as GPL, which is a true open source license, but GPL restricts you from embedding MySQL technology into your product. Your product also has to be open sourced. The way MySQL has gotten around that is by giving out a commercial license, which is the same as any other commercial license. You would have to pay a license fee to MySQL. So it's not truly open sourced. You never pay a license for Ingres r3."
They are equating the need for a license for commercial extensions to MySQL to not being "really" open source.
If they wanted to allow commercial use, they could have chosen the LGPL with a IP indemnification clause.
Dual (not "Duel") licensing is one of the accepted ways to make money from Open Source. The fact that the OSS license is GPL is icing on the cake.
Slashdot Mirror
Open source is where every company programmer, consultant and techie can put their effort into a whole that is larger than the sum of its parts.
The programmers gets to do less work because there are other programmers to spread it out with -- more or less. It typically tends to work out where each programmer/company has their specific areas of interest and you have several of such prople working together to some degree.
You get free QA from others who want to use your software which is invaluable.
Sure many might say that the consultant will try to make it harder to use to keep their client base. But even though there are consultants like that, others will invariably have their own direction to make it easier. What sysadmin or company programmer wouldn't want fewer support calls they have to field?
Where is the code, and what steps do the users have to go through to send a fax?
It looks like Open Office is targeting MS Access in their next release.
:). Does Open Office 1.9.mXX render a document differently than your other office suite (be it Word, Wordperfect, Works or etc)? Do your part:
I have been testing the 1.9.mXX releases (currently preparing for their first beta release) for a few weeks now, and most issues have been minor formatting changes, and a couple crashes here and there -- all of which have been reported. The one major issue I have come across is the problem where graphics are lost after saving changes to a document Issue 36459 where the fix has already been checked into 1.9.m64.
The pre-beta milestones have improved import/export filters, and many new features most people will like. It needs people to stomp on it in their worst way (ie, regular usage
o Create a seperate file with only the portion that changed from the other suite.
o Create a PDF of the document from the other suite.
o Create a PDF of the document from the latest development snapshot of OpenOffice (using the same pdf program if possible -- I use the Open Source PDFCreator which is a ghostscript front end).
o Zip the files (I use the Open Source 7-zip program)
o Report the issue (and create an account if you don't have one) with your best description of the problem with a step by step list of what actions need to be performed to reproduce the problem.
o Attach the zip file of the three files you created before.
The development code needs more people who are able to write bug reports -- that means don't install it on grandma's computer. If you think "it doesn't work" is a good bug report then please move to the next message, thanks.
172.0.0.1 . . .
The way geeks find themselfs.
Public key encryption might be a good way to secure a file that is being transmitted from one entity to another, but it completely subverts the P2P network where sharing files with multiple people is their entire purpose.
I believe the next stable release after sarge will be called etch.
That would be apt-get.org
This will work until the package in testing is compiled against a newer lib than in stable.
The solution in this case is backports.org.
So is Gnome, Debian and many other large projects.
Your web site doesn't tell anyone crap about what you can do for them except for vague references to video work.
Also, if you advocate using Linux for video editing, where are your links to those groups?
"Hell, for $100 bucks of HD space, I could image over 200 of my CDs right now."
Add two zeros for mp3 or ogg...
The problem is that if you attack the ones at the top (Don't vote for their tax increases or bond measures for more money or etc) they'll take the money from the low level workers you mention so they will go on strike in front of the media because their department had funding cuts. The end result is a guilt trip "think of the children!" for the people who don't believe in giving more money to beaurocrats.
So how do you go about getting the bad managers out at the top without them fucking everyone over in the process?
The power user doesn't protect you much from what an administrator account can do.
Power Users can write to most of the filesystem, including \Program Files. There are limitations, but, Power User doesn't buy you much.
Well, you would get shock absorbers and padded chairs in those Caterpillers at least.
That may be so if you ask someone unfamiliar with Linux internals to do the porting. On the other hand, a lot of the ineternals, and especially the VFS is very well documented.
I would say that writing a mid-layer between the licensed journaling filesystem and the proprietary OS would be a good "get it working" first step. The later code factoring to integrate the two can come later. But consider changing the base OS instead of the licensed FS since you will want to be able to easily handle future updates of the licensed code.
The concept is freedom.
The idea is that you can not have software freedom without the source. The GPL enforces that software under that license keeps its freedom.
Freedom does not mean anarchy, as you can't kill someone and keep your freedom (and avoiding capture doesn't count).
If you are rounding up to 512 bytes per record, it looks like your "database" saves each record in a seperate file.
And remember that $3,000 was a lot of money back then. Something like $200,000 today (just guessing).
Does anyone know what the story was about 2.0.23 or therabouts? It was supposed to be a release blunder on the level of any 2.4 earlier than 2.4.14, but I never cought the details.
Anyone?
I'm not discounting what you're saying, and your arguments have just added weight behind my argument.
"As the grandparent said, on the show they *routinely* use the liver temp. And they *always* note that it is approximate. And yes, 1-2 hours *is* significanty narrowed down[...]"
So you can narrow it down to hours on a few day old body with various means.
"Also, they routinly use other means to estimate the time of death from corpses that are very old - yes, even with maggots. One of the people on the show plays an entomologist, and he uses the types and amounts of insect puba casings and larva to estimate the time of death to within a few weeks if the corpse is months old, or to within a few days if it is weeks old.[...]"
And if it is several weeks/months old, they are only able to narrow down the time of death to a certain span of days.
That was my point, not to discount what is shown on CSI. I know next to nothing about forensics, and these arguments are great sources against the people who think "those shows just give too much information to the bad guys".
Simple, if you have more than X points on your license, you have to get additional insurance in addition to the insurance in the GF's post.
Let's just say the longer a body has been dead the larger the window of possible time of death and leave it at that.
You're not going to get a 2-4 hour window of time of death after a body has maggots.
Ahh yes, 2.0.36. It came out a few weeks after my first Linux install (on Debian "hamm" 2.0). It was also the first kernel I compiled. :)
Are you kidding me?
Businesses want a front end where your average tech dummy (think sales person or PHB) can change a form, move fields around to whatever order they want, and able to set the margins for printing on dead trees.
Firebird, MySQL, PostgreSQL are all back end database systems. They don't provide the front end that the end user is going to be starting on their desktop for pretty menus.
"Gaughan: If you look at MySQL's license it is commonly known as a duel license. It is essentially released as GPL, which is a true open source license, but GPL restricts you from embedding MySQL technology into your product. Your product also has to be open sourced. The way MySQL has gotten around that is by giving out a commercial license, which is the same as any other commercial license. You would have to pay a license fee to MySQL. So it's not truly open sourced. You never pay a license for Ingres r3."
They are equating the need for a license for commercial extensions to MySQL to not being "really" open source.
If they wanted to allow commercial use, they could have chosen the LGPL with a IP indemnification clause.
Dual (not "Duel") licensing is one of the accepted ways to make money from Open Source. The fact that the OSS license is GPL is icing on the cake.