Many improvements for sfs loading scripts
The deb package looks fine to me.fredx181 wrote:Here's .deb package for portablesfs (thoroughly tested this time, )
I think I did the packaging right but it's not easy these days with the new "rules" (for gsu/gksu))
It is better to have the same scripts in both versions when it is possible. I will rename the old one and keep it in case I find some problem with the new loadmodule in DD-Jwm.Attached loadmodule_loadsfs.tar.gz:
Includes:
. New 'loadmodule' script, fixes:
- When (sometimes) a module fails to unload, added forcing unmount (in case it doesn't normally)
- Added workaround for OpenBox version to show the application in the menu after loading.
Toni, I found that on Jwm version there's no problem at all so you can keep the older version if you want.
We can add second icon on the desktop for loadsfs-fuse named SFSdrop-chroot or think of some way to create it from debdog-full-install script, or we can just add the information how to change the path for SFSdrop icon for full install in Howto thread.Script "loadsfs"
It is using the default "Sfs-load mode" and I think this will be best to use for the SFSdrop icon on the Desktop.
Disadvantage is that it doesn't work with full install.
Advantage is that it doesn't need unionfs-fuse package
loadsfs-fuse can also be used, I'm not sure yet what's best.
My opinion is to keep loadsfs for SFSdrop icon as default for frugall install.
I thought it is permissions problem for sudo or sudoers in /mnt/unionfs... folder but it is not. I will also try to find fix for this.Edit: Small disadvantage for portablesfs "Chroot mode", loadsfs-fuse and loadsfs-fuse-writesfs:
When using it when logged in with normal user account, sudo and su doesn't work (when running Xterm from "Applications" menu and trying to use sudo or su). Can't figure out why.
Edit: From root account typing sudo in Applications -> xterm gives correct output. The problem is for user account.
Edit 2: Just found something related here:
http://askubuntu.com/questions/299878/e ... environmet
According to this post the problem could be in nosuid but it does not give real solution:
Code: Select all
puppy@debian:~$ mount
.....................
unionfs-fuse on /mnt/unionsfs_13204 type fuse.unionfs-fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
Code: Select all
#!/bin/bash
loadsfs-fuse "$@"
Edit 4: About sudo problem I can use sudo from user account by starting xterm with click on /.unionfs/Xterm.desktop or /mnt/unionsfs_20128/usr/bin/xterm
The problem is only when starting xterm with double click from Applications yad window.
Toni