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

+++ Michael Lorenz [freebsd] [20/07/07 16:19 -0400]:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hello,
>
>On Jul 20, 2007, at 15:42, Sampson Stein wrote:
>
>>+++ Michael Lorenz [freebsd] [20/07/07 13:43 -0400]:
>>>-----BEGIN PGP SIGNED MESSAGE-----
>>>Hash: SHA1
>>>
>>>Hello,
>>>
>>>On Jul 20, 2007, at 13:31, Sampson Stein wrote:
>>>
>>>>+++ Michael Lorenz [freebsd] [20/07/07 13:19 -0400]:
>>>>>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=20
>>>>>>>>>>machine, but wouldnt using '-O /usr/netbsd/obj' to build.sh=20
>>>>>>>>>>result in paths being screwed up when installing from the mac?
>>>>>>>>>
>>>>>>>>>No. obj is for .o files and similar stuff, the actual userland=20
>>>>>>>>>you're building will show up in whatever dir you passed as=20
>>>>>>>>>destination using - -D
>>>>>>>>>
>>>>>>>>>>Also, how should I upgrade the userland and such on the mac..=20
>>>>>>>>>>the kernel, I just copied it... but I'm guessing if I did all=20
>>>>>>>>>>the building on the freebsd, I could use build.sh to install=20
>>>>>>>>>>too correct?
>>>>>>>>>
>>>>>>>>>Yes, but I usually prefer building tarballs ( build.sh sets,=20
>>>>>>>>>they'll show up in whatever you passed as release dir -R ) -=20
>>>>>>>>>tar xpzf base.tgz etc., then run 'postinstall fix' to get rid=20
>>>>>>>>>of obsolete files an such ( make sure /usr.src points at your=20
>>>>>>>>>sources or postinstall won't work )
>>>>>>>>>With tarballs you can build everything on FreeBSD and just=20
>>>>>>>>>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 /;=20
>>>>>>>>tar xpzf /path/to/tarballs/tarball.tgz; postinstall fix'
>>>>>>>>correct?
>>>>>>>
>>>>>>>Exactly. the p option is important so file permissions and=20
>>>>>>>ownership will be restored correctly - without that you'd end up=20
>>>>>>>with - for instance - a /usr/bin/su without suid bit set which=20
>>>>>>>therefore wouldn't work.
>>>>>>>
>>>>>>>have fun
>>>>>>>Michael
>>>>>>>
>>>>>>Alright man, thanks a lot. I got it working now, except for a=20
>>>>>>little hickup
>>>>>>in the postinstall fix command, I ran it again and it tries to do=20
>>>>>>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=20
>>>>>some reason ( sendmail was removed a while ago and replaced with=20
>>>>>postfix ) - that error is harmless, just delete the directory by=20
>>>>>hand.
>>>>>
>>>>>>as well as the output of 'ofctl -p'.
>>>>>
>>>>>Eh, I see the mach64 but it doesn't have an OpenFirmware ROM it=20
>>>>>seems so you won't be able to use it as console.
>>>>>
>>>>>>I also have attached an intel ethernet card, that works like a=20
>>>>>>charm.
>>>>>
>>>>>Most PCI device drivers should Just Work, even though many of them=20
>>>>>have never been used on macppc. You may want to pick up a cheap USB=20
>>>>>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=20
>>>>>kernel config:
>>>>>options OFB_FAKE_VGA_FB
>>>>>this lets X mmap the region usually occupied by the legacy VGA=20
>>>>>framebuffer ( 0xa0000-0xbffff ) which is unused on macppc but some=20
>>>>>stupid, PC-centric XFree86 drivers insist on playing with it even=20
>>>>>if it has no effect.
>>>>>options OFB_ALLOW_OTHERS
>>>>>This will allow the Xserver to access other devices than the=20
>>>>>console display through /dev/ttyE0. Obviously a monstrous security=20
>>>>>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
>>>>>
>>>
>>>>Thanks a lot man, everything's working like a charm... I'll try that=20
>>>>stuff
>>>>for X out, btw.. I have the config set to use the new adb and such,=20
>>>>works
>>>>great as well. Now to figure out what the heck to do with this thing=20
>>>>xD
>>>
>>>Gah, I just had a look at the source - OFB_ALLOW_OTHERS got nuked but=20
>>>if you really want to play with that I'll send you a patch. wsfb=20
>>>should work with the onboard fb though.
>>>
>>>have fun
>>>Michael
>>>
>>But I can only get 640x480 then right
>
>You'll get whatever the firmware set up, with OF 1.0.5 that's usually=20
>640x480 at 8 bit.
>
>have fun
>Michael
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.4 (Darwin)
>
>iQEVAwUBRqEYzMpnzkX8Yg2nAQIV3Af+JvI0k/25KS1vgcrnJClUjDghr46d8FQ3
>2K3wbo7MK76+N04rY74/TXKw/bqPYmWiHqCXFcmxccNqJHluWS5xKUiU8C+W19te
>o1gs0t6t2PwxHIAwjBuxrGGiPaW7fih/ULa7rK+/xSymqi8JakXvZqXjorEacCjn
>IyXioAzKP2dWunwiNNE3DlnaA+/K+OfcsyIoFxYgi7Q2CwfUKfwBWQZVqyDzgDC3
>nlX4yG1CplTQz0RVBjuPUpOUJR5jJAgaA8OI2XWH7GMrKaTRHJ6l28DLAtokloin
>0RnB8YHUSu5S3eb2oo8SAIhjE1GB2xLO/zBpGq1NYitRW1MTbZuVBg=3D=3D
>=3D06kE
>-----END PGP SIGNATURE-----
>
So would this work as a server of some sort then? I need to find some sort =
of
use for it.. heh.
--=20
Sampson C. Stein
b1tt3r -- You know.. like sugar?

The future not being born, my friend,
we will abstain from baptizing it.
		-- George Meredith

--BOKacYhQ+x31HxR3
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGoi8KmwmGN8fZjHgRAoANAJ41djVlB6V2vBmlbk5WWHsA/HPsEACfTRRj
I26VF1d2OCsM02xn5EZlfOU=
=FCtx
-----END PGP SIGNATURE-----

--BOKacYhQ+x31HxR3--