Heads up: idmapd changes and BFU

Heads up: idmapd changes and BFU

Date: Fri, 14 Dec 2007 22:20:37 -0600
From: Nicolas Williams <Nicolas.Williams at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com, on-all at eng dot sun dot com, cifs-team at sun dot com
Subject: Heads up: idmapd changes and BFU

If you've never run the SMB server in domain member mode, or if you
eventually do but never care to BFU backwards past the snv_81, then you
can ignore this heads up message.

The putback for:

PSARC/2007/616 Winchester update for diagonal ID mapping
6587015 wildcard rules should have better case-sensitivity options
6587455 case-insensitive Windows user/group name matching is crucial
6607916 "diagonal" mapping needed (mapping windows users to GIDs and groups to UIDs)
6630586 idmap panic: process termintated by SIGSEGV
6635629 libc's lint library needs to know about u8_textprep functions
6637550 idmap crashes after auto-discovery fails

changes the schema for the ID mapping service (svc:/system/idmap).

idmapd(1M) will automatically upgrade the running schema on restart or
reboot, so BFU will get you past this change.

However, a backwards BFU will not get you past this change.

If you have svc:/system/idmap:default enabled and wish to BFU backwards
past this putback then you must:

 - list or export and save whatever name-based rules you have
   (/usr/sbin/idmap list or export)

 - svcadm disable idmap

 - rm /var/idmap/idmap.db /var/run/idmap/idmap.db

 - BFU and reboot

 - restore your name-based rules

   This last step cannot be automated because this putback extends the
   semantics of ID mapping name-based rules in such a way that some new
   rules cannot be carried backwards losslessly.

If you should forget to follow this procedure that's OK, your system
will not turn into a brick ~-- simply stop the idmap service, remove
those two databases, and restart the idmap service.

Nico
~--