Porno sites must be lightyears ahead of the game when it comes to online marketing. Afterall, everyone who visits one just LOVES the 5 gazillion popup (pun intended) windows that surface. Even banner ads on regular pages are causing a window to popup now.
Actually, the PPRO's problems were due to an overly small TLB cache. 16bit code hits the TLB cache pretty hard, and this was causing the PPRO to lag.
In the case of AMD vs Intel, they're both doing the same thing. AMD has been doing CISC->RISC instruction translation for about 5 years now. The Athlon is based partly on the Nexgen work, who they bought a few years ago. The real deal is that AMD has a more mature instruction translator than Intel, which should give them a leg up. Also, if the 64 really is 2 athlons stuck together, they might be doing some hairy SMP-on-chip kind of stuff that gets both execution units to work in tandem like SMP does. Intel's architecture is going to be slow because of the instruction width and memory access issues. The 32 bit instructions cannot fetch memory as fast as the 64 bit instructions because they are inherently limited to 32 bits wide of data access. This is the same issue as MMX, it can fetch in large quanities, that's why a simple read-write routine is twice as fast, it's twice as wide as a 32 bit read-write routine.
It's going to be a battle between 2 entirely different approaches, EPIC vs Tandem. The AMD approach has a lot of promise, however the Intel approach has a longer term benefit. Once the chipsets and memory catch up to their 3rd gen EPIC system, it'll be pretty fast. AMD may not be able to pull off a leapfrog unless they have a lot of tricky chipset work, and their 3rd gen 64 bit processor is scaled beyond the inherently bottlenecked Tandem/dual core setup.
# Linux DShield Client. V 0.0.2
#
# This script will extract relevant lines form the log file and
# send them to 'report@dshield.org'.
#
# It should run from cron regularly to look for new entries. See
# 'parameters' for more details.
#
# Parameters:
#
$userid="0"; # replace with your userid if you have one.
$email="none"; # replace with your e-mail address.
$to='report@dshield.org'; # send log to this address. Change for testing.
$local_log='/tmp/dshield.log'; # keep a local copy here for revie
$filter="input DENY"; # we only care for lines that contain this line.
$state="/var/tmp/dshield"; # file that is used to store length of log file.
$logfile="/var/log/messages"; # location of log file.
# setup a halfway safe/tmp file
srand(time);
$tmp="/tmp/dshield".$$.rand(1000);
$last_count=0;
#
# the 'state' file contains the length of the log file
# in lines the last time the script ran.
#
$length=`wc -l $logfile | sed 's/[^0-9]//g'`;
chomp $length;
#
# if the log file size 'shrank', we assume that the entire file
# is relevant. This will not catch log rotations where the
# log file grows rapidly.
#
$last_count=0 if ($length<$last_count);
$count=$length-$last_count;
#
# remove stale tmp files. This should never happen, as
# the temp file name is generated randomly
if (-s $tmp) {
system ("rm $tmp");
}
#
# this line 'does the work' of extracting relevant lines
#
# send the file. Only bother if there is something to
# report.
if ( -s $tmp) {
open (MAIL,"|/usr/sbin/sendmail -t -oi");
print MAIL "To: $to\n";
print MAIL "From: $email\n";
print MAIL "Subject: FORMAT LINUX USERID $userid\n\n";
print MAIL `cat $tmp`;
close MAIL;
if ($local) {
open (MAIL,"> $local");
print MAIL "To: $to\n";
print MAIL "From: $email\n";
print MAIL "Subject: FORMAT LINUX USERID $userid\n\n";
print MAIL `cat $tmp`;
close MAIL;
}
}
#
# cleanup the temp file and write a new state file
#
system ("rm $tmp");
system ("echo $length > $state");
When a big company buys you out, it usually has a stipulation in the purchase that the principals stay around. See, Justin is getting paid to do what he wants. What's more, he can only get fired to be released from the contract. He's probably got a 3 year term in the purchase, to stick around. There's only an upside for him.
--
The company I work for got bought, and they had the CEO stick around doing nothing because of the purchase contract.
They speak of the robot driving the car as a passenger. There are onboard computer systems in cadillacs today that can prevent you from breaking the car loose from the road. In fact, they do everything short of turning the wheel for you. If I was to develop a computer controlled race car, I would use telemetry, lateral acceleration sensors, and other sensors to keep the car on the edge of control. The race car driver's job today is to get the car, in it's static configuration, around the track as fast as possible. The computer controlled car has the ability to change damping rates, roll rates, and perform yaw control on the car, things that a human driver cannot. In fact, all the 'driver' has to do is point the car in the direction of the corners and hold the accelerator to the floor, the computer will do the rest.
Don't believe everything you read.
Whoa, hold on ther tex
on
Watch Camera
·
· Score: 1
A guy I work with just bought one of these, it's 120x120x16. This is NOT a high res device that is capable of doing a lot. It's just like those polaroid izone cameras or other silly toys.
I have the wingman commander and it definitely isn't a mouse. They claim it is, but mice don't have bounding limits and the commander does. It has feedback for games that support it, but you have to use it as a joystick in games like Ut or q3. It cost's $99 and is a complete waste of money. Other than it's cool feedback test buttons and dragging on the desktop, it sucks.
Just from peeking over the shoulder of my friend time after time, I can speculate that what he did was this:
When the plugin (it REALLY is a plugin, not an ad remover) is loaded, it finds out what the parent hwin of AIM is, goes through it's resource list and gets the hwin handle for the ad boxes. It whites them out initially. When you turn on winamp, it simply paints the vu meter/o-scope to the hijacked hwins. It also probably updates AIM's resource list with a couple of invisible hwins (I don't know if MS has a null hwin).
It's not as hard or as cynical as a lot of people have posed.
It seems to be that there is a cynical bias on this issue. I personally have a theory that is not based on a mis-appropriation of google results, but rather pure technical know how. Since Yahoo partnered with google, they need to have their information indexed. It makes sense that google has most of it indexed, but it's unlikely that every page yahoo has generated is in google's index. So, google needs to index every page they have. It only makes sense that google would have more accurate results by thoroughly indexing yahoo. The issue that people are having is that the yahoo index isn't sectioned off into it's own little cluster, but part of the larger index in google. It's simply the fact that google has a more complete index of the yahoo pages, not because yahoo is paying for search results.
4. Linux users are more keen to privacy issues than Windoze users and decided to play Unreal Tournament instead, because they didn't want they're software contacting id's keyserver to *ALLOW* them to play a game.
id lost my business because of that. I only play UT now. Bad move, and I was ready to go buy the q3a boxed tin at Software etc...
There are many advantages to having the HTTP server execute in the domain of the kernel. First, there is no overhead for multiple process instances; most people will use a statically compiled binary to achieve a slightly higher performance, at the expense of system memory. Also, the HTTP server can use the kernel disk and network buffers as it's own. This means that when you want a file from the server, it can use the buffer cache, which probably already holds the file (if it's recently used) and just send those buffers directly to the network; this is how the sendfile function works. The HTTP server can also take better advantage of scheduling intimacy. If you're in the kernel, you can lock-step the server with the scheduler, so no time is wasted. The latency for connection handling is greatly reduced because there is no need to wakeup a user space program, wait for a scheduling slot, and accept the connection; this can all be done in one fell swoop by the server, because it's inside the kernel. Also, taking advantage of multiple processors is easier to do inside the kernel, where you want a very tight control on what processor does what. The enables certain processes to be tasked with running the webserver, and this helps eliminate cache hits because the thread actually exists as one chunk of code, and doesn't get swapped out. This brings up another issue, anything inside the kernel is non-swapable, so there is no swap overhead, reducing latency and context switches. Most of the benefits of a kernel based server are realized from the tight integration (in an efficient way, not IE type of way) into the 'core' of the operating system. This also makes way for appliance based servers. Something like a proxy cache or appliance web server. Network appliance has an HTTP server protocol available for their filers, but it is far less featurful than what TUX sounds like, plus TUX comes with source code!
Transmeta was unique in that they actually RELEASED a product before announcing it. They actually put forth some physical product before asking for investors to kick down.
Good job, and I hope Linus has some principal equity (I'd be suprised if he didn't).
I'm the person who originally explored the security issues with Frontpage. My rantings are detailed (err, carved in stone unfortunately) on several security websites.
Incidentally, there is a rogue bit of code in the Visual interdev libs that ship with Frontpage 98 NT extensions. This code (as evidenced) allows backdooring of administrator access.
At no time were the Unix extensions vulnerable to this bit of code jocky arrogance.
I'd really like to see your response to this: For many years people have been taping (analog streaming medium) radio for the express purpose of playing it back later. This has been accepted as a perfectly fine behaviour as long as you did not 'rebroadcast' the tape. This was to protect the radio stations' intellectual property. When I taped radio programs, I listened to them for private use only. Occasionally I'd lend a copy to a friend and let them copy it.
Explain to me how downloading MP3's of songs I hear on the radio is any different than recording the radio with a tape deck (remember, the analog streaming medium) and playing it back later?
It's not.
It's the same argument you make about ripping your CD with the Rio software and playing it back on your Rio; space shifting your music.
So if I download Sugar Ray's 'Fly' and play it back on my computer, how is that any less legal than taping a really good broadcast of 'Fly' on my local radio station, and playing THAT back?
It's not. They're both lossy forms of audio playback and recording.
This weekend I bought 3 new CD's, at the total sum of $60 bucks, because I like 6 songs.
I PAID $10 a song to own a non-exlcusive, non-reproducable, license per a song. It really pisses me off that I HAVE to go to Sam Goody to buy Sugar Ray's 14:59, Offspring's Americana, and Incubus' debut album, because I owned the MP3's for a long time, and I listend to them.
Bottom line: I have 25GB of MP3's, and I listen to 4GB worth. Just because I have 21GB of stuff I don't listen to, doesn't mean I should pay for it (Wesley Willis is DEFINITELY not in my playlist, but it's hogging space).
I buy CD's of MP3's I like, for 3 reasons: I feel a moral obligation to own the plastic. I want to rip the 112Kbps crap at 160Kbps and replace the crap. I haven't finished building my car/home MP3 player (the 40x4 Matrix Orbital is on the way).
So get off your horse. There's a lot of shit MP3's out there. They are all lossy. Most are 128Kbps. Many are 112Kbps. Shitty quality MP3's are a fact of life. I buy the CD to rip at higher quality.
I won't pay for MP3's I have, but don't listen to. I don't listen to the wichy-wu stations, so why should I pay for their crap programming by listening to their commercials?
Pay-per-orgasm is broadcast into every home in my community. It's available, but I don't buy it, because I don't want to; it's crap. I pay for good channels like Speedvision (YEAH!).
Stick that in your sanctimonious pipe and smoke it.
I have been an opponent of the RBL for a while. There is absolutely no checks and balances to prevent personal grudges from taking a toll on businesses, etc. The company I work for was placed on the RBL by one of the board members, without any contact. The reason: He received an email he didn't want from a customer which had a website with us. Mind you they didn't use our mail system to send him this email, nor was it SPAM.
Subjective control of the Net is wrong, for the same reason that censorware is wrong.
The RBL is a heavy handed approach to solving problems. Rather than taking the approach ESR took with Netscape, they are extorting email providers into compliance. That's just wrong.
ORBS only serves to make an application level RBL. These approaches are entirely wrong, diplomatic approaches must be made to solve the problem, not heavy handed politics.
Go yo your local car audio shop and look at the dash mounted DVD LCD stereo players. Also, goto Circuit city and look at the MD video cameras. Color cell phones are just a coming attraction. Well, and OF COURSE the PS2 is going to be making an appearance at my house:)
The important thing that these developments are bringing out is the technology. Loki is developing a suite of porting tools for making Windoze games work under Linux. This means that A3D and D3D and other stuff will work under Linux without having to rewrite everthing every time.
With this business card sized media, you could put literally any data on the cdrom, up to 52MB (on the true business card sized ones).
Programs such as ssh, gpg, and other crypto sensitive stuff could be placed on here. To hide their contents, make a par-point presentation in staroffice and put that on there. That way, when you meet anyone, just give them one of these rediculously overpriced CDRs with your info on it, and they'll also get a copy of all the non-exportables.
Actually, the export business is getting easier now, but it doesn't hurt to put something important on them. Just think, if you were Kevin Mitnick and you wanted your data back from the feds, you could've just burned a stack of these things and mailed them to your friends. When you got out of jail, just call one of them up and have them send you your card back. With a stack of 50, the sheer volume would assure you access to your data.
Actually that brings up another idea for these, put copies of data you need to keep and mail them to people. Or how about a distributed collection of data, each person has to provide the business card to complete the library and access the data. You could make a high-tech easter egg hunt out of this.
Even better yet, you put the secret key to get at your fortune, spread across a bunch of these. You then mail them out to all your willed partiticpants. When you die, they ALL have to cooperate to get at your money!
How about putting a unique key on each one of these and having people use them as access cards, you could block out specific access cards and institute your own access policy.
This would be great for a website. You send each member a card that they have to use each time they access your website, as a password substitute. This would bypass user chosen passwords and provide the ultimate security for accessing a service. If one of the cards is compromised, cancel access for it.
To the non-net-centric public Amazon is not neccessarily a bad company, they just have their pocketbook on the brain. Companies will register patents to protect themselves from a semi-original idea being patented by a competitor. However Amazon has demonstrated that they only wish to crush their competitors the only way they can: infringement. Any really good company is going to win out with quality and not legal wrangling.
Unfortunately the legal wrangling will win more times than not. Decency has been lost in American companies. A lot of American companies see customers as dollar signs and will cut corners and compete at the worst level, all in search of the next nickel.
Microsoft is a prime example of companies that win not through a superior service or product, but trying to crush the competition using any number of underhanded means at their disposal.
Look at your favorite ISP that you love to hate, they provide crappy service, but because the barrage the customer with ads, the customer has no clue that it's relative shit.
Now those same crappy ISPs are trying to lock people into 3 year contracts. You get locked into a 3 year contract when you buy or lease a car too, draw your own analogy.
Amazon is just another company that is using their perceived upper hand to crush their competitor, it has nothing to do with providing better service to their customers. Besides, you don't use patent law for that, you use tradmark law for protecting the customer by preventing bastardization of the interface.
Amazon has just hit the mud-slinging stage of their timeline. I hope they have a good garden hose, because the shit's gonna get deep.
You are incorrect. Microsoft released a BETA version of Windows 3.1, it ran fine on DRDOS 6.0. When Microsoft released the gold version, it mysteriously stopped working. It turns out that they used their ability to call certain API quirks in DOS to prevent DRDOS users from running Windows 3.1. I called Digital Research and they sent me the 2 360k floppies for free, upgrading DRDOS to work with the released version of Windows 3.1.
This has absolutely NOTHING to do with Open Source. They are giving away pre-adorned HTML to people who want to use it. Open Source is Free Speech, not the RIGHT to Free Beer.
I understand Napster's reasons for not releasing the protocol information before (he didn't want freaky hacks and stuff). However, OTOH he is currently the target of a pretty serious suit, so his rights to run his server service may be impinged. I can only see one way to ensure that the cool idea stays around, that's for him to release the protocol and make it open. Ideally I'd like to see this server and client opensourced so that it can be improved upon.
His reasons for keeping the protocol closed seem to be pretty petty right now. With the threat of suit, it would benefit him to open it. The Napster concept is a really good one, it's a really useful way for data content to be shared in a fully distributed and peer-like manner.
The reality is that there isn't a whole lot to the Napster protocol that someone would want to purposefully disrupt. It's just a peer file sharing service, people really don't spend all their time trying to disrupt such a cool service. The Napster concept is an underground one, and most of the people who would care to DoS or crack such things are part of the underground mindset too; you don't mailbomb BugTraq if you're a person who uses it regularly.
Ps, Please moderate this up, I think it's an important comment:)
I did some poking around. The linuxopen.com domain they own is hosted off of a T1 with some company described as 'pacmicro'. If you sniff around www.linuxone.net, you'll find that it's an ADSL connection via pacbell. It's running a stock redhat 6.0/6.1 and probably has the vulnerable BIND installed on it (that's an open port BTW).
I would challenge someone to explore that situation a little more and report back their results.
That $4677 is probaby a new computer and ADSL and hosting costs.
She touched on the lightbulb, but it's obvious that she doesn't have the extreme technically in-depth knowledge to properly acknowledge the light bulb.
The premise of the lightbulb was to burn a conductor in a vacuum. The lack of an atmosphere prevents oxidation in bulbs, and the incineration.
The lightbulb is the father of modern computing. Take a lightbulb and a relay, cross them and you have a vacuum tube. The vacuum tube works very similar to a lightbulb. They both exist in a vacuum and generate heat. When a vacuum tube is excited, electrons pass through it like a transistor. However vacuum tubes are analog and have an infinitely variable throughput.
An interesting thing about vacuum tubes is that they emit RF radiation, radio. Properly controlled they can be used to broadcast radio. Even today, many radio stations still use a vacuum tube transmitter, called a 'klystron' (sp?) I believe.
You wouldn't have instant heat microwave popcorn without the vacuum tube either. In microwaves, there is a special vacuum tube called the 'magnatron' which emits microwave energy. This is routed via metal ducting and used to nuke your food.
The CRT is a direct decendant of the vacuum tube. It's basically a vacuum tube turned on end, with the phospor end being the collector and 1 or more guns being the emitter.
We wouldn't have radio, television, microwave popcorn, or computers if the lightbulb hadn't been invented.
Slashdot Mirror
Porno sites must be lightyears ahead of the game when it comes to online marketing. Afterall, everyone who visits one just LOVES the 5 gazillion popup (pun intended) windows that surface. Even banner ads on regular pages are causing a window to popup now.
Actually, the PPRO's problems were due to an overly small TLB cache. 16bit code hits the TLB cache pretty hard, and this was causing the PPRO to lag.
In the case of AMD vs Intel, they're both doing the same thing. AMD has been doing CISC->RISC instruction translation for about 5 years now. The Athlon is based partly on the Nexgen work, who they bought a few years ago. The real deal is that AMD has a more mature instruction translator than Intel, which should give them a leg up. Also, if the 64 really is 2 athlons stuck together, they might be doing some hairy SMP-on-chip kind of stuff that gets both execution units to work in tandem like SMP does. Intel's architecture is going to be slow because of the instruction width and memory access issues. The 32 bit instructions cannot fetch memory as fast as the 64 bit instructions because they are inherently limited to 32 bits wide of data access. This is the same issue as MMX, it can fetch in large quanities, that's why a simple read-write routine is twice as fast, it's twice as wide as a 32 bit read-write routine.
It's going to be a battle between 2 entirely different approaches, EPIC vs Tandem. The AMD approach has a lot of promise, however the Intel approach has a longer term benefit. Once the chipsets and memory catch up to their 3rd gen EPIC system, it'll be pretty fast. AMD may not be able to pull off a leapfrog unless they have a lot of tricky chipset work, and their 3rd gen 64 bit processor is scaled beyond the inherently bottlenecked Tandem/dual core setup.
#!/usr/bin/perl
/tmp file
/usr/sbin/sendmail -t -oi");
# Linux DShield Client. V 0.0.2
#
# This script will extract relevant lines form the log file and
# send them to 'report@dshield.org'.
#
# It should run from cron regularly to look for new entries. See
# 'parameters' for more details.
#
# Parameters:
#
$userid="0"; # replace with your userid if you have one.
$email="none"; # replace with your e-mail address.
$to='report@dshield.org'; # send log to this address. Change for testing.
$local_log='/tmp/dshield.log'; # keep a local copy here for revie
$filter="input DENY"; # we only care for lines that contain this line.
$state="/var/tmp/dshield"; # file that is used to store length of log file.
$logfile="/var/log/messages"; # location of log file.
# setup a halfway safe
srand(time);
$tmp="/tmp/dshield".$$.rand(1000);
$last_count=0;
#
# the 'state' file contains the length of the log file
# in lines the last time the script ran.
#
if ( -e $state ) {
$last_count=`cat $state`;
chmod $last_count;
}
#
# get the current length of the logfile
#
$length=`wc -l $logfile | sed 's/[^0-9]//g'`;
chomp $length;
#
# if the log file size 'shrank', we assume that the entire file
# is relevant. This will not catch log rotations where the
# log file grows rapidly.
#
$last_count=0 if ($length<$last_count);
$count=$length-$last_count;
#
# remove stale tmp files. This should never happen, as
# the temp file name is generated randomly
if (-s $tmp) {
system ("rm $tmp");
}
#
# this line 'does the work' of extracting relevant lines
#
system("tail -$count $logfile | grep '$filter' > $tmp");
# send the file. Only bother if there is something to
# report.
if ( -s $tmp) {
open (MAIL,"|
print MAIL "To: $to\n";
print MAIL "From: $email\n";
print MAIL "Subject: FORMAT LINUX USERID $userid\n\n";
print MAIL `cat $tmp`;
close MAIL;
if ($local) {
open (MAIL,"> $local");
print MAIL "To: $to\n";
print MAIL "From: $email\n";
print MAIL "Subject: FORMAT LINUX USERID $userid\n\n";
print MAIL `cat $tmp`;
close MAIL;
}
}
#
# cleanup the temp file and write a new state file
#
system ("rm $tmp");
system ("echo $length > $state");
When a big company buys you out, it usually has a stipulation in the purchase that the principals stay around. See, Justin is getting paid to do what he wants. What's more, he can only get fired to be released from the contract. He's probably got a 3 year term in the purchase, to stick around. There's only an upside for him.
--
The company I work for got bought, and they had the CEO stick around doing nothing because of the purchase contract.
They speak of the robot driving the car as a passenger. There are onboard computer systems in cadillacs today that can prevent you from breaking the car loose from the road. In fact, they do everything short of turning the wheel for you. If I was to develop a computer controlled race car, I would use telemetry, lateral acceleration sensors, and other sensors to keep the car on the edge of control. The race car driver's job today is to get the car, in it's static configuration, around the track as fast as possible. The computer controlled car has the ability to change damping rates, roll rates, and perform yaw control on the car, things that a human driver cannot. In fact, all the 'driver' has to do is point the car in the direction of the corners and hold the accelerator to the floor, the computer will do the rest.
Don't believe everything you read.
A guy I work with just bought one of these, it's 120x120x16. This is NOT a high res device that is capable of doing a lot. It's just like those polaroid izone cameras or other silly toys.
I have the wingman commander and it definitely isn't a mouse. They claim it is, but mice don't have bounding limits and the commander does. It has feedback for games that support it, but you have to use it as a joystick in games like Ut or q3. It cost's $99 and is a complete waste of money. Other than it's cool feedback test buttons and dragging on the desktop, it sucks.
My 2 cents.
Just from peeking over the shoulder of my friend time after time, I can speculate that what he did was this:
When the plugin (it REALLY is a plugin, not an ad remover) is loaded, it finds out what the parent hwin of AIM is, goes through it's resource list and gets the hwin handle for the ad boxes. It whites them out initially. When you turn on winamp, it simply paints the vu meter/o-scope to the hijacked hwins. It also probably updates AIM's resource list with a couple of invisible hwins (I don't know if MS has a null hwin).
It's not as hard or as cynical as a lot of people have posed.
'Bogus
It seems to be that there is a cynical bias on this issue. I personally have a theory that is not based on a mis-appropriation of google results, but rather pure technical know how. Since Yahoo partnered with google, they need to have their information indexed. It makes sense that google has most of it indexed, but it's unlikely that every page yahoo has generated is in google's index. So, google needs to index every page they have. It only makes sense that google would have more accurate results by thoroughly indexing yahoo. The issue that people are having is that the yahoo index isn't sectioned off into it's own little cluster, but part of the larger index in google. It's simply the fact that google has a more complete index of the yahoo pages, not because yahoo is paying for search results.
4. Linux users are more keen to privacy issues than Windoze users and decided to play Unreal Tournament instead, because they didn't want they're software contacting id's keyserver to *ALLOW* them to play a game.
id lost my business because of that. I only play UT now. Bad move, and I was ready to go buy the q3a boxed tin at Software etc...
Now we'll have moody computers: "I'm sorry, I just don't feel like playing Unreal Tournament today, sorry!"
Grr.
There are many advantages to having the HTTP server execute in the domain of the kernel. First, there is no overhead for multiple process instances; most people will use a statically compiled binary to achieve a slightly higher performance, at the expense of system memory. Also, the HTTP server can use the kernel disk and network buffers as it's own. This means that when you want a file from the server, it can use the buffer cache, which probably already holds the file (if it's recently used) and just send those buffers directly to the network; this is how the sendfile function works. The HTTP server can also take better advantage of scheduling intimacy. If you're in the kernel, you can lock-step the server with the scheduler, so no time is wasted. The latency for connection handling is greatly reduced because there is no need to wakeup a user space program, wait for a scheduling slot, and accept the connection; this can all be done in one fell swoop by the server, because it's inside the kernel. Also, taking advantage of multiple processors is easier to do inside the kernel, where you want a very tight control on what processor does what. The enables certain processes to be tasked with running the webserver, and this helps eliminate cache hits because the thread actually exists as one chunk of code, and doesn't get swapped out. This brings up another issue, anything inside the kernel is non-swapable, so there is no swap overhead, reducing latency and context switches. Most of the benefits of a kernel based server are realized from the tight integration (in an efficient way, not IE type of way) into the 'core' of the operating system. This also makes way for appliance based servers. Something like a proxy cache or appliance web server. Network appliance has an HTTP server protocol available for their filers, but it is far less featurful than what TUX sounds like, plus TUX comes with source code!
Transmeta was unique in that they actually RELEASED a product before announcing it. They actually put forth some physical product before asking for investors to kick down.
Good job, and I hope Linus has some principal equity (I'd be suprised if he didn't).
I'm the person who originally explored the security issues with Frontpage. My rantings are detailed (err, carved in stone unfortunately) on several security websites.
Incidentally, there is a rogue bit of code in the Visual interdev libs that ship with Frontpage 98 NT extensions. This code (as evidenced) allows backdooring of administrator access.
At no time were the Unix extensions vulnerable to this bit of code jocky arrogance.
Later...
I'd really like to see your response to this: For many years people have been taping (analog streaming medium) radio for the express purpose of playing it back later. This has been accepted as a perfectly fine behaviour as long as you did not 'rebroadcast' the tape. This was to protect the radio stations' intellectual property. When I taped radio programs, I listened to them for private use only. Occasionally I'd lend a copy to a friend and let them copy it.
Explain to me how downloading MP3's of songs I hear on the radio is any different than recording the radio with a tape deck (remember, the analog streaming medium) and playing it back later?
It's not.
It's the same argument you make about ripping your CD with the Rio software and playing it back on your Rio; space shifting your music.
So if I download Sugar Ray's 'Fly' and play it back on my computer, how is that any less legal than taping a really good broadcast of 'Fly' on my local radio station, and playing THAT back?
It's not. They're both lossy forms of audio playback and recording.
This weekend I bought 3 new CD's, at the total sum of $60 bucks, because I like 6 songs.
I PAID $10 a song to own a non-exlcusive, non-reproducable, license per a song. It really pisses me off that I HAVE to go to Sam Goody to buy Sugar Ray's 14:59, Offspring's Americana, and Incubus' debut album, because I owned the MP3's for a long time, and I listend to them.
Bottom line: I have 25GB of MP3's, and I listen to 4GB worth. Just because I have 21GB of stuff I don't listen to, doesn't mean I should pay for it (Wesley Willis is DEFINITELY not in my playlist, but it's hogging space).
I buy CD's of MP3's I like, for 3 reasons: I feel a moral obligation to own the plastic. I want to rip the 112Kbps crap at 160Kbps and replace the crap. I haven't finished building my car/home MP3 player (the 40x4 Matrix Orbital is on the way).
So get off your horse. There's a lot of shit MP3's out there. They are all lossy. Most are 128Kbps. Many are 112Kbps. Shitty quality MP3's are a fact of life. I buy the CD to rip at higher quality.
I won't pay for MP3's I have, but don't listen to. I don't listen to the wichy-wu stations, so why should I pay for their crap programming by listening to their commercials?
Pay-per-orgasm is broadcast into every home in my community. It's available, but I don't buy it, because I don't want to; it's crap. I pay for good channels like Speedvision (YEAH!).
Stick that in your sanctimonious pipe and smoke it.
I have been an opponent of the RBL for a while. There is absolutely no checks and balances to prevent personal grudges from taking a toll on businesses, etc. The company I work for was placed on the RBL by one of the board members, without any contact. The reason: He received an email he didn't want from a customer which had a website with us. Mind you they didn't use our mail system to send him this email, nor was it SPAM.
Subjective control of the Net is wrong, for the same reason that censorware is wrong.
The RBL is a heavy handed approach to solving problems. Rather than taking the approach ESR took with Netscape, they are extorting email providers into compliance. That's just wrong.
ORBS only serves to make an application level RBL. These approaches are entirely wrong, diplomatic approaches must be made to solve the problem, not heavy handed politics.
Go yo your local car audio shop and look at the dash mounted DVD LCD stereo players. Also, goto Circuit city and look at the MD video cameras. Color cell phones are just a coming attraction. Well, and OF COURSE the PS2 is going to be making an appearance at my house :)
The important thing that these developments are bringing out is the technology. Loki is developing a suite of porting tools for making Windoze games work under Linux. This means that A3D and D3D and other stuff will work under Linux without having to rewrite everthing every time.
Now *that's* the important part.
With this business card sized media, you could put literally any data on the cdrom, up to 52MB (on the true business card sized ones).
Programs such as ssh, gpg, and other crypto sensitive stuff could be placed on here. To hide their contents, make a par-point presentation in staroffice and put that on there. That way, when you meet anyone, just give them one of these rediculously overpriced CDRs with your info on it, and they'll also get a copy of all the non-exportables.
Actually, the export business is getting easier now, but it doesn't hurt to put something important on them. Just think, if you were Kevin Mitnick and you wanted your data back from the feds, you could've just burned a stack of these things and mailed them to your friends. When you got out of jail, just call one of them up and have them send you your card back. With a stack of 50, the sheer volume would assure you access to your data.
Actually that brings up another idea for these, put copies of data you need to keep and mail them to people. Or how about a distributed collection of data, each person has to provide the business card to complete the library and access the data. You could make a high-tech easter egg hunt out of this.
Even better yet, you put the secret key to get at your fortune, spread across a bunch of these. You then mail them out to all your willed partiticpants. When you die, they ALL have to cooperate to get at your money!
How about putting a unique key on each one of these and having people use them as access cards, you could block out specific access cards and institute your own access policy.
This would be great for a website. You send each member a card that they have to use each time they access your website, as a password substitute. This would bypass user chosen passwords and provide the ultimate security for accessing a service. If one of the cards is compromised, cancel access for it.
Make up your own use for these!
To the non-net-centric public Amazon is not neccessarily a bad company, they just have their pocketbook on the brain. Companies will register patents to protect themselves from a semi-original idea being patented by a competitor. However Amazon has demonstrated that they only wish to crush their competitors the only way they can: infringement. Any really good company is going to win out with quality and not legal wrangling.
Unfortunately the legal wrangling will win more times than not. Decency has been lost in American companies. A lot of American companies see customers as dollar signs and will cut corners and compete at the worst level, all in search of the next nickel.
Microsoft is a prime example of companies that win not through a superior service or product, but trying to crush the competition using any number of underhanded means at their disposal.
Look at your favorite ISP that you love to hate, they provide crappy service, but because the barrage the customer with ads, the customer has no clue that it's relative shit.
Now those same crappy ISPs are trying to lock people into 3 year contracts. You get locked into a 3 year contract when you buy or lease a car too, draw your own analogy.
Amazon is just another company that is using their perceived upper hand to crush their competitor, it has nothing to do with providing better service to their customers. Besides, you don't use patent law for that, you use tradmark law for protecting the customer by preventing bastardization of the interface.
Amazon has just hit the mud-slinging stage of their timeline. I hope they have a good garden hose, because the shit's gonna get deep.
You are incorrect. Microsoft released a BETA version of Windows 3.1, it ran fine on DRDOS 6.0. When Microsoft released the gold version, it mysteriously stopped working. It turns out that they used their ability to call certain API quirks in DOS to prevent DRDOS users from running Windows 3.1. I called Digital Research and they sent me the 2 360k floppies for free, upgrading DRDOS to work with the released version of Windows 3.1.
This has absolutely NOTHING to do with Open Source. They are giving away pre-adorned HTML to people who want to use it. Open Source is Free Speech, not the RIGHT to Free Beer.
Come on now!
I understand Napster's reasons for not releasing the protocol information before (he didn't want freaky hacks and stuff). However, OTOH he is currently the target of a pretty serious suit, so his rights to run his server service may be impinged. I can only see one way to ensure that the cool idea stays around, that's for him to release the protocol and make it open. Ideally I'd like to see this server and client opensourced so that it can be improved upon.
:)
His reasons for keeping the protocol closed seem to be pretty petty right now. With the threat of suit, it would benefit him to open it. The Napster concept is a really good one, it's a really useful way for data content to be shared in a fully distributed and peer-like manner.
The reality is that there isn't a whole lot to the Napster protocol that someone would want to purposefully disrupt. It's just a peer file sharing service, people really don't spend all their time trying to disrupt such a cool service. The Napster concept is an underground one, and most of the people who would care to DoS or crack such things are part of the underground mindset too; you don't mailbomb BugTraq if you're a person who uses it regularly.
Ps, Please moderate this up, I think it's an important comment
I did some poking around. The linuxopen.com domain they own is hosted off of a T1 with some company described as 'pacmicro'. If you sniff around www.linuxone.net, you'll find that it's an ADSL connection via pacbell. It's running a stock redhat 6.0/6.1 and probably has the vulnerable BIND installed on it (that's an open port BTW).
I would challenge someone to explore that situation a little more and report back their results.
That $4677 is probaby a new computer and ADSL and hosting costs.
She touched on the lightbulb, but it's obvious that she doesn't have the extreme technically in-depth knowledge to properly acknowledge the light bulb.
The premise of the lightbulb was to burn a conductor in a vacuum. The lack of an atmosphere prevents oxidation in bulbs, and the incineration.
The lightbulb is the father of modern computing. Take a lightbulb and a relay, cross them and you have a vacuum tube. The vacuum tube works very similar to a lightbulb. They both exist in a vacuum and generate heat. When a vacuum tube is excited, electrons pass through it like a transistor. However vacuum tubes are analog and have an infinitely variable throughput.
An interesting thing about vacuum tubes is that they emit RF radiation, radio. Properly controlled they can be used to broadcast radio. Even today, many radio stations still use a vacuum tube transmitter, called a 'klystron' (sp?) I believe.
You wouldn't have instant heat microwave popcorn without the vacuum tube either. In microwaves, there is a special vacuum tube called the 'magnatron' which emits microwave energy. This is routed via metal ducting and used to nuke your food.
The CRT is a direct decendant of the vacuum tube. It's basically a vacuum tube turned on end, with the phospor end being the collector and 1 or more guns being the emitter.
We wouldn't have radio, television, microwave popcorn, or computers if the lightbulb hadn't been invented.