On Mon, Sep 03, 2001 at 09:33:16AM -0400 or thereabouts, Ben Collins wrote: > On Mon, Sep 03, 2001 at 02:49:49PM +0200, Roberto Giorgetti wrote: > > On Thu, Aug 30, 2001 at 09:06:46PM -0400 or thereabouts, Ben Collins wrote: > > > On Thu, Aug 30, 2001 at 11:12:11PM +0200, Roberto Giorgetti wrote: > > > > After a blackout the boot showed me: > > > > > > > > VFS: Mounted root (ext2 filesystem) readonly > > > > INIT: Version 2.80 booting > > > > INIT: Cannot execute "/etc/init.d/rcS" > > > > INIT: Entering runlevel: 2 > > > > INIT: Cannot execute "/etc/init.d/rc" > > > > > > Boot with "linux init=/bin/bash", remount rw, and chmod both of these > > > files 755. Then reboot. You should upgrade the sysvinit package, since > > > you have a version that contained this mode bug. > > > > > > > Ben, > > thank you for your help. Now with your suggestion, I don't > > receive error messages executing any scripts but... the /dev/hda1 > > is still mounted read-only. Of course I am not able to umount / > > and to remount it read-write. I only add that running > > fdisk /dev/hda > > I receive: > > What happens when you run "mount / -o remount,rw" as root? What error > messages, if any are produced? What shows in in the log files when you > do this?
Sorry for answering you so late, but I had a bad family problem. Now I came back to my severe SPARC problem. Yes, if I run: mount / -o remount,rw / is mounted read-write. Then I issued: chmod 755 /etc/init.d/rc chmod 755 /etc/init.d/rcS but when I reboot, root (/) is still mounted as read-only and I receive a lot of error messages complaining about /proc mounted as read-only and then something coming from modprobe. By the way how can I stop the log of booting in order to read what is scrolling down on the screen? Besides after the reboot /etc/init.d/rcS still come back to 644! Thank for your help. Roberto Giorgetti.
