On 02/12/15 at 12:57pm, Harald Hoyer wrote:
On 12.02.2015 07:00, Dave Young wrote:
> On 02/11/15 at 04:19pm, Colin Walters wrote:
>>> Rethink about it, since dracut is use /sysroot as mount point, really
atomic
>>> should
>>> choose another dir name instead of /sysroot which conflicts with dracut.
>>
>> Without investigating closely, there's no conflict here, it's just
confusing.
>> In the initramfs, there exists a /sysroot that points to the physical storage.
>
> Dracut is using /sysroot as mounting point for real root since the very beginning
> Also see below systemd doc (Sectin "Bootup in the Initial RAM Disk):
>
http://www.freedesktop.org/software/systemd/man/bootup.html
>
> It says " If the root device can be mounted at /sysroot, the sysroot.mount
unit
> becomes active and initrd-root-fs.target is reached.
>
> So there's many assumptions about /sysroot...
Note: initrd-root-fs.target also has an additional condition
ConditionPathExists=/etc/initrd-release
So, that on normal systems, the target is not activated.
There's below logic for ostree prepare root, not sure if this is the one in RHEL
though
https://github.com/GNOME/ostree/blob/master/src/switchroot/ostree-prepare...
It setup /sysroot and leave it for systemd initrd-switch-root.target to take over
Looks like it is running in initrd?
But from the code it is restruct /sysroot so there seems no conflict.
>>
>> Thus, there is a:
>>
>> /sysroot/ostree/deploy/rhel-atomic-host/deploy/$checksum.$serial/sysroot
>>
>> When booted, there is also a /sysroot which points to the physical storage.
>>
>> But I don't believe there is a point where there is an actual conflict.
>>
>>
_______________________________________________
kexec mailing list
kexec(a)lists.fedoraproject.org
https://lists.fedoraproject.org/mailman/listinfo/kexec