I'd prefer,
The first option (two yes/nos and a list) since it seems cleaner and
more obvious. The only issue that I could see is where someone might
want a service started by hotplug rather than coldplug or vice-versa. I
honestly don't know anywhere near enough about the difference (up
Roy,
I think the complaint is the automatic loading of modules by udev.
Seemingly in the udev Changelog this is referred to as add udevtrigger
to request events for coldplug, whereas it seems you're using coldplug
to refer to the automatic starting of services. Is there another name
for
Well,
I think a lot of what I've been thinking recently has already been said
by Daniel. I'm actually in the middle of being inducted and I'm just
concerned that I'm going to get extra responsibility without any real
positive aspects for me. I don't really *want* access to check into
Ok,
Well, what if instead we were to try and treat the overlay trees as
exactly that, overlays. So the moves were used from the lowest layer
(ie the main tree) unless a higher up layer overrode them, could that
work? It would mean effectively that the overlay moves were global, but
I guess
Yeah,
Sorry about the double posting, patrick told me about a gmail feature
that means you never see your own posts...
I agree that the updates should only affect that individual tree.
Whilst I can imagine cases where a move in the main tree should affect
overlay trees (such as
101 - 105 of 105 matches
Mail list logo
