Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 204087
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Genkernel Maintainers <genkernel@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Marek Szuba <Marek.Szuba@if.pw.edu.pl>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
genkernel-gen_initramfs.sh-rm_busybox_tar.patch genkernel-gen_initramfs.sh-rm_busybox_tar.patch patch Marek Szuba 2008-01-02 17:55 0000 565 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 204087 depends on: Show dependency tree
Bug 204087 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2008-01-02 17:54 0000 
Hello,

While building an initramfs image using the bincache package of busybox,
genkernel places the bincache tarball into the subdirectory bin/ of the
directory initramfs is built from and does not remove it after it has been
unpacked; this causes the final initramfs image to become unnecessarily large.
Attached you will find a patch which removes the tarball after it's been used.
I suppose one could modify the script in question otherwise, i.e. have it
unpack the tarball directly from the cache directory and thus skip both the
copying and the removal altogether.

------- Comment #1 From Marek Szuba 2008-01-02 17:55:09 0000 ------- 
Created an attachment (id=139890) [details]
genkernel-gen_initramfs.sh-rm_busybox_tar.patch

------- Comment #2 From Chris Gianelloni (RETIRED) 2008-01-11 23:42:17 0000 ------- 
Thank you for the patch.  I fixed it to extract directly from the
BUSYBOX_BINCACHE, rather than copying it.

------- Comment #3 From Chris Gianelloni (RETIRED) 2008-01-12 00:51:17 0000 ------- 
This should be resolved in genkernel 3.4.9, which will be hitting the tree
shortly.  If this is still an issue with that version, please REOPEN this bug
(or comment, if you cannot REOPEN it).
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug