Some others have already mentioned 'The Hobbit', which is great for his age (I read it to my son at the same age yours is).
I can't believe no one has yet mentioned 'Harry Potter and the Philosopher's Stone' yet though. That was about the age I read that to my son too. The only caveat is be careful how fast you progress. He's likely not old enough for 'Harry Potter and the Deathly Hallows'. We've tackled that by giving one a year for Christmas.
That will just result in them getting more argumentative and less likely to form a government.
Instead, you must have sex with a different senator of another party each day until a government is formed.
I predict either a government forming on day one or a unity government coming together after a month or so. I also predict a sudden surge in viewership for Belgian parliamentary broadcasts.
Did you even RTFA? Here is a quote:
"I felt like I was letting down one of our most promising engineers. He was someone who had the most knowledge about the business we supported and was an expert in the core client-server application. "
It wasn't someone sitting in a corner shooing kids off his lawn while he became an old curmudgeon, it was the team lead in the core application. I don't know about you, but I don't always have time to become an expert in every new IT technology that comes along. I have limited time and so I pick and choose. This guy had spent his time working hard and becoming their team lead, which naturally meant focusing on their core business and application. He then finds out they're hiring graduates at a 30% higher salary and expecting him to mentor them in the business requirements because he hasn't also had time to become an expert in mobile applications. Tell me you wouldn't be pissed off in such a situation?
Yes, the salary for the graduates was driven by the market, and purely from a fiscal perspective the company did the best thing for it. Let's not pretend though that there aren't people involved and that they weren't screwed.
They'll ignore it. The LDS church hierarchy never comments on stuff like this anyway. You might see some apologist from BYU or FARMS write an article that will allow wavering intelligent saints who actually read studies like this to paper over yet another crack in the fabric of their reality, but that will be the extent of it.
Besides, for most of them this isn't a new "stunning disproof" of their religion since there have been previous genetic studies of Native Americans which have shown them to not be Semitic in the slightest. Even if it were such a "stunning disproof" the "true believers" would still ignore it.
Remember that you're talking about people who believe they need to learn secret pass phrases and handshakes to get into the celestial kingdom. Not to mention the magic undies:).
You've completely missed the point. The problem isn't distribution. The problem is that although you can distribute the dual-licensed code under whichever of the licenses you choose, you can't file the other license off the code (in general). In this case, the BSD license specifically disallows doing this. The intent of the patch that was being complained about was exactly that, it filed the BSD license off the code while keeping the GPL license intact. Only the copyright holder(s) of the code can decide to do that.
For reference, here are the relevant clauses of the BSD license:
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
That makes it pretty clear that removing the copyright notice from redistributions of the code is illegal.
So true. You should clearly side with the governments of the only countries to support the reelection of President Bush, Russia and Iran. They obviously have the best interests of the USA at heart.
However, this is a completely different situation than NetBSD importing it.
NetBSD and OpenBSD both distribute X as a distribution set, that is, as part of the main operating system. They maintain a separate source tree for X inside their main repositories.
This is quite different from being part of the FreeBSD ports collection which houses a diverse collection of third party software, much of which would never be incorporated into FreeBSD itself due to license incompatbilities. So, the question of whether FreeBSD has a problem is not being addressed by its presence in the ports collection since the ports collection can contain pretty much anything, including ports of commercial software.
I think you'll find that FreeBSD has only made amd64 a tier-1 architecture starting with FreeBSD 5.2 which isn't out yet and has been recently delayed until January.
See the freebsd-arch thread starting with the
post by Doug Barton. In particular, point 2 of his future actions says:
Backport/etc/rc.subr to RELENG_4 prior to 4.9-Release. The purpose here is to allow ports authors to make use of the rcNG system for their
startup scripts, and to possibly allow us to backport major features that just work better in the NG framework.
Later posts mention how to use rcNG in ports scripts and still maintain backwards compatibility.
One of the features of rcNG is to allow dependencies. For example, the nfsd startup script expresses a dependency on mountd, so starting nfsd with the script will first check if mountd isn't started and start that. This is, IMO, more powerful than the SysV concept of ordering where scripts are started and stopped when changing run levels based on their "number".
No, rcNG also applies to the ports start up scripts.
What you're seeing is that most port maintainers haven't updated the start up scripts for their ports to use rcNG. This will happen in time, particularly as more people move to 5.x (probably starting with 5.1).
Actually, I define FUD in the traditional meaning of "fear, uncertainty, doubt". You'll note that the original article included, amongst similar content, the question "Would someone from the FreeBSD team care to elaborate and assuage our worries?". The stated "worries" is presumably because the poster is now in a state of fear, uncertainty or doubt about the future of FreeBSD. Spreading this, without any basis, is normally referred to as "FUD".
See the repeated "Matt Dillon has left, FreeBSD is dying" posts for an example.
Also, please read the "secret" rules before commenting on them. The "elite" cabal is also publically documented.
With FreeBSD, you basically have a bunch of whiny elitest developers writing code behind closed doors and releasing periodic snapshots for the dirty masses to consume.
Please explain how a public CVS repository (and CVS commit mailing list) is "writing code behind clsoed doors".
While you are at it, you may want to explain the logical leap from internal developer politics to code openness.
You seem to have some of your terminology mixed up.
Core are not the only ones allowed to commit. They are simply the democratically elected body of committers who preside over the welfare of the project. There are many more committers than there are Core members. I don't see Core as a particularly lofty title (for heavens sake, they have to be called something).
Note that until a few years ago, Core wasn't elected, so its hard to argue that the project is moving in a direction that is more dictatorial.
For that matter, I can't seriously believe you are arguing that FreeBSD is somehow a big bad dictatorship when you've just compared it to Linux. Linux has a committer list of precisely one, Linus. Perhaps you need to refresh your memory on what a dictatorship is:).
This has to be one of the most FUD ridden articles that have been posted in a while.
Firstly, the FreeBSD Core team (the use of "core developer" in the title of the article could be misleading) have given a lengthy explanation of this decision on the developers private list. This is where the explanation belongs and where it should stay. The reasons and the action are internal to the project and don't need to be aired in public.
Secondly, Matt is not the first, nor the last I dare say, high profile developer to leave the project. It didn't mean the death of FreeBSD then, it doesn't now. No single developer, no matter how talented and hard working, is irreplaceable. While Matt's technical contributions will certainly be missed, the claims of "imminent death, film at 11" are the same baseless FUD that came out when Mike Smith left or would have come out when John Dyson left (had Slashdot been around).
Thirdly, Matt is still free to contribute should he so wish. The only difference is that he will now have to contribute through PRs, at least for the near future, just as every other contributor started off doing, rather than directly committing himself. Whether he chooses to do this once the dust has settled is, of course, up to Matt.
Finally, long live FreeBSD! Can we please get back to worthwhile stories now:).
Slashdot Mirror
Some others have already mentioned 'The Hobbit', which is great for his age (I read it to my son at the same age yours is).
I can't believe no one has yet mentioned 'Harry Potter and the Philosopher's Stone' yet though. That was about the age I read that to my son too. The only caveat is be careful how fast you progress. He's likely not old enough for 'Harry Potter and the Deathly Hallows'. We've tackled that by giving one a year for Christmas.
That will just result in them getting more argumentative and less likely to form a government. Instead, you must have sex with a different senator of another party each day until a government is formed. I predict either a government forming on day one or a unity government coming together after a month or so. I also predict a sudden surge in viewership for Belgian parliamentary broadcasts.
Did you even RTFA? Here is a quote: "I felt like I was letting down one of our most promising engineers. He was someone who had the most knowledge about the business we supported and was an expert in the core client-server application. " It wasn't someone sitting in a corner shooing kids off his lawn while he became an old curmudgeon, it was the team lead in the core application. I don't know about you, but I don't always have time to become an expert in every new IT technology that comes along. I have limited time and so I pick and choose. This guy had spent his time working hard and becoming their team lead, which naturally meant focusing on their core business and application. He then finds out they're hiring graduates at a 30% higher salary and expecting him to mentor them in the business requirements because he hasn't also had time to become an expert in mobile applications. Tell me you wouldn't be pissed off in such a situation? Yes, the salary for the graduates was driven by the market, and purely from a fiscal perspective the company did the best thing for it. Let's not pretend though that there aren't people involved and that they weren't screwed.
But there's nothing so lonesome, morbid or drear!
Besides, for most of them this isn't a new "stunning disproof" of their religion since there have been previous genetic studies of Native Americans which have shown them to not be Semitic in the slightest. Even if it were such a "stunning disproof" the "true believers" would still ignore it.
Remember that you're talking about people who believe they need to learn secret pass phrases and handshakes to get into the celestial kingdom. Not to mention the magic undies :).
For reference, here are the relevant clauses of the BSD license:
That makes it pretty clear that removing the copyright notice from redistributions of the code is illegal.
Good to see Linux catching up. Too bad it won't be in the kernel for you ;).
So true. You should clearly side with the governments of the only countries to support the reelection of President Bush, Russia and Iran. They obviously have the best interests of the USA at heart.
NetBSD and OpenBSD both distribute X as a distribution set, that is, as part of the main operating system. They maintain a separate source tree for X inside their main repositories.
This is quite different from being part of the FreeBSD ports collection which houses a diverse collection of third party software, much of which would never be incorporated into FreeBSD itself due to license incompatbilities. So, the question of whether FreeBSD has a problem is not being addressed by its presence in the ports collection since the ports collection can contain pretty much anything, including ports of commercial software.
On the other hand, NetBSD has had amd64 support since 2001.
OpenBSD is reportedly working on it, but I haven't seen anything hit the tree as yet.
I thought thats what they called Papa Smurf.
Backport /etc/rc.subr to RELENG_4 prior to 4.9-Release. The purpose here is to allow ports authors to make use of the rcNG system for their
startup scripts, and to possibly allow us to backport major features that just work better in the NG framework.
Later posts mention how to use rcNG in ports scripts and still maintain backwards compatibility.One of the features of rcNG is to allow dependencies. For example, the nfsd startup script expresses a dependency on mountd, so starting nfsd with the script will first check if mountd isn't started and start that. This is, IMO, more powerful than the SysV concept of ordering where scripts are started and stopped when changing run levels based on their "number".
No, rcNG also applies to the ports start up scripts. What you're seeing is that most port maintainers haven't updated the start up scripts for their ports to use rcNG. This will happen in time, particularly as more people move to 5.x (probably starting with 5.1).
Also, please read the "secret" rules before commenting on them. The "elite" cabal is also publically documented.
Please explain how a public CVS repository (and CVS commit mailing list) is "writing code behind clsoed doors".
While you are at it, you may want to explain the logical leap from internal developer politics to code openness.
Core are not the only ones allowed to commit. They are simply the democratically elected body of committers who preside over the welfare of the project. There are many more committers than there are Core members. I don't see Core as a particularly lofty title (for heavens sake, they have to be called something).
Note that until a few years ago, Core wasn't elected, so its hard to argue that the project is moving in a direction that is more dictatorial.
For that matter, I can't seriously believe you are arguing that FreeBSD is somehow a big bad dictatorship when you've just compared it to Linux. Linux has a committer list of precisely one, Linus. Perhaps you need to refresh your memory on what a dictatorship is :).
Firstly, the FreeBSD Core team (the use of "core developer" in the title of the article could be misleading) have given a lengthy explanation of this decision on the developers private list. This is where the explanation belongs and where it should stay. The reasons and the action are internal to the project and don't need to be aired in public.
Secondly, Matt is not the first, nor the last I dare say, high profile developer to leave the project. It didn't mean the death of FreeBSD then, it doesn't now. No single developer, no matter how talented and hard working, is irreplaceable. While Matt's technical contributions will certainly be missed, the claims of "imminent death, film at 11" are the same baseless FUD that came out when Mike Smith left or would have come out when John Dyson left (had Slashdot been around).
Thirdly, Matt is still free to contribute should he so wish. The only difference is that he will now have to contribute through PRs, at least for the near future, just as every other contributor started off doing, rather than directly committing himself. Whether he chooses to do this once the dust has settled is, of course, up to Matt.
Finally, long live FreeBSD! Can we please get back to worthwhile stories now :).