Hi,
Or there any news on this issue?
How can I help to isolate this problem?
Is it at all a openbsd problem or a samba problem?
last week I did an new checkout of src and ports of current, compiled bsd and
the samba package and installed them:
# sysctl | fgrep -i bsd
kern.ostype=OpenBSD
On Mon 2008-03-17 23:57, Ian McWilliam wrote:
Please try the attached tar ball. It's against a 4.2-stable port tree.
I am not running 4.2-stable, I have switched to current:
# uname -a
OpenBSD boromir.zuhause.lan 4.3 GENERIC#2 i386
But I tried your tar ball, but got no different.
First I
On 14 Mar 2008, at 7:21 AM, Holger von Rhein wrote:
On Fri 2008-03-14 01:36, Ian McWilliam wrote:
I can confirm that mounting the fs as read only causes smbclient to
not
display directory contents. It appears to be an smbclient issue as
mapping the drive under Windows XP when the file
Hi,
On Thu 2008-03-06 03:46, Ian McWilliam wrote:
The attached tarball has the fixes and security updates for 4.2-stable.
Enjoy.
I tried nearly everything.
1) I updated my src and ports directories from cvs for 4.2 and compiled kernel,
objects and samba. Still empty directories.
2) I insert
Holger von Rhein wrote:
Hi,
On Thu 2008-03-06 03:46, Ian McWilliam wrote:
The attached tarball has the fixes and security updates for 4.2-stable.
Enjoy.
I tried nearly everything.
1) I updated my src and ports directories from cvs for 4.2 and compiled kernel,
objects and samba.
On Fri 2008-03-14 01:36, Ian McWilliam wrote:
I can confirm that mounting the fs as read only causes smbclient to not
display directory contents. It appears to be an smbclient issue as
mapping the drive under Windows XP when the file system is read only
works. If I get a chance, I'll read some
On Tue 2007-12-11 09:46, Marc Winiger wrote:
we have problems to share non-ffs filesystems with samba. it makes no
difference if the share points to such a filesystem or the filesystem is
mounted as a subdirectory of the share.
this happens on 4.2 and -current
anybody can confirm? any
