The study DID NOT find that sleep deprivation increases the memory capability. Indeed, it found that despite the increased brain activity, the brain cannot overcome the sleep deprivation and performs poorly.
They had newconfig before we had newbus, our USB came from them, they have things we don't.
Frankly, it's very difficult to make a case for either FreeBSD or NetBSD, unless you have some particular hardware only one of them supports (NetBSD supports many more platforms than FreeBSD, but compared to the Intel platform it's a drop of water in the river), or a particular software feature (I don't know... PPPoN, maybe? jail? logfs?). NetBSD installation is not up to FreeBSD standards, though, and FreeBSD is much more popular.
Daniel C. Sobral obviously *didn't* point out exactly what I had to do
I did. I said you had to compile/install a new kernel, reboot, and then make world. This is exactly what you had to do.
since his information was quite incorrect./usr/src/UPDATING has been long out-of-date on FreeBSD 3.x
Since you were talking about running 4.0-CURRENT, I thought it would have been obvious that the correct file should be/usr/src/UPDATING from 4.0-CURRENT.
I'm well aware that -CURRENT is reserved for Big Important Busy People like yourself
-CURRENT is not supported. If you run into problems, you are expected to deal with them by yourself (which includes searching freebsd-current archives for a report on the problem). Furthermore, -CURRENT does not work all the time. Sometimes it just plain doesn't. It's very, very easy to end up with an unusable system while running -CURRENT.
Now, since the problem you described has been WIDELY reported on the mailing list, and since it is mentioned in/usr/src/UPDATING, of which all -current users should be aware of, you can't blame us for thinking you do not fit the profile of people who can run -current without much fear. That's why both bugg and me have advised you to stay away from it. It's not that we want to exclude you, it's just that we haven't got it to the user-friendlyness level you seem to be expecting.
That on my 3.4-STABLE box, the obvious thing to update from.
I fail to understand how the 3.4-STABLE source tree is the obvious place to get information on how to upgrade to 4.0-CURRENT. Perhaps, if you would update the source first, the file will then contain useful information?
FreeBSD does not have HOWTOs, we have documentation.:-)
Anyway, I do not know if it would be interesting for you, in particular to try FreeBSD. Some people like it better, some don't. It's a matter of taste.
For help, check out the official website for general information, the handbook for general documentation, the FAQ for frequently asked questions (including some installation problems) and the FreeBSD Diary for the most recommended beginner's site.
BTW, FreeBSD installation is generally known to be easy and painless. It can be done through the net by downloading just two floppy disk images, and there are mirror sites all over the world, and this list of mirror sites is shown to you during the installation.:-)
You obviously have not read/usr/src/UPDATING. Please, unless you take the time to read -current mailing list and search on it for problems, stay away from -current.
FYI, you must first compile a new kernel, reboot, and then make world. But that's just one of the many things you should take care of, so I recommend you wait until it becomes -stable, at which time a proper upgrade procedure should be in place.
Yeah, this is pretty much the way I see it, though you can add to that the despair of the last humans, who have been denied the stars so that their children could go beyond them.
The assertion that the Overlords are the protagonists is a reasonable one, though one I never made (I never bothered with identifying a protagonist -- the book is not about individual characters). Still, I can identify with everything you say, and it is really a shame that the Overlord's side of the story was ignored by the reviewer.
Childhood's End is my favorite Clarke's novel, and that's not a small thing. I fear the reviewer simply read the book with the wrong perspective. To his criticisms, I offer one simple answer: that's not what the book is about.
Forth offers all functionality needed to PROVIDE the features you mention. You can extend the language until it reads Perl code, if you want. The other way around is not possible, though...
First, FreeBSD upped it's default root partition size. It's 50Mb now, if I'm not mistaken. This was done so:
1)/tmp, which is not separate by default, gets more space. 2) GENERIC is getting bigger and bigger. This way we can keep a couple of kernel files around, Just In Case.
Second, Solaris uses a big root because it requires shared libs during single user boot. This greatly increases the amount of space required.
Third... "a couple core files"? First, core dumps are physical-memory sized. You ain't gonna have a couple of these on 30 Mb, unless you are using a computer with 8 Mb RAM.:-) Second, if you have ordinary programs core files in the root partition, you are doing something wrong. At the very least, / ought to be read only.
Frankly, this is not a good decision. What ought to have been ruled is that LINKING is not illegal, since it is not an actual copy of the content, and thus cannot possibly have broken a copyright license.
OTOH, I won't say I'm happy because the decision offers a loophole through which conduct piracy. It's not only illegal, it's not ethical. Let me put it this way: to illegaly copy a song is equivalent to take GPL code and violate it's license (by making it proprietary, for instance).
There I go... no moderation on this story just to answer to this.
In two words: not true.
A "closed group" of people? Of two hundred people with DIRECT access to the repository? Hell, that's so not true that you can see the very proof in the message to which this one is a reply. It mentions the treatment that Matthew Dillon received. Yes, and, guess what, he is a committer too.
There is nothing "closed" about FreeBSD. It gets new committers all the time, often people whose involvement with FreeBSD is quite recent.
Do you think all these people from all these different countries have always known each other? That they all even get along with each other all the time? The very existence of some incompatibilities between some of these developers is a proof that the group is by no means closed.
But, ok, let me back this with facts. Me. I once submitted a keyboard layout and a patch to the ide driver long, but never did anything to actually catch any attention. Then, around mid december 1998, I got interested in the on-going work with the boot loader. I submitted some patches and within two months I was a committer.
I certainly never got rejected by anyone who knew more than me, and I never saw any signs of envy from anyone knowing less than me.
Sure, I had to submit patches. You can't become a developer if you don't develop, though. But FreeBSD WILL welcome anyone who is actually willing to do something. This might range from doing userland programming to kernel programming to third-party applications porting to documentation writing to bug fixing. And even if your contribution is not in enough volume to turn you into a committer, your contributions are still accepted (like my keyboard map once was).
Don't trust me. Check for yourself. The list of committers, minus the core team, who are also committers, and the additional contributors. Feel free to count them. Pretty closed group, eh?:-)
And that's not even the complete list...
Now, let me ask you a question... did you intentionally misrepresented the facts, or you just failed to do any research and mindless repeated FUD you read elsewhere?
"Public corporation" refers to corporations that belong to the people (as in all people, through the government).
Please, do not try to apply english usage to a bad translation.:-) It says "all sectors of the Brazilian Government". So, please use that thing on top of your neck and realize that this was just a bad translation. Most of it is pretty bad, anyway.
For that matter, there have been articles from brazilian sources translated and slashdotted before. Like the Interview with WindowMaker (sp?) creator, a poll with Linux users on what they'd like to see in the next versions, specially wrt to documentation, and another one more recently I didn't bother to check.
Besides, for such a Linux-centered community, it can be downright ridiculous to assume all members of this community are US nationals.:-) Try, for instance... mmm... let me think... anyone hear heard of the Linus guy?:-)
Come on, now. Informative? Funny, certainly. Interesting, probably. Insightful, maybe. But informative? No way.
Hey anyone knows why attacks on BSD always come from Anonymous Cowards? Me thinks it's because they think all BSD users are expert hackers and will make their lives miserable if we find out their true identity. Which is true, of course, but they don't realize that we are snooping all connections to Slashdot through our back-door in Echelon, and preparing a major offensive on all these losers!
Slashdot Mirror
FreeBSD.
...has been using gigabit ethernet for some time.
The study DID NOT find that sleep deprivation increases the memory capability. Indeed, it found that despite the increased brain activity, the brain cannot overcome the sleep deprivation and performs poorly.
NetBSD has technical advantages over FreeBSD too.
They had newconfig before we had newbus, our USB came from them, they have things we don't.
Frankly, it's very difficult to make a case for either FreeBSD or NetBSD, unless you have some particular hardware only one of them supports (NetBSD supports many more platforms than FreeBSD, but compared to the Intel platform it's a drop of water in the river), or a particular software feature (I don't know... PPPoN, maybe? jail? logfs?). NetBSD installation is not up to FreeBSD standards, though, and FreeBSD is much more popular.
The license only applies to THEIR code, though BSDL allows someone to impose such restrictions.
No boom today, boom tomorrow. There is always a boom tomorrow. BOOM!
not one but two FreeBSD advocates/developers had to insult him
Can you please quote exactly what I said to offend the guy?
Daniel C. Sobral obviously *didn't* point out exactly what I had to do
/usr/src/UPDATING has been long out-of-date on FreeBSD 3.x
/usr/src/UPDATING from 4.0-CURRENT.
/usr/src/UPDATING, of which all -current users should be aware of, you can't blame us for thinking you do not fit the profile of people who can run -current without much fear. That's why both bugg and me have advised you to stay away from it. It's not that we want to exclude you, it's just that we haven't got it to the user-friendlyness level you seem to be expecting.
I did. I said you had to compile/install a new kernel, reboot, and then make world. This is exactly what you had to do.
since his information was quite incorrect.
Since you were talking about running 4.0-CURRENT, I thought it would have been obvious that the correct file should be
I'm well aware that -CURRENT is reserved for Big Important Busy People like yourself
-CURRENT is not supported. If you run into problems, you are expected to deal with them by yourself (which includes searching freebsd-current archives for a report on the problem). Furthermore, -CURRENT does not work all the time. Sometimes it just plain doesn't. It's very, very easy to end up with an unusable system while running -CURRENT.
Now, since the problem you described has been WIDELY reported on the mailing list, and since it is mentioned in
That on my 3.4-STABLE box, the obvious thing to update from.
I fail to understand how the 3.4-STABLE source tree is the obvious place to get information on how to upgrade to 4.0-CURRENT. Perhaps, if you would update the source first, the file will then contain useful information?
AFAIK, it's not a code freeze, but a feature freeze.
FreeBSD does not have HOWTOs, we have documentation. :-)
:-)
Anyway, I do not know if it would be interesting for you, in particular to try FreeBSD. Some people like it better, some don't. It's a matter of taste.
For help, check out the official website for general information, the handbook for general documentation, the FAQ for frequently asked questions (including some installation problems) and the FreeBSD Diary for the most recommended beginner's site.
BTW, FreeBSD installation is generally known to be easy and painless. It can be done through the net by downloading just two floppy disk images, and there are mirror sites all over the world, and this list of mirror sites is shown to you during the installation.
You obviously have not read /usr/src/UPDATING. Please, unless you take the time to read -current mailing list and search on it for problems, stay away from -current.
FYI, you must first compile a new kernel, reboot, and then make world. But that's just one of the many things you should take care of, so I recommend you wait until it becomes -stable, at which time a proper upgrade procedure should be in place.
OpenBSD? FreeBSD?
It's an install option with FreeBSD. (OpenBSD too, probably.)
Yeah, this is pretty much the way I see it, though you can add to that the despair of the last humans, who have been denied the stars so that their children could go beyond them.
The assertion that the Overlords are the protagonists is a reasonable one, though one I never made (I never bothered with identifying a protagonist -- the book is not about individual characters). Still, I can identify with everything you say, and it is really a shame that the Overlord's side of the story was ignored by the reviewer.
Childhood's End is my favorite Clarke's novel, and that's not a small thing. I fear the reviewer simply read the book with the wrong perspective. To his criticisms, I offer one simple answer: that's not what the book is about.
Forth offers all functionality needed to PROVIDE the features you mention. You can extend the language until it reads Perl code, if you want. The other way around is not possible, though...
So, which is the higher level language?
Let's clarify a few things...
/tmp, which is not separate by default, gets more space.
:-) Second, if you have ordinary programs core files in the root partition, you are doing something wrong. At the very least, / ought to be read only.
First, FreeBSD upped it's default root partition size. It's 50Mb now, if I'm not mistaken. This was done so:
1)
2) GENERIC is getting bigger and bigger. This way we can keep a couple of kernel files around, Just In Case.
Second, Solaris uses a big root because it requires shared libs during single user boot. This greatly increases the amount of space required.
Third... "a couple core files"? First, core dumps are physical-memory sized. You ain't gonna have a couple of these on 30 Mb, unless you are using a computer with 8 Mb RAM.
OTOH, I won't say I'm happy because the decision offers a loophole through which conduct piracy. It's not only illegal, it's not ethical. Let me put it this way: to illegaly copy a song is equivalent to take GPL code and violate it's license (by making it proprietary, for instance).
In two words: not true.
A "closed group" of people? Of two hundred people with DIRECT access to the repository? Hell, that's so not true that you can see the very proof in the message to which this one is a reply. It mentions the treatment that Matthew Dillon received. Yes, and, guess what, he is a committer too.
There is nothing "closed" about FreeBSD. It gets new committers all the time, often people whose involvement with FreeBSD is quite recent.
Do you think all these people from all these different countries have always known each other? That they all even get along with each other all the time? The very existence of some incompatibilities between some of these developers is a proof that the group is by no means closed.
But, ok, let me back this with facts. Me. I once submitted a keyboard layout and a patch to the ide driver long, but never did anything to actually catch any attention. Then, around mid december 1998, I got interested in the on-going work with the boot loader. I submitted some patches and within two months I was a committer.
I certainly never got rejected by anyone who knew more than me, and I never saw any signs of envy from anyone knowing less than me.
Sure, I had to submit patches. You can't become a developer if you don't develop, though. But FreeBSD WILL welcome anyone who is actually willing to do something. This might range from doing userland programming to kernel programming to third-party applications porting to documentation writing to bug fixing. And even if your contribution is not in enough volume to turn you into a committer, your contributions are still accepted (like my keyboard map once was).
Don't trust me. Check for yourself. The list of committers, minus the core team, who are also committers, and the additional contributors. Feel free to count them. Pretty closed group, eh?
And that's not even the complete list...
Now, let me ask you a question... did you intentionally misrepresented the facts, or you just failed to do any research and mindless repeated FUD you read elsewhere?
Packaging never contaminated anything. Ever seen a BSD GPLed because of GCC?
Please, do not try to apply english usage to a bad translation.
I have an issue with "must explicitly allow". How many licenses explicitly allow for distribution of compiled binaries, instead of implicitly?
Besides, for such a Linux-centered community, it can be downright ridiculous to assume all members of this community are US nationals.
(of course, the guy used a shotgun, which I think it's also illegal, but what the heck...
Hey anyone knows why attacks on BSD always come from Anonymous Cowards? Me thinks it's because they think all BSD users are expert hackers and will make their lives miserable if we find out their true identity. Which is true, of course, but they don't realize that we are snooping all connections to Slashdot through our back-door in Echelon, and preparing a major offensive on all these losers!
Then again, maybe not...