Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 434554 - [ia64] handbook update
Summary: [ia64] handbook update
Status: RESOLVED FIXED
Alias: None
Product: [OLD] Docs on www.gentoo.org
Classification: Unclassified
Component: Installation Handbook (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: nm (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 415175
  Show dependency tree
 
Reported: 2012-09-10 09:13 UTC by Raúl Porcel (RETIRED)
Modified: 2012-09-12 09:56 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
handbook-bootloader (hb-install-x86+amd64-bootloader.xml.diff,865 bytes, patch)
2012-09-10 09:14 UTC, Raúl Porcel (RETIRED)
Details | Diff
handbook-kernel (hb-install-ia64-kernel.xml.diff,2.95 KB, patch)
2012-09-10 09:15 UTC, Raúl Porcel (RETIRED)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Raúl Porcel (RETIRED) gentoo-dev 2012-09-10 09:13:36 UTC
I'm attaching some handbook updates to fix bug 415175, feel free to fix any wording before applying.

Also i've done some changes to the kernel location, since elilo likes to mount the /boot partition by itself, so copying the kernels+initramfs to /boot isn't a great idea(since it isn't mounted). Besides the elilo configuration example in the handbook uses /vmlinuz as a kernel, which means it will look for /vmlinuz in the root partition
Comment 1 Raúl Porcel (RETIRED) gentoo-dev 2012-09-10 09:14:51 UTC
Created attachment 323386 [details, diff]
handbook-bootloader

I have no idea why the elilo part is in the x86+amd64 handbook...
Comment 2 Raúl Porcel (RETIRED) gentoo-dev 2012-09-10 09:15:18 UTC
Created attachment 323388 [details, diff]
handbook-kernel
Comment 3 nm (RETIRED) gentoo-dev 2012-09-11 20:15:29 UTC
is there a reason why the ia64 bootloader/initramfs/genkernel instructions have to differ so much from the other arches?

i'd love to just program a single <include> that works across alpha/ia64/sparc, without having to copy-paste large chunks that differ by just a few lines. for example, i'm not sure why you removed the <keyval id="kernel-name"/> variable and replaced it with <c>vmlinuz</c>, when the existing code fetches the proper name from handbook-ia64.xml and fills in that space. your change replaces one variable with another, one that doesn't have an example filename.
Comment 4 nm (RETIRED) gentoo-dev 2012-09-11 22:52:13 UTC
fixed in CVS. split out the initramfs instructions to a cross-arch <include>, linked it into the doc, added <keyval> variables to handbook-*.xml for kernel/initrd versions.

(raúl, please double check that everything is okay per comment #3.)
Comment 5 Raúl Porcel (RETIRED) gentoo-dev 2012-09-12 09:56:24 UTC
(In reply to comment #3)
> is there a reason why the ia64 bootloader/initramfs/genkernel instructions
> have to differ so much from the other arches?
> 
> i'd love to just program a single <include> that works across
> alpha/ia64/sparc, without having to copy-paste large chunks that differ by
> just a few lines. for example, i'm not sure why you removed the <keyval
> id="kernel-name"/> variable and replaced it with <c>vmlinuz</c>, when the
> existing code fetches the proper name from handbook-ia64.xml and fills in
> that space. your change replaces one variable with another, one that doesn't
> have an example filename.

I just replaced the keyval thing because in the bootloader part it used /vmlinuz. So it wasn't in sync with the copying kernel part.

But I agree, feel free to rename vmlinuz everywhere to the keyval thingy