[Voyage-linux] persistence of changes in root filesystem

jegunn (spam-protected)
Thu May 12 00:22:53 HKT 2011


Hi, Punky.

I am running the April 26 2.6.38-voyage kernel (Voyage-MPD) on a VIA C7 
system with a real (PATA) hard disk. I noticed last night that when
I edited a few scripts in /usr/local/bin and also in /usr/lib/mpd
and rebooted, the changes vanished. Clearly the rootfs filesystem
did not get flushed to /hda1. I put the changes back, rebooted,
and all was fine over the NEXT reboot. I installed Voyage with the
`PC' configuration option, and was somewhat surprised that the root
directory is still in a rootfs when the system is running. This
is probably fine for a system as small as Voyage, but I would
rather it run off the disk partition. I put a line in /etc/fstab
saying / should be mounted on /dev/hda1, but it is never
remounted there in the init. I am not sufficiently savvy to
know either how to do this or to figure out why my changes
SOMETIMES do not survive a reboot. Any help/ideas??? ( I removed
the line from /etc/init.d/voyage-util which remounts / read-only
just before the login, but I think have touched nothing else; I
have it set up to autologin user mpd.) Now I think about it,
why DO you remount / read-only if it is a running rootfs, running
entirely in memory???

thanks

--jim




More information about the Voyage-linux mailing list