Puppy Linux Discussion Forum

eden6000 · Joined: 08 Apr 2007 Posts: 259

HI Patriot, there is a bug (I suppose) in latest 0.1.8 beta: if I double right click on a share it answers "unable to mount ....; please check you username/password", both parameters are regularly saved, infact if I double left-click, connect and mount, everything works.
Ah, I didn't try this in previous versions, so I don't know if it used to work...

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm .....

eden6000,

Thanks for the report ... but it's actually not a bug. Global username/password is not used for fast mount-n-explore. The reason is to have a standard mount behavior for protected shares, so protected shares needs to be mounted using the normal mount dialog first. Once mounted, fast mount-n-explore (right double-click) will work fine.

HairyWill asked me about this recently and I believe it's better to leave it this way (at least for now) for the more common situations where protected shares in a decentralized peer-to-peer that would need different credentials (as the global credential is only good for one centralized resources).

Only protected shares have this limitation. Fast mount-n-explore works fine with open shares ... In the future, I will figure out a better way to handle multiple credentials and remove this limitation ...

Rgds

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm .....

lameSMBxplorer v0.2.0 beta introduces a new add-on utility: lameSMBqmount and the automount script, rc.smbqmsvc. While they were originally planned as a plug-in addon, it has been re-designed as a standalone utility to provide functionality in areas where lameSMBxplorer could not easily provide without gaining excess cellulite ... lameSMBqmount is meant to allow quickmounting without any scanning function. It also provides the interface for selecting a required shares for automounting on startup.

For this release, they are combined into a single package. In the future, they may be released as individual packages if there's a need ... Kindly go to the first page of this thread to give it a test run. I'd appreciate any input, bugs, feedbacks and suggestions that you may have ...

Rgds

eden6000 · Joined: 08 Apr 2007 Posts: 259

Hi Patriot, thanks for your answer, I understand what is the rationale there...btw I tried your latest 0.2.0, very good idea the one of quickmounting a share...actually in my network there are more than a hundred servers, but what I need is, almost always, to access only some specific shares, not all the network...but I haven't been able to automount at startup...parameters are there, I rebbooted, waited some minutes (is there a way to shorten the 120 seconds?), but there was no share mounted on /mnt/network...am I doing something wrong?

eden6000 · Joined: 08 Apr 2007 Posts: 259

I checked my bootsysinit.log, it says:
smbqmsvc: Error mounting //ip_address/share
smbqmsvc: Error mounting //ip_address/share

Béèm · Posted: Tue 09 Feb 2010, 17:25 Post subject:

Patriot · Joined: 15 Jan 2009 Posts: 734

hmmm .....

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm .....

This bugfix release corrects one minor issue for the automounting script.

changelog for lameSMBqmount v0.1.1 beta:
- added (automounting): extra mount info will be printed if it's run from the command line.
- bugfix (automounting): mount list parsing for share names containing spaces or overlapping share names.
- changed (automounting): mount list is now retrieved directly from /proc/mounts
- changed (automounting): additional delay time option reduced to 30 seconds

Note: this update should only be applied to lameSMBxplorer v0.2.0b

Rgds

eden6000 · Joined: 08 Apr 2007 Posts: 259

No way, Patriot....automounting still doesn't work, but if I launch from the command line
# /etc/init.d/rc.smbqmsvc start
it regularly mounts the shares....
this is my bootsysinit.log, if useful (I don't see anything private, so I think I can post it):

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm .....

Ah, yes ... the log is definitely helpful ... I can see exactly where it borks ... Thanks ...

Ok, to temporarily resolve this, you can just enable the "Add 30s delay" option ... The lo device route oversight is causing a premature mounting ... A bug fix should be ready within 24 hours ...

Rgds

eden6000 · Joined: 08 Apr 2007 Posts: 259

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm .....

This combined package is a bugfix release that corrects one minor issue for the automounting script where the lo device route (which should be excluded) causes premature automounting attempt.

The package have successfully gone through several rounds of automount tests in a static, dhcp, wifi and mixed network setup. If anyone still experiencing automounting issues, kindly post your bootsysinit.log (zip 'em up please) ...

Rgds

eden6000 · Joined: 08 Apr 2007 Posts: 259

Good work Patriot, now automounting works like a charm!

ejb · Joined: 23 Sep 2009 Posts: 12

I am attempting to access a naslite server. Naslite does not require or use userids or passwords.
I am able to connect to the server with lameSMBxplorer v0.2.1 beta. I can see the directories
and files on the server. However, when I click on any of the files, I get a permission denied
message. Any idea how to get past this problem??? I can access the files on the server using
a web browser.
Thanks.

PS: I attempted to attach to the NASLITE server using linNeighborhood and it worked.
I noticed that linNeighborhood connected with filemode 644 and dirmode 755.
I don't know if that is relevant, but the result was successful.

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm .....

Thanks for the feedback, ejb ... Please give me a bit of time to get a naslite testbed setup to do some connection tests ... I'm a bit short on spare time right now but hopefully I'll be able to resolve this by sometime next week ... (I do appreciate the note on the file access mode, thanks ...)

Rgds