> On Oct 1, 2015, at 21:20, Jeremy Huddleston Sequoia <[email protected]> > wrote: > > >> On Oct 1, 2015, at 04:23, Richard L. Hamilton <[email protected]> wrote: >> >> ...as part of the "rootless"/System Integrity Protection setup, presumably. >> >> Specifically, >> >> apple:Fonts root# pwd >> /Library/SystemMigration/History/Migration-AF8CBD75-2455-4B1C-A87C-296C69E2FABE/QuarantineRoot/System/Library/Fonts >> lapple:Fonts root# ls >> encodings.dir fonts.dir fonts.list fonts.scale > > The install removes them just like older OS installs removed them. Nothing > changed in that regard. > > There is an exception in rootless to allow us to create these files. > >> (the part after Migration- probably varies) >> >> I imagine that means the fonts in /System/Library/Fonts are no longer >> available to the X server. > > No, those files should be recreated on first launch.
I haven't seen them, and I've certainly run the X11 app since upgrading to 10.11. Nor do I see an exception entry: sh-3.2# grep -i /System/Library/Fonts /System/Library/Sandbox/rootless.conf sh-3.2# >> >> The specific font files in there (and presumably no longer usable by the X >> server) are: >> Apple Braille Outline 6 Dot.ttf >> Apple Braille Outline 8 Dot.ttf >> Apple Braille Pinpoint 6 Dot.ttf >> Apple Braille Pinpoint 8 Dot.ttf >> Apple Braille.ttf >> Apple Color Emoji.ttf >> Apple Symbols.ttc >> AppleSDGothicNeo.ttc >> AquaKana.ttc >> ArialHB.ttc >> Avenir Next Condensed.ttc >> Avenir Next.ttc >> Avenir.ttc >> Courier.dfont >> GeezaPro.ttc >> Geneva.dfont >> HelveLTMM >> Helvetica.dfont >> HelveticaNeue.dfont >> HelveticaNeueDeskInterface.ttc >> Hiragino Sans GB W3.ttc >> Hiragino Sans GB W6.ttc >> Keyboard.ttf >> Kohinoor.ttc >> KohinoorBangla.ttc >> KohinoorTelugu.ttc >> LastResort.ttf >> LucidaGrande.ttc >> MarkerFelt.ttc >> Menlo.ttc >> Monaco.dfont >> Noteworthy.ttc >> Optima.ttc >> Palatino.ttc >> PingFang.ttc >> SFNSDisplay-Black.otf >> SFNSDisplay-Bold.otf >> SFNSDisplay-Heavy.otf >> SFNSDisplay-Light.otf >> SFNSDisplay-Medium.otf >> SFNSDisplay-Regular.otf >> SFNSDisplay-Semibold.otf >> SFNSDisplay-Thin.otf >> SFNSDisplay-Ultralight.otf >> SFNSText-Bold.otf >> SFNSText-BoldG1.otf >> SFNSText-BoldG2.otf >> SFNSText-BoldG3.otf >> SFNSText-BoldItalic.otf >> SFNSText-BoldItalicG1.otf >> SFNSText-BoldItalicG2.otf >> SFNSText-BoldItalicG3.otf >> SFNSText-Heavy.otf >> SFNSText-HeavyItalic.otf >> SFNSText-Light.otf >> SFNSText-LightItalic.otf >> SFNSText-Medium.otf >> SFNSText-MediumItalic.otf >> SFNSText-Regular.otf >> SFNSText-RegularG1.otf >> SFNSText-RegularG2.otf >> SFNSText-RegularG3.otf >> SFNSText-RegularItalic.otf >> SFNSText-RegularItalicG1.otf >> SFNSText-RegularItalicG2.otf >> SFNSText-RegularItalicG3.otf >> SFNSText-Semibold.otf >> SFNSText-SemiboldItalic.otf >> STHeiti Light.ttc >> STHeiti Medium.ttc >> STHeiti Thin.ttc >> STHeiti UltraLight.ttc >> Symbol.ttf >> Thonburi.ttc >> Times.dfont >> TimesLTMM >> ZapfDingbats.ttf >> ヒラギノ明朝 ProN W3.ttc >> ヒラギノ明朝 ProN W6.ttc >> ヒラギノ角ゴシック W0.ttc >> ヒラギノ角ゴシック W1.ttc >> ヒラギノ角ゴシック W2.ttc >> ヒラギノ角ゴシック W3.ttc >> ヒラギノ角ゴシック W4.ttc >> ヒラギノ角ゴシック W5.ttc >> ヒラギノ角ゴシック W6.ttc >> ヒラギノ角ゴシック W7.ttc >> ヒラギノ角ゴシック W8.ttc >> ヒラギノ角ゴシック W9.ttc >> >> >> I disabled rootless, because I have other stuff I've ported that needs to be >> in /usr (like a PAM module in /usr/l/ib/pam > > Why not use /usr/local/lib/pam instead Where is that documented? Or do I have to use full paths in /etc/pam.d/* configuration files? >> , or various items in /usr/share > > Why not use /usr/local/share instead? Will added terminfo or zoneinfo or similar files placed in the corresponding directory there be automatically found, or will all such cases require full pathnames or environment variables to be set to use them? It's not that I want to be able to modify most system files (although I can imagine there will always be a few that I might, if with care that they wouldn't get clobbered in a minor update, and/or that I'd keep a list and check after same); it's that there's no gathered documentation to suggest how to supplement those in protected directories _transparently_. > >> ). But that's obviously not the desirable answer. (I'm curious if I can >> put them back with csrutil disable in effect, and then re-enable it, and see >> whether it clobbers them again or leaves them in place; but for now, I'm >> just annoyed with the interference, since I've tweaked Unix distros and >> administered many flavors of Unix systems since before there was an OS X, >> and have little patience with Orwellian approaches to locking something >> down, i.e. those I have to fight with to get around, even with >> administrative privileges.) >> >> So what (if anything) can/should be done so that the X server can once again >> use those fonts? > > You don't need to do anything. Then I must have already done something wrong, because the files aren't being re-created.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. X11-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/x11-users/archive%40mail-archive.com This email sent to [email protected]
