Re: Re: Re: Re: NFS mounts and Debian

2012-05-21 Thread Antoine Journeaux
Ortelious wrote: > I'm having the exact same problem since updating to netbase 5.0 and > ifupdown 0.7~rc3 Booting is taking around 10 minutes as it tries to > map the four nfs4 shares i have on my server. After it gets the timed > out messages it boots normally and the shares are connected fine.

Re: Re: Re: NFS mounts and Debian

2012-05-21 Thread Ortelious
I'm having the exact same problem since updating to netbase 5.0 and ifupdown 0.7~rc3 Booting is taking around 10 minutes as it tries to map the four nfs4 shares i have on my server. After it gets the timed out messages it boots normally and the shares are connected fine. Information during boot:

Re: NFS mounts and Debian

2012-05-21 Thread Andrei POPESCU
On Sb, 19 mai 12, 20:43:16, antoine...@free.fr wrote: > > # cat /etc/network/interfaces > > allow-hotplug eth0 > Is this all? Maybe you should just attach the file instead. Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/l

Re: NFS mounts and Debian

2012-05-19 Thread Tom H
On Sat, May 19, 2012 at 2:43 PM, wrote: > > What's going on with Debian today? > > After the aptitude checksum fail, now comes the /etc/init.d/networking bug at > startup. > > Description of the problem: > After a pair of update of ifupdown and netbase (i think, but i'm not shure), > the > compu

Re: Re: NFS mounts and Debian

2012-05-19 Thread antoinejou
> i am not sure about your updates, but in my wheeze i have no new version > ifupdown yet, then i don't upgraded the netbase. I know, that this can be > mirror depending... > > Are you sure, that you don't uninstall old (0.7~alpha5+really0.6.16) > ifupdown (because netbase has breaks for it)? > >

Re: NFS mounts and Debian

2012-05-19 Thread Slavko
Ahoj, Dňa Sat, 19 May 2012 20:43:16 +0200 antoine...@free.fr napísal: > Hi everybody... > What's going on with Debian today? > > After the aptitude checksum fail, now comes the /etc/init.d/networking > bug at startup. > > Description of the problem: > After a pair of update of ifupdown and netb