All frontline workers have Windows desktops (looks like 2000 Workstation) which they run a terminal app on to connect to what looks like a UNIX back end of some description.
Home taping is hard to use as a comparison because it doesn't have the network effects that benefit the distribution efficency of P2P file sharing.
Home taping was limited by: time taken to dub the album; usage of physical media; the number of people you knew or could get in contact with via conventional means (snail mail, phone, fax etc.etc.). So one person sharing an album had limited impact due to constraints on time, resources and reach.
A pervasive network such as the Internet allows someone to share with complete strangers and do so without any effort on their part. Although still limited to an extent by some resources (particulary bandwidth), sharing via P2P networks is vastly more efficient then home taping.
Steve Cannane is the presenter of Hack, a half hour current affairs program on the national "youth" radio station Triple J.
There isn't much bio information on the website but he is in his second year of presenting Triple J's current affairs program and was previously a reporter for same. You can listen to the show online.
IBM will win on the merits of the case (IMHO, going on the current state of play evidenced by all the court filings) but more importantly they can afford to fight this. SCO's intent is to drag it out as long as possible but IBM has more money in the piggy bank for paying all those expensive lawyer types.
I think the grandparent's point was that a large company can bankroll this defence. Compare this to the recent Spamhaus case, where depsite winning the case Steve Linford & Co can't afford the legal bill.
Problem is, you can't really "step aside" from the architectural issues given the point he is making. The DDoS attacks on SCO have been exclusively aimed, as far as I can tell from the reports, at their *web* sites -- which appear to be located in a Denver co-location.
If the attacks had been aimed at SCO's mail server, or local ISP connection, then then Hafen might have a point. But unless he's using the Denver co-lo for his office connection and e-mail, then I think he just has a problem with his ISP that is unrelated to the DDoS attacks on SCO.
I think you'll find that the DOS is aimed generally at SCO's servers in the co-location facility, not at any particular service on those servers.
Other customers in the colo facility might not be the target of the attack but if the DOS is sufficiently large it will take out network elements upstream of SCO's equipment that these other companies connections also run through.
ie. some of center7's core or border routers are being affected.
if i could do a traceroute to either of them i'd show you what i mean, but it just keeps timing out.
Many of the distributor's fixes are ad hoc kludges that are designed to quickly making the thing *work*, ignoring elegance and maintainability...
I don't understand why a distro would bother shipping a kernel (or app for that matter) with a patch that was "ad hoc". It wouldn't exactly endear their customers to provide repeat business.
I think you will find that most distros test their patched kernels thoroughly before releasing them to the world. This would include not only checking that the patch fixes the problem, but that it compiles on all supported architectures and does not jeopradise future modifications to the same bit of code or adjacent or related pieces of code.
Why they don't submit all the patches to the kernel maintainer I don't know? Maybe the patch was submitted and was passed over or missed and then not resubmitted.
Dark address space refers to globally unique IPs (ie. not private IPs as defined by the RFCs) that should be accessible from anywhere on the internet but are not due to one of many reasons. The two reasons I am most familiar with are:
Route filtering.
To reduce the size of the routing table in the memory of their core routers, some providers throw away announcements of small blocks (say/24 or longer masks). This means that unless there is an aggregrate route for that block that will get the packets there eventually, the IP is dark for people using that provider.
Some providers also filter blocks that are listed by the one of allocators (ARIN, RIPE, APNIC) as not being allocated or are reserved for special use. The article infers that this is what happens to lots of.mil
Black holed routes.
Sometimes, either intentionally or accidently, providers announce routes to blocks that they actually can't reach directly. This is usually a misconfiguration or done on purpose to null route blocks containing a host performing a DOS or some other network misdemeanour. This is usually a transient state.
I thought i was being taken to something about a 61" flat panel for $28,000 but the first link actually takes you to where you can purchase a 22" IBM flat panel for US$16,000. After finding that out, the write up starts to make sense...
For those who haven't experienced it, a lot of the au (except com.au) administration (registration, redelgations etc.) is done at a snails pace because it has to go through this one guy. If you thought NSI was bad...
I thought the graphics chip was still "in the making" and, hence, any images released are running on a not to spec XBox or something that is emulating the XBox (or they are completely fabricated anyway).
The "OSI Model" is just that, a model. (there is no such thing as "OSI protocols")
TCP/IP is an implementation of various components of that model.
OSI level Application (I will use telnet as an example) Presentation (eg. handled by telnet) Session (eg. handled by telnet) Transport (eg. TCP) Network (eg. IP) Data Link (eg. ethernet) Physical (eg. Cat5 UTP)
You need to remember that there is both mechanical copyright (for the performance) and publishing copyright (for the authoring of the music). So by my calculations a few of your examples would still be in breach of copyright where you have only considered mechanical copyright:
1.) Metallica's Enter Sandman from the black album (copyright owner: Elektra Records)
Mechanical: Elektra. Publishing: Metallica
2.) Metallica's Enter Sandman from a live concert which I recorded legally (Copyright owner: me)
Mechanical: you. Publishing: Metallica. ie you still need Metallica's permission to distribute it
3.) Metallica's Enter Sandman from a performance on the Grammy Awards (Copyright Owner: NARAS)
Mechanical: NARAS. Publishing: Metallica
4.) Apocalyptica's Enter Sandman from their "Metallica by Four Cellos" CD (Copyright owner: Apocalyptica)
You mistake what Nautilus is trying to achieve. They are embeding components so you don't have to deal with another app...
ie. if you want a web browser, you don't install a web browser and run it under Nautilus. you get only the components that Nautilus doesn't have by default that are required for web browsing.
it is a bit like having one of those screwdrivers with plugin heads, you only have to have one handle, instead of each one requiring its own.
Nautilus will step over the boundary into multilayering and bloatware when it embeds something that doesn't share any components with anything else...
Regarding your first point, are you saying that melanocytes in the eye produce pigment (resulting in tanning) due to sunlight? If so, it's untrue: people have the same eye colour with or without lots of sunlight; uvea do not tan.
I believe he was refering to melanocytes in general and not specifically the eye. Perhaps someone can enlighten us as to why the eye has melanocytes?
Regarding your second point, the Sunday Times was just reporting the study (in layman's terms) as it appeared in Epidemology. There's nothing wrong with this. The study presents EVIDENCE for a link. No more; no less. The Slashdot story, the Sunday Times, and the article in Epidemology made this clear.
I take issue with the wording you have used ("presents EVIDENCE for a link") as this implies that the two are somehow related other then chance. What he has demostrated is that there is a troubling correlation (which is not the same as a link) between those with high phone usage and the eye cancer. He had a hypothesis to link the two but I did not see any "evidence" to prove that the hypothesis was anything more then considered extrapolation of known facts. Until such time as someone can definatively point to a cause/effect relationship between phone use and cancer, statements like "The study presents EVIDENCE for a link. " only serve to mislead those who don't know any better.
Trust me, your email didn't do anything for the community, unless you count making it the object of ridicule by anyone who thinks that the rest of us are like you.
So you think everyone that reads that press release is going to notice the paragraph at the top that mentions that "Linux" != Linux ?!?
Just curious, but do you always fire off stupid, anal-retentive emails like that?
Not all the time, just when I feel like putting my 2 cents in. If your comment was so valid, put your name to it.
Slashdot Mirror
What does this mean for OpenMoko?
All frontline workers have Windows desktops (looks like 2000 Workstation) which they run a terminal app on to connect to what looks like a UNIX back end of some description.
Home taping is hard to use as a comparison because it doesn't have the network effects that benefit the distribution efficency of P2P file sharing.
Home taping was limited by: time taken to dub the album; usage of physical media; the number of people you knew or could get in contact with via conventional means (snail mail, phone, fax etc.etc.). So one person sharing an album had limited impact due to constraints on time, resources and reach.
A pervasive network such as the Internet allows someone to share with complete strangers and do so without any effort on their part. Although still limited to an extent by some resources (particulary bandwidth), sharing via P2P networks is vastly more efficient then home taping.
marty
There isn't much bio information on the website but he is in his second year of presenting Triple J's current affairs program and was previously a reporter for same. You can listen to the show online.
He has written some interesting articles for the Sydney Morning Herald in the past, including this one on the decline of Sydney and another on censorship of CDs.
cheers
marty
I think the grandparent's point was that a large company can bankroll this defence. Compare this to the recent Spamhaus case, where depsite winning the case Steve Linford & Co can't afford the legal bill.
marty
I think you'll find that the DOS is aimed generally at SCO's servers in the co-location facility, not at any particular service on those servers.
Other customers in the colo facility might not be the target of the attack but if the DOS is sufficiently large it will take out network elements upstream of SCO's equipment that these other companies connections also run through.
ie. some of center7's core or border routers are being affected.
if i could do a traceroute to either of them i'd show you what i mean, but it just keeps timing out.
Choice quote from the article:
"The problem here is consumers conveniently don't employ common sense," she said. "If it sounds too good to be true, it probably is."
marty
Lennon quote when asked "Is Ringo the best drummer in the world?":
"In the world? He's not even the best drummer in the band."
toodles
marty
They don't.
There are 200+ X-Window terminals. Only some users who need to run MS products connect to MS Terminal Servers using the *nix Citrix client.
marty
M$ is now helping AMD to compete, because AMD is not helping Linux.
Ummmm... didn't AMD contract SUSE to optimise Linux for the Hammer chip.
AMD Announces SuSE Linux Support for Next-Generation Processors
marty
Many of the distributor's fixes are ad hoc kludges that are designed to quickly making the thing *work*, ignoring elegance and maintainability...
I don't understand why a distro would bother shipping a kernel (or app for that matter) with a patch that was "ad hoc". It wouldn't exactly endear their customers to provide repeat business.
I think you will find that most distros test their patched kernels thoroughly before releasing them to the world. This would include not only checking that the patch fixes the problem, but that it compiles on all supported architectures and does not jeopradise future modifications to the same bit of code or adjacent or related pieces of code.
Why they don't submit all the patches to the kernel maintainer I don't know? Maybe the patch was submitted and was passed over or missed and then not resubmitted.
marty
A mirror of the letter and response is here.
A mirror of the full story is here.
HTH
marty
The letter and response are here.
The full story is here.
HTH
marty
Dark address space refers to globally unique IPs (ie. not private IPs as defined by the RFCs) that should be accessible from anywhere on the internet but are not due to one of many reasons. The two reasons I am most familiar with are:
/24 or longer masks). This means that unless there is an aggregrate route for that block that will get the packets there eventually, the IP is dark for people using that provider.
.mil
Route filtering.
To reduce the size of the routing table in the memory of their core routers, some providers throw away announcements of small blocks (say
Some providers also filter blocks that are listed by the one of allocators (ARIN, RIPE, APNIC) as not being allocated or are reserved for special use. The article infers that this is what happens to lots of
Black holed routes.
Sometimes, either intentionally or accidently, providers announce routes to blocks that they actually can't reach directly. This is usually a misconfiguration or done on purpose to null route blocks containing a host performing a DOS or some other network misdemeanour. This is usually a transient state.
hth
Marty
I thought i was being taken to something about a 61" flat panel for $28,000 but the first link actually takes you to where you can purchase a 22" IBM flat panel for US$16,000. After finding that out, the write up starts to make sense...
marty
It is likely that you have not been blackholed by MAPS's RBL but by MAPS's DUL. The distinction is important.
The RBL is for servers known to be relaying or originating spam and is generated by testing of the server in question.
The DUL is for IP ranges that ISPs submit as "dial-up". This encourages their dynamic IP customers to utilise their SMTP server.
For a better explanation of the difference compare these two descriptions RBL and DUL.
marty
No wonder redelegations take so long! :)
:)
For those who haven't experienced it, a lot of the au (except com.au) administration (registration, redelgations etc.) is done at a snails pace because it has to go through this one guy. If you thought NSI was bad...
later
marty
I thought the graphics chip was still "in the making" and, hence, any images released are running on a not to spec XBox or something that is emulating the XBox (or they are completely fabricated anyway).
marty
The "OSI Model" is just that, a model. (there is no such thing as "OSI protocols")
TCP/IP is an implementation of various components of that model.
OSI level
Application (I will use telnet as an example)
Presentation (eg. handled by telnet)
Session (eg. handled by telnet)
Transport (eg. TCP)
Network (eg. IP)
Data Link (eg. ethernet)
Physical (eg. Cat5 UTP)
Have a look at this page
hth
marty
You need to remember that there is both mechanical copyright (for the performance) and publishing copyright (for the authoring of the music). So by my calculations a few of your examples would still be in breach of copyright where you have only considered mechanical copyright:
1.) Metallica's Enter Sandman from the black album (copyright owner: Elektra Records)
Mechanical: Elektra. Publishing: Metallica
2.) Metallica's Enter Sandman from a live concert which I recorded legally (Copyright owner: me)
Mechanical: you. Publishing: Metallica. ie you still need Metallica's permission to distribute it
3.) Metallica's Enter Sandman from a performance on the Grammy Awards (Copyright Owner: NARAS)
Mechanical: NARAS. Publishing: Metallica
4.) Apocalyptica's Enter Sandman from their "Metallica by Four Cellos" CD (Copyright owner: Apocalyptica)
Mechanical: Universal. Publishing: Metallica
my 2 cents
marty
You mistake what Nautilus is trying to achieve. They are embeding components so you don't have to deal with another app...
ie. if you want a web browser, you don't install a web browser and run it under Nautilus. you get only the components that Nautilus doesn't have by default that are required for web browsing.
it is a bit like having one of those screwdrivers with plugin heads, you only have to have one handle, instead of each one requiring its own.
Nautilus will step over the boundary into multilayering and bloatware when it embeds something that doesn't share any components with anything else...
my 2 cents
marty
Regarding your first point, are you saying that melanocytes in the eye produce pigment (resulting in tanning) due to sunlight? If so, it's untrue: people have the same eye colour with or without lots of sunlight; uvea do not tan.
I believe he was refering to melanocytes in general and not specifically the eye. Perhaps someone can enlighten us as to why the eye has melanocytes?
Regarding your second point, the Sunday Times was just reporting the study (in layman's terms) as it appeared in Epidemology. There's nothing wrong with this. The study presents EVIDENCE for a link. No more; no less. The Slashdot story, the Sunday Times, and the article in Epidemology made this clear.
I take issue with the wording you have used ("presents EVIDENCE for a link") as this implies that the two are somehow related other then chance. What he has demostrated is that there is a troubling correlation (which is not the same as a link) between those with high phone usage and the eye cancer. He had a hypothesis to link the two but I did not see any "evidence" to prove that the hypothesis was anything more then considered extrapolation of known facts. Until such time as someone can definatively point to a cause/effect relationship between phone use and cancer, statements like "The study presents EVIDENCE for a link. " only serve to mislead those who don't know any better.
my 2 cents
marty
If the comment is valid, it can stand on its own without a basically untraceable pseudonym attached to it.
There is a reason they have "Anonymous Coward". It is for those who won't stand behind their opinion.
(the only reason it still exists is that it has the benefit of providing a hiding place for those revealing facts that they shouldn't).
As for posting my details, anyone with half a brain could figure out who I am. Send me an email with my address and I will take you seriously.
marty
If you had to choose short hand for "VA Linux", would you use:
a) Linux = 5 letters
b) VA = 2 letters
c) I'm illiterate.
Trust me, your email didn't do anything for the community, unless you count making it the object of ridicule by anyone who thinks that the rest of us are like you.
So you think everyone that reads that press release is going to notice the paragraph at the top that mentions that "Linux" != Linux ?!?
Just curious, but do you always fire off stupid, anal-retentive emails like that?
Not all the time, just when I feel like putting my 2 cents in. If your comment was so valid, put your name to it.
marty