the "tile mode" of various elder consoles and current handheld gaming systems. Where the ability to program the character glyphs is part of the terminal protocol. If this were standardized on top of an existing console standard it'd pretty damn cool (best of both worlds). While an IBM PC BIOS is not capable of it, real framebuffers are easy to come by and could emulated it. And maybe you can design the protocol to gracefully degrade (graphical tiles will display garbage or have wrong colors, but at least the text parts can still be displayed).
You save memory on the side hosting the application (but not necessarily on the display, if it needs a seperate framebuffer).
Consider that for a second. In a less open environment you'd be screwed.
Like me with the fucking Monster Sound MX440 which absolutely DOES NOT WORK in Win2k+ on an SMP box (and it crashes lots in UP). Goddamn Diamond had to get bought by Rio and then dropped just as soon as I bought that stupid goddmamn card that only works in 98.
I wrestled with that through many card inserts and removals, wrong-localed Taiwanese OEM driver installs, and a few OS rebuilds. I'd say you had an easier time.
So retarded. But GUEEESSSSS what? Works fine in linux.
is a USB-audio device. Works great, standardized, and you can move the DAC away from your computer and power cords to prevent undue noise. Plus it usually means easily accessible headphone jack.
the intel8x0 driver "just works" every time I use it. (I assume he has one of those chipsets: just about anything labeled Intel I've tried has worked with it, even the Nforce shit). So what's the deal? Did he care to look up his audio codec to make sure what he was doing was sane? Did he try Redhat or Mandrake, those "mainstream" distros? No...
Even if the autodetection tools on those distros sucked, someone needs to show this guy "modprobe" and "lsmod". ALSA was a step in the right direction (he probably should have ran "chkconfig --add alsasound" to make sure it was running at boot and not just installed... he should read the things labeled README)
My god the center of mass is gut-wrenchingly high on that piece of shit. There are plenty of other reasons to NOT get a Hummer. If you want a Hummer, get the real thing (AM General HMMWV, diesel), not the sluggish H2 (based on a Suburban).
I've got images of the Windows 95B CD in my home directory. I don't see that going anywhere anytime soon, and I'm not even trying for preservation.
Listen, you can by an SDAT tape drive that can read DAT tapes that were invented 15 years ago, and consolidate 10 of them into one new cartridge. And if you want to be safe, you make a copy and send that to a different site. And in 10 years there'll be a new generational standard that's backwards compatible, so you'll do another transfer then. Hell, you should be making multigenerational copies every few years and checking checksums between generations of media to make sure you're not propogating errors.
And why will this be possible? Because companies NEED THIS. They need to keep records for ages for various purposes. So the situation you detail will never happen if the custodians of the digital archive are just SLIGHTLY aware of the marketplace. Better than just leaving them to rot, eh?
Not to sound like a greenie...
on
A New Ice Age?
·
· Score: 1
but I would have thought that we would LIKE to be an ever greater net absorber of CO2. Anything that we could use to justify lowering duties in other countries in exchange for such credits. And to reduce the overall CO2 in the environment. (For anyone who has doubts that CO2 is a greenhouse gas and doubts whether it can, in the long run, contribute to climatic change, please direct your eyes towards Venus on a clear morning. Can you see it? That's CO2.)
Your web browser sends ALL the cookies that the webserver ever left.
Note the singular 'the'. Which means the same webserver that we've contacted. Such that aol.com gets all the unexpired aol.com cookies that IT LEFT, but not other ones.
The less benign cookies are those that belong to domains like doubleclick which many sites subscribe; those are the ones you should be aware of.
r00tkits are the linux equivalent of spyware/trojans. They are very small utilities, of which the most successful hook themselves into the running kernel using module loading, then intercept your system calls. They do things like hide files that names match certain patterns when you open directories or search the output of ps for program names.
Then the r00tkit launches backdoor programs that have names that match the hiding string. So as long as you don't notice the drain on resources (CPU, network) while the kit is being used, you may never know you were compromised. The machine can then be used remotely for any purpose.
Of course, the more sophisticated here have many countermeasures and tricks to find these inconsistencies. Tripwire is a commonly cited one.
At it's simplest a cookie is a just a mapping from a string to a value that your computer stores on the behalf of some webserver. It looks like this:
slashdot.org / 31 Apr 2004 user 621112::jrLk8rfhJlszg7DMS6cI83
Your webbrowser will provide that information to the server (slashdot.org) at a later time (before the expiration, 31 Apr in this case). In this way the server can "remember" who you are by storing whatever it would have otherwise forgotten as that cookie which is saved to your hard drive. In this case it's remembering that "user" equals 621112...blah blah blah. When slashdot sees me trying to load the front page, it gets that cookie, which it looks up and figures out maps to "Ayanami Rei" and shows me my Slashdot homepage as opposed to the generic one.
Here's the thing. Your web browser justs sends ALL the cookies that the webserver ever left everytime you fetch a URL from that server since it can't tell which one it might want... the server ignores the ones it's not intereseted in.
So whenever you see an ad banner coming from some site like doubleclick.net, you can be sure that it's setting and checking a doubleclick cookie. The thing that makes it dangerous is that it can also tell (from Referer headers also graciously provided by your browser) what page that ad was referenced from (and hence what page you were browsing!) So doubleclick.net can track you between sites that use their ad banners.
Etc. Some websites concerned about tracking traffic insert invisible images that fetch and set cookies from centralized webservers to get statistics. While cookies only get and set themselves to servers with the same name, that doesn't mean a bunch of websites can't subscribe to one tracking service. (And they often do...)
So while I wouldn't call it spyware, you need to be aware of the potential privacy implications and you need to carefully inspect your cookie files or cookie permissions. Mozilla lets you block access to cookies by originating sites, so you can control who can and can't use your cookie storage.
is that a sufficiently small segment of their users did NOT figure out how to remove the Earthlink spyware. This surprised no one until some genius figured out they could turn it into a sort of expose for good press.
Actually what they did was a good thing. They bundled the source to GPL things they used (uClinux, some other stuff), and they omitted things that were propietary (they didn't even bundle them in the zip).
I'm confused, what other GPL software did they use that isn't included there?
If they want to use GPL code, it's quite simple...
Do what they did in remedy UPFRONT, at the BEGINNING.
Then, OH LOOK, no court battle. OH LOOK, how nice, that company's distributing a binary version of project code AND PROVIDING ACCESS TO THE SOURCE AS THEY SHOULD HAVE.
AMAZING!
Is that so difficult to comprehend? Sure they can use BSD source too. In fact they can use WHATEVER THE HELL THEY WANT. They just have to read a FEW SIMPLE INSTRUCTIONS AND ADD A GODDAMN LINK TO THE DRIVER PAGE.
why should I pick one over the other? Let me add that I don't care whether some commercial entity has an easier time making money with my software or not. In fact I'd rather get money if I could.
Slashdot Mirror
the "tile mode" of various elder consoles and current handheld gaming systems. Where the ability to program the character glyphs is part of the terminal protocol. If this were standardized on top of an existing console standard it'd pretty damn cool (best of both worlds). While an IBM PC BIOS is not capable of it, real framebuffers are easy to come by and could emulated it. And maybe you can design the protocol to gracefully degrade (graphical tiles will display garbage or have wrong colors, but at least the text parts can still be displayed).
You save memory on the side hosting the application (but not necessarily on the display, if it needs a seperate framebuffer).
but at least it was POSSIBLE.
Consider that for a second. In a less open environment you'd be screwed.
Like me with the fucking Monster Sound MX440 which absolutely DOES NOT WORK in Win2k+ on an SMP box (and it crashes lots in UP). Goddamn Diamond had to get bought by Rio and then dropped just as soon as I bought that stupid goddmamn card that only works in 98.
I wrestled with that through many card inserts and removals, wrong-localed Taiwanese OEM driver installs, and a few OS rebuilds. I'd say you had an easier time.
So retarded. But GUEEESSSSS what? Works fine in linux.
is a USB-audio device. Works great, standardized, and you can move the DAC away from your computer and power cords to prevent undue noise. Plus it usually means easily accessible headphone jack.
the intel8x0 driver "just works" every time I use it. (I assume he has one of those chipsets: just about anything labeled Intel I've tried has worked with it, even the Nforce shit).
So what's the deal? Did he care to look up his audio codec to make sure what he was doing was sane? Did he try Redhat or Mandrake, those "mainstream" distros? No...
Even if the autodetection tools on those distros sucked, someone needs to show this guy "modprobe" and "lsmod". ALSA was a step in the right direction (he probably should have ran "chkconfig --add alsasound" to make sure it was running at boot and not just installed... he should read the things labeled README)
I'm there.
(I figured that was going to happen 9 months ago when the 8-way systems weren't coming out... just waiting for the inevitable)
My god the center of mass is gut-wrenchingly high on that piece of shit. There are plenty of other reasons to NOT get a Hummer. If you want a Hummer, get the real thing (AM General HMMWV, diesel), not the sluggish H2 (based on a Suburban).
contains the kernel-blahblah.src.rpm. The vanilla sources are in there and end up in /usr/src/redhat/SOURCES after installing.
$ cat /etc/redhat-release
Red Hat Linux release 9 (Shrike)
$
That was the sound of your nuts.
Now you can mod me flamebait.
It's too bad it didn't pan out that well.
STFU
- ruri
I've got images of the Windows 95B CD in my home directory. I don't see that going anywhere anytime soon, and I'm not even trying for preservation.
Listen, you can by an SDAT tape drive that can read DAT tapes that were invented 15 years ago, and consolidate 10 of them into one new cartridge. And if you want to be safe, you make a copy and send that to a different site. And in 10 years there'll be a new generational standard that's backwards compatible, so you'll do another transfer then. Hell, you should be making multigenerational copies every few years and checking checksums between generations of media to make sure you're not propogating errors.
And why will this be possible? Because companies NEED THIS. They need to keep records for ages for various purposes. So the situation you detail will never happen if the custodians of the digital archive are just SLIGHTLY aware of the marketplace. Better than just leaving them to rot, eh?
but I would have thought that we would LIKE to be an ever greater net absorber of CO2. Anything that we could use to justify lowering duties in other countries in exchange for such credits. And to reduce the overall CO2 in the environment.
(For anyone who has doubts that CO2 is a greenhouse gas and doubts whether it can, in the long run, contribute to climatic change, please direct your eyes towards Venus on a clear morning. Can you see it? That's CO2.)
is posted on a weekday next week just before lunch hour eastern time.
Your web browser sends ALL the cookies that the webserver ever left.
Note the singular 'the'. Which means the same webserver that we've contacted. Such that aol.com gets all the unexpired aol.com cookies that IT LEFT, but not other ones.
The less benign cookies are those that belong to domains like doubleclick which many sites subscribe; those are the ones you should be aware of.
I randomly swapped and modified a few letters. Please, by all means, try using it.
I wanted an example that would look familiar to a curious user who examined her own cookie file after having visited slashdot.
r00tkits are the linux equivalent of spyware/trojans. They are very small utilities, of which the most successful hook themselves into the running kernel using module loading, then intercept your system calls. They do things like hide files that names match certain patterns when you open directories or search the output of ps for program names.
Then the r00tkit launches backdoor programs that have names that match the hiding string. So as long as you don't notice the drain on resources (CPU, network) while the kit is being used, you may never know you were compromised. The machine can then be used remotely for any purpose.
Of course, the more sophisticated here have many countermeasures and tricks to find these inconsistencies. Tripwire is a commonly cited one.
At it's simplest a cookie is a just a mapping from a string to a value that your computer stores on the behalf of some webserver. It looks like this:
slashdot.org / 31 Apr 2004 user 621112::jrLk8rfhJlszg7DMS6cI83
Your webbrowser will provide that information to the server (slashdot.org) at a later time (before the expiration, 31 Apr in this case). In this way the server can "remember" who you are by storing whatever it would have otherwise forgotten as that cookie which is saved to your hard drive. In this case it's remembering that "user" equals 621112...blah blah blah. When slashdot sees me trying to load the front page, it gets that cookie, which it looks up and figures out maps to "Ayanami Rei" and shows me my Slashdot homepage as opposed to the generic one.
Here's the thing. Your web browser justs sends ALL the cookies that the webserver ever left everytime you fetch a URL from that server since it can't tell which one it might want... the server ignores the ones it's not intereseted in.
So whenever you see an ad banner coming from some site like doubleclick.net, you can be sure that it's setting and checking a doubleclick cookie. The thing that makes it dangerous is that it can also tell (from Referer headers also graciously provided by your browser) what page that ad was referenced from (and hence what page you were browsing!) So doubleclick.net can track you between sites that use their ad banners.
Etc. Some websites concerned about tracking traffic insert invisible images that fetch and set cookies from centralized webservers to get statistics. While cookies only get and set themselves to servers with the same name, that doesn't mean a bunch of websites can't subscribe to one tracking service. (And they often do...)
So while I wouldn't call it spyware, you need to be aware of the potential privacy implications and you need to carefully inspect your cookie files or cookie permissions. Mozilla lets you block access to cookies by originating sites, so you can control who can and can't use your cookie storage.
is that a sufficiently small segment of their users did NOT figure out how to remove the Earthlink spyware. This surprised no one until some genius figured out they could turn it into a sort of expose for good press.
heh.
Citrix or Unix (whatever variety), then use XTerminal thin clients or Citrix thin clients.
Duhhh! Welcome to the 1980s.
That's the difference.
Actually what they did was a good thing. They bundled the source to GPL things they used (uClinux, some other stuff), and they omitted things that were propietary (they didn't even bundle them in the zip).
I'm confused, what other GPL software did they use that isn't included there?
If they want to use GPL code, it's quite simple...
Do what they did in remedy UPFRONT, at the BEGINNING.
Then, OH LOOK, no court battle. OH LOOK, how nice, that company's distributing a binary version of project code AND PROVIDING ACCESS TO THE SOURCE AS THEY SHOULD HAVE.
AMAZING!
Is that so difficult to comprehend? Sure they can use BSD source too. In fact they can use WHATEVER THE HELL THEY WANT. They just have to read a FEW SIMPLE INSTRUCTIONS AND ADD A GODDAMN LINK TO THE DRIVER PAGE.
why should I pick one over the other? Let me add that I don't care whether some commercial entity has an easier time making money with my software or not. In fact I'd rather get money if I could.
Thanks.