On Sunday 09 January 2005 17:42, Matthias Meyer wrote: > Matthias Meyer wrote: > > Blaisorblade wrote: > >> Almost certainly you just need to setup samba to allow write access to > >> that share... maybe you have "security=host" in your smb.conf (if that > >> value for "security" exists). > > > > This some values out of my smb.conf > > map to guest = Bad User > > encrypt passwords = Yes > > keepalive = 60 > > wins support = Yes > > unix password sync = Yes > > local master = Yes > > security = user > > > >> Notice that, if you want to setup authentication (the alternative is > >> enabling guest access read/write, with : > >> > >> guest ok = yes > >> writable = no > > > > and some other values out of my smb.conf > > [Video] > > writeable = yes > > public = yes > > guest ok = Yes > > read only = No > > path = /Video > > > >> ), either you set the lan hosts to use unencrypted passwords (because > >> when receiving the Win hash it can't check it against the Unix hash), or > >> you set an indipendent Samba password for each user you want to enable > >> (as I did, having only 1 user) with smbpasswd, or you use winbind to > >> make your Unix account fetch passwords from the Samba database (or even > >> you create a Windows 2000 domain with Samba 3 and LDAP). > > > > I have no problems with encrypted passwords between Windows and Samba. My > > Samba-Server can provide any directory for read/write access but not the > > hostfs-directory. > > Maybee it help to know: > # cat /proc/filesystems > nodev rootfs > nodev bdev > nodev proc > nodev sockfs > nodev tmpfs > nodev shm > nodev pipefs > nodev binfmt_misc > ext3 > ext2 > nodev ramfs > nodev devfs > nodev devpts > nodev hostfs > > Is it possible that the "nodev hostfs" entry restricted samba to provide > this share only for readonly? Uh? I hope not.... I don't see any reason for that. Try creating a tmpfs mount inside the share to verify your idea.
Instead, it is more likely something strange is acting with permissions... hostfs is not nice when it comes to handling permissions. Let's say file A is owned by user U on the host (U is the numerical UID) - that is what is seen inside UML. The best thing to do is to have everything owned by the user running UML. But DO NOT run UML as root, that means giving free root access to your box! In short, verify the user that Samba is using to access the share actually succeeds in using it... -- Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 http://www.user-mode-linux.org/~blaisorblade ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
