Yes you are correct of course. I'm just picking up the pieces from the previous developers. The next system I roll out will incorporate your suggestion.
On Fri, May 16, 2014 at 7:41 PM, Charles Steinkuehler < [email protected]> wrote: > On 5/16/2014 7:05 PM, John Syn wrote: > > > >> Thank you, damn should've found that myself. > >> > >> The only thing I am worried about is rebooting into fsck mode and then > having > >> it make changes and making the system unbootable. Not much I can do > about > >> that I suppose as I only have Ethernet access via a cell modem... > > In that case, you should use a read only filesystem that you donšt have > to > > check and another which is writeable. You can unmount the writeable > > partition and run fsck. Either use two storage devices (eMMC and SDCard) > or > > use two partitions on one device. > > And if you really need to fix this remotely without risk of the system > not coming back, you can craft a chroot rescue environment in a ram > based file-system, pivot-root to that, and fsck the unmounted flash > drive. You could even pivot-root back to the fixed filesystem without > rebooting unless you need to update the kernel. > > -- > Charles Steinkuehler > [email protected] > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
