On 9/7/06, Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
Seb <[EMAIL PROTECTED]> writes:
> Another question that nobody seems to mention in the various how-tos is
> what happens if you have say both the same 64-bit app in the main system
> and 32-bit app in the chroot? Because /home is mounte
[EMAIL PROTECTED] writes:
> On Thu, Sep 07, 2006 at 09:27:08AM +0200, Goswin von Brederlow wrote:
>>
>> My suggestion is: Don't do it. If you need the 32bit version for
>> something then use it for everything. The benefit of 64bit is generaly
>> negible anyway. No point in having say a 64bit and
On Thu, Sep 07, 2006 at 09:27:08AM +0200, Goswin von Brederlow wrote:
>
> My suggestion is: Don't do it. If you need the 32bit version for
> something then use it for everything. The benefit of 64bit is generaly
> negible anyway. No point in having say a 64bit and 32bit mozilla.
Well, there's a r
Martin Jambor wrote:
On 9/6/06, Seb <[EMAIL PROTECTED]> wrote:
I'm in the same situation with Firefox as you are, but do not see the
extension compatibility wizard kicking in. The danger I see is the
64-bit
and 32-bit versions modifying ~/.mozilla differently, which may mess the
files up at s
On Thu, 07 Sep 2006 09:27:08 +0200,
Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
[...]
> It isn't.
> Even worse is when the 32bit and 64bit ~/.application file are
> incompatible. One should consider that a bug but it has happened.
> My suggestion is: Don't do it. If you need the 32bit versi
"Martin Jambor" <[EMAIL PROTECTED]> writes:
> On 9/6/06, Seb <[EMAIL PROTECTED]> wrote:
>> I'm in the same situation with Firefox as you are, but do not see the
>> extension compatibility wizard kicking in. The danger I see is the 64-bit
>> and 32-bit versions modifying ~/.mozilla differently, wh
On 9/6/06, Seb <[EMAIL PROTECTED]> wrote:
I'm in the same situation with Firefox as you are, but do not see the
extension compatibility wizard kicking in. The danger I see is the 64-bit
and 32-bit versions modifying ~/.mozilla differently, which may mess the
files up at some point.
As far as
Seb <[EMAIL PROTECTED]> writes:
> Another question that nobody seems to mention in the various how-tos is
> what happens if you have say both the same 64-bit app in the main system
> and 32-bit app in the chroot? Because /home is mounted in both systems,
> each version will be messing with each o
On Wed, 06 Sep 2006 15:25:21 -0500,
Owen Heisler <[EMAIL PROTECTED]> wrote:
> On Wed, 2006-09-06 at 13:45 -0500, Seb wrote:
[...]
> Installed firefox, mplayer, w32codecs, realplayer (last 3 from
> Marillat's repos). I haven't tested mplayer yet, but realplayer has quite
> jumpy video (not smoot
On Wed, 2006-09-06 at 13:45 -0500, Seb wrote:
> On Mon, 04 Sep 2006 23:38:41 -0500, Owen Heisler wrote:
> > In that HOWTO, _I_ would skip 1.3, 1.4, and 1.5. The only changes I
> > make to the real system is to /etc/fstab.
>
> Yes, this is what I really felt like doing, since I had the ia32-libs
>
On Mon, 04 Sep 2006 23:38:41 -0500,
Owen Heisler <[EMAIL PROTECTED]> wrote:
[...]
> In that HOWTO, _I_ would skip 1.3, 1.4, and 1.5. The only changes I
> make to the real system is to /etc/fstab.
Yes, this is what I really felt like doing, since I had the ia32-libs
package. So I went ahead and
Seb <[EMAIL PROTECTED]> writes:
> Hi,
>
> I'm trying to create a chroot in a AMD64 Debian system, following a how-to
> posted from http://www.debian-administration.org/articles/356. However,
> I'm not comfortable messing with my main system config files (like
> /et/ld.so.conf), which the how-to s
On Tue, 2006-09-05 at 11:32 -0500, Seb wrote:
> On Tue, 05 Sep 2006 09:08:02 -0500, Owen Heisler wrote:
> > I use schroot to run stuff in the chroot. Just "schroot -p ",
> > unless you have multiple chroots, then add the -c option. It works
> > nicely.
>
> I wasn't aware of schroot, but followed
On Tue, 05 Sep 2006 09:08:02 -0500,
Owen Heisler <[EMAIL PROTECTED]> wrote:
[...]
> I'm not sure about that. I just wanted to make as few changes as
> possible to my system (/var/chroot/* & /etc/fstab).
Same here!
> I use schroot to run stuff in the chroot. Just "schroot -p ",
> unless you h
On Tue, 2006-09-05 at 07:52 -0500, Seb wrote:
> On Mon, 04 Sep 2006 23:38:41 -0500, Owen Heisler wrote:
> > On Mon, 2006-09-04 at 14:34 -0500, Seb wrote:
> >> I'm trying to create a chroot in a AMD64 Debian system, following a
> >> how-to posted from http://www.debian-administration.org/articles/35
Thanks for these pointers.
On Mon, 04 Sep 2006 23:38:41 -0500,
Owen Heisler <[EMAIL PROTECTED]> wrote:
> On Mon, 2006-09-04 at 14:34 -0500, Seb wrote:
>> I'm trying to create a chroot in a AMD64 Debian system, following a
>> how-to posted from http://www.debian-administration.org/articles/356.
>
On Mon, 2006-09-04 at 14:34 -0500, Seb wrote:
> I'm trying to create a chroot in a AMD64 Debian system, following a how-to
> posted from http://www.debian-administration.org/articles/356. However,
> I'm not comfortable messing with my main system config files (like
> /et/ld.so.conf), which the how
Hi,
I'm trying to create a chroot in a AMD64 Debian system, following a how-to
posted from http://www.debian-administration.org/articles/356. However,
I'm not comfortable messing with my main system config files (like
/et/ld.so.conf), which the how-to suggests. For other reasons, I also had
the
18 matches
Mail list logo
