| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
HFS+ filesystems will be mounted read-only if they're not clean, so get
fstab set up correctly.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If you import locale before the file(s) get created, you end up with a
traceback from locale that says:
Error: unsupported locale setting
And this happens no matter what the locale is.
We used to create the locale files for the default lang in loader, so
now let's have anaconda declare a default locale and build its locale
data before we import locale.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Prevents using the same UUIDs for multiple installations when NM creates
UUID for already existing ifcfg file based on hashing of configuration
file name.
Resolves: rhbz#705328
|
| | | | |
| | | | |
| | | | |
| | | | | |
brcm_iscsuio is symlink to iscsiuio currently.
|
| | |/ / |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It was missing an argument.
Signed-off-by: Brian C. Lane <bcl@redhat.com>
|
| | | |
| | | |
| | | |
| | | | |
hfs+ is called hfsplus in-kernel, so it's needed.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Macs are slightly special in terms of their UEFI implementation. The
easiest way to handle boot choice is via the firmware boot picker menu,
which doesn't make use of EFI boot variables. In order for something to
show up here, the filesystem needs to be HFS+ and have some magic done
to it. Handle this case by detecting that we're on a Mac and using an HFS+
/boot/efi partition rather than a FAT one. That lets us then install the
mactel-boot package which will deal with configuring the bootloader.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We'll want to actually create HFS+ partitions, so add the missing bits
for that.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
dracut does this now by using the ip= and rd.znet= parameters when
booting the system, thus rendering everything linuxrc.s390 does in
this area pointless.
Some support code is there to ensure that NetworkManager does not
drive over the already-configured interface.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We switched from using the lvs command to the pvs command in our
udev rules, so now we have to count the _mimage_XX volumes to
determine the number of stripes in a mirrored lv.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rationalle:
<phcoder> pjones, mjg59: anaconda shouldn't include partitions in
device.map
<pjones> phcoder: oh? any particular reason why not, or is it just not
a thing that should happen?
<phcoder> pjones: we don't use partitions in device.map. We use the
corresponding ioctl's.
<pjones> oh, I see. okay, sure.
<phcoder> pjones: such a line creates a disk "hd0\,1"
<pjones> where the \ means "don't parse the comma as a partition"?
<phcoder> hamzy: I've spoken with IBM guys. They are looking into as to
why their system claims to be 100x40. Do you know a reliable
way to detect these systems which claim wrong resolution? If
so we can include a workaround
<phcoder> pjones: yes. We need it because of IEEE1275
<pjones> hah, of course.
<pjones> /pci@1e,600000/
<phcoder> pjones: these entries claim that BIOS exposes separate
partitions as fully-pledged disks.
<pjones> right, which is clearly not the case.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When an installed system cannot be upgraded it may be helpful to know if
it was the product, version or arch that didn't match. This propagates
that info up from productUpgradable so that it can be show to the user.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Sometimes a format module may have an error in it during development. It
would be helpful to see the traceback to speed up debugging.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Macs won't boot with the PMBR boot flag set, and EFI systems won't need
it set so skip it when the system is an EFI system.
Signed-off-by: Brian C. Lane <bcl@redhat.com>
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Resolves: rhbz#755147
|
| | |/ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit adds AnacondaOptionParser, which is an OptionParser subclass
that parses kernel boot arguments in addition to commandline arguments.
It looks for boot args that match the parser's long options. You can
also provide extra boot args to look for, e.g.:
op.add_option("--kickstart", "ks", dest="ksfile")
This patch also switches anaconda over to the new parser, which means we no
longer need loader to parse boot args for us.
NOTE BEHAVIOR CHANGE: anaconda now expects (but does not yet require)
all boot arguments to begin with "inst.", and will emit warning
log messages if you use the old forms (repo=..., ks=..., etc.).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
set_cmdline_bool replaces decideCmdlineFlag - it uses BootArgs.getbool.
read_cmdline sets a bunch of flags based on the contents of cmdline -
this code is basically just split from where it used to live at the end
of __init__.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This replaces Flags.cmdline (and Flags.createCmdlineDict()) with a new
BootArgs class.
BootArgs' parsing is slightly cleaner and it reads from other data
locations (/run/initramfs/etc/cmdline for example).
It's a subclass of OrderedDict, so things specified later
on the boot commandline can override things near the start.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- make Flags a subclass of object
- Drop the silly games with __dict__['flags'] in favor of directly
setting attributes
- Preserve the exception-on-get/set-of-unknown-attribute behavior
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Anaconda was expecting serial console options with only the baud rate
after the comma, for example:
console=ttyS0,115200
But this is also valid (see Documentation/kernel-parameters.txt):
console=ttyS0,115200n8
So this patch adds a function to parse the options correctly, and improves
the GRUB serial_command() method to use the parsed options wherever they
vary from the default values.
Based on a patch by Jan Stancek <jstancek@redhat.com> - thanks!
|
| | |
| | |
| | |
| | |
| | |
| | | |
When upgradig to F17 the dracut convertfs script needs to be
run on the target filesystem so that it can convert /bin, /sbin,
/lib and /lib64 to symlinks into /usr
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
file only once in such cases
Resolves: rhbz#750710
(cherry-picked from 7cba80ba8d8d934c4596404686b46887c398d028)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The option can be set in boot command line, in kickstart file using network
command, and in loader UI. The option takes effect only if there is no device
with configured ipv6.
Resolves: rhbz#735791
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Some BIOS systems (LENOVO) have problems booting from GPT without the
boot flag of the protective MBR set. This makes sure that it is alway on
when using GPT labeled disks.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In loader strverscmp(3) is used so the patch will cover vast majority of
cases (although e.g. eth9 would precede eth10 in loader, whereas eth10
would precede eth9 in stage 2 if there were more than 10 devcies having
link).
Resolves: rhbz#760250
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It's a different key depending on whether you are after the VG name
for a PV or an LV, so make it clear by using a separate function.
Related: rhbz#772878
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The initial loop through udev's block device list is mostly to
identify and assemble mpaths. Already-active mpaths in that list
cause problems because of the special way mpaths are handled. However,
mpath member devices are never device-mapper devices so we can safely
skip over them in this mpath-specific loop.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This accompanies a kickstart option to autopart, type:
autopart --type=lvm|btrfs|plain
|