-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Jul 20, 2007, at 01:35, Sampson Stein wrote:

> +++ Michael Lorenz [freebsd] [19/07/07 23:36 -0400]:
>>
>> Hello,
>>
>> On Jul 19, 2007, at 23:06, Sampson Stein wrote:
>>
>>> +++ Michael Lorenz [freebsd] [19/07/07 14:26 -0400]:
>>>>
>>>> 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
>>
> Alright man, thanks a lot. I got it working now, except for a little 
> hickup
> in the postinstall fix command, I ran it again and it tries to do the 
> part it
> failed on, which I will attach a typescript of it to this email,

It complains about being unable to remove /usr/share/sendmail for some 
reason ( sendmail was removed a while ago and replaced with postfix ) - 
that error is harmless, just delete the directory by hand.

> as well as the output of 'ofctl -p'.

Eh, I see the mach64 but it doesn't have an OpenFirmware ROM it seems 
so you won't be able to use it as console.

> I also have attached an intel ethernet card, that works like a charm.

Most PCI device drivers should Just Work, even though many of them have 
never been used on macppc. You may want to pick up a cheap USB card 
though, the one button Apple mice get annoying quickly in X.
So, you /may/ be able to use the mach64 in X - put this into your 
kernel config:
options OFB_FAKE_VGA_FB
this lets X mmap the region usually occupied by the legacy VGA 
framebuffer ( 0xa0000-0xbffff ) which is unused on macppc but some 
stupid, PC-centric XFree86 drivers insist on playing with it even if it 
has no effect.
options OFB_ALLOW_OTHERS
This will allow the Xserver to access other devices than the console 
display through /dev/ttyE0. Obviously a monstrous security hole, that's 
why it's not enabled by default.
Use the wsfb driver for the onboard fb and atimisc for the mach64.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRqDuocpnzkX8Yg2nAQIbVAf9GqPlqnhkGhlQVsdyWPrttaax+WKGb5Pj
BgRUGu9ZERFLU0D8dshf8ThERtZehTyCHS5Owu/puq5a4XgPlsPkftA26BTpfAC8
3nog/MYYQMpuM/zKbB3OrcqqYpfbtAV5bMdq89BxM8y+25uSdHo3OU80Y+8AL2kj
xFI8iwpTHYDncfeK0ce5g7S93ZlIcDnsRETJeONK9a3tD96vch8F7jNp2DJymmNH
2gwva21WCA+/3Qzeg8MD4dJOubC00fMdVP9NcRhBnspBpQKOvwPWcRJt6kNjMRbb
4v73XFA37arKEqRVW9k3Wok3pHek6Dy/+asoTolz8sn9vh0snHz6Hw==
=Wb06
-----END PGP SIGNATURE-----