reynhout

Not sure "WASP-y" applies much of anywhere in Rhode Island. It's reportedly[0] the most Roman Catholic state in the U.S.

It definitely does. Barrington, East Greenwich, North Kingstown, Tiverton, Newport, and (parts of) Providence are very white, Anglo-Saxon, and Protestant. Also relatively high Jewish populations.

Rural RI (and most of rural southern New England) is definitely "more" conservative than the suburbs, but it's nothing compared to Rural USA. There's a bit of self-reliance theater going on. Rural northern New Englanders are a bit more committed.

And then there's Warwick, Cranston, Johnston, North Providence, Pawtucket, Central Falls. Long history of Italian and Portuguese culture, and the attendant Catholicism.

Rhode Island is an interesting mix of cultures. It's also quite beautiful. Most visitors have only seen it from I-95 between NYC and Boston, which is by far the least attractive way to see the area.

I miss RI pizza and seafood terribly. Nowhere else in the US really compares. However, I make the conscious trade for better Mexican and Asian food!

ChromeOS does not use an on-disk swap partition. Your SSD died just because cheap SSDs like those typically found in Chromebooks die early. :(

ChromeOS uses zram instead of physical swap, which works quite well, even on 2GB models. Zram is available in any Linux distro, being built into the kernel, and is also the default configuration in GalliumOS (Ubuntu+Xfce for Chromebooks, most of which are less broadly compatible than your PEPPY).

Which 11e? GLIMMER or ULTIMA?

What issues are you having?

You can hide the dev mode screen, or disable the functionality completely, with a firmware update.

It's a very common (and safe) procedure. There's a good write up at https://wiki.galliumos.org/Firmware

The hardware list should be correct. The ARM machines you linked are Acer Chromebooks 13s (CB5-311), not Chromebook 11s. The 2016 11s are Intel Bay Trail, and supported.

GalliumOS has good-to-very-good support for almost all Intel Chromebooks, but does not support any ARM models yet.

GalliumOS works very well on the 2015 Pixels. It was a lot of work to get there.

And as with all Linux laptops throughout history, you should definitely check the hardware compatibility list first.

You're right, that could be more clear. We plan to add ARM support, but we aren't there yet. Sorry for the disappointment.

There are 101 (really) Chromebook models, past and present. 33 are ARM, but GalliumOS supports almost all of the remaining 68.

https://wiki.galliumos.org/Hardware_Compatibility

Thank you for the info.

The work on third-party firmware is not directly a part of GalliumOS, but the projects are symbiotic. You've probably encountered the folks who focus on firmware in other venues as well.

I know booting arbitrary Linux distros is not a goal of factory firmware builds, but often it's almost there -- just not fully implemented, or not fully tested. If you're in any way involved in keeping that functionality alive, we appreciate it.

Parts of the factory firmware are open, including coreboot and SeaBIOS (where applicable) -- but not the whole ROM, and none of the build configurations are published, as far as I know.

I'd love to be wrong though, so I'd appreciate pointers to any sources.

The custom firmware options are open source, so you would be miles ahead of where you started with the factory firmware.

Dual-boot on Bay Trail is a very recent development and not all of the docs have been updated yet.

https://wiki.galliumos.org/Hardware_Compatibility is correct.

https://wiki.galliumos.org/Firmware and https://chrx.org/ have more detailed information.

Not sure where you live, Phil, but that's absolutely not the way mortgages are structured by national banks in the US.

In the early years of a mortgage, the buyer is gaining the leverage of a large amount of the bank's money, so a huge percentage of his payment goes to interest on the loan. In the later years, when the remaining principal is smaller, he pays less interest. The buyer's total payment is the same amount over the term of the loan, but the portion allocated to principal vs interest varies linearly over time, til remaining principal == 0.

At any time, the buyer can pay off the note by delivering the currently-remaining principal to the lender.

The schedule you describe would effectively prevent anyone from ever moving before their mortgage was mostly-completely satisfied. If you bought a $200K house and sold it a day later, you would have to send the bank a check for about $600K. I'm pretty sure this never happens.

Furthermore, the lender is always making his margins (modulo interest rate variability, and ignoring loan quality), because any payments sent to the lender by the borrower will get re-loaned to someone else. I guess you could write a contract so that the borrower would be penalized if he paid off early, but I'm not sure it wouldn't be usury.

Note that if you double a mortgage payment, you should be explicit that you want the excess applied to your remaining principal. Otherwise, the bank can choose to apply it as "the next payment" and therefore split at your current ratio. Regardless, you still have to pay next month's bill too. :)

So...Homebrew is MacPorts with simplified Portfiles and a smaller dependency graph?