similar to: /etc/passwd.rpmnew changes "x" to "*"

> From: Johnny Hughes <johnny at centos.org> > > In this case you DO NOT want to integrate these changes [...] > This issue was caused in CentOS-4 (a /etc/passwd.rpmnew file) > due to an > update to the "setup" rpm in March ... and in this case, you can > remove/ignore that file. Thank you for explaining all of this. Is this issue documented somewhere?

Matt Seitz (matseitz) would like to recall the message, "CentOS Digest, Vol 41, Issue 29". -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20080630/e1f9e3d1/attachment-0001.html>

Hi! System: Debian/testing with selfcompiled kernel 3.5.5 (same error with 3.4 or 3.6) XEN: 4.1.3 After booting the Dom0 I notice the following errors: [ 2.939078] microcode: CPU0 sig=0x1067a, pf=0x1, revision=0xa07 [ 2.991998] microcode: CPU0 update to revision 0xa0b failed [ 2.992035] microcode: CPU1 sig=0x1067a, pf=0x1, revision=0xa07 [ 2.995882] microcode: CPU1 update to

Hi, I''m currently trying to use a Linovo R61 Thinkpad equipped w/ Core2 Duo for HVM Virtualization. BIOS shows CPU/Virtualization->enabled. Xen 3.2.0 shows (Xeo) VMX disabled by BIOS Does someone knows any problems with R61 Thinkpads? Thanks in advance. cheers, Stephan -- Stephan Seitz Senior System Administrator *netz-haut* e.K. multimediale kommunikation zweierweg 22 97074

Hi! I have the following questions/problems with * 1.4. We have several Snom phones (320 and 360). Hints are configured in extensions.conf (core show hints shows the correct values). My Snom phone is registered to some numbers (validated by using sip show subscriptions). I see the lights blinking if someone calls the subscribed number and steady lights if the call is established. So far, so

Hi there, during peak load on some running domU, I noticed random iSCSI "Reported LUNs data has changed" which forced me to shutdown the respective domU, re-login the target and do a fsck before starting domU again. This occurred on a 16 core machine, having only about 14 domUs running. Spare memory has been occupied by dom0 (about 40G). Each domU has it''s own iSCSI target.

AFAICT our current version does not correspond to any version in the Linux history. This commit resynchronised to the state in Linux commit 598bae70c2a8e35c8d39b610cca2b32afcf047af. Differences from upstream: find_cpio_data is __init, printk instead of pr_*. This appears to fix Debian bug #785187. "Appears" because my test box happens to be AMD and the issue is that the (valid) cpio

Hi! Some persons are using a TAPI driver to connect via the manager interface to the asterisk (1.4). While I can give every user his own password, I didn?t find a way to restrict a user to a certain phone number, so that he can only dial with his number via the TAPI driver and can only answer calls for another number. Is the possible? If yes, how? Thanks for the answers. Shade and sweet

Hi I have a degraded array /dev/md2 ===================================================================== $ mdadm -D /dev/md2 /dev/md2: Version : 00.90.01 Creation Time : Thu Oct 6 20:31:57 2005 Raid Level : raid5 Array Size : 221953536 (211.67 GiB 227.28 GB) Device Size : 110976768 (105.84 GiB 113.64 GB) Raid Devices : 3 Total Devices : 2 Preferred Minor : 2

Hi Alexander, Not sure if this of any help, but we had a similar problem with runaway SMBDs and what seemed to be oplocks. We are running RH6.2 with 0.7.26 ACLs. After much messing around and hassling Jeremy, I eventually changed the kernel from 2.2.19 to 2.2.20 and recompiled everything from scratch. Since then we have not had one of these rogue processes. I think Jeremy was right when he

Thanks for replying to my question. However, I am still confused. Rafal Szczesniak <mimir@samba.org> wrote: >On Thu, Jul 17, 2003 at 08:58:30AM -0700, Matt Seitz wrote: >> The Samba web site contains "The Samba Team announces Samba 3.0.0 >> beta3". This document includes a section titled "Trust Relationships >> and a Samba Domain". For

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 d''morning listmembers, it''s about a few weeks now, i''m fiddling around with xen-unstable, patching, migrating compiling and even the hard job: learning the concept. by now, i''m wondering which testing environment you''re (well, some of you) using, to test the vt part of xen? even more strange, until now, no

I'm puzzled by such statements as diff /var/clamav/daily.cvd /var/clamav/daily.cvd.rpmnew Binary files /var/clamav/daily.cvd and /var/clamav/daily.cvd.rpmnew differ I thought the point of rpmnew files was so that we could check what has been changed? Anne -- New to KDE4? - get help from http://userbase.kde.org Just found a cool new feature? Add it to UserBase -------------- next part

The upgrade to 5.2 creates /etc/pam.d/system-auth.rpmnew. I see that /etc/pam.d/system-auth actually is a symlink to system-auth-ac. Is it recommended to replace that symlink with the rpmnew file? Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

Hi there, just a short question: Does someone know if it''s possible to use an USB HDD in one HVM domU? It doesn''t need to be the particular USB device, deligating the whole USB controller to this single domU wouldn''t hurt either. Also reconfiguration isn''t an issue, as - if it''s possible - USB devices would only be used by one domU. Thanks in

After you do your update, done forget to do updatedb, makewhatis, ... The locate for rpmnew has a couple items of interest and the locate for rpmsave returns one that occupies 24MB of your precious disks - /var/lib/Pegasus/prev-repository*. It compresses nicely to appx. 1MB, cpio bzipped --best. Change in your rndc key too, for DNS.

Hey, FYI, I just upgraded my 6.0 to 6.1 and saw: ... warning: /etc/shadow created as /etc/shadow.rpmnew ... # ll /etc/shadow.rpmnew ls: cannot access /etc/shadow.rpmnew: No such file or directory JD

On Tue, 2015-05-19 at 13:31 +0200, Stephan Seitz wrote: > On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: > >Here's an idea. First extract the real initrd from the back half of the > >initrd: > > ijc at dagon:tmp$ cat /boot/initrd.img | ( cpio -t >&2 ; cat ) > initrd.real > > kernel > > kernel/x86 > >

Hi, I''ve recently setup a few machines with 3.2 64bit without any unresolvable problem. These machines all run pv domU''s and a view "basic" hvm domUs. As I''ve got one machine left for internal use and testing, I would like to take a look at pciback with VT-d support (bios screen shows a VT-d [enable|disable]). My question is, do I need to add patches, or use

Hi, I''ve recently setup a few machines with 3.2 64bit without any unresolvable problem. These machines all run pv domU''s and a view "basic" hvm domUs. As I''ve got one machine left for internal use and testing, I would like to take a look at pciback with VT-d support (bios screen shows a VT-d [enable|disable]). My question is, do I need to add patches, or use