Bug 613803 - ip / ifconfig appears to not work in single-user mode
Summary: ip / ifconfig appears to not work in single-user mode
Status: CLOSED DUPLICATE of bug 585053
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts   
(Show other bugs)
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-12 20:46 UTC by Need Real Name
Modified: 2014-03-17 03:24 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-13 16:32:03 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Need Real Name 2010-07-12 20:46:20 UTC
1. Boot into runlevel 1
2. Edit /etc/sysconfig/network-scripts/ifcfg-eth0, and change NM_CONTROLLED=yes to NM_CONTROLLED=no
3. /etc/init.d/networking restart
4. ifconfig

(no output)

5. ifconfig -a

(no output)

6. ping

(I get output)

7. ip addr

(no output)

Something is going wrong here... same as if I run with ifup eth0

Comment 1 Jiri Popelka 2010-07-13 12:12:46 UTC
Steps to reproduce:

1. telinit 1

2. 'ip a' or 'ifconfig -a'
(no output)

3. setenforce 0

4. 'ip a' or 'ifconfig -a'
(work as expected)

Comment 2 Daniel Walsh 2010-07-13 12:31:36 UTC
This is a known problem, which we are changing by forcing the running of sulogin.

If you execute sulogin, the terminals will work correctly.

Or you can do a little trick by executing

ip a | cat

Comment 3 Bill Nottingham 2010-07-13 16:32:03 UTC
Actually, we're not forcing sulogin, but we're putting another command in between so policy can work.

*** This bug has been marked as a duplicate of bug 585053 ***

Note You need to log in before you can comment on or make changes to this bug.