On 13 January 2015 at 14:18, Carlos E. R.
In your case, also check what keeps /isofrom busy (lsof is your friend)
He has placed a bootable iso image into a FAT stick, as file, not dd, and that is what is running. Then he has read/write access to that same FAT filesystem. But it is owned by root and he wants access by plain user.
As it is FAT, directories can not be chowned. And as it is mounted, because the booting and running live is inside, it can not be umounted and mounted again as user.
Yeah, sums things up nicely. So looks like I have four options: - LD_PRELOAD and pass requests for that filesystem to a root-owned process. Way too much coding. - Change the initrd image that actually mounts the file system and reads the ISO. Downside: I have to redo the changes each time I roll a new version of the ISO, as the initrd is extracted from the ISO by live-fat-stick. (Or just use the older initrd for newer versions of the iso, given that I don't actually change kernel-related configuration?) - Repartition the flash drive and install Linux on one partition while using VFAT on the other for general use (with Windows PCs). No longer do ISO. Either do a raw image in susestudio, or forgo opensuse and use debootstrap (I have a Debian workstation). - Forgo plain user access to the FAT32 file system. Instead, create a file on that system and use that as persistent storage witn an ext2 file system in it. When I want to exchange files with Windows systems, just use the root user to copy them to the FAT32 file system I am thinking of taking the last option. It will also allow me to mount the file as /home and, hopefully, to encrypt it (I am going to try including dm-crypt in the ISO). -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org