--envbJBWh7q8WU6mo
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

+++ Michael Lorenz [freebsd] [19/07/07 23:36 -0400]:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hello,
>
>On Jul 19, 2007, at 23:06, Sampson Stein wrote:
>
>>+++ Michael Lorenz [freebsd] [19/07/07 14:26 -0400]:
>>>-----BEGIN PGP SIGNED MESSAGE-----
>>>Hash: SHA1
>>>
>>>Hello,
>>>
>>>On Jul 19, 2007, at 14:02, Sampson Stein wrote:
>>>
>>>>I want to use that obj dir whilst building on the FreeBSD machine,=20
>>>>but wouldnt using '-O /usr/netbsd/obj' to build.sh result in paths=20
>>>>being screwed up when installing from the mac?
>>>
>>>No. obj is for .o files and similar stuff, the actual userland you're=20
>>>building will show up in whatever dir you passed as destination using=20
>>>- -D
>>>
>>>>Also, how should I upgrade the userland and such on the mac.. the=20
>>>>kernel, I just copied it... but I'm guessing if I did all the=20
>>>>building on the freebsd, I could use build.sh to install too=20
>>>>correct?
>>>
>>>Yes, but I usually prefer building tarballs ( build.sh sets, they'll=20
>>>show up in whatever you passed as release dir -R ) - tar xpzf=20
>>>base.tgz etc., then run 'postinstall fix' to get rid of obsolete=20
>>>files an such ( make sure /usr.src points at your sources or=20
>>>postinstall won't work )
>>>With tarballs you can build everything on FreeBSD and just unpack on=20
>>>the Mac.
>>
>>By /usr.src did you mean /usr/src?
>
>Yes. I'm fluent in typo :p
>
>>Also, should be unpacking these tarballs to /? like... `cd /; tar xpzf=20
>>/path/to/tarballs/tarball.tgz; postinstall fix'
>>correct?
>
>Exactly. the p option is important so file permissions and ownership=20
>will be restored correctly - without that you'd end up with - for=20
>instance - a /usr/bin/su without suid bit set which therefore wouldn't=20
>work.
>
>have fun
>Michael
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.4 (Darwin)
>
>iQEVAwUBRqAtxspnzkX8Yg2nAQJY+gf/X3abALn6MzYYC8mhKJ84tjRnveXXrUHp
>/8CQnSb5jjvNrBGxo2+4GMtZGiFys89EBprEup0CBCp6DrB3008RbKk/CdPAokKI
>aac7moPSXnJTg/iIFpWL332Q0oLVraxSfGWEaaZXYFcVlM76lSnmmEuvrxcmcom1
>9mzt3kGwsqtkftCMaNd/kFsFrEdm2Bj1k96LZ19csnM681oCLPFAbYyjwP5iGKpR
>PckvRAL/H3n+CWf/4s16ZhvNdfGErdLoOmI9vx3ATir/X2uTbFTAL3NZazci8ZQ+
>rfS6FjVXKUHp5znn3/GJ38YknHxu/JnvSVU4C33kCzD50DljkeuD+Q=3D=3D
>=3DDtE0
>-----END PGP SIGNATURE-----
>
Also, do you know how to set the date in open firmware 1.0.5? I've been
searching about but I cant seem to find anything.=20
--=20
Sampson C. Stein
b1tt3r -- You know.. like sugar?

A chicken is an egg's way of producing more eggs.

--envbJBWh7q8WU6mo
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFGoFF4mwmGN8fZjHgRAm0iAKCBmwhpXSzTwWORdNc7XhWhIG8lggCgpe2s
UCVELCEnD6ekaY/2xPzs8fs=
=Zr5b
-----END PGP SIGNATURE-----

--envbJBWh7q8WU6mo--