Starting networking without init.d?

[Tom H]

On Sat, May 29, 2010 at 9:09 PM, don fisher <hdf3 at comcast.net> wrote:
> Tom H wrote:
>> On Sat, May 29, 2010 at 7:40 PM, don fisher <hdf3 at comcast.net> wrote:
>>> Is there documentation that indicates how the functions that existed in
>>> /etc/init.d are to be performed. Such as starting and stopping networking?
>>>
>>> I would like to understand how the new system works. Most of the
>>> documentation links took me to a 404 page not found link.
>>
>> The /etc/init.d files that have been migrated to upstart have been
>> moved to /etc/init and replaced by a symlink in /etc/init.d to
>> /lib(init/upstart-job.
>>
>> You can start/stop /etc/init.d scripts with invoke-rc.d or service and
>> /etc/init scripts with initctl (or the start and stop symlinks to it)
>> or service.
>>
>> (By the way, if you are using NM, you will have to stop and start
>> networking using network-manager and not networking.)
>
> I am not using NM. I was trying to understand if that is why my upgraded
> system claims network not available. I gave up on NM and currently use
> wicd to select network links.
>
> Do you have any other ideas on what the omission of NM may cause?

I don't use NM and have never used WICD but as far as I have seen on
this list, WICD is a good replacement for NM for wifi but it doesn't
do 3G or VPN.