<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>114188</bug_id>
          
          <creation_ts>2005-12-01 13:37 0000</creation_ts>
          <short_desc>vserver-sources missing bme patch</short_desc>
          <delta_ts>2006-04-21 00:04:20 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Core system</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>c.affolter@stepping-stone.ch</reporter>
          <assigned_to>vserver-devs@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>c.affolter@stepping-stone.ch</who>
            <bug_when>2005-12-01 13:37:32 0000</bug_when>
            <thetext>It would be really nice if Herbert&apos;s bme (Bind Mount Extensions) patch could be
included in the vserver-sources. The patch provides read only bind mounts.

Otherwise the suggested handy /usr/portage ro bind mount within a vserver will
be writable.

I&apos;ve successfully applied the latest bme patch
(http://vserver.13thfloor.at/Experimental/delta-2.6.14.2-vs2.0.1-rc2-bme0.06.1.diff)
against vserver-sources 2.0.1_rc3-r2

Reproducible: Always
Steps to Reproduce:
1.
2.
3.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>phreak@gentoo.org</who>
            <bug_when>2005-12-02 02:46:18 0000</bug_when>
            <thetext>Thanks for the headsup Christian, commited an -r3 just a second ago.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>c.affolter@stepping-stone.ch</who>
            <bug_when>2006-04-19 15:34:18 0000</bug_when>
            <thetext>I&apos;m sorry for disturbing you again with this issue... But within vserver-sources-2.1.0-r[1|2] (2.6.15) the bme patch seems to be disappeared.

As far as I can see, the patch was included for the last time inside the [1] patch set.

unfortunately according to this thread [2] there isn&apos;t any bme diff against 2.6.15 around :(


I&apos;ve tried to apply both, the 2.6.14 [3] and 2.6.16 [4] diff against the vserver-sources-2.1.0-r2 (2.6.15), with no luck.

Would it be possible to re-include the patch in the next release (&gt;=2.6.16), or even forward/back port one of the available patches?

Many thanks!

[1] http://dev.gentoo.org/~phreak/distfiles/vserver-patches-2.6.14_2.0.1_rc5-r1.tar.bz2
[2] http://list.linux-vserver.org/archive/vserver/msg12329.html
[3] http://vserver.13thfloor.at/Experimental/BME/delta-2.6.14.2-vs2.0.1-rc2-bme0.06.1.diff
[4] http://vserver.13thfloor.at/Experimental/patch-2.6.16-rc1-bme0.06.2.diff
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>c.affolter@stepping-stone.ch</who>
            <bug_when>2006-04-19 15:51:24 0000</bug_when>
            <thetext>Uhmm, I was talking about sys-kernel/vserver-sources-2.0.1-r2 not sys-kernel/vserver-sources-2.1.0-r2. Sorry for that!</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>hollow@gentoo.org</who>
            <bug_when>2006-04-21 00:04:20 0000</bug_when>
            <thetext>beside that bme was not in 2.0.1 (but in 2.0-r1) i have added 2.0.1-r3 to the tree with bme included.. it seems we forgot to carry bme arround in 2.0.1 since it is included in 2.0.2 and 2.1* already..

anyway, in cvs, fixed, thanks.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>