similar to: Why does RH's Samba build use a file for shared memory?

I often find with Samba v2.0.3 that files accessed via Win95 (OSR2) stay locked forever after exiting the application that used them. I've got an application called Visual SlickEdit (VSE), which is installed on a shared drive. The drive is an exported Samba share from my RedHat v5.2 (kernel v2.2.5) server. Both the Win32 and OS/2 versions of VSE are installed beneath the same subdirectory

Hello All, Just a short note to add my vote for a HUGE round of applause to the CentOS team for their untiring efforts in getting releases out the door. I've just upgraded several servers to 5.6 and it all "just works". None of the team's work is easy to accomplish, especially when less-than-useful complaints keep popping up from thoughtless users who don't appreciate

Hey, digest 2286 incomplete, only first 3 topics contained. Can I get a new copy ? Thanks, Hans-Joerg Glock > -----Urspr?ngliche Nachricht----- > Von: samba@samba.org [SMTP:samba@samba.org] > Gesendet am: Mittwoch, 27. Oktober 1999 22:12 > An: Multiple recipients of list SAMBA > Betreff: SAMBA digest 2286 > > SAMBA Digest 2286 > > For information on

When an OS/2 or Win9x client logs into a (Linux) Samba v2.0.6 server the running smbd spawns a copy of itself. That second instance of smbd then handles all the shares for that client machine. In contrast, a Linux client which does multiple smbmounts (also Samba v2.0.6) will cause the server to spawn a copy of smbd for *each* smbmount mountpoint. This has the potential for using up a lot more

When I attempted to build Samba (v2.0.7) on a LynxOS (v3.1) box I was told that configure could determine my operating system. LynxOS, for those that don't know, is a Unix-like RTOS. It comes with a binary version of Samba, but a) it's old and b) it's not built for encrypted passwords which means I can't access it from WinNT. Can anyone advise me on what it would take to build

Unknown recipient ----- Original Message ----- From: <samba@samba.org> To: Multiple recipients of list SAMBA <samba@samba.org> Sent: Thursday, July 08, 1999 1:02 AM Subject: SAMBA digest 2158 > SAMBA Digest 2158 > > For information on unsubscribing see http://samba.org/listproc/ > Topics covered in this issue include: > > 1) msaccess and samba prob solved -

[Steve Snyder <swsnyder@home.com>] > When I attempted to build Samba (v2.0.7) on a LynxOS (v3.1) box I was > told that configure could determine my operating system. > > LynxOS, for those that don't know, is a Unix-like RTOS. It comes > with a binary version of Samba, but a) it's old and b) it's not built > for encrypted passwords which means I can't

These days dma ops can be overridden per device, and the virtio core uses that to handle the dma quirks transparently for the rest of the kernel. So we can drop the virtio_has_dma_quirk() checks, just use the dma api unconditionally and depend on the virtio core having setup dma_ops as needed. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_object.c

These days dma ops can be overridden per device, and the virtio core uses that to handle the dma quirks transparently for the rest of the kernel. So we can drop the virtio_has_dma_quirk() checks, just use the dma api unconditionally and depend on the virtio core having setup dma_ops as needed. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_object.c

Hi, I have a problem when I compile Samba 2.0.3, the next error message is generated doing "make": Using LIBS = Compiling locking/shmem.c locking/shmem.c: In function `smb_shm_open': locking/shmem.c:921: `PROT_READ' undeclared (first use this function) locking/shmem.c:921: (Each undeclared identifier is reported only once locking/shmem.c:921: for each function it appears in.)

Hi, > > (a) software rendering: client allocates shared memory buffer, renders > > into it, then passes a file handle for that shmem block together > > with some meta data (size, format, ...) to the wayland server. > > > > (b) gpu rendering: client opens a render node, allocates a buffer, > > asks the cpu to renders into it, exports

Hi, > > (a) software rendering: client allocates shared memory buffer, renders > > into it, then passes a file handle for that shmem block together > > with some meta data (size, format, ...) to the wayland server. > > > > (b) gpu rendering: client opens a render node, allocates a buffer, > > asks the cpu to renders into it, exports

For a couple of years people have been reporting intermittent problems with rsync over ssh freezing during a large transfer (typically several GB). I have now gotten to the bottom of these problems, and have written a small test program which demonstrates a deadlock in sshd when doing large bi-directional transfers. Luckily the problem is easily solved by modifying sshd to use socketpair() instead

Hi, > > Hmm? I'm assuming the wayland client (in the guest) talks to the > > wayland proxy, using the wayland protocol, like it would talk to a > > wayland display server. Buffers must be passed from client to > > server/proxy somehow, probably using fd passing, so where is the > > problem? > > > > Or did I misunderstand the role of the proxy? >

Hi, > > Hmm? I'm assuming the wayland client (in the guest) talks to the > > wayland proxy, using the wayland protocol, like it would talk to a > > wayland display server. Buffers must be passed from client to > > server/proxy somehow, probably using fd passing, so where is the > > problem? > > > > Or did I misunderstand the role of the proxy? >

I wish to mount a Win95 share on my linux machine. I can use smbclient to get to the shared disk, using this format: smbclient //win95.machine/share <password> The win95.machine is listed in my /etc/hosts file. I've tried every permutation of the smbmount syntax that I've been able to find in the documentation, dejanews, or this mailing list. Perhaps I've missed some. I

[Note: This has been posted to linux-kernel and was ignored. Since smbfs is maintained by the samba team, I am retrying here] Hi! To maintain and install packages from CD-ROM to my Debian/GNU Linux system, I use Debian's apt package. Since my Linux box is stowed away in a closet, I use an smbfs mount to mount the CD-ROM drive from my Windows desktop machine to the Linux box. This used to

On Mon, Feb 05, 2018 at 03:46:17PM +0100, Tomeu Vizoso wrote: > On 02/05/2018 01:20 PM, Gerd Hoffmann wrote: > > Hi, > > > > > > Why not use virtio-vsock to run the wayland protocol? I don't like > > > > the idea to duplicate something with very simliar functionality in > > > > virtio-gpu. > > > > > > The reason for

On Mon, Feb 05, 2018 at 03:46:17PM +0100, Tomeu Vizoso wrote: > On 02/05/2018 01:20 PM, Gerd Hoffmann wrote: > > Hi, > > > > > > Why not use virtio-vsock to run the wayland protocol? I don't like > > > > the idea to duplicate something with very simliar functionality in > > > > virtio-gpu. > > > > > > The reason for

DRM's fbdev console uses regular load and store operations to update framebuffer memory. The bochs driver on sparc64 requires the use of I/O-specific load and store operations. We have a workaround, but need a long-term solution to the problem. This patchset changes GEM's vmap/vunmap interfaces to forward pointers of type struct dma_buf_map and updates the generic fbdev emulation to use