| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This is an attempt to make sure that everything anaconda's mounted during
a partially completed installation is unmounted and cleaned up. Note
that there's still plenty of opportunity for failures here depending on
where you restart anaconda. I think during package installation is
especially suspect.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This allows you to manually make changes to the new initrd before
the final build of the .iso
eg. Copy loader.debug over the top of /sbin/loader so that
backtrace will include useful symbols if a segfault is triggered.
|
| | |
|
| |
|
|
|
|
|
| |
Add options to leave tmp directory, skip iso creation and specify
an alternate destination directory.
Added support for f15
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This script allows you to update an existing boot.iso with a new
anaconda rpm. It also works on full DVD isos.
The current version does not work with rawhide's single initrd image
yet.
|
| |
|
|
| |
This conditionalizes adding support for UEFI when creating boot.iso
|
| |
|
|
|
| |
Due to changes related to gtk-3, we have to have Adwaita theme files in
the image to keep the nice themed look (buttons, window decorations).
|
| |
|
|
| |
Also rename loop.get_device_path to loop.get_backing_file.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
We need this command to handle clearing the cio_ignore blacklist.
Related: rhbz#633469
(cherry picked from commit fcbcea085aa69adbb082b75fbf285f9956cc30b9)
|
| |
|
|
| |
New name is anaconda-cleanup.
|
| | |
|
| |
|
|
|
| |
Part of the removal never happened in the first place, and part of it got
overwritten when I pushed the install image merging patch series.
|
| |
|
|
|
|
|
|
| |
We need this to change the IPL device before rebooting, plus it
fixes the broken lsreipl symlink in the initrd.img on s390x.
Related: rhbz#632325
(cherry picked from commit 2422dc268571269de3e172a90d13eecd78362598)
|
| | |
|
| |
|
|
| |
This should cover all the formats recognized by blkid. Finally.
|
| |
|
|
|
| |
Cleanup-only mode doesn't need passphrases for active LUKS devices
since it is only going to deactivate them.
|
| |
|
|
| |
More reliable than the rescue image...
|
| |
|
|
|
|
|
| |
Includes brcm_iscsiuio daemon for bnx2i cards as well as loading the
drivers and spawning the daemons in stage2 storage code.
Related: rhbz#442980
|
| |
|
|
| |
Related: rhbz#576439
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Multiple image files can be specified via "--image=/path/to/image[:name]"
on the anaconda command line. The name cannot contain colons.
Whenever disk images are specified, they automatically become the
only disks visible to anaconda, as if "ignoredisks --only-use" had
been used.
Fow now, only normal disk images are supported. Do not try to build
a fwraid or mpath in image files and expect anaconda to handle it
correctly.
Don't log to system log for disk image installs. For one thing, it adds
a huge amount of text to /var/log/messages. It also has some problem
that prevents subsequent attempts to connect to the syslog socket (from
anaconda_log.py, anyway) to fail.
Don't allow configuration of network devices during disk image installs.
Also, don't write anything in /etc/sysconfig on the host system
when doing image installs.
Don't start auditd when doing an image install.
Don't run setupTimezone if installing to disk image file(s). We don't
want to change settings on the host system.
Don't start or stop iscsi, fcoe, dasd, or zfcp during image installs.
|
| |
|
|
| |
Resolves: rhbz#654432
|
| | |
|
| | |
|
| |
|
|
| |
Related: rhbz#442980
|
| |
|
|
|
|
|
|
|
|
|
| |
Previously we used an .xml file. That bore two problems:
a) the xml contained paths to schmas making the tweaking code longer and
error-prone when the schema paths change.
b) the syntax we used to call gconftool-2 is not really documented in
gconftool's manpage.
The patch calls gconftool-2 directly, with specific paths, exactly in the
same way livecd spin kickstarts do.
|
| | |
|
| | |
|
| |
|
|
| |
With the new images, '/sbin' no longer appears in PATH for the tty2 bash.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For i386, pungi hanged when PAE kernel modules are gathered: this was
because we extracted the PAE modules into the same location as the non-PAE
modules previously. By this time, non-PAE modules exist compressed with
.gz. When mk-images runs gzip on the new modules, it interactively asks
user whether it should owerwrite the compressed (non-PAE) files. Pungi
doesn't show you the prompt so all you see is that it hangs. This is not
observable with x86_64 composes since they only produce one
kernel. Neither is it observable with any pungi composes run via cron
since (my explanation) cron closes stdin for pungi, gzip inherits that and
assumes 'no' for overwriting files, producing a corrupted initrd.img in
the process.
The second problem was that our PAE initrds have always contained both sets
of modules, thus making them 20 MB larger then necessary.
|
| | |
|
| | |
|
| |
|
|
| |
If stage2= is used, drop into the method selection UI instead.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
First, change --initrdto to --dest. That seems more clear to me. Second,
have makeinitrd operate on $IMGPATH instead of $MBD_DIR. That no longer
exists.
|
| |
|
|
|
|
| |
There's no need for all this file creation, installation, and copying to exist
in makeinitrd when it could just as easily be in upd-instroot with everything
else.
|
| |
|
|
|
|
| |
This eliminates almost all the calls to instbin in makeinitrd. Since the images
are being merged, there's no need to copy to a second root just to pack them
up there.
|
| | |
|
| |
|
|
| |
upd-instroot.
|
| | |
|
