https://barn.pgsty.com/tags/ux/ Recent content in UX on Barn Hugo en-US Wed, 02 Sep 2026 00:00:00 +0800 https://barn.pgsty.com/blog/release/farrow-0.4.0/ Wed, 02 Sep 2026 00:00:00 +0800 https://barn.pgsty.com/blog/release/farrow-0.4.0/ <p>Farrow 0.4.0 was the public pre-1.0 release superseded by 0.5.0. It makes the first run one command, fixes the default data disk on Debian and Ubuntu images, and gives every command the same output style. The Pigsty Inventory format, the fixed-IP deployment model, the state layout, and the embedded Catalog revision <code>2026082903</code> are unchanged.</p> <h2 id="what-changed">What changed </h2> <ul> <li>On a terminal, <code>farrow up</code> runs <code>farrow setup</code> itself when the fixed-IP network has never been installed, shows the setup plan, asks before the privileged step, and then continues. <code>farrow init</code> points at <code>farrow up</code>.</li> <li><code>vm_disks[].fs</code> defaults to <code>auto</code>: a blank disk is formatted XFS when the guest has <code>mkfs.xfs</code> and ext4 otherwise, the same choice Pigsty&rsquo;s Vagrant flow makes. The old <code>xfs</code> default failed on Debian and Ubuntu images, which ship without xfsprogs. Deployments created with the old default are not reported as drift and their persistent disks stay compatible.</li> <li>The guest error marker carries the failing command&rsquo;s last message, so <code>up</code> reports <code>guest bootstrap failed during data-disks: xfs requested but mkfs.xfs is unavailable</code> instead of an exit status.</li> <li>Lifecycle commands and <code>status</code> print a node table and, after <code>up</code>, a <code>next: farrow ssh &lt;node&gt;</code> hint. <code>plan</code> and <code>validate</code> print one line when nothing changes; <code>image list</code>, <code>network status</code>, <code>doctor</code>, and preflight errors use plain sentences without machine codes; <code>spec hash</code> and other internals moved to <code>--json</code>. Errors about an unknown node list the nodes.</li> <li><code>farrow ssh &lt;node&gt; -- 'df -h /data; id'</code> passes the remote command exactly as OpenSSH does.</li> </ul> <h2 id="upgrading">Upgrading </h2> <p>A d13, d12, or Ubuntu node created by 0.3.0 or earlier whose <code>/data</code> never mounted needs one <code>farrow recreate &lt;node&gt;</code>; the disk is then formatted ext4 on those images and XFS on Enterprise Linux images. Automation that runs <code>up</code> on an unprepared host without a terminal still needs <code>farrow setup --yes</code> first.</p>