From: Stuart M. <Stu...@st...> - 2001-11-05 12:01:48
|
Adrian One of the options which is passed to the kernel is whether to mount the root file system, r/w or read only. This is not passed on the command line, but as a separate parameter (the read only flag is at offset 0 to the parameter block, the command line offset 256 bytes). Its normal to write the root file system read only rather then read write so that fsck can check it first. Of course this doesn't make much sense for a network file system! I suspect the problem you're having is that full mount tries to maintain /etc/mtab, which at this point is on the read only file system. So just add the -n option to your mount. At the moment I'm using: mount -n -o remount,rw /dev/root / -t root which appears to work fine. Stuart On Nov 5, 12:20am, ad...@mc... wrote: > Subject: [linuxdc-dev]NFS Mounting problem > I have been NFS mounting my shell (busybox) successfully but I am now > attempting to mount the m17n GNU/Debian distro but I am having serious > difficulties... > > I can mount the files, but only as read only. > > All the commands to NFS are rw and I think it is the boot loader > (kernel-boot.S) that is forcing a read only mount. > > I had exactly the same problem with busybox but simply fixed this by > remounting the NFS filesystem in rcS: mount -o remount,rw /. This won't work > here (it seems the mount supplied is not as flexible as the one in the > busybox shell?) > > There were issues about the kernel mismatch (the m17n distro is built for > 2.4.5 and I am using 2.4.10-pre6) but this is secondary, as far as I can see, > to the issue of rw mounting the filesystem. > > Has anybody else had this problem and, if so, how did they fix it? > > Thanks > > Adrian > > _______________________________________________ > Linuxdc-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxdc-dev > > >-- End of excerpt from ad...@mc... |