{"version":"2.1.227","anchor":"read-only-home-directories-no-longer-raise-an-error-at-start","canonical_anchor":"read-only-home-directories-no-longer-raise-an-error-at-start","heading":"Read-only home directories no longer raise an error at startup","tier":"notice","area":"Startup","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/read-only-home-directories-no-longer-raise-an-error-at-start","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Read-only home directories no longer raise an error at startup\n\nStarting up on a read-only home directory logs a note instead of throwing an error.\n\n**What**\n\nSetting up the task output link on a read-only filesystem now logs `initTaskOutputAsSymlink failed (EROFS)` and falls back, instead of surfacing an error report. `EROFS` joined the set of errno values already downgraded to a log line.\n\n**Evidence**\n\n`initTaskOutputAsSymlink failed (`\n\n- Area: Startup\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}