|
Bugzilla – Full Text Bug Listing |
| Summary: | Missing Files for BootX installation | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Forgotten User v5inq2MBSE <forgotten_v5inq2MBSE> |
| Component: | Installation | Assignee: | Ruediger Oertel <ro> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | coolo, snwint |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | PowerPC | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | extract_inst32.sh | ||
|
Description
Forgotten User v5inq2MBSE
2007-10-13 13:48:32 UTC
No idea where these files should come from or if the wiki page is outdated Created attachment 181019 [details]
extract_inst32.sh
something like the attached helper script should run before syncing the factory tree or the final openSuSE release to the internet install repository.
extract_inst32.sh
#!/bin/bash
# $0 CD1/suseboot/inst32 CD1/suseboot/linux32 CD1/suseboot/initrd32.gz
input_zimage_initrd=$1
output_vmlinux=$2
output_initrd_gz=$3
rm -fv "$output_vmlinux" "$output_vmlinux".gz
objcopy \
-O binary \
-j .kernel:vmlinux.strip \
"$input_zimage_initrd" \
"$output_vmlinux".gz
gunzip -fv "$output_vmlinux".gz
rm -fv "$output_initrd_gz"
objcopy \
-O binary \
-j .kernel:initrd \
"$input_zimage_initrd" \
"$output_initrd_gz"
Thank you Olaf, the script works fine. It's no problem to install openSUSE with the extracted files and BootX. I'm sorry I was not able to report the bug earlier, but my PowerBook was defect, three years. I've managed to repair it on the weekend after 10.3 was released (yes, it was no high priority). shouldn't this be done in the installation-images specfile ? From the report it sounds as if it used to be done there and was removed lately. Olaf? if it comes from installation-images, the 4 files will end up on the DVD. This should be avoided. Thats why I'm asking for a factory/release only solution. Then you could place the files in the FTP directory in installation-images; that's how we deal with bootdisk images on i386. Or you might want to just provide that script above and let the user create the files. I have adjusted the script for factory. fixed in installation-images on dec3/2007 by snwint |