similar to: The problem on joining a computer running FreeBSD(v5.4) to a Windows 2003 Active Directory domain using samba3.

Hi Adrian, Thank you for your help! I did it according your advice ,for example: [IT Dept] comment = IT Department file space path = /appl/it valid users = "@all it" public = No writable = yes but I cann't pass the authentication by AD. The error message in log likes this: 2005/10/11 12:05:06, 4] smbd/reply.c:reply_tcon_and_X(407) Client

Hi. I am trying to run Solaris 10 under Xen but I have few problems. First of all, there are some weird errors while booting up system. Here is a screenshot: http://kosjenka.srce.hr/~jsosic/xen-solaris10u8.png Messages are these: WARNING: xdf: couldn''t write version WARNING: xdf: couldn''t write version WARNING: Disk is too large: Model QEMU HARDDISK Serial# QM00002 NOTICE:

h>From: samba-request@lists.samba.org >Reply-To: samba@lists.samba.org >To: samba@lists.samba.org >Subject: samba Digest, Vol 34, Issue 14 >Date: Mon, 10 Oct 2005 12:05:06 +0000 (GMT) ------------------------------------------------------------------------------------------------------- From: Liu, Hong Quan ÁõºìȪ <liuhongquan@nwbsc.com> To: <samba@lists.samba.org>

On Wed, Dec 11, 2019 at 11:03:07AM -0500, Michael S. Tsirkin wrote: > On Fri, Dec 06, 2019 at 03:39:12PM +0100, Stefano Garzarella wrote: > > When we receive a new packet from the guest, we check if the > > src_cid is correct, but we forgot to check the dst_cid. > > > > The host should accept only packets where dst_cid is > > equal to the host CID. > > >

On Wed, Dec 11, 2019 at 11:03:07AM -0500, Michael S. Tsirkin wrote: > On Fri, Dec 06, 2019 at 03:39:12PM +0100, Stefano Garzarella wrote: > > When we receive a new packet from the guest, we check if the > > src_cid is correct, but we forgot to check the dst_cid. > > > > The host should accept only packets where dst_cid is > > equal to the host CID. > > >

On Thu, Dec 12, 2019 at 07:56:26AM -0500, Michael S. Tsirkin wrote: > On Thu, Dec 12, 2019 at 01:36:24PM +0100, Stefano Garzarella wrote: > > On Wed, Dec 11, 2019 at 11:03:07AM -0500, Michael S. Tsirkin wrote: > > > On Fri, Dec 06, 2019 at 03:39:12PM +0100, Stefano Garzarella wrote: > > > > When we receive a new packet from the guest, we check if the > > >

On Mon, Aug 19, 2019 at 11:38 AM Hans Verkuil <hverkuil-cisco at xs4all.nl> wrote: > > Hi all, > Hi Hans. > The patches in this series can be applied independently from each other. > > If you maintain one of these drivers and you want to merge it for v5.4 > yourself, then please do so and let me know. If you prefer I commit it > to drm-misc, then please review and

On Thu, Dec 12, 2019 at 01:36:24PM +0100, Stefano Garzarella wrote: > On Wed, Dec 11, 2019 at 11:03:07AM -0500, Michael S. Tsirkin wrote: > > On Fri, Dec 06, 2019 at 03:39:12PM +0100, Stefano Garzarella wrote: > > > When we receive a new packet from the guest, we check if the > > > src_cid is correct, but we forgot to check the dst_cid. > > > > > > The

Hi Dariusz, Hans, I can apply the dw-hdmi patches if necessary. Neil On 19/08/2019 11:38, Hans Verkuil wrote: > Hi all, > > The patches in this series can be applied independently from each other. > > If you maintain one of these drivers and you want to merge it for v5.4 > yourself, then please do so and let me know. If you prefer I commit it > to drm-misc, then please

I am looking for yum-priorities or any info on any changes here for CentOS 5.4. There is also a forum post for this here: <https://www.centos.org/modules/newbb/viewtopic.php?topic_id=22798&forum=37> Is this missing on purpose? Function merged with another yum package? Or is it just missing as an oversight? -- //Morten //morten at mortent.org

Hello, I have the following data frame (DF): V5 V5.1 V5.2 V5.3 V5.4 V5.5 2 -5890.18905 -6019.84665 -6211.06545 -6198.9353 -6616.8677 -6498.7183 3 -5890.18905 -6019.84665 -6211.06545 -6198.9353 -6616.8677 -6498.7183 4 -5890.18905 -6019.84665 -6211.06545 -6198.9353 -6616.8677 -6498.7183 5 -5890.18905 -6019.84665 -6211.06545 -6198.9353 -6616.8677

from [CentOS] CentOS 5.4? anyone? > Is that a big problem for the people who write the code and have every > revision preserved for posterity (and for others to learn from) in a > public revision control system? > I'm not sure that I understand. Is there indeed such a public repository of the build scriptds / RPM specs used by CentOS? That would indeed be fascinating and useful

When we receive a new packet from the guest, we check if the src_cid is correct, but we forgot to check the dst_cid. The host should accept only packets where dst_cid is equal to the host CID. Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> --- drivers/vhost/vsock.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/vhost/vsock.c

When we receive a new packet from the guest, we check if the src_cid is correct, but we forgot to check the dst_cid. The host should accept only packets where dst_cid is equal to the host CID. Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> --- drivers/vhost/vsock.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/vhost/vsock.c

Hi all, The patches in this series can be applied independently from each other. If you maintain one of these drivers and you want to merge it for v5.4 yourself, then please do so and let me know. If you prefer I commit it to drm-misc, then please review and (hopefully) Ack the patch. I would really like to get this in for v5.4 so I can get the userspace bits in for v5.4 as well through the

I'm pretty new to the task of upgrading CentOS or RedHat o.s.'s. I'm more familiar with upgrading Debian based o.s.'s. Here are my questions: 1) will yum ever upgrade the major version? I understand that there is no upgrade path from v5.x to v6.x, but is that always the case? e.g. was there an upgrade path from v4.x -> v5.x? If yum is capable of doing so, what are the

This series updates DRM drivers to use new CEC notifier API. Changes since v6: Made CEC notifiers' registration and de-registration symmetric in tda998x and dw-hdmi drivers. Also, accidentally dropped one patch in v6 (change to drm_dp_cec), brought it back now. Changes since v5: Fixed a warning about a missing comment for a new member of drm_dp_aux_cec struct. Sending to a wider

Hi all, I'm getting a segmentation fault with yum when I try to update a CentOS v5.4 install to v5.5. What I've done: * Ran yum clean all. * Ran yum update yum* * Ran yum update, and got the segmentation fault. * Yum suggested running with option --skip-broken, which I did. Still got the segmentation fault. * Rebooted machine and ran yum update again. Segmentation fault... * Googled

Hello, I just registered to the wiki under the login: MathieuBaudier I'm currently testing a lot CentOS (see below: To introduce myself quickly) and although I target server deployments, I have also spent some time configuring desktops. I went through some of the pain and I would have been happy to share it with other through the wiki. Especially: - I configured a fairly recent MacBook Pro

https://bugs.freedesktop.org/show_bug.cgi?id=111841 Bug ID: 111841 Summary: Setting gamma or color temperature on GK104 causes horizontal artifacts / flickering Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: