On Sat, May 12, 2012 at 01:57:38AM +1000, David Diggles wrote:
> Hi Nick,
> 
> Ok I'll tell you (and everyone) a little bit about it.
> 
> On Fri, May 11, 2012 at 07:27:00AM -0400, Nick Holland wrote:
> > If you are running an m68k machine, it's a labor of love, I really have
> > difficulty believing that it's a practical event.  And since you only
> > talk of releases over three years old, again, I'm hoping this is not a
> > production machine of any kind.
> 
> You are correct.  It's more of an animated ascii art lava lamp,
> novelty.  It was in production serving http when 4.4 was current,
> but I think after 4.5, mac68k no longer had a maintainer, so it
> just became a lava lamp.

At least snapshots are appearing now. There was a big gap before.
I'm thankfull.

> 
> > So...build what you want!  It's part of the fun!
> 
> Maybe, if I NFS mount src and ports.  It doesn't have a lot of disk space.

That works. I also run my Quadra 650 diskless. [Miod made me a
patch not-commited. I do have to ftp any new kernel from the NFS
server into the local MacOS partition. But it allows me to keep the
whole local disk for MacOS.]

> 
> > As for cross compiling: 1) no.  2) WHY?  that's like jogging for health,
> > and taking a short cut because its easier...
> 
> Well I did worse.  Lazy cheat.  I left 4.4 on it, installed what
> I needed from 4.2 packages, symlinked any any libs it complained
> about.
> 
> > And run 5.1, building the packages you want shouldn't take more than a
> > few weeks.
> 
> When I installed 4.4, I modified the install script to accept tar
> instead of tgz to save time.  If I did it again, I would have also
> made it skip the keygen sequence on the first boot, as it takes
> half a day.  This could be generated somewhere else and copied over
> post install.
> 

That remind me when the arch was still using BSDtar from within
MacOS. That was so painfully slow that I was making myself smaller
tar set so I didn't have to run the thing more than the minimum.
Was also untarring a filled /dev/ tree so BSDtar wouldn't run
have to run MAKEDEV.

That's a good trick modifying the install script for .tar. I often
forget about ssh-keygen but I have no patience for it. More than
10 minutes and I just interrupt the booting process and create them
elsewhere for download.

At around OpenBSD 4.6, I really try to re-install on my LCII. A
machine more awful than your SE/30. But I went nowhere with it. It
must run a non standard kernel very small and wouldn't load bsd.rd.
And there was an "ae" driver fault introduced when ae was moved from
arch/mac68k to arch/m68k. So I had no network on it. It was still
a lot of fun even if I wasn't succesfull.

[I need a mouse and keyboard cable for that machine so I can run
it at the same time than my Quadra.]

My Quadra has been off for while. I really need to start it up and
try to get 5.1 on it. I'll check for building packages but I think
only the most simple programs will work. It use gcc 2.9 and that
is starting to be old and only m68k, m88k and vax are still using
it. They are also the only arch on the old non-ELF toolchain. But
at least m68k has shared librairies.

It will probably not be until next week-end but I could take package
requests for 5.1.

Also, mac...@openbsd.org is not completly dead. I'm still subscribed
even if the ratio of SPAM to genuine post is high.

> I also run telnetd on it from an older version of obsd (i think
> it was removed somewhere back in the 3.x series)... because ssh
> takes 10 mins to login.  PF restricts this by IP and OS, to another
> obsd local box.

Sometimes I would downgrade to SSH version 1 because that was
slighty faster than version 2. But nothing beats telnetd I guess.

This works for me in 5.0, will need to test in 5.1 when I get there:

cvs -d anon...@anoncvs.openbsd.org:/cvs get -PA -rOPENBSD_3_7 \
        -d telnetd src/libexec/telnetd
cd telnetd
mkdir obj
make KERBEROS5=no depend && make KERBEROS5=no && \
        make BINDIR=/usr/libexec install

Reply via email to