a chroot is like booting into that folder
so files are generated the same as a frugal install

but a new root allows you to install and remove files without booting into the folder so no personalized configurations based on your hardware are generated

I had to write that code the formatting of pet packages
how they are registered in woof are very different so all my work on this is for pre woof versions of puppy ( I have no plans to modify the code for the new package format )

I also use package tools (slackwares package management)

Quote:

do I run your script within the chroot'ed environment, or outside

after you chrooted into the folder you run the script I posted above
and the new display for number for X puppy will let you use startx instead of xwin so you dont need to change that

i've been pokiing around trying to find a way to run
puppy inside another linux, mintppc, running on a debian
base on a power pc. so the field of emulators/virtualisers
is drastically reduced. i had found chroot , which seemed
potentially useful.

yr reply to the poster gives me hope, big bass, because
i do not know the code to see if i could get puppy running
with chroot.

this is a very advanced way of test building so it it mostly used for a development stage
to boot into a chroot
so you have to understand a quite few things before getting started

1.)if you are booting from another linux distros kernel
you will have different modules loaded before switching into the new root

in a nut shell this is for pre testing ideas before hand
doing this booting slackware with a slackware chroot is much easier
doing this booting puppy and then a puppy chroot is much easier
*I can say that with confidence because I tried it the hard way of having a different kernel and modules
it can be done but it gets much more complex quickly (slaxer pup came from much testing )
so if this sounds interesting to you do the easy way first
to get a feel for what is happening

2.)if you are booting from another distro you have to have squashfs compiled in if you want to mount
sfs but it is not needed if you first decompress the filing system into a folder

3.)since you are in a chroot the display number has to be increased from 0 to 1

this is in no way a complete how to because I always have to tweak many things to get the full
system running

anyway thanks for posting
I hope this clears up some questions
you will have to invest a lot of time

i tried qemu, too slow to be useful.
i just wanted to see if i could get a puppy running on a powerpc
and because a port is going slowly for much more informed users
than myself i found a nice linux for powerpc, mintppc.

it's debian based. in the mintppc forum one of their moderators wondered
if anyone had tried running puppy in qemu. that was how i started.
then i found that very few emulators/virtualiser would encompass
a host ppc/linux guest pc/linux setup

i got so far as installing schroot which looked as though it might
make things easier. i have the time to invest and the target compu
is a 'spare' with internet. it's a g4, big old thing with built in handles,
runs in utter silence -disconnected the fans-

in fact i'm not sure that chroot on linux on a powerpc will run a
linux/pc distro like puppy? just thought of that.

a suggestion would be to rebuild mintppc lighter
using packages this will save you tons of time
when you decide to upgrade and it will be much more organized
when you search for info using a debian base

you could then build packages on your already running system
as far as what is or what isnt puppy on a ppc
there is no attempt to standardize anything
to be linux compatible on one

the best way would be a small light mintppc full install
then pick only the best smallest apps you need

I tried setting some variables, like PATH, LD_LIBRARY_PATH, PKG_CONFIG_PATH, LANG, and a few others but nothing made a difference.

You should just source /etc/profile (assuming bash isn't doing it itself).
This way some, hmm, esoteric things like USER will be set.

Whenever I update my sfs I use chroot for running indexgen.sh and fixmenus and they work fine. For running any serious programs you'll want to do what Joe suggested, 'though what you really want is to run /etc/rc.d/rc.sysinit but without all the module loading... there's all kinds of stuff like setting the hostname etc._________________What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum