search for: orbs

Some lists and emails are distributed via ns1.samba.org. For those of you that use ORBS, you'll find it is blacklisted now. There is no mention of it on the website and it doesn't return a positive when you enter it for testing but it has slipped into the ORBS blacklist somewhere. Samba.org admins may wish to force all ns1 outbound email via another netblock, bringing it up t...

Hi, armed with Samba-3 -by example I proceeded to test my 2 linux lan [suselinux pro 9.1 with Samba 3.0.9-2.6-suse]. I followed instructions and made the smb.config as small as possiblw: [global] workgroup = snj server string = Samba Server guest ok = yes [orb] comment = removable 2.2 gb hd path = /orb browsable = yes read only = no However, I was stumped practically immediately as you can

Currently I only have one machine backing up to another. I am backing up to a filesystem that is mounted as nosuid. The syncing process works perfectly except it fails on files that are suid. Example proc/ root/ tmp/ mknod tmp/mysql.sock : Invalid argument mknod tmp/orbit-daud/orb-12573780511489051058 : Invalid argument mknod tmp/orbit-daud/orb-139425434385535813 : Invalid argument mknod

hi, I'm new to Samba. I use Suse linux 9.1pro & kde on a small network with Samba 3.0.9. I tried the testparm from the Official Samba -3 howto. Unfortunately the book, etc. does not address the error msg given, follows. Can somebody help? scn@scn:~> testparm -s -v | egrep "(lp|print|spool|driver|ports|\[)" Load smb config files from /etc/samba/smb.conf Processing section

I apologize for sending this to the list. Keith from Hazleton... your mail server is rejecting mail I'm sending you from my mail servers, as well as from gmail... you may really want to consider using a different blacklist.. the on you are using now is going to block almost everything and everyone.

hi, I thought it would be easy and over quickly - it has been anything but... I decided to test and use Samba 3.+ on my Suse linux pro 9.1 lan but cannot get it to work and need some help/guidance. I have two essentially identical linux computers [east and west] and I have both of them as both server AND client. At a later date, after this `simple' lan works, I plan to add a ms portable

Hello, I'd like to switch off this silly "Nakatomi Socrates" message which reminds me on Linux and their childish naming schemes. It is only cosmetics, but it bothers me whenever I switch on the laptop. I guess there is a switch already prsent to have in the bootloader config? Thanks, oh -------------- next part -------------- A non-text attachment was scrubbed... Name:

Is there anyone on this list running DamageControl on a Debian or a Windows system ? If so would you care to share how you accomplished this (details ... it''s all in the details) ? While I will still work through the problems I am encountering (it''s a great learning experience) I would still like to have a working instance of DamageControl to use in the meantime. I am

Handle the new CCW_CMD_SET_IND_ADAPTER command enabling adapter interrupts on guest request. When active, host->guest notifications will be handled via global_indicator -> queue indicators instead of queue indicators + subchannel I/O interrupt. Indicators for virtqueues may be present at an offset. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/s390x/css.c |

Handle the new CCW_CMD_SET_IND_ADAPTER command enabling adapter interrupts on guest request. When active, host->guest notifications will be handled via global_indicator -> queue indicators instead of queue indicators + subchannel I/O interrupt. Indicators for virtqueues may be present at an offset. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/s390x/css.c |

On Fri, 5 Apr 2019 01:16:15 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > Virtio-ccw relies on cio mechanisms for bootstrapping the ccw device. Well, a ccw device is, by definition, using cio mechanisms ;) Better say: "As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor." Or something like that. > Thus we

As virtio-ccw devices are channel devices, we need to use the dma area within the common I/O layer for any communication with the hypervisor. Note that we do not need to use that area for control blocks directly referenced by instructions, e.g. the orb. It handles neither QDIO in the common code, nor any device type specific stuff (like channel programs constructed by the DASD driver). An

Hi, here's the qemu patch that implements the new adapter indicators ccw in virtio-ccw and injects adapter interrupts for the devices enabled for it. Cornelia Huck (1): s390/virtio-ccw: Adapter interrupt support. hw/s390x/css.c | 10 ++++++++ hw/s390x/css.h | 2 ++ hw/s390x/virtio-ccw.c | 66 ++++++++++++++++++++++++++++++++++++++++++++++++- hw/s390x/virtio-ccw.h |

Hi, here's the qemu patch that implements the new adapter indicators ccw in virtio-ccw and injects adapter interrupts for the devices enabled for it. Cornelia Huck (1): s390/virtio-ccw: Adapter interrupt support. hw/s390x/css.c | 10 ++++++++ hw/s390x/css.h | 2 ++ hw/s390x/virtio-ccw.c | 66 ++++++++++++++++++++++++++++++++++++++++++++++++- hw/s390x/virtio-ccw.h |

Hi, here's the current implementation of virtio-ccw adapter interrupts in qemu. Code is unchanged, only rebased against current master. Cornelia Huck (1): s390/virtio-ccw: Adapter interrupt support. hw/s390x/css.c | 10 ++++++++ hw/s390x/css.h | 2 ++ hw/s390x/virtio-ccw.c | 64 ++++++++++++++++++++++++++++++++++++++++++++++++- hw/s390x/virtio-ccw.h | 4 ++++

Hi, here's the current implementation of virtio-ccw adapter interrupts in qemu. Code is unchanged, only rebased against current master. Cornelia Huck (1): s390/virtio-ccw: Adapter interrupt support. hw/s390x/css.c | 10 ++++++++ hw/s390x/css.h | 2 ++ hw/s390x/virtio-ccw.c | 64 ++++++++++++++++++++++++++++++++++++++++++++++++- hw/s390x/virtio-ccw.h | 4 ++++

As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor. This patch addresses the most basic stuff (mostly what is required for virtio-ccw), and does take care of QDIO or any devices. An interesting side effect is that virtio structures are now going to get allocated in 31 bit addressable storage. Signed-off-by: Halil Pasic <pasic at

From: Halil Pasic <pasic at linux.ibm.com> As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor. It handles neither QDIO in the common code, nor any device type specific stuff (like channel programs constructed by the DASD driver). An interesting side effect is that virtio structures are now going to get allocated in 31 bit

From: Halil Pasic <pasic at linux.ibm.com> As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor. It handles neither QDIO in the common code, nor any device type specific stuff (like channel programs constructed by the DASD driver). An interesting side effect is that virtio structures are now going to get allocated in 31 bit

On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux wrote: > On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote: > > On Wed, Oct 07, 2015 Geert Stappers wrote > > > 13:36:47.964636 IP 192.168.205.1.47973 > 192.168.205.50.1938: UDP, length 30 > > > 13:36:47.964685 IP 192.168.205.50.1938 > 192.168.205.1.47973: UDP, length 4 > >