[illumos-gate] 15732 Cannot bring down zone due to lingering IP references -- Andy Fiddaman <illumos⊙fn>

[illumos-gate] 15452 bge MAC_PROP_MEDIA support -- Robert Mustacchi <rm⊙fo>

[illumos-gate] 15733 Windows client gets disconnected when copying files to SMB share -- Matt Barden <mbarden⊙rc>

[illumos-gate] 15720 pcidr: the comparison will always evaluate as 'true' -- Toomas Soome <tsoome⊙mc>

what's generally preferred, and why? routeadm, or just enabling smf services directly?

I usually use routeadm, and because it's there

I usually assume if there's a facility for the admin to do something, and another more manual way, the tool is going to be the safer, supported-er, path.

But, `routeadm -u -e ipv4-forwarding` is exactly the same as just `svcadm enable ipv4-forwarding`.

yup, I'm just not one to go off into the woods on a technicality.

Does routeadm play with some SMF properties too? It's a while since I looked

Some things like that never sat well with me, but I highly prefer declarative configuration rather than imperative.

andyf: It can, but I don't need any of those.

the routeadm manual -- surprisingly to me -- says using svcadm too is fine

I'd rather just say that the service should be enabled rather than write a mini script to read the state and change it if necessary

it also says routeadm -u can't be used with other options though

so obviously there's some quirks in there :)

bahamat: I think that's what I did in ansible to kick routing on for tailscale, but I thought at the time "I should really have a routeadm module thingy for this"

I don't know, maybe routeadm is just syntatic sugar on top of svccfg for all the routing services. It's really hard to tell what the intended usage pattern is supposed to be.

I think that is basically it

But I also always hated SMF service properties. I like SMF a lot otherwise. I don't mind XML, but using svccfg to set/read properties...no thanks. Give me a flat file any day.

but I was surprised the service properties etc, are documented as also interfaces.

I remember using solaris 10, and the documentation for bind was to set all the smf service properties, then smf would modify your bind config for you. I *hated* that.

And thus the benefit of not steeping in any given OS. I didn't even know routeadm existed until just now.

bahamat: the goal (then?) was that all that stuff could be in an SMF profile, you would apply.

the flip side of that is that it handles persistent vs temporary, parsing, atomicity, etc for you

which many, many things often screw up

(even things in-gate)

which side-steps config management rather unfortunately.

e.g. dladm

richlowe: Yeah, but it makes config management a nightmare.

[illumos-gate] 15721 rcm_daemon: the comparison will always evaluate as 'true' -- Toomas Soome <tsoome⊙mc>