Bug 83526
Summary: | up2date error | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Ole Skartveit <ole.skartveit> |
Component: | up2date | Assignee: | Bret McMillan <bretm> |
Status: | CLOSED WONTFIX | QA Contact: | Fanny Augustin <fmoquete> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 7.2 | CC: | gafton, mihai.ibanescu |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-04-22 15:01:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 120092 |
Description
Ole Skartveit
2003-02-05 09:42:42 UTC
would it be possible to get a copy of the lilo.conf file? lilo.conf: prompt timeout=50 default=cpq-2.4.9-e. # (previously, default=linux) boot=/dev/cciss/c0d0p1 map=/boot/map install=/boot/boot.b message=/boot/message linear image=/boot/vmlinuz-2.4.9-e.3smp label=linux initrd=/boot/initrd-2.4.9-e.3smp.img read-only root=/dev/cciss/c0d0p5 image=/boot/vmlinuz-2.4.9-e.3 label=linux-up initrd=/boot/initrd-2.4.9-e.3.img read-only root=/dev/cciss/c0d0p5 # The following entry was added by Compaq HBA install script image=/boot/vmlinuz-2.4.9-e.3smp label=cpq-2.4.9-e. initrd=/boot/cpq-initrd-2.4.9-e.3smp.img read-only root=/dev/cciss/c0d0p5 Hmm, thats a strange looking lilo.conf. Looks like the parser doesnt find the stanza for the label=cpq-2.4.9-e. bit. I'll take a look. up2date is no longer shipped with Fedora Core; it's functionality has been replaced by pup, found in the pirut package. The only fixes likely to be made to up2date in RedHat Linux and earlier Fedora Core versions are security fixes by Fedora Legacy. This does not seem to be a security bug, so I'm closing it. If the problem is appropriate to RHEL and occurs to a user there, it can be filed as such. |