skeleton: remove loopback interface configuration from inittab
PATCH 1/1 skeleton: remove loopback interface configuration from inittab
The lo interface is marked auto in /etc/network/interfaces, so the configuration of the loopback network interface is part of the S40network init script. This causes the "RTNETLINK answers: File exists" error message to appear at startup time.
--- .../Atmel/root/target_busybox_skeleton/etc/inittab | 2 -- .../device/Atmel/root/target_skeleton/etc/inittab | 2 -- target/device/xtensa/skeleton-patch/etc/inittab | 2 -- target/generic/target_busybox_skeleton/etc/inittab | 2 -- target/generic/target_skeleton/etc/inittab | 2 -- 5 files changed, 0 insertions(+), 10 deletions(-)
target/device/Atmel/root/target_busybox_skeleton/etc/inittab +0 -2
@@ -24,8 +24,6 @@ ::sysinit:/bin/mount -o remount,rw / ::sysinit:/bin/mount -a ::sysinit:/bin/hostname -F /etc/hostname -::sysinit:/sbin/ifconfig lo 127.0.0.1 up -::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo # now run any rc scripts ::sysinit:/etc/init.d/rcS
target/device/Atmel/root/target_skeleton/etc/inittab +0 -2
@@ -18,8 +18,6 @@ null::sysinit:/bin/mount -o remount,rw / null::sysinit:/bin/mount -t proc proc /proc null::sysinit:/bin/mount -a null::sysinit:/bin/hostname -F /etc/hostname -null::sysinit:/sbin/ifconfig lo 127.0.0.1 up -null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo # now run any rc scripts ::sysinit:/etc/init.d/rcS
target/device/xtensa/skeleton-patch/etc/inittab +0 -2
@@ -18,8 +18,6 @@ null::sysinit:/bin/mount -t proc proc /proc null::sysinit:/bin/mount -o remount,rw / null::sysinit:/bin/mount -a null::sysinit:/bin/hostname -F /etc/hostname -null::sysinit:/sbin/ifconfig lo 127.0.0.1 up -null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo # now run any rc scripts ::sysinit:/etc/init.d/rcS
target/generic/target_busybox_skeleton/etc/inittab +0 -2
@@ -24,8 +24,6 @@ ::sysinit:/bin/mount -o remount,rw / ::sysinit:/bin/mount -a ::sysinit:/bin/hostname -F /etc/hostname -::sysinit:/sbin/ifconfig lo 127.0.0.1 up -::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo # now run any rc scripts ::sysinit:/etc/init.d/rcS
target/generic/target_skeleton/etc/inittab +0 -2
@@ -19,8 +19,6 @@ null::sysinit:/bin/mount -t proc proc /proc null::sysinit:/bin/mkdir -p /dev/pts null::sysinit:/bin/mount -a null::sysinit:/bin/hostname -F /etc/hostname -null::sysinit:/sbin/ifconfig lo 127.0.0.1 up -null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo # now run any rc scripts ::sysinit:/etc/init.d/rcS
Signature · 1 line
1.7.1
PATCH 1/1 skeleton: remove loopback interface configuration from inittab
Hi Buildroot list,
Ping?
Any comment on this?
baruch
Quoted 82 lines · Baruch Siach
The lo interface is marked auto in
/etc/network/interfaces, so the configuration of the loopback network interface is part of the S40network init script. This causes the "RTNETLINK answers: File exists" error message to appear at startup time.Signed-off-by Baruch Siach <[email protected]>--- .../Atmel/root/target_busybox_skeleton/etc/inittab | 2 -- .../device/Atmel/root/target_skeleton/etc/inittab | 2 -- target/device/xtensa/skeleton-patch/etc/inittab | 2 -- target/generic/target_busybox_skeleton/etc/inittab | 2 -- target/generic/target_skeleton/etc/inittab | 2 -- 5 files changed, 0 insertions(+), 10 deletions(-)target/device/Atmel/root/target_busybox_skeleton/etc/inittab +0
-2@@ -24,8 +24,6 @@ ::sysinit:/bin/mount -o remount,rw / ::sysinit:/bin/mount -a ::sysinit:/bin/hostname -F /etc/hostname -::sysinit:/sbin/ifconfig lo 127.0.0.1 up -::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo # now run any rc scripts ::sysinit:/etc/init.d/rcStarget/device/Atmel/root/target_skeleton/etc/inittab +0
-2@@ -18,8 +18,6 @@ null::sysinit:/bin/mount -o remount,rw / null::sysinit:/bin/mount -t proc proc /proc null::sysinit:/bin/mount -a null::sysinit:/bin/hostname -F /etc/hostname -null::sysinit:/sbin/ifconfig lo 127.0.0.1 up -null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo # now run any rc scripts ::sysinit:/etc/init.d/rcStarget/device/xtensa/skeleton-patch/etc/inittab +0
-2@@ -18,8 +18,6 @@ null::sysinit:/bin/mount -t proc proc /proc null::sysinit:/bin/mount -o remount,rw / null::sysinit:/bin/mount -a null::sysinit:/bin/hostname -F /etc/hostname -null::sysinit:/sbin/ifconfig lo 127.0.0.1 up -null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo # now run any rc scripts ::sysinit:/etc/init.d/rcStarget/generic/target_busybox_skeleton/etc/inittab +0
-2@@ -24,8 +24,6 @@ ::sysinit:/bin/mount -o remount,rw / ::sysinit:/bin/mount -a ::sysinit:/bin/hostname -F /etc/hostname -::sysinit:/sbin/ifconfig lo 127.0.0.1 up -::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo # now run any rc scripts ::sysinit:/etc/init.d/rcStarget/generic/target_skeleton/etc/inittab +0
-2@@ -19,8 +19,6 @@ null::sysinit:/bin/mount -t proc proc /proc null::sysinit:/bin/mkdir -p /dev/pts null::sysinit:/bin/mount -a null::sysinit:/bin/hostname -F /etc/hostname -null::sysinit:/sbin/ifconfig lo 127.0.0.1 up -null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo # now run any rc scripts ::sysinit:/etc/init.d/rcSSignature · 1 line
1.7.1
Signature · 3 lines
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -PATCH 1/1 skeleton: remove loopback interface configuration from inittab
In reply to Baruch SiachQuoted 4 lines · On Thu, 3 Jun 2010 08:36:50 +0300 Baruch Siach <[email protected]> wrote:
The lo interface is marked auto in
/etc/network/interfaces, so the configuration of the loopback network interface is part of the S40network init script. This causes the "RTNETLINK answers: File exists" error message to appear at startup time.
Not tested, but I think it's ok.
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH 1/1 skeleton: remove loopback interface configuration from inittab
Hi Thomas,
Quoted 11 lines · Thomas Petazzoni
Quoted 4 lines · On Thu, 3 Jun 2010 08:36:50 +0300 Baruch Siach <[email protected]> wrote:
The lo interface is marked auto in
/etc/network/interfaces, so the configuration of the loopback network interface is part of the S40network init script. This causes the "RTNETLINK answers: File exists" error message to appear at startup time.Not tested, but I think it's ok.
Acked-by Thomas Petazzoni <[email protected]>
Thanks.
Any chance of this being accepted upstream?
baruch
Signature · 3 lines
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -PATCH 1/1 skeleton: remove loopback interface configuration from inittab
Quoted 5 lines · On Wed, 9 Jun 2010 04:58:35 +0300 Baruch Siach <[email protected]> wrote:
Quoted 5 lines
Quoted 4 lines
The lo interface is marked auto in
/etc/network/interfaces, so the configuration of the loopback network interface is part of the S40network init script. This causes the "RTNETLINK answers: File exists" error message to appear at startup time.
Quoted 7 lines
Quoted 3 lines
Not tested, but I think it's ok.
Acked-by Thomas Petazzoni <[email protected]>Thanks.
Any chance of this being accepted upstream?
Yes. Just wait for Peter (Buildroot's maintainer) to pick up your patch. It may take a few days for this to happen. If we haven't merged your patch in one week from now, then ping us again.
Thanks!
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
PATCH 1/1 skeleton: remove loopback interface configuration from inittab
In reply to Baruch SiachQuoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Baruch" == Baruch Siach <[email protected]> writes:
Baruch> The lo interface is marked auto in /etc/network/interfaces, so the Baruch> configuration of the loopback network interface is part of the Baruch> S40network init script. This causes the "RTNETLINK answers: File exists" error Baruch> message to appear at startup time.
Committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard