If you haven't tried them yet, I'd recommend using jmmv's sysbuild & sysupgrade tools (http://blog.netbsd.org/tnf/entry/introducing_sysbuild_and_sysupgrade) for consistent builds & upgrades without much manual interventions...
/P On Oct 18, 2014, at 13:47 , Paul Goyette <[email protected]> wrote: > Ooopppsss! > > > <red-face> > > Seems like I forgot the -p option when untarring the distribution sets! > > Turns out that /usr/bin/su was also missing the Set-UID bit, and fixing that > make su(1) work again, too! > > Thanks for all the quick rpelies that led to finding the solution. > > > > > On Sat, 18 Oct 2014, Havard Eidnes wrote: > >>>>> It's not at all clear to me where maildrop directory is. And it is > >>>>> also not clear to me why this is broken, since I took great pains to > >>>>> avoid modifying the postfix {master,main}.cf files during etcupdate. >>>> >>>> I hit that last week - I think it is a change postfix... >>>> >>>> $ ls -ld /var/spool/postfix/maildrop >>>> drwx-wx--- 2 postfix maildrop 512 Oct 18 10:12 >>>> /var/spool/postfix/maildrop >>> >>> Yep, that's what my machine says, too. (Identical except for the >>> mtime.) >>> >>> But, since postdrop runs as setgid=maildrop it should be able to write >>> the files: >>> >>> $ ls -l `which postdrop` >>> -r-xr-xr-x 1 root wheel 183109 Sep 30 00:38 /usr/sbin/postdrop >>> >>> Any clue on how to fix? >> >> Yesterday I upgraded a local host (via local src build) to 6.1.5 >> and have: >> >> # ls -l `which postdrop` >> -r-xr-sr-x 1 root maildrop 183109 Oct 17 13:41 /usr/sbin/postdrop >> # >> >> Regards, >> >> - Håvard >> > > ------------------------------------------------------------------------- > | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | > | (Retired) | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com | > | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net | > | Kernel Developer | | pgoyette at netbsd.org | > -------------------------------------------------------------------------
