So why are you sending me this message?
I have never seen this bug before.

on Friday 09/28/2007 Christian Roessner([EMAIL PROTECTED]) wrote
 > Hi,
 > 
 > I am not wuiet sure, but I guess, I do have the excat same bug in gutsy-
 > tribe 5 on 2 different machines.
 > 
 > I also did an init 1, umounted /var/run/var/lock, and as described
 > above, the directories were not empty. So I deleted all the files. But
 > on next reboot, everything was there, again.
 > 
 > I can not use NetworkManager (which works on my first macine as a
 > workaround), because I use a very complex /etc/network/interfaces file:
 > 
 > auto lo
 > iface lo inet loopback
 > 
 > mapping eth0 # lan
 >         script /usr/sbin/guessnet-ifupdown
 >         map lan-home
 >         map default: default-net
 >         map timeout: 20
 >         map verbose: true
 > 
 > mapping eth1 # wlan
 >         script /usr/sbin/guessnet-ifupdown
 >         map wlan-home
 >         map wlan-home2
 >         map wlan-fh
 >         map default: default-net
 >         map timeout: 20
 >         map verbose: true
 > 
 > #
 > ## lan
 > #
 > iface lan-home inet dhcp
 >         test1 peer address 192.168.3.1 mac 00:12:17:15:F5:CC
 >         post-up /etc/init.d/openvpn start licherstr
 >         pre-down /etc/init.d/openvpn stop licherstr
 > 
 > #
 > ## wlan
 > #
 > iface wlan-home inet dhcp
 >         test1 wireless essid "RNS"
 >         pre-up /etc/init.d/wpasupplicant.init-daemon start
 >         post-up /etc/init.d/openvpn start licherstr
 >         pre-down /etc/init.d/openvpn stop licherstr
 >         post-down /etc/init.d/wpasupplicant.init-daemon stop
 > 
 > iface wlan-home2 inet dhcp
 >         test1 wireless essid "RNS_FSt12"
 >         pre-up /etc/init.d/wpasupplicant.init-daemon start
 >         post-up /etc/init.d/openvpn start licherstr
 >         pre-down /etc/init.d/openvpn stop licherstr
 >         post-down /etc/init.d/wpasupplicant.init-daemon stop
 > 
 > iface wlan-fh inet dhcp
 >         test1 wireless essid "FHGIFB2"
 >         pre-up /etc/init.d/wpasupplicant.init-daemon start
 >         post-up /etc/init.d/openvpn start licherstr
 >         pre-down /etc/init.d/openvpn stop licherstr
 >         post-down /etc/init.d/wpasupplicant.init-daemon stop
 > 
 > #
 > ## Default
 > #
 > iface default-net inet dhcp
 >         pre-up /etc/init.d/wpasupplicant.init-daemon start
 >         post-up /etc/init.d/openvpn start licherstr
 >         pre-down /etc/init.d/openvpn stop licherstr
 >         post-down /etc/init.d/wpasupplicant.init-daemon stop
 > 
 > The file wpasupplicant.init-daemon is taken from
 > /usr/share/doc/wpasupplicant/examples and modified for my device eth1.
 > 
 > Everytime after having logged into gnome session, I have to open a
 > terminal and run ifup eth1 (Running ifdown eth1 before, I get the
 > information: Device has not been configured, yet. Or similar message).
 > 
 > Important: The exactly same setup was working absolutely fine under
 > Feisty. So this is a Gutsy bug.
 > 
 > What I tested:
 > 
 > cd /etc
 > mv initramfs-tools initramfs-tools-old
 > dpkg --force-depends -P initramfs-tools
 > aptitude install initramfs-tools
 > Removing the -old folder
 > Rebooted
 > 
 > Because mountkernfs.sh is in rcS.d as S01, I guess the problem is
 > created in the initrd.
 > 
 > drwxr-xr-x   2 root root  4096 2007-09-27 19:34 .
 > drwxr-xr-x 140 root root 12288 2007-09-28 11:19 ..
 > -rw-r--r--   1 root root   785 2007-09-21 09:11 README
 > lrwxrwxrwx   1 root root    24 2007-02-27 17:12 S01mountkernfs.sh -> 
 > ../init.d/mountkernfs.sh
 > [...]
 > lrwxrwxrwx   1 root root    20 2007-02-27 17:12 S40networking -> 
 > ../init.d/networking
 > [...]
 > 
 > As you can see, there _should_ be no problem
 > 
 > Thanks
 > Christian
 > 
 > -- 
 > Intefraces do not get assigned IP-addresses on boot
 > https://bugs.launchpad.net/bugs/105236
 > You received this bug notification because you are a direct subscriber
 > of the bug.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         [EMAIL PROTECTED]

-- 
Intefraces do not get assigned IP-addresses on boot
https://bugs.launchpad.net/bugs/105236
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to