Re: Defaut browser
by Alexandre Strube
Em Ter, 2005-01-04 às 10:27 +0100, Philippe Alain escreveu:
> Bonjour,
>
> I think that Firefox is not a good choice for a default browser (for example,
> there are no translations or with some bugs). Why not a stable Gnome browser
> as Epiphany ?
Firefox is getting mature right now. The translations are coming.
Anyway, mozilla has never had my language on redhat/fedora, so my
customers does not seem to care.
19 years, 3 months
New testing kernel. 2.6.10-1.727_FC3
by Dave Jones
A new year, (another) new testing kernel. This rebases
the whole tree to the latest upstream release 2.6.10,
with the 2.6.10-ac2 patch on top for good measure.
With around 4000 changes between 2.6.9 and 2.6.10,
this fixes a lot of problems, including the infamous
'ACPI wont turn off my computer' bug.
No doubt it accidentally brings along new regressions,
so please, jump on it for a while, and once the worst
bits are shaken out, I'll push this out as an update.
This is not the same as the 2.6.10 in rawhide, as that
one is tracking the daily -bk snapshots heading toward
2.6.11, whilst FC3 will get a 2.6.10-ac update.
Thanks,
Dave
19 years, 3 months
smp 724_FC3 can't read superblock on ext3 filesystem
by Anne & Lynn Wheeler
i've been running smp 681_FC3 kernel w/o any apparent problems. I
recently tried smp 724_FC3 and it aborted pretty early in the boot
process claiming that it couldn't find superblock on ext3 filesystem
19 years, 3 months
RE: FC 3 and Kernel Lock or Hang
by Browder, Tom
> -----Original Message-----
> From: fedora-test-list-bounces(a)redhat.com
> [mailto:fedora-test-list-bounces@redhat.com] On Behalf Of Alan Cox
> Sent: Tuesday, January 04, 2005 10:51 AM
> To: For testers of Fedora Core development releases
> I've got the ASUS one. I would say that nowdays there isnt
> any point getting dual athlon boards given their slow
> performance relative to a modern system.
But why are we now having problems not evident with the FC 1 kernels?
Thanks.
Tom Browder
19 years, 3 months
Fedora Core 2 Test Update: system-config-kickstart-2.5.19-1.fc2
by Chris Lumens
---------------------------------------------------------------------
Fedora Test Update Notification
FEDORA-2004-588
2005-01-04
---------------------------------------------------------------------
Product : Fedora Core 2
Name : system-config-kickstart
Version : 2.5.19
Release : 1.fc2
Summary : A graphical interface for making kickstart files.
Description :
Kickstart Configurator is a graphical tool for creating kickstart files.
---------------------------------------------------------------------
Update Information:
This update fixes bug #143946, where system-config-kickstart cannot
load kickstart configuration files. It also incorporates all the
other fixes and improvements that have taken place since the FC2
version of this utility. Please test that your existing kickstart
files can be loaded, edited, and saved by this new version. This
update will be pushed to final updates on January 11, 2005 if no
major problems are found. Problem reports to clumens(a)redhat.com.
---------------------------------------------------------------------
* Tue Jan 04 2005 Chris Lumens <clumens(a)redhat.com> - 2.5.19-1.fc2
- Rebuilt 2.5.19 for Fedora Core 2 to fix #143946.
* Mon Dec 20 2004 Chris Lumens <clumens(a)redhat.com> - 2.5.19-1
- Fixed a segfault in pygtk on the partitioning screen.
- Fixed RAID editing screen so the config values don't change if you
repeatedly edit a RAID volume.
* Fri Dec 10 2004 Chris Lumens <clumens(a)redhat.com> - 2.5.18-1
- Get package group lists and their translations out of the comps.xml
file instead of relying on a built-in (and out of date) list.
- Added an "Install Everything" button (#134679).
* Thu Dec 02 2004 Chris Lumens <clumens(a)redhat.com> - 2.5.17-1
- Remove obsolete dependency resolution radio buttons.
* Tue Nov 23 2004 Chris Lumens <clumens(a)redhat.com> - 2.5.16-1
- Fix display in indic locale (#138310) and (#138601)
- Monitor order (#127477)
- Translation of RAID message (#127687)
- Unencrypted root passwords (#134678)
- Broken nfs line parsing (#134681)
* Fri Oct 01 2004 Paul Nasrat <pnasrat(a)redhat.com> - 2.5.15-1
- Translations
* Tue Sep 21 2004 Paul Nasrat <pnasrat(a)redhat.com> - 2.5.14-1
- ks.cfg parsing errors
* Tue Sep 07 2004 Paul Nasrat <pnasrat(a)redhat.com> - 2.5.13-1
- i18n .desktop
* Mon Sep 06 2004 Paul Nasrat <pnasrat(a)redhat.com> - 2.5.12-4
- PyGTK API fix
* Tue Aug 10 2004 Paul Nasrat <pnasrat(a)redhat.com> - 2.5.12-3
- Fix for mouse autoprobe (#129504)
* Mon Aug 02 2004 Paul Nasrat <pnasrat(a)redhat.com> 2.5.12-2
- fix Japanese man page encoding (bug #128767)
* Wed Jun 23 2004 Brent Fox <bfox(a)redhat.com> - 2.5.12-1
- use base names for packages (bug #122755)
* Thu Jun 17 2004 Brent Fox <bfox(a)redhat.com> - 2.5.11-3
- comps name changed for KDE (bug #124612)
- format of rhpl mouse dict changed (bug #125361)
* Tue May 25 2004 Brent Fox <bfox(a)redhat.com> 2.5.11-2
- handle missing mouse line (bug #124341)
- use N_ instead of _ in packages.py (bug #124144)
- remove code for dead firewall widgets (bug #124342)
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/2/
91d90cfbcdf0db6cb6f526906740c8f1 SRPMS/system-config-kickstart-2.5.19-1.fc2.src.rpm
cd470a7301f12946959663ff27cba9c4 x86_64/system-config-kickstart-2.5.19-1.fc2.noarch.rpm
cd470a7301f12946959663ff27cba9c4 i386/system-config-kickstart-2.5.19-1.fc2.noarch.rpm
This update can also be installed with the Update Agent; you can
launch the Update Agent with the 'up2date' command. You may
need to edit your up2date channels configuration. Within
/etc/sysconfig/rhn/sources enable the following line:
yum updates-testing http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/2...
---------------------------------------------------------------------
19 years, 3 months
re: a modest request
by gslink
The problem with bad sectors is not with sectors that show a write check
but with those that don't show a write check but are bad. The write
check on most hard drives is very simple and consists only of parity.
If a certain number of bits are dropped then there will be no write
check and install will work perfectly. You will never know about this
until you try to run the program because there will be no read error.
In addition there is the case where buffers are being allocated. No
check of media integrity is made on these(swap partition). This has
always been a problem with RH. Most shops have discs with small bad
spots and many discs develop these over time. The c option was put into
mkfs just to take care of these problems. At the present time we must
take ANY disc that displays even a small bad spot and use mkfs on
another system before we can install Linux. I suspect that a surprising
number of the strange troubles that are being reported by only one user
are due to this problem. When you invoke Disc Druid you need to be able
to request a long format or else mkfs needs to be on the recovery disc.
Currently discs are tested at the factory and bad sectors are locked
out In some large discs there are quite a few bad spots. In normal
operation perfectly good discs will have bad spots develop over time.
This is not a serious problem with modern discs if it is handled by the
software. The problem has always been that RH doesn't handle the
problem. Incidently, Microsoft does.
19 years, 3 months
USB2 trouble: EHCI HCD died
by Michael J Gruber
Sorry for cross-posting, but this refers to FC3 and FC4 alike:
I have an external USB2 hard disk and a PCMCIA USB2 controller. With
kernel 2.6.5 (Knoppix) both are recognized, EHCI picks up the device and
runs it at "high speed" (USB2 speed); on two different laptops (Dell and
Toshiba, both Intel 32 architecture).
With FC3 and the standard kernel-2.6.9-1.667, the USB2 controller is
recognized and EHCI picks up. When I plug in the USB2 hard disk, EHCI
gives up on it (ehci_hcd 0000:03:00.2: fatal error, ehci_hcd
0000:03:00.2: HC died; cleaning up), OHCI picks up instead and drives
the device at "full speed" (USB1 speed). Of course the drive works this
way, but about 20 to 40 times slower than with kernel 2.6.5. This
happens with kernel .681 as well, on the two different laptops mentioned
above.
I hoped 2.6.10 would cure this, but the same happens when I run FC3 with
the FC4 kernel 2.6.10-1.1063_FC4; that's why I am cross-posting to the
test-list. (The FC4 kernel works nicely on FC3 otherwise.)
Has anyone experienced symptoms like these? Is anyone driving USB2
devices at high speed successfuly with FC3/4?
Thanks for any hints!
Michael
Jan 3 22:18:54 kolibri kernel: PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
Jan 3 22:18:54 kolibri kernel: ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 10 (level, low) -> IRQ 10
Jan 3 22:18:54 kolibri kernel: ohci_hcd 0000:03:00.0: OHCI Host Controller
Jan 3 22:18:54 kolibri kernel: ohci_hcd 0000:03:00.0: irq 10, pci mem 12dc8000
Jan 3 22:18:54 kolibri kernel: ohci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 3
Jan 3 22:18:54 kolibri kernel: hub 3-0:1.0: USB hub found
Jan 3 22:18:54 kolibri kernel: hub 3-0:1.0: 3 ports detected
Jan 3 22:18:54 kolibri kernel: PCI: Enabling device 0000:03:00.1 (0000 -> 0002)
Jan 3 22:18:54 kolibri kernel: ACPI: PCI interrupt 0000:03:00.1[B] -> GSI 10 (level, low) -> IRQ 10
Jan 3 22:18:54 kolibri kernel: ohci_hcd 0000:03:00.1: OHCI Host Controller
Jan 3 22:18:54 kolibri kernel: ohci_hcd 0000:03:00.1: irq 10, pci mem 12dca000
Jan 3 22:18:54 kolibri kernel: ohci_hcd 0000:03:00.1: new USB bus registered, assigned bus number 4
Jan 3 22:18:56 kolibri kernel: hub 4-0:1.0: USB hub found
Jan 3 22:18:56 kolibri kernel: hub 4-0:1.0: 2 ports detected
Jan 3 22:18:56 kolibri kernel: PCI: Enabling device 0000:03:00.2 (0000 -> 0002)
Jan 3 22:18:56 kolibri kernel: ACPI: PCI interrupt 0000:03:00.2[C] -> GSI 10 (level, low) -> IRQ 10
Jan 3 22:18:56 kolibri kernel: ehci_hcd 0000:03:00.2: EHCI Host Controller
Jan 3 22:18:56 kolibri kernel: ehci_hcd 0000:03:00.2: irq 10, pci mem 12dcc000
Jan 3 22:18:56 kolibri kernel: ehci_hcd 0000:03:00.2: new USB bus registered, assigned bus number 5
Jan 3 22:18:56 kolibri kernel: ehci_hcd 0000:03:00.2: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
Jan 3 22:18:56 kolibri kernel: hub 5-0:1.0: USB hub found
Jan 3 22:18:56 kolibri kernel: hub 5-0:1.0: 5 ports detected
Jan 3 22:19:09 kolibri kernel: ehci_hcd 0000:03:00.2: fatal error
Jan 3 22:19:09 kolibri kernel: ehci_hcd 0000:03:00.2: HC died; cleaning up
Jan 3 22:19:09 kolibri kernel: ohci_hcd 0000:03:00.0: wakeup
Jan 3 22:19:11 kolibri kernel: usb 3-1: new full speed USB device using address 2
Jan 3 22:19:11 kolibri kernel: usb 3-1: not running at top speed; connect to a high speed hub
Jan 3 22:19:11 kolibri kernel: scsi1 : SCSI emulation for USB Mass Storage devices
Jan 3 22:19:11 kolibri kernel: Vendor: WDC WD25 Model: 00JB-00GVA0 Rev: 08.0
Jan 3 22:19:11 kolibri kernel: Type: Direct-Access ANSI SCSI revision: 02
Jan 3 22:19:11 kolibri kernel: SCSI device sda: 488397169 512-byte hdwr sectors (250059 MB)
Jan 3 22:19:11 kolibri kernel: sda: assuming drive cache: write through
Jan 3 22:19:11 kolibri kernel: sda:Current sda: sense key No Sense
Jan 3 22:19:11 kolibri kernel: sda1 sda2 sda3 sda4 < sda5 >
Jan 3 22:19:11 kolibri kernel: Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ohci_hcd 0000:03:00.0: NEC Corporation USB
PCI: Setting latency timer of device 0000:03:00.0 to 64
ohci_hcd 0000:03:00.0: irq 10, pci mem d187e000
ohci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 3 ports detected
PCI: Enabling device 0000:03:00.1 (0000 -> 0002)
ohci_hcd 0000:03:00.1: NEC Corporation USB (#2)
PCI: Setting latency timer of device 0000:03:00.1 to 64
ohci_hcd 0000:03:00.1: irq 10, pci mem d19ac000
ohci_hcd 0000:03:00.1: new USB bus registered, assigned bus number 4
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
PCI: Enabling device 0000:03:00.2 (0000 -> 0002)
ehci_hcd 0000:03:00.2: NEC Corporation USB 2.0
ehci_hcd 0000:03:00.2: irq 10, pci mem d19d1000
ehci_hcd 0000:03:00.2: new USB bus registered, assigned bus number 5
ehci_hcd 0000:03:00.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 5 ports detected
usb 5-1: new high speed USB device using address 2
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: WDC WD25 Model: 00JB-00GVA0 Rev: 08.0
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 488397169 512-byte hdwr sectors (250059 MB)
sda: assuming drive cache: write through
sda: sda1 sda2 sda3 sda4 < sda5 >
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
USB Mass Storage device found at 2
Jan 3 21:56:34 kolibri kernel: PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
Jan 3 21:56:34 kolibri kernel: ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 10 (level, low) -> IRQ 10
Jan 3 21:56:34 kolibri kernel: ohci_hcd 0000:03:00.0: OHCI Host Controller
Jan 3 21:56:34 kolibri kernel: ohci_hcd 0000:03:00.0: irq 10, pci mem 0x10800000
Jan 3 21:56:34 kolibri kernel: ohci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 3
Jan 3 21:56:34 kolibri kernel: hub 3-0:1.0: USB hub found
Jan 3 21:56:34 kolibri kernel: hub 3-0:1.0: 3 ports detected
Jan 3 21:56:35 kolibri kernel: PCI: Enabling device 0000:03:00.1 (0000 -> 0002)
Jan 3 21:56:35 kolibri kernel: ACPI: PCI interrupt 0000:03:00.1[B] -> GSI 10 (level, low) -> IRQ 10
Jan 3 21:56:35 kolibri kernel: ohci_hcd 0000:03:00.1: OHCI Host Controller
Jan 3 21:56:35 kolibri kernel: ohci_hcd 0000:03:00.1: irq 10, pci mem 0x10801000
Jan 3 21:56:35 kolibri kernel: ohci_hcd 0000:03:00.1: new USB bus registered, assigned bus number 4
Jan 3 21:56:35 kolibri kernel: hub 4-0:1.0: USB hub found
Jan 3 21:56:35 kolibri kernel: hub 4-0:1.0: 2 ports detected
Jan 3 21:56:36 kolibri kernel: PCI: Enabling device 0000:03:00.2 (0000 -> 0002)
Jan 3 21:56:36 kolibri kernel: ACPI: PCI interrupt 0000:03:00.2[C] -> GSI 10 (level, low) -> IRQ 10
Jan 3 21:56:36 kolibri kernel: ehci_hcd 0000:03:00.2: EHCI Host Controller
Jan 3 21:56:36 kolibri kernel: ehci_hcd 0000:03:00.2: irq 10, pci mem 0x10802000
Jan 3 21:56:36 kolibri kernel: ehci_hcd 0000:03:00.2: new USB bus registered, assigned bus number 5
Jan 3 21:56:36 kolibri kernel: ehci_hcd 0000:03:00.2: USB 2.0 initialized, EHCI 1.00, driver 26 Oct 2004
Jan 3 21:56:36 kolibri kernel: hub 5-0:1.0: USB hub found
Jan 3 21:56:36 kolibri kernel: hub 5-0:1.0: 5 ports detected
Jan 3 21:56:53 kolibri kernel: ehci_hcd 0000:03:00.2: fatal error
Jan 3 21:56:53 kolibri kernel: ehci_hcd 0000:03:00.2: HC died; cleaning up
Jan 3 21:56:54 kolibri kernel: usb 3-1: new full speed USB device using ohci_hcd and address 2
Jan 3 21:56:54 kolibri kernel: usb 3-1: not running at top speed; connect to a high speed hub
Jan 3 21:56:54 kolibri kernel: scsi2 : SCSI emulation for USB Mass Storage devices
Jan 3 21:56:59 kolibri kernel: Vendor: WDC WD25 Model: 00JB-00GVA0 Rev: 08.0
Jan 3 21:56:59 kolibri kernel: Type: Direct-Access ANSI SCSI revision: 00
Jan 3 21:56:59 kolibri kernel: SCSI device sda: 488397169 512-byte hdwr sectors (250059 MB)
Jan 3 21:56:59 kolibri kernel: sda: assuming drive cache: write through
Jan 3 21:56:59 kolibri kernel: SCSI device sda: 488397169 512-byte hdwr sectors (250059 MB)
Jan 3 21:56:59 kolibri kernel: sda: assuming drive cache: write through
Jan 3 21:56:59 kolibri kernel: sda: sda1 sda2 sda3 sda4 < sda5 >
Jan 3 21:56:59 kolibri kernel: Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
19 years, 3 months
Re: Defaut browser
by Chuck Anderson
On Tue, Jan 04, 2005 at 10:27:29AM +0100, Philippe Alain wrote:
> Bonjour,
>
> I think that Firefox is not a good choice for a default browser (for example,
> there are no translations or with some bugs). Why not a stable Gnome browser
> as Epiphany ?
One that supported session management would be good. What a pain that
Firefox/Mozilla don't.
19 years, 3 months
Trying to trace why rpm is not working
by Paul F. Johnson
Hi,
rpm --vv gives me the following output when I try to install just about
anything. I need to be able to track down what has gone a miss for so
many packages to give me preun and postun errors (it's just about every
package on my machine that I try to install using rpm or via yum) and
need to get it sorted quite quickly.
Is it likely that I have two versions of the some package installed
which is causing the script error and if that's the case, how do I track
them down? (I'll guess at rpm -qa | grep - but I'm not sure how to only
list duplicates or even everything installed in alphabetical order)
D: ============== kernel-2.6.10-1.1056_FC4.i686.rpm
D: Expected size: 16773245 = lead(96)+sigs(180)+pad(4)+data
(16772965)
D: Actual size: 16773245
D: kernel-2.6.10-1.1056_FC4.i686.rpm: MD5 digest: OK
(5c8481c8999b44702da2be0f30f588e4)
D: added binary package [0]
D: found 0 source and 1 binary packages
D: opening db environment /var/lib/rpm/Packages joinenv
D: opening db index /var/lib/rpm/Packages rdonly mode=0x0
D: locked db index /var/lib/rpm/Packages
D: ========== +++ kernel-2.6.10-1.1056_FC4 i686/linux 0x0
D: opening db index /var/lib/rpm/Depends create mode=0x0
D: Requires: rpmlib(VersionedDependencies) <= 3.0.3-1 YES (rpmlib
provides)
D: opening db index /var/lib/rpm/Providename rdonly mode=0x0
D: read h# 852 Header SHA1 digest: OK
(f5148bed26f7c4c4a5558898d4383610569069e1)
D: Requires: fileutils YES (db
provides)
D: read h# 854 Header SHA1 digest: OK
(2bf0bc913297f811aea435020e287ab33034f1d2)
D: Requires: module-init-tools YES (db
provides)
D: read h# 492 Header SHA1 digest: OK
(44eb4c9dcf49b732335da2d8800c0380e4ae4646)
D: Requires: initscripts >= 5.83 YES (db
provides)
D: read h# 659 Header SHA1 digest: OK
(47f73590bf09a7586210d18bbb3c18d9c5b80f5b)
D: Requires: mkinitrd >= 4.1.15 YES (db
provides)
D: opening db index /var/lib/rpm/Basenames rdonly mode=0x0
D: read h# 68 Header SHA1 digest: OK
(21bd0b96e584da659d47243215e54c2e243a2e73)
D: Requires: /bin/sh YES (db
files)
D: Requires: /bin/sh YES (cached)
D: Requires: /bin/sh YES (cached)
D: Requires: rpmlib(PayloadFilesHavePrefix) <= 4.0-1 YES (rpmlib
provides)
D: Requires: rpmlib(CompressedFileNames) <= 3.0.4-1 YES (rpmlib
provides)
D: read h# 751 Header SHA1 digest: OK
(1ae380b9bd9b2abb08853d4442a724e0d6f81327)
D: Conflicts: ppp <= 2.3.15 NO
D: read h# 131 Header SHA1 digest: OK
(c2f3c39b4c7268b3a32f51cee2fd95c91ce22524)
D: Conflicts: pcmcia-cs <= 3.1.20 NO
D: read h# 983 Header SHA1 digest: OK
(6a8c0f0c44773fe59e67d2646bffcebb94c85c2f)
D: Conflicts: isdn4k-utils <= 3.0 NO
D: read h# 1037 Header SHA1 digest: OK
(26bce07e8f9848075583ef135909fbb048281c25)
D: Conflicts: mount < 2.10r-5 NO
D: opening db index /var/lib/rpm/Pubkeys rdonly mode=0x0
D: read h# 66 Header sanity check: OK
D: ========== DSA pubkey id b44269d04f2a6fd2
D: read h# 1003 Header V3 DSA signature: OK, key ID 4f2a6fd2
D: Conflicts: nfs-utils < 1.0.3 NO
D: read h# 796 Header V3 DSA signature: OK, key ID 4f2a6fd2
D: Conflicts: e2fsprogs < 1.29 NO
D: Conflicts: util-linux < 2.10 NO
D: Conflicts: jfsutils < 1.0.14 NO
D: Conflicts: reiserfsprogs < 3.6.3 NO
D: Conflicts: xfsprogs < 2.1.0 NO
D: read h# 746 Header SHA1 digest: OK
(8e7576b053285767a1423aab2ecd1b3e6cc14316)
D: Conflicts: procps < 2.0.9 NO
D: read h# 828 Header V3 DSA signature: OK, key ID 4f2a6fd2
D: Conflicts: oprofile < 0.5.3 NO
D: Conflicts: cipe < 1.4.5 NO
D: read h# 1020 Header SHA1 digest: OK
(fd0a8f8275c3eea26325cf32777c2411ab722eeb)
D: Conflicts: kudzu <= 0.92 NO
D: Conflicts: initscripts < 7.23 NO
D: read h# 684 Header SHA1 digest: OK
(ab2a234956bac6ed5d7c2d1c5949702dffe48ae7)
D: Conflicts: dev < 3.2-7 NO
D: read h# 480 Header SHA1 digest: OK
(0f5f0d98640ce57bac9f4bfc8b0124edcd19fbd8)
D: Conflicts: iptables < 1.2.5-3 NO
D: Conflicts: bcm5820 < 1.81 NO
D: Conflicts: nvidia-rh72 <= 1.0 NO
D: read h# 218 Header SHA1 digest: OK
(42cd02a992ff839079b193da3e02c69298f6b8e2)
D: Conflicts: SysVinit < 2.84-13 NO
D: read h# 742 Header SHA1 digest: OK
(9d248f1a3b7bd800bf97d6e55bfc5826fd06fbef)
D: Conflicts: pam < 0.75-48 NO
D: read h# 856 Header SHA1 digest: OK
(f28fa22e3a15d0e451f71cdd3082a5532ef2b6f2)
D: Conflicts: vixie-cron < 3.0.1-73 NO
D: Conflicts: privoxy < 3.0.0-8 NO
D: read h# 126 Header SHA1 digest: OK
(ef7b03d639df6c3527947d919bf87fa7fe0cc996)
D: Conflicts: spamassassin < 2.44-4.8.x NO
D: read h# 1027 Header SHA1 digest: OK
(0de24248a864a527a82079eb5f3d952004a376f4)
D: Conflicts: cups < 1.1.17-13 NO
D: opening db index /var/lib/rpm/Conflictname rdonly mode=0x0
D: read h# 261 Header SHA1 digest: OK
(bbf461f9d961f099cef7553c9c2b2f03a490a42a)
D: read h# 643 Header SHA1 digest: OK
(2be0d6f6f63c222df07d98522da42c1abcee5d3f)
D: read h# 660 Header SHA1 digest: OK
(d97f50add501eb55584e039f22f77a9d69100fb8)
D: read h# 674 Header SHA1 digest: OK
(ee78e8ed97377b5ce4cc4c964b702d9425164cdd)
D: Conflicts: kernel < 2.2.0 NO
D: Conflicts: kernel < 0:2.6 NO
D: Conflicts: kernel < 2.2.12-7 NO
D: closed db index /var/lib/rpm/Pubkeys
D: closed db index /var/lib/rpm/Depends
D: closed db index /var/lib/rpm/Conflictname
D: closed db index /var/lib/rpm/Providename
D: closed db index /var/lib/rpm/Basenames
D: closed db index /var/lib/rpm/Packages
D: closed db environment /var/lib/rpm/Packages
D: ========== recording tsort relations
D: ========== tsorting packages (order, #predecessors, #succesors, tree,
depth)
D: 0 0 0 0 0 +kernel-2.6.10-1.1056_FC4
D: installing binary packages
D: opening db environment /var/lib/rpm/Packages joinenv
D: opening db index /var/lib/rpm/Packages create mode=0x42
D: mounted filesystems:
D: i dev bsize bavail iavail mount point
D: 0 0x0301 4096 6415763 3825198 /
D: 1 0x0003 4096 0 -1 /proc
D: 2 0x0000 4096 0 -1 /sys
D: 3 0x0009 4096 0 -1 /dev/pts
D: 4 0x0010 4096 96984 96983 /dev/shm
D: 5 0x0305 4096 4217971 3623939 /usr
D: 6 0x0341 4096 14095612 9634914 /home
D: 7 0x0342 4096 4255400 4928919 /MP3
D: 8 0x2201 4096 6652654 10714788 /Programming
D: 9 0x2202 4096 7906951 4293625 /web
D: 10 0x2241 4096 7094245 14809266 /backup
D: 11 0x0012 4096 0 -1 /proc/sys/fs/binfmt_misc
D: 12 0x0013 4096 0 -1 /var/lib/nfs/rpc_pipefs
D: sanity checking 1 elements
D: opening db index /var/lib/rpm/Name create mode=0x42
D: read h# 643 Header SHA1 digest: OK
(2be0d6f6f63c222df07d98522da42c1abcee5d3f)
D: read h# 660 Header SHA1 digest: OK
(d97f50add501eb55584e039f22f77a9d69100fb8)
D: read h# 674 Header SHA1 digest: OK
(ee78e8ed97377b5ce4cc4c964b702d9425164cdd)
D: computing 8380 file fingerprints
D: computing file dispositions
D: opening db index /var/lib/rpm/Basenames create mode=0x42
D: ========== +++ kernel-2.6.10-1.1056_FC4 i686-linux 0x0
D: Expected size: 16773245 = lead(96)+sigs(180)+pad(4)+data
(16772965)
D: Actual size: 16773245
D: install: kernel-2.6.10-1.1056_FC4 has 8380 files, test = 0
D: install: %pre(kernel-2.6.10-1.1056_FC4.i686) asynchronous scriptlet
start
D: install: %pre(kernel-2.6.10-1.1056_FC4.i686) execv(/bin/sh) pid
5058
D: install: waitpid(5058) rc 5058 status ff00 secs 0.002
error: %pre(kernel-2.6.10-1.1056_FC4.i686) scriptlet failed, exit status
255
error: install: %pre scriptlet failed (2), skipping
kernel-2.6.10-1.1056_FC4
D: closed db index /var/lib/rpm/Basenames
D: closed db index /var/lib/rpm/Name
D: closed db index /var/lib/rpm/Packages
D: closed db environment /var/lib/rpm/Packages
--
"He's not the Messiah, he's a very naughty boy!"
- Life of Brian, Monty Python
19 years, 3 months