similar to: Support for SLES9

Hello all, I am running SLES9 with the latest kernel patches (2.6.5-7.282-bigsmp) and ocfs2 version (1.2.1-SLES), I was wondering if anyone had any info on if the latest ocfs2 will be included in SLES anytime soon. Or how to get the patches from Novell. Thanks in advance! - Andy Andy Kipp Network Administrator Velcro USA Inc. 406 Brown Ave. Manchester, NH 03103 Phone: (603) 222-4844 Email:

hi! when will OCFS be available on RedHat AS/ES 4 or any 2.6 kernel distro ? Thanks Miguel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20050516/52aa4375/attachment.html

Hello, I've been unable to succeed with Samba-Ldap setup on SLES9 until this evening. I thought I had a PAM issue but that was not the case. To cut to the chase, I ran Yast's 'ldap-server' module without any changes as it found the ldap server settings. Once finished I could join the domain from XP Pro which is what I was unable to do. I checked what Yast did and it reset

Haven't really tried this yet, but I'm wondering what the direction is for official ocfs support on SLES9. Anyone know if there are plans to support OCFS 1.x on sles9 at some point? I know it's a 2.6 kernel instead of 2.4... thanks, Jeremy This message (including any attachments) contains confidential information intended for a specific individual(s) and purpose, and is protected

Hi I need to install a current version of samba on a server running SuSE9.0 :-/ My Idea was to use the binary package provided at samba.org for SLES9 but I do not have the exact libraries that are needed: libtalloc.so.1 is needed by samba-3.2.8-2.1.140 libtdb.so.1 is needed by samba-3.2.8-2.1.140 libwbclient.so.0 is needed by samba-3.2.8-2.1.140 -> these are also

All - This evening I attempted to catch up on security releases and upgraded from SLES9 3.0.20 to 3.0.26a and found that getent only returns local UNIX groups and users. We are using winbind to communicate with an NT domain. The server has been restarted and services are running. Using wbinfo -u and -g does provide NT domain groups and users as expected and net rpc testjoin result is OK. I have

Anyone managed to get a SLES9-SP4 HVM installed? I''ve been going round in circles for hours with this one. What I''ve found out: 1 - I can''t install from an emulated cdrom. The installer does boot from the cdrom, but later gives up, saying that it can''t find the install CD. I''ve done all sorts of messing around with virsh and the qemu monitor, but

I recently brought up our fifth Samba domain member server with 3.0.26a-0.9-1787-SUSE-SLES9 against an NT4 domain on a new subnet. The subnet also has an NT4 BDC that is working correctly. Wbinfo and getent both work properly but users can not get to the [homes] service but can get to another share that is on the same system. If I setup a share definition in smb.conf for myself as a home

Any ideas why a vfs module loads successfully then can't be found? [2005/01/30 03:52:08, 5] lib/util_seaccess.c:se_access_check(309) se_access_check: access (2) granted. [2005/01/30 03:52:08, 3] smbd/vfs.c:vfs_init_default(203) Initialising default vfs hooks [2005/01/30 03:52:08, 3] smbd/vfs.c:vfs_init_custom(229) Initialising custom vfs hooks from [/usr/lib/samba/vfs/audit.so]

We are trying to install a 32-bit SLES9-SP4 paravirtual machine on a 64-bit SLES10-SP1 Dom0 host from scratch. We have two problems: 1. The YaST2 VM creation tool fails to create a vm if a network card is selected. 2. The initial vm boots from the SLES9-SP4 iso file, but then complains it can''t find the installation source. Here is the /etc/xen/vm/file (after manually editing for a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This patch teaches the sles9 spec file to understand that configfs is built conditionally, and may not be present in the output. - -Jeff diff -ruNp ocfs2-1.2.5/vendor/sles9/ocfs2.spec-generic.in ocfs2-1.2.5.devel/vendor/sles9/ocfs2.spec-generic.in - --- ocfs2-1.2.5/vendor/sles9/ocfs2.spec-generic.in 2007-03-27 15:54:15.000000000 -0400 +++

I am trying to get hotplugable USB support in a Windows HVM using Xen 3.2 on Fedora 8. I am running a Dell 755 workstation with VT-D support and I am attempting to use the PCI passthrough process to grab a USB controller from the workstation and make it available to the Windows XP DomU. I have successfully hidden the USB controller from Dom0 and my Windows XP VM does detect a "New USB

My head hurts from trying to figure this out for the past several hours . . . I want to determine what provider to use based on a fact (thanks for the suse version fact btw) but I ain''t gettin it: What''s wrong? Am I going down the completely wrong path? Is there a better way? # suse-yum.pp case $suse_repo_name { #sled10-i586: {Package{ provider => rug}} sled10-i586:

Hello, I try to compile pigeonhole ( hg clone from yesterday ) on SLES9 I get the following error: ---- snip cd dovecot-2.0-pigeonhole ./autogen.sh configure.in:17: option `tar-ustar' not recognized autoreconf: automake failed with exit status: 1 --- snap automake-1.8.3 autoconf-2.59 I found something similar here: http://osdir.com/ml/science.robotics.orocos.devel/2006-03/msg00029.html

hi, just to complete the story: i downloaded the iso-images of SLES9-SP4_x86_64 from novell and found inside ocfs2-tools and ocfs2console, both version 1.2.1. :-( we solved our problem without resizing the FS for now, but it would have been less complicated with resizing. perhaps we should consider upgrading to SLES10... :-D greetz, thomas

I'm running Samba 3.0.9 on SLES9 as a domain member with an NT4 PDC, using winbind to authorise domain users. I have set up a general share for all users which works fine and is accessible by all users but I am unable to set up the home shares correctly. When attempting to connect via smbclient I get the following:- tree connect failed: NT_STATUS_ACCESS_DENIED What does this mean and where

Hello everybody, I''am trying to make an installation of a sles9 based system. In order to install this system after booting a floppy disk (or usb) should be "inserted" with a auto configuration file. My problem is what ever I try I can not attach a floppy image to the sles9. the command I tried is xm block-attach <dom nr> file://path/to/floppy.img /dev/fd0 w After

Hi, I'm installing CentOS5 on a HP DL380-G4 server with 4Gb RAM. It had SLES9 on it, and SLES9 find all the RAM. But now CentOS5 x86_64 can't find all the RAM. From free: [root at Suzuka ~]# free total used free shared buffers cached Mem: 3986376 1591996 2394380 0 113896 1180852 -/+ buffers/cache: 297248

Hi, I don't know if this is a problem of SLES11 or winbind itself. I recently installed the lastest samba winbind 3..5.2 on a SLES9 box and a SLES11 box. If I remove a user from a group in Active Directory the change is visible immediately on the SLES9 box but not on the SLES11 box. Both are running exactly the same version of winbind: gedaiv64:~ # cat /etc/SuSE-release SUSE Linux

Hi 3.0.23rc3 pam_winbind on SLES9/i386 with the provided RPMs doesn't work: PAM unable to resolve symbol: pam_sm_authenticate PAM unable to resolve symbol: pam_sm_setcred Is this a compile problem ? SLES9 specific ? I am trying to setup the cool Kerberos integration that Samba can do for Linux. Can anyone point me to docs about that ? Thanks, Schlomo