That spec seems to be missing the point entirely. The issue isn't just that it's CLI vs. GUI. It's that the CLI thing itself requires the user to try out about a thousand different ways to connect and provides no useful feedback (of any kind!) when it fails. Any sane user would rather have a CLI system that works and does the Right Thing (whatever that right thing may be) over a GUI system that is confusing, frustrating and poorly-documented.
In short, the issue isn't the UI, it's the functionality proper. Pppoeconf doesn't work, out of the box, for any system I've ever used it on. I'm sure it works for some people somewhere, and I'm sure that if you're really tenacious you can make it work on any system anywhere, but when <b>MICROSOFT</b> can make something complex work simply and quickly out of the box, not to mention every router box in the world, and Linux can't? It's time to make Linux catch up with what the rest of the world has been able to do for years. Linksys, incidentally, has a lot of GPLed code for their router and DSL boxes. Linksys routers, by coincidence, are easy to connect up to DSL setups. Perhaps a quick peek at <a href="ftp://ftp.linksys.com/opensourcecode";>ftp://ftp.linksys.com/opensourcecode</a> could make this happen quickly? -- DSL configuration is suboptimal. https://launchpad.net/bugs/52167 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
