> Do you mean 'full-time IP connectivity', because if you can setup a UUCP
> connection, you can just as easily setup a PPP connection over the same
> medium, giving you IP connectivity.

True, but there's a lot more infrastructure overhead involved in
setting up a group of disconnected machines via dialup IP than
there is connecting them via UUCP. And where dialup time is precious
UUCP is the hands-down winner for not wasting any of that dialup

> therefore doesn't belong in the mainstream release.  It *is* still
> available as an add-on port, so those who need it can still get it

So the base distribution contains /bin/sh, /sbin/init, and
/sbin/pkg_add? Me, I like my bikesheds painted in white and green
zebra stripes.

>   Finally, the security
> issues make it a non-starter to keep in the default distribution.

I would like to see evidence of where --config is *required* to
make someone's UUCP setup work. And what percentage of the overall
UUCP user population are represented by those people? I still
contend the "problem" can be fixed by removing --config. While that
fix will apparently impact some people, the impact of that fix is
a lot lower than ripping out UUCP altogether.


We've heard that a million monkeys at a million keyboards could produce
the Complete Works of Shakespeare; now, thanks to the Internet, we know
this is not true.
                        -- Robert Wilensky, University of California

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to