This is why you don't blindly run emerge -u world. On a production machine, you would pick the update you want to run out of what is available, and take time and care when updating major services....this applies to ANY distro....
On one hand, making the kde platform and applications available for windows definitely adds value to the platform and can drastically cut the cost of running windows on desktop clients. Not having to take out licenses for cd burning software (k3b), desktop publishing software (scribus), office software(OOo & koffice), vector and raster graphics software(inkscape & gimp), or email/groupware software(evolution/kontact) makes it far, far easier to stay on the windows platform and at the same time, get the benefits of open source software at the application level. You get the benefits of OSS without the pain of changing a platform. In addition, it takes away any incentive people might have for adopting some "killer" app that might develop on the Linux platform. If it were exclusively available for linux, then there would be a much better incentive for people to switch platforms. This is the position apple has take with its iApps only porting the apps that directly further their platform goals (Quicktime & iTunes). You can draw a lot of people to the platform by making your "killer" apps only available on that platform. On linux, it has been argued that asterisk might be such an app, but this has more to do with the lack of windows support for the digium hardware than anything else, and this is mainly a server side app that people don't really see on thier desktops.
On the other hand, this type of thing would dramatically expand the user base of OSS software, which can be considered a very good thing if it results in overal improvements to the software that a larger, and involved, user base can bring. In addition it makes people "more used" to OSS apps so that if and when the platform changes (withouth thier choice/intervention most likely), the apps they are used to are still there and available. This assumes that people don't really choose operating systems, but merely accept what they are given.
The idea is to have software the integrates and takes advantage of everything the kde environment has to offer. There are two ways of doing this. 1. Pull your hair out trying to cajole existing applications originally created off of an entirely different framework, to take some, limited advantage of what kde has to offer. 2. Start from scratch with an environment that makes fast development very easy and very quick, without massive quantities of hair left in your hands.
I wonder if the Spo-compton parking meter nazis will use this. I wouldn't be surprised as when I was living there attending Gonzaga, they had an incredible and uncanny ability to pounce on an expired meter literally withing 60 seconds of expiration. They probably could cut that time down to a quarter of that if each meter had a wifi device and a simple program to broadcast when a meter has expired.....
SCO vs. Linux: The time of the conspiracy theories
In history around SCO and the source code from SCO existence, rich at idioms and twists, possibly transferred after Linux, new turns are to be reported. With the conspiracy theory that Microsoft behind SCO stands, it associates the theory that the refusal of the requirements of SCO is a only one, well camouflaged campaign of IBM. Thus the InfoWorld reported that SCO boss sees Darl McBride IBM as an author of the dirt campaign. IBM caused Novell to place itself against SCO meant McBride, employed long years with Novell as a director/conductor of the Netware Embedded division (NEST). IBM has talks floated to complain against SCO means it in addition. Also Eric Raymond of the open SOURCE initiative would stand on the pay roll IBMs, which would finance besides the Free software Foundation and thus the lawyer evenly Moglen, continued to implement Darl McBride.
While IBM as talk has the accusations lapidary for nonsense explained and about Novell none came, Eric Raymond raffte itself up to send an open letter at Darl McBride. In it answered in the negative Raymond by IBM to be paid did not deny however IBM to have helped. Altogether Raymond appealed to the reason of the SCO upper one with an allusion to the insight ability of Darth Vader : "you have the choice. Remove the dark helmet and converse with us like a human nature, or you continue your way, which lets bad times fear for us, however you and the entire SCO Topmanagement into the ruin will completely surely float."
Off the roaring star Wars Rhetorik Eric Raymond used the open letter, in order to make attentive on a Petition of the Linux Community, which were read out on the SCOForum. In their the SCO Group is requested to give up and all inkriminierten places in the SOURCE code call the confrontation course. In response the Linux programmers want to assure to revise all questionable places: "if right right-hurt-hurting that code in the Linux Kernel to be present should become, we it remove, because our community would not like to have a part of this Kernels."
The polite request will possibly remain without answer, because SCO with first, on which SCOForum published proofs could not convince. Apart from the problem of the "Greek" code is in the meantime the Berkeley presented by SCO pack filter (BPF) into the center of the interest moved. The SCO example originates from the file/sys/net/bpf.c, which is available here. In the cutout shown by SCO is missing the BSD Lizenzbedigungen, which is to be always called in accordance with BSD license: "Redistributions OF SOURCE code must retain the above copyright notice, this cunning OF conditions and the following more disclaimer." Because they are missing, code experts go such as Bruce Perens and Greg Lehey of the fact out that SCO with the example proved that the license conditions were removed agreement-adversely.
Thus a classical self-gate could be present, particularly since other possibilities are impossible. Like that the programmer of the version used in Linux was employed by BPF, Jay trainingist, with Caldera, wrote however the Clean Room variant of BPF before its time with Caldera. From the circles of former Caldera developers several persons can remember that in the SCO Trees in many places with the BSD code the copyright notes were missing. The procedure to cut "redundant" licenses off seems to have practiced also at other companies. Thus heise on-line developers to, that experienced the "technology" at Siemens Nixdorf, announced themselves. If the proof situation in the case SCO should confirm itself, then the code Hunter of this company excavated a proof, which occupies the exact opposite of the accusations by SCO. At least in the case of BPF SCO the power POINT presentation would not only have ( when ppt , when pdf ) separate the whole code make public, in order to weaken the suspicion.
SCO vs. Linux: The time of the conspiracy theories
In history around SCO and the source code from SCO existence, rich at idioms and twists, possibly transferred after Linux, new turns are to be reported. With the conspiracy theory that Microsoft behind SCO stands, it associates the theory that the refusal of the requirements of SCO is a only one, well camouflaged campaign of IBM. Thus the InfoWorld reported that SCO boss sees Darl McBride IBM as an author of the dirt campaign. IBM caused Novell to place itself against SCO meant McBride, employed long years with Novell as a director/conductor of the Netware Embedded division (NEST). IBM has talks floated to complain against SCO means it in addition. Also Eric Raymond of the open SOURCE initiative would stand on the pay roll IBMs, which would finance besides the Free software Foundation and thus the lawyer evenly Moglen, continued to implement Darl McBride.
While IBM as talk has the accusations lapidary for nonsense explained and about Novell none came, Eric Raymond raffte itself up to send an open letter at Darl McBride. In it answered in the negative Raymond by IBM to be paid did not deny however IBM to have helped. Altogether Raymond appealed to the reason of the SCO upper one with an allusion to the insight ability of Darth Vader : "you have the choice. Remove the dark helmet and converse with us like a human nature, or you continue your way, which lets bad times fear for us, however you and the entire SCO Topmanagement into the ruin will completely surely float."
Off the roaring star Wars Rhetorik Eric Raymond used the open letter, in order to make attentive on a Petition of the Linux Community, which were read out on the SCOForum. In their the SCO Group is requested to give up and all inkriminierten places in the SOURCE code call the confrontation course. In response the Linux programmers want to assure to revise all questionable places: "if right right-hurt-hurting that code in the Linux Kernel to be present should become, we it remove, because our community would not like to have a part of this Kernels."
The polite request will possibly remain without answer, because SCO with first, on which SCOForum published proofs could not convince. Apart from the problem of the "Greek" code is in the meantime the Berkeley presented by SCO pack filter (BPF) into the center of the interest moved. The SCO example originates from the file/sys/net/bpf.c, which is available here. In the cutout shown by SCO is missing the BSD Lizenzbedigungen, which is to be always called in accordance with BSD license: "Redistributions OF SOURCE code must retain the above copyright notice, this cunning OF conditions and the following more disclaimer." Because they are missing, code experts go such as Bruce Perens and Greg Lehey of the fact out that SCO with the example proved that the license conditions were removed agreement-adversely.
Thus a classical self-gate could be present, particularly since other possibilities are impossible. Like that the programmer of the version used in Linux was employed by BPF, Jay trainingist, with Caldera, wrote however the Clean Room variant of BPF before its time with Caldera. From the circles of former Caldera developers several persons can remember that in the SCO Trees in many places with the BSD code the copyright notes were missing. The procedure to cut "redundant" licenses off seems to have practiced also at other companies. Thus heise on-line developers to, that experienced the "technology" at Siemens Nixdorf, announced themselves. If the proof situation in the case SCO should confirm itself, then the code Hunter of this company excavated a proof, which occupies the exact opposite of the accusations by SCO. At least in the case of BPF SCO the power POINT presentation would not only have ( when ppt , when pdf ) separate the whole code make public, in order to weaken the suspicion.
Because yes size does indeed matter.....
on
Looking at Longhorn
·
· Score: 1
In the field of usability, bigger has been found to be, in general, better. Bigger interfaces are more tolerant to mistakes, are easier to "read" and interpret, can be accessed and used quicker, and are overall more obvious to use. Now, this isn't always the case, and stuff can be made too big, but most of the time this is the case. Pop "fitts law" into google for more info.
But I took it in a different direction. This would not just be a libel suit involving just Linus or the distromakers, this is defamation/libel of an entire community of developers. Thus a multi-plaintiff suit, or perhaps even a class-action suit might be more worthwhile. Second, my understanding of libel torts is that you while have to even prove intent to mislead/lie/etc, blatent negligence to the facts of your assertions can constitute this intent.
If IBM isn't going to counter-sue, WE SHOULD.
And this is precisely why I run a looping chrooted bootstrap with prime95 in the background as a stability test for all of my overclocked systems. If they can consistently produce fully functional code with a really, really intense integer application hammering the system in the background for over 24 hours without croaking, I consider it stable. The sad thing is is that it isn't uncommon for me to come across boards from ECS that can't even hack this test at default clock speeds.....
As someone else noted, this is highly ironic as the airfone clearly helped the UA 79 passengers bring the flight down to prevent it from hitting the Capitol.
Actually that story about what happend to Flight 93 is somewhat suspiscious see here.
You only have to make the source available to those that you provide binaries. Lindows, from what I understand lets you donwload the source packages for all gpl/lgpl binary packages that lindows distributes once you have become a Lindows customer. In other words, you don't have to make the sources completely public, but you can't keep the people you distribute the sources to from making them public.
Why can't AT&T have the users change the password immediatly after the first login? I.e, login for the first time with the default password, then FORCE a change of password before anything else can be done in the voicemail system. Combine this with a semirandom set of default passwords, then only accounts that are new would be even somewhat vulnerable.
Based on some informal googling I found that the average human head weighs around 10-13 lbs while attached (mine naturally is much heavier than that though). However, when it is detached, a significant amount of blood will be lost out of the head, and so you can then presume it to be 2-3 pounds lighter, unless you replace the blood with some sort of embalming fluid. Now if you are mailing this within the US, you can refer to the USPS rate chart available at www.usps.com
I just pulled the faad source from cvs, did a./bootstrap, a./configure, a make, and then a make install. It installed the lib in my Gentoo box to/usr/local/lib.
Oh, and BTW, our network admins have pretty much blocked all P2P/file sharing programs network ports, it's pretty much impossible to download anything that's not over the WWW/FTP.
This is why why I'm very glad to be living off campus now. Comcast(formerlly Attbi, formerly ATT@home) provides a far better connection than ZagNet ever did, without p2p stuff all closed down, and in a house with five people paying for it, its pretty dang cheap. Definitely made the inconvenience of being forced off campus because of the housing mess worthwhile.
Mod this down. Misleading link that has nothing to do with Greenspan. Link is actually to http://www.outwar.com/page.php?x=623513 which seems to be more of some kind of popularity counting site.
I've been running the 2.5 kernel on my laptop for a couple of weeks now to get the new cpufreq support. It seems to work really pretty well. Getting pcmcia-cs to build took some work, but I finally got it up and running and the performance of this new kernel is really nice, especially for the desktop.
The only catch with this though is that unless you have a lot of memory, or doing a stage3 install, the bootstrap and emerge system will a little longer because of less available memory. Otherwise it works really, really well, especially since the laptop network card support on the gentoo live cd's is somewhat incomplete.
Slashdot Mirror
I'd would be interested to see a reference on this....
This is why you don't blindly run emerge -u world. On a production machine, you would pick the update you want to run out of what is available, and take time and care when updating major services....this applies to ANY distro....
On one hand, making the kde platform and applications available for windows definitely adds value to the platform and can drastically cut the cost of running windows on desktop clients. Not having to take out licenses for cd burning software (k3b), desktop publishing software (scribus), office software(OOo & koffice), vector and raster graphics software(inkscape & gimp), or email/groupware software(evolution/kontact) makes it far, far easier to stay on the windows platform and at the same time, get the benefits of open source software at the application level. You get the benefits of OSS without the pain of changing a platform. In addition, it takes away any incentive people might have for adopting some "killer" app that might develop on the Linux platform. If it were exclusively available for linux, then there would be a much better incentive for people to switch platforms. This is the position apple has take with its iApps only porting the apps that directly further their platform goals (Quicktime & iTunes). You can draw a lot of people to the platform by making your "killer" apps only available on that platform. On linux, it has been argued that asterisk might be such an app, but this has more to do with the lack of windows support for the digium hardware than anything else, and this is mainly a server side app that people don't really see on thier desktops.
On the other hand, this type of thing would dramatically expand the user base of OSS software, which can be considered a very good thing if it results in overal improvements to the software that a larger, and involved, user base can bring. In addition it makes people "more used" to OSS apps so that if and when the platform changes (withouth thier choice/intervention most likely), the apps they are used to are still there and available. This assumes that people don't really choose operating systems, but merely accept what they are given.
Just so this doesn't get seen as a bad Stephen King prank, here is the linky.
I'll take one. I have a p3 550 cpu not doing anything and it needs a home. Contatct me at my gmail address with the name of joekowalski.
The idea is to have software the integrates and takes advantage of everything the kde environment has to offer. There are two ways of doing this. 1. Pull your hair out trying to cajole existing applications originally created off of an entirely different framework, to take some, limited advantage of what kde has to offer. 2. Start from scratch with an environment that makes fast development very easy and very quick, without massive quantities of hair left in your hands.
I wonder if the Spo-compton parking meter nazis will use this. I wouldn't be surprised as when I was living there attending Gonzaga, they had an incredible and uncanny ability to pounce on an expired meter literally withing 60 seconds of expiration. They probably could cut that time down to a quarter of that if each meter had a wifi device and a simple program to broadcast when a meter has expired.....
Well, the goal of the GPL is to expand the availability of Free (as in freedom) software, not to be "a standard for use in all applications."
SCO vs. Linux: The time of the conspiracy theories
In history around SCO and the source code from SCO existence, rich at idioms and twists, possibly transferred after Linux, new turns are to be reported. With the conspiracy theory that Microsoft behind SCO stands, it associates the theory that the refusal of the requirements of SCO is a only one, well camouflaged campaign of IBM. Thus the InfoWorld reported that SCO boss sees Darl McBride IBM as an author of the dirt campaign. IBM caused Novell to place itself against SCO meant McBride, employed long years with Novell as a director/conductor of the Netware Embedded division (NEST). IBM has talks floated to complain against SCO means it in addition. Also Eric Raymond of the open SOURCE initiative would stand on the pay roll IBMs, which would finance besides the Free software Foundation and thus the lawyer evenly Moglen, continued to implement Darl McBride.
While IBM as talk has the accusations lapidary for nonsense explained and about Novell none came, Eric Raymond raffte itself up to send an open letter at Darl McBride. In it answered in the negative Raymond by IBM to be paid did not deny however IBM to have helped. Altogether Raymond appealed to the reason of the SCO upper one with an allusion to the insight ability of Darth Vader : "you have the choice. Remove the dark helmet and converse with us like a human nature, or you continue your way, which lets bad times fear for us, however you and the entire SCO Topmanagement into the ruin will completely surely float."
Off the roaring star Wars Rhetorik Eric Raymond used the open letter, in order to make attentive on a Petition of the Linux Community, which were read out on the SCOForum. In their the SCO Group is requested to give up and all inkriminierten places in the SOURCE code call the confrontation course. In response the Linux programmers want to assure to revise all questionable places: "if right right-hurt-hurting that code in the Linux Kernel to be present should become, we it remove, because our community would not like to have a part of this Kernels."
The polite request will possibly remain without answer, because SCO with first, on which SCOForum published proofs could not convince. Apart from the problem of the "Greek" code is in the meantime the Berkeley presented by SCO pack filter (BPF) into the center of the interest moved. The SCO example originates from the file/sys/net/bpf.c, which is available here. In the cutout shown by SCO is missing the BSD Lizenzbedigungen, which is to be always called in accordance with BSD license: "Redistributions OF SOURCE code must retain the above copyright notice, this cunning OF conditions and the following more disclaimer." Because they are missing, code experts go such as Bruce Perens and Greg Lehey of the fact out that SCO with the example proved that the license conditions were removed agreement-adversely.
Thus a classical self-gate could be present, particularly since other possibilities are impossible. Like that the programmer of the version used in Linux was employed by BPF, Jay trainingist, with Caldera, wrote however the Clean Room variant of BPF before its time with Caldera. From the circles of former Caldera developers several persons can remember that in the SCO Trees in many places with the BSD code the copyright notes were missing. The procedure to cut "redundant" licenses off seems to have practiced also at other companies. Thus heise on-line developers to, that experienced the "technology" at Siemens Nixdorf, announced themselves. If the proof situation in the case SCO should confirm itself, then the code Hunter of this company excavated a proof, which occupies the exact opposite of the accusations by SCO. At least in the case of BPF SCO the power POINT presentation would not only have ( when ppt , when pdf ) separate the whole code make public, in order to weaken the suspicion.
SCO vs. Linux: The time of the conspiracy theories In history around SCO and the source code from SCO existence, rich at idioms and twists, possibly transferred after Linux, new turns are to be reported. With the conspiracy theory that Microsoft behind SCO stands, it associates the theory that the refusal of the requirements of SCO is a only one, well camouflaged campaign of IBM. Thus the InfoWorld reported that SCO boss sees Darl McBride IBM as an author of the dirt campaign. IBM caused Novell to place itself against SCO meant McBride, employed long years with Novell as a director/conductor of the Netware Embedded division (NEST). IBM has talks floated to complain against SCO means it in addition. Also Eric Raymond of the open SOURCE initiative would stand on the pay roll IBMs, which would finance besides the Free software Foundation and thus the lawyer evenly Moglen, continued to implement Darl McBride. While IBM as talk has the accusations lapidary for nonsense explained and about Novell none came, Eric Raymond raffte itself up to send an open letter at Darl McBride. In it answered in the negative Raymond by IBM to be paid did not deny however IBM to have helped. Altogether Raymond appealed to the reason of the SCO upper one with an allusion to the insight ability of Darth Vader : "you have the choice. Remove the dark helmet and converse with us like a human nature, or you continue your way, which lets bad times fear for us, however you and the entire SCO Topmanagement into the ruin will completely surely float." Off the roaring star Wars Rhetorik Eric Raymond used the open letter, in order to make attentive on a Petition of the Linux Community, which were read out on the SCOForum. In their the SCO Group is requested to give up and all inkriminierten places in the SOURCE code call the confrontation course. In response the Linux programmers want to assure to revise all questionable places: "if right right-hurt-hurting that code in the Linux Kernel to be present should become, we it remove, because our community would not like to have a part of this Kernels." The polite request will possibly remain without answer, because SCO with first, on which SCOForum published proofs could not convince. Apart from the problem of the "Greek" code is in the meantime the Berkeley presented by SCO pack filter (BPF) into the center of the interest moved. The SCO example originates from the file/sys/net/bpf.c, which is available here. In the cutout shown by SCO is missing the BSD Lizenzbedigungen, which is to be always called in accordance with BSD license: "Redistributions OF SOURCE code must retain the above copyright notice, this cunning OF conditions and the following more disclaimer." Because they are missing, code experts go such as Bruce Perens and Greg Lehey of the fact out that SCO with the example proved that the license conditions were removed agreement-adversely. Thus a classical self-gate could be present, particularly since other possibilities are impossible. Like that the programmer of the version used in Linux was employed by BPF, Jay trainingist, with Caldera, wrote however the Clean Room variant of BPF before its time with Caldera. From the circles of former Caldera developers several persons can remember that in the SCO Trees in many places with the BSD code the copyright notes were missing. The procedure to cut "redundant" licenses off seems to have practiced also at other companies. Thus heise on-line developers to, that experienced the "technology" at Siemens Nixdorf, announced themselves. If the proof situation in the case SCO should confirm itself, then the code Hunter of this company excavated a proof, which occupies the exact opposite of the accusations by SCO. At least in the case of BPF SCO the power POINT presentation would not only have ( when ppt , when pdf ) separate the whole code make public, in order to weaken the suspicion.
In the field of usability, bigger has been found to be, in general, better. Bigger interfaces are more tolerant to mistakes, are easier to "read" and interpret, can be accessed and used quicker, and are overall more obvious to use. Now, this isn't always the case, and stuff can be made too big, but most of the time this is the case. Pop "fitts law" into google for more info.
But I took it in a different direction. This would not just be a libel suit involving just Linus or the distromakers, this is defamation/libel of an entire community of developers. Thus a multi-plaintiff suit, or perhaps even a class-action suit might be more worthwhile. Second, my understanding of libel torts is that you while have to even prove intent to mislead/lie/etc, blatent negligence to the facts of your assertions can constitute this intent. If IBM isn't going to counter-sue, WE SHOULD.
And this is precisely why I run a looping chrooted bootstrap with prime95 in the background as a stability test for all of my overclocked systems. If they can consistently produce fully functional code with a really, really intense integer application hammering the system in the background for over 24 hours without croaking, I consider it stable. The sad thing is is that it isn't uncommon for me to come across boards from ECS that can't even hack this test at default clock speeds.....
Actually that story about what happend to Flight 93 is somewhat suspiscious see here.
You only have to make the source available to those that you provide binaries. Lindows, from what I understand lets you donwload the source packages for all gpl/lgpl binary packages that lindows distributes once you have become a Lindows customer. In other words, you don't have to make the sources completely public, but you can't keep the people you distribute the sources to from making them public.
Why can't AT&T have the users change the password immediatly after the first login? I.e, login for the first time with the default password, then FORCE a change of password before anything else can be done in the voicemail system. Combine this with a semirandom set of default passwords, then only accounts that are new would be even somewhat vulnerable.
Based on some informal googling I found that the average human head weighs around 10-13 lbs while attached (mine naturally is much heavier than that though). However, when it is detached, a significant amount of blood will be lost out of the head, and so you can then presume it to be 2-3 pounds lighter, unless you replace the blood with some sort of embalming fluid. Now if you are mailing this within the US, you can refer to the USPS rate chart available at www.usps.com
I just pulled the faad source from cvs, did a ./bootstrap, a ./configure, a make, and then a make install. It installed the lib in my Gentoo box to /usr/local/lib.
Perhaps this would be modded funny if people took the time figure out what the acronym for "Global Optical
Automatic Transient Search EXperiment" is.
And in Soviet russia, the soda fountain installs YOU!
Mod this down. Misleading link that has nothing to do with Greenspan. Link is actually to http://www.outwar.com/page.php?x=623513 which seems to be more of some kind of popularity counting site.
Lol....I wish I had some modpoints.
I've been running the 2.5 kernel on my laptop for a couple of weeks now to get the new cpufreq support. It seems to work really pretty well. Getting pcmcia-cs to build took some work, but I finally got it up and running and the performance of this new kernel is really nice, especially for the desktop.
The only catch with this though is that unless you have a lot of memory, or doing a stage3 install, the bootstrap and emerge system will a little longer because of less available memory. Otherwise it works really, really well, especially since the laptop network card support on the gentoo live cd's is somewhat incomplete.