(old)Puppy Linux Discussion Forum

YASSM has been updated to v2.8. See the notes on page 1.

YASSM has been updated to v2.9. See the notes on page 1. The yassm-select procedure has changed.

Hi,
Thanks a lot.
Have a nice christmas day.
Philippe

It seems that in yassm-select.desktop there is a wrong translation.
There is Name[fr]=YASSM-Recherche de partage Samba like in the yassm-search.desktop file but it's not the same and Name[fr]=YASSM-Sélection de partage Samba will be better, i think.
Philippe

D'accord. I will fix that and post another version.

I have not received any feedback on the new yassm-select procedure. Is it working for you?

I just try with one share and it works fine.
Thanks,
Philippe

Hi,
After i register a share, without the password (i don't like to have a password in clear in a file), the window yassm-login comes to ask the password. Before there was a window but just with the pasword and not all the fields. I have just to write the password but i think that it is better for a user to don't have all these fields even if he just has to complete one field.
Philippe

I never liked the old yassm-select. The instructions were complicated, especially for non-English users. And it was easy to make a mistake when building your database of shares.

The new method is much simpler - just click Set and give the share a title. But when you run yassm-select, you now see two screens - one to select the share and one to login. (It's the same procedure as what you do with yassm-search). In the old yassm-select, you only saw the first screen. That will be a little annoying for users of the old method.

Regarding passwords - in the old method you could hide a share's password by putting ??? in the database. In the new method, you have to enter it in the Password box of yassm-login. But you can insert the password in the share's setup file, which is in the hidden folder /root/.yassm. So you don't have to enter it when you login. It is "sort-of-hidden" from other users.

I will give this problem some thought.

Bill

This alternate version of YASSM-select addresses the issues raised by augras above.

1. It will automatically mount the selected share without going through the YASSM-login screen.

2. If the password in the /root/.yassm/xxx.set file is ***, it will pop-up a password entry box.

3. Your .set files can use server names instead of IP addresses.

Please test and report.

Hi!

Many thx for your scripts. I found them very usefull. BTW dont you think to add iocharset=utf8 while mounting by default? Cause I ve got national coding with ???? in filenames and folder whilist I did not put it into options field. It is OK and easy but it can be a problem for a newbie to figure out what to do

Thanks for the feedback.

Regarding the iocharset option: when I started development of YASSM, I was reluctant to lock in various options for fear that there would be negative effects on users who did not need them.

For example, does the option work with shares on different generations of Windows machines?

It seemed safer to leave it as an option that people can easily add on their own.

YASSM v3.0 posted above. The search tool recognizes multiple networks.

YASSM v4.0 is posted above. It is a major revision that combines the previous functions (yassm-search, yassm-select, yassm-login) into one program. It eliminates potential problems that come with searching a network for shares.

------------------------

YASSM v4.1 is posted above. There are changes to the user interface.

Once you have done the setup for a share, you can mount it with one click.

YASSM v4.1 downloaded and installed in LxPupSc 17.08.24T on one of my core 2 duo Fujitsu S6520 laptops. Took this old user a minute to make the leap from yassm-search to the new interface (I hadn't used 4.0) but the help walkthrough is clear and once set up the single panel UI is neater. Currently my server box is also running on the samba in LxPupSc but in general it runs X-Slacko 4.2, now 4.3. Both the PcManFm in the LxPups and the Thunar in the X- series can connect to the shares but after a period of non-use even though the server box doesn't hibernate or sleep they sometimes fail to connect. Yassm-search always has.
Thanks,

Marv wrote:... but after a period of non-use even though the server box doesn't hibernate or sleep they sometimes fail to connect. Yassm-search always has.

Thanks for testing - I was concerned about this possibility.

In v4, will an unmount-remount operation wake up the server?

In v3, did you need to run the "Wake" operation to wake up the server, or was a new search good enough?

In v3, the Wake operation hit each host on the network with a ping. So try this in v4 when the server goes to sleep: Then mount again.

In v2 a simple search was enough to wake the server up, thus my preference for the Yassm-search. I will try both the unmount/mount test and the ping test in v4. It will take a bit to get a definitive answer as I need a failure to wake first and I will check the server running both LxPupSc and X-slacko 4.3.

In v3, a search operation did the following:
a. ran pnscan to locate the server
b. ran nmblookup to get its NETBIOS name
c. ran smbclient to get the list of shares
d. ran mount to mount the selected share.

But those middle steps should be unnecessary if you already know where the share is.

So v4 just does the following:
a. runs arp-scan to locate the server
b. runs mount

I have never seen arp-scan have a problem finding a server on the network.

[Edit] Here is something to try:

1. Open /usr/local/bin/yassm
2. Go to line 88
3. Change it to This increases the number of retries if the server doesn't respond.

So far v4 just works (finds and mounts correctly). I'll keep testing with the combinations I noted above. My NAS and printer addresses are all static to keep life simple in that regard.

I am going to repost v4.1 with the "-r" option. It sounds like the safe thing to do. There is no downside if the server is detected immediately.