m68k not working past 3.5 (was: mac68k install process)

This is all I've seen on it.

Begin forwarded message:

> From: Ted Unangst <[email protected]>
> Date: April 19, 2004 5:52:34 PM CDT
> To: [email protected]
> Subject: CVS: cvs.openbsd.org: src
>
> CVSROOT:	/cvs
> Module name:	src
> Changes by:	[email protected]	2004/04/19 16:52:33
>
> Modified files:
> 	sys/kern       : kern_sysctl.c uipc_mbuf.c
> 	sys/sys        : sysctl.h
> 	sys/uvm        : uvm_extern.h uvm_init.c uvm_km.c uvm_km.h
>
> Log message:
> introduce a new km_page allocator that gets pages from kernel_map using
> an interrupt safe thread.
> use this as the new backend for mbpool and mclpool, eliminating the  
> mb_map.
> introduce a sysctl kern.maxclusters which controls the limit of  
> clusters
> allocated.
> testing by many people, works everywhere but m68k.  ok deraadt@
>
> this essentially deprecates the NMBCLUSTERS option, don't use it.
> this should reduce pressure on the kmem_map and the uvm reserve of  
> static
> map entries.
>

On Jul 2, 2004, at 9:34 AM, Matt R wrote:

> Well thats kinda crappy ;-)
>
> Seriously, I understand why dropping mac68k makes
> sense.  I 'll just raise a glass in its honor tonight
> when I get home.
>
> As far as it being broken, what exactly IS broken?
> I'll admit I haven't kept up on m68k as much as I used
> to, (was just looking into getting my mac68k 3.3
> machine upraded; last nights install was on the test
> machine), so I may have missed the "it's broken"
> email.
>
> And how broken is it?  I'll admit that if I offered
> help for fixing/keeping m68k up to date, I'll probably
> be way in over my head, but sink or swin, right?
>
> --Matt
>
>> Matt R wrote:
>>> Hey list
>>>
>>> after struggling with the mac68k installer, I've
>>> decided I wanted to do something about it.  I seem
>> to
>>> remember a conversation with the list back when
>> 3.3
>>> was new...something to the effect of " we have the
>>> source but can't compile it ".
>>>
>>> If someone would be so kind as to point me at said
>>> source and what tools they need or just let me
>> know
>>> what tools they need, I will find/get/buy/whatever
>> to
>>> get the freaking installer updated.
>>
>>
> ftp://ftp.openbsd.org/pub/OpenBSD/3.5/mac68k/utils/ 
> Installer_1.3_src.sea.hqx
>>
>> Can't remember what compiler this thing uses, it is
>> on the MacOS
>> platform.  It is pretty clearly spelled out in the
>> SEA file.  At this
>> point, the version used would be something like ten
>> years old -- I'm not
>> sure how much, if at all, the Mac world has kept
>> producing 680x0
>> development tools.  The hard part is finding it.
>>
>> However, a word of warning: All the m68k platforms
>> have been broke for
>> quite some time now, and I'm not aware of anyone
>> actively working on a
>> fix.  You will note no snaps for any of the m68k
>> platforms (hp300,
>> mvme68k, mac68k) have been made since 3.5 was
>> released.  No, it isn't
>> because we switched to gcc3 and are still waiting
>> for the first snap to
>> complete compilation...  At this point, I somewhat
>> suspect OpenBSD v3.6
>> will ship with a few less platforms.  Evolving the
>> installer at this
>> point may not be overly productive. 8-/
>>
>> Nick.
>> -- 
>> http://www.holland-consulting.net
>>
>>
>
>
>
> 		
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - 50x more storage than other providers!
> http://promotions.yahoo.com/new_mail