... inside of another app platform (web browser)... inside of another app platform (the OS). Why do we need all this? We need to re-think the app platform concept.
Quite a number of programs can adjust the font size just fine. Sadly, Firefox seems to be among those that can't. It has the capability, but just plain refuses to do it when any aspect of the web page requested a font size.
HDTV has caused 1920x1200 monitors to nearly disappear. Most are now 1920x1080. 1920x1200 works fine over HDMI, as does 2048x1280. DVI has dual-channel, so it can double the bandwidth and 2560x1600 works fine there. The later could well be explained by marketing (not enough economy of scale to depress the prices and make an attractive market for other brands). The 1920x1080 situation is a huge economy of scale for OEM display panels because so many are being used for smaller HDTVs, now.
Hospital grade is not just selecting the display with a perfect panel. It's a major design difference to meet specific needs. One example requires sealed electronics in an operating room environment to prevent a risk of explosion from the gases used for anesthesia.
He handed over the passwords. He just waited until he could do so with someone that could be trusted and/or could be definitively determined to have the proper authority.
It would take more than a decade to re-implement OS software to handle 127/8 as other than loopback, and another decade for it to be widely enough deployed to be usable.
... the cost of getting static IP space will go up dramatically. ISPs will be charged more and more from ARIN for what few exist. They will in turn charge more to their customers. And there will be more strict justification requirements. It will seem like the end of the world is coming (which for many, it is). We'll probably see it in 2012:-)
Yes, many ISPs are hoarding IPv4 space already. At work, we use Verizon Business (wasn't my choice). They are using FOUR (4) PUBLIC IP addresses (a/30 in CIDR terms) just to number the connection to our router. They gave us a/29 saying that was the smallest they can do. They also said that we could use 5 of those addresses. Well, I used all 8 of them, anyway. The key to doing that is NAT. Just don't number any broadcast interface (e.g. ethernet, token ring, etc) with that subnet, and you can NAT every one of them somewhere (so you can run 8 separate HTTPS servers, for example).
So all these "business customers" are burning up 12 IP addresses each, when they could in most cases use far fewer. Put the link to the router in a private IP space (usually, no one outside of your ISP or your own network needs access to these interfaces). Route exactly as many IP addresses as needed and NAT them all. They don't even need to be contiguous (although if they are proper CIDR subnets, fewer route table entries are needed).
I assume you mean 1920x1200. Actually, Walmart carries ONE such monitor at the online store, only. Best Buy carries NONE! The problem is, everyone is going to 1920x1080 because OEM panels of that size are cheaper due to the economy of scale with the mini sized HDTV market.
Actually, the MBR partitioning method itself can work with any size drive, and use up to almost 4 TB of it (I don't use that "TiB" terminology, and won't until it goes through the proper standards process). No ONE partition can exceed 2 TB (2199023255040 bytes) in size. No ONE partition can start past the 2 TB point (sector number 4294967295). Arrange it right and you can use 4 TB less 2 sectors.
But the biggest problem is the software to handle MBR is most likely limited to using 32 bit unsigned int for sector numbers. Hence the hard 2 TB limit is an implementation limit. GPT is still better, and should be used. It supports up to 128 partitions, and provides a backup copy of the table (so writing over the first few sectors of the drive can still be recovered from). Too bad the only command line GPT-aware tool I've seen included in major Linux distros is buggy and hard to work with. I'll be writing my own for the command line crowd. I don't know if the GUI ones work right or not (I've had endless problems with GUI system admin tools for years and don't trust any of them for now).
I would agree with you. I designed a partition system many years ago, myself. And mine is even more flexible than the GPT one. For instance it included a means to identify bootable images that will reside in partitions, tagged with properties like which architecture, version numbers, relocatability or load address, etc. Basically, it allowed for a number of different properties to be attached to each partition. It even included discontiguous allocation. But when I heard Intel had made one (GPT), then I realized all my effort was in vain and every would flock to GPT because that's the one Intel would pressure everyone to use. Well, at least GPT is still a substantial improvement over the crappy one Microsoft stuck us with for so many years.
Unfortunately, Amazon's web store sucks for purchasing an LCD display. The selectors on the left have no selection mechanism for either screen size or screen geometry. None of the descriptions of the displays in the long list have the geometry which means using the browser finder won't work. To see which monitors will suit my need, I have to click on each individual model, then click on specifications, for each of the 80-some models I managed to narrow the selection down to. That's a MAJOR FAIL for Amazon's web team, and a loss of this potential customer.
Or maybe they borrowed it from lens makers where a tiny bubble in the glass was not accepted for a return. And in most cases that bubble didn't affect things (it did in very dark scenes with a strong light source aimed at the camera). Photographers were known to buy 3 or 4 of the same lens and sell the imperfect ones via the used equipment sellers (used photo equipment in 10+ condition still commanded very good prices).
Especially with applications that put row after row of junk buttons along the top and bottom and never on the sides, making the vertical space crunch even worse. Everything from Firefox to OpenOffice has this issue. We need to knock some developer heads around.
Because the stigma associated with the 32-bit LBA fields in the MBR (MS-DOS) partition table format. While a nearly-4TB drive could still be utilized in full, it would have to be divided up with the last partition starting at just under the 2TB mark, and be a size of 2TB. And this may not even work unless the implementing OS or partitioning tools handle the arithmetic with more than 32 bits. Windows 7, Linux, and most BSDs support the newer GUID Partition Table format (and even provide for an easy 128 primary partitions), drive makers know there will be issues that complicates the sale of the drives. Older OSes won't handle the size and/or the new partition table format. And besides, they are also working the 4096 sector size issue, too, which adds its own complications that minimize the market.
RAID arrays have already gone long past this limit (we have four 20-TB arrays at work) and use the new partition tables. But these are the exceptions, and they typically aren't even using drives beyond 1 TB (our 20-TB arrays have 24 drives of 1 TB). They will eventually get past these issues and you should be seeing 3TB and 4TB drives in a few months. But be prepared for 4096 byte sectors and a new partition table format (that is more powerful and even has a backup copy at the end of the drive or array).
... inside of another app platform (web browser) ... inside of another app platform (the OS). Why do we need all this? We need to re-think the app platform concept.
Quite a number of programs can adjust the font size just fine. Sadly, Firefox seems to be among those that can't. It has the capability, but just plain refuses to do it when any aspect of the web page requested a font size.
HDTV has caused 1920x1200 monitors to nearly disappear. Most are now 1920x1080. 1920x1200 works fine over HDMI, as does 2048x1280. DVI has dual-channel, so it can double the bandwidth and 2560x1600 works fine there. The later could well be explained by marketing (not enough economy of scale to depress the prices and make an attractive market for other brands). The 1920x1080 situation is a huge economy of scale for OEM display panels because so many are being used for smaller HDTVs, now.
Hospital grade is not just selecting the display with a perfect panel. It's a major design difference to meet specific needs. One example requires sealed electronics in an operating room environment to prevent a risk of explosion from the gases used for anesthesia.
He handed over the passwords. He just waited until he could do so with someone that could be trusted and/or could be definitively determined to have the proper authority.
Poorer by ... $77 million ... for raising the safety from 99% to 100%.
It would take more than a decade to re-implement OS software to handle 127/8 as other than loopback, and another decade for it to be widely enough deployed to be usable.
And that's one more year most ISPs can sit on their hands and do nothing.
... the cost of getting static IP space will go up dramatically. ISPs will be charged more and more from ARIN for what few exist. They will in turn charge more to their customers. And there will be more strict justification requirements. It will seem like the end of the world is coming (which for many, it is). We'll probably see it in 2012 :-)
Yes, many ISPs are hoarding IPv4 space already. At work, we use Verizon Business (wasn't my choice). They are using FOUR (4) PUBLIC IP addresses (a /30 in CIDR terms) just to number the connection to our router. They gave us a /29 saying that was the smallest they can do. They also said that we could use 5 of those addresses. Well, I used all 8 of them, anyway. The key to doing that is NAT. Just don't number any broadcast interface (e.g. ethernet, token ring, etc) with that subnet, and you can NAT every one of them somewhere (so you can run 8 separate HTTPS servers, for example).
So all these "business customers" are burning up 12 IP addresses each, when they could in most cases use far fewer. Put the link to the router in a private IP space (usually, no one outside of your ISP or your own network needs access to these interfaces). Route exactly as many IP addresses as needed and NAT them all. They don't even need to be contiguous (although if they are proper CIDR subnets, fewer route table entries are needed).
Then you have an annoying bar down the middle. I just want 1920x1440 or 2048x1536. What's so hard about that?
I assume you mean 1920x1200. Actually, Walmart carries ONE such monitor at the online store, only. Best Buy carries NONE! The problem is, everyone is going to 1920x1080 because OEM panels of that size are cheaper due to the economy of scale with the mini sized HDTV market.
Actually, many bad pixels can be fixed. Many cannot be fixed. And monitors with unfixable bad pixels may still be sellable at a lower price.
Actually, the MBR partitioning method itself can work with any size drive, and use up to almost 4 TB of it (I don't use that "TiB" terminology, and won't until it goes through the proper standards process). No ONE partition can exceed 2 TB (2199023255040 bytes) in size. No ONE partition can start past the 2 TB point (sector number 4294967295). Arrange it right and you can use 4 TB less 2 sectors.
But the biggest problem is the software to handle MBR is most likely limited to using 32 bit unsigned int for sector numbers. Hence the hard 2 TB limit is an implementation limit. GPT is still better, and should be used. It supports up to 128 partitions, and provides a backup copy of the table (so writing over the first few sectors of the drive can still be recovered from). Too bad the only command line GPT-aware tool I've seen included in major Linux distros is buggy and hard to work with. I'll be writing my own for the command line crowd. I don't know if the GUI ones work right or not (I've had endless problems with GUI system admin tools for years and don't trust any of them for now).
I would agree with you. I designed a partition system many years ago, myself. And mine is even more flexible than the GPT one. For instance it included a means to identify bootable images that will reside in partitions, tagged with properties like which architecture, version numbers, relocatability or load address, etc. Basically, it allowed for a number of different properties to be attached to each partition. It even included discontiguous allocation. But when I heard Intel had made one (GPT), then I realized all my effort was in vain and every would flock to GPT because that's the one Intel would pressure everyone to use. Well, at least GPT is still a substantial improvement over the crappy one Microsoft stuck us with for so many years.
Unfortunately, Amazon's web store sucks for purchasing an LCD display. The selectors on the left have no selection mechanism for either screen size or screen geometry. None of the descriptions of the displays in the long list have the geometry which means using the browser finder won't work. To see which monitors will suit my need, I have to click on each individual model, then click on specifications, for each of the 80-some models I managed to narrow the selection down to. That's a MAJOR FAIL for Amazon's web team, and a loss of this potential customer.
Or maybe they borrowed it from lens makers where a tiny bubble in the glass was not accepted for a return. And in most cases that bubble didn't affect things (it did in very dark scenes with a strong light source aimed at the camera). Photographers were known to buy 3 or 4 of the same lens and sell the imperfect ones via the used equipment sellers (used photo equipment in 10+ condition still commanded very good prices).
I will check and see what their policy is, here.
How many of those stores also sell high end computer monitors (like 2560x1600) and have them in stock?
Of course it works. That's because the sleazeball retailers that used a "screw the consumer" business model to get rich quick ... moved to the USA.
So, in a program with 4,096,000 lines of code in it, you'd insist on fixing it if 0.000024% of those lines let any hacker in? I would!
Even Bet Buy doesn't have the high-end displays. Does Costco?
Especially with applications that put row after row of junk buttons along the top and bottom and never on the sides, making the vertical space crunch even worse. Everything from Firefox to OpenOffice has this issue. We need to knock some developer heads around.
I've looked for one and have not found it. You know of one? And I'm not talking about Walmart since they don't have the top end monitors I would want.
Because the stigma associated with the 32-bit LBA fields in the MBR (MS-DOS) partition table format. While a nearly-4TB drive could still be utilized in full, it would have to be divided up with the last partition starting at just under the 2TB mark, and be a size of 2TB. And this may not even work unless the implementing OS or partitioning tools handle the arithmetic with more than 32 bits. Windows 7, Linux, and most BSDs support the newer GUID Partition Table format (and even provide for an easy 128 primary partitions), drive makers know there will be issues that complicates the sale of the drives. Older OSes won't handle the size and/or the new partition table format. And besides, they are also working the 4096 sector size issue, too, which adds its own complications that minimize the market.
RAID arrays have already gone long past this limit (we have four 20-TB arrays at work) and use the new partition tables. But these are the exceptions, and they typically aren't even using drives beyond 1 TB (our 20-TB arrays have 24 drives of 1 TB). They will eventually get past these issues and you should be seeing 3TB and 4TB drives in a few months. But be prepared for 4096 byte sectors and a new partition table format (that is more powerful and even has a backup copy at the end of the drive or array).
... gets 137.333...(repeating). So 137 votes is not even enough. 136 is clearly not.