Hello Roger and Petter!!!
Have a good year!
Thanks for your fast responses and sorry for my late reply.
El 31/12/11 07:03, Petter Reinholdtsen escribió:
[Roger Leigh]
I'm somewhat unsure what the reason for the problem is? What causes
failure when the directory is present?
I suspect NFS mounting fail. but the bug reporter need to provide more
information. But perhaps this bug is related to the inverted logic in
the NFS mounting code that was fixed in recent uploads?
Sorry for my bad report! I thought you would look at what the
original reporter said, which is that if that directory exists at boot,
then NFS refuses to mount anything, leading to an unusable system in
some cases, and also a reboot doesn't fix it, so, someone must go and
remove that directory for NFS mounts to work again.
I looked at the changelog of nfs-utils package up to and including
2010 (using
http://packages.debian.org/changelogs/pool/main/n/nfs-utils/nfs-utils_1.2.5-3/changelog)
and didn't found anything about this.
Note that /run is a tmpfs and /var/run and /var/lock are now therefore
always on tmpfs by default.
Yes, but we need to support non-tmpfs run and lock directories too. :)
Thats true, but also maybe a patch for Squeeze could be done to
support stable users.
Thanks a lot!!!
Have a great day!!!
--
Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: iba...@codigolibre.net - http://go.to/ibaldo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
