O

oscheck

Wrapper to create and track baselines tests against fstests

  • Luis Chamberlain's avatar
    oscheck: fix dhcp races when using linux-next · 56db5b03
    Luis Chamberlain authored
    When booting the latest linux-next I see that network interfaces
    are up but dhcp never kicks in. It seems we have yet again a device
    name change issue... Seriously...
    
    If we are not doing network development or working on systemd stuff we
    frankly don't care about this bug, so just allow us to work around it.
    *We* filesystem kernel developers don't care about this bug so just
    work around this nasty issue by ensuring all of our non loopback devices
    *get* a DHCP request issued, *always*.
    
    We use a new ansible role for this which captures this easily.
    Only observed on Debian so far, so other distros won't have anything
    done for them.
    Signed-off-by: default avatarLuis Chamberlain <mcgrof@kernel.org>
    56db5b03
Name
Last commit
Last update
LICENSES/preferred Loading commit data...
ansible Loading commit data...
expunges Loading commit data...
fstests-configs Loading commit data...
osfiles Loading commit data...
scripts Loading commit data...
terraform Loading commit data...
triage Loading commit data...
vagrant Loading commit data...
.bashrc Loading commit data...
.gitignore Loading commit data...
.oscheck-setup Loading commit data...
CONTRIBUTING Loading commit data...
COPYING Loading commit data...
LICENSE Loading commit data...
Makefile Loading commit data...
README.md Loading commit data...
gendisks.sh Loading commit data...
globals.mk Loading commit data...
ld-version.sh Loading commit data...
naggy-check.sh Loading commit data...
oscheck.sh Loading commit data...
requirements.yml Loading commit data...