| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Add vt320 terminfo files, remove bterm from the terminfo list (#219556).
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
In mk-images.ppc, remove the iSeries stuff. The ppc
community has stated that iSeries support is not longer
necessary.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
yum wants to look in installroot+/etc/yum.repos.d for config files, which
means it ends up looking under /mnt/sysimage. On fresh installs this is
no problem because that path does not exist, but on upgrades it does. We
end up with the wrong repo config objects in the upgrade case. The least
hacky fix is to change where we store repo config files to a path that
likely won't exist on installed systems.
|
| |
|
|
|
|
| |
live.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Since we don't create an anaconda-runtime package anymore, buildinstall
querying for it was going wrong. Admittedly this may be a problem with
repoquery and yumdownloader, and that will be investigated, but for the
sake of getting things working, I'm fixing it here.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
udev is stopping supporting udevcontrol/udevtrigger as symlinks, so we
should change what we call
|
|
|
|
|
|
| |
This option allows us to pass a mirrorlist into buildinstall instead of or in
addition to baseurls. This will allow the yum object to make use of a list of
potential mirrors should it have difficulties downloading something.
|
|
|
|
|
| |
Avoid having two copies of the dynamic linker in the
initrd.
|
|
|
|
| |
working directory /if/ it's a git+ssh checkout of anaconda.
|
|
|
|
| |
* po/sk.po: Typo fix.
|
| |
|
|
|
|
|
| |
busybox's shell isn't really happy running on tty2, it just exits immediately
whenever a command is run. Let's just switch to using bash
|
| |
|
| |
|
| |
|
|
|
|
| |
check that it's not our install image.
|
| |
|
| |
|
|
|
|
| |
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.
|