Re: Someone broke diskless booting
- From: Kris Kennaway <kris@xxxxxxxxxxxxxx>
- Date: Tue, 27 Feb 2007 00:32:57 -0500
On Sun, Feb 25, 2007 at 06:33:33PM -0500, Kris Kennaway wrote:
Some time in the past week or so someone committed a change to the
kernel that broke diskless booting:
Trying to mount root from nfs:
fxp0: link state changed to UP
NFS ROOT: 69.147.83.43:/a/nfs/7.dir1
Interface fxp0 IP-Address 69.147.83.96 Broadcast 69.147.83.127
mdmfs: mdconfig (attach) exited with error code 1
cp: /etc/gss/mech: Read-only file system
cp: /etc/gss/qop: Read-only file system
cp: utimes: /etc/gss: Read-only file system
cp: /etc/ppp/ppp.conf: Read-only file system
...
nfs server 69.147.83.43:/a/nfs/7.dir1: not responding
nfs server 69.147.83.43:/a/nfs/7.dir1: not responding
nfs server 69.147.83.43:/a/nfs/7.dir1: not responding
Kris
A kernel from 1 week ago boots.
Kris
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- References:
- Someone broke diskless booting
- From: Kris Kennaway
- Someone broke diskless booting
- Prev by Date: Re: HEADS UP: UNIX domain socket locking changes merged to CVS HEAD
- Next by Date: geli broken
- Previous by thread: Someone broke diskless booting
- Next by thread: Anyone interested in improving postgresql scaling?
- Index(es):
Relevant Pages
|
|
