In its current form? No. It's far more likely that the interesting bits of technology will be integrated into swsusp - there's no chance whatsoever of stuff like the in-kernel user interface going in.
The kernel part of the driver has about 250K of source code (about half of which is header files) and 3.5 megabytes of binary. None of the userspace code is open. How is that "mostly open source"?
The GroupDAV standard is nice and simple, and it ought to be easy enough to implement. However, it's lacking in various useful features. For instance,
Due to this reasons the client SHOULD store alarms locally and SHOULD NOT transmit them to server. The server is MAY reject iCalendar resources containing alarms but MUST signal that using a proper error code.
Woo. I use a GroupDAV server to store my calendar information from my desktop. While I'm on the road, I synchronise my PDA against it. Then I have to go through every event to reset the alarms, since otherwise I don't get any warning about them. Excellent.
Clients SHOULD not post recurring tasks to the server.
I mean, come on.
To allow the client to search for UIDs stored in the server, the server would need to expose the UID as a WebDAV property for use in DASL queries. While this is possible in some implementations (eg OpenGroupware.org ZideStore) it would complicate basic implementations significantly.
Yeah, I can see that making synchronisation fun.
The standard is littered with "This is difficult, so it's not implemented". That's fine - it results in a lightweight specification that's easy to implement, and in many cases it may well be good enough. But it's not appropriate for this to be the standard for open source groupware. It's missing too much functionality. Trying to sell it as a solution for competing with existing groupware solutions is just insane.
I've disassembled the Thinkpad BIOS and read the code myself. It scans every PCI device and flags any that have a class id starting with "02" (which signifies communication devices). Each communication device is then compared against a whitelist of PCI vendors, device IDs and subvendor information. If it's not on that list, the system will print an "1802: Unauthorized network device detected" error and stop booting. At that point, all you can do is switch off the machine. It's easy enough to fix in the BIOS - thankfully, it's even easier to fix by setting a CMOS bit that disables the check.
Intel tags each wireless card they make with a subdevice string. Each laptop manufacturer gets a different subdevice string in their cards. The only people making these cards are Intel, but HPs will only work with cards with an HP subdevice string, and IBMs with an IBM one. Now, it's possible that Intel make "better" cards for some manufacturers than others, but it's not very likely.
The FCC regulations don't actually require what IBM does - the closest is a requirement that you not be able to use unauthorised antennae with an authorised card, which is the direct opposite of IBM's solution. The amount of the planet over which the FCC have jurisdiction is also fairly small compared to the size of IBM's market...
My recollection is that Fedora aims to include only free software by default. Realplayer is very, very non-free. Helix (the approximately free software that Realplayer is built on) doesn't appear to include mp3 support.
The study didn't prove that large eagles existed. The remains they had did that. All they did was demonstrate that the large eagles were related to much smaller ones, and speciation probably only occurred a million years ago. Comparative genomics is a useful science, but it's not at the point of telling us what an eagle's adult wingspan is yet.
No, that wasn't the reason. The reason for putting the button that you're most likely to want to choose (the one that means "Yes, do this thing I just asked you to do") in the corner is because the first place you tend to look is the corner. Putting it above the message would be confusing because you want to read the message before thinking about your response.
With the extra battery, you get 6 hours of life for a total weight of about 2.5 pounds. That's roughly the same as for the Thinkpad X40 (which is a tiny bit heavier, but gets another hour and a half out of a charge)
Slashdot Mirror
In its current form? No. It's far more likely that the interesting bits of technology will be integrated into swsusp - there's no chance whatsoever of stuff like the in-kernel user interface going in.
The kernel part of the driver has about 250K of source code (about half of which is header files) and 3.5 megabytes of binary. None of the userspace code is open. How is that "mostly open source"?
Based on http://www.ubuntu.com/wiki/HoaryPMResults, a decently large number of machines will do ACPI suspend to RAM now. You probably want vbetool to restore video state after resume.
The GroupDAV standard is nice and simple, and it ought to be easy enough to implement. However, it's lacking in various useful features. For instance,
Due to this reasons the client SHOULD store alarms locally and SHOULD NOT transmit them to server. The server is MAY reject iCalendar resources containing alarms but MUST signal that using a proper error code.
Woo. I use a GroupDAV server to store my calendar information from my desktop. While I'm on the road, I synchronise my PDA against it. Then I have to go through every event to reset the alarms, since otherwise I don't get any warning about them. Excellent.
Clients SHOULD not post recurring tasks to the server.
I mean, come on.
To allow the client to search for UIDs stored in the server, the server would need to expose the UID as a WebDAV property for use in DASL queries. While this is possible in some implementations (eg OpenGroupware.org ZideStore) it would complicate basic implementations significantly.
Yeah, I can see that making synchronisation fun.
The standard is littered with "This is difficult, so it's not implemented". That's fine - it results in a lightweight specification that's easy to implement, and in many cases it may well be good enough. But it's not appropriate for this to be the standard for open source groupware. It's missing too much functionality. Trying to sell it as a solution for competing with existing groupware solutions is just insane.
No. It modifies the contents of the CMOS, not the BIOS flash. /dev/nvram doesn't provide access to BIOS code.
No Alphas used Microchannel - you're thinking of Turbochannel.
Here
Uh, Insyde, not Incyte.
Unlikely. The affected HP and Compaq ones I've looked at are by Incyte, while the Thinkpad BIOSes are from Phoenix.
I've disassembled the Thinkpad BIOS and read the code myself. It scans every PCI device and flags any that have a class id starting with "02" (which signifies communication devices). Each communication device is then compared against a whitelist of PCI vendors, device IDs and subvendor information. If it's not on that list, the system will print an "1802: Unauthorized network device detected" error and stop booting. At that point, all you can do is switch off the machine. It's easy enough to fix in the BIOS - thankfully, it's even easier to fix by setting a CMOS bit that disables the check.
The Thinkpad TCPA chip has nothing to do with the BIOS whitelist for wireless cards.
Intel tags each wireless card they make with a subdevice string. Each laptop manufacturer gets a different subdevice string in their cards. The only people making these cards are Intel, but HPs will only work with cards with an HP subdevice string, and IBMs with an IBM one. Now, it's possible that Intel make "better" cards for some manufacturers than others, but it's not very likely.
MiniPCI is a PCI SIG standard. See here.
There's an easier way. See this page for a utility that disables the check without requiring BIOS modification.
The FCC regulations don't actually require what IBM does - the closest is a requirement that you not be able to use unauthorised antennae with an authorised card, which is the direct opposite of IBM's solution. The amount of the planet over which the FCC have jurisdiction is also fairly small compared to the size of IBM's market...
My recollection is that Fedora aims to include only free software by default. Realplayer is very, very non-free. Helix (the approximately free software that Realplayer is built on) doesn't appear to include mp3 support.
The study didn't prove that large eagles existed. The remains they had did that. All they did was demonstrate that the large eagles were related to much smaller ones, and speciation probably only occurred a million years ago. Comparative genomics is a useful science, but it's not at the point of telling us what an eagle's adult wingspan is yet.
There is no ACPI certification process, to the best of my knowledge
The final release does not use the controversial theme by default. It's been replaced with something more similar to the earlier previews.
Let me rephrase that. Why do you believe that you are the intended userbase at this point in time?
No, that wasn't the reason. The reason for putting the button that you're most likely to want to choose (the one that means "Yes, do this thing I just asked you to do") in the corner is because the first place you tend to look is the corner. Putting it above the message would be confusing because you want to read the message before thinking about your response.
Why do you believe that those claiming to be alienated are the intended userbase?
The machine in question isn't run by Red Hat admins.
They both run QTopia. You'll be able to use the same synchronisation software on both.
With the extra battery, you get 6 hours of life for a total weight of about 2.5 pounds. That's roughly the same as for the Thinkpad X40 (which is a tiny bit heavier, but gets another hour and a half out of a charge)