-----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, 
>>> but wouldnt using '-O /usr/netbsd/obj' to build.sh result in paths 
>>> being screwed up when installing from the mac?
>>
>> No. obj is for .o files and similar stuff, the actual userland you're 
>> building will show up in whatever dir you passed as destination using 
>> - -D
>>
>>> Also, how should I upgrade the userland and such on the mac.. the 
>>> kernel, I just copied it... but I'm guessing if I did all the 
>>> building on the freebsd, I could use build.sh to install too 
>>> correct?
>>
>> Yes, but I usually prefer building tarballs ( build.sh sets, they'll 
>> show up in whatever you passed as release dir -R ) - tar xpzf 
>> base.tgz etc., then run 'postinstall fix' to get rid of obsolete 
>> files an such ( make sure /usr.src points at your sources or 
>> postinstall won't work )
>> With tarballs you can build everything on FreeBSD and just unpack on 
>> 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 
> /path/to/tarballs/tarball.tgz; postinstall fix'
> correct?

Exactly. the p option is important so file permissions and ownership 
will be restored correctly - without that you'd end up with - for 
instance - a /usr/bin/su without suid bit set which therefore wouldn't 
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==
=DtE0
-----END PGP SIGNATURE-----