| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Using bash on the initrd.img now, but make sure we keep the
/bin/sh link.
|
|
|
|
|
|
| |
New NetworkManager appeared in rawhide that does not perform
UTF-8 conversions on DHCP options, so we don't need to include
/usr/lib/gconv in the install image.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Finally, no more libdhcp.
This is the first set of changes to take anaconda over to
the wonderful world of NetworkManager. We are no longer
linking with libdhcp to do interface configuration. NM
is started early in the installation and opens the door
to things like WPA installation support and things like
that.
|
|
|
|
|
|
| |
To make the installation image files more clear and since
we have removed minstg2.img, rename stage2.img to
install.img.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
kernel-xen is dead, replaced now with pv_ops Xen guest
support in the stock kernels.
On x86_64 and ia64, we now just point the [images-xen]
.treeinfo stanza at the stock kernels in images/pxeboot.
On x86_32, things are a bit more complicated. The stock
kernel is kernel.i586 but Xen guests support is only
included in kernel-PAE.i686 because Xen only runs in PAE
mode.
In this case, we just copy the kernel-PAE vmlinuz to
images/pxeboot/vmlinuz-PAE and build another initrd as
images/pxeboot/initrd-PAE.img. It's these images we point
the [images-xen] stanza at.
Signed-off-by: Mark McLoughlin <markmc@redhat.com>
|
| |
|
|
|
|
|
|
|
|
| |
Do not remove the anaconda-runtime or syslinux directories
before calling doPostImages. We need files from there for
the mkisofs step. In makemainimage, make sure we exclude
the anaconda-runtime and syslinux directories when making
the second stage image there.
|
|
|
|
|
| |
Fix up some errors in mk-images and upd-instroot that are
preventing images from building correctly.
|
|
|
|
|
|
| |
The minstg2 image has outlived its usefulness. We are at
a point where we have been maintaining two stage 2 images
and they are slowly becoming identical.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The s390 can boot El Torito CD or DVD images iff they are attached
by zFCP, used as the IPL device, and contain a specially formatted
boot image on the disc. IBM provided the tool to combobulate the
boot image together and a description of the desired execution
path.
When you boot on s390, the linuxrc.s390 will look to see if you
IPL'ed from a CD or DVD. If you did, it will ask if you also
want to install from that device. If you answer yes (y, Y, or
any case spelling of 'yes'), the script will bring the IPL device
online so the kernel assigns it a device name. Then it skips over
the network configuration and starts you in to loader. If you
tell it no or did not IPL from a CD or DVD, it'll launch the
missiles--wait, no, I mean you get the normal network installation
questions before loader starts.
I have no way to test this as it requires the following changes:
(1) Rel-eng needs to build s390x media with -no-emul-boot and
specify the new cdboot.img file on that platform. I have
already contacted rel-eng about making this change.
(2) I don't have a CD-ROM drive in my mainframe. IBM does and
testing is all falling on them. IBM knows this...maybe.
I explain all of this like anyone else on the team will ever get a
chance to experience it.
So there you have it. A letter opener.
|
| |
|
|
|
|
|
| |
udev is stopping supporting udevcontrol/udevtrigger as symlinks, so we
should change what we call
|
|
|
|
|
| |
Avoid having two copies of the dynamic linker in the
initrd.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The attached patch makes anaconda stop neutering DRI/DRM (at least it should.)
It does it by including the DRI userspace modules (from mesa) and the kernel
DRM drivers.
Why do this?
To be more like the 'normal' installed system. Heck, if DRI's going to fail,
the system's just going to blow up on the first boot anyway. Furthermore,
there are cards/chips that do 2D accel via the 3D pipeline.
Plus, if we want to actually disable it in anaconda, we should do it
explicitly, not by accident as a consequence of some files not being
there.
Caveats:
- listing the kernel drivers explicitly is a hack
- this doesn't pull libGL onto the second stage. Assuming nothing dlopens()
it, that shouldn't be a problem
|
| |
|
| |
|
|
|
|
| |
The default ls alias does not use -F, so removed that.
|
|
|
|
|
| |
Make the prompt and ls command more like the final system.
Removed \u@\h from the prompt, but it's still more useful.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
notting removed module balls some time ago:
commit 7971fbec83064b096a6592055d66df573bdb8eea
Author: Bill Nottingham <notting@redhat.com>
Date: Wed Dec 19 14:53:45 2007 -0500
Don't ship module balls; just ship a 'normal' /lib/modules and /lib/firmware tree.
but mk-images still has some remnants of them.
Signed-off-by: Mark McLoughlin <markmc@redhat.com>
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
The ia64 kernel is under /boot/efi not /boot. Fix up our finding
of the vmlinuz (patch from Yi Zhan <yi.zhan@intel.com> #441470)
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
| |
uname -r as reported by the kernel should be figured out based on some files
that get written, not by depending on "knowing" that it's version-release
|
| |
|
| |
|
|
|
|
|
|
| |
At least for in the tree, having the ISO as boot.iso helps tools such
as virt-manager, which is a convincing reason to leave it. When pungi
copies into the iso/ directory, it's probably reasonable to change the name
|
|
|
|
|
|
|
| |
This is necessary on ppc where we are trying to download the ppc64
kernel from a ppc environment. Requires an updated yum-utils that
supports the --archlist option to yumdownloader, but I don't know
the n-v-r of that build yet, so no change to anaconda.spec yet.
|
|
|
|
|
|
| |
This is necessary for composing ppc, where the compose is done on ppc, but we
want to find a ppc64 kernel. By default, repoquery won't return results that
don't match the running arch.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Stop building boot.iso (and diskboot.img) in preference for building a
netinst.iso with the boot bits as well as the second stage. This will
replace the rescue image and is overall far more useful
|
|
|
|
|
|
| |
Instead of doing tricks with find, use repoquery and yumdownloader to download
things like anaconda-runtime and kernels and firmware packages. This also
has the nice side effect of letting us run buildinstall against an http repo
|
| |
|
| |
|
|
|
|
|
|
|
| |
Use named options when passing things to mk-images so that it's more
clear as to what's going on. Also, make things like arch more explict.
This also adds support for output from mk-images to go elsewhere, although
that's currently not used by anything
|
| |
|