Date: Fri, 9 Jul 2010 09:41:57 -0700 From: Randi Harper <randi@freebsd.org> To: Karsten Behrmann <BearPerson@gmx.net> Cc: freebsd-sysinstall@freebsd.org Subject: Re: silly, silly sysinstall Message-ID: <AANLkTik2Cfty8a-i6ck3tA13hIL4AGmThBpSfkOmMFJ0@mail.gmail.com> In-Reply-To: <E672C0E1-CB83-4266-8DE7-AAA26B7E91CB@gmx.net> References: <1278649973.3102.14.camel@localhost.localdomain> <756E9A5F-D580-42DE-A088-9F6FBACB5249@gmx.net> <E672C0E1-CB83-4266-8DE7-AAA26B7E91CB@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 9, 2010 at 2:56 AM, Karsten Behrmann <BearPerson@gmx.net> wrote: >> Asin, the thing boots correctly, seems to use the proper-OS image >> as root (otherwise it'd have a hard time finding sysinstall at all), > > Silly me. It's too early to be writing mails. > Sysinstall lives in mfs at first, and then tries to figure out what > to mount for the other stuff. > I suppose that's the stage that goes wonky - maybe we need more code > in the heuristic that determines what "actual root" is... > > Still, detailed error message/behavior reports would go a long way ;) > Or, if you *really* want to be awesome with helping us debug this: * pull down the latest code for sysinstall * compile it (i recommend making sure it's got -static) * pop it into the mfsroot of your install media (using a USB memstick is easier - fixit there is actually functional) along with an install.cfg that specifies a syslogdServer and network setup * send us the logs. :P
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTik2Cfty8a-i6ck3tA13hIL4AGmThBpSfkOmMFJ0>