similar to: Disallow Deletion from Trash Folder

Hello: I'm using Dovecot to provide IMAP services for Thunderbird clients. The user's mail is stored in Maildir format and the individual emails which the user "receives" are actually downloaded and put into the Maildir "repository" using a Python email client (POP3 client). I am trying to create the dovecot-uidlist file and maintain the "next UID" value

Hello, when testing FreeBSD-7.1-BETA i discovered that the floppy disk controller doesn't work correctly. Trying to format a floppy (perhaps with bad blocks) i get: Processing fdformat: ioctl(FD_FORM): Device not configured instead of the normal E letter. I then checked the same problem is present on FreeBSD-6.3 and it has been reported by Beech Rintoul (*) in 2006! Of course the floppy disk

I have installed and am running Samba4 as a domain controller in an existing Domain as described in "Samba4/HOWTO/Join a domain as a DC". I compiled Samba4 using the latest git sources. However I am having problems with shares on the samba server. I have a share called public on the Samba4 server. I created a folder in the share using Windows 2003 server called test and gave everyone

Hello Everyone, I have disallow=all and allow=g729 set in sip.conf however, it seems that asterisk still thinks it support other codecs: Capabilities: us - 0x80000008000e (gsm|ulaw|alaw|h263|testlaw). How can I disable gsm,ulaw,alaw..... Thanks in Advance, Nick.

If a domain has PCI devices then we can''t safely save or migrate it. At least one user has had system crashes due to this, and the way the xendomains script automatically saves and restores domains on reboot. Since there''s no sensible semantics for it at the moment, we should disallow it and return an appropriate error message to xm. The first attached patch prevents the

The code currently only supports one virtio-rng device at a time. Invoking guests with multiple devices causes the guest to blow up. Check if we've already registered and initialised the driver. Also cleanup in case of registration errors or hot-unplug so that a new device can be used. Reported-by: Peter Krempa <pkrempa at redhat.com> Reported-by: <yunzheng at redhat.com>

The code currently only supports one virtio-rng device at a time. Invoking guests with multiple devices causes the guest to blow up. Check if we've already registered and initialised the driver. Also cleanup in case of registration errors or hot-unplug so that a new device can be used. Reported-by: Peter Krempa <pkrempa at redhat.com> Reported-by: <yunzheng at redhat.com>

For virtio-1 devices, the driver must not attempt to set feature bits after it set FEATURES_OK in the device status. Simply reject it in that case. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/virtio/virtio.c | 16 ++++++++++++++-- include/hw/virtio/virtio.h | 2 ++ 2 files changed, 16 insertions(+), 2 deletions(-) diff --git a/hw/virtio/virtio.c

On Fri, 12 Dec 2014 11:55:38 +0100 Thomas Huth <thuth at linux.vnet.ibm.com> wrote: > On Thu, 11 Dec 2014 14:25:14 +0100 > Cornelia Huck <cornelia.huck at de.ibm.com> wrote: > > > For virtio-1 devices, the driver must not attempt to set feature bits > > after it set FEATURES_OK in the device status. Simply reject it in > > that case. > > > >

-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw -------------- next part -------------- >From aaf03a51a26ee501f5dbf2720bbb8a5e3b4e1e6b Mon Sep 17

For virtio-1 devices, the driver must not attempt to set feature bits after it set FEATURES_OK in the device status. Simply reject it in that case. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/virtio/virtio.c | 16 ++++++++++++++-- include/hw/virtio/virtio.h | 2 ++ 2 files changed, 16 insertions(+), 2 deletions(-) diff --git a/hw/virtio/virtio.c

On Fri, 12 Dec 2014 11:55:38 +0100 Thomas Huth <thuth at linux.vnet.ibm.com> wrote: > On Thu, 11 Dec 2014 14:25:14 +0100 > Cornelia Huck <cornelia.huck at de.ibm.com> wrote: > > > For virtio-1 devices, the driver must not attempt to set feature bits > > after it set FEATURES_OK in the device status. Simply reject it in > > that case. > > > >

Hi, On the general section of my sip.conf I had a disallow=all. Then I put disallow=all, allow=g729, allow=ulaw on my users. It didn't work until I removed the disallow=all from the header. I know disallow=all in the header is totally useless in this case (since I have it for every user), but anyway, is this the correct behavior? Thank you Dov -------------- next part -------------- An

Hello, everyone. I've installed asterisk SVN-branch-1.4-r62942 and every time I reload asterisk I get this in CLI: -- Reloading module 'app_playback.so' (Sound File Playback Application) [May 3 20:04:26] NOTICE[13892]: app_playback.c:455 reload: Reloading say.conf == Parsing '/etc/asterisk/say.conf': Found [May 3 20:04:26] WARNING[13879]: frame.c:1289

With the exception of modesets which would switch the DPMS state of a connector from on to off, we want to make sure that we disallow all modesets which would result in enabling a new monitor or a new mode configuration on a monitor if the connector for the display in question is no longer registered. This allows us to stop userspace from trying to enable new displays on connectors for an MST

With the exception of modesets which would switch the DPMS state of a connector from on to off, we want to make sure that we disallow all modesets which would result in enabling a new monitor or a new mode configuration on a monitor if the connector for the display in question is no longer registered. This allows us to stop userspace from trying to enable new displays on connectors for an MST

Transitional devices should all use __virtioXX types. Modern ones should use __leXX. _uXX type would be a bug. Let's prevent that. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- include/linux/virtio_config.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/include/linux/virtio_config.h b/include/linux/virtio_config.h index 64da491936f7..c68f58f3bf34

On Mon, 3 Aug 2020 16:59:57 -0400 "Michael S. Tsirkin" <mst at redhat.com> wrote: > Transitional devices should all use __virtioXX types. I think they should use __leXX for those fields that are not present with legacy devices? > Modern ones should use __leXX. > _uXX type would be a bug. > Let's prevent that. That sounds right, though. > > Signed-off-by:

Transitional devices should all use __virtioXX types (and __leXX for fields not present in legacy devices). Modern ones should use __leXX. _uXX type would be a bug. Let's prevent that. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- include/linux/virtio_config.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/include/linux/virtio_config.h

_Generic version allowed __uXX types but that is no longer necessary: Transitional devices should all use __virtioXX types (and __leXX for fields not present in the legacy devices). Modern ones should use __leXX. _uXX type would be a bug. Let's prevent that. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- include/linux/virtio_config.h | 16 ++-------------- 1 file changed, 2