| Subject: | Re: [PATCH] xfstests: enable test 032 (mkfs overwrite) for btrfs |
|---|---|
| From: | Linda Walsh <xfs@xxxxxxxxx> |
| Date: | Sat, 16 Mar 2013 05:14:04 -0700 |
| Cc: | linux-btrfs <linux-btrfs@xxxxxxxxxxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <5143568F.5060900@xxxxxxxxxx> |
| References: | <5140A2BC.7010800@xxxxxxxxxx> <51435555.2020706@xxxxxxx> <5143568F.5060900@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.24) Gecko/20100228 Lightning/0.9 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666 |
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...
;-/
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_fsr, sunit, and swidth, Stan Hoeppner |
|---|---|
| Next by Date: | Xfs_repair and journalling, Subranshu Patel |
| Previous by Thread: | Re: [PATCH] xfstests: enable test 032 (mkfs overwrite) for btrfs, Eric Sandeen |
| Next by Thread: | Re: [PATCH] xfstests: enable test 032 (mkfs overwrite) for btrfs, Rich Johnston |
| Indexes: | [Date] [Thread] [Top] [All Lists] |