17:16:14 <patrikr> i just compiled mksh from sources, installed it in /opt/local. i tried using passwd -e to set it, but that errors out saying its unacceptable, editing /etc/passwd directly worked fine but im curious as to how to make it an acceptable shell
17:26:44 <rmustacc> I think the bit here is what's found in the getusershell(3C) manual with the need to put something in it looks like an /etc/shells?
17:30:07 <patrikr> ah, i assumed that because there is no /etc/shells that file just wasnt used on illumos
17:30:11 <patrikr> thanks
17:30:46 <rmustacc> No, it falls back to the built-in list defined in the manual.
17:31:07 <rmustacc> You'll need to add the built-in ones you want as I think the presence of the file overrides all built-ins.
17:32:20 <patrikr> yeah i just noticed trying to test it
17:33:27 <patrikr> The getusershell() function opens the file /etc/shells, if it exists,
17:33:27 <patrikr>        and returns the next entry in the list of shells. I feel like the wording implies it uses the built-in list first then uses whatevers in /etc/shells
17:35:06 <patrikr> maybe I'm confused
17:36:04 <rmustacc> If you read the first paragraph of the description I thought that made the behavior fairly clear?
17:36:23 <rmustacc> At least, it did for me. But certainly we can always make these things clearer.
17:43:37 <patrikr> it's mostly about using 'the list' when just having listed the built-in list, i think it tripped me up
17:43:55 <patrikr> anyway, works as expected now with the /etc/shells populated
17:44:55 <patrikr> also would be nice if passwd -e would accept an absolute path to a shell instead of having the prompt