James Carlson <[email protected]> writes: > Harry Putnam wrote: >> James Carlson <[email protected]> >> writes: >>> The big problem you'll run into with restarting physical:default is CR >>> 6181431 -- that service lacks a 'stop' method, so restarting it doesn't >>> really do what you want. (And restarting NWAM should just never be >>> necessary. If you have to do that, then at least contact the NWAM team, >>> and perhaps also file a bug.) >> >> So do you mean to say then that if I wanted to change from a dhcp >> provided address to a static address... I could just edit >> /etc/nwam/llp to say: >> >> rge0 static 192.168.0.29 >> >> And edit /etc/hosts to comply with that. >> >> And from there on that's my new static address... no retarting of >> anything required? > > Not exactly. The new NWAM (in development now) has a configuration > interface -- comand line and GUI tools -- and doesn't force you to edit > text files to control the system. > > But, yes, the broader idea is that. You shouldn't have to go through > acrobatics to do something simple like this.
I guess I'm wondering how it is less acrobatic to work thru some kind of config tool, than to edit a text file. To do the job I mentioned (change from dhcp served IP to a static IP). What would these cmdline configuration tools require me to do? And what changes would take place in the filesystem? _______________________________________________ networking-discuss mailing list [email protected]
