Date: Sun, 1 Jun 2014 13:34:35 -0400 From: Jason Hellenthal <jhellenthal@dataix.net> To: Alfred Perlstein <bright@mu.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Upgrading an i386 machine from amd64. Message-ID: <5B82C892-12A4-4251-B3D2-A6D3EAAF90F9@dataix.net> In-Reply-To: <538B61EC.9000403@mu.org> References: <538B61EC.9000403@mu.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] What if you just NFS mount the obj directory from the 386 to the amd64 build world for 386 the mount the src on the i386 and just rebuild strip and friends ? A little more of a hack i know but would get the job done. -- Jason Hellenthal Voice: 95.30.17.6/616 JJH48-ARIN > On Jun 1, 2014, at 13:25, Alfred Perlstein <bright@mu.org> wrote: > > Hello hackers. > > Is there a way to build on amd64 and then mount over nfs the build and src and installworld from an i386 machine? > > The problem seems to be that "install" and "strip" and etc are built as amd64 binaries so that the installworld will fail. > > Below I have a solution I was going to do a blog post about, but then realized maybe I'd be leading people down the wrong path. > > Can someone verify that I need to use rsync as opposed to installworld for this to work? > > I have an old i386 based soekris geode box called "soekris": > CPU: Geode(TM) Integrated Processor by AMD PCS (499.91-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x5a2 Family = 0x5 Model = 0xa Stepping = 2 > Features=0x88a93d<FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CLFLUSH,MMX> > AMD Features=0xc0400000<MMX+,3DNow!+,3DNow!> > real memory = 536870912 (512 MB) > avail memory = 502792192 (479 MB) > > Building on this machine is difficult because of the speed and lack of space, so I decided to use my more powerful amd64 machine "spigot": > CPU: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz (3392.37-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x206a7 Family=0x6 Model=0x2a Stepping=7 > ... > real memory = 17179869184 (16384 MB) > avail memory = 16585228288 (15816 MB) > FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads > > So I've built an 10-stable on the amd64 machine using: > > spigot % TARGET=i386 > spigot % make -j24 buildworld > spigot % make -j24 buildkernel > > Works great, I get an i386 object tree under /usr/obj/i386.386/... > > Then I go to install this over NFS and this is where I get stuck. > > If I mount the i386 machine like so and install I get errors on libc and other libraries: > > spigot % mount soekris:/ /usr/soekris > spigot % cd /usr/src && make installworld > ..... > ===> lib/libcrypt (install) > install -C -o root -g wheel -m 444 libcrypt.a /usr/soekris/usr/lib > install -C -o root -g wheel -m 444 libcrypt_p.a /usr/soekris/usr/lib > install -s -o root -g wheel -m 444 -fschg libcrypt.so.5 /usr/soekris/lib > install: /usr/soekris/lib/libcrypt.so.5: Input/output error > *** Error code 71 > > Stop. > make[5]: stopped in /usr/trees/freebsd.git/lib/libcrypt > *** Error code 1 > > OK, so that doesn't work... > > Maybe if I mount the amd64 build host under the soekris box, no that breaks because the bootstrap tools (install(1), strip(1)) are built for amd64 so the install fails. > > So what I finally did on the amd64 box was: > > spigot % mkdir /use/soekris.local > spigot % make installworld DESTDIR=/usr/soekris.local > spigot % mount soekris:/ /usr/soekris > spigot % rsync -avvH /usr/soekris.local/ /usr/soekris/ > > That hung at the end forever at the end: > var/unbound/ > var/yp/ > var/yp/Makefile > var/yp/Makefile.dist > .... > > but after giving it an hour I just hit ^C and rebooted and everything was more or less fine. > > Is there a better way to do this? Was the "installworld to NFS" breaking because of NFS bugs? Should I get those to Rick? I'm just confused. > > -Alfred > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" [-- Attachment #2 --] 0 *H 01 0 + 0 *H 90000 *H 01 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 130518085048Z 140519220947Z0H1 0 U jhellenthal@dataix.net1%0# *H jhellenthal@dataix.net0"0 *H 0 '`TmfkܨJ5u +c'Upb`zv)&ȸXZ*VN6JvLoVoh}g pQDŽKf/tZA˳( "4Ԅ˻'d2h| IBl' ^v^;'e8S99ۿVm|k8_UQtC"5l!kjZ]އQGn \Bh!F TsD%pV^Eӑd¨x"9 г" f 00 U 0 0 U 0 U %0++0 U ڔfmVʢ$䟓0 U #0Sr풜\|~5NԸQ0!U 0jhellenthal@dataix.net0LU C0?0; +70*0.+"http://www.startssl.com/policy.pdf0+00' StartCom Certification Authority0This certificate was issued according to the Class 1 Validation requirements of the StartCom CA policy, reliance only for the intended purpose in compliance of the relying party obligations.06U /0-0+)'%http://crl.startssl.com/crtu1-crl.crl0+009+0-http://ocsp.startssl.com/sub/class1/client/ca0B+06http://aia.startssl.com/certs/sub.class1.client.ca.crt0#U 0http://www.startssl.com/0 *H {0Ӹ,52W{Ey8b [ {7 _+P"n["-,@ŽpJ-W$ݍjWA-6z( RdIZ. KzXє[ K6}{s+v.Qh0PͅK hTw 0I73lz*K v4Kkگ63;p1:ױ@)]ok>:W%XwC1þL/o8~#oP040 0 *H 0}1 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1)0'U StartCom Certification Authority0 071024210155Z 171024210155Z01 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0"0 *H 0 -).2AUGo#G B|NDRpM-B=o -we5JQpa>O.#._<V [~**pz~3WG .ᘟMlr[<Ce6fqO"uxfWN#uicgkv$Lb%y`_{`xK'GN 00U 00U 0 U Sr풜\|~5NԸQ0 U #0N @[i04hCA0f+Z0X0'+0http://ocsp.startssl.com/ca0-+0!http://www.startssl.com/sfsca.crt0[U T0R0'%#!http://www.startssl.com/sfsca.crl0'%#!http://crl.startssl.com/sfsca.crl0U y0w0u +70f0.+"http://www.startssl.com/policy.pdf04+(http://www.startssl.com/intermediate.pdf0 *H }x,\c^ #wMq}>UK/^yX֏y frMIŲB61ymQҨݬZ0& ;@#13qۑ& ̢o 6r_;GO>*I( 74XS1r3)!LJy6Kotˆ# _wSr ;B ADp(fs 䰷6%.W0J3:bC<8t X1<Cn=t==wST~\wkBf|15zUP)(IjVB!OfI=bb\4-*em/нSJm7N[]'@ڽ D9Kr>R7/|o^I@ټ'Pa $ z9a'L)( I}vcH]۸D*W} m>Q|C.(,lQ000 *H 0}1 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1)0'U StartCom Certification Authority0 060917194636Z 360917194636Z0}1 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1)0'U StartCom Certification Authority0"0 *H 0 lF|x{3rb6 "$^wC d̎68#nm<r =3+/AYg} tyL7z9RYFC҅qub4, 4ǖR=3M ;JK&/ r5w<]&6v\t%x- 0-ryF*I cSb:̵fkt+v>mDsb ;ľSV%lQ ʿvmۿ=f VH:KߧXP8u[C lMp[)eݪ]̯1 ҍ{n'f HnB?!>{ pclT\%zɢɋ,~^MXn 2n6IHiMi y"H{ipz7 vOW`g:ԋr"Ɵƶ\R<*s `z/ۣn&0݉W=+ŷv+*r3] KtRK R0N0 U 00 U 0 U N @[i04hCA0dU ]0[0,*(&http://cert.startcom.org/sfsca-crl.crl0+)'%http://crl.startcom.org/sfsca-crl.crl0]U T0P0L +70;0/+#http://cert.startcom.org/policy.pdf05+)http://cert.startcom.org/intermediate.pdf0+00' Start Commercial (StartCom) Ltd.0Limited Liability, read the section *Legal Limitations* of the StartCom Certification Authority Policy available at http://cert.startcom.org/policy.pdf0 `HB 08 `HB +)StartCom Free SSL Certification Authority0 *H lf 4Ѕ^} N8 ^ߦ%K2;=D [I)f% <6+Kh9f=&9 Q{~ZWpi^X ߌE8 ^Wbz )n(DÐ8<CMdE(\s{諱.\dns1:}Q;Mf{<Ӛ ePu/CiyCFrd6% 8w~kjDKx, KD4R' ]xS2݀fuٵh(a.8 gd./pǖ|eCTݥ9`4ɖp, H{ ~k";*RKU"4N&",uJ} d6/# ;sIjWxřCcMw-eriG V$ yX. ~m >J9+u U77Cb VKel$$4"}?eQ 0j r^1o0k001 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 + 0 *H 1 *H 0 *H 1 140601173436Z0# *H 1dϼMX]F2r0 +71001 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 *H 101 0 UIL10U StartCom Ltd.1+0)U "Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 *H xt< vg5+q< }GݿV {^QF#\C*KygKƎk74`_R+=ֳ ?[:UCH Q:9Ad%notpVɠu_U;1Φ,3ס Cwݬf5c%(;y2Ys[@phgi.۞ϔaӱ}FJRL!LЀ h/9A4CİH@Xf$nzhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5B82C892-12A4-4251-B3D2-A6D3EAAF90F9>