vasco.nevoa at sapo.pt
vasco.nevoa at sapo.pt
Thu Sep 25 13:22:54 CEST 2008
If resolvconf isn't doing what it should, then it is our
responsibility as users to file enough bugs with enough pertinent info
until it is corrected.
If you have a clear use case that fails, open a ticket.
I don't care which kind of connection management system is inside
openmoko, as long as it works and is flexible to accommodate any
networking scenario we may come up with (which pretty much narrows it
down to resolvconf IMHO).
Let's make it work, ok? File the necessary bugs.
Citando roguemoko at roguewrt.org:
> OK, so this resolvconf thing is inherited from debian and has been
> implented obviously without much thought to general functionality. I say
> this in the context of normal (non-debian) services functioning as
> expected when not massaged by resolvconf.
> I understand the intention, don't get me wrong, and it is indeed a nice
> idea. But when all people want to do is gain connectivity with their
> chosen method, this resolvconf facility seems to be more of a hinderence
> and is unlike a lot of linux distros. Shouldn't this, at least
> currently, be optional?
> If something as fundamental as _core_ network services are going to be
> overlayed with something like this, it should really be working first,
> rather thaan people editing files left and right without understanding why.
> This is just what I think, take it as you will. In the end I am the
> master of my device ;)
> I've actually just done a bit of research before posting and it
> _appears_ this was implemented with good intention, just without the
> required software support. It seems to be very much of debian origins
> and a little bit of overkill for managing the facilities on the
> freerunner, but that's just my opinion. If I was currently using usb0,
> eth0 and a tun/tap interface simultaneously, that all flapped or had
> dynamic dns requirments (sounds more like a router) it would make sense
> to me. I imagine the end goal is to consolidate gprs and wifi dns but
> currently no resolvconf is going to teach people how to get that going.
> When om2008 is mature and these kind of connections can be made easily,
> without much knowledge, this utility would be a godsend ... as it stands
> you currently need basic linux knowledge to understand why things don't
> work and then you need to know how to manipulate resolvconf.
> Maybe it's my BSD upbringing, thanks for the clarification however. :)
> Openmoko community mailing list
> community at lists.openmoko.org
More information about the community