include biosdevname calls in dracut
PATCH 1/1 include biosdevname calls in dracut
For your consideration. This allows biosdevname to be called from network-using functions in dracut. biosdevname is included in Fedora 15, and there are tickets open to include it in other distros.
Thanks,
Matt
From ef6a283f685571c730063a666830e2f02d8e9244 Mon Sep 17 00:00:00 2001
From: Matt Domsch <[email protected]>
Date: Fri, 3 Dec 2010 23:41:01 -0600
Subject: [PATCH] add biosdevname calls to network subpackage
--- dracut.spec | 1 + modules.d/95udev-rules/install | 5 +++-- 2 files changed, 4 insertions(+), 2 deletions(-)
dracut.spec +1 -0
@@ -113,6 +113,7 @@ Requires: bridge-utils Requires: iscsi-initiator-utils Requires: nfs-utils Requires: dhclient +Requires: biosdevname %endif %if 0%{?suse_version}
modules.d/95udev-rules/install +3 -2
@@ -6,10 +6,11 @@ # ultimately, /lib/initramfs/rules.d or somesuch which includes links/copies # of the rules we want so that we just copy those in would be best dracut_install udevd udevadm /etc/udev/udev.conf /etc/group -dracut_install basename +dracut_install basename biosdevname inst_rules 50-udev-default.rules 60-persistent-storage.rules \ 61-persistent-storage-edd.rules 80-drivers.rules 95-udev-late.rules \ - 60-pcmcia.rules + 60-pcmcia.rules \ + 71-netdevice.rules #Some debian udev rules are named differently inst_rules 50-udev.rules 95-late.rules
Signature · 1 line
1.7.3.2
A message that is not in the archive (sent off-list or not yet received): 20101206005229.GA687-fZmvIyTar7vbK7CpiBUVEGyRm/Zj/t/[email protected]
Quoted 3 lines · Matt Domsch
For your consideration. This allows biosdevname to be called from network-using functions in dracut. biosdevname is included in Fedora 15, and there are tickets open to include it in other distros.
Any thoughts on this patch?
Thanks,
Matt
Signature · 3 lines
Matt Domsch Technology Strategist Dell | Office of the CTO
A message that is not in the archive (sent off-list or not yet received): 20101214195807.GB31714-fZmvIyTar7vbK7CpiBUVEGyRm/Zj/t/[email protected]
Excerpts from Matt Domsch's message of Tue Dec 14 20:58:07 +0100 2010:
Quoted 7 lines · Matt Domsch
Quoted 4 lines
For your consideration. This allows biosdevname to be called from network-using functions in dracut. biosdevname is included in Fedora 15, and there are tickets open to include it in other distros.
Any thoughts on this patch?
I think that better would be to include your patch with first its usage. Having additional dependencies without a real use brings mess. But it's just my opinion and I'm not in charge. :-)
Cheers,
Signature · 3 lines
Amadeusz Żołnowski PGP key fpr: C700 CEDE 0C18 212E 49DA 4653 F013 4531 E1DB FAB5
Quoted 7 lines · Amadeusz ??o??nowski
Excerpts from Matt Domsch's message of Tue Dec 14 20:58:07 +0100 2010:
Quoted 6 lines · Matt Domsch
Quoted 4 lines
For your consideration. This allows biosdevname to be called from network-using functions in dracut. biosdevname is included in Fedora 15, and there are tickets open to include it in other distros.
Quoted 5 lines
Quoted 1 line
Any thoughts on this patch?
I think that better would be to include your patch with first its usage. Having additional dependencies without a real use brings mess. But it's just my opinion and I'm not in charge. :-)
The use case is simple - any network-using functions that are started using dracut (NFS root, iSCSI root, FCoE root) will then use the biosdevname names for devices, rather than the non-deterministic kernel names ethX.
The three instances where <interface> can be passed are:
ip=<interface>:{dhcp|on|any|dhcp6|auto6}
bootdev=<interface>
netroot=fcoe:<interface|MAC>:<dcb|nodcb>
plus the forceable rewrite rule:
ifname=<interface>:<MAC>
which only works when you already know the MAC address of the target device.
The biosdevname method behaves similarly to the ifname= method, except you get device names from BIOS, without needing to know the MAC address of the target device(s).
With this patch, you no longer need to use bootdev=eth0 and later have udev rename eth0 to be em1, which leads to different devices names for configuration at different times (dracut and post-dracut). Both dracut and post-dracut use the same device names.
Thanks,
Matt
Signature · 3 lines
Matt Domsch Technology Strategist Dell | Office of the CTO