From: Linda Walsh <xfs@tlinx.org>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: enable test 032 (mkfs overwrite) for btrfs
Date: Sat, 16 Mar 2013 05:14:04 -0700 [thread overview]
Message-ID: <5144620C.4040203@tlinx.org> (raw)
In-Reply-To: <5143568F.5060900@redhat.com>
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...
;-/
WARNING: multiple messages have this Message-ID (diff)
From: Linda Walsh <xfs@tlinx.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: enable test 032 (mkfs overwrite) for btrfs
Date: Sat, 16 Mar 2013 05:14:04 -0700 [thread overview]
Message-ID: <5144620C.4040203@tlinx.org> (raw)
In-Reply-To: <5143568F.5060900@redhat.com>
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...
;-/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-16 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 16:01 [PATCH] xfstests: enable test 032 (mkfs overwrite) for btrfs Eric Sandeen
2013-03-13 16:01 ` Eric Sandeen
2013-03-15 17:07 ` Rich Johnston
2013-03-15 17:07 ` Rich Johnston
2013-03-15 17:12 ` Eric Sandeen
2013-03-15 17:12 ` Eric Sandeen
2013-03-16 12:14 ` Linda Walsh [this message]
2013-03-16 12:14 ` Linda Walsh
2013-03-15 17:11 ` Rich Johnston
2013-03-15 17:11 ` Rich Johnston
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5144620C.4040203@tlinx.org \
--to=xfs@tlinx.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.