Am 01.09.2014 um 19:51 schrieb Dave Reisner: > On Mon, Sep 01, 2014 at 07:36:16PM +0200, Christian Hesse wrote: >> Dave Reisner <[email protected]> on Mon, 2014/09/01 13:22: >>> On Mon, Sep 01, 2014 at 07:14:24PM +0200, Christian Hesse wrote: >>>> Pierre Schmitz <[email protected]> on Mon, 2014/09/01 19:01: >>>>> Hi, >>>>> >>>>> I just build the new ISO image. But I noticed some strange things are >>>>> going on with the systemd services. It seems all available services are >>>>> enabled and get started. Of course some of them will then fail: >>>>> https://paste.archlinux.de/Blu/ >>>>> >>>>> I did not look into it yet; cant tell when though. >>>> >>>> This is a known issue with systemd 216-1: >>>> >>>> https://bugs.archlinux.org/task/41711 >>>> >>>> Though I doubt the fix from systemd 216-2 is a good idea for live >>>> media... We want a new machine-id for every system, no? >>> >>> Not sure what you mean by this -- systemd has always generated a >>> machine-id on first install, making live CDs all have the same machine >>> ID. This isn't a problem. The newly installed system will always have a >>> separate and unique machine-id of its own.. >> >> I thought this should be really unique... Are there any use cases where this >> can make problems? I do boot several instances of the same ISO in one >> network. > > I don't think this would ever be a problem in normal usage of a live > environment. However, it'd be pretty simple to randomize the UUID -- > generate one via method of your choosing (there's at least 5 methods > available) as a late_hook().
Yes, IMO we should do that.
signature.asc
Description: OpenPGP digital signature
