Anaconda-devel November 2010

anaconda-devel@lists.fedoraproject.org

27 participants
57 discussions

[PATCH] include biosdevname
by Matt Domsch 29 Nov '10

29 Nov '10

Below is a patch to pull biosdevname into the anaconda environment. This is in partial fulfillment of https://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming approved by FESCo. Please review and apply. Thanks, Matt -- Matt Domsch Technology Strategist Dell | Office of the CTO >From a77d5942d2f92175e4f5ea7508e4b98ee5c46d4b Mon Sep 17 00:00:00 2001 From: Matt Domsch <Matt_Domsch(a)dell.com> Date: Mon, 15 Nov 2010 11:28:58 -0600 Subject: [PATCH] add biosdevname to installer environment --- scripts/upd-instroot | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/scripts/upd-instroot b/scripts/upd-instroot index 84287a5..5f8c85a 100755 --- a/scripts/upd-instroot +++ b/scripts/upd-instroot @@ -228,7 +228,7 @@ EOF PACKAGES="GConf2 NetworkManager NetworkManager-gnome ORBit2 acl anaconda anaconda-yum-plugins at-spi atk attr audit-libs bash bind-utils - bitmap-fonts-cjk + biosdevname bitmap-fonts-cjk btrfs-progs bzip2 bzip2-libs ca-certificates cairo cjkuni-uming-fonts comps-extras coreutils cpio cracklib cracklib-dicts cracklib-python cryptsetup-luks cyrus-sasl-lib db4 dbus dbus-python dbus-x11 dejavu-sans-fonts @@ -491,6 +491,7 @@ lib/udev sbin/*gfs* sbin/arping sbin/badblocks +sbin/biosdevname sbin/blockdev sbin/btrfsctl sbin/btrfsck -- 1.7.2.3

2 1

[PATCH rhel6-branch] Fix default of network --device option to match rhel5 (#647462).
by Radek Vykydal 29 Nov '10

29 Nov '10

Use ksdevice, or device activated in loader, or first device found. Use case: - have 2 NICs - PXE boot from one of them - want to configure this (bootif) device in kickstart using network command We should probably also document it. --- kickstart.py | 13 ++++++++++++- network.py | 2 ++ 2 files changed, 14 insertions(+), 1 deletions(-) diff --git a/kickstart.py b/kickstart.py index e197c32..8b4f865 100644 --- a/kickstart.py +++ b/kickstart.py @@ -558,7 +558,18 @@ class NetworkData(commands.network.F8_NetworkData): devices = anaconda.id.network.netdevices - device = self.device or min(devices.keys()) + if not self.device: + if anaconda.id.network.ksdevice: + # ksdevice boot parameter + device = anaconda.id.network.ksdevice + elif network.hasActiveNetDev(): + # device activated in stage 1 by network kickstart command + device = network.getActiveNetDevs()[0] + else: + # first device found + device = min(devices.keys()) + else: + device = self.device # If we were given a network device name, grab the device object. # If we were given a MAC address, resolve that to a device name diff --git a/network.py b/network.py index 5b1ebb9..b902f31 100644 --- a/network.py +++ b/network.py @@ -369,6 +369,8 @@ class Network: if ksdevice == 'link' and isys.getLinkStatus(dev): self.ksdevice = dev break + elif ksdevice == 'bootif': + self.ksdevice = ":".join(flags.cmdline.get('BOOTIF')[3:].split("-")) elif ksdevice == dev: self.ksdevice = dev break -- 1.7.2

3 6

[PATCH rhel6-branch 1/2] Resolve /dev/disk/ devices during rescue (#605312)
by Brian C. Lane 24 Nov '10

24 Nov '10

Convert symlinks in /dev/disk/ to their real paths before trying to resolve them when mounting the disks for rescue. Resolves: rhbz#605312 --- storage/devicetree.py | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/storage/devicetree.py b/storage/devicetree.py index 56721e8..728191e 100644 --- a/storage/devicetree.py +++ b/storage/devicetree.py @@ -2304,6 +2304,9 @@ class DeviceTree(object): if device is None: log.error("failed to resolve device %s" % devspec) elif devspec.startswith("/dev/"): + if devspec.startswith("/dev/disk/"): + devspec = os.path.realpath(devspec) + # device path device = self.getDeviceByPath(devspec) if device is None: -- 1.7.3.2

2 3

[RHEL6] Add ntpdate to install.img (#614399)
by Martin Gracik 24 Nov '10

24 Nov '10

--- scripts/upd-instroot | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/scripts/upd-instroot b/scripts/upd-instroot index fceb511..1c182b8 100755 --- a/scripts/upd-instroot +++ b/scripts/upd-instroot @@ -185,7 +185,7 @@ PACKAGES="GConf2 NetworkManager NetworkManager-gnome ORBit2 acl anaconda lohit-oriya-fonts lohit-punjabi-fonts lohit-sindhi-fonts lohit-tamil-fonts lohit-telugu-fonts lvm2 madan-fonts mdadm mesa-dri-drivers metacity mkinitrd module-init-tools nash ncurses neon net-tools - newt newt-python nfs-utils nspr nss nss-softokn ntfs-3g + newt newt-python nfs-utils nspr nss nss-softokn ntfs-3g ntpdate openldap openssh openssh-server pam pango parted pciutils pcre psmisc pygtk2-libglade pykickstart pyparted python python-bugzilla python-decorator @@ -632,6 +632,7 @@ usr/sbin/gptsync usr/sbin/hald usr/sbin/lldpad usr/sbin/lvm +usr/sbin/ntpdate usr/sbin/prelink usr/sbin/semodule usr/sbin/showpart -- 1.7.1.1

2 1

[master] It's /usr/bin/gdbserver.
by Ales Kozumplik 24 Nov '10

24 Nov '10

Related: rhbz#442980 --- scripts/upd-instroot | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/scripts/upd-instroot b/scripts/upd-instroot index 84287a5..f99efa5 100755 --- a/scripts/upd-instroot +++ b/scripts/upd-instroot @@ -616,7 +616,7 @@ usr/bin/dbus-launch usr/bin/du usr/bin/eject usr/bin/expr -usr/bin/gdb-gdbserver +usr/bin/gdbserver usr/bin/gdialog usr/bin/gdk-pixbuf-query-loaders* usr/bin/gtk-query* -- 1.7.3.2

2 2

User Experience improvements for Anaconda
by Máirín Duffy 23 Nov '10

23 Nov '10

Hi, In case you don't know me, my name is Máirín Duffy (mizmo in IRC) and I'm the Fedora design team lead & an interaction designer with Red Hat. I worked a bit with Chris and Peter before Fedora 12 came out to try to improve Anaconda's UI for more specialized storage devices. I'm very interested in improving Anaconda's user interface, and in general Fedora's installation experience from beginning to end. One thing we've worked on for the past two releases of Fedora is an improved experience for downloading Fedora from the website. You may have noticed the redesigned 'Get Fedora' pages with Fedora 13's launch, and the redesigned Fedora main website released with Fedora 14's launch a couple of weeks ago. I think the next logical step is to examine the current state of our installation process, identifying the issues we see today, and brainstorming ways to improve the experience of installing Fedora. Here's what we have so far towards this end: - A wiki page to store links to discussions, record decisions, store mockups, and any other data needed: https://fedoraproject.org/wiki/Anaconda/UX_Redesign - There was a long thread on Fedora's devel list about improving the installer experience. (http://lists.fedoraproject.org/pipermail/devel/2010-October/144105.html ) There are some notes distilled from that thread on the UX_Redesign wiki page right now (although they'll probably need some more cleanup to be useful.) - David put together some notes on the install experience for other distributions: http://dcantrel.fedorapeople.org/installer-evals/ - James documented the supported installation methods tested in Anaconda: https://www.redhat.com/archives/anaconda-devel-list/2010-May/msg00305.html - This week I created screen-by-screen walkthroughs of the Live Media install process in F14 (https://fedoraproject.org/wiki/Anaconda/F14_Live_Media_Install ) and the DVD install process as well (https://fedoraproject.org/wiki/Anaconda/F14_DVD_Install ). I also put together a comparison chart of the two methods - https://fedoraproject.org/wiki/Anaconda/UX_Redesign/Current_Install_Process… - Today we had some conversation in #anaconda and I wrote that up as well on that last wiki page: https://fedoraproject.org/wiki/Anaconda/UX_Redesign/Current_Install_Process… I really want to help make our installation process an easy and pleasant experience - so if you have any feedback on the above or ideas on how to get there, let's talk about it. I think even bad or crazy ideas are good brain food, and can lead to awesome innovation. I'm definitely planning to put together some pretty crazy mockups to feed our brains so be on the lookout for those. :) Thanks, ~m

12 30

Proposal for --noformat handling
by David Cantrell 23 Nov '10

23 Nov '10

clumens and I were discussing the --noformat option in kickstart files today (sort of came out of bug #652417, but this is a larger proposal) and how we should have a policy in place for people who want to prepare their own filesystems. First, for those not familiar with the --noformat option, see: http://fedoraproject.org/wiki/Anaconda/Kickstart It is a valid option for part, raid, volgroup, and logvol. It instructs anaconda to not run the mkfs command to initialize the volume. It tells anaconda to assume the volume is ready for use. The primary use of --noformat is for people using a %pre script to set up complex mount points and then direct anaconda to use then as-is. A common pitfall is people passing --noformat for the / volume definition, which can result in an unusable system. After discussing the issues for a while, we came up with: (1) Add a new option to the %pre script definition called --mountpoint=PATH. A pre script defined this way would be treated as a volume preparation script and would executed after other %pre scripts lacking the --mountpoint parameter. (2) Volume preparation scripts must prepare only a single mount point. On success, they should exit with a status of 0. (3) Any storage command used for / with the --noformat option would require a '%pre --mountpoint=/' script. If the script is missing or the exit code is non-zero, installation would stop. Obviously, this doesn't prevent people from creating '%pre --mountpoint=/' scripts that just have "exit 0" as the only line, but that's NOTABUG. For non-root mount points using the --noformat option, we could have an optional check users could enable to cause anaconda to check the exit code of the %pre script. Our first thought was that anaconda should only enforce the one for /, but users might want it for other mount points. Something like: %pre --mountpoint=/home ... DO STUFF ... exit 0 %end ... part /home --onpart=sda47 --noformat --checkuserinit Where --checkuserinit tells anaconda to check for a successful return code of the %pre script that sets up that mount point. Thoughts? Comments? Wayland? -- David Cantrell <dcantrell(a)redhat.com> Red Hat / Honolulu, HI

4 8

Patches for "Allowable drives" in the Partition editor (641910)
by Ales Kozumplik 23 Nov '10

23 Nov '10

Hi, This follows up on what tmlcoch started and didn't have the time to finish: https://www.redhat.com/archives/anaconda-devel-list/2010-October/msg00326.h… What the user wanted in the BZ is not having all the existing devices preselected when creating a new RAID partition. What Tomas did in his patches (what now has become the first patch in this set) was adding a header fields in the checklist, clicking the left one selects/unselects all (like in the filterting UI). Notice that I am also making the whole window taller since the column headers are taking extra space: http://akozumpl.fedorapeople.org/select_all_button.png The second patch goes even further and really does not select all the items when a new RAID partition is to be created (for regular partitions it still selects all devices, i.e. leaves it to anaconda to choose what disk to put it on): http://akozumpl.fedorapeople.org/new_raid_partition.png Ales

2 4

[firstboot 1/2] Add the pwcheck module for getting the password strength
by Martin Gracik 23 Nov '10

23 Nov '10

pwcheck returns the strength of a password in an interval of 0 to 7, 0 meaning weak, and 7 strong. It also has a mapping of string representations of these strength values, so we can show this information to the user. --- firstboot/pwcheck.py | 123 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 123 insertions(+), 0 deletions(-) create mode 100644 firstboot/pwcheck.py diff --git a/firstboot/pwcheck.py b/firstboot/pwcheck.py new file mode 100644 index 0000000..6aae573 --- /dev/null +++ b/firstboot/pwcheck.py @@ -0,0 +1,123 @@ +import re +import cracklib + +import logging +logging.basicConfig(level=logging.INFO) +logger = logging.getLogger("pwcheck") + +import gettext +_ = lambda x: gettext.ldgettext("firstboot", x) + + +class PwError(Exception): + pass + + +class PwRule(object): + + def __init__(self, rule, weight=1, required=False, desc=""): + if callable(rule): + # is a func + self.rule = rule + else: + # is a regex + pattern = re.compile(rule) + self.rule = lambda x: bool(pattern.search(x)) + + if not weight: + raise PwError("weight must be a non-zero value") + + self.weight = weight + self.required = required + + self.desc = desc + + @property + def include(self): + return self.weight > 0 + + @property + def exclude(self): + return self.weight < 0 + + def check(self, password): + passed = self.rule(password) + + if ((self.include and self.required and not passed) or + (self.exclude and self.required and passed)): + logger.debug("%s: %d", self.desc, 0) + raise PwError("password does not meet required criteria") + + if ((self.include and passed) or + (self.exclude and not passed)): + logger.debug("%s: %d", self.desc, self.weight) + return self.weight + else: + logger.debug("%s: %d", self.desc, 0) + return 0 + + +class Password(object): + + def cracklib_check(password): + try: + cracklib.FascistCheck(password) + except ValueError: + return False + else: + return True + + RULES = [ PwRule(rule=lambda x: len(x) >= 4, weight=1, required=True, + desc="4 characters or more"), + PwRule(rule=lambda x: len(x) >= 8, weight=1, required=False, + desc="8 characters or more"), + PwRule(rule=lambda x: len(x) >= 12, weight=1, required=False, + desc="12 characters or more"), + PwRule(rule=r"[a-z]+", weight=1, required=False, + desc="at least one lowercase character"), + PwRule(rule=r"[A-Z]+", weight=1, required=False, + desc="at least one uppercase character"), + PwRule(rule=r"[0-9]+", weight=1, required=False, + desc="at least one digit"), + PwRule(rule=r"[^a-zA-Z0-9]+", weight=1, required=False, + desc="at least one special character"), + PwRule(rule=cracklib_check, weight=-1, required=False, + desc="cracklib") ] + + STRENGTH_STRINGS = [ _("Very weak"), + _("Very weak"), + _("Weak"), + _("Weak"), + _("Fairly strong"), + _("Strong"), + _("Very strong"), + _("Very strong") ] + + def __init__(self, password): + self.password = password + + @property + def strength(self): + strength = 0 + for rule in self.RULES: + try: + strength += rule.check(self.password) + except PwError: + return 0 + + return strength + + @property + def strength_string(self): + strength = self.strength + + if strength < 0: + return self.STRENGTH_STRINGS[0] + + try: + return self.STRENGTH_STRINGS[strength] + except IndexError: + return _("Undefined") + + def __str__(self): + return "%s" % self.password -- 1.7.1.1

1 1

Fwd: DHCPv6 broken in RHEL 6.x
by Harald Hoyer 23 Nov '10

23 Nov '10

Interesting. -------- Original-Nachricht -------- Betreff: DHCPv6 broken in RHEL 6.x Datum: Tue, 16 Nov 2010 17:14:16 -0500 Von: Ray Soucy <rps(a)maine.edu> An: teg(a)redhat.com, harald(a)redhat.com Hi, Not sure if you guys are the right ones to nag about this, but maybe you know who the right people are. I recently took a look at RHEL 6 to see how you guys are doing with IPv6 support. I was happy to see the installer actually offered IPv6 configuration in Stateless, DHCPv6, and Static. Unfortunately, the DHCPv6 network configuration for RHEL 6 is broken. There are two major problems: 1. The default "ip6tables" configuration blocks DHCPv6 responses. I've very glad to see ip6tables have sane defaults. The problem here is the assumption that DHCPv6 client traffic would be caught by conntrack and the ESTABLISHED,RELATED rule. Unfortunately with DHCPv6 this is not the case. Thus for DHCPv6 to work at all you need to include a rule like "-A INPUT -p udp --dport 546 -j ACCEPT" in the default policy. 2. There seems to be an assumption made that "stateless" == "autoconf". When DHCPv6 is selected in the installer, it adds a IPV6_AUTOCONF="no" to the interface configuration. DHCPv6 has no way to provide default route information. In IPv6, that task is handled by router advertisement. If you disable autoconf, then you disable the mechanistic for the host to get a default gateway, making DHCPv6 pointless. Similarly, host systems should not decide to "disable" stateless address configuration in favor of DHCPv6. The "A" (autonomous) flag within a router advertisement signals hosts on a network whether to assign a stateless address or not; Linux already respects this flag. It is a legitimate configuration to use _both_ a stateless and a stateful IPv6 address on a single interface. That should be determined by the network, not the host, as the default behavior. If the RFC were followed, you would actually wait for an IPv6 router advertisement to announce either the "M" or "O" flags before starting a DHCPv6 client; but I'm not sure how you would do that in Linux. The only reliable way right now is to just enable DHCPv6 by default if "Automatic" configuration is selected. 3. DHCPv6 seems to replace resolve.conf with IPv6-only version, instead of a version with both IPv4 and IPv6 nameservers. It's not really an issue, since IPv6 DNS should be preferred per RFCs, but it makes me wonder if it would revert to IPv4 resolve.conf if IPv6 were to go away on the host. 4. The network setup utility (which has your names on it, ;D) doesn't provide for IPv6 configuration as the installer does. We really need the default tools to setup IPv6 to be in place at this point. We can't wait for RHEL 7 to get this right. Essentially, there should be 2 options for IPv6: "Automatic" and "Static" configuration. Automatic should imply that a working DHCPv6 client will be started. If you have a way to only start it when a router advertisement with the "O" (other) or "M" (managed) flags set, then that would be better since it would match the requirement by the RFC... I can't think of a way to easily do that though (maybe with udev...). So the other obvious solution is to just start the DHCPv6 client up in case it's needed. This seems to be how Windows handles it by default. DHCPv6 has been ignored until now, but a growing number of people are starting to make use of it as people quickly find out that stateless is not a good option for the enterprise (even Apple has reversed its position on DHCPv6). Is there any way we can get RHEL 6 to come into the fold? Little things like this really hold back IPv6 deployment, and I don't think there is time for us to wait another 5 years for RHEL 7 to fix it. Modified ip6tables default: # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p ipv6-icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p udp --dport 546 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A INPUT -j REJECT --reject-with icmp6-adm-prohibited -A FORWARD -j REJECT --reject-with icmp6-adm-prohibited COMMIT Example interface configuration for "automatic" IPv6: DEVICE="eth0" BOOTPROTO="dhcp" DHCPV6C="yes" HWADDR="00:1D:09:EF:E9:9A" IPV6INIT="yes" IPV6_AUTOCONF="yes" NM_CONTROLLED="yes" ONBOOT="yes" If someone really wants to kill DHCPv6, they can always edit the file. The average user should have no knowledge of whether IPv6 is stateful or stateless. DHCPv6 is also needed in a stateless environment for DNS server information. Let me know if I can help. I'm a member of the Internet2 IPv6 working group, and head up IPv6 deployment for the University of Maine System. -- Ray Soucy Epic Communications Specialist Phone: +1 (207) 561-3526 Networkmaine, a Unit of the University of Maine System http://www.networkmaine.net/

3 4

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel November 2010