SSDs are good at being fast and surviving being dropped. HDDs are good at being cheap per GB. Both have their place. There is no reason you can't have both in (or for use with) the same system.
I work at a small-market IT subcontractor where we do project and break-fix work for a huge variety of businesses and hardware manufacturers.
Out there in the real world very few large businesses use over 40~80GB on the primary hard drives of end-user desktops or point of sale, despite the fact that they all come with at least 500GB. Anything other than the OS and applications and current user's profile really should live on the network somewhere. That somewhere is probably on a spinning platter.
SMBs often will have a lot of data on each desktop HDD, but they really should have a workgroup server to do centralized authentication (domain|LDAP), email (exchange|IMAP), user (profiles|homedirs), fileshares and centralized backup as very few have any organized way to recover from loss or damage of one or more workstation. Most users need very little space; Executive, secretary, accounting, medical office data, etc all is small and should really be on a server. Some applications (ie CAD, GIS, medical imaging, media editing, etc) do require large local fast storage, but this can be handled by having two drives: 1 SSD and one or more HDD in the few workstations that need it.
Home users can easily have more than that much on their desktop or laptop, but there's no reason their computer can't have 1 SSD and 1 or more HDDs be they internal, external, or NAS.
Or desktops with heatpipe based heatsinks... Tiny laptop fans can get pretty loud. With much bigger dissipation surface an overclockig heatsink on a low power CPU can spend most of it's time with the fan off.
Windows NT was first released in 1993, making it the same age as Debian. Before NT, windows was a user interface on top of DOS, not an OS on it's own (although it was doing VM as of 3.1 and networking as of 3.11, but not it's own filesystem management).
I doubt if there's anything Pre-Built and Open-Source that can do that, but I bet with a few person-years or less of work you could make something with GRASS, PostGIS and/or qGIS that can map the equipment given a GPS & SMS capable tracking device (purpose built or smartphone app). Not so sure about the route finding though.
For a failed build, our upstream helpdesks usually recommend HDD, then MB, then PS. CPU and RAM are way down the list (strangely above bringing in a network verifier which almost always finds the problem if the HDD and MB didn't fix it and the deployment is network based). This observation is based on most of the big-time contracting services in Canada.
For most users it may be of limited utility, But I can see it being useful for technicians who may want to be able to connect customers laptops to mobile hotspots to download patches etc, as well as a host of other uses. I've thought of doing this (albeit with a Dlink DiR-655 and rocket stick, not some $300 purpose built device).
Problem with that is to know which site is which, you'd pretty much have to either be into kiddie porn yourself or be in law enforcement and assigned to KP patrol.
The OLPC must be built substantially different from every laptop that I've worked on (Acer Aspire One, Almost every recent Dell, Thinkpad, HP, or Toshiba). Almost all of them have the LVDS connector on the motherboard and fed through the hinge, requiring disassembling the base to some degree to get the cable out, then about 6 screws to open the bezel, then several more to get the screen module out, then several more to get the frame off the screen. I suppose you could re-use the LVDS cable to avoid opening the base, but it's usually fragile.
Makes me wonder if an electrolysis->fuel cell system would be a good way of doing this... You'd just have to clean out the electrolysis cell periodically and replace the energy lost to heat (hopefully similar to what the RO pumps were using).
This is based on the assumption that you're not ingesting any ions in the food you eat. That would pretty much require a diet of pure paper or complete fasting. Anything that was once alive and hasn't been completely purified (paper or pure gelatine) is going to have some sodium, potassium, and calcium.
Or, they could do like the article says and pre-calculate it all. It's made even easier by the fact that there's only 12 jurisdictions, all of which are processed by CRA, and no regional district or city income tax. Most people would just need to proof-read their return and sign it.
Apparently one of the advancements in OSX snow leopard is that SL apps keep track of whether they have any pending writes. If they don't, the OS can kill -9 them on shutdown, so only third-party apps have to be sigterm'd, which greatly speeds shutdown. (I haven't upgraded yet so I've not experienced the difference this makes).
When Linux pages out but doesn't need the memory at the moment, it keeps the contents, but clears the dirty bit after writing the page out. It only needs to read the data back in if it has given the space to another process (speeding up that more-active process).
Actually, the first things I think of are runaway printer drivers, Failed HDDs, Bloatware, and cases so thin that a parallel cable can tork a PCI riser out of it's socket.
Slashdot Mirror
This entire "debate" is rediculous anyways.
SSDs are good at being fast and surviving being dropped. HDDs are good at being cheap per GB. Both have their place. There is no reason you can't have both in (or for use with) the same system.
I work at a small-market IT subcontractor where we do project and break-fix work for a huge variety of businesses and hardware manufacturers.
Out there in the real world very few large businesses use over 40~80GB on the primary hard drives of end-user desktops or point of sale, despite the fact that they all come with at least 500GB. Anything other than the OS and applications and current user's profile really should live on the network somewhere. That somewhere is probably on a spinning platter.
SMBs often will have a lot of data on each desktop HDD, but they really should have a workgroup server to do centralized authentication (domain|LDAP), email (exchange|IMAP), user (profiles|homedirs), fileshares and centralized backup as very few have any organized way to recover from loss or damage of one or more workstation. Most users need very little space; Executive, secretary, accounting, medical office data, etc all is small and should really be on a server. Some applications (ie CAD, GIS, medical imaging, media editing, etc) do require large local fast storage, but this can be handled by having two drives: 1 SSD and one or more HDD in the few workstations that need it.
Home users can easily have more than that much on their desktop or laptop, but there's no reason their computer can't have 1 SSD and 1 or more HDDs be they internal, external, or NAS.
Or desktops with heatpipe based heatsinks... Tiny laptop fans can get pretty loud. With much bigger dissipation surface an overclockig heatsink on a low power CPU can spend most of it's time with the fan off.
Most of the things the reporter is pointing to under the hood of that car are actually fuel or vacuum lines, not wires.
Windows NT was first released in 1993, making it the same age as Debian. Before NT, windows was a user interface on top of DOS, not an OS on it's own (although it was doing VM as of 3.1 and networking as of 3.11, but not it's own filesystem management).
Alienware is Dell XPS with a fancier case.
Why were they 1) on your network and 2) expecting privacy and/or not using an encrypted tunnel?
I doubt if there's anything Pre-Built and Open-Source that can do that, but I bet with a few person-years or less of work you could make something with GRASS, PostGIS and/or qGIS that can map the equipment given a GPS & SMS capable tracking device (purpose built or smartphone app). Not so sure about the route finding though.
8 years... The location of the G8 rotates among the members.
Just like the "homebuilt cruise missile" (basically a V1 with GPS guidance) from New Zeland a few years ago.
Nice case, thanks... I'm looking to build a giant box to house HDDs and VMs, and this looks like just the ticket.
A cell phone with SMS service only and a really loud ringtone. Works where there is marginal cell service as only the SMS has to get through.
An outlook or Thunderbird plugin would have done the job much better.
For a failed build, our upstream helpdesks usually recommend HDD, then MB, then PS. CPU and RAM are way down the list (strangely above bringing in a network verifier which almost always finds the problem if the HDD and MB didn't fix it and the deployment is network based). This observation is based on most of the big-time contracting services in Canada.
For most users it may be of limited utility, But I can see it being useful for technicians who may want to be able to connect customers laptops to mobile hotspots to download patches etc, as well as a host of other uses. I've thought of doing this (albeit with a Dlink DiR-655 and rocket stick, not some $300 purpose built device).
If most programs are spending 20% of their time on memory management, something is wrong.
Problem with that is to know which site is which, you'd pretty much have to either be into kiddie porn yourself or be in law enforcement and assigned to KP patrol.
The OLPC must be built substantially different from every laptop that I've worked on (Acer Aspire One, Almost every recent Dell, Thinkpad, HP, or Toshiba). Almost all of them have the LVDS connector on the motherboard and fed through the hinge, requiring disassembling the base to some degree to get the cable out, then about 6 screws to open the bezel, then several more to get the screen module out, then several more to get the frame off the screen. I suppose you could re-use the LVDS cable to avoid opening the base, but it's usually fragile.
If disks in the safe deposit box are fast enough to access, running to the store to buy a generic power supply is fast enough recovery.
BC produces so much Hydroelectric power we export most of it.
Makes me wonder if an electrolysis->fuel cell system would be a good way of doing this... You'd just have to clean out the electrolysis cell periodically and replace the energy lost to heat (hopefully similar to what the RO pumps were using).
This is based on the assumption that you're not ingesting any ions in the food you eat. That would pretty much require a diet of pure paper or complete fasting. Anything that was once alive and hasn't been completely purified (paper or pure gelatine) is going to have some sodium, potassium, and calcium.
Errr... 13 jurisdictions... I forgot about Nunavut.
Or, they could do like the article says and pre-calculate it all. It's made even easier by the fact that there's only 12 jurisdictions, all of which are processed by CRA, and no regional district or city income tax. Most people would just need to proof-read their return and sign it.
Apparently one of the advancements in OSX snow leopard is that SL apps keep track of whether they have any pending writes. If they don't, the OS can kill -9 them on shutdown, so only third-party apps have to be sigterm'd, which greatly speeds shutdown. (I haven't upgraded yet so I've not experienced the difference this makes).
When Linux pages out but doesn't need the memory at the moment, it keeps the contents, but clears the dirty bit after writing the page out. It only needs to read the data back in if it has given the space to another process (speeding up that more-active process).
Actually, the first things I think of are runaway printer drivers, Failed HDDs, Bloatware, and cases so thin that a parallel cable can tork a PCI riser out of it's socket.