regarding to the original bug, when mounting an nfs-root with nfsmount:
is there any way to reproduce this bug without having a busy/missconfigured switch in between?
and @Oliver Grawert is the bug still present when you use the busybox mount (which is still included in busybox-initramfs-1.01-4ubuntu1tcos1):
--- scripts/nfs.org 2006-01-27 21:54:00.092757473 +0000 +++ scripts/nfs 2006-01-27 21:54:39.846412979 +0000 @@ -33,7 +33,7 @@ roflag="-o rw" fi
- nfsmount ${roflag} ${NFSOPTS} ${NFSROOT} ${rootmnt} + mount -o nolock ${roflag} ${NFSOPTS} ${NFSROOT} ${rootmnt}
[ "$quiet" != "y" ] && log_begin_msg "Running /scripts/nfs-bottom" run_scripts /scripts/nfs-bottom
regarding to the original bug, when mounting an nfs-root with nfsmount:
is there any way to reproduce this bug without having a busy/missconfigured switch in between?
and @Oliver Grawert is the bug still present when you use the busybox mount (which is still included in busybox- initramfs- 1.01-4ubuntu1tc os1):
--- scripts/nfs.org 2006-01-27 21:54:00.092757473 +0000
roflag= "-o rw"
+++ scripts/nfs 2006-01-27 21:54:39.846412979 +0000
@@ -33,7 +33,7 @@
fi
- nfsmount ${roflag} ${NFSOPTS} ${NFSROOT} ${rootmnt}
+ mount -o nolock ${roflag} ${NFSOPTS} ${NFSROOT} ${rootmnt}
[ "$quiet" != "y" ] && log_begin_msg "Running /scripts/ nfs-bottom"
run_scripts /scripts/nfs-bottom