Date: Sun, 1 Jun 2014 22:25:47 -0400 From: Jason Hellenthal <jhellenthal@dataix.net> To: Alfred Perlstein <bright@mu.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Jordan Hubbard <jkh@mail.turbofuzz.com> Subject: Re: Upgrading an i386 machine from amd64. Message-ID: <76274000-0CB3-4EF5-A745-4818F5E10C16@dataix.net> In-Reply-To: <538BDDF5.708@mu.org> References: <538B61EC.9000403@mu.org> <5B82C892-12A4-4251-B3D2-A6D3EAAF90F9@dataix.net> <538B6FCC.9090301@mu.org> <B007D0DE-EFC1-49D8-9E6A-F4A24B66DB8C@dataix.net> <538B761C.7060300@mu.org> <50E51CBE-7F7B-4093-86A5-320ACE81072E@dataix.net> <538B7937.2030104@mu.org> <098847BE-04B5-4E6F-98B8-87B5C7055C69@mail.turbofuzz.com> <538B8494.3040701@mu.org> <7977A65A-5ABE-49DD-8E76-074B54943D64@mail.turbofuzz.com> <538BDDF5.708@mu.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] mtree -deU /etc/mtree/filehere I believe that might roll through and set the proper perms and. schg flags. -- Jason Hellenthal Voice: 95.30.17.6/616 JJH48-ARIN > On Jun 1, 2014, at 22:14, Alfred Perlstein <bright@mu.org> wrote: > > >> On 6/1/14, 1:27 PM, Jordan Hubbard wrote: >>> On Jun 1, 2014, at 12:52 PM, Alfred Perlstein <bright@mu.org> wrote: >>> >>>> On 6/1/14, 12:45 PM, Jordan Hubbard wrote: >>>>> On Jun 1, 2014, at 12:04 PM, Alfred Perlstein <bright@mu.org> wrote: >>>>> >>>>> Unfortunately I'm doing it over NFS and I don't think we support chflags over NFS (not even with an extension). >>>> Try the installworld with NO_FSCHG=yes >>>> >>>> I think that catches at least 7 of the 8 places that need to be conditionalized. :) >>>> >>>> - Jordan >>> Thanks Jordan, >>> >>> I did wind up using that, but NFS still was giving me: >>> 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 >> Well, like I said, I think the NO_FSCHG implementation is incomplete. That’s weird though - bsd.lib.mk (in -current at least) does have a NO_FSCHG check. Are you sure that’s set in your environment? Did that change not make it into whatever branch you’re using, perhaps? > OK you were right about me forgetting to set NO_FSCHG in that pass, however even when I set it: > > /usr/src # NO_FSCHG=YES TARGET=i386 DESTDIR=/usr/soekris 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 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 > > It appears it's that schg is set on it on the target host: > > .(02:10:18)(alfred@soekris.local) > /lib % ls -lo libcrypt* > -r--r--r-- 1 root wheel schg 81988 Aug 16 2013 libcrypt.so.5 > -r--r--r-- 1 root wheel - 1468336 Aug 16 2013 libcrypto.so.6 > -r--r--r-- 1 root wheel - 1626140 Jun 1 11:15 libcrypto.so.7 > > Ugh, that was frustrating... but now fixed sorta... > > Is there a post-processing step i can do on the target install host to get my schg bits set on the right things? > > -Alfred > > > > > >> - Jordan >> >> >> _______________________________________________ >> 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" > > _______________________________________________ > 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 010 + 0 *H 90000 *H 010 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 130518085048Z 140519220947Z0H10Ujhellenthal@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!FTsD%pV^Eӑd¨x"9 г"f 00 U0 0U0U%0++0UڔfmVʢ$䟓0U#0Sr풜\|~5NԸQ0!U0jhellenthal@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#U0http://www.startssl.com/0 *H {0Ӹ,52W{Ey8b[{7 _+P"n["-,@ŽpJ-W$ݍjWA-6z( RdIZ.KzXє[K6}{s+v.Qh0PͅKhTw 0I73lz*Kv4Kkگ63;p1:ױ@)]ok>:W%XwC1þL/o8~#oP0400 *H 0}10 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1)0'U StartCom Certification Authority0 071024210155Z 171024210155Z010 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 00U00U0USr풜\|~5NԸQ0U#0N@[i04hCA0f+Z0X0'+0http://ocsp.startssl.com/ca0-+0!http://www.startssl.com/sfsca.crt0[UT0R0'%#!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&
