Comment 7 for bug 377432

Yes, there is a file named "85-ifupdown.rules" in /lib/udev/rules.d.

Thanks,
Bryce

On Thu, Aug 13, 2009 at 7:10 AM, Scott James Remnant<email address hidden> wrote:
> On Wed, 2009-08-05 at 14:19 +0000, Bryce Thornton wrote:
>
>> I ran into this yesterday.
>>
>> I had to manually create the /var/run/network directory and then
>> manually create an "ifstate" file within it.  I haven't rebooted since,
>> so I can't confirm that it gets deleted upon reboot.
>>
>> The /etc/udev/rules.d/85-ifupdown.rules file didn't exist on my system,
>> so that method of "fixing" the problem didn't apply.
>>
> Do you have a file of the same name in /lib/udev/rules.d ?
>
> Scott
> --
> Scott James Remnant
> <email address hidden>
>
> --
> ifdown: failed to open statefile /var/run/network/ifstate:
> https://bugs.launchpad.net/bugs/377432
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “ifupdown” package in Ubuntu: New
>
> Bug description:
> Binary package hint: ifupdown
>
> Booting Jaunty, configuring networking interfaces fails, as does
>
> ~$ sudo /etc/init.d/networking restart
>  * Reconfiguring network interfaces...
> ifdown: failed to open statefile /var/run/network/ifstate: No such file or directory
> ifup: failed to open statefile /var/run/network/ifstate: No such file or directory
>
> If I mkdir  /var/run/network/, then I get my network - for this boot, and have the same problem again the next time I boot.
>