-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
oh well, I am ashamed! Adding "provide = virtual/net/${NAME} virtual/net;" to
dhcpcd.i of course solved the problem. Thank's for your answer! :-) I think
the output of ngc -L is superfluous, then?
Another question: I want to use InitNG on a server, which has three nics. Two
of them are statically configured (these are the ones he "serves"), but the
third connects him to another subnet where he acts like a client and gets its
IP via DHCP. The problem is, that it mounts a NFS share from
the "client-subnet". I know that this isn't a good architecture, but I want
to keep this as an example for my consideration.
I would, to meet my needs, add net/eth0 and net/eth1 as statically-configured
devices, and daemon/dhcpcd/eth2 for the third mentioned interface.
system/netmount depends on virtual/net, which is provided by net/eth0,
net/eth1 and daemon/dhcpcd.i. What would satisfy its dependency:
(a) Either one of net/eth0, net/eth1 and daemon/dhcpcd, or
(b) All three, which means that all have to start up before system/netmount?
The problem with (a) is that system/netmount.i could start right after
net/eth0, but before daemon/dhcpcd.
Generally spoken, are service providers connected via OR or via AND?
Regards,
EMSPV
- ------ Original Message ------
Sender: Ismael Luceno <[EMAIL PROTECTED]>
Recipient: [email protected]
Date: Monday 24 July 2006 02:49
Subject: Re: [Initng] Network/DHCP and InitNG
>Eric MSP Veith escribió:
>> The DHCP link is the only one I use with this particular machine. If I add
>> daemon/dhcpcd/eth0 (and net/eth0, which just quits with returncode 0,
>> since the interface is configured via DHCP), system/netmount (which mounts
>> my /home directories) happens to be started *before* daemon/dhcpcd/eth0
>> runs. That's why I began editing the dhcpcd.i and net.i scripts adding
>> these "virtual/dhcp/${NAME}" entries.
>>
>> Perhaps I misunderstood something? Should I stop adding net/eth0 if I use
>> daemon/dhcpcd? But net.i is the only script providing virtual/net to, for
>> example, daemon/portmap?
>
>If you modify the dhcpcd script to put the interface up, then you should
>add "provide = virtual/net" to dhcpcd.i too.
>
>> Honestly spoken, I am confused, too. I thought I understood how use
>> and "provide = virtual/blah" works. :-/
>
>It's very simple:
>
>When a service that provides some other is started, that provided service
>is put in the DB, then when the service provider is up, the provided
>service gets the PROVIDED status.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFExCBAMpEdE19y46cRAriNAJwKDj6QOKRPNLrUuftMmbgN9V16qgCgmYM9
vov3R8+If951m+p+2bIahlw=
=LSUb
-----END PGP SIGNATURE-----
--
_______________________________________________
Initng mailing list
[email protected]
http://jw.dyndns.org/mailman/listinfo/initng
