If you divest US bonds, you would probably put them into bonds from other nations (and corporate bonds from non-US companies), easiest thing is to try to find a index to track; Vanguard's BNDX tracks the Bloomberg Global Aggregate ex-USD Float Adjusted RIC Capped Index (Hedged).
In a mark to market world, the value of a bond is its acquisition cost, so buying bonds enough to raise prices increases their value, but not their coupons or their face value. It's hard to make sense of the value of a sequence of payments, it's reasonable to consider the present value and the market price is an easily justified present value for a bond.
Selling bonds and buying stocks is a different thing altogether. Selling US stocks and buying EU stocks wouldn't change the value of the underlying assets, however, having an increased stock price does have benefits for the company when issuing new shares or bonds.
You would presumably supply usb floppy drives on the way back in time, and then you'd be alright. And an ethernet NIC with 10base2 and AUI for thicknet, cause twisted pair wasn't typical that early.
Network booting PCs happened a lot later, but if the booter used bios calls to access the disk, you could probably netboot that too.
I got a similar deal; the phone was locked to tracfone (or one of the other verizon owned mvnos), no contract, just had to activate it and pay the first month's service. When the month was up, put it in a drawer. 60 days from activation, pull it from the drawer, connect to wifi, and it would unlock.
> Why is anyone even tolerating a carrier selling them a phone locked for a single day (unless it is free with plan or something in which case there's nothing wrong)?
I sometimes buy carrier locked phones when the unlock period is reasonable and the locked phone + the required service is a good deal compared to buying unlocked.
I don't think a 1 year locked period is reasonable though, unless it was locked to the carrier I actually intend to use.
Verizon around the Nexus 5 still had a lot of CDMA and you needed to have a phone activated.
Now that networks are pretty much LTE and 5G only, if your phone takes a SIM, take the SIM out of the old phone and put it in the new phone. Some carriers still play games with allowlists for VoLTE though.
But you might have better luck (and better pricing) with a MVNO or the prepaid side of your preferred carrier.
Allowlists for VoLTE are a perfectly reasonable (if extremely unfortunate) safety measure.
Because of the special handling that emergency calls must get in cellular networks, many older phones will use circuit-switched fallback (AKA 3g or 2G) for those calls, even if they are otherwise VoLTE capable.
This was pretty much fine back in the day, as 2g and 3g networks were just as (if not more) widespread as VoLTE, but those networks are now being shut down. If you have one of these phones and an LTE-only carrier allows it onto their network, you will be able to make any normal call, but emergency calls will not work.
To add insult to injury, there's no way for the carrier to tell whether any specific phone does emergency calls over VoLTE or not, especially if they don't have a contract with that vendor. Some phones may only do it in certain configurations, E.G. when branded for that specific carrier and configured with their preferred modem settings.
Once a month seems like a reasonable rule of thumb.
But you're balancing the cost of the scrub vs the benefit of learning about a problem as soon as possible.
A scrub does a lot of I/O and a fair amount of computing. The scrub load competes with your application load and depending on the size of your disk(s) and their read bandwidth, it may take quite some time to do the scrub. There's even maybe some potential that the read load could push a weak drive over the edge to failure.
On my personal servers, application load is nearly meaningless, so I do an about monthly scrub from cron which I think will only scrub one zpool at a time per machine, which seems reasonable enough to me. I run relatively large spinning disks, so if I scrubbed on a daily basis, the drives would spend most of the day scrubbing and that doesn't seem reasonable. I haven't run ZFS in a work environment... I'd have to really consider how the read load impacted the production load and if scrubbing with limits to reduce production impact would complete in a reasonable amount of time... I've run some systems that are essentially alwayd busy and if a scrub would take several months, I'd probably only scrub when other systems indicate a problem and I can take the machine out of rotation to examine it.
If I had very high reliability needs or a long time to get replacement drives, I might scrub more often?
If I was worried about power consumption, I might scrub less often (and also let my servers and drives go into standby). The article's recommendation to scan at least once every 4 months seems pretty reasonable, although if you have seriously offline disks, maybe once a year is more approachable. I don't think I'd push beyond that, lots of things don't like to sit for a year and then turn on correctly.
I don't like the stock launcher because I can't remove the search bar and I never use the search bar. Nova feels like a no nonsense launcher that does what I need. I think last time it came up, the recommended option was missing something for me so I stayed with Nova, but the writing is on the wall.
Checked again and I don't see a way to get a button to show the app drawer on Lawnchair, and I don't want to use a gesture, so that's going to be hard to use.
I just tried a few launchers and none of them forced a search bar (or do you mean not on the home screen?). In fact, in Lawnchair and Octopi, I had to manually add a search bar if I wanted one.
Yeah, I tried out a handful of launchers too and none of them forced a search bar on me. Most of the had a search bar widget by default, but it was easy to remove.
I switched to Nova for the same reason. I paid for it, too. I pay and donate for good software all the time, but this is another sober reminder to never pay for proprietary software.
My previous house had hammock hooks installed by a previous owner. I'm sure you've got somewhere that could work. Or enough floorspace somewhere for a metal hammock stand.
> Just how much data do you need when these sort of clustered approaches really start to make sense?
You really need an enormous amount of data (or data processing) to justify a clustered setup. Single machines can scale up rather quite a lot.
It'll cost money, but you can order a 24x128GB ram, 24x30TB ssd system which will arrive in a few days and give you 3 TB ram, 720 TB (fast) disk. You can go bigger, but it'll be a little exotic and the ordering process might take longer.
If you need more storage/ram than around that, you need clustering. Or if the processing power you get in your single system storage isn't enough, you would need to cluster, but ~ 256 cores of cpu is enough for a lot of things.
In a mark to market world, the value of a bond is its acquisition cost, so buying bonds enough to raise prices increases their value, but not their coupons or their face value. It's hard to make sense of the value of a sequence of payments, it's reasonable to consider the present value and the market price is an easily justified present value for a bond.
Selling bonds and buying stocks is a different thing altogether. Selling US stocks and buying EU stocks wouldn't change the value of the underlying assets, however, having an increased stock price does have benefits for the company when issuing new shares or bonds.
reply