> In the meantime, your best bet would be to create a > custom service > that's dependent on network/physical, or just a plain > old rc3.d > script, and add the desired "route add" command > there.
Hehe, uups! I came up with the same thing and posted it before I got down to reading this! Good call anyways. Now for Solaris 9 this will have to go into /etc/init.d/ The questions are though: a) for Solaris 9, should I link to the init.d/ script in rc2.d, or rc3.d? The default route should be up fairly early in the boot process, what is the earilest I could sucessfully pull it off? b) for Solaris 10, there are several possible SMF dependencies. Should I pick: svc:/network/physical:default or svc:/milestone/network:default or svc:/network/initial:default? Which of these would be most appropriate to list as a dependency, the way Sun would do it? It's extremely important to me that this be implemented as cleanly as possible and as Sun-like as possible (it'll even come onto the system as a package). This message posted from opensolaris.org _______________________________________________ networking-discuss mailing list [email protected]
