does anyone else find it odd that such articles (i'm talking about nature.com's article, not the/. article) rarely include actual links to the websites they're referring to? I swear, this is like a conspiracy of the journalists...
that solar system is actually the home system of the Aschen (ref: Stargate) - they have converted one of their gas giants into a second sun so that their crops would have higher yield
I feel obligated to point out that in the NTSC standard, everything you see on your TV is interlaced already (at 60Hz, so the end result is considered to be 30fps).
to see how this technology will migrate to prosthetics, see the anime Angelic Layer;)
P.S. other two references I can remember from the top of my head are Playstation commercial (guessing that they will have a brain-controlled PS sometime in the future) and a gaming console in Cowboy Bebop
The conference is a collaborative effort put together by a hack-savvy group to educate the masses.
From my past experience, nearly all efforts by a group that contains "hack" in their name or description hasn't been able to "educate the masses". Most of these people just don't have what it takes to do that. What they need to do instead is to educate the media (TV, newspapers, radio, et cetera) and those will "educate" the populus.
If anyone remembers, the Internet was originally created as a defense network, able to withstand a nuclear explosion *snicker* Somebody can just accuse VeriSign of tampering with the internet in such way that it may stop being a reliable communication network...and if that doesn't really apply, then we can file an antitrust suit: VS is a monopoly in this field; they have no right to enforce sitefinder if nobody else can compete
tell me why i'm full of it to svist^at$hotmail*com
Then, there's the second category; those programs which are add-on packages. In the BSD world, this is usually called the "ports system". That name is chosen for a specific reason.
Traditionally, when you wanted to run a package on your system, the first thing you had to do was compile it. And often before you could compile it, you'd have to fiddle with it. Your system would require different header files. Sometimes, manifest constants would be different. Sometimes, you'd even need to rewrite parts of it from scratch, because of basic assumption that didn't hold on your system.
Or, in other words, you'd have to "port" it to your OS, and/or to your specific system. The basic intent of the ports system is to do all that "porting" stuff for you. That it also automates building and installing, and provides packaging services (for things like 'uninstall') isn't as well reflected in the name.
But as with many things, it grew past its name into the beast it is today. The current FreeBSD ports collection has close to 10,000 packages in it (this number will, of course, be outdated quickly, but that's the nature of development). The most obvious feature of ports is that it builds things from source all the time, rather than just install pre-build binaries. This, it seems, is another one of those blatant differences that trip people up when trying to look at BSD from a Linux perspective. That it builds from source is just a side effect, it's not the primary purpose or difference. Binary packages are also available; in fact, binary packages are built from the ports tree!
Now, it's true that most Linux users install binary packages, and most BSD users install by building from source. Partly, that's a result of the tools; the ports system is designed around the concept of building from source, with the ability to make and install binary packages being something of an afterthought, while Linux packaging like RPM and dpkg and such are designed around the concept of installing a binary package, with building from source as an afterthought. Some of this is historical; binary packaging historically isn't a predominant theme in Unix systems, as I mentioned earlier. For that matter, packaging itself is a more recent thing. Traditionally, you'd deal with uninstalling and such manually.
Now, there are advantages to pre-compiled binaries; mostly time (as in much less), and usually it'll take a lot less space to install a pre-compiled package, than it would to compile the package. There's also advantages to building from source, like avoiding all sorts of library versioning ugliness (my personal pet peeve with binary packages). You can install binary packages on Linux or BSD; you can build from source on Linux or BSD. But the users seem to be biased differently, because the systems are biased differently, because the users are biased differently... it all dovetails.
I guess what's important here is to realize that the difference between ports and RPM's isn't just that ports compile and RPM's just install. Ports are designed to cover the full range of bits and pieces of installing stuff; encoding and tracking and installing dependancies, packaging, installing and deinstalling, local changes necessary to build on your system, compile-time configuration tweaks... all those things. An RPM is just a binary package. If you want to auto-install dependancies, you have to have a higher-level tool like urpmi or apt-get to do it. And, since it's binary, you have to deal with library versioning conflicts, or missing compile options, or any of the other limitations you incur by not building it on your own system.
And further, ports, like the rest of the BSD systems, are centralized. The "ports tree" is really just a big directory tree with a bunch of categorized directories, each containing a Makefile with some variable definitions, a checksum file, a packing list, and various other possible things. Each of those directories represents a single program, which is described by th
You probably haven't noticed a small device that stands a chance of replacing PVRs. If you're still at CES, look for MVP by Hauppauge and check it out.
In a few words, it uses an ethernet connection to connect to a computer with the video data, then just forwards it to the TV over RCA or S-video cables.
Who needs a VCR that takes up space if you can record TV directly to your computer and then watch it on the TV in the comfort of your living room (that is, if you have one;) Hell, you can probably even watch those divx movies you downloaded off the net.
WOWZER! found mah machine:D..or rather another one like it: http://www.interface1.net/zx/clones/delta.html Mi ne didn't have the russian letters, though... but I now remember I color-coded the keys, too;)
I guess I should've kept it for nostalgic purposes XD
I remember my first computer. The thing about it wass... it was a Sinclair ZX-Spectrum knockoff o_O It had a slightly faster processor than z80 (i remember that because some games seemed a bit too fast and sounds a tad too high-pitched). Nevertheless, it was otherwise fully zx-compatible:)
amen, dude! imagine the horror when the majority of/.-ers will start a flame war if such a change happens.
Did you know that somewhere deep inside Intel, there's a document that states that only 20%* of incremental changes is allowed for successive chips? *err... well, i THINK it was 20%... if i'm wrong, feel free to reply:P
Slashdot Mirror
My binary clock pWnz you. I get more fun times, like 12:44:21
does anyone else find it odd that such articles (i'm talking about nature.com's article, not the /. article) rarely include actual links to the websites they're referring to? I swear, this is like a conspiracy of the journalists...
that solar system is actually the home system of the Aschen (ref: Stargate) - they have converted one of their gas giants into a second sun so that their crops would have higher yield
XD
The story, in fact, is NOT about Arthur Dent, but rather, about The Hitchhiker's Guide itself.
:P
just a thought..
They should just ask SpaceShipOne to deliver some food :)
In the future that may actually be possible
... if the HWL1 had an antenna connector: then it could be simply connected to your laptop's wifi card for a much better signal.
please fix the link
thanks
are run in an interlaced (flickery) screen mode
I feel obligated to point out that in the NTSC standard, everything you see on your TV is interlaced already (at 60Hz, so the end result is considered to be 30fps).
using human body heat as a power source ;)
to see how this technology will migrate to prosthetics, see the anime Angelic Layer ;)
P.S. other two references I can remember from the top of my head are Playstation commercial (guessing that they will have a brain-controlled PS sometime in the future) and a gaming console in Cowboy Bebop
well, at least hackers can talk to the media... and some media personalities actually know the difference between white-hat and black-hat hackers...
me == grammar fiend :D
--> nearly all efforts by any group that contains "hack" in their name or description have not been successful in "educat[ing] the masses" --
The conference is a collaborative effort put together by a hack-savvy group to educate the masses.
From my past experience, nearly all efforts by a group that contains "hack" in their name or description hasn't been able to "educate the masses". Most of these people just don't have what it takes to do that. What they need to do instead is to educate the media (TV, newspapers, radio, et cetera) and those will "educate" the populus.
...I can back up my brain
If anyone remembers, the Internet was originally created as a defense network, able to withstand a nuclear explosion *snicker* ...and if that doesn't really apply, then we can file an antitrust suit: VS is a monopoly in this field; they have no right to enforce sitefinder if nobody else can compete
Somebody can just accuse VeriSign of tampering with the internet in such way that it may stop being a reliable communication network
tell me why i'm full of it to svist^at$hotmail*com
The Ports System
Then, there's the second category; those programs which are add-on packages. In the BSD world, this is usually called the "ports system". That name is chosen for a specific reason.
Traditionally, when you wanted to run a package on your system, the first thing you had to do was compile it. And often before you could compile it, you'd have to fiddle with it. Your system would require different header files. Sometimes, manifest constants would be different. Sometimes, you'd even need to rewrite parts of it from scratch, because of basic assumption that didn't hold on your system.
Or, in other words, you'd have to "port" it to your OS, and/or to your specific system. The basic intent of the ports system is to do all that "porting" stuff for you. That it also automates building and installing, and provides packaging services (for things like 'uninstall') isn't as well reflected in the name.
But as with many things, it grew past its name into the beast it is today. The current FreeBSD ports collection has close to 10,000 packages in it (this number will, of course, be outdated quickly, but that's the nature of development). The most obvious feature of ports is that it builds things from source all the time, rather than just install pre-build binaries. This, it seems, is another one of those blatant differences that trip people up when trying to look at BSD from a Linux perspective. That it builds from source is just a side effect, it's not the primary purpose or difference. Binary packages are also available; in fact, binary packages are built from the ports tree!
Now, it's true that most Linux users install binary packages, and most BSD users install by building from source. Partly, that's a result of the tools; the ports system is designed around the concept of building from source, with the ability to make and install binary packages being something of an afterthought, while Linux packaging like RPM and dpkg and such are designed around the concept of installing a binary package, with building from source as an afterthought. Some of this is historical; binary packaging historically isn't a predominant theme in Unix systems, as I mentioned earlier. For that matter, packaging itself is a more recent thing. Traditionally, you'd deal with uninstalling and such manually.
Now, there are advantages to pre-compiled binaries; mostly time (as in much less), and usually it'll take a lot less space to install a pre-compiled package, than it would to compile the package. There's also advantages to building from source, like avoiding all sorts of library versioning ugliness (my personal pet peeve with binary packages). You can install binary packages on Linux or BSD; you can build from source on Linux or BSD. But the users seem to be biased differently, because the systems are biased differently, because the users are biased differently... it all dovetails.
I guess what's important here is to realize that the difference between ports and RPM's isn't just that ports compile and RPM's just install. Ports are designed to cover the full range of bits and pieces of installing stuff; encoding and tracking and installing dependancies, packaging, installing and deinstalling, local changes necessary to build on your system, compile-time configuration tweaks... all those things. An RPM is just a binary package. If you want to auto-install dependancies, you have to have a higher-level tool like urpmi or apt-get to do it. And, since it's binary, you have to deal with library versioning conflicts, or missing compile options, or any of the other limitations you incur by not building it on your own system.
And further, ports, like the rest of the BSD systems, are centralized. The "ports tree" is really just a big directory tree with a bunch of categorized directories, each containing a Makefile with some variable definitions, a checksum file, a packing list, and various other possible things. Each of those directories represents a single program, which is described by th
oops, correction: the device is called MediaMVP
linkified: MediaMVP
You probably haven't noticed a small device that stands a chance of replacing PVRs. If you're still at CES, look for MVP by Hauppauge and check it out.
;) Hell, you can probably even watch those divx movies you downloaded off the net.
In a few words, it uses an ethernet connection to connect to a computer with the video data, then just forwards it to the TV over RCA or S-video cables.
Who needs a VCR that takes up space if you can record TV directly to your computer and then watch it on the TV in the comfort of your living room (that is, if you have one
WOWZER! :D ..or rather another one like it: http://www.interface1.net/zx/clones/delta.htmli ne didn't have the russian letters, though... but I now remember I color-coded the keys, too ;)
found mah machine
M
I guess I should've kept it for nostalgic purposes XD
I remember my first computer. :)
The thing about it wass... it was a Sinclair ZX-Spectrum knockoff o_O
It had a slightly faster processor than z80 (i remember that because some games seemed a bit too fast and sounds a tad too high-pitched). Nevertheless, it was otherwise fully zx-compatible
i think it's obvious that the job should be left to Zap Brannigan
...just use the Fry-kun's hexadecimal filing system... :P
a somewhat longer entry at wiki :)
looks like the guys forgot to mix the concoction while adding Chemical X... err... i mean liquid nitrogen :P
amen, dude! /.-ers will start a flame war if such a change happens.
:P
imagine the horror when the majority of
Did you know that somewhere deep inside Intel, there's a document that states that only 20%* of incremental changes is allowed for successive chips?
*err... well, i THINK it was 20%... if i'm wrong, feel free to reply