Re: how to: chroot 32bit (forgot one thing)

2005-03-30 Thread Erik Norman
Hi again,

I forgot one question:

You also need a link to your 32bit linker in the /lib path. Change in
to directory /lib and create a link to the 32bit linker library of your
chroot: (The name of the 64bit linker is ld-linux-x86-64.so.2)

According to the instructions I entered the chroot. Do I have to exit
the chroot, or not? 
Why not write down the complete command, so newbies (like me) can just
copy and paste the command?

Thanx, Erik



On Mit, 2005-03-30 at 10:30 +0200, Erik Norman wrote:
 Hello,
 
 I wanted to point out that I had (still have) some problems to
 UNDERSTAND the how to-instructions to set up a chroot-environment for
 the 32bit applications.
 
 There is the possibility of mounting it.
 Which instructions should be left out, if I don't want have it
 mounted? 
 
 Why not add a valid /etc/sources.list for the 32bit applications? (Just
 to start easily; who then knows better can always use a better one)
 For example, I could not find the package libx11-6.
 
 
 The command chroot /var/chroot/sid-ia32 is twice on that page.
 Didn't I already chroot? Is it needed twice? 
 
 Erik
 
 
 
 
 
 
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: how to: chroot 32bit (forgot one thing)

2005-03-30 Thread Inoad Dreamer
Hi Erik,
you are talking about mounting the chroot. i think that you are talking 
about the point where it is explained how to mount some partions like 
/home INTO the chroot - this ist necessary.
Because without this mounts you wouldn't be able to save date in your 
home dir because it isn't available in the chroot.

here is my sources.list i use in my chroot:
deb ftp://ftp.de.debian.org/debian sarge main contrib non-free
for most things this ist enough.
(maybe you find a better one for your country, because this one contains 
the german server)

every time when you type chroot  /var/chroot/sid-ia32 you chang into 
your chroot. by typing exit you will be back at your original session.

If you now have forgotten some options just exit from the chroot, do 
what you have to do and than type again: chroot  /var/chroot/sid-ia32

cu Inoad
---
sorry for my bad english
Hi again,
I forgot one question:
You also need a link to your 32bit linker in the /lib path. Change in
to directory /lib and create a link to the 32bit linker library of your
chroot: (The name of the 64bit linker is ld-linux-x86-64.so.2)
According to the instructions I entered the chroot. Do I have to exit
the chroot, or not? 
Why not write down the complete command, so newbies (like me) can just
copy and paste the command?

Thanx, Erik

On Mit, 2005-03-30 at 10:30 +0200, Erik Norman wrote:
 

Hello,
I wanted to point out that I had (still have) some problems to
UNDERSTAND the how to-instructions to set up a chroot-environment for
the 32bit applications.
There is the possibility of mounting it.
Which instructions should be left out, if I don't want have it
mounted? 

Why not add a valid /etc/sources.list for the 32bit applications? (Just
to start easily; who then knows better can always use a better one)
For example, I could not find the package libx11-6.
The command chroot /var/chroot/sid-ia32 is twice on that page.
Didn't I already chroot? Is it needed twice? 

Erik



   


 


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Re: how to: chroot 32bit (forgot one thing)

2005-03-30 Thread Dr Gavin Seddon
Hi,
Would it not be advantagious to add a 32bit sources.list similar to that
in the howto for 64bit.  Also, I found it easier to add 
alias 32bit 'dchroot -c ia32 -d'
to my .cshrc to make things easier.  Since I need to run various 32 bit
apps in terminals, it gives me 'freedom'.  Would a command like this for
csh and bash not be useful in the howto?  Or, would 'people' just
complain iff they had 'other' shells?
Gavin.



On Wed, 2005-03-30 at 12:40 +0200, Inoad Dreamer wrote:
 Hi Erik,
 
 you are talking about mounting the chroot. i think that you are talking 
 about the point where it is explained how to mount some partions like 
 /home INTO the chroot - this ist necessary.
 Because without this mounts you wouldn't be able to save date in your 
 home dir because it isn't available in the chroot.
 
 here is my sources.list i use in my chroot:
 
 deb ftp://ftp.de.debian.org/debian sarge main contrib non-free
 
 for most things this ist enough.
 (maybe you find a better one for your country, because this one contains 
 the german server)
 
 every time when you type chroot  /var/chroot/sid-ia32 you chang into 
 your chroot. by typing exit you will be back at your original session.
 
 If you now have forgotten some options just exit from the chroot, do 
 what you have to do and than type again: chroot  /var/chroot/sid-ia32
 
 cu Inoad
 
 ---
 sorry for my bad english
 
 Hi again,
 
 I forgot one question:
 
 You also need a link to your 32bit linker in the /lib path. Change in
 to directory /lib and create a link to the 32bit linker library of your
 chroot: (The name of the 64bit linker is ld-linux-x86-64.so.2)
 
 According to the instructions I entered the chroot. Do I have to exit
 the chroot, or not? 
 Why not write down the complete command, so newbies (like me) can just
 copy and paste the command?
 
 Thanx, Erik
 
 
 
 On Mit, 2005-03-30 at 10:30 +0200, Erik Norman wrote:
   
 
 Hello,
 
 I wanted to point out that I had (still have) some problems to
 UNDERSTAND the how to-instructions to set up a chroot-environment for
 the 32bit applications.
 
 There is the possibility of mounting it.
 Which instructions should be left out, if I don't want have it
 mounted? 
 
 Why not add a valid /etc/sources.list for the 32bit applications? (Just
 to start easily; who then knows better can always use a better one)
 For example, I could not find the package libx11-6.
 
 
 The command chroot /var/chroot/sid-ia32 is twice on that page.
 Didn't I already chroot? Is it needed twice? 
 
 Erik
 
 
 
 
 
 
 
 
 
 
 
   
 
 
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]