similar to: problems with SLES!

Hi all, Just curious, Quite a while a go, i was checking for supported SW-platform. AFAIR, it was RHES and SLES Now it's only RHES-4 and FC-3 or FC-4. Not a single syllable about CentOS or SLES-9 or SLES-10 It probably just runs fine, but any chance of getting support for their *-enterprise version? (just in case of, if one needs it) Hans -- pgp-id: 926EBB12 pgp-fingerprint: BE97 1CBF

Hi, It would be great if the spec file could be updated to remove the dependency on python-ctypes for sles 11 since this seems to be included as part of the python package. Also, there are lot of pragma warnings. It doesn't look like those pragma's work with the gcc on suse 11p2: ../../../../rpc/xdr/src/cli1-xdr.h:25: warning: unknown option after '#pragma GCC diagnostic' kind

Hi all, I've just recently carried out 2 clean installs of SUSE SLES 10 (SUSE Linux Enterprise Server 10 (i586) - Kernel 2.6.16.21-0.8-smp (0)) and have found on both occasions that the YAST configuration tool for SAMBA in this release is broken. Initial configuration seems to be OK, but whenever subsequent changes are made they are not reflected in smb.conf. Just a little frustrating!

I'd imagine document will answer many prayers for stumped admins These are my notes to setup SuSE Linux Enterprise Server v9 and how to configure Samba v3.04-SuSE to work as a member server in a domain Also, this document contains FULL instructions on how to setup SSL Secured SWAT (Samba Web Administration Tool) This document is a step by step guide to installing SLES and Samba. Of course

Update SuSE Linux detection. Up to now everything with a /etc/SuSE-release file was treated as openSuSE. With this change SLES based distributions such as "SUSE Linux Enterprise Server", "SUSE Linux Enterprise Desktop" and "Novell Linux Desktop" will show up as "sles". The 'opensuse' detection was updated to handle older openSuSE releases as well as

Hi all, I installed SLES 10.0b3 with XEN on some test-systems and created a SLES 10.0b3-image for use with domU''s. The installation and booting of this domU was no problem, but on some systems the host dom0 restarts if I generate some IP-traffic from the guest. This happens on an old AMD Athlon 1,3GHz, an old Intel P3 and an Intel desktop with P4 HT/VT/EM64T but not on an Intel

Hello everyone, I''m totally new to Xen and trying to run it on some platforms (x86, x64) using SLES (that is what I have to use for reasons other than technical). Several machines on which I tried using Xen simply fails to run normally using Xen kernel: either network communication is not functioning at all despite proper configuration (that works on non-Xen kernel), or the kernel

Use the common denominator for SLES and openSUSE in the dependencies. For example most of NetworkManager pieces and metacity aren't provided on SLES. ifconfig is in the net-tools-deprecated package in openSUSE Factory, which means after openSUSE Leap 42.2. Older versions have it in the net-tools package. Adding this complexity only to add ifconfig because sysadmins prefer it isn't too

The "sles" distribution string in libguestfs represents both SLES and SLED, so map the osinfo descriptions of "sled" distributions as "sles". --- src/osinfo.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/osinfo.c b/src/osinfo.c index 907580e..7fdaf1c 100644 --- a/src/osinfo.c +++ b/src/osinfo.c @@ -625,7 +625,7 @@ parse_distro (guestfs_h

Same question for asterisk-users as well: ----- Forwarded message from Tzafrir Cohen <tzafrir.cohen at xorcom.com> ----- Date: Wed, 7 Mar 2012 21:14:04 +0200 From: Tzafrir Cohen <tzafrir.cohen at xorcom.com> To: asterisk-dev at lists.digium.com Short version: it's now time to remove. Anybody actually uses latest DAHDI with RHEL4? See inline, On Thu, Dec 29, 2011 at 07:42:39PM

Hello, I am unable to do a graceful shutdown or reboot of SLES 10 SP4 virtual machines (Kernel version: 2.6.16.60-0.85.1-default) with virsh shutdown or virsh reboot commands. (e.g virsh shutdown "vmname" ). On issuing these commands there is no impact on the VM. Also unable to perform the shutdown or reboot operations from the menu options available on the console when accessing the

I currently manage approximately 150 hosts with a handful of ZLM policies, but I''ve had one too many policies lost by the management server to keep using this solution. I''m wondering if anyone has any experiences (good or bad) they''d be willing to share specific to using Puppet with SLES (9 and 10). What experiences have you had with package management tools? Would

On Wednesday 09 September 2015 15:54:10 Olaf Hering wrote: > Just poked around in my =libguestfs folder... > > On Wed, Sep 09, Pino Toscano wrote: > > > + if (STRPREFIX (line, "ID=")) { > > This is not handled: > > NAME="SLES" > VERSION="12" > VERSION_ID="12" > PRETTY_NAME="SUSE Linux Enterprise Server

I think this is a recurrence of an old bug. Running Samba 3.5.4 with CTDB on GPFS 3.4.0.6 with the vfs_gpfs module using CentOS 5.6. It is a vanilla CentOS RPM's with the vfs_gpfs module a self compiled add on. Running with NFSv4 ACL's. Basically what happens is when a user saves a file in Office 2010 (no Office 2007 to test with) with Windows 7 on the Unix side the permissions on the

Hello all, I'm gearing up for an RPM deployment of 4.2p1 on SuSE (SLES 9). However, the files under contrib/suse in the OpenSSH distribution appear to be out-of-date. In particular, SuSE seems to handle init scripts quite differently now. So, is anyone building local RPMs for SuSE? If so, could you post the .spec file you are using? Is there any interest in updating the contrib/suse

Hi there, Here are a few patches to get virt-p2v working on openSUSE and SLES. Note that I intentionnaly use icewm and yast2 lan for SLES and openSUSE since SLES doesn't ship metacity and all of NetworkManager pieces. Cédric Bosdonnat (4): p2v: use yast2 lan on SUSE distros rather than NM p2v: fix dependencies for SLES / openSUSE p2v: add virt-p2v-make-kiwi to generate kiwi config

It needs to check for the minor version, not major version. Fixes commit a442d2c3217f709128f0e377f88649fb6ba90f45. --- builder/repository_main.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/builder/repository_main.ml b/builder/repository_main.ml index bb440563b..9932fbae4 100644 --- a/builder/repository_main.ml +++ b/builder/repository_main.ml @@ -178,7 +178,7 @@ let

To the Linux Community at Large: I reported to this list back in January, 2010 that the standard x86_64 kernel, when built from the src.rpm and modified for AMD K8 / K10 Extensions would not build. I reported this here and to Red Hat via Bugzilla ID number 558367. RH AS / Centos 5.3 worked fine. That was Centos 5.4 / Red Hat Enterprise AS 5 Update 4. Today we tried to optimize Red Hat

Hi, Is there any SuSE SLES rebuild project like CentOS/RHEL?? doesnt SuSE make SRPMS available to public? Regards.

Hello, Whenever copying files using ssh (scp) from SLES 8 (openssh 3.4p1-263) to another box (e.g SLES 8, Solaris 8, Windows XP), the memory of the initial SLES 8 box gets depleted. To make sure this is true I use the free command whilst copying and see that the used memory reaches 90 / 100%. After the copying is finished this memory is never released. No memory tool can tell me what happened