** Changed in: ifupdown (Ubuntu)
Status: New => Invalid
--
OpenAFS client does not wait for DHCP lease
https://bugs.launchpad.net/bugs/249240
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
This bug was fixed in the package openafs - 1.4.8.dfsg1-2
---
openafs (1.4.8.dfsg1-2) unstable; urgency=low
* Make openafs-modules-source architecture-specific (arch: any instead
of arch: all). The new method for generating the kernel source tree
only generates correct buil
Ansgar Burchardt <[EMAIL PROTECTED]> writes:
> Using -dynroot was not enough it seems. After logging in over SSH (so
> network was already setup), my $HOME was still not accessible.
More details? What did you try? What did you expect? What didn't work?
What error messages did you get?
--
Ru
** Also affects: openafs (Ubuntu)
Importance: Undecided
Status: New
--
OpenAFS client does not wait for DHCP lease
https://bugs.launchpad.net/bugs/249240
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
** Changed in: ifupdown (Ubuntu)
Sourcepackagename: openafs => ifupdown
--
OpenAFS client does not wait for DHCP lease
https://bugs.launchpad.net/bugs/249240
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Using -dynroot was not enough it seems. After logging in over SSH (so
network was already setup), my $HOME was still not accessible.
But I found the real problem: udev backgrounds bringing up the network
interfaces [1]. Adding a rule to prevent this allows the rc-script to
bring up the network
