[prev in list] [next in list] [prev in thread] [next in thread] 

List:       klik-devel
Subject:    Re: [klik-devel] klik-devel Digest, Vol 11, Issue 1
From:       lionel.tricon () free ! fr
Date:       2006-12-20 22:50:57
Message-ID: 20061220235057.7tkebji9csgc8wwg () imp4 ! free ! fr
[Download RAW message or body]

Quoting Jason Taylor <killerkiwi2005@gmail.com>:
> Awesome work!

Well, for the moment, i succeed to chroot a fuse filesystem if :
- i use the 2.6.1 version of fuse (you need to create an  
/etc/fuse.conf file with the user_allow_other sentence inside in order  
to use the allow_root option from the fuseiso command line)
- i patch slightly the fusermount utility to allow options suid and dev
- i changed right permission of chroot and fusermount to 4755

The last (and very annoying) issue is that, up to now, it's seems  
impossible to use special devices (remember that my own version of  
fuseiso merge data from the real root filesystem and data from the  
fuseiso file, and so present file from /dev) ... if someone have an  
idea ...

bash-3.1$ echo "toto" > /dev/null
bash: /dev/null: Permission denied

But if i use the "mount --bind" feature to mount /dev and /tmp into  
the fuse filesystem, all is working correctly ... (/dev and x11  
applications ...)

> Feature request if your hacking, being able to specify a mount
> offset would be great :)

I think it's a feature that need to be added directly into the fuse  
filesystem ...

But there is a trivial hack :
- use the losetup utility to mount the file with the help of the  
"offset" option
- call fuseiso/fusecram by using the /dev/loopX device instead of the file

Not terrible but it's better than nothing ...

Lionel
_______________________________________________
klik-devel mailing list
klik-devel@kde.org
https://mail.kde.org/mailman/listinfo/klik-devel
[prev in list] [next in list] [prev in thread] [next in thread]