similar to: SLES10 SP1 3.0.32 - Excel files set read only

We have setup a Samba member server using Winbind (3.0.14a and NT4). I am trying to "map" the NT Domain ids to root (root = admin administrator rdehn) but this seems to be ignored when I try and connect to a share. The "username map = /etc/samba/smbusers" line is in the Global section of smb.conf and testparm is OK. What am I missing? Is this not possible? Thanks in

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

All - We are using 3.0.20a on SLES 9 and are trying to configure a member server for our NT4 domain. The wbinfo commands (-u and -g) show correct information. The getent commands (passwd and group) work fine also. If Samba is running without winbind, I can see the shares in the config file (net view \\xxxxxxxx) from a PC. With winbind running I get an error message about the computer name

Hi, After some hard trying to use lustre on our debian servers with an up2date kernel I decided to buy sles10 to make everything more comftable: I installed (rpm -i) the new kernelbinaries from 1.6.2/sles10-i686 to a sles10 test box (AMD64). When i try to install the modules form 1.6.2/sles10-i686 it says : sles2:/usr/src/lustre # rpm -i

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

I''ve just set up a small lustre installation on mixed SLES10 32-bit and SLES10 SP1 64-bit. 32-bit would give ksym errors upon installation of modules rpm, while 64-bit SP1 it was only warnings. I did a little research on the ksym package and it seemed to me it was only needed if you were trying to install a module compiled for a different kernel version. Since CFS is providing a

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

Hi, I''m trying to build non sles10 domU under sles10 dom0. I''ve downloaded centos and debian images from www.jailtime.org fixed the config file and try to start domU. After creating domU from images I get Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I''m running without problems two sles10 domU machines. After using google allot :-)

I start sles10 use kernel-xen, but there''re not NIC eh0, and only have xenbr0, but the xenbr0 cannot get IP address via DHCP, (in normal sles10, the eth0 can get IP via DHCP), how can I connect to Internet in kerne-xen via xenbr0? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi Mark, I had this same issue trying to install SLES9SP4 PV on to SLES10SP1 host. You cannot do this. You can however install a SLES9SP4 FV guest. If you want a PV SLES9SP4, you will need SLES10SP2. -A _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I''ve just uneventfully installed SLES10 as an HVM DomU (after finding out, the hard way, that OpenSUSE 10.3 won''t install on Intel VT). This almost went without a hitch, but I''ve been banging my head against a brick wall for a few hours trying to get VNC working. I can get a remote desktop, but a few seconds after I log in to the remote desktop, the screen goes

Hi, We have configured several xen guest OSes on a server running SLES10. The physical server is a Sun 4200 with 3 NICs installed, configured, and working. Each of the xen guest OSes have three virtual nics, configured for RAC, Interconnect, and public IPs as follows; eth0 - public (routable and registered in DNS) eth1 - private (not routable, uses a seperate network subnet for

Hi, I thought about changing the RPM package the guys of Redhat created, because I wanted an Init Script for SLES10 built-in. I started documenting the steps I took. Maybe it''s useful for someone else, although in German.. but the basic steps should be useable. My little Installating puppet Howto: http://wiki.njh.eu/Konfigurationsmanagement#Installation_3 The Init Script for SLES10:

Hi,All, how can I install suse sles10 as para Dom-U on RHEL5, I have update xen to 3.2. In python-virtinst readme,there is only support Fedora/Red Hat Enterprise Linux. README of python-virtinst: virtinst is a module to help in starting installations of Fedora/Red Hat Enterprise Linux related distributions inside of virtual machines. It supports both paravirt guests (for which only FC and

Hi, I have a problem with augeas, puppet and Suse 10 SP2. Augeas works when I use the augtool to edit files. But I would like to use it in combination with puppet. My class looks something like this: augeas {"sysctl.conf": provider => "augeas", context => "/files/etc/sysctl.conf", changes => [ "set

Hello friends! In this week, i had a problem with Xen version 3.0.2_09749-0.7 on SLES10 for x86, when the initrd-xen file was loaded. On console, various messages about "No space left on device" appears later that the "/dev" was monted on a tmpfs filesystem (for udev). The only sollution for this problem at that moment, was remove the "dom0_mem=192M" and the

Hello, my apologies for not being sure whom to tell this problem, but it is very strange. Let me tell the story: I''m using XEN (3.0.2) with SLES10 (x86_64, SunFire X4100). On one machine I have three virtual machines ("DomU") that are very identically configured (SLES10 x86_64 also). There is also a SLES9 (i386) acting as a multi-homed NFS server. I can mount and access a

Hello, First, thanks to all the people who helped to license this software under the GPL. This is a very important piece of work for the Free Software in the Enterprise Market. Just a few newbie questions. We've been thinking about implmenting a mail cluster with a Fiber SAN (IBM DS-4000) and OCFSv2 as the storage backend. The information on this volume will essentially be Postfix Maildirs,

I am having issues with guest OSes running on SLES10 (Sun 4200) hosts. Periodically, the guest OS system drops off the network. From the general network it is not pingable, consequently, ssh fails. If however, I log into the SLES10 server that is hosting the guest OS and ssh to the guest OS, then it becomes immediately pingable and accessible to the rest of the network. Almost like the

Hello CFS, I was wondering if the new SLES10 kernel will be part of the 1.6.4 release. It appears to be tracked by: https://bugzilla.lustre.org/show_bug.cgi?id=13874 As this contains a major security fix (privilege escalation), it is a mandatory upgrade in many places and it would be nice to not have to roll our own kernel. Thanks, Kit