The moderators are not one-dimensional, but the way how the moderation is presented makes them look so.
It's a bug in Slashcode. If it annoys you, get the code and post the fix. The moderation flavor of the message should be determined by majority of the moderations, not by the last moderation.
Even better, the flavor of the message should be determined by majority of the moderations with the same polarity as the sum of moderations made to the post, so that a message moderated up would never be marked as Flamebait, even if it got e.g. 2 Flamebait, 1 Insightful, 1 Interesting and 1 Funny.
Of course, the ties should be so solved in favor of the last moderation.
Wouldn't the mod point wasted on the previous
comment (about nipples) be better spent on the
parent comment?
I believe that very few people are using
threshold 0, and they should see a lot of
such comments made by ACs. I wouldn't worry much
about them.
On the other side, people who read at +3 are here
to read good comments. They would win if an
informative comment is moderated from +2 to +3.
And these are the people who/. really needs,
who can make/. better,
unlike those who come here to read troll
comments.
I'm amazed that Pete Zaitcev continues to update YMF PCI sound driver in the middle of discussion about the source layout of ALSA drivers. Nobody doubts that ALSA will be included, the only question is how.
I believe one of the problems is that the distinction between public and private speech is blurred on the net. If I publish a comment on a prominent site, e.g. Slashdot, that's clearly public speech. If I write an e-mail to a single person, that's clearly private speech. But what if I put my comment on a site that very few people know about? Where is exactly the boundary?
If the URL is cryptic, then it's private, e.g.:
http://www.foo.net/203e29be2c571dabb41f651fdcc103/
But if it's easier to guess? What if Mike describes his experience on angrymike.com? And what if it's veryveryangrymike2002.com? Is it the number of visitors that matters?
It's a bug, that's why it's in bugzilla. And please note, the bug is not closed! I don't think that anybody would break ABI compatibility intentionally.
You contention that "major Linux distros can't keep binary compatibility between updates and errata" is not corroborated by any evidence. It is only RedHat and they seem to be working on the correct fix now.
Re:Picture of bills with US bill
on
The Euro
·
· Score: 1
Using jet engines to slow down in thin atmosphere
on
Flying on Mars
·
· Score: 3, Insightful
From the article:
Reverse thrust? NOPE!!!! With only 1% atmosphere, jet or prop engines can put out basically no thrust...
I was surprised that Austin Meyer doesn't understand that the thrust of jet engines in either direction doesn't depend on the atmosphere density, unlike prop engines. Am I missing something?
The sound drivers are very poorly written. A lot of code is duplicated. Not all drivers support some ioctls. Every driver has its peculiarities, e.g. some drivers reset dsp to mono, 8bit on DSP_RESET, some don't. Some support/dev/audio, some don't.
Not having ALSA in 2.4.x means no good sound support in the stable kernel for another year of two. Do you plan to integrate ALSA into the 2.4 branch? If yes, will it happen after it's done on the 2.5 branch?
The funniest error message that I've ever seen
was
expect unexpected
Actually, the message was telling me that
the keyword "expect" was not expected
to be in that position.
Alan's branch
on
Linux 2.4.13
·
· Score: 5, Interesting
SlashDot seems to pay more attention
to the Linus' branch, but if you really
want to be on the edge, you should
track the Alan's branch (i.e. the "ac"
series). The branches are synchronized
with each other from
time to time, but if you want to fix some
problem, check the code in the AC branch -
it may have the fix already.
That's especially true for the sound
drivers.
As for stability, the Linus' releases
don't seem to be formally tested anyway.
Maybe Linus is more conservative in
applying patches before the release,
but the recent events (2.4.11 and 2.4.12)
show that the kernel may not compile
in a common configuration and
be released notwithstanding.
Re:Small Unix utilities written in assembly
on
Tiny Apps
·
· Score: 3, Informative
Another poster already mentioned
Busybox
(site seems to be broken now, but I'm including the link anyway).
Together with
Tinylogin
,
it provides everything you
need for setting up an embedded
OS, including init, shell and login.
On the other side, those utilities
only work on GNU/Linux and GNU/Hurd.
Only purist 'license zealots' will
worry about the terms of the license.
Wrong. If you violate the license you
are potentially in trouble. If you are
a company in Europe or in the
United States and you use Qt in
violation of the license, your chances
to be sued by Trolltech are very high
(I would say above 50%).
Of course, if you are in Russia (seems to be the case for you) or
in North Korea or in Iraq, you
may want to risk. However, please
don't generalize. I'm not a license
zealot, but I'm not going to
violate their license (e.g. pretend
to be a university professor).
Resistance drops by a factor of about 1 million?
on
Desktop Biodetectors
·
· Score: 2
Cork said that when targets such as anthrax, smallpox or tuberculosis are in the sample, electrical resistance across the gap typically drops by a factor of about 1 million, thus providing a definitive sign of their presence.
I'm sorry but I don't believe it. It's very unlikely that the cells are so different and no other cells (i.e. benign microorganisms) have this property. Can anybody comment on this?
I think it's a waste of money to use systems so many integrated components for a cluster. Do you really need Firewire, S-Video output and all other fancy things on every node?
Perhaps Shuttle could make another version of the motherboard, more suitable for low-end servers, and put it to a similar box. That would be more suitable for the Beowulf cluster.
Slashdot Mirror
Wow! Timothy refused to advertize KMart on Slashdot. As a result, KMart filed for Chapter 11.
It's a bug in Slashcode. If it annoys you, get the code and post the fix. The moderation flavor of the message should be determined by majority of the moderations, not by the last moderation.
Even better, the flavor of the message should be determined by majority of the moderations with the same polarity as the sum of moderations made to the post, so that a message moderated up would never be marked as Flamebait, even if it got e.g. 2 Flamebait, 1 Insightful, 1 Interesting and 1 Funny.
Of course, the ties should be so solved in favor of the last moderation.
I believe that very few people are using threshold 0, and they should see a lot of such comments made by ACs. I wouldn't worry much about them.
On the other side, people who read at +3 are here to read good comments. They would win if an informative comment is moderated from +2 to +3. And these are the people who /. really needs,
who can make /. better,
unlike those who come here to read troll
comments.
Sorry for offtopic, but it's getting annoying.
I'm amazed that Pete Zaitcev continues to update YMF PCI sound driver in the middle of discussion about the source layout of ALSA drivers. Nobody doubts that ALSA will be included, the only question is how.
By the way, do you know that FTP sends plain text password over the net?
I remember seeing 35 mod points on a comment saying that dropping nukes on Japan in WWII was justified.
Soon every electric chair will have an IP address and web based interface.
it is also the first *BSD OS to have version above 4.4.
If the URL is cryptic, then it's private, e.g.: http://www.foo.net/203e29be2c571dabb41f651fdcc103/
But if it's easier to guess? What if Mike describes his experience on angrymike.com? And what if it's veryveryangrymike2002.com? Is it the number of visitors that matters?
You contention that "major Linux distros can't keep binary compatibility between updates and errata" is not corroborated by any evidence. It is only RedHat and they seem to be working on the correct fix now.
http://www.bep.treas.gov/document.cfm/5/43/150
... and the third pilot as sysadmin.
I was surprised that Austin Meyer doesn't understand that the thrust of jet engines in either direction doesn't depend on the atmosphere density, unlike prop engines. Am I missing something?
Of course no admin is needed for the landing
This kind of experiment would be a relatively easy to implement on a Beowulf cluster by simulating one or more chips on every node.
My children will have separate accounts.
Agvogato misspelled his name and then apologized
below in a comment to the article. Too bad they
didn't edit the actual article.
Not having ALSA in 2.4.x means no good sound support in the stable kernel for another year of two. Do you plan to integrate ALSA into the 2.4 branch? If yes, will it happen after it's done on the 2.5 branch?
expect unexpected
Actually, the message was telling me that the keyword "expect" was not expected to be in that position.
As for stability, the Linus' releases don't seem to be formally tested anyway. Maybe Linus is more conservative in applying patches before the release, but the recent events (2.4.11 and 2.4.12) show that the kernel may not compile in a common configuration and be released notwithstanding.
On the other side, those utilities only work on GNU/Linux and GNU/Hurd.
Of course, if you are in Russia (seems to be the case for you) or in North Korea or in Iraq, you may want to risk. However, please don't generalize. I'm not a license zealot, but I'm not going to violate their license (e.g. pretend to be a university professor).
$ killall ebola
Permission denied
$ su
Password:
# killall ebola
# killall ebola
# killall -KILL ebola
deathstar kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000134
deathstar kernel: current->tss.cr3 = 2526c000, %%cr3 = 2526c000
deathstar kernel: *pde = 00000000
deathstar kernel: Oops: 0002
deathstar kernel: CPU: 1
deathstar kernel: EIP: 0010:[decontaminate+188/344]
deathstar kernel: EFLAGS: 00010206
deathstar kernel: eax: 00000100 ebx: df622e40 ecx: df622e40 edx: efd0ba10
deathstar kernel: esi: df622e40 edi: 00000000 ebp: c07ff820 esp: d5469d70
deathstar kernel: ds: 0018 es: 0018 ss: 0018
deathstar kernel: Process ebola (pid: 6913, process nr: 59, stackpage=d5469000)
Perhaps Shuttle could make another version of the motherboard, more suitable for low-end servers, and put it to a similar box. That would be more suitable for the Beowulf cluster.