New answers tagged

2

In Suse start and stop order of services are managed by insserv package and based on dependency with other services. So it is little different. The answer to your question is given in details with examples in the following Suse article: Manipulating the start and stop order of Linux services Under the LSB (Linux Standards Base), the start and stop order ...


0

run sudo zypper install pam_ldap # then you will be able to run the following command with no error. pam-config --add --ldap The following files will be modified by the pam-config command /etc/pam.d directory: common-password common-auth common-session-pc This is the line was added auth required pam_ldap.so use_first_pass


1

You should be able to do it using file.sed: salt '*' file.sed /etc/zypp/zypp.conf '^(#|)\s*solver.allowVendorChange(.+)?$' 'solver.allowVendorChange = true'


1

And that's why you don't blindly following tutorials without knowing what they are talking about. Your installation doesn't use LVM so you can't extend the size of the disks by a method meant to increase LVM volume size.


0

Below worked for me for SUSE Linux Enterprise Server 11 v 11 .Both bonding , ipv4 and IPv6 host_name:/etc/sysconfig/network # cat ifcfg-bond0 STARTMODE='auto' BONDING_MASTER='yes' BONDING_MODULE_OPTS='mode=active-backup miimon=100' BOOTPROTO='static' IPADDR='10.120.xx.xxx/24' IPADDR_0='2607:f480:111:xxxx:xxxx:xxx:379:aaaa' PREFIXLEN_0=64 USERCONTROL='no' ...


2

There are generic file modification modules and states in SaltStack. For example, you could use file.replace: salt '*' file.replace /etc/zypp/zypp.conf pattern='solver.allowVendorChange = true' repl='solver.allowVendorChange = false' In case the line doesn't exist at all, you can append it to the configuration in a state using file.blockreplace: ...


2

The discrepance is mostly likely caused by more sparsely-populated file on the old disk. Anyway, let's first check that file and inode numbers are the same: issue find <path> | wc -l on both mountpoints. Is the number of file/directory the same? issue df -i. Is the number of inodes the same? If the answer to both question is yes, than the ...


0

Your rsync options won't copy hardlinks, try adding -H -H, --hard-links This tells rsync to look for hard-linked files in the transfer and link together the corresponding files on the receiving side. Without this option, hard-linked files in the transfer are treated as though they were separate files. When you are updating a non-empty destination, ...


0

It is most likely related to sparse files on the original filesystem.


0

When I've seen differences like this in the past it was usually due to a difference in the block size of the drives. This is especially true if the original drive is older. You can verify this with the following. tune2fs -l /dev/sdXX | grep -i 'block size'



Top 50 recent answers are included