Oops, hit send too soon. I was able to get portmap working using the
older version (etch portmap 5-26), but statd still did not start up. It
complains that: Opening /var/run/rpc.statd.pid failed: Read-only file
system. Which seems crazy, as the whole point of this is to have /
mounted over nfs,
I am having a similar problem, and portmap 6.0-9 does not solve my
problem either. On my setup, rpc.statd does not start because portmap
does not start, so my nfs mounts do not happen. I end up booting with
the read only file system mounted by initrd. I did also try adding
ASYNCMOUNTNFS=no to /etc
I am having a similar problem, and portmap 6.0-9 does not solve my
problem either. On my setup, rpc.statd does not start because portmap
does not start, so my nfs mounts do not happen. I end up booting with
the read only file system mounted by initrd. I did also try adding
ASYNCMOUNTNFS=no to /
[Raphael Manfredi]
> How do I capture the output on the console?
Not sure how to best do this.
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Quoting Petter Reinholdtsen:
: The scripts involved are /etc/network/if-up.d/mountnfs and
: /etc/init.d/mountnfs.sh. The first do the real mounting when the last
: network interface is brought up, and the second wait for the first to
: complete before continuing the boot. Could it be that these s
[Raphael Manfredi]
> But I'm reluctant to use this. I would prefer to help you
> understand why it does not work here, to benefit everyone. Although
> I do have exotic configs on some machines, others are pretty
> standard and exhibit the same problems.
The scripts involved are /etc/network/if-u
Quoting Petter Reinholdtsen:
: [Raphael Manfredi]
: > I don't use /etc/network/interfaces on this machine. It uses the
: > old /etc/init.d/network hardwired configuration which says:
:
: Wow. I have never seen such setup, and it will not work with the
: current way NFS mounting is handled. Beca
[Raphael Manfredi]
> I don't use /etc/network/interfaces on this machine. It uses the
> old /etc/init.d/network hardwired configuration which says:
Wow. I have never seen such setup, and it will not work with the
current way NFS mounting is handled. Because of the new behaviuor of
the linux ker
Quoting Petter Reinholdtsen:
: Can you provide the content of /etc/network/interfaces and /etc/fstab?
: NFS mounts are done when all interfaces are up. Are there some
: interfaces listed that are not brought up during boot?
I don't use /etc/network/interfaces on this machine. It uses the
old /et
[Raphael Manfredi]
> Everything was working fine when my systems did not use
> "initscripts". Unfortunately, I had to install them as some
> unstable packages I needed to use required them, so I cannot
> downgrade.
Can you provide the content of /etc/network/interfaces and /etc/fstab?
NFS mounts
Package: initscripts
Version: 2.86.ds1-57
Severity: important
Since I upgraded my Debian systems to use "initscripts", my NFS filesystems
are no longer mounted at boot time.
I see a:
Waiting for...
message with one of my mounted NFS partition at boot time on the console,
but it hangs th
11 matches
Mail list logo
