Summary: | =sys-apps/baselayout-1* missing slave in bond shouldn't be fatal | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcin Mirosław <bug> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | floppym |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marcin Mirosław
2010-12-20 15:24:41 UTC
I'm not sure that there is any way to detect the difference between a hardware failure and a configuration error here. Network bonding also seems quite different from RAID in that network adapters fail far less frequently than hard disks. Please retest with the latest git of openrc, where this has changed. (In reply to comment #1) > I'm not sure that there is any way to detect the difference between a hardware > failure and a configuration error here. I have no idea how to detect difrence too. Imho it's nothing to worry about. For me, ewarn is enough to warn user about missing device. > Network bonding also seems quite different from RAID in that network adapters > fail far less frequently than hard disks. Agree. It was analogy. (In reply to comment #2) > Please retest with the latest git of openrc, where this has changed. For me nothing changed between openrc-0.6.8 and openrc-9999 - bond device is crated, even without any slave present. Both version works correctly for me. And what about stable baselayout-1.x.x? Is any chance to fix it? No, we're not backporting to baselayout1. I'm trying to get all oldnet issues solved with it so we can stabilize. |