Iain Buchanan [EMAIL PROTECTED] writes:
aha, that did it for me, now I can browse smb:// shares again! However
there are other problems with it (new thread...)
What did you do?
I'm not sure what was meant by checking if samba USE flag is `set'.
I had the problem with Nautilus (IIRC you
Ian Porter [EMAIL PROTECTED] writes:
I had an similar problem with samba when I update the samba version, found
out
that samba users was not re-created. (/etc/samba/smbusers) thus I just
smdpasswd
What do you mean here.. you changed the way you use samba or what?
--
On Thu, 2006-02-09 at 05:33 -0600, Harry Putnam wrote:
Iain Buchanan [EMAIL PROTECTED] writes:
aha, that did it for me, now I can browse smb:// shares again! However
there are other problems with it (new thread...)
What did you do?
I'm not sure what was meant by checking if samba
I've made a little script in perl that scans some ip's and makes
entries for automount in /var/smb and than this script makes dirs like
192.168.0.3... and in them makes links to ghosted dirs in /var/smb.
Any one intrested in it?
This scripts scans only guest accessible shares.
It helped me solve
On 2/9/06, Harry Putnam [EMAIL PROTECTED] wrote:
Iain Buchanan [EMAIL PROTECTED] writes:
after you put USE=samba smb into your /etc/make.conf, type
$ emerge -p --newuse world
to see all the ebuilds affected by the new use flags.
I hope this clears it up a bit for you. Otherwise, keep
Harry Putnam wrote:
Iain Buchanan [EMAIL PROTECTED] writes:
after you put USE=samba smb into your /etc/make.conf, type
$ emerge -p --newuse world
to see all the ebuilds affected by the new use flags.
I hope this clears it up a bit for you. Otherwise, keep posting :)
There aren't any
On Thu, 2006-02-09 at 15:45 +0100, CapSel wrote:
I've made a little script in perl that scans some ip's and makes
entries for automount in /var/smb and than this script makes dirs like
192.168.0.3... and in them makes links to ghosted dirs in /var/smb.
Any one intrested in it?
This scripts
James Ausmus [EMAIL PROTECTED] writes:
The KDE package that utlizes a samba USE flag is:
kde-base/kdebase-kioslaves
What do the USE flags show for it if you do an emerge -pv kdebase-kioslaves?
Looks like cups is another that uses samba flag.
Running emerge -vp -uD --newuse on
Ryan Tandy [EMAIL PROTECTED] writes:
Sooo... you can access it from nearby Windows boxes, or you can't?
There appears to be a contradiction here. If you can't, restart samba
to make sure it's actually on.
Yeah sorry I noticed that too after posting. The correct statement is
that I CAN
On Thu, 2006-02-09 at 18:57 -0600, Harry Putnam wrote:
James Ausmus [EMAIL PROTECTED] writes:
The KDE package that utlizes a samba USE flag is:
kde-base/kdebase-kioslaves
What do the USE flags show for it if you do an emerge -pv kdebase-kioslaves?
Looks like cups is another that
Harry Putnam [EMAIL PROTECTED] writes:
I'm currently recompiling kdebase-kioslaves and cups with samba flag set.
The recompile made the difference. After recompiling kioslaves with
samba and smb flags set I know have the smb:// browse functionality in
konq again.
--
gentoo-user@gentoo.org
Iain Buchanan [EMAIL PROTECTED] writes:
aha, that did it for me, now I can browse smb:// shares again! However
there are other problems with it (new thread...)
What did you do?
I'm not sure what was meant by checking if samba USE flag is `set'.
Do you mean it appears in /etc/make.conf ... or
On Wed, 2006-02-08 at 23:59 -0600, Harry Putnam wrote:
Iain Buchanan [EMAIL PROTECTED] writes:
aha, that did it for me, now I can browse smb:// shares again! However
there are other problems with it (new thread...)
What did you do?
I'm not sure what was meant by checking if samba USE
13 matches
Mail list logo
