15 марта 2015 г. 21:26 пользователь "Robert Peichaer" <rob...@peichaer.org> написал: > > On Sun, Mar 15, 2015 at 09:03:45PM +0300, Vadim Zhukov wrote: > > 15 ?????????? 2015 ??. 20:50 ???????????????????????? "Theo de Raadt" < dera...@cvs.openbsd.org> > > ??????????????: > > > > > > > On Sun, Mar 15, 2015 at 11:24:32AM -0400, Kenneth Westerback wrote: > > > > > Using DUIDs in the installed /etc/fstab has been the default for some > > time now. > > > > > > > > > > We'd like to eliminate the question in the installer and just use > > > > > DUIDs unconditionally. > > > > > > > > > > But first we need to know you are aware of any circumstances where > > > > > people need or prefer to use the non-DUID option when installing? > > > > > > > > I prefer not using DUIDs. > > > > > > OK, I think Ken made a mistake mentioning preferences. The real > > > question is if anyone has a use-case where DUIDs do not work. > > > > > > Preference has nothing to do with it. If DUIDs have no downsides, > > > and only the upsides that they were designed to support, then it is > > > time to remove the installation question. > > > > > > The non-DUID access patterns continue to work, of course. That is > > > also not part of the question. > > > > Virtualization appliances: after cloning you could get a different drive > > ID, right? - and thus get a non-bootable system. That's the only real issue > > I know. Hope to be wrong. :) > > > > -- > > Vadim Zhukov > > At least on VMware, the DUID does not change after cloning.
Nice to know, thanks. I'll recheck tomorrow (at $mainjob) how it goes with KVM. -- Vadim Zhukov
