Steven wrote:
>
> Michael Polak wrote:
> >
> > Yes, so now you understand why Arachne should be
> > able to configure PPP even graphicaly ;-))))
>
> Certainly, a Linux+Arachne package for new users
> should configure everything (including PPP) as
> quickly and as easily as possible. Auto-probe,
> GUI, point-and-click. Whatever.
>
> However, things are quite different for existing users
> of Linux. They have already configured their systems.
> They are already climbing the learning curve of Linux.
> All they need is the bare-bones browser.
I already have my ppp set up on my machine and don't need, or want, an
application program changing what I already have set up. I'm not
talking learning curve here, I've already been there and don't want to
have to go back just to correct what Arachne or any other application
tried to change.
> It seems to me that the first step is to produce the
> bare-bones browser for the existing Linux community.
> This will enable debugging and optimization to begin.
> Later, when the browser is working smoothly, it can
> be incorporated into a comprehensive package targeted
> at new users.
I set up DOS based machines for my computer illiterate friends who can't
afford to buy a new Windows capable machine. I install Arachne on them
so they can have email and limited web browsing. I would like to be
able to do the same with Linux based machines and be able to eliminate
DOS.
> IMHO there is no need to consider ppp configuration
> at this stage. It is not required by the vast majority
> of Linux users. What we need right now is a working
> browser, and that is where all the energy should be
> going.
I have no problem setting up ppp access on Linux. All I need is Arachne
so I can give my friends a real operating system / browser combination.
> Cheers,
> Steven
Mark LaPierre
