diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20121031')
20 files changed, 120 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20121031/1c0f4c47/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121031/1c0f4c47/attachment-0001.asc new file mode 100644 index 000000000..59c7fe250 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/1c0f4c47/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.12 (GNU/Linux) + +iEYEARECAAYFAlCRk3sACgkQMYWkoYueEqvvMACeOb6iCWZIiQ8T/PVI68KyYyzZ +pugAoIaqnc1aCbtk9yOVRkaU/YvTyr9D +=yWLy +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121031/1c0f4c47/attachment.asc b/zarb-ml/mageia-dev/attachments/20121031/1c0f4c47/attachment.asc new file mode 100644 index 000000000..59c7fe250 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/1c0f4c47/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.12 (GNU/Linux) + +iEYEARECAAYFAlCRk3sACgkQMYWkoYueEqvvMACeOb6iCWZIiQ8T/PVI68KyYyzZ +pugAoIaqnc1aCbtk9yOVRkaU/YvTyr9D +=yWLy +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121031/37ad18fe/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121031/37ad18fe/attachment-0001.html new file mode 100644 index 000000000..0f91d29d2 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/37ad18fe/attachment-0001.html @@ -0,0 +1 @@ +<div><div>Yes i know it uses hardlink, what i mean what advantages do you see by changing to bind mount.  </div><div><br/></div><div><br/></div><div>I mean if it works, why shall we fix it?</div><div><font style="color:#333333">Enviado desde mi DROID 4G LTE de Verizon Wireless</font></div></div><br><br>Olav Vitters <olav@vitters.nl> escribió:<br><br>On Wed, Oct 31, 2012 at 05:59:12AM -0600, Luis Daniel Lucio Quiroz wrote:<br>> Please explain me why you want to change the current bind mount of<br>> sasl for postfix? What you propose?<br><br>If you read the thread you'll notice that Colin said it uses hard link<br>and that I suggested bind mounts. If it is already using bind mounts<br>instead of hard links, cool.<br><br>-- <br>Regards,<br>Olav<br>Email Shield provided by NOCWorldWide.com<br>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20121031/37ad18fe/attachment.html b/zarb-ml/mageia-dev/attachments/20121031/37ad18fe/attachment.html new file mode 100644 index 000000000..0f91d29d2 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/37ad18fe/attachment.html @@ -0,0 +1 @@ +<div><div>Yes i know it uses hardlink, what i mean what advantages do you see by changing to bind mount.  </div><div><br/></div><div><br/></div><div>I mean if it works, why shall we fix it?</div><div><font style="color:#333333">Enviado desde mi DROID 4G LTE de Verizon Wireless</font></div></div><br><br>Olav Vitters <olav@vitters.nl> escribió:<br><br>On Wed, Oct 31, 2012 at 05:59:12AM -0600, Luis Daniel Lucio Quiroz wrote:<br>> Please explain me why you want to change the current bind mount of<br>> sasl for postfix? What you propose?<br><br>If you read the thread you'll notice that Colin said it uses hard link<br>and that I suggested bind mounts. If it is already using bind mounts<br>instead of hard links, cool.<br><br>-- <br>Regards,<br>Olav<br>Email Shield provided by NOCWorldWide.com<br>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20121031/54ea060d/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121031/54ea060d/attachment-0001.html new file mode 100644 index 000000000..503a2daff --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/54ea060d/attachment-0001.html @@ -0,0 +1,7 @@ +Hello,<div><br></div><div>Could somebody remove all ruby 1.9 related packages in core/updates_testing, so that we could land it into core/release.</div><div><br></div><div>The package lists goes (in format of srpm:rpm):</div> +<div><div>ruby-1.9.3.p194-2.mga3.src.rpm:ruby-rake</div><div> ruby-1.9.3.p194-2.mga3.src.rpm:ruby-RubyGems</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-bigdecimal</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-io-console</div> +<div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-json</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-minitest</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-rake</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-rdoc</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:libruby1.9</div> +<div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-devel</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-doc</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-irb</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-tk</div> +<div> ruby-hiera-0.3.0-1.mga3.src.rpm:ruby-hiera</div><div> ruby-hiera-0.3.0-1.mga3.src.rpm:ruby-hiera-doc</div><div> ruby-qt4-4.9.1-2.mga3.src.rpm:libqtruby4shared2</div><div> ruby-qt4-4.9.1-2.mga3.src.rpm:ruby-qt4</div> +<div> ruby-qt4-4.9.1-2.mga3.src.rpm:ruby-qt4-devel</div><div> ruby-RubyGems-1.8.24-4.mga3.src.rpm:ruby-RubyGems</div><div> ruby-rubytree-0.8.3-1.mga3.src.rpm:ruby-rubytree</div><div> ruby-rubytree-0.8.3-1.mga3.src.rpm:ruby-rubytree-doc</div> +<div> weechat-0.3.8-1.mga3.src.rpm:weechat-ruby</div><div> </div></div><div>The reason why I couldn't load it directly into release, is that I introduced unwanted epoch for ruby packages when doing testing.</div> diff --git a/zarb-ml/mageia-dev/attachments/20121031/54ea060d/attachment.html b/zarb-ml/mageia-dev/attachments/20121031/54ea060d/attachment.html new file mode 100644 index 000000000..503a2daff --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/54ea060d/attachment.html @@ -0,0 +1,7 @@ +Hello,<div><br></div><div>Could somebody remove all ruby 1.9 related packages in core/updates_testing, so that we could land it into core/release.</div><div><br></div><div>The package lists goes (in format of srpm:rpm):</div> +<div><div>ruby-1.9.3.p194-2.mga3.src.rpm:ruby-rake</div><div> ruby-1.9.3.p194-2.mga3.src.rpm:ruby-RubyGems</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-bigdecimal</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-io-console</div> +<div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-json</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-minitest</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-rake</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-rdoc</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:libruby1.9</div> +<div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-devel</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-doc</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-irb</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-tk</div> +<div> ruby-hiera-0.3.0-1.mga3.src.rpm:ruby-hiera</div><div> ruby-hiera-0.3.0-1.mga3.src.rpm:ruby-hiera-doc</div><div> ruby-qt4-4.9.1-2.mga3.src.rpm:libqtruby4shared2</div><div> ruby-qt4-4.9.1-2.mga3.src.rpm:ruby-qt4</div> +<div> ruby-qt4-4.9.1-2.mga3.src.rpm:ruby-qt4-devel</div><div> ruby-RubyGems-1.8.24-4.mga3.src.rpm:ruby-RubyGems</div><div> ruby-rubytree-0.8.3-1.mga3.src.rpm:ruby-rubytree</div><div> ruby-rubytree-0.8.3-1.mga3.src.rpm:ruby-rubytree-doc</div> +<div> weechat-0.3.8-1.mga3.src.rpm:weechat-ruby</div><div> </div></div><div>The reason why I couldn't load it directly into release, is that I introduced unwanted epoch for ruby packages when doing testing.</div> diff --git a/zarb-ml/mageia-dev/attachments/20121031/5d520271/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121031/5d520271/attachment-0001.asc new file mode 100644 index 000000000..5e031f728 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/5d520271/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQkav+T1rWTfpocyQRAqMvAJ49cO8BWGZyKLkcj1kunngU+MxYSQCgr/Qg +DdEOYUwS5FzMtnArxCwe5EA= +=hgUD +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121031/5d520271/attachment.asc b/zarb-ml/mageia-dev/attachments/20121031/5d520271/attachment.asc new file mode 100644 index 000000000..5e031f728 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/5d520271/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQkav+T1rWTfpocyQRAqMvAJ49cO8BWGZyKLkcj1kunngU+MxYSQCgr/Qg +DdEOYUwS5FzMtnArxCwe5EA= +=hgUD +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121031/653faf27/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121031/653faf27/attachment-0001.html new file mode 100644 index 000000000..3047109ff --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/653faf27/attachment-0001.html @@ -0,0 +1 @@ +<div><div>Please explain me why you want to change the current bind mount of sasl for postfix?  What you propose?</div><div><br/></div><div><font style="color:#333333">Enviado desde mi DROID 4G LTE de Verizon Wireless</font></div></div><br><br>Olav Vitters <olav@vitters.nl> escribió:<br><br>On Tue, Oct 30, 2012 at 04:55:28PM +0000, Colin Guthrie wrote:<br>> So, what should we do? Should we switch to bind mounts? Should we make<br>> saslauthd/postfix use abstract sockets instead to get around the chroot?<br><br>bind mount for just saslauth seems cleanest to me. Don't bind mount<br>entire /run or /var/run, could impact security of the chroot somehow.<br><br>-- <br>Regards,<br>Olav<br>Email Shield provided by NOCWorldWide.com<br>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20121031/653faf27/attachment.html b/zarb-ml/mageia-dev/attachments/20121031/653faf27/attachment.html new file mode 100644 index 000000000..3047109ff --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/653faf27/attachment.html @@ -0,0 +1 @@ +<div><div>Please explain me why you want to change the current bind mount of sasl for postfix?  What you propose?</div><div><br/></div><div><font style="color:#333333">Enviado desde mi DROID 4G LTE de Verizon Wireless</font></div></div><br><br>Olav Vitters <olav@vitters.nl> escribió:<br><br>On Tue, Oct 30, 2012 at 04:55:28PM +0000, Colin Guthrie wrote:<br>> So, what should we do? Should we switch to bind mounts? Should we make<br>> saslauthd/postfix use abstract sockets instead to get around the chroot?<br><br>bind mount for just saslauth seems cleanest to me. Don't bind mount<br>entire /run or /var/run, could impact security of the chroot somehow.<br><br>-- <br>Regards,<br>Olav<br>Email Shield provided by NOCWorldWide.com<br>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20121031/6fb8250d/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121031/6fb8250d/attachment-0001.html new file mode 100644 index 000000000..bd984e6dd --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/6fb8250d/attachment-0001.html @@ -0,0 +1,15 @@ +ping?<br><div class="gmail_extra"><br><br><div class="gmail_quote">2012/10/31 Funda Wang <span dir="ltr"><<a href="mailto:fundawang@gmail.com" target="_blank">fundawang@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +Hello,<div><br></div><div>Could somebody remove all ruby 1.9 related packages in core/updates_testing, so that we could land it into core/release.</div><div><br></div><div>The package lists goes (in format of srpm:rpm):</div> + +<div><div>ruby-1.9.3.p194-2.mga3.src.rpm:ruby-rake</div><div> ruby-1.9.3.p194-2.mga3.src.rpm:ruby-RubyGems</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-bigdecimal</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-io-console</div> + +<div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-json</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-minitest</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-rake</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-rdoc</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:libruby1.9</div> + +<div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-devel</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-doc</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-irb</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-tk</div> + +<div> ruby-hiera-0.3.0-1.mga3.src.rpm:ruby-hiera</div><div> ruby-hiera-0.3.0-1.mga3.src.rpm:ruby-hiera-doc</div><div> ruby-qt4-4.9.1-2.mga3.src.rpm:libqtruby4shared2</div><div> ruby-qt4-4.9.1-2.mga3.src.rpm:ruby-qt4</div> + +<div> ruby-qt4-4.9.1-2.mga3.src.rpm:ruby-qt4-devel</div><div> ruby-RubyGems-1.8.24-4.mga3.src.rpm:ruby-RubyGems</div><div> ruby-rubytree-0.8.3-1.mga3.src.rpm:ruby-rubytree</div><div> ruby-rubytree-0.8.3-1.mga3.src.rpm:ruby-rubytree-doc</div> + +<div> weechat-0.3.8-1.mga3.src.rpm:weechat-ruby</div><div> </div></div><div>The reason why I couldn't load it directly into release, is that I introduced unwanted epoch for ruby packages when doing testing.</div> +</blockquote></div><br></div> diff --git a/zarb-ml/mageia-dev/attachments/20121031/6fb8250d/attachment.html b/zarb-ml/mageia-dev/attachments/20121031/6fb8250d/attachment.html new file mode 100644 index 000000000..bd984e6dd --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/6fb8250d/attachment.html @@ -0,0 +1,15 @@ +ping?<br><div class="gmail_extra"><br><br><div class="gmail_quote">2012/10/31 Funda Wang <span dir="ltr"><<a href="mailto:fundawang@gmail.com" target="_blank">fundawang@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +Hello,<div><br></div><div>Could somebody remove all ruby 1.9 related packages in core/updates_testing, so that we could land it into core/release.</div><div><br></div><div>The package lists goes (in format of srpm:rpm):</div> + +<div><div>ruby-1.9.3.p194-2.mga3.src.rpm:ruby-rake</div><div> ruby-1.9.3.p194-2.mga3.src.rpm:ruby-RubyGems</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-bigdecimal</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-io-console</div> + +<div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-json</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-minitest</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-rake</div><div> ruby-1.9.3.p194-8.mga3.src.rpm:ruby-rdoc</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:libruby1.9</div> + +<div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-devel</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-doc</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-irb</div><div> ruby-1.9.3.p286-1.mga3.src.rpm:ruby-tk</div> + +<div> ruby-hiera-0.3.0-1.mga3.src.rpm:ruby-hiera</div><div> ruby-hiera-0.3.0-1.mga3.src.rpm:ruby-hiera-doc</div><div> ruby-qt4-4.9.1-2.mga3.src.rpm:libqtruby4shared2</div><div> ruby-qt4-4.9.1-2.mga3.src.rpm:ruby-qt4</div> + +<div> ruby-qt4-4.9.1-2.mga3.src.rpm:ruby-qt4-devel</div><div> ruby-RubyGems-1.8.24-4.mga3.src.rpm:ruby-RubyGems</div><div> ruby-rubytree-0.8.3-1.mga3.src.rpm:ruby-rubytree</div><div> ruby-rubytree-0.8.3-1.mga3.src.rpm:ruby-rubytree-doc</div> + +<div> weechat-0.3.8-1.mga3.src.rpm:weechat-ruby</div><div> </div></div><div>The reason why I couldn't load it directly into release, is that I introduced unwanted epoch for ruby packages when doing testing.</div> +</blockquote></div><br></div> diff --git a/zarb-ml/mageia-dev/attachments/20121031/8ea63eb2/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121031/8ea63eb2/attachment-0001.asc new file mode 100644 index 000000000..9c16ba172 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/8ea63eb2/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.12 (GNU/Linux) + +iEYEARECAAYFAlCR5CkACgkQMYWkoYueEqsG+wCeKDIDDBgghEmZ4g9meMrV1GZO +kaQAoJbGc4bZWc7Mz4cilyLWCS6QCMUB +=NIGS +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121031/8ea63eb2/attachment.asc b/zarb-ml/mageia-dev/attachments/20121031/8ea63eb2/attachment.asc new file mode 100644 index 000000000..9c16ba172 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/8ea63eb2/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.12 (GNU/Linux) + +iEYEARECAAYFAlCR5CkACgkQMYWkoYueEqsG+wCeKDIDDBgghEmZ4g9meMrV1GZO +kaQAoJbGc4bZWc7Mz4cilyLWCS6QCMUB +=NIGS +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121031/9134fad5/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121031/9134fad5/attachment-0001.asc new file mode 100644 index 000000000..e4f566327 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/9134fad5/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQkHmFT1rWTfpocyQRAjagAJ4jaxgDy8uvpXva+du4zDDVzRvwsQCglCFQ +HHMq5JByMnroPp7Rc1NDhv0= +=nwjn +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121031/9134fad5/attachment.asc b/zarb-ml/mageia-dev/attachments/20121031/9134fad5/attachment.asc new file mode 100644 index 000000000..e4f566327 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/9134fad5/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQkHmFT1rWTfpocyQRAjagAJ4jaxgDy8uvpXva+du4zDDVzRvwsQCglCFQ +HHMq5JByMnroPp7Rc1NDhv0= +=nwjn +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121031/cf409adb/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121031/cf409adb/attachment-0001.asc new file mode 100644 index 000000000..0dde7960f --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/cf409adb/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.12 (GNU/Linux) + +iEYEARECAAYFAlCR1psACgkQMYWkoYueEqvFxgCfYVwUeMNGC4iyupnh5QSUepal +/cMAnReSi+N+InNm0PjgAQqduGUA8Cqh +=uyhG +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121031/cf409adb/attachment.asc b/zarb-ml/mageia-dev/attachments/20121031/cf409adb/attachment.asc new file mode 100644 index 000000000..0dde7960f --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/cf409adb/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.12 (GNU/Linux) + +iEYEARECAAYFAlCR1psACgkQMYWkoYueEqvFxgCfYVwUeMNGC4iyupnh5QSUepal +/cMAnReSi+N+InNm0PjgAQqduGUA8Cqh +=uyhG +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121031/f2d9c6e6/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121031/f2d9c6e6/attachment-0001.html new file mode 100644 index 000000000..e7aeea19c --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/f2d9c6e6/attachment-0001.html @@ -0,0 +1 @@ +<div><div>Ok, i will fix it.</div><div><br/></div><div>Driving...</div><div><br/></div><div><font style="color:#333333">Enviado desde mi DROID 4G LTE de Verizon Wireless</font></div></div><br><br>Colin Guthrie <mageia@colin.guthr.ie> escribió:<br><br>'Twas brillig, and Luis Daniel Lucio Quiroz at 31/10/12 12:58 did gyre<br>and gimble:<br>> Yes i know it uses hardlink, what i mean what advantages do you see by<br>> changing to bind mount. <br>> <br>> <br>> I mean if it works, why shall we fix it?<br><br>That's the problem, it doesn't work anymore in cauldron as /var/run is<br>on a different filesystem to /var/spool/postfix/var/run and hardlinks<br>only work within the same filesystem.<br><br>Even the old way would have been broken if /var/lib was mounted<br>separately (although this would be very rare indeed!).<br><br>So as I stated originally, hardlinks simply won't work as a solution any<br>more.<br><br>I was thinking of bind mounting only the individual mux socket.<br><br>It's not ideal, but I can't think of a nicer way.<br><br>Col<br><br><br>-- <br><br>Colin Guthrie<br>colin(at)mageia.org<br>http://colin.guthr.ie/<br><br>Day Job:<br> Tribalogic Limited http://www.tribalogic.net/<br>Open Source:<br> Mageia Contributor http://www.mageia.org/<br> PulseAudio Hacker http://www.pulseaudio.org/<br> Trac Hacker http://trac.edgewall.org/<br>Email Shield provided by NOCWorldWide.com<br>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20121031/f2d9c6e6/attachment.html b/zarb-ml/mageia-dev/attachments/20121031/f2d9c6e6/attachment.html new file mode 100644 index 000000000..e7aeea19c --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121031/f2d9c6e6/attachment.html @@ -0,0 +1 @@ +<div><div>Ok, i will fix it.</div><div><br/></div><div>Driving...</div><div><br/></div><div><font style="color:#333333">Enviado desde mi DROID 4G LTE de Verizon Wireless</font></div></div><br><br>Colin Guthrie <mageia@colin.guthr.ie> escribió:<br><br>'Twas brillig, and Luis Daniel Lucio Quiroz at 31/10/12 12:58 did gyre<br>and gimble:<br>> Yes i know it uses hardlink, what i mean what advantages do you see by<br>> changing to bind mount. <br>> <br>> <br>> I mean if it works, why shall we fix it?<br><br>That's the problem, it doesn't work anymore in cauldron as /var/run is<br>on a different filesystem to /var/spool/postfix/var/run and hardlinks<br>only work within the same filesystem.<br><br>Even the old way would have been broken if /var/lib was mounted<br>separately (although this would be very rare indeed!).<br><br>So as I stated originally, hardlinks simply won't work as a solution any<br>more.<br><br>I was thinking of bind mounting only the individual mux socket.<br><br>It's not ideal, but I can't think of a nicer way.<br><br>Col<br><br><br>-- <br><br>Colin Guthrie<br>colin(at)mageia.org<br>http://colin.guthr.ie/<br><br>Day Job:<br> Tribalogic Limited http://www.tribalogic.net/<br>Open Source:<br> Mageia Contributor http://www.mageia.org/<br> PulseAudio Hacker http://www.pulseaudio.org/<br> Trac Hacker http://trac.edgewall.org/<br>Email Shield provided by NOCWorldWide.com<br>
\ No newline at end of file |