On 11/28/2013 12:11 AM, Felix Miata wrote:
1-cloned a nicely functional 13.1 partition 2-assigned new UUID & partition label, updated Grub menu & fstab on cloned partition 3-booted the clone 4-zypper clean -a 5-replace 13.1 repos with Factory's in /etc/zypp/repos.d/ 6-zypper ref; zypper in zypper libzypp rpm glibc libsolv-tools, udev systemd; zypper -v dup 7-booted the updated clone partition to the newly installed kernel
Result: can't do much until manually remounting / rw
Often, (usually) root is mounted 'ro' by the boot loader -- a protective measure in case your kernel went haywire on boot. Not sure how often that happens these days. Might check your boot line and see if it has a read-only or read-write in the entry for the new kernel. This used to be taken care of in a boot script "boot.rootfsck" - which, of course, has been removed... and the systemd equiv?.. no clue.
Is this expected with 3.12.1? Expected of Dracut? Bug? Explicit rw now required for / in fstab?
Easiest might be for it not to be r/o to begin with (i.e. see about mounting it r/w on boot? Maybe depends on how stable your booting OS's are... hmmm..... maybe keep it r/o for now and ask Christian for the systemd replacement for boot.rootfsck... ;-) (When you come up in 'S' mode root would always be r/o because the "B"(oot) scripts hadn't run yet...) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org