Of *course* a discrete card is going to spank an integrated one. However you're talking about a $250 card vs an entire laptop costing $500.
And unless you're doing CAD or gaming, the integrated stuff is just fine. My 2-year-old i3 with integrated graphics handles basic effects and does hardware-accelerated h.264. Realistically, that's 99% of what it spends its time doing.
The current Nvidia binary blob resides in a bit of a grey area. They have a binary blob that was originally written without looking at the linux specs, and is not a derivative work of the kernel.
They then have an open-source "shim" that is clearly a derivative work of the kernel that allows the binary blob (which has its own API) to interface with the kernel (which has a different API).
The GPL says that any derivative work must be released under the GPL. Normally (as a logic shortcut) this means anything linked against the kernel, however in this case there is a real argument that the binary blob is NOT in fact a derivative work.
However, now we have a new funky feature being added to the kernel. If the binary blob is updated to make use of it, then there is a reasonable argument that it now actually IS a derivative work of the kernel and thus should be released under the GPL.
There's absolutely no reason why you should first look for things in Google instead of asking them in a forum, other than your personal opinion that it's the right thing to do.
Actually, there is. The original poster is clearly at some sort of computing device. It is faster and easier for that person to look it up themselves rather than post on/. and then periodically check back in hoping that someone has answered their question.
Unless the person is trying to start some sort of conversation (which seems unlikely) then taking a simple straightforward question that is easily answered via Google and asking it on a web forum seems like a huge waste of time as well as intellectual laziness.
You can already get green-laser safety goggles for medial purposes which have a notch filter right around 532nm but a colour-balanced view outside that frequency. At http://brinellgreenlaser.blogspot.ca/ they specifically mention using them for pilot protection.
Seems to me the pilots could just wear these on takeoff/landing and they'd be fine.
If you streamed 128kbps data 24/7 for a month, you're looking at roughly 41GB, which really isn't all that much. 720p H.264 video runs about a gigabyte an hour, so it adds up a lot quicker.
Back in the dialup days an ISP could just get a few ISDN lines and a bunch of phone lines and modems and scale out. Since it used the phone system for the link between the subscriber and the ISP there were no "last mile" issues, that was already covered by the phone system.
Nowadays the speeds are much higher so you pretty much need a dedicated connection to each house--which basically means either the phone company or the cable company taking care of the physical wire.
Theoretically you *could* let them take care of the last mile and then branch off to a bunch of ISPs for upstream connectivity, but that adds complexity.
It costs big ISPs something like 3 cents per gigabyte.
The logical pricing model for an ISP is to treat it as a utility and charge a reasonable flat monthly cost for customer service and keeping the lines maintained (maybe $20 or $30) then a reasonable price (10-30 cents per gig?) for data throughput.
That way the bills reflect the true cost of the service, and there is minimal cross-subsidization.
The problem I have is with ISPs that want to charge $2/GB for a wired connection.
Around here all these are public utilities run by either the city or the province. (I'm in Canada.) And actually the old-school twisted-pair phone system is run by the province as well.
I think it would make perfect sense to run 'net access as a utility. It naturally lends itself to the utility pricing model as well--a flat amount per month just to get the connection and maintain the lines, then a reasonable fee per gigabyte.
I have a dual-drive RAID1 NAS with 2TB drives that is my main household storage. I've got a couple of 2TB external drives to back up the NAS, and one of them lives off-site.
The other devices all mostly access big files from the NAS.
The camera and microphone are often wonky nonstandard things that need special drivers. The CM team often needs to reverse engineer or hack together shims to get the original binary drivers working, but this is prone to glitches.
Since all IPv4 addresses have a unique IPv6 representation, an IPv6-only subscriber using a device with a hybrid dual-stack can access an IPv4 address by specifying the applicable IPv6 address. See rfc3493, "Compatibility with IPv4 Nodes".
I think Romney is actually more liberal than he needs to portray himself as in order to get tea party votes. I bet if he wasn't pandering to right-wing lunatics he and Obama could actually find a lot to agree on.
I was living up in Ottawa, and it was quicker/easier to cross the border down into the Adirondacks than to drive up to Algonquin park. Fewer people, fewer fees, less traffic. I'm surprised more people don't do it.
We have one tablet for a family of four. I really wish they'd support something like "slide to your user icon to unlock as this user", where each user would have their own preferences for visible apps, brightness, etc.
I know they want use to get one tablet per person, but that's not going to happen. (By choice, not lack of ability.)
Netflix does the same thing--really hard to share an account between young kids and adults.
slackware debian redhat mandrake fedora yellowdog (for work on powerpc) Wind River Linux (for work) centos (for work) redhat (for work) currently using fedora on work laptop
Slashdot Mirror
Of *course* a discrete card is going to spank an integrated one. However you're talking about a $250 card vs an entire laptop costing $500.
And unless you're doing CAD or gaming, the integrated stuff is just fine. My 2-year-old i3 with integrated graphics handles basic effects and does hardware-accelerated h.264. Realistically, that's 99% of what it spends its time doing.
The current Nvidia binary blob resides in a bit of a grey area. They have a binary blob that was originally written without looking at the linux specs, and is not a derivative work of the kernel.
They then have an open-source "shim" that is clearly a derivative work of the kernel that allows the binary blob (which has its own API) to interface with the kernel (which has a different API).
The GPL says that any derivative work must be released under the GPL. Normally (as a logic shortcut) this means anything linked against the kernel, however in this case there is a real argument that the binary blob is NOT in fact a derivative work.
However, now we have a new funky feature being added to the kernel. If the binary blob is updated to make use of it, then there is a reasonable argument that it now actually IS a derivative work of the kernel and thus should be released under the GPL.
If the fix changes a behaviour in a corner-case not caught by a unit test then your module regression test isn't worth much anymore.
the proper answer is to fix the law, not attack the court
if they find a day-one bug in existing legislation?
There's absolutely no reason why you should first look for things in Google instead of asking them in a forum, other than your personal opinion that it's the right thing to do.
Actually, there is. The original poster is clearly at some sort of computing device. It is faster and easier for that person to look it up themselves rather than post on /. and then periodically check back in hoping that someone has answered their question.
Unless the person is trying to start some sort of conversation (which seems unlikely) then taking a simple straightforward question that is easily answered via Google and asking it on a web forum seems like a huge waste of time as well as intellectual laziness.
They were designed originally for medical purposes.
You can already get green-laser safety goggles for medial purposes which have a notch filter right around 532nm but a colour-balanced view outside that frequency. At http://brinellgreenlaser.blogspot.ca/ they specifically mention using them for pilot protection.
Seems to me the pilots could just wear these on takeoff/landing and they'd be fine.
If you streamed 128kbps data 24/7 for a month, you're looking at roughly 41GB, which really isn't all that much. 720p H.264 video runs about a gigabyte an hour, so it adds up a lot quicker.
Back in the dialup days an ISP could just get a few ISDN lines and a bunch of phone lines and modems and scale out. Since it used the phone system for the link between the subscriber and the ISP there were no "last mile" issues, that was already covered by the phone system.
Nowadays the speeds are much higher so you pretty much need a dedicated connection to each house--which basically means either the phone company or the cable company taking care of the physical wire.
Theoretically you *could* let them take care of the last mile and then branch off to a bunch of ISPs for upstream connectivity, but that adds complexity.
It costs big ISPs something like 3 cents per gigabyte.
The logical pricing model for an ISP is to treat it as a utility and charge a reasonable flat monthly cost for customer service and keeping the lines maintained (maybe $20 or $30) then a reasonable price (10-30 cents per gig?) for data throughput.
That way the bills reflect the true cost of the service, and there is minimal cross-subsidization.
The problem I have is with ISPs that want to charge $2/GB for a wired connection.
Around here all these are public utilities run by either the city or the province. (I'm in Canada.) And actually the old-school twisted-pair phone system is run by the province as well.
I think it would make perfect sense to run 'net access as a utility. It naturally lends itself to the utility pricing model as well--a flat amount per month just to get the connection and maintain the lines, then a reasonable fee per gigabyte.
I have a dual-drive RAID1 NAS with 2TB drives that is my main household storage. I've got a couple of 2TB external drives to back up the NAS, and one of them lives off-site.
The other devices all mostly access big files from the NAS.
Works fairly well.
We cannot (given current understanding and resource consumption patters) maintain the current population of the planet indefinitely.
The camera and microphone are often wonky nonstandard things that need special drivers. The CM team often needs to reverse engineer or hack together shims to get the original binary drivers working, but this is prone to glitches.
Paying someone to do something they like doesn't actually make them happier doing it.
For me the biggest things are getting a chance to work on interesting projects, working with good people, and flexibility in hours.
but you can also just implement the firewall without NAT and get the same level of security.
The one you quote is deprecated.
Since all IPv4 addresses have a unique IPv6 representation, an IPv6-only subscriber using a device with a hybrid dual-stack can access an IPv4 address by specifying the applicable IPv6 address. See rfc3493, "Compatibility with IPv4 Nodes".
I think Romney is actually more liberal than he needs to portray himself as in order to get tea party votes. I bet if he wasn't pandering to right-wing lunatics he and Obama could actually find a lot to agree on.
I was living up in Ottawa, and it was quicker/easier to cross the border down into the Adirondacks than to drive up to Algonquin park. Fewer people, fewer fees, less traffic. I'm surprised more people don't do it.
for an addin card. Which is interesting since the actual chip is something like $90 from Intel.
but I guess you didn't use any of them.
We have one tablet for a family of four. I really wish they'd support something like "slide to your user icon to unlock as this user", where each user would have their own preferences for visible apps, brightness, etc.
I know they want use to get one tablet per person, but that's not going to happen. (By choice, not lack of ability.)
Netflix does the same thing--really hard to share an account between young kids and adults.
slackware
debian
redhat
mandrake
fedora
yellowdog (for work on powerpc)
Wind River Linux (for work)
centos (for work)
redhat (for work)
currently using fedora on work laptop