Chrooted Debian The Other Easier? Way

[pgas]

Sorry, I don't know what the problem is.

can you try

Code: [Select]

mount -o remount,suid,dev /mnt/card
And then startdebian.sh? (I suggest you first reboot you zaurus to be sure that there are no remaining mount point from a previous execution)

remounting like this had fixed a problem I had when I was creating a chroot jail for another program.

I have no clue as why you get the mnt/card/debroot/mnt/card/debroot/proc etc...

Has anybody else tried this method with a C1000 or 3100?, maybe the kernel doesn't allow this? maybe the kernel causes problem?

(If someone wants to donate a new Zaurus: you are welcome )

[apink]

-pgas,  Thank you for your help so far.  It is appreciated.  If you have some time, could you post your output from mount after startdebian.sh so that I know what to aim for?  No worries if you can't get to it.  I am guessing that by doing a "mount -rbind /mnt/card . . ." as a last command, all of the /mnt/card/debroot/yadayada points already mounted get remounted, thus the mnt/card/debroot/mnt/card/debroot/yadayada.  

Also, my output after reboot of mount before running startdebian.sh includes a line of

none on /dev type tmpfs (rw)

Could it be that devfs was replaced with tmpfs for the C1000?

[pgas]

after a second look at your list of mount points:

try to mount

 /dev/pts on /mnt/card/debroot/dev/devpts

[apink]

after a second look at your list of mount points:

try to mount

 /dev/pts on /mnt/card/debroot/dev/devpts
[div align=\"right\"][a href=\"index.php?act=findpost&pid=108197\"][{POST_SNAPBACK}][/a][/div]

Yes,

mount --bind /dev/pts ${DEBROOT}/dev/pts

worked.

I now have Crd aterm creating a new terminal with debian running.  Thank you.  

I am still a little unclear about what to do about the

mount --rbind /mnt/card ${DEBROOT}/mnt/card

line at the end of your script.  Right now I have changed --rbind to just --bind and that seems to work.

[pgas]

line at the end of your script. Right now I have changed --rbind to just --bind and that seems to work.

I read again the man page of mount, I must have read it too quickly the first time:

This call attaches only (part of) a  single  filesystem,  not  possible
       submounts.  The entire file hierarchy including submounts is attached a
       second place using
              mount --rbind olddir newdir

So rbind does the what you see, and bind should be used and rbind does not seems
 to work as expected on the 860.

Thanks for beeing patient , I'll try to update the scripts

[smuelas]

line at the end of your script. Right now I have changed --rbind to just --bind and that seems to work.

I read again the man page of mount, I must have read it too quickly the first time:

This call attaches only (part of) a  single  filesystem,  not  possible
       submounts.  The entire file hierarchy including submounts is attached a
       second place using
              mount --rbind olddir newdir

So rbind does the what you see, and bind should be used and rbind does not seems
 to work as expected on the 860.

Thanks for beeing patient , I'll try to update the scripts
[div align=\"right\"][a href=\"index.php?act=findpost&pid=108312\"][{POST_SNAPBACK}][/a][/div]

After a few days of testing different possibilities for mounting/unmounting Debian on pdaxrom, and for the specific problems created on the SL-6000, it is now clear the picture: Everything runs perfectly well if using an SD card. The problems arise with the microdrive that I have on the CF slot. And those are, as you suspected, the mounting/unmounting of /mnt/cf when suspending and resuming.
This is the "only" problem that I've found on the 6000. In a normal session, without using Suspend, everything works fine.
Now, what I do is to unmount /mnt/cf before suspending. For "Suspend" I don't need to click the button. I just use the ON/OFF key on the 6000, as in the original ROM. Another way is to include the unmounting of /mnt/cf on the Suspend icon, and this simplifies the process.
Nevertheless, there is still a "remaining" problem, referring to your scripts for Debian. And it is the fact that usually "stopdebian.sh" is not able to finish the whole process. More specifically, the "tmp" and "dev" mounted, produce a message of "/mnt/cf busy" and the final unmounting of /mnt/cf is impossible, what makes the solution above mentioned, useless.
Would it be any way of forcing unmounting of those two and include them in "stopdebian.sh"??

smuelas