(old)Puppy Linux Discussion Forum

@sheldonisaac: And thank you for all your testing. Yours is one of the worst-case scenarios, so I am happy that we have resolved it.

I think that I will leave v1.3 alone for now. I will put a note in the how-to warning Win9X users that the share and server names are case-sensitive.

Bill

YASSM v1.5 is now available above. It has a new feature for hiding passwords in the samba-select share database.

There may be rare situations where samba-login cannot locate a share by its name. But the share should still be mountable using the option ip=aaa.bbb.ccc.ddd.

I am still looking for people who can test YASSM with Vista or Win7 shares.

Thanks.

Tested samba-login of YASSM-1.5.pet.

• Windows 7, Users
• Windows Xp, SharedDocs

Both set up open for public, everyone required no password.
Both successfully mounted without username, pasword nor Options.
I only input Server name and Share name.
Test performed on Lupu-517.

shinobar wrote:Tested samba-login of YASSM-1.5.pet.

• Windows 7, Users
• Windows Xp, SharedDocs

Both set up open for public, everyone required no password.
Both successfully mounted without username, pasword nor Options.
I only input Server name and Share name.
Test performed on Lupu-517.

Tested a textfile with Japanese file name on Windows Xp.
It is shown in the Rox-Filer after mounting with samba-login of YASSM-1.5.pet.
But it cannot copy to the local disk, 'ERROR: No such file or directory'.
This does not occur with pnethood.

shinobar wrote:Tested a textfile with Japanese file name on Windows Xp.
It is shown in the Rox-Filer after mounting with samba-login of YASSM-1.5.pet.
But it cannot copy to the local disk, 'ERROR: No such file or directory'. :(
This does not occur with pnethood.

Did you include the option iocharset=utf8?

rcrsn51 wrote:

shinobar wrote:Tested a textfile with Japanese file name on Windows Xp.
It is shown in the Rox-Filer after mounting with samba-login of YASSM-1.5.pet.
But it cannot copy to the local disk, 'ERROR: No such file or directory'.
This does not occur with pnethood.

Did you include the option iocharset=utf8?

Tried the option iocharset=utf8, but seems ignored.
I am now on LupQ-511 + lang_pack_cjk, so pnethood mount shows japanese file names correctly(they are not windows now but samba on Vine linux box).
But the samba-login of YASSM-1.5.pet with or without iocharset=utf8 option, they are all showing '??' and cannot access.

EDIT: It was my fault. The ROX-Filer needed 'refresh'.
No problem found with iocharset=utf8 option

shinobar, is your LOCALE set to enable utf8? I found out that even with iocharset=utf8, if your locale not set to utf8, then winxp shared folders with unicode filenames will not properly. In my case, I had to ensure that my LANG setting is en_AU.utf8 instead of just en_AU.

jamesbond wrote:shinobar, is your LOCALE set to enable utf8?

Thanks. Yes, i am shure with utf8( really, UTF-8 ).
LupQ-511 + lang_pack_cjk, so pnethood mount shows japanese file names correctly.

BTW, Samba on my remote Linux box and Windows share can be different.
I may need another test with Windows...

Sorry, the ROX-Filer needed to refresh.
No problem with Japanese file names if i add iocharset=utf8 option.
Local: LupQ-511 + lang_pack_cjk
Remote: Both Samba on Linux, Windows Xp

Hope iocharset=utf8 option as the default.
Pnethood has iocharset=utf8 option for years and seems harmless.

shinobar wrote:No problem with Japanese file names if i add iocharset=utf8 option.

Excellent. Thank you for testing this.

This is a wonderful little pet. It works perfectly on my Windows XP LAN.

Can anyone tell me if it is possible to use Samba to share files between machines running puppy? I use ftp for this now, but this is much more limited than actually mounting the remote drive.

drblock2 wrote:Can anyone tell me if it is possible to use Samba to share files between machines running puppy? I use ftp for this now, but this is much more limited than actually mounting the remote drive.

You need to install a Samba server package on one of your Puppies. My favourite is Samba-TNG.

Out of curiosity, does your Windows LAN use simple file sharing with open shares or the more complicated version with password security?

My Windows LAN uses simple file sharing with open shares.

One interesting observation. If I mount via samba share select, the path to the mounted file system goes via /root/samba. If I mount with pnethood, the path is direct, e.g., /mnt/network/host/share, whereas the samba share select mount has the path /root/Samba/share. This is somewhat inconvenient as the user has to keep this "small detour" in mind when accessing the share with the command line or a file manager.

This should, perhaps, be mentioned in the instructions.

Thanks for the link to Samba-TNG. I will experiment with this asap. This is, I think, very important. It is one thing to maintain compatibility with Windows because we have to deal with Windows computers and quite another to have to rely on ftp because there is no other way for puppy computers to talk to one another.

One interesting observation. If I mount via samba share select, the path to the mounted file system goes via /root/samba. If I mount with pnethood, the path is direct, e.g., /mnt/network/host/share, whereas the samba share select mount has the path /root/Samba/share. This is somewhat inconvenient as the user has to keep this "small detour" in mind when accessing the share with the command line or a file manager.

This should, perhaps, be mentioned in the instructions.

It is:

Samba-login uses the folder /root/Samba to hold the mount points.

This was a matter of personal preference on my part. If, when using pnethood, I close the share window, I then have to drill all the way down into /mnt/network to open it again. It seemed much simpler to put the mount points in /root. Most applications start their File>Open dialog there.

Is there a way to auto mount the shares at boot ?
Thanks for any response.
Love puppy linux!

Deleted.

I can't download the pet. Is the download link still valid?

It's hosted locally on the forum, so, yes, the link should still be valid. However, there's currently an issue or two with the forum (you may have noticed 'garbage' appearing at the top of a page or two, for example), that appears to be interfering with things like the post attachment above. Hopefully, it'll all be sorted, soon.

It also works fine on Fatdog64, thanks

sebus

YASSM v2.2 is posted on Page 1.