Reminds me of a Jamiroquai song
Yes, with /dev/mmcblk0p2
I used 2017-07-05-raspbian-jessie-lite.img just a few days ago.
Maybe some bad new line encodings in config.txt/cmdline.txt is breaking the boot? It's a bit strange really.Heater wrote: ↑Mon Jul 31, 2017 1:52 amTried all sorts of combinations. Checked over everything a dozen times. Nothing works.
Reverting the changes to config.txt and cmdline.txt still does not boot.
Except, in my frustration, I forgot to backup cmdline.txt so now I don't know what that PARTUUID should be!
Too tired to continue...
Re-read Heater's post above. What you want may be possible, but won't achieve what you hope.mlepage wrote: is there a guide to having a distribution be read-only, and another partition (on the same sd card) be writable?
Wait a minute. I missed that part.I'd like to put on a standard raspbian lite, that is protected from corruption, but I can make writeable if I wish so I can perform updates now and then.
Are we speaking here about
Code: Select all
/etc/fstab Add “,ro” flag to both block devices (after "defaults") + /boot/cmdline.txt At the end add noswap ro
I've been mounting samba shares using cifs to a mount point in an overlay filesystem for two years. Prior to that I did the same thing using aufs, the out-of-kernel overlay filesystem. The problem is not overlay, but as you've noticed something to do with the kernel7.img initramfs.
No.Are we speaking here about ... /etc/fstab ...Add “,ro” flag to both block devices