| Summary: | genkernel leaves initrd.gz in /tmp | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Drake Wyrm <lilwyrm> |
| Component: | [OLD] Core system | Assignee: | Daniel Robbins (RETIRED) <drobbins> |
| Status: | VERIFIED FIXED | ||
| Severity: | trivial | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Fixed in 1.6; will be online soon. Thanks! |
When genkernel runs, it creates the file /tmp/initrd.gz, but doesn't clean up before exiting. Reproducible: Always Steps to Reproduce: 1. run genkernel 2. ls /tmp 3. Profit! Actual Results: genkernel debris in /tmp Expected Results: genkernel should clean up after itself I am leaving out the 'emerge info' dump, as this seems pretty irrelavent. This bug could be fixed by either changing 'cp -f ${TEMP}/initrd.gz /boot/initrd-${KV}' to 'mv -f ${TEMP}/initrd.gz /boot/initrd-${KV}' in the initrd() function or by adding 'rm -f ${TEMP}/initrd.gz' to the finish() function.