I would presume that phones are not allowed on the factory floor - if only for safety reasons around machinery. That would reduce the probability of having records.
I think the article is overplaying the promise of CO reductions.
Around 60% of CO2 (see 1) emissions during cement manufacturing are just a byproduct of the chemical process converting calcium carbonate to lime (see 2) - nothing that solar power can help with.
I thought that the problem with air travel is not (just) the amount of CO2 emitted, but also the altitude, which makes the green house effect bigger per ton of CO2.
It's not about CO2 emissions, but rather the high-altitude NOx that contributes more to climate change than low-altitude emissions. However, it's debatable whether the amount is very significant, at least compared to other sources of NOx.
The byproduct of the chemical process is largely reabsorbed as the cement cures. The part that's from the fuel burned to heat it is not, and that's the part that matters in the long-term balance.
What keeps me from updating that I am confused about the way forward regarding FileVault & APFS. I currently have FileVault enabled as I need my drive to be fully encrypted (liability for my clients). I want my backups to be encrypted as well.
But now APFS solves disk encryption on FS layer instead of going through CoreStorage. And I'm confused about the way forward for me.
Is there some documentation that explains
1) What happens to FileVault/Backups during initial conversion?
2) Am I better off to disable FileVault and then encrypt using APFS?
3) How does the APFS full disk encryption work? Does it have any problems, especially backup related?
4) Can I enable/disable FileVault after the conversion?
From my personal experience with the developer betas on my laptop;
I experienced no issue during the conversion of Corestorage Filevault to APFS Filevault. The conversion to APFS was offered as an option to me during the Developer Beta series.
I am not sure whether this will be done automatically for the release version. However I do understand that the conversion will only be offered to systems with Flash Storage only, whereas Fusion Drive and Hard Disk equipped systems will not. (as per: https://support.apple.com/en-us/HT208018 )
I found that the process required no interaction on my part and that my system came back up without issue. Likewise, there was no change with how Time Machine operated for me, in fact I don't believe that Time Machine backups are touched by the conversion process.
On another fusion drive equipped system I have, I was able to manually enable Filevault after filesystem conversion to APFS. You should be able to disable it after conversion too, though I've not yet tested this out.
That was a concern to me before I migrated two laptops: one had FileVault enabled and the other not†. The conversion dealt with FileVault without a hitch. Even better, enabling FileVault on the non-encrypted one after the conversion let it encrypt without even the reboot previously required with HFS+, one less excuse not to enable it.
Backups to an external disk are still done to HFS+. External disks formatted as APFS either do not show up as available disks to backup to or prompt to format the disk back to HFS+ (I encountered both cases as I was trying to put TM into submission on that one). Remote backups (over AFP) are unaffected and still use (optionally encrypted) sparse bundles. So Time Machine itself appears to have not changed much in that regard. Local snapshots do leverage APFS snapshots though and are browsable at /Volumes/com.apple.TimeMachine.localsnapshots.
† A mistake on my part following a restore from Time Machine where I did not enable encryption.
And I'm even more confused about how things should go about for more complicated Core Storage setups. I have several disks with Core Storage. All of them have multiple logical volume families in a single logical volume group. And some are encrypted and others are not. I also have Core Storage volume groups that span multiple hard disks and/or hard disk partitions. I read the Ars review but that doesn't cover APFS in much technical detail at all. I'm really missing those Core Storage deep dives in Siracusa reviews.
System Information 10.13 reports a medium type "SSD" for my stock MacPro6,1 flash and medium types "SSD" or "Rotational", as appropriate, for SATA SSDs and hard drives connected via non-RAID Thunderbolt AHCI controllers.
For my two Thunderbolt SAS RAID arrays, however, System Information shows no "Medium Type" field at all. And Disk Utility reports "Solid state: No" for both, even though one is, in fact, all SSD.
Therefore, on this one particular Areca controller at least, I'd be willing to bet that SSD boot volumes would look just like rotational hard drives to APFS and the installer, and therefore would not have been auto-converted at installation time.
With that said, on the GM candidate, converting the volumes on these RAID arrays to APFS after the fact was as simple as right-clicking each in Disk Utility and selecting "Convert to APFS...". And it the week or so since I did so, I've had no problems or regrets.
All volumes on this system are FileVault-encrypted, and APFS conversion did nothing to change this.
Really? If you're going to do that, it seems like you might as well just merge all those users into a single account anyway, considering how trivial it would be for any one of them to execute arbitrary code as any other.
I moved away from homebrew, to compiling my own software on macOS which I just put in ~/build. I don't use sudo make install since I own the ~/build folder.
I'm planning to try the same. Would you have some pointers where to start my job search? Did you write to specific companies or did you start your search by crawling job offer sites?
take a look at https://tus.io/