CVS: src/si/phase4/package-build kernel.xml,1.3,1.4

Mats Wichmann <[email protected]>
Newsgroups gmane.linux.lsb.implementation
Message-ID <[email protected]>
Update of /cvsroot/lsb/src/si/phase4/package-build
In directory sc8-pr-cvs1:/tmp/cvs-serv15590/phase4/package-build

Modified Files:
	kernel.xml 
Log Message:
For ia64, use /boot instead of /boot/efi since the prep steps
don't make a /boot/efi. The bootable kernel is supposed to go
under /boot/efi on an efi-enable system, but in a separate partition.
Thus, when we're building the -boot tarball it doesn't really matter
where we put it, so take the easy way out.


Index: kernel.xml
===================================================================
RCS file: /cvsroot/lsb/src/si/phase4/package-build/kernel.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -r1.3 -r1.4
*** kernel.xml	27 Sep 2002 14:54:15 -0000	1.3
--- kernel.xml	14 Jan 2003 19:09:39 -0000	1.4
***************
*** 82,87 ****
  			    <base>&phase4_build_dir;/&linux-directory;</base>
  			    <source>vmlinux.gz</source>
  			    <destination>
! 				&LSBsi-phase4-install;/boot/efi/vmlinuz-&linux-version;
  			    </destination>
  			</copy>
--- 82,90 ----
  			    <base>&phase4_build_dir;/&linux-directory;</base>
  			    <source>vmlinux.gz</source>
+ 			    <!-- ia64 should really go in /boot/efi, but
+ 			         since this isn't a bootable setup without
+ 				 manual intervention, bot in /boot -->
  			    <destination>
! 				&LSBsi-phase4-install;/boot/vmlinuz-&linux-version;
  			    </destination>
  			</copy>
***************
*** 90,94 ****
  			    <options>force</options>
  			    <base>&LSBsi-phase4-install;/</base>
! 			    <target>boot/efi/vmlinuz-&linux-version;</target>
  			    <name>vmlinuz</name>
  			</link>
--- 93,97 ----
  			    <options>force</options>
  			    <base>&LSBsi-phase4-install;/</base>
! 			    <target>boot/vmlinuz-&linux-version;</target>
  			    <name>vmlinuz</name>
  			</link>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.