Date: Mon, 09 Nov 2015 18:26:57 -0800 (PST) From: "Jeffrey Bouquet" <jbtakk@iherebuywisely.com> To: "Bryan Drewery" <bdrewery@FreeBSD.org> Cc: "current" <current@freebsd.org> Subject: Re: Cannot installworld, don't expect to...Workaround? Message-ID: <E1Zvye9-0004gF-Fr@rmm6prod02.runbox.com> In-Reply-To: <5641360F.5080901@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 9 Nov 2015 16:10:55 -0800, Bryan Drewery <bdrewery@FreeBSD.org> wro=
te:
> On 11/7/2015 7:14 PM, Jeffrey Bouquet wrote:
> > I've a not-complete-installworld from today, dumped core halfway throug=
h=20
> > despite single-user mode...
>=20
> Did you use -j to installworld?
>=20
> --=20
> Regards,
> Bryan Drewery
No. May have used -j 2 to buildworld...
Just then reading Makefile and Makefile.inc1 I was wondering (for lack of
which way to proceed... install to /tmp and rsync back over the system...)
Since the build tree appears to be too complex (Makefiles too numerous) to
test each command in installworld in advance before completion to be sure
the whole lot would complete, I wonder which of the targets in those two
files are most complete in making installworld complete, at the cost of a
longer buildworld.
Something like tinderbox; toolchain; > buildworld or whatever ensures that
all binaries, libraries etc used or referenced in the buildworld/installwor=
ld cycle
can complete a CLI without error; and that all target directories exist...
[I've had installworld fail due to missing target directories in=20
/usr/share for example.. which I patched up with a make -k ...]
A slight chance the installworld failed because of a drive bios quirk, thou=
gh the
chance is only slight
Another slight chance it was due to EIDE rather than SATA cabling...
Another slight chance it ran "too fast" and if slowed down (twenty Makefile=
s one starts
manually. sh Makefile.1 sh Makefile.2 ... ) may complete or at least be s=
crutinized
better.
.......................................................................
Just so reading this post doesn't entirely anyone's time, here is an alias =
to try
possibly...
[ most recent files in the current directory listed last] ... which I coul=
d use daily.
/usr/local/bin/gnuls -halstir |grep -v drw | awk '{print $11}'
...easier to read than the plain gnuls command above.
that I figured out today. Maybe duplicate of another "ls" alias
I've already crafted, but here too many to count... so I seldom remember
more than a few.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1Zvye9-0004gF-Fr>