[Sugar-devel] life w/o NM
Mikus Grinbergs
mikus at bga.com
Fri Dec 5 01:52:08 EST 2008
paul wrote:
>
> aleksey wrote:
> > as far as I can understand, NM is required to monitor/set net
> > devices/self IPs. Is it necessary to use it in case of common
> > desktop e.g. w/o wireless and with stable ethernet connection?
>
> no, certainly not. unix systems with ethernet have existed far
> longer than network manager. (NM isn't _required_ for the
> wireless case, either.) but is it worth _not_ using network
> manager for that one, mostly exceptional, case? probably not.
> the trick is making sure network manager works correctly for that
> case.
Been running my XO since Dec 2007 w/o wireless and with a stable
ethernet connection.
I'm a believer in 'manual control', and would like to *tell* NM
what_to_do/what_not_to_do. From my perspective, the implementation
of NM in Sugar has been for 'automatic control', with no user input
needed/allowed. One result has been several open tickets [for
example, current NM sets up only an IPv6 address for the XO, and in
general NM does not support a static IPv4 address for the XO].
What I would like to do is to use ethernet in place of an AP, but be
able to collaborate with other XOs over the mesh. Please forgive me
for saying that in the past year I've found NM to be an obstacle.
mikus
More information about the Sugar-devel
mailing list