Booting problem

[Zachary Crownover]

It would be the killing blow to DragonFlyBSD on any virtual hardware.

On Tue, Aug 18, 2015 at 12:23 PM, nans_nans1 <nans_nans1 at yahoo.de> wrote:

>
> Why not? All big linux distributions drop generation of  ISO images ...
>
> Von Samsung Mobile gesendet
>
>
>
> -------- Ursprüngliche Nachricht --------
> Von: "Steve Petrie, P.Eng." <apetrie at aspetrie.net>
> Datum: 18.08.2015 19:57 (GMT+01:00)
> An: users at dragonflybsd.org
> Betreff: Re: Booting problem
>
>
> I agree with Stephen Walker and Gennady Proskurin,
>
> Please don't drop generation of DragonFlyBSD ISO images.
>
> I am using DragonFlyBSD as a KVM guest os on Elastic Hosts (EH)
> www.elastichosts.com. EH supports custom os install for KVM by means of
> ISO
> image.
>
> Steve
>
> * * *
>
> Steve Petrie, P.Eng.
>
> ITS-ETO Consortium
> Oakville, Ontario, Canada
> (905) 847-3253
> apetrie at aspetrie.net
>
> ----- Original Message -----
> From: "Stephen Welker" <stephen.welker at nemostar.com.au>
> To: <users at dragonflybsd.org>
> Sent: Sunday, August 16, 2015 3:13 AM
> Subject: Re: Booting problem
>
>
> Hi,
>
> Please don’t retire ISO generation.
>
> I only (clean) install production distributions from CD (ISO).
>
>
> > On 15 Aug 2015, at 1:14 am, Matthew Dillon <dillon at backplane.com> wrote:
> >
> > It might be time to retire the ISO generation entirely.
> >
> > -Matt
> >
> > On Wed, Aug 12, 2015 at 1:30 PM, Gavin Reade <greadey at gmail.com> wrote:
> > I could not get the iso to work and thinking it was the cheap CDs I
> > bought, consigned it to the beer mat pile.  Tried the USB image and it
> > worked perfectly.
> >
> > greadey
> >
> > On Wed, Aug 12, 2015 at 8:43 PM, <nans_nans1 at yahoo.de> wrote:
> > Hi,
> >
> > again: The DragonFly-x86_64-LATEST-ISO.iso won't boot !!!
> >
> > But: Who cares?
>
>
> Stephen Welker.
>
>


-- 
Sincerely,

Zachary Crownover
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20150818/96918fed/attachment-0002.html>