Eric Sandeen wrote:
>>
>> It did not put mkfs.btrfs in /sbin. This did however, validate all the
>> error paths ;).
> Heh ;)
> Well, mixing & matching upstream installs from source w/ rpm-packaged
> binaries is usually asking for trouble.
> I don't think it's a bug, just bad administrative practice ;)
----
SuSE is moving most if not all of their boot-related binaries off of
"/" and
putting
them in /usr, requiring that you either have 1 partition for / and /usr or you
run
their initrd that will pre-mount /usr on "/". Supposedly this is a requirement
of moving the the MS-compat boot architecture, "systemd" and is being done by
all
the distros... (supposedly)... At least RedHat and SuSE are going that way...
It's great to boot up in single-user from your hard disk and be told
mount
needs libs on a yet-to-be mounted partition...
;-/
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
