3) This guy was banned for only a month because he was responding in a very hostile way. He was told he would be unbanned at that point. However, he seems just like an angry individual in general, and I hope he gets counseling or something in order to help with anger management issues. He was not banned because he forked Growl, I think that's kind of neat actually and the point of being open source. He was being a poisonous person, and was removed as such. I will not discuss this any further, but wanted to address this here.
I'm sure you have no desire to discuss it any further, since it would shed a very unfavorable light on you. Still, I'd like you to point me to one (only one) angry/hostile post by this user. Because to me you seem to be the angry one, see http://www.mail-archive.com/growldiscuss@googlegroups.com/msg09608.html
It does still place a restriction on how you can partition your drives. The largest available drives today are 300GB, with hardware raid (common on servers) that number can well be much higher.
Especially a server system should be able to use all storage resources available during installation. There is no excuse for having this 1024 cylinder limit, it's simply a thing of the past.
OpenBSD 3.4 was a real stinker in these tests. The installation routine sucks, the disk performance sucks, the kernel was unstable, and in the network scalability department it was even outperformed by it's father, NetBSD. OpenBSD also gets points deducted for the sabotage they did to their IPv6 stack. If you are using OpenBSD, you should move away now.
Sabotage? Someone able to bring me up to speed on this?
Well, seems like someone just read the last paragraph of TFA. Just read the section about OpenBSD 3.4 near the top. You'll also find out that the complaints about the installation routine are not about the lack of a nice interface, but about not being able to install OpenBSD on a partition above 1024 cylinders.
As a someone who is relatively new to/., the 'geek scene', and alternative software
Welcome. Hope you like it here.
I haven't finished reading the article yet, [...]
It's quite obvious you're new. Noone here really reads the linked articles. Just read the headline, maybe skim the summary and then post either a "Fuck M$"! post or make a 1. [Headline] 2. ??? 3. Profit! joke. That's how it works here.
The GPL has no real valid legal meaning until it has been tested in a court of law. I think the fact that no GPL violation case has ever made it into a courtroom speaks volumes!
Yes it does. It means that until now noone has had the guts to risk a legal confrontation to free themselves from the requirements the GPL imposes.
And even if the GPL has no valid legal meaning, what remains? Standard copyright law. So without the GPL you don't even have the right to download the source, let alone modify and republish it!
Here is the complete article, the fscking lameness filter made it quite a struggle to get it posted here. Anyway:
Zwane Mwaikambo announced today on the lkml that he's successfully boot the 2.5.65 development kernel on a 32-way NUMA-Q server with -preempt enabled. Speaking to Robert Love [interview], the kernel preemption maintainer, he began his announcement saying, "Robert, I suppose you can add another notch on your erm.. bedpost(?) and congratulations to all the kernel developers!" NUMA awareness in the scheduler was added into the development kernel in late January [story].
William Lee Irwin III [interview] explained the significance of this achievement:
"This has had a hard time historically. I'm really glad NUMA-Q's are now immune (in the sense of correctness) to this config; previously it was believed that preemption points in printk(linux_banner) would take out the machine early in boot if preemption was enabled. Congratulations rml! If you're booting without issues on these things, you are a _very_ long way toward being race-free. This is incredibly good news, both for the preemption support, and for the general stability of the i386 bootstrap."
Read on for the full thread.
From: Zwane Mwaikambo Subject: 2.5.65-preempt booting on 32way NUMAQ Date: Sun, 6 Apr 2003 06:48:33 -0400 (EDT)
Robert i suppose you can add another notch on your erm.. bedpost(?) and congratulations to all the kernel developers! It survived some local networking stress tests, but there is more fun stuff like tty layer to completely obliterate;)
Patches required: 2.5.65 (only because isp1020 decided to get huffy) Purge assign_irq_vector panic - Zwane Mwaikambo
[boot messages]
From: Robert Love Subject: Re: 2.5.65-preempt booting on 32way NUMAQ Date: 06 Apr 2003 14:28:42 -0400
On Sun, 2003-04-06 at 06:48, Zwane Mwaikambo wrote: > Robert i suppose you can add another notch on our erm.. bedpost(?) > and congratulations to all the kernel developers! It survived some > local networking stress tests, but there is more fun stuff like tty > layer to completely obliterate;)
Excellent, Zwane.
Congratulations! Good work.
Robert Love
From: William Lee Irwin III Subject: Re: 2.5.65-preempt booting on 32way NUMAQ Date: Sun, 6 Apr 2003 04:23:40 -0700
On Sun, Apr 06, 2003 at 06:48:33AM -0400, Zwane Mwaikambo wrote: > Robert i suppose you can add another notch on our erm.. bedpost(?) > and congratulations to all the kernel developers! It survived some > local networking stress tests, but there is more fun stuff like tty > layer to completely obliterate;)
Wow!
This has had a hard time historically. I'm really glad NUMA-Q's are now immune (in the sense of correctness) to this config; previously it was believed that preemption points in printk(linux_banner) would take out the machine early in boot if preemption was enabled.
Congratulations rml!
If you're booting without issues on these things, you are a _very_ long way toward being race-free. This is incredibly good news, both for the preemption support, and for the general stability of the i386 bootstrap.
All that's really left is driver and non-i386 arch coverage if I'm right.
-- wli
From: Zwane Mwaikambo Subject: Re: 2.5.65-preempt booting on 32way NUMAQ Date: Sun, 6 Apr 2003 07:25:09 -0400 (EDT)
On Sun, 6 Apr 2003, William Lee Irwin III wrote:
> This has had a hard time historically. I'm really glad NUMA-Q's are now > immune (in the sense of correctness) to this config; previously it was > believed that preemption points in printk(linux_banner) would take out > the machine early in boot if preemption was enabled.
Which kernel version was that from
Re:But what I am rellay looking forward to...
on
KDE 3.1 Released
·
· Score: 1
Thanks for the response, I've been doing this myself. I just hoped there was a place where the developers discussed how the goal of a unified source tree could be achieved, what should be done next with KHTML etc. It seems to me right now that both teams are each taking code from the other one and merging it back into their tree without really communicating about future development work.
Re:But what I am rellay looking forward to...
on
KDE 3.1 Released
·
· Score: 2, Interesting
Speaking of Safari and a unified source tree for both projects, is there a public mailing list or newsgroup where one can monitor the progress (and the communication) between the two teams? Or is most of this happening in private mail between the developers?
There is another side-effect: Just think of an update that does not only fix two recent security flaws, but also implements incompatible changes to the CIFS/SMB protocol. All users of MS Software are forced to upgrade, so there won't be any interoperability issues. But all those Samba File/Print/PDC installations across the world are suddenly broken.
The problem with the Progeny installer is that it is not available for all platforms Debian supports, and it was decided it would be easier to write one from scratch.
Why it couldn't be used for the platform 90%+ of Debian users use (i386) I don't know.
Good distribution in what regard? If good == user-friendly || good == up-to-date, then Debian is certainly not very good. Debian has to decide if it wants to adopt these goals.
It correctly noted that Debian's distribution system rocks. Dselect is a great tool that works for more than simple installs.
This is not the point. I use Debian for over two years and I love apt-get, I love dselect. So what? It was a PAIN to learn and I only got through because it's a hobby for me!
Reading the insturctions that you MUST click out, you learn that simple vi style searches work!
AAHH!! You know why only geeks use vi or emacs? Because they SUCK! They are so friggin' unintuitive I think someone wanted to see what geeks can endure! It doesn't matter what they can do for you once you have mastered them, because "normal" people will never bother to go through all the hassle just to write some text. Debian has to realize this if they want to get better reviews in the future. dselect sucks from a usability standpoint. FIX IT, don't tell me what it can do if I stop thinking as a human.
This should be posted somewhere on bugzilla.mozilla.org where it's visible. Maybe make a big link "search bugzilla" with a longer search field and this text underneath. Thanks for this cool information!
I never said BSD was dead. I never said Slackware was dead. What I said was that the market for support and services in the enterprise space is overcrowded because there are
a) already many distributions to choose from b) these distributors nowadays offer all support and service contracts themselves because that's where the money is.
That's why I didn't mention the *BSDs or Slackware: they simply don't matter in this regard.
You can always differ, and I'm certainly not always right. But the language you use shows who the troll really is.
Slashdot Mirror
It looks like GNU really isn't Unix anymore...
3) This guy was banned for only a month because he was responding in a very hostile way. He was told he would be unbanned at that point. However, he seems just like an angry individual in general, and I hope he gets counseling or something in order to help with anger management issues. He was not banned because he forked Growl, I think that's kind of neat actually and the point of being open source. He was being a poisonous person, and was removed as such. I will not discuss this any further, but wanted to address this here.
I'm sure you have no desire to discuss it any further, since it would shed a very unfavorable light on you. Still, I'd like you to point me to one (only one) angry/hostile post by this user. Because to me you seem to be the angry one, see http://www.mail-archive.com/growldiscuss@googlegroups.com/msg09608.html
LinuxAnt have responded.
As stated in the press release, "[t]o avoid overlap with another open source project". That would be the Firebird database.
It does still place a restriction on how you can partition your drives. The largest available drives today are 300GB, with hardware raid (common on servers) that number can well be much higher.
Especially a server system should be able to use all storage resources available during installation. There is no excuse for having this 1024 cylinder limit, it's simply a thing of the past.
OpenBSD 3.4 was a real stinker in these tests. The installation routine sucks, the disk performance sucks, the kernel was unstable, and in the network scalability department it was even outperformed by it's father, NetBSD. OpenBSD also gets points deducted for the sabotage they did to their IPv6 stack. If you are using OpenBSD, you should move away now.
Sabotage? Someone able to bring me up to speed on this?
Well, seems like someone just read the last paragraph of TFA. Just read the section about OpenBSD 3.4 near the top. You'll also find out that the complaints about the installation routine are not about the lack of a nice interface, but about not being able to install OpenBSD on a partition above 1024 cylinders.
Man, even HURD is more advanced.
As a someone who is relatively new to /., the 'geek scene', and alternative software
Welcome. Hope you like it here.
I haven't finished reading the article yet, [...]
It's quite obvious you're new. Noone here really reads the linked articles. Just read the headline, maybe skim the summary and then post either a "Fuck M$"! post or make a 1. [Headline] 2. ??? 3. Profit! joke. That's how it works here.
The GPL has no real valid legal meaning until it has been tested in a court of law. I think the fact that no GPL violation case has ever made it into a courtroom speaks volumes!
Yes it does. It means that until now noone has had the guts to risk a legal confrontation to free themselves from the requirements the GPL imposes.
And even if the GPL has no valid legal meaning, what remains? Standard copyright law. So without the GPL you don't even have the right to download the source, let alone modify and republish it!
Here is the complete article, the fscking lameness filter made it quite a struggle to get it posted here. Anyway:
;)
;)
;)
Zwane Mwaikambo announced today on the lkml that he's successfully boot the 2.5.65 development kernel on a 32-way NUMA-Q server with -preempt enabled. Speaking to Robert Love [interview], the kernel preemption maintainer, he began his announcement saying, "Robert, I suppose you can add another notch on your erm.. bedpost(?) and congratulations to all the kernel developers!" NUMA awareness in the scheduler was added into the development kernel in late January [story].
William Lee Irwin III [interview] explained the significance of this achievement:
"This has had a hard time historically. I'm really glad NUMA-Q's are now immune (in the sense of correctness) to this config; previously it was believed that preemption points in printk(linux_banner) would take out the machine early in boot if preemption was enabled. Congratulations rml! If you're booting without issues on these things, you are a _very_ long way toward being race-free. This is incredibly good news, both for the preemption support, and for the general stability of the i386 bootstrap."
Read on for the full thread.
From: Zwane Mwaikambo
Subject: 2.5.65-preempt booting on 32way NUMAQ
Date: Sun, 6 Apr 2003 06:48:33 -0400 (EDT)
Robert i suppose you can add another notch on your erm.. bedpost(?) and congratulations to all the kernel developers! It survived some local networking stress tests, but there is more fun stuff like tty layer to completely obliterate
(Hardware courtesy of OSDL)
Running configuration
32 Processors, PIII 500
32G RAM
Patches required:
2.5.65 (only because isp1020 decided to get huffy)
Purge assign_irq_vector panic - Zwane Mwaikambo
[boot messages]
From: Robert Love
Subject: Re: 2.5.65-preempt booting on 32way NUMAQ
Date: 06 Apr 2003 14:28:42 -0400
On Sun, 2003-04-06 at 06:48, Zwane Mwaikambo wrote:
> Robert i suppose you can add another notch on our erm.. bedpost(?)
> and congratulations to all the kernel developers! It survived some
> local networking stress tests, but there is more fun stuff like tty
> layer to completely obliterate
Excellent, Zwane.
Congratulations! Good work.
Robert Love
From: William Lee Irwin III
Subject: Re: 2.5.65-preempt booting on 32way NUMAQ
Date: Sun, 6 Apr 2003 04:23:40 -0700
On Sun, Apr 06, 2003 at 06:48:33AM -0400, Zwane Mwaikambo wrote:
> Robert i suppose you can add another notch on our erm.. bedpost(?)
> and congratulations to all the kernel developers! It survived some
> local networking stress tests, but there is more fun stuff like tty
> layer to completely obliterate
Wow!
This has had a hard time historically. I'm really glad NUMA-Q's are now immune (in the sense of correctness) to this config; previously it was
believed that preemption points in printk(linux_banner) would take out the machine early in boot if preemption was enabled.
Congratulations rml!
If you're booting without issues on these things, you are a _very_ long way toward being race-free. This is incredibly good news, both for the preemption support, and for the general stability of the i386 bootstrap.
All that's really left is driver and non-i386 arch coverage if I'm right.
-- wli
From: Zwane Mwaikambo
Subject: Re: 2.5.65-preempt booting on 32way NUMAQ
Date: Sun, 6 Apr 2003 07:25:09 -0400 (EDT)
On Sun, 6 Apr 2003, William Lee Irwin III wrote:
> This has had a hard time historically. I'm really glad NUMA-Q's are now
> immune (in the sense of correctness) to this config; previously it was
> believed that preemption points in printk(linux_banner) would take out
> the machine early in boot if preemption was enabled.
Which kernel version was that from
Thanks for the response, I've been doing this myself. I just hoped there was a place where the developers discussed how the goal of a unified source tree could be achieved, what should be done next with KHTML etc. It seems to me right now that both teams are each taking code from the other one and merging it back into their tree without really communicating about future development work.
Speaking of Safari and a unified source tree for both projects, is there a public mailing list or newsgroup where one can monitor the progress (and the communication) between the two teams? Or is most of this happening in private mail between the developers?
Oh my god, have we slashdotted ati.com? I can't reach their site anymore.
:-)
Probably running their new drivers on the linux-powered webserver.
There is another side-effect: Just think of an update that does not only fix two recent security flaws, but also implements incompatible changes to the CIFS/SMB protocol. All users of MS Software are forced to upgrade, so there won't be any interoperability issues. But all those Samba File/Print/PDC installations across the world are suddenly broken.
And Samba is just a randomly picked example.
It is fine not to like you Windows, but you don't have to make it that using Windows is the crime of the century.
You're new to Slashdot, aren't you?
The problem with the Progeny installer is that it is not available for all platforms Debian supports, and it was decided it would be easier to write one from scratch.
Why it couldn't be used for the platform 90%+ of Debian users use (i386) I don't know.
Good distribution in what regard? If good == user-friendly || good == up-to-date, then Debian is certainly not very good. Debian has to decide if it wants to adopt these goals.
It correctly noted that Debian's distribution system rocks. Dselect is a great tool that works for more than simple installs.
This is not the point. I use Debian for over two years and I love apt-get, I love dselect. So what? It was a PAIN to learn and I only got through because it's a hobby for me!
Reading the insturctions that you MUST click out, you learn that simple vi style searches work!
AAHH!! You know why only geeks use vi or emacs? Because they SUCK! They are so friggin' unintuitive I think someone wanted to see what geeks can endure! It doesn't matter what they can do for you once you have mastered them, because "normal" people will never bother to go through all the hassle just to write some text. Debian has to realize this if they want to get better reviews in the future. dselect sucks from a usability standpoint. FIX IT, don't tell me what it can do if I stop thinking as a human.
trust me, I am a mcse ;-)
famous last words...
It's funny. Laugh.
Yes it is, although it should be noted that the author uses Python under Windows, so additional help and tips are mainly relevant for that platform.
Man, you want the job to be done well.
This should be posted somewhere on bugzilla.mozilla.org where it's visible. Maybe make a big link "search bugzilla" with a longer search field and this text underneath. Thanks for this cool information!
Are you sure the 286 had 32 bit registers? AFAIK they were introduced with the 386, all of them.
That's what everyone said when Lokigames filed for Chapter 11...
I never said BSD was dead. I never said Slackware was dead. What I said was that the market for support and services in the enterprise space is overcrowded because there are
a) already many distributions to choose from
b) these distributors nowadays offer all support and service contracts themselves because that's where the money is.
That's why I didn't mention the *BSDs or Slackware: they simply don't matter in this regard.
You can always differ, and I'm certainly not always right. But the language you use shows who the troll really is.