What is this line ?

@moulefrite
Could you pls. give some more details on how you chroot ?

Hi

I've just read that chrooting implies that you are not allowed to go downwards :
e.g : if one chroot in /home/slitaz/chroot , not possible to reach /home/slitaz

In the code I see /dev/null: Permission denied  ..  anything related with ?
..

@OldGuy

Just as described in handbook in 3 commands

http://doc.slitaz.org/fr:guides:chroot

I just went through the 3 steps
   tazpkg get-install slitaz-dev-tools
   tazdev gen-chroot
   tazdev chroot

Thereafter I installed firefox (tazpkg get-install firefox) within the chroot environment without any problems in regards to /dev/null.

There are a few strange things I noticed:
When the 3 steps are used under Slitaz stable core, the flavor of the chroot environment is cooking (as described in the tazdev usage - gen-chroot  Generate a chroot using the last cooking base rootfs) and if I then search for the firefox package (tazpkg search firefox) I'll get version 3.6.13 out of the cooking tree.

You install firefox 3.5.7 which is part of the stable tree.

Are you sure you're within the chroot environment?


Nevertheless, your chroot environment should have a /dev/ directory with a device 'null'
What does 'ls -l /dev/nu*' give you when you're in the chroot env. ?

You are right !

I've change tazpkg parameter (change the mirror to target towards stable packages) . But, as you pointed it out,

tazdev typically  download the tiny slitaz core . How can I change paramaters the way it downloads a classical

Slitaz 3.0 Xvesa to build the chroot environment ?

 

Beside this, you are OK to say that it's impossible to make any tazpkg link's through the chroot to reach any partition and/or device . Right ?

I'm not sure about how to change the chroot env. to anything different.
I think you're right, it should be a parameter to tazdev, as tazdev creates the env. (tazdev gen-chroot)

About the devices and links.
You should be able to mount any device/partition in the chroot as you could in the normal environment.

Nevertheless, the error you get indicates a problem with /dev/null.
Therefore it would be good to see the output of 'ls -l /dev/nu*' within the chroot env.

In fact , tazdev can be easily editable in /usr/bin . So you can set a chroot by downloading any Slitaz .

I used to chroot quite often to devices which I didn't boot from (especially to fix GRUB issues) but I never experienced any trouble doing so.

Ok,

Sorry,

 first you said you used the way described in the handbook,
than you mentioned on the side that you modified tazpkg to 'targettowards stable' and
now I'm wondering what you have done to get tazdev to create the chroot on a usb-(stick?)

I've tried the standard way and it worked!

If you want help with your problem you got to explain, in detail and step by step, what you've done and how.