Re: [beagleboard] enabling the BBxM to start in 'ro' mode
Thank you. Could you post here the scripts (or send me them to me?). I fear the problem is not with the script but with the need of creating a initrd image with aufs to allow for temporary storage of information on the RAM, as it is done with Live CDs. Would mounting rootfs read-only be possible without compromising functioning of the system? I'm sure there must be someone expert out there... L On Tuesday, July 15, 2014 4:41:58 PM UTC+2, WB8TKL wrote: Greetings, There is a Linux distro called Voyage Linux that runs read-only. There are scripts that can be run as root called 'remountrw' and remoutro' to change modes as neccessary. Sadly, Voyage Linux is written to run on the x86 andis not available for the ARM processor. But if someone ever converts it to ARM I will switch in a heartbeat! I have several Voyage boxes being used for data collection and love them! It would certainly be sweet to have Voyage on the BBB :) See: http://linux.voyage.hk Enjoy! --- Jay Nugent WB8TKL Ypsilanti, Michigan On Fri, 11 Jul 2014, Leonardo Gabrielli wrote: Hello, I'd need the SD image I prepared for the xM to be supplied to people without them changing a single bit in it. Also, this avoids write failure with power supply failures and increases the life of the SD. From my understanding this can be done by mounting the rootfs as read-only at some point in the boot and writing any change to the RAM without making them persistent. But I'm not expert in the bootstrap process with Linux. The only similar case I know in detail so far is with Ubuntu 10.10 https://ccrma.stanford.edu/~eberdahl/satellite/ and it has two uInitrd images for boot, one with aufs enable and the other without. They only differ in a couple of scripts and if one wants changes to be persistents it is enough to mv files in the boot partition in order for the bootloader to pick the right one. Now, I'm using debian and the rcn-ee builds. Here the boot partition is different it uses initrd.img and zImage. I'm not sure what to do here since it is a different boot method. Are there any suggestions on how to reach my goal? Any simple solution, even performed with an init script after bootstrap would be fine as a starter. Regards -- () ascii ribbon campaign in /\ support of plain text e-mail o Averaging at least 3 days of MTBWTF!?!?!? o The solution for long term Internet growth is IPv6. o To compel a man to furnish funds for the propagation of ideas he disbelieves and abhors is sinful and tyrannical. -Thomas Jefferson ++ | Jay Nugent j...@nuge.com javascript:(734)484-5105 (734)649-0850/Cell | | Nugent Telecommunications [www.nuge.com] | | Internet Consulting/Linux SysAdmin/Engineering Design | | ISP Monitoring [www.ispmonitor.org] ISP Modem Performance Monitoring | ++ 10:01:01 up 8 days, 2:17, 1 user, load average: 0.82, 0.73, 0.99 -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] enabling the BBxM to start in 'ro' mode
Greetings, There is a Linux distro called Voyage Linux that runs read-only. There are scripts that can be run as root called 'remountrw' and remoutro' to change modes as neccessary. Sadly, Voyage Linux is written to run on the x86 andis not available for the ARM processor. But if someone ever converts it to ARM I will switch in a heartbeat! I have several Voyage boxes being used for data collection and love them! It would certainly be sweet to have Voyage on the BBB :) See: http://linux.voyage.hk Enjoy! --- Jay Nugent WB8TKL Ypsilanti, Michigan On Fri, 11 Jul 2014, Leonardo Gabrielli wrote: Hello, I'd need the SD image I prepared for the xM to be supplied to people without them changing a single bit in it. Also, this avoids write failure with power supply failures and increases the life of the SD. From my understanding this can be done by mounting the rootfs as read-only at some point in the boot and writing any change to the RAM without making them persistent. But I'm not expert in the bootstrap process with Linux. The only similar case I know in detail so far is with Ubuntu 10.10 https://ccrma.stanford.edu/~eberdahl/satellite/ and it has two uInitrd images for boot, one with aufs enable and the other without. They only differ in a couple of scripts and if one wants changes to be persistents it is enough to mv files in the boot partition in order for the bootloader to pick the right one. Now, I'm using debian and the rcn-ee builds. Here the boot partition is different it uses initrd.img and zImage. I'm not sure what to do here since it is a different boot method. Are there any suggestions on how to reach my goal? Any simple solution, even performed with an init script after bootstrap would be fine as a starter. Regards -- () ascii ribbon campaign in /\ support of plain text e-mail o Averaging at least 3 days of MTBWTF!?!?!? o The solution for long term Internet growth is IPv6. o To compel a man to furnish funds for the propagation of ideas he disbelieves and abhors is sinful and tyrannical. -Thomas Jefferson ++ | Jay Nugent j...@nuge.com(734)484-5105(734)649-0850/Cell | | Nugent Telecommunications [www.nuge.com]| | Internet Consulting/Linux SysAdmin/Engineering Design | | ISP Monitoring [www.ispmonitor.org] ISP Modem Performance Monitoring | ++ 10:01:01 up 8 days, 2:17, 1 user, load average: 0.82, 0.73, 0.99 -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] enabling the BBxM to start in 'ro' mode
Hello, I'd need the SD image I prepared for the xM to be supplied to people without them changing a single bit in it. Also, this avoids write failure with power supply failures and increases the life of the SD. From my understanding this can be done by mounting the rootfs as read-only at some point in the boot and writing any change to the RAM without making them persistent. But I'm not expert in the bootstrap process with Linux. The only similar case I know in detail so far is with Ubuntu 10.10 https://ccrma.stanford.edu/~eberdahl/satellite/ and it has two uInitrd images for boot, one with aufs enable and the other without. They only differ in a couple of scripts and if one wants changes to be persistents it is enough to mv files in the boot partition in order for the bootloader to pick the right one. Now, I'm using debian and the rcn-ee builds. Here the boot partition is different it uses initrd.img and zImage. I'm not sure what to do here since it is a different boot method. Are there any suggestions on how to reach my goal? Any simple solution, even performed with an init script after bootstrap would be fine as a starter. Regards -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
