Quote:> I've had almost no luck setting up networking in LinuxPPC R5. To boot, I
> keep hearing wonderful news about how "pump" is screwed up.
One more bug in the initial RedHat 6.0 release that has been fixed for
quite some time now...
Quote:> At this point, I don't care if I'm running 4 or 5 -- I just want the silly
> thing to work.
Someone posted a note about how to setup a working dhcp a while ago.
I'm not sure it used `pump' or not; a little search on Deja should
reveal it.
This is, by the way, not an R4-vs-R5 thing. IMHO, this is where linux
architecture is exhibiting its downside; networking implies kernel-level
hacquery in Linux, with the effect that a kernel update may necessitate
a slew of changes to other code. With the arrival of the 2.2.x kernel,
one of the things that broke happened to be dhcp. And it usually takes
a while for the dust to settle down if such a thing happens...
From my personal experience: going from R4 to R5 wasn't painless
(morale: don't update, just reinstall from scratch), and installation
wasn't as smooth as R4. But once installed, and once (most of) the
well-known issues (as discussed here) were resolved, I ended up with a
Unix in which important things now actually *work* (e.g. some forms of
dynamical loading).
Quote:> And IPNetRouter running on the MacOS is looking sweet -- at least it worked.
Yes, IPNR is a very sweet program. It helps of course that Mac OS
offers the advanced networking architecture (and performance) of the
Mentat streams architecture: thinks like proxying and routing are
hideous hacks in classic Unix `sockets' networking, which is one of the
reasons you won't find it in a more modern Unix like Solaris or HP/UX.
If all you need is make a router of existing PPC hardware, there's
little reason for LinuxPPC, if you ask me. I've seen ancient hardware
run IPNR smoothly and without a glitch for months in a row.
-- J$
--
dash dash space
this is my .sig it's not so .big
by