View Single Post
pipeline's Avatar
Posts: 693 | Thanked: 502 times | Joined on Jul 2007
#13
Originally Posted by qole View Post
pipeline: I think we should work together to turn my chroot scripts in Easy Debian into a generic ext2 image chroot appliance launcher. You definitely want the latest version of my package, since it has that cool turbo loop stuff in it, and I definitely want to move towards your isorun / ext2run system. I'm thinking of trying out qwerty12's recent zenity package as the GUI frontend.
Yea definately... i had thought about using zenity within the appliances but you're thinking of using it as frontend for managing the chroot? That sounds interesting too.

Basically i have my 'ext2run' command which calls :
- ext2mount
- ext2chroot /autorun.sh $2 $3 $4 $5 $6
- ext2drop (unmount.. important for reuse of mountpoint)

additionally i added an 'alternate' mountpoint for simple side-by-side mount for copying between (useful when authoring the ext2 images)... those are ext2bmount and ext2bdrop

With 'most' of my appliances, a 1-at-a-time restriction for 'running' them is tolerable, but long term it might be neat to have up to... say 4... mountpoints and a rollover capability in script. Chroot apps dont know the difference, but would make for a tricky mount script.


Originally Posted by qole
AHA. I have the solution. I should break apart my Easy Debian package into an easy-chroot package and easy-debian package. The easy-chroot package has a very generic chroot script that is designed to be wrapped by other scripts, and the easy-debian package has the Debian chroot-specific stuff in it, including the Debian image downloader, LXDE window manager, and all of that stuff. Then you (and others) can depend on the easy-chroot package and wrap it in your own scripts... Sounds like a plan?
hmm would you be able to replace my package entirely? if so i wouldn't need to add as a dependency at all I do kind of need the independent mount/run/drop commands and at least 2 mountpoints in order to create the images i make though... after all how i can i rip off more of your debian apps if i cant access the destination ext!

Any thoughts on how easy that would be to integrate into your scripts?

Last edited by pipeline; 2009-01-14 at 00:00.