How did they use it as a "reference"? Did the same developer(s) look directly at the GPL'ed driver code, and the write a BSD implementation? Or did they reverse engineer it using the typical method of two independent groups who have no contact besides a written specification of the hardware?
Support for ext2 and ext3 (directly derived from Linux, that is) may have been made available by third parties, but they are not part of the FreeBSD kernel core.
While it doesn't preclude the possibility of it being ported over, it will not be included in the main distribution. As such, it most likely will not become widely used as a native FreeBSD filesystem. It will probably only be used by the technically astute who would use it for compatibility with existing Linux filesystems. As such, it probably would not receive widespread testing. And when it comes to filesystems, the more testing the better.
Also, GCC isn't part of the FreeBSD kernel, you know.
Revolutionary often suggests a higher degree of complexity. Licensing issues aside, it's not just a matter of getting the ReisierFS3 or ReiserFS4 code to compile with the FreeBSD kernel. It has to be tested for compatibility, quality and performance. You can't be losing data, and if it doesn't offer a performance benefit over UFS or UFS2 then there's very little point in porting it.
The FreeBSD and Linux kernels do differ fairly significantly, so it may not even be an easy task porting over the code (again, licensing issues aside). Indeed, it may even be a better idea for the FreeBSD team to perform their own implementation of the ReiserFS4 concepts and algorithms.
You, me, and everyone else. That is "we". We are Slashdot, and we are the open source community. Together we can feel shame in knowing that a developer of our creed has shown such a lack of professionalism.
The poultry farmers aren't just motivated by money. Poultry to them, especially in some of these poorer nations, is what provides them their ability to live.
I don't think you would like it much if your nation's government came along, proceeding to confiscate and destroy your computers, even those running Linux or OS X, to prevent the spread of a computer worm. Now remember, you most likely could get by without your computers, unlike many of the poultry farmers.
Perhaps the richer countries should purchase these birds at market prices, and then proceed to destroy them. It gives the farmers incentive to get rid of the birds, and helps ensure a greater number are destroyed. It costs a bit of money, but probably far less than if the flu were to spread.
Such childish insults are not what I expected from an open source developer. Indeed, it does serve as a good example of what open source developers should not post online.
The complete lack of professionalism was disturbing, and it is unfortunate that both the KDE and KOffice projects had to suffer damaged reputations because of that single rogue developer.
The fact remains that I was correct, and the developer was wrong. However, that was no reason for him to throw out such insults, especially in public and while claiming to be a KOffice developer. That was very irresponsible behaviour of him to partake in.
What exactly is a "potentially dangerous" animal? Most animals are potentially dangerous. Many dogs can easily harm humans. Will all dogs need to be embedded with such a device? Even cats can bite and scratch. Will they require tracking devices? Even timid bunny rabbits can give a good bite if provoked enough. Again, will they need such devices?
Thank you for bringing to our attention the issue of open source professionalism. Indeed, for some developers it is something that needs much work. Especially that particular KOffice developer who went around publically insulting a long time KDE and KOffice user. It saddens me that a single comment like that from such a developer can have such a negative impact on the image of such otherwise respectable projects.
Slashdot Mirror
How did they use it as a "reference"? Did the same developer(s) look directly at the GPL'ed driver code, and the write a BSD implementation? Or did they reverse engineer it using the typical method of two independent groups who have no contact besides a written specification of the hardware?
It would appear they have not, or if support is available they do not include it with the core FreeBSD code.
It's not in the kernel modules portion of the FreeBSD CVS repository:
http://www.freebsd.org/cgi/cvsweb.cgi/src/lkm/
Nor is such code with the other filesystem code:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/fs/
Support for ext2 and ext3 (directly derived from Linux, that is) may have been made available by third parties, but they are not part of the FreeBSD kernel core.
It's not in the kernel modules portion of the FreeBSD CVS repository:
http://www.freebsd.org/cgi/cvsweb.cgi/src/lkm/
Nor is such code with the other filesystem code:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/fs/
ext2 Extent-based file system
goatseFS gaping ass fuck based file system
afs AFS client support for remote file sharing
As most of us know, goatseFS is NOT a filesystem.
Could you write us a more in-depth article, since this one does not suffice?
While it doesn't preclude the possibility of it being ported over, it will not be included in the main distribution. As such, it most likely will not become widely used as a native FreeBSD filesystem. It will probably only be used by the technically astute who would use it for compatibility with existing Linux filesystems. As such, it probably would not receive widespread testing. And when it comes to filesystems, the more testing the better.
Also, GCC isn't part of the FreeBSD kernel, you know.
Revolutionary often suggests a higher degree of complexity. Licensing issues aside, it's not just a matter of getting the ReisierFS3 or ReiserFS4 code to compile with the FreeBSD kernel. It has to be tested for compatibility, quality and performance. You can't be losing data, and if it doesn't offer a performance benefit over UFS or UFS2 then there's very little point in porting it.
The FreeBSD and Linux kernels do differ fairly significantly, so it may not even be an easy task porting over the code (again, licensing issues aside). Indeed, it may even be a better idea for the FreeBSD team to perform their own implementation of the ReiserFS4 concepts and algorithms.
The term is usually "monolithic kernel", rather than "macrokernel".
Licensing issues. You won't see GPL'ed code in the FreeBSD kernel, for instance.
By "smiling man" do you mean good ol' goatse, with his grinning anus?
It seems their page fails to validate, at least according to the W3C's HTML Validator.
g ov.uk/output/Page79.html
http://validator.w3.org/check?uri=http://www.mi6.
However, the one error is quite minor. Merely a "GET" which must be changed to "get".
It has nothing to do with age. The poster you replied to is most likely a Republican. That explains his high degree of stupidity and immaturity.
No, mainly because Q died in a car accident.
You, me, and everyone else. That is "we". We are Slashdot, and we are the open source community. Together we can feel shame in knowing that a developer of our creed has shown such a lack of professionalism.
Recall that: Democrat = Republican
Therefore: Democrat Rage = Republican Rage
Sufferers of Democrat Rage, such as yourself, also suffer from Republican Rage. That's because Democrat Rage and Republican Rage are the same thing.
The poultry farmers aren't just motivated by money. Poultry to them, especially in some of these poorer nations, is what provides them their ability to live.
I don't think you would like it much if your nation's government came along, proceeding to confiscate and destroy your computers, even those running Linux or OS X, to prevent the spread of a computer worm. Now remember, you most likely could get by without your computers, unlike many of the poultry farmers.
Perhaps the richer countries should purchase these birds at market prices, and then proceed to destroy them. It gives the farmers incentive to get rid of the birds, and helps ensure a greater number are destroyed. It costs a bit of money, but probably far less than if the flu were to spread.
Thank you yet again for bringing the matter of the flaming KOffice developer to our attention.
6 46636
http://slashdot.org/comments.pl?sid=163348&cid=13
Such childish insults are not what I expected from an open source developer. Indeed, it does serve as a good example of what open source developers should not post online.
The complete lack of professionalism was disturbing, and it is unfortunate that both the KDE and KOffice projects had to suffer damaged reputations because of that single rogue developer.
The fact remains that I was correct, and the developer was wrong. However, that was no reason for him to throw out such insults, especially in public and while claiming to be a KOffice developer. That was very irresponsible behaviour of him to partake in.
Democrat, Republican, whatever. They're the same thing these days. Big government, corruption, war mongering. All the traits of a nation in decline.
Have you sought medical treatment for your Republican Rage?
It looks like you are suffering from Republican Rage.
Amen!
What exactly is a "potentially dangerous" animal? Most animals are potentially dangerous. Many dogs can easily harm humans. Will all dogs need to be embedded with such a device? Even cats can bite and scratch. Will they require tracking devices? Even timid bunny rabbits can give a good bite if provoked enough. Again, will they need such devices?
Has a group such as PETA made any comment with regards to this practice?
Thank you for bringing to our attention the issue of open source professionalism. Indeed, for some developers it is something that needs much work. Especially that particular KOffice developer who went around publically insulting a long time KDE and KOffice user. It saddens me that a single comment like that from such a developer can have such a negative impact on the image of such otherwise respectable projects.