Attachment 302353 Details for Bug 442365 – Saved crash log from anaconda

Saved crash log from anaconda

InstallError.txt (text/plain), 1.28 MB, created by Sebastian Vahl on 2008-04-14 15:42:44 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Sebastian Vahl

Created: 2008-04-14 15:42:44 UTC

Size: 1.28 MB

patch

obsolete

>anaconda None exception report
>Traceback (most recent call first):
>  File "/usr/lib/anaconda/livecd.py", line 188, in doInstall
>    buf = os.read(osfd, readamt)
>  File "/usr/lib/anaconda/backend.py", line 215, in doInstall
>    return anaconda.backend.doInstall(anaconda)
>  File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep
>    rc = stepFunc(self.anaconda)
>  File "/usr/lib/anaconda/dispatch.py", line 131, in gotoNext
>    self.moveStep()
>  File "/usr/lib/anaconda/gui.py", line 1259, in nextClicked
>    self.anaconda.dispatch.gotoNext()
>  File "/usr/lib/anaconda/iw/progress_gui.py", line 80, in renderCallback
>    self.intf.icw.nextClicked()
>  File "/usr/lib/anaconda/gui.py", line 1280, in handleRenderCallback
>    self.currentWindow.renderCallback()
>OSError: [Errno 5] Input/output error
>
>Local variables in innermost frame:
>roottype: ext3
>self: <livecd.LiveCDCopyBackend instance at 0xa11c0cc>
>rootfd: 11
>written: 1310720
>r: fsentry -- device: sdb1   mountpoint: /
>  fsystem: ext3 format: True
>  ismounted: 0  options: 'defaults'
>  label: / fsprofile: None
>
>osfd: 8
>readamt: 8388608
>anaconda: <__main__.Anaconda instance at 0xb7c37d0c>
>progress: <InstallProgressWindow.InstallProgressWindow instance at 0xa9ead4c>
>copied: 873725952
>rootfs: /dev/sdb1
>buf: uÐÇ(ÿÿÿµøþÿÿ½øþÿÿ¹µ4ÿÿÿÇ4ó¦ÿøþÿÿ@ 0ÿÿÿEÌÀÇ,ÿÿÿ}óøþÿÿEÈÿÿÿÇE¸R Dÿÿÿ ÿÿÿyÿu¸1ÿE°U¤µÿÿÿÿÿÿôþÿÿët&ø¥µÿÿÿÇ;~ÅÿÿÿµÿÿÿÿÿÿA  ÿÿÿ¸t$ÇD$T$E°Dÿÿÿ$D$èæôÿÀÜþÿÿuE¸0öuHÉä ÿÿÿÇD$D$$èfôôÿÀ"ÜþÿÿÒuÜþÿÿEÌÀtµ0ÿÿÿÇD$D$4$è-ôôÿÜþÿÿÉiüÿÿvÿÿÿÿÿÿÿÿÿ9B,LûÿÿÜþÿÿÀlüÿÿé7üÿÿXÿÿÿÇÀø rñET$ÿÿÿÇD$ÿÿÿÇD$hÿÿÿEÇD$ÇXÿÿÿ	lÿÿÿEpÿÿÿE tÿÿÿB$D$èãôÿÀÜþÿÿ®ûÿÿµÿÿÿÇFéÖúÿÿ¶ÇÜþÿÿé!ÿÿÿÜþÿÿÀàþÿÿµÿÿÿÇ;~;þÿÿÇEÈ1ÿ(ÿÿÿÀ6½Üþÿÿ}ÇEÐt6}t0µÿÿÿFD$ÿÿÿ$èñíôÿF ÿÿÿD$$èÜíôÿ½ÜþÿÿµÜþÿÿöeûÿÿéNþÿÿE°µôþÿÿøþÿÿÇD$D$Dÿÿÿt$$D$è¾ôÿÜþÿÿE¸éÝýÿÿøþÿÿEÌUÈµÿÿÿI HÿÿÿLÿÿÿÇE¼<ÿÿÿÇE´Ç8ÿÿÿÇPÿÿÿÇÜþÿÿFÀE´ðþÿÿë/´&½,ÿÿÿÿÿÿ8ÿÿÿ8ÿÿÿ;B½,ÿÿÿÿÿÿ8ÿÿÿµ8ÿÿÿB ÁæÀE¬t¶ðþÿÿLÿÿÿ<ÿÿÿÇD$D$E¬T$D$$èqãôÿÀt!øhÇPÿÿÿ½,ÿÿÿéiÿÿÿv}tU´ÀuBÀj½LÿÿÿÿÌ}Æu¼öÒE¼U´, ,ÿþÿÿT$$è(ÈôÿÇE´ÀPÿÿÿçþÿÿE¼$èßôÿ½,ÿÿÿÇE¼´&E´Àt4<ÿÿÿÇD$D$$èðôÿÀÜþÿÿtPÿÿÿ½,ÿÿÿÉtµPÿÿÿ½,ÿÿÿµÜþÿÿE¼À$èÞôÿÀÜþÿÿÒuÜþÿÿ½ÜþÿÿÿÿÞûÿÿEÈÀÓûÿÿ$èy¿ôÿÀÜþÿÿ½ûÿÿ}ÇEÈÇ$ÿÿÿéøÿÿÿÿÿMÈUÈÒ@ÿÿÿ3ùÿÿÿÿÿ@ÿÿÿé"ùÿÿÿÿÿ½,ÿÿÿA ÇPÿÿÿÇ0Ò¶ýÿÿµ<ÿÿÿÇD$T$4$èïôÿÇE´ÀPÿÿÿýÿÿé´þÿÿt&}Ð¹µ4ÿÿÿÇ4ó¦t\vEÄÿÿÿD$4ÿÿÿÇD$D$p$èûôÿÀÜþÿÿ½ÜþÿÿNÿÿ¹ÜþÿÿÀ¬øÿÿUÐöx@øþÿÿÇ(ÿÿÿé5ùÿÿfÜþÿÿÀþÿÿUÈÒá}ÇD$$è9ÃôÿÇEÈÜþÿÿÜþÿÿÀm÷ÿÿEÈÀt$èÏ½ôÿÀÇz½ÜþÿÿéGûÿÿ¶µ,ÿÿÿu°u¸t&E°À²9E¬<ÿÿÿE°t$ÇD$ÇD$D$$èàôÿÀPÿÿÿu-U¸<ÿÿÿBÇD$T$$E°èÚíôÿÀPÿÿÿt½,ÿÿÿéýÿÿEÈÀt
>}Qøÿÿ1À0ÿÿÿ}UÌT$ÿÿÿÀÀD$EÀÇEÀT$D$$èxßôÿÀÜþÿÿùÿÿEÌuÐ@µøþÿÿ,ÿÿÿé÷÷ÿÿE´µxÿÿÿÇÇ@1ÀÇÀørñøþÿÿU´x¸@xÿÿÿöÅuáùÀàúÀ |ÿÿÿHÿÿÿBt$µLÿÿÿÇD$L$D$ BÇD$L$t$D$øþÿÿ$èþêôÿÀPÿÿÿÐþÿÿ½,ÿÿÿU´éîüÿÿEÄÇD$üþÿÿµ@ÿÿÿ@L$t$D$ÿÿÿ$è·ôÿÜþÿÿ½ÜþÿÿNÿÿGýÿÿÇ(ÿÿÿé»ýÿÿLÿÿÿE¼øþÿÿÇD$D$T$$èòßôÿÀPÿÿÿùúÿÿé/þÿÿvPÿÿÿ½,ÿÿÿé7ûÿÿÜþÿÿÀxýÿÿ(ÿÿÿÀÊøÿÿÿÿÿEÐÇD$L$$èËôÿÀÜþÿÿøÿÿÿøÿÿéøÿÿÇÜþÿÿéKôÿÿ}¬ÿ¶tRE´µ,ÿÿÿøþÿÿxÇ@pfÇ@Æ@fPE´Æ@U´ÇPÿÿÿÇÇBéûÿÿÇPÿÿÿéyþÿÿt&ÿÿÿp`LûÇD$$è¿ôÿµÿÿÿÇEÈÜþÿÿpHLéFüÿÿUÌ,ÿÿÿ9BuÿÿÿpÀtö@Lu4ÿÿÿÀtµÿÿÿöu#µþÿD$ÿÿÿ$èÓôÿUÌT$0ÿÿÿÇD$$è\êôÿÀÜþÿÿöÿÿEÐÇEÌ$èL¶ôÿÀÂÿÿÿEÌµ0ÿÿÿD$EÀÇEÀÇD$L$D$4$èýÛôÿÀÜþÿÿ¡õÿÿEÌ,ÿÿÿPÇD$D$4$èÏéôÿÀÜþÿÿsõÿÿÇEÌé7ûÿÿÇ(ÿÿÿé(ûÿÿEÐµÿÿÿèþÿÿ@(T$L$4$D$èpêôÿäþÿÿàþÿÿD$EÐT$@(4$D$>µþÿD$èðÑôÿéÍúÿÿT$0ÿÿÿÇD$$è1éôÿÀÜþÿÿbÿÿÿéÐôÿÿfèkUåWVSìlMèvöôÿÃ·±}A1ÀtFpÒt
ö-ûMUfyÇÇBxº@öÄuUE·NUÐòuÐÊFEÈ·T$ú$)ÈD$è	åôÿUMÈf}Îfz·r·	föfMÆt/1Òt&}Ð·ÂG·f9EÆvfEÎfE·pÂf9ÖwØUFÿfB·À1Ò;Et$+EÀD$MuÐDND$}È<$èäôÿ1ÒÄlÐ[^_]Ã¶|Àt@<Àt
öøçþÿÿxº@öÄ®E}ÜBE·UEÀEEØEØT$(ÇD$$D$ |$ED$BT$ÇD$ÇD$D$A4$D$ènëôÿÀÂPÿÿÿMfyuþÿÿf1ÒfÇAfAÄlÐ[^_]ÃàøÒâúÂ é\þÿÿt&àøÒâúÂ é?ÿÿÿt&UåWVSì\}UèCôôÿÃ¯EÌMÌ·Bx¹@öÆuâúÉáúÁ U·À·r6)Ðº)È;EûWÒtMÌApÉt
ö-MÇÇAMÉEÌx¸@öÅuÈàøÀàúÀ }Ç;uöuÐU·Bf+EfBUÐfEº@f@öÅuáùÒâúÂ EEÐMu·ÆA4$T$D$èÎôÿE1ÒÀt EMpA4$T$D$è`Îôÿ1ÒÄ\Ð[^_]ÃU+uMÒ6D$D$DOUÐ$èìáôÿEÌxé:ÿÿÿf|Àt@<Àt
öøÉþÿÿEMD$(EL$$MD$ EL$MD$AT$ÇD$ÇD$D$EÌL$$èþèôÿÀÂFÿÿÿU·résþÿÿt&U1ÀÒtU·BfEðMÔEðÆEòEÔÇEØMéJþÿÿU¹ÿÿÿÿåEE9rÀ¶ÈÈ]ÃfUåWVSì,uèÆñôÿÃ}u#M9ÂtEUèÄ,[^_]ÃÈRúÿD$ÇD$M4$L$è+³ôÿ}1ÉÇEðïÿ~#1Ò1ÉÇEðD+9ÈvUðÁÂ9×éEU|üUEìEäEì+EèEä)ø9Èv9}ìt:6uäEäé\ÿÿÿt&MðUDMèÄ,[^_]ÃUåìuøu]ôèÃðôÿÃ¬}ü}öt!~yÀtD$E$è-ÊôÿÇÿt!yÀtUD$$èÊôÿÇEÀt'ExyÀtD$E$èÝÉôÿUÇ]ôuø}üì]Ãt&¼'Uåì8}ü}]ôèðôÿÃT«uøÿty
WÒtÉt1öð]ôuø}üì]ÃvEðD$EÇEðT$$èçÀôÿÀÆtEðÀtÄD$E$è;ÉôÿÇëÇD$GUÇD$<$D$EðD$ÿR,ÀÆuµEðévÿÿÿUåìuüu]øUèPïôÿÃªöu'}$À÷Ð%D$èR¶ôÿÆð]øuüì]Ã$èü°ôÿÀtèD$E$èÙ¬ôÿ]øÆðuüì]Ãë
UåSìEèØîôÿÃªUÉt"üµþÿD$$èÜÉôÿ¸Ä[]Ãt&Ét&ÇD$D$ÇD$$èfÊôÿÄ[]Ãt&@¶þÿD$$èÉôÿ¸ë¬´&Uåì(uøÖU]ôèAîôÿÃ©}üxEðÇD$ëBt$<$D$è<àôÿÀu4MQâÈú@tCw1Òt=úft6ÇD$t$<$èÏôÿf]ôuø}üì]ÃvútúuÊMÉvtÖMðI$ÉtÌÒuÈ¶þÿD$t$<$è¶Èôÿ¸ë«vUåWVSì,EèvíôÿÃ·¨xEØðÀt
>@@Àu}EØx÷Â|Àt@<ÀtöøtöÆ@tqâv
>}ÇEà´&ø¼¶þÿ¾D$<$èÈôÿÄ,ð[^_]Ãöõ@vÿÿÿ<$èÏôÿÄ,[Æð^_]Ã´&¯¾þÿD$<$èò½ôÿÆöuµ·¼öÊEðÇD$D$<$èg½ôÿÀÆuÇD$UBxD$BD$EØ$è]ÑôÿÀÆEðÀtÇ@UÇD$T$E<$D$è§±ôÿÄ,ð[^_]ÃUUàE<$D$è×ÝôÿÀÆÿÿÿ}àv[¯¾þÿÇD$D$<$è}ÍôÿÆé&ÿÿÿfÇEðéGÿÿÿt&UT$ED$UT$E$ètÈôÿÆéJÿÿÿUàÀþÿØÿàfEØöytU<$T$èAÝôÿÇEÜÀÆiþÿÿÇD$E¿þÿ$EØèØüÿÿÀÆCþÿÿÇD$U$EØÑîýÿè²üÿÿÀÆþÿÿEÜÀtEö@ t@ÀÍt&UÌ@À4þÿÿ}à
*þÿÿ}à þÿÿ}àt&þÿÿì¶þÿ¾D$<$è·Åôÿé«ýÿÿEØ¸xþÿÿ@ÀþÿÿvÇEÜé>ÿÿÿt&UØBønþÿÿøv¾ø`þÿÿUØöz@Pþÿÿ1À}ÀÀEÜÓþÿÿéôþÿÿf½¾þÿÇD$D$<$è²ËôÿÆé[ýÿÿë
Uåì8]ôuøu}ü8EèèËéôÿÃ¥Uä1Ò÷ÆHGEìtUìlÀòæÿÿÿ·Áêâð%0ÇEðt=0æÿÿÿÏÇEðFüøvTUMäEìÇD$T$L$$è×®ôÿUìÅ¾þÿÇD$D$$èÚÊôÿÂ]ôÐuø}üì]Ãt&lÀþÿØÿàt&x©u©tözuÿÿÿMä¿þÿøÇD$$èeúÿÿÀÂuEÑîýÿÇD$$øèDúÿÿÀÂnÿÿÿMðÉMèÌ@Àu-þþýþfòþ´&âæ@t&ÿÿÿUèÇD$BxD$B<$D$è-ÍôÿÂéîþÿÿf¢þÿÿUMìT$$èØÙôÿÀþÿÿEäUìD$$è¾ÙôÿÀúþÿÿéiþÿÿt&Ò¶u~fNþÿÿféÓþÿÿvöz6þÿÿMäEìL$$èlÙôÿÀ¨þÿÿéþÿÿvEðÀvþÿÿÅ¾þÿD$EìÇD$$èÉôÿÂé"þÿÿ¶Mì,·þÿD$$èOÂôÿºéýýÿÿÅ¾þÿ$D$èrÜôÿÂéãýÿÿ´&MAöÄu%t·þÿD$Eì$èÂôÿºé²ýÿÿ¶MäA¨ uOMA=ÿv;r©ÿ#þÿÿì·þÿD$ ¸þÿD$þÿD$Eì$è¥ÁôÿºéSýÿÿ°·þÿë´&ì¶þÿénÿÿÿt&Uåì8E]ôuø}ü8è>æôÿÃ¡WðUÜÀt@@Àt
öõ@ªö{P¸þÿoU¸þÿâÿÿÿþ÷E0UàPE%ÿÿÿ¾øqèøUÜÓ¾þÿÇD$D$$èTÇôÿÀÆUàET$U$EèûÿÿÀÆøUÜ¼À«EðD$EÜÇD$$è=¶ôÿÀÆÃUàET$UD$ET$UD$$èlÂôÿÀÆuBUÜ|Àt5@<Àt.öùt%öôt÷EuÇD$$è'ÉôÿÆEðÀtÇ@EUD$ET$UÜD$$è6ªôÿë$}àÿÿÿ¹þÿD$EÜ¾$è ¿ôÿð]ôuø}üì]Ãt&$è¤ÆôÿÆëàt&ø
>t&u&EÀtVUEÜT$$èÖôÿÀÆtë°t&EÀvzÿÿÿUøÇD$$¿þÿè§õÿÿÀÆ_þÿÿétÿÿÿöEàô¾þÿuâ¾þÿD$Ð¸þÿ¾D$EÜ$èä¾ôÿé?ÿÿÿvÇEðémþÿÿt&UåWVSì,EèãôÿÃ×pðÀt@@Àt
öõ@EÀâ¼ÇEàÀEðÇD$D$4$è*´ôÿÀ |Àð@<ÀåøÀ×ÇD$¿ÇD$ÇD$E$èÝôÿÀ´&ED$E$è¢¬ôÿÀtMàÉÿt&UðEàÒt
>EàÇBÄ,[^_]Ã¶}ÿÿÿ¿þÿÇD$D$4$èÄôÿEà¼ÀþþÿÿÇEðéÿÿÿ´&}àÿtY1ÿ¶éSÿÿÿvÿEàsÿÿÿ4$èQÃôÿÀcÿÿÿUàÒXÿÿÿEà´&éIÿÿÿv4$è$ÄôÿÄ,[^_]ÃEà1ÿéþþÿÿ¶Uåì8U]ôuø}üè®áôÿÃïxðÀt@@Àt
öõ@åEU%ÿÿÿþEàD$E$Uè}÷ÿÿÀÆ§¼À½EðÇD$D$<$è*²ôÿÀÆu|EàUD$ET$UD$$è$¯ôÿÀÆu*|Àt @<Àtöùtöôug´&EðÀtÇ@EUÇD$<$D$T$èH¦ôÿð]ôuø}üì]Ãt&<$èÜÂôÿÆëàt&ÇEðéSÿÿÿv÷EuÇD$<$èºÄôÿÆëv¼'Uåì(}ü}]ôuøuè=àôÿÃ~PðÀt@@Àt
öõ@öt&þvt¿þÿÇD$D$$è ÁôÿëLf¼ÉtNEðÇD$D$$è»°ôÿÀu%Et$<$D$èËôÿUðÒÁt	ÇBÈ]ôuø}üì]ÃÇEðëÄ´&$è¼ÁôÿëØ´&¼'Uåì8E]ôuø}ü8èNßôÿÃwðÀt
>@@ÀuRx÷Âu|ÀtR@<ÀtKöøtBæ@u=$¿þÿD$4$èG°ôÿÀtg]ôuø}üì]Ãföõ@u¥4$èÁôÿëÞt&EÀvt&}ft$¿þÿÇD$D$4$èPÀôÿë§fUÌ@Àtx¼Àt^EðÇD$D$4$è[¯ôÿÀpÿÿÿUÇD$BxD$B<$D$èRÃôÿÀtJUðÒ@ÿÿÿÇBé4ÿÿÿvÇEðë·¶ì¶þÿD$4$è"¹ôÿ¸éÿÿÿt&EUD$$è"Âôÿë¢t&UåVSì uèÇÝôÿÃPðÀt
>@@ÀuiEÀÌHÉti¼À£EôÇD$D$$è`®ôÿÀuWE4$D$èý¢ôÿUôÒÁt?ÇBÈÄ [^]Ãöõ@u$ès¿ôÿÄ [^]Ãì¶þÿD$$è:¸ôÿ¸Ä [^]Ãf2¿þÿÇD$D$$è¢¾ôÿÄ [^]Ã´&ÇEôélÿÿÿ¶¿Uåì(}ü}]ôuøè°ÜôÿÃñpðÀt
>@@Àub¼ÀtpEðÇD$D$4$èeôÿÀu,ö,t\GÀtu<$è½ôÿÇUðøÒt	ÇBø]ôuø}üì]Ãt&öõ@u4$èc¾ôÿëÜt&ö,ÇEðu¤B¿þÿ¿D$4$è·ôÿë´&|Àt@<ÀvÿÿÿøÀhÿÿÿ<$è¼ôÿ4$Çèç¸ôÿÀXÿÿÿÿPÿÿÿÇéHÿÿÿvUåì8E]ôuø}üpè}ÛôÿÃ¾ðÀt@@ÀEf¸x}ÿ¬¼ÉEðÇD$D$4$è¬ôÿÀu>|Àt@<ÀtøÒE$èôÿÇUðøÒt	ÇBø]ôuø}üì]Ãöõ@cÿÿÿ4$èÿ¼ôÿëÜ`¿þÿÇD$D$4$è2Öôÿë¿t&`¿þÿÇD$D$4$è2¼ôÿët&EÇD$ÇD$ÇD$$èyÔôÿÀÇ\ÿÿÿE$èÔôÿ4$Çèz»ôÿÀ?ÿÿÿÿ7ÿÿÿÇt&é,ÿÿÿvÇEðéðþÿÿvUåìhE]ôuø}üpèíÙôÿÃ.ðÀt
>@PÒudUxfÀz÷Eÿ?ÿÿ©u|ÒtLR<ÒtEöøt<öÄ@u7i¿þÿD$4$èÑªôÿÇéJ¶öõ@u4$è£»ôÿÇé,EÀt}4$|$è&ËôÿÀÇEÀtE4$D$èËôÿÀÇì¼ÀEðÇD$D$4$èç©ôÿÀÇ½|Àt@<ÀtøÀÒÇEÀ}ÿ}UBøñøöèíEÇD$$è(®ôÿÇEÀÀEðÀtÇ@UEÇD$4$T$D$èßôÿëi¿þÿÇD$D$4$èÂÓôÿÇø]ôuø}üì]Ãt&i¿þÿÇD$D$4$è²¹ôÿÇëÎfUÇD$ÇD$ÇD$$èùÑôÿÇEÀÀ/ÿÿÿÇEÀé÷þÿÿf÷E@ÿÿÿE U|$}D$ET$U|$}D$T$<$è,ÊôÿÇéïþÿÿÇEðé{þÿÿt&4$t&è¸ôÿÀÓþÿÿÿËþÿÿÇéÄþÿÿEUÌ¹	×ó«×émþÿÿ¶¼'UåìHE]ôuø}üxèýÖôÿÃ>ðÀt@@Àt
öõ@/ExfÒ}E%ÿÿÿý÷ÂEàu/|À@<ÀöøtöÆ@k{²þÿD$<$èÅ§ôÿÆö;¼ÀÙEðÇD$D$<$è6§ôÿÀÆ|À@<ÀøÀ1À}ÇD$ÇD$ÀD$E$è
ÐôÿÇEÔÀÆudEÀéÇEØEÇD$ÇD$D$E$è¼ºôÿÀÆEØÀMÔÉt<$èÈ¶ôÿÀ4t&EðÀtÇ@UEÇD$<$T$D$èàôÿëf{²þÿÇD$D$<$èÂÐôÿÆð]ôuø}üì]Ãt&÷ÂuH}àf¶uàöt&{²þÿÇD$D$<$è¶ôÿÆéZþÿÿ8¹þÿ¾D$<$èÕ¯ôÿë´&<$èä¶ôÿÆ¶égÿÿÿvÇEÔé§þÿÿvÇEðé;þÿÿv}àt&2}à¶hÿÿÿfÇEÜEÜUD$E$¿þÿèÖåÿÿÀÆøþÿÿEÑîýÿÇD$$Eè°åÿÿÀÆÒþÿÿUÜÒEö@ UöB tE¸x§UöB}àtE<$D$èÅôÿÀÆuþÿÿU<$T$èvÅôÿÀÆ\þÿÿéýÿÿvEt$ÇD$<$D$è¿ôÿÀÊýÿÿöÂýÿÿÆvé¸ýÿÿvö¶ÂýÿÿÆé»ýÿÿvæt&Òþÿÿfé1þÿÿvEUàD$ET$UD$ET$$èeÄôÿÆéLýÿÿfUö{ýÿÿEÇD$D$ÇD$<$è®ôÿÇEØÀÆÞüÿÿéýÿÿvUBèø¤ýÿÿMÇEÜÉ3þÿÿéSþÿÿ´&EÀþÿÿUöB ¶lþÿÿBÀaþÿÿ½¾þÿÇD$D$<$èá³ôÿÆé·ûÿÿ`¹þÿ¾D$<$è3ôÿéÞüÿÿfUåì8uøu]ô}üEè@èêÑôÿÃ+Uä1Ò÷ÆLEìtQUìlÀÄu¿þÿD$EìÇD$ÇD$t$$èß·ôÿÀÇuD1Ò÷ÆÂæÿÿÿ³÷Æ0ÇEðu5þvNÇD$u¿þÿD$Eì$è³ôÿÇø]ôuø}üì]Ãf÷Æ u(ðæÿÿÿïÁèàþEðw²³ÐÀþÿØÿà´&ÇD$ë¶u¿þÿD$$èRÆôÿÇëfUEìT$$èºÂôÿÀÇ{ÿÿÿUäEìT$$èÂôÿÇ1ÀÿUäD$Eè$¿þÿè>âÿÿÀÇ;ÿÿÿEÑîýÿÇD$$EèèâÿÿÀÇÿÿÿEðÀ
>ÿÿÿUBöÄîà¹þÿf¿D$Eì$èW«ôÿéÝþÿÿ¶Ò æ¿þÿt&u}¿þÿUì¿D$¨¹þÿD$$è«ôÿéþÿÿt&Eèöz`þÿÿUäEìT$$è¢ÁôÿÀÇcþÿÿ¸éüþÿÿfUEäÇD$T$UìD$$èôÿé1þÿÿfEðÀeþÿÿUèz¶òýÿÿfëªUäB¨ uRUB=ÿvUè;r©ÿäýÿÿì·þÿ¿D$£¿þÿD$þÿD$Eì$è+ªôÿé±ýÿÿºþÿ¿D$Eì$èªôÿéýÿÿt&¼'UåWVSìLEèÆÎôÿÃxðÀt@@À¼ÀHEðÇD$D$<$èuôÿÀu^EÀtEÀ(D$U<$T$èÄôÿÀÆu&EÀt`EÀ,D$M<$L$èÛÃôÿÀÆtAUððÒt	ÇBðÄL[^_]Ã´&öõ@]ÿÿÿ<$è?°ôÿÄL[^_]ÃvEUÁP0xt|À@<À°øö1À}ÇD$ÇD$ÀD$$è±ÇôÿÇEÐÀÆKÿÿÿ÷EWEÀEÈ)ÉëÇEØUHþÿER%ÿÿÿýEàUÜÇD$¹Á
>D$MÌL$$è;¿ôÿÀÆuQE%@=@Þe!}!8}þE¾D$À¿þÿD$UÜ$èé§ôÿt&EÀ%Mx1ÀöÂÀâ³EÔEöxßEØÀ:EÐÀFþÿÿ<$è³ôÿÀ6þÿÿöt&)þÿÿÆé"þÿÿvEÇEðÀÈýÿÿ¶éÜýÿÿvÇEÐé§þÿÿvÇD$EÌD$UÜ$èºôÿÆö<ÿÿÿÇD$E D$UàT$ML$ED$UT$ED$M$èôÿÀÆõþÿÿÇEÔUÒt
ö
ÿÿÿEx1ÀöÁtEEÀ¶ÀámMÉWÀÕþÿÿÇD$ML$ET$D$U$è©ôÿé«þÿÿöôØýÿÿ÷Et&ÇýÿÿfED$<$èmºôÿÀÆ}þÿÿMÇEØMÈé¡ýÿÿt&UDÁþÿØÿà÷Eà8ºþÿt7D$MÜ¾$èÛ¥ôÿéòýÿÿ¸D$M$èB ôÿÀÆÔýÿÿUÜô©¨pºþÿ¾D$$è¥ôÿé¤ýÿÿ¸ë°¸ë©¸ë¡¶t$MÔL$E<$D$èR¶ôÿÀ¤ýÿÿöýÿÿÆt&éýÿÿÀ}ýÿÿfÇD$ÇD$MT$L$E$è&¨ôÿéPýÿÿt&¨uMÜtÒº}ày}©uvÀºþÿD$EÜ¾$èÀ¤ôÿé×üÿÿ´&pÀö@L¶t~Exé¼üÿÿöôtUÈöüûÿÿ<$èK¯ôÿÆé¾üÿÿöEàt&EÈÀt&ÜUÈöÌ}L »þÿéMÿÿÿt&÷Eà 5üÿÿEx÷Â)üÿÿ »þÿ¾D$<$èâ£ôÿéýÿÿÇD$MÌL$EÜ$èRªôÿÆéüÿÿ}Â÷EàtLMÜlMÈ	Át<ÀÄþÿ¢P»þÿ¾T$D$EÜ$èo£ôÿéûÿÿèºþÿépýÿÿEÀ¶.üÿÿÒu9EÀüÿÿM¡xþýÿÿé
üÿÿºþÿ¾D$$è£ôÿé-ûÿÿEÀtËx»þÿ¾D$UÜ$èð¢ôÿéûÿÿè@þÿéSÿÿÿ1Òfé#ÿÿÿt&¼'UåWVSì,EèÇôÿÃ×xðÀt@@Àö·¼öEðÇD$D$<$èEôÿÀ»|ÀÛ@<ÀÐøÉÂUPÇD$ÇD$ÒÀ¶ÀD$E$èÁôÿÇEàÀÆuFU}rÒ¿þÿ4$ÇD$D$èp¨ôÿÀÆEàÀÏ´&UððÒt	ÇBðÄ,[^_]Ã¶öõ@ýþÿÿ<$è¯¨ôÿÄ,[^_]ÃvU}ÇEàrsÿÿÿEÀ¾UÀ±HEPÒuërfPÒtiÀ;Jvtî ¼þÿD$4$è ¡ôÿEà¾ÀLÿÿÿëfÇEðéþÿÿv<$t&è§ôÿÀ"ÿÿÿöÿÿÿÆéÿÿÿvUT$ED$UT$E$è´ôÿÆEàÀãþÿÿë©ä»þÿD$4$è ôÿémÿÿÿUåì8E]ôuø}üpèMÅôÿÃðÀt@@À¨Ufºx¯¼ÀÁEðÇD$D$4$èîôÿÀu^|Àt@<ÀtøÀ¯ÇEàUEìD$B $èôÿÀÇtuEàÀÂUðøÒt	ÇBø]ôuø}üì]Ãvöõ@Kÿÿÿ4$è·¦ôÿëÙÛ¿þÿÇD$D$4$èê¿ôÿë¼t&ÇEðéNÿÿÿt&EìÀvtv@UétÿÿÿEÇD$ÇD$ÇD$$è)¾ôÿÇEàÀÇ$ÿÿÿéEÿÿÿ´&4$è$¥ôÿÀ¶(ÿÿÿÿ ÿÿÿÇéÿÿÿvEf¿ÇÿÿÿÿX¼þÿD$4$èÅôÿéçþÿÿt&UåWVSì,EèÃôÿÃÇ~xðÀt@@À¾Ef¸x}¼ÀEðÇD$D$<$è$ôÿÀ|Àt@<ÀtøÀiÇEØE%ÿÿÿýEàExP÷Áu|ÀtQ@<ÀtJöøtAå@u<â¿þÿD$$èôÿÆëM¶öõ@5ÿÿÿ<$è×¤ôÿÄ,[^_]ÃvuàöUâ¿þÿÇD$D$$è¤ôÿÆöQMÉÇEÜÇD$ÇD$ED$E$è9§ôÿÀÆ;UÜÒt$ÇD$E<$D$è®ôÿÀåöÝÆvéÓvâ¿þÿ<$ÇD$D$èR½ôÿÄ,[^_]Ã¶ÇEðé|þÿÿt&1À}ÇD$ÇD$ÀD$E$è»ôÿÇEØÀÆeþÿÿ´&EðÀtÇ@ÇD$ÇD$E<$D$èÇôÿÄ,ð[^_]ÃE$D$èý²ôÿÀÆ¶þÿÿ´&EØÀt¡<$è=¢ôÿÀtövuÆt&ë¶EàD$ED$ED$E$è´µôÿÆéþÿÿEö{ZþÿÿEÇD$D$ÇD$<$èmôÿÇEÜÀÆ1þÿÿékÿÿÿt&¼'UåWVSì<}èVÀôÿÃ{GEàG @@TÀtEÀUEðD$ÇD$ÇD$ÇD$GT$<$D$èrôÿÀÆ³Eàöôtv¶}¹ÿtÿtE¹Àt¹UðL$ÇD$´D$B|D$BxUàD$$èºôÿÀÆøÿÿt&úEð÷Eª,÷Etw,@U1öÄ<ð[^_]Ã´&÷EuEà1Òö÷ åþÿÿUàEÇD$D$ÇD$$è×ôÿÀÆu¬Ué«þÿÿvUÒtöuÿÿÿt&ésÿÿÿvUÒvRÿÿÿövBÿÿÿfé1ÿÿÿvEð$èIôÿt&é:ÿÿÿvEð,é÷þÿÿ¶Eð,éßþÿÿ¶Uåì8}ü}]ôè3¾ôÿÃtyuø÷Ç¯çÿÿÿ÷¸D$EðD$ED$E$è[¤ôÿÀÆuqEUðMèBEBE¸ÉBÿupÏE$|$D$ED$ED$èðôÿÆEð$èSôÿÀtöuÆt&ð]ôuø}üì]Ã1À÷ÇNÿÿÿçÿÿÿû¸é>ÿÿÿfÿ@uë¶B<Bféoÿÿÿt&¼'UåìHE]ôuø}üxè
½ôÿÃNxðÀt@@Àt
öõ@UxfÀyQ©uj¼þÿ¾D$<$èßôÿEU<$D$ET$D$è2ôÿð]ôuø}üì]Ã´&ê¿þÿÇD$D$<$è¸ôÿÆëÌfE%ÿÿÿþ÷E0EàPUâÿÿÿ²ÐèøUÜnê¿þÿÇD$D$<$èÐôÿÀÆWÿÿÿEàUD$E$UèòéÿÿÀÆ5ÿÿÿ¼ÀâEðÇD$D$<$è¿ôÿÀÆ#ÿÿÿ|Àt@<ÀtøÀ:ÇEØEàUD$ET$UD$ET$UD$$è±ôÿÀÆu?|Àt5@<Àt.öùt%öôt÷EuÇD$<$èôÿÆEØÀõEðÀWþÿÿÇ@éKþÿÿ¶¸þÿ¾D$<$è
ôÿé)þÿÿt&<$èôÿÆ¶é-þÿÿvEÀt&E¿þÿÇD$$EèMÌÿÿÀÆàýÿÿ}ÜþÿÿEÀU<$T$è[¬ôÿÀÆ[þÿÿéýÿÿ1ÀU}ÇD$ÇD$ÀD$$èd´ôÿÇEØÀÆþÿÿé
ÿÿÿf<$èdôÿÀ¶õþÿÿöíþÿÿÆéæþÿÿvÇEðé2þÿÿ¹þÿ¾D$<$èôÿéýÿÿë
Uåì8E]ôuø}üxè¹ôÿÃîtðÀt@@ÀUfºxEÀ,·¼öEìÇD$D$<$èCôÿÀÏ|Àt@<ÀtøÉÇEàUEÇD$ÇD$T$$èôÿÀÆu9UBø2røt&ÂD$ó¿þÿD$<$è8ôÿÆfUàÒÍ<$èñôÿÀ½öv²Æé«vöõ@òþÿÿ<$è¾ôÿf]ôuø}üì]Ãvó¿þÿÇD$D$<$èâ³ôÿëÔt&ó¿þÿÇD$D$<$èâôÿë´t&1À}ÇD$ÇD$ÀD$E$è$²ôÿÇEàÀÆÎþÿÿ´&UìðÒcÿÿÿÇBðéUÿÿÿt&ÇEìéuþÿÿt&E<$D$è©ôÿÀÆßþÿÿEðUD$EÇD$T$$èâôÿÀÆ´þÿÿEUÇD$D$EðT$$èwvôÿÆEð$è
>ôÿÀtöuÆUÇD$ÇD$<$T$è±|ôÿéXþÿÿEÇD$$è©ôÿÆé>þÿÿ¶Uåì8}ü}]ôèã¶ôÿÃ$ruø÷Ç¯çÿÿÿ÷¸D$EðD$ED$E$èôÿÀÆuqEUðèBE,BE¸÷Çÿÿÿ¯BuÏE|$$D$ED$èdôÿÆEðÀt$èôÿÀtöuÆt&ð]ôuø}üì]Ã÷Çtçÿÿÿû¸éDÿÿÿø%ÿèøÀàé-ÿÿÿö¼'UåìHE]ôuø}üxèÍµôÿÃqðÀt@HÉt
öõ@¯Ef¸xnEU%ÿÿÿýEÜE%ÿÿÿüEàD$E$EècãÿÿÀÆU¼ÒkEðÇD$D$<$è0ôÿÀÆ&|ÀL@<ÀAøÀ31À}ÇD$ÇD$ÀD$E$è¯ôÿÇEÔÀÆu~÷Eàu¶EàèøÍEàÇEØ%@øÀàD$EÇD$D$E$èôÿÀÆEØÀ«EÔÀt<$è¨ôÿÀÌt&EðÀtÇ@EÇD$<$D$ED$èÀyôÿëfu¿þÿÇD$D$<$è¢¯ôÿÆð]ôuø}üì]Ãt&<$è4ôÿÆëàt&ÇEðé©þÿÿvÇEÔéõþÿÿvEt$ÇD$<$D$èÑôÿÀ2ÿÿÿö*ÿÿÿÆvé ÿÿÿvö¶*ÿÿÿÆé#ÿÿÿvEàD$ED$ED$ED$E$èE¤ôÿÀÆÉþÿÿ|À»þÿÿ@<À°þÿÿöù£þÿÿöôþÿÿ÷EÜþÿÿÇD$<$èKôÿÆérþÿÿEÀtÇEØ1Àé5þÿÿEö{tæEÇD$D$ÇD$<$èôÿÀÆ3þÿÿÇEØ1ÀéòýÿÿUåì8E]ôuø}üxè}²ôÿÃ¾mðÀt@@ÀèEf¸xï¼ÀEðÇD$D$<$èôÿÀEÀéÆEãE÷EPt²löÖE%ÿÿÿãøUøôÀEÇD$ÇD$D$E$èÆôÿÀÆ }ãt<$èÎôÿUððÒt	ÇBð]ôuø}üì]Ãvöõ@ÿÿÿ<$è§ôÿëÙp²þÿÇD$D$<$èÚ¬ôÿë¼t&EÇEðÀÿÿÿ|À	ÿÿÿ@<ÀþþÿÿøÀðþÿÿ<$è3ôÿÆEãÀÆÞþÿÿéRÿÿÿt&Ex÷Áu/|Àõþÿÿ@<ÀêþÿÿöøÝþÿÿå@Ôþÿÿp²þÿD$$èêôÿÆë^fEx÷Áu×|Àt@<Àtöøtå@t¸öôþÿÿvp²þÿÇD$D$$èêôÿÆöþÿÿéSþÿÿ´&p²þÿD$$èr¥ôÿÆëÖfED$ED$ED$E$èLôÿÀÆDþÿÿé1þÿÿUåWVSì,EèÆ¯ôÿÃkpðÀt@@Àt
öõ@EÀê¼ÇEàÀ
>EðÇD$D$4$èZôÿÀ¨|Àø@<ÀíøÀßÇD$¿ÇD$ÇD$E$è3©ôÿÀ§´&EÇD$D$E$èÊôÿÀtMàÉÿt&UðEàÒt
>EàÇBÄ,[^_]Ã¶}ÿÿÿ¿þÿÇD$D$4$è8ôÿEà¼ÀöþÿÿÇEðé	ÿÿÿ´&}àÿtY1ÿ¶éKÿÿÿvÿEàsÿÿÿ4$èyôÿÀcÿÿÿUàÒXÿÿÿEà´&éIÿÿÿv4$èLôÿÄ,[^_]ÃEà1ÿéöþÿÿ´&¼'UåìHE]ôuø}üxèÍôÿÃiðÀt@@Àà¼ÀBEðÇD$D$<$è~ôÿÀ|À½@<À²øÀ¤1ÀU}ÇD$ÇD$ÀD$$èX§ôÿÇEØÀÆu1uèÀtvf´¼þÿ¾D$<$è%ôÿEØÀ¦UððÒt	ÇBð]ôuø}üì]Ã´&öõ@ÿÿÿ<$èÿôÿëÕuÇEØèÀuðÀuuExP÷ÁtXø¼þÿ¾D$$èôÿéfÿÿÿ´&ÇEðéÑþÿÿt&<$t&èôÿÀDÿÿÿö<ÿÿÿÆé5ÿÿÿux©t,½þÿ¾D$$è(ôÿéþþÿÿÀyd½þÿ¾D$$èôÿéÞþÿÿ©@t½þÿ¾D$$èåôÿé»þÿÿuv9òuÔtöôröôeuv$ösuv$ösuöEÇD$@$%ÿÿÿýEàD$ÀþÿD$èiôÿÀÆ:þÿÿEÀ»ÇEÜuEÇD$ÇD$4$D$èôÿÀÆtTUÜÒõýÿÿEt$ÇD$<$D$èÿôÿÀÒýÿÿöÊýÿÿÆéÂýÿÿv$t&è§¦ôÿÀÆu¬UàÀuàEuàT$UD$Et$$D$èhôÿÆétÿÿÿUö{5ÿÿÿEÇD$D$ÇD$<$è*ôÿÇEÜÀÆÿÿÿé/ýÿÿà½þÿ¾D$$è=ôÿéýÿÿuv$öþÿÿ$¾þÿ¾D$$èôÿééüÿÿ©tát&dþÿÿh¾þÿ¾D$$èßôÿéµüÿÿ´&¼'UåìH]ôè©ôÿÃÚduøu}ü}ÇD$LÀþÿ|$D$F$èôÿÀt]ôuø}üì]Ã¶UØÇÀørñEÇEäÇEð |$D$ET$4$D$ÿLë¬UåSèþ¨ôÿÃ?dì\ÁþÿD$E@$èôÿÄ¸ÿÿ[]Ãt&¼'UåSìEè¸¨ôÿÃùcPðÀt@@Àt	öõ@tÄ¸[]Ã¶$è¼ôÿÄ[]Ãv¼'UåSìEèX¨ôÿÃcPðÀt@HÉt	öõ@tÄ¸[]Ã¶$è\ôÿÄ[]Ãv¼'UåWVSìUEèó§ôÿÃ4c2ÌN$~EèÉ}ìkEPÒL@BuÉF_UìðÀt@pöó}è1öÇEðLÿtJUè<µB°Àt$è(ôÿÀtEðUèB8Àt$èôÿÀtEð}èÆ9wLw¶UèD$uì4$èÆôÿ}èG4$D$è´ôÿG4$D$è¥ôÿG4$D$èôÿG4$D$èôÿG0ÀtD$4$èdôÿEèD$Uì$èbôÿut$}ì<$èPôÿEðÄ[^_]ÃEìöõ@ýþÿÿ$èÌôÿEðEðÄ[^_]Ãf}Gôé©þÿÿL$<$è¿eôÿÀuN$é}þÿÿL$}ì<$èôÿÀþÿÿÇEðÿÿë´&UåWVSì<Eè¦ôÿÃWaÇEðÇEìxEðD$ÇD$0ÇD$<$èõôÿÀÆUìÒtwBÀtD$<$èaôÿUìBÀt#Àt$èiôÿUìB<$D$è7ôÿUìBÀtD$<$è!ôÿUìÀtD$<$èôÿUìT$<$èýôÿEðÀtD$<$èêôÿÄ<ð[^_]Ãt&EìD$ÇD$TÇD$<$è-ôÿÀÆ8ÿÿÿEìÇD$<$ÀD$èôÿÀÆÿÿÿEìUÇEÜÇEàH,HH@PUÇ@2ötÂ
>PÉuô+UÁúUÜÂUàMàÇ@Ç@Ç@ÇÀD$ÇD$L$<$èxôÿÀÆþÿÿEìÇD$<$ÀD$EàD$èMôÿÀÆXþÿÿEìUàÇD$<$ÀD$T$è"ôÿÀÆ-þÿÿEìMàÇD$<$D$L$èú~ôÿÀÆþÿÿEÀEØtMÇEÌUìMÌEØR
>UìBÇBÇÆ0EÆµMÌ°ÀEØuºUìMÜöEJLðÇD$BD$B$è(ôÿÀÆsýÿÿUð¢úÿMôÐXúÿüØ8¤úÿàøúÿìEì
>HMÌ@BEEH$Éu}EÇBôBEôEðUÀÉôYýÿÿL$<$è×ôÿÀEýÿÿ¾ÿÿé;ýÿÿÈ£úÿD$ÇD$L$B$èdôÿUìéçþÿÿL$<$è¯aôÿÀu¼EUðH$éeÿÿÿUåì8E]ôuø}ü8è¢ôÿÃ_]wðÀt@@À¼À¸EðÇD$D$4$èÍrôÿÀu_|Àt{@<ÀttøÀtjE@<$ÇD$ÇD$ÀÀ¶ÀD$è´ôÿÀÇtbfUðøÒt	ÇBø]ôuø}üì]Ãöõ@]ÿÿÿ4$èôÿëÛE$èéôÿÇvë¶¶ÇEðéWÿÿÿt&E$èÁôÿ4$ÇèWôÿÀtÿuÇé{ÿÿÿt&¼'Uåì(E]øuüèã ôÿÃ$\0EôD$E$èlfôÿÀt]ø1Àuüì]ÃEðD$4$èMfôÿÀuáEô+Eð]øuüì]Ã¶¼'UåWVSì¬Eès ôÿÃ´[0VðtÿÿÿÀt@@Àt
öõ@âMáLpÿÿÿu9EÀtRøtMöÁþÿÇD$D$tÿÿÿ$è¹ôÿÄ¬[^_]ÃftÿÿÿlÀ´E%ÿÿÿ³Àu®Eö@ t/ÁþÿD$tÿÿÿ$èÛzôÿÄ¬¸[^_]Ã´&tÿÿÿ¼ÀüEðÇD$D$tÿÿÿ$ècpôÿÀbÿÿÿtÿÿÿ|À@<À¸øÿzM1ÀyÇD$ÇD$ÀD$4$è6ôÿÇxÿÿÿÀÇþUÌ@MEEHE÷ÁýÉy	UÇMAP¨:àþAPAhÿÿÿUÂUM8ÀàõÀpÿÿÿD$ED$hÿÿÿT$A$è~lôÿ=éÿÿÇMÀ-ExLvP¾´&MµÐU°AÒt$èä~ôÿÀÇîUE°BMÆÇ;qLr¼UBHÉ-MÆÇE MU ;QLUE ÁàBÒZEHU E ÁàE¤MM¶UzUÿCÀM´1ÀlÿÿÿlÿÿÿÇÀørëpÿÿÿMÌT$ÈD$hÿÿÿL$E$èEkôÿÀÆoþóÿÿkMU ÆDÿêU¨!EU¤HU À4uOéuvÇD$MIM¤U¤$T$èôÿÀÇEH1VE À0u¤Ö$èU}ôÿÀÇucMU ÆAM¤ÀuEU¤HÇë°$è~ôÿÄ¬[^_]ÃÿUEÀtU1ÿMB0B4AvxÿÿÿÀttÿÿÿ$èT}ôÿÀtÿuÇ¶EðÀtÇ@ÇD$ÇD$UT$tÿÿÿ$èaaôÿÄ¬ø[^_]ÃÇxÿÿÿé³üÿÿþéÿÿuUUhÿÿÿBÀBL$D$E$èhôÿÀÇEU HU¨U¨U é²ýÿÿv,¾öU ÷ÿÿÿME E ;ALÆUM¤Bpö8ýÿÿÈBÒ)ýÿÿÇD$D$E$èÂôÿÀÇýÿÿé·þÿÿ´&E´D$UB$èWtôÿpÿÿÿÈ	D$ML$hÿÿÿD$U$è®hôÿÆélýÿÿvÇEðéûÿÿt&pÿÿÿÈD$ED$UÂhÿÿÿT$MA$è`hôÿÀÇþÿÿE`PþU÷Bw1ÿ}÷ýÿÿMÇE÷AÈM¬uEÇEÀ0E¬UBEJpEìMD$BxÇD$ÇD$D$FL$4$D$è(^ôÿÀÇº÷pÿÿÿ+}ÿtUöUì÷pÿÿÿuMÉtMöt,@BB¸Bpÿÿÿ,%@ÈD$E¬D$M$L$è!gôÿÇEì$èÄyôÿÀ«üÿÿÿtøÇÿóÿÿ¼EHPé°üÿÿEÐ1ÒÇÂúrñEéçùÿÿt&lÿÿÿT$ML$E$ÿ×À¿ýÿÿUT$ML$E¸D$E´L$D$UB$èdôÿÀÆ8ûÿÿE´D$MA$èÞqôÿéòüÿÿt&»àûÿÿé²úÿÿt&öÁþÿD$tÿÿÿ$è|ôÿéøÿÿvMhÿÿÿAÀAT$D$M$èÐ}ôÿÀÇ@ùÿÿUBD$ÌÁþÿD$M$èçrôÿéûÿÿÆéÑùÿÿÇD$ÇD$MAD$T$D$E$è©côÿÀÇPýÿÿUJPéGûÿÿUì,éÝýÿÿÇD$D$UM B$èôÿÀÇ|ùÿÿéûÿÿ¶÷EoøÿÿUB@Àt
öSøÿÿMA$èÔzôÿÀÇ¾úÿÿéúÿÿMA@À.øÿÿÇ|ÿÿÿ¾ëMÇD$Ur$t$èyôÿÀbüÿÿM|ÿÿÿÆAÂÖÁæ|ÿÿÿÀÐ÷ÿÿ$è.wôÿÀÇ8úÿÿEP@Àt2xÿtUB0ÀsÿÿÿMAÇ0ëMÆéèúÿÿU1ÀåºMùv¶ÒÀ9Ñw÷]ÃUåWVìM}ÇEôÉtAuÈÑèÇEô9úuë@ÈuÑèEô9út/9×v	ÀéEôÑéuÞ}ôUôÿuEôÄ^_]Ã´&UÄ^_]Ãt&U¹åEE9wÉÈ]Ã¶Uåìx}ü}]ôuøuèôÿÃ^Pözt~tWGÀt&,¨@uÀx21Ò]ôÐuø}üì]Ã~uät$B$èÏeôÿÂë×´&~uÈfëÜ¶RÇE´ÇE°ÇE¼$ÇEÐMÀVUÄFÇD$ÇD$UäEÈEèEðD$E°D$GxÇEÌMàÇEìD$èàvôÿÀÂtEÐ9Eð:ÿÿÿEÀEÄFEÈFEÌFéÿÿÿ¶UåìÈuøu]ô}üèíôÿÃ.O~Böôhÿÿÿ=lÉ/B }@cÿÿÿ@TÀt
½cÿÿÿ*,öÁûöÅê}t
>öÁâEEàøÀ÷ÐÀ°Eàû}tÿÿÿÿt¿ytÿÿÿÈ%½cÿÿÿdÿÿÿtÀtÇEöÅÇlÿÿÿu ÿÇlÿÿÿtÁèàlÿÿÿEèøJlÿÿÿÀ1ÀÇ|ÿÿÿÆsÿÿÿÆEÁàV|TUÇDT1ÀåuG E}u	½sÿÿÿtG|ÿÿÿ|ÿÿÿ|ÿÿÿÁàÇDDUÁàLTUBABABAEðD$|ÿÿÿUT$\ÿÿÿhÿÿÿD$tÿÿÿD$Fx$D$ètôÿÀÁ|ÿÿÿµ\ÿÿÿÁàD0à9Eðæÿtùíÿÿùîÿÿu)hÿÿÿö÷u±íëv}tBfU1ÉÇ]ôÈuø}üì]Ã¶ÿÎýÿÿöÁýÿÿvëÆ¶hÿÿÿ|ÀÀýÿÿ@<Àµýÿÿöø¨ýÿÿt&ëEUD$F|D$tÿÿÿT$hÿÿÿD$Fx$D$è^ôÿÁéÿÿÿv½|ÿÿÿµ|ÿÿÿD6ýuÁàTDBFBFBFéÜþÿÿféÿÿÿt&ÈtÿÿÿéEýÿÿfE8ªýÿÿÿÝ}ÓöÁ@´&txf»dÿÿÿÀt
Ex¤öz\ýÿÿUzOýÿÿUÇEÇEÇxÿÿÿÇ|ÿÿÿE BE¤BÇE¬ÇEE¨¸lÿÿÿÒuVÁà½xÿÿÿV|TUsÿÿÿ½xÿÿÿÇDTEéýÿÿ1ÀÇxÿÿÿÇ|ÿÿÿë§´&½xÿÿÿP|ÿÿÿsÿÿÿ½xÿÿÿEé¤üÿÿE UE¤BE¨BE¬BécýÿÿUåWVSìLEUèôÿÃTJu@ ÇD$4$EÔh¯úÿD$UØT$èPôÿEEàEØÀüUØRUàÁàLô;UÜtévé;UÜu~êmØUÜuê1öÇEØUÜ9UàuEØUÄLð[^_]Ã¶1ÀuÔ}$ÀD$ÐÀ4$D$ècqôÿÀÆuÉ}ÿtUU+EÜBUÜEë¡fuØvÁàUuð}uÌ1öÂ9×UÐsÿÿÿèEÈë%t&E$Àmÿÿÿþõÿÿaÿÿÿ1öÇ9}ÐvguÔEÌUÇD$4$D$T$|$è6rôÿÀÆu´E$ÀtMMð;Gt;UuÔB4$L$D$èôÿÀÆøþÿÿÇ9}ÐwEEàéÒþÿÿvA;Gu½UÇD$uBUÔt$D$EÌ$D$èQôÿÀÆu3EEÈ9ÇtMðGAu FAégÿÿÿfMðÇAëàUBD$EðD$EÔ$è\ôÿéSþÿÿuàuÜé.þÿÿUåWVSì}uè°ôÿÃñGÇEÜGW öÇEèÇEàEUtMuÇÇEðD$EÇEìÇD$<$D$è³rôÿÀÆtÄð[^_]Ãt&EðUÄÇEäUT$ÇD$ÇD$ÇD$ÇD$$èÀdôÿÀÆMÜÉtEL$$èyôÿUìÒt%Eð@T$UD$$è@~ôÿÀtöuÆfEÄÀu)Eð$èblôÿÀMÿÿÿöEÿÿÿÆt&é:ÿÿÿvMEðL$$è²RôÿÀtÁöu½Æt&ëµ¶EìuD$EðMäÇD$M@4$L$D$è®oôÿÀÆ.ÿÿÿM ÉtrUìM B BÀEäudMÜE ÀtB } }ÿ}àB })ø}G EÀÜþÿÿEÀÑþÿÿE}MÇEÜ9éÎþÿÿUìëfEuÜut$ÇD$$è§jôÿÀÆþÿÿUÜMèÇE MUéuEðÇD$Ut$@$D$ED$è¹nôÿÀÆ9þÿÿEäUèMuB
>FNBEäEð@T$D$E$èw|ôÿÀÆ÷ýÿÿUäEÒtYU u Ò2ÁàEÜ9EdÿÿÿEU D$RUÁàD$$èoôÿÀÆ©ýÿÿE MÜÑè@Eé%ÿÿÿuðMÜ)MÁ}FiU«ªªªÀUà
@¸pûö-î|Àt@<Àt
öøÐRUìÁàE¬E¨D$$ÇEÔÇEØB ÇD$T$ÇD$D$ EÔD$ÇD$T$FM¨<$D$èykôÿÀÆÉüÿÿUìMÜB T$UL$MD$EàÇD$D$T$L$<$è%sôÿÀÆüÿÿEàÀu,UìÇBé]ýÿÿEàEéýÿÿUìÇÇBëMÜUìBé3ýÿÿ¶¿UåWVSìEèôÿÃTC}uÈuÇEðÇEìÇEäPH Et$U¨M¬ÇD$ÇD$ÇD$ÇD$<$èw`ôÿÀÆtmUìÒtM}¬AT$<$D$èzôÿUðÒtM}¬AT$<$D$èñyôÿ}ÈÿtEUD$$èNôÿÄð[^_]Ã´&EðU¬D$ÇD$G$D$EäED$èkôÿÀÆ^ÿÿÿMðAÀf}yMÇé;ÿÿÿA ÇE°ÇEØÇEÜÀEäÇE´E}Pçÿÿÿ}¸ÒÆ@¸pÿ|ö-us|Àt@<Àt	öøuYA }°T$UÇD$D$(E¸|$$L$ÇD$D$ EäL$$D$EØD$èËSôÿÀÆpþÿÿMðë
ÇÇAu°}´q#uìQ}¬VuFL$<$D$èYxôÿÇEðÆEÈÀéöþÿÿE¸èø¢MìyAM¼¹}À}¼Eðó«E¼}MU¼HBöxtJ}ÀM¼¶E¸yAE´À¡}¸ÂUö,²öz£BÀMEìÇD$ÇD$L$@ÇD$$D$è«]ôÿÀtcÆé/ýÿÿt&}EìD$U¬ÇD$ G$D$ED$è1iôÿÀÆöüÿÿEäuìMðA ÇÇFFéþÿÿfEì}éýÿÿvuEäEì}D$ÇD$F|$D$E¬$èÆhôÿÀÆüÿÿuìVFU°EÜUØ¶FÀîÇE´MðéFýÿÿEìMÇ@Ç@Æ@fÇ@fP¶U¸PéþÿÿEUD$$è
>KôÿÀýýÿÿö	üÿÿÆt&éþûÿÿ}MèEàL$D$G ÇEàM $èùWôÿÀþÿÿEàÀ&þÿÿUèüÿÿÿD$B$D$èyrôÿE D$EàèD$G $è½FôÿÀåýÿÿÆé}ûÿÿ¶ÀMD$Fu¨D$A(4$D$ÂþÿD$è!^ôÿ4$ÇD$èÁ@ôÿÆéûÿÿ´&¼'UåWVSì,EèÃôÿÃ>M´ÇEðÇEì8ÇEàÇEèÿÿÿW L$ÇD$ÇD$ÿÿÿÇD$ÇD$$è&[ôÿÀÆtDUÒt-MAT$D$ÿÿÿ$è½tôÿÀt
öu	Æ´&Ä,ð[^_]ÃvUuðt$MèµüþÿÿµÿÿÿÇD$Bÿÿÿ4$L$D$èbfôÿÀÆUðÒt MAT$D$ÿÿÿ$è5tôÿÀuUE´À¢Uì;Uð:ÿÿÿÒ2ÿÿÿMAT$D$ÿÿÿ$èösôÿÀÿÿÿöÿÿÿÆéÿþÿÿvö¶u¡Æt&ë¶EðMäµÿÿÿÿÿÿP @4$L$Hÿÿÿ ÿÿÿEàD$è}UôÿÀÆ+ÿÿÿMäÉüuF;HÿÿÿÚUàÇEÜÒÇ$ÿÿÿÿÿÿD$BÿÿÿD$$è+DôÿÀÆuþÿÿ$ÿÿÿÀEÜMäÈ(ÿÿÿEàÀt*;EÜt%ÁàEä+(ÿÿÿD$(ÿÿÿD$À$èmoôÿE(ÿÿÿ@$ÿÿÿÀi	MEìD$µÿÿÿÇD$$ÿÿÿAt$UèD$ÿÿÿ$èwdôÿÀÆþÿÿEìÇ0ÿÿÿPÿÿÿ ÿÿÿMqö@pÒö-|Àt@<Àt
öøaµ|ÿÿÿ1ÀµÿÿÿÿÿÿÇÀørëxº@MöÄ|ÿÿÿuàøÒâúÂ 0ÿÿÿ1öUÀuµHÿÿÿ9qÀ¶ð¶Aè<
>wB¶À,ÂþÿØÿàÿÿÿMT$$è/FôÿÀAýÿÿö9ýÿÿÆé1ýÿÿÇEHÿÿÿ ÿÿÿD$$ÿÿÿT$ ÿÿÿD$EèT$D$AMt$T$D$A<$D$èÀOôÿÀÆüÿÿf0ÿÿÿÀuHÿÿÿ9VÔUÇD$ÿÿÿBD$B$D$ED$èFvôÿÀÆDüÿÿÿÿÿE
>RÇ@fÇ@ ÿÿÿPHÆ@fPEÆ@$ÿÿÿÀEUð@Béîûÿÿ·AEéäþÿÿ·AfÀ×þÿÿ·ÀB·QEE)Ð ÿÿÿEED$(HÿÿÿT$ ÿÿÿD$$ÿÿÿT$D$EèD$AMt$T$D$A<$D$èvbôÿÀÆ¸þÿÿéOûÿÿvµÿÿÿÇÇFéþÿÿUàÇ(ÿÿÿÇ0ÿÿÿÒtUTü9Ñ(ÿÿÿw7µ(ÿÿÿPÿÐ;tévµ(ÿÿÿè;l(ÿÿÿ;(ÿÿÿvàÇ0ÿÿÿEð@ HÿÿÿUÇD$µÿÿÿüþÿÿBD$B4$L$D$ètôÿÀÆúÿÿEðÇ$ÿÿÿÿÿÿérüÿÿEÜL$D$T$F$èeôÿMÜÉUä$ÿÿÿUàé@ûÿÿuäµ(ÿÿÿé~ûÿÿHÿÿÿÇ(ÿÿÿÇ0ÿÿÿéAÿÿÿEä)(ÿÿÿMàUðEØEÁ½(ÿÿÿuPÿÿÿ(ÿÿÿj LÿÿÿÁP µ4ÿÿÿ@ÿÿÿÇEÌ<ÿÿÿÇEÔ,ÿÿÿMEpöÂ@pÉsö-f|Àt@<Àt
öøHPÿÿÿ+,ÿÿÿµ@ÿÿÿ@ÁàÿÿÿÿÿÿEÌD$L$F$è[ôÿÀÆÏEÌµPÿÿÿ,ÿÿÿ8ÿÿÿÂEØÁæµDÿÿÿ<ð9Ç#EÐÿÿÿëRvEÐµ8ÿÿÿPNVD$<ÿÿÿÇD$$èölôÿÀÆu]DÿÿÿÇEØ9ÇÊ8ÿÿÿu8ÿÿÿÿÿÿL$ÇD$F|$D$<ÿÿÿ$è^ôÿÀÆoÿÿÿEÌÀt@ÿÿÿD$B$ègôÿ4ÿÿÿÀt"M<ÿÿÿA$D$4ÿÿÿD$èKlôÿUÔÒtMAT$D$<ÿÿÿ$è(lôÿÇEUðéÄ÷ÿÿEUä@;mýÿÿUàé¬øÿÿÿÿÿfÇFAÇFF ÿÿÿFÆFfFEÆ@EÿÿÿÇD$D$$è¬kôÿÀÆJ÷ÿÿµÿÿÿHÿÿÿÇEÇD$4$L$è\ôÿÀÆ÷ÿÿUðÇEj é	÷ÿÿLÿÿÿÇÇ@MÔÉtµLÿÿÿFA4ÿÿÿ<ÿÿÿÇD$D$$èkôÿÀÆwþÿÿEØ,ÿÿÿµ<ÿÿÿÇD$4$D$èt[ôÿÀÆtuÇ4ÿÿÿé<þÿÿ9ÐûÿÿÇ0ÿÿÿéûÿÿEPEìPéOöÿÿuEÔD$ÇD$F$D$üÿÿÿEØD$èx\ôÿÀÆÛýÿÿéuüÿÿ,ÿÿÿEØLÿÿÿèÒA ÅÇA,ÿÿÿEØ<ÿÿÿD$T$$è#;ôÿÇ4ÿÿÿÆéýÿÿUÌ`ÿÿÿÿÿÿÇEÄÇEÈdÿÿÿUÔÒ«Lÿÿÿ`ÿÿÿD$$uA T$D$ BL$D$AÇD$L$D$FD$@ÿÿÿ$èÃYôÿÀÆöüÿÿé9þÿÿuUÔFÇBT$D$<ÿÿÿ$è^iôÿÀÆvþÿÿÇEÔéÿÿÿÇ0ÿÿÿé#úÿÿLÿÿÿ`ÿÿÿD$$Mµ@ÿÿÿB ÇD$T$D$ EÄD$BÇD$T$D$A4$D$èYôÿÀÆGüÿÿéýÿÿUåìH}ü}]ôuøè0vôÿÃq1EÜ@ ÇD$EàEðD$GD$ED$Eà$è|ZôÿÀÆ£OÉto@pÒt`ö-uW|Àt@<Àt	öøu=UðÇD$ÿÿÿÿT$BÇD$T$L$D$EÜ$è¨]ôÿÀÆuFUðëUðÇÇBGfjT$D$Eà$èÑgôÿÆð]ôuø}üì]Ãt&GD$EðD$Eà$è£gôÿëÒt&UåWVSì|}èuôÿÃG0P E¼EðE¸EèE°UÀUU´U¸ÇD$T$GUÀD$E´$D$è@YôÿÀÆOUðfzdÇD$GU¸D$GT$D$EÀ$è lôÿÀÆbGÀ@°pöüö-ï|Àt@<Àt
öøÑU¼Mðxº@öÄuàøÒâúÂ U¼EÌ·AÇEèL$$ÇEìEÐE°D$,D$(EÌD$ AD$AD$AÇD$ÇD$L$D$G$D$èiôÿÀÆUðBfÇBT$<$Eè8=ôÿÀÆuMÉþÿÿÄ|ð[^_]ÃUðÇÇBëº¶GT$D$EÀ$è®eôÿE<$D$è¿ZôÿÆë´´&GUÀD$Eð$D$è{eôÿëGD$EðD$EÀ$è`eôÿétÿÿÿë
UåWVSìEè³rôÿÃô-uP E¨xU¬º@öÄuàøÒâúÂ vÇE¼öu´2f)Ñ1ÿfM²·ñE¸MðEÄMEé`|Àt@<Àt
öøE¸ÿÇEäEÄíOUð}M¤MàU U uBVL$,M·u²D$EèD$E¨L$(M ÇEàuÈÇD$L$$MÇD$ÇD$T$L$ M¤$L$ègôÿÀE¼|ÿtEèUìWMðEèUìfÇA·E²QU¨fAxº@öÄuàøÒâúÂ M¸t$$L$èLôÿÿ¢UðM¬BGGBUB|$$D$è~côÿUð)u´×u¸;u´v·U´fU²MuÇD$L$4$èZôÿÀEÀuSFÀt@pÉt
ö-PþÿÿÇEè·u²ÇEìéõþÿÿUðM)u´B×u¶uÀu¼ÿt'UM¬B|$$D$èÉbôÿÀt
>U¼ÒuE¼E¼Ä[^_]ÃuðMàÇE¤Mu é
þÿÿÿtUM¬B|$$D$èwbôÿ}ðë¶UåWVSìLEuMU@èÊoôÿÃ+I UÔEÈFÇEØMÌ¨ tMÇEÔI9ÑMØkÀxöÄ~EUÔ;PMEÔuÉFu
1ÿé+¶UÔÒtìUðMEÜÇEÐUÄMÀvuÄÇD$t$ED$UÀT$MÌ$èSôÿÀEàÏMðEÐ·y·÷ð9EØUxº@öÄuàøÒâúÂ MÐ9MØvEØ)ÈÂøf+EØ<·÷;uÔv·uÔExðT$ÂÇD$t$@+EÔ$D$MÈÿQ,ÀÇ8uÜ)uÔMðAU·qEBL$D$MÌ$èÁ`ôÿEÀuv}àÄLø[^_]Ãu+UØNUÔ9ÑþÿÿMÔéyþÿÿt&¨ut¨@fï} ÿt&tU Àt}9EÔwxu¿éÿÿöt¡UMéNþÿÿt&EÔÀt·ÆEÐévþÿÿ¶t$T$UÜ$èùHôÿé'ÿÿÿML$uÔt$EÈ$è>ôÿÀÇöýÿÿé5ÿÿÿML$uÔt$EÈ$è3SôÿÀÇÿÿÿU M2uéºýÿÿuFD$EðD$EÌ$è_ôÿÄLø[^_]ÃUT$MÔL$uÈ4$è\ôÿÀÇqýÿÿé°þÿÿP¿éÿÿvé þÿÿt&¼'UåWVSì¬EUÇEÌMÇEÐ@ èlôÿÃÛ'ÉEEUÇEBEÜEèpÿÿÿBEèEBEÔEätÿÿÿBUÔEäEÜ,}°1ÀÇÀørñU1À|ÿÿÿ|ÿÿÿÇÀørëEàUD$EÐD$EèÇEÌÇEÐÇEØD$EÜÇEà|$$D$ED$èYôÿÀÆt?EÐÀtUD$B$èGYôÿEÌÀtUD$B$è.YôÿÄ¬ð[^_]ÃEØUD$EÌD$EäT$D$EÔD$|ÿÿÿD$E$èXôÿÀÆu|ÿÿÿE|$T$$ÿUUébÿÿÿ¶9ÐEåEðlÿÿÿEèÀÙEäÀÎlÿÿÿUÇD$D$pÿÿÿT$UD$$èDOôÿÀÆ,ÿÿÿEìtÿÿÿD$EÇD$T$D$E$èOôÿÀÆ{ME9ÁvÁUðUUxöÄÝ¨
EUìÀ E¸ xÿÿÿÉt?µxÿÿÿUÆ¶¶8ÐÁyÿ1ÉëfUÆ¶D
>Á¶8Ð9ÏuãUBxÿÿÿEèBUÇD$EäE$D$èP\ôÿÀÆÛEìUÇD$D$$è,\ôÿÀÆþÿÿEÀþÿÿU)Uéþÿÿ¶EUìÀ@E¸@xÿÿÿé&ÿÿÿt&¶Ò¶À)ÐUéSÿÿÿ¶EUìÀE¸xÿÿÿéîþÿÿt&UéþÿÿEÔ9EÜwPr^U1öÇé|ýÿÿEðUÇD$D$$èp[ôÿé]ýÿÿEìÇD$D$E$èQ[ôÿé>ýÿÿU1öÇé.ýÿÿE1öÇÿÿÿÿéýÿÿUåWVSìlEèhôÿÃ×#@ E´EÀ}Ì1ÀÇÀørñEèuD$EìUD$ME4$ÇEìÇEèD$T$|$L$èpUôÿÀÆu.UE|$$D$ÿUM UEìD$B$èUôÿÄlð[^_]Ã¶uUðM U¬>ÇFE¼¶E¼Àuuö-E 1öÇë±EÀuM 1öÇët&EuM¬D$E´ÇD$t$L$$èìKôÿÀÆfÿÿÿUðM¼·BU°M¸9ÁvE¸uº@xöÄuàøÒâúÂ E¸Àt9U°UÀ¶¶8ÐuwM¸éM¨1ÉëfuÀ¶¶TÁ8ÐuVÇ9M¨uæu°UM´FEBt$$D$èHYôÿÀÆÂþÿÿE ÀµþÿÿU¸)U)U¼é×þÿÿ´&¶Ò¶À)ÐU ë£u Çÿÿÿÿ1öéþÿÿU1Àå]Ãö¼'U1Àå]Ãö¼'UåW1ÿVSìLEðD$Eè=fôÿÃ~!ÇEèÇEðÇEìD$E$è&^ôÿÀÆuPEÀ¡uMðQBÇD$AD$EìD$AD$E$è#ôÿÀÆtm1ÿ=NÿÿtDUèÒtEì@T$<$D$è#XôÿEðÀtD$E$è-SôÿÄLð[^_]Ã´&Mð1ÿQ1öAMAë¥MðéeÿÿÿEìUèUÔx EðT$ÇD$ÇD$ÀD$<$èªIôÿÀtz}}ÆEãÆEâþEðUÔÇD$ÇD$À0T$D$<$èaIôÿÀÕ}âD$Eð@0D$Eì$è&/ôÿÆéïþÿÿvuð~Eè;VEÐUØ_I¹ÿÿÿÿ}Â}ÀÐt	ùÿöÉuÀvGEUØ;,Eì@<$D$EÐD$è¯VôÿÀÆeþÿÿ}ÇEèEã}Eâéÿþÿÿt&MèE190MÐïÇEÜMð;q4ät&âÇEÄ¶Eâ
>EãEàt
>}ÄÿîAUÄøÁÒÂÉìÒä}à"EÜºÀEÏ1ö}ÏtEÀt7}t1}vt(¶Ò¶ðÀ¶t~}àftvEìÇD$UÔ@ÇD$T$<$D$è)[ôÿÀeMèMÐMðuÐAFEÀ¸}®}¤uMÐFAt&EìuÐ@t$<$D$è#UôÿÀÆÙüÿÿMðÇEèyýÿÿEÔÇD$ÇD$<$D$A$D$èßFôÿÀ»}âÌD$Eð@$éyýÿÿf¹é²ýÿÿ¶UÐ1ÉF 9BýÿÿýÿÿëÖ¶D$Eð@¶é2ýÿÿvEÐQ8ÇEÄ9Pþÿÿéþÿÿt&UÐMÇEÜB9AÊýÿÿéÒýÿÿf}ãÛüÿÿMðvéÿÿÿvUèuð
>;N(UÐuÈtujº¶Eâ
>Eãtúÿ¶ÒuÀt&U;
>t&´EìuÐ@t$<$D$èSôÿÀÆcûÿÿÇEèMðéûÿÿEÈ1ÒuÐ@,9FwÿÿÿëfÇEÜÿÿÿÿéýÿÿt&ÇEÄÿÿÿÿéýÿÿu|Àt@<Àt
öøAøÁ1Ò´&øÀ}ÜÆEÏÀt}ÏtEÀt'}vt}ftÉt&ýÿÿféñüÿÿvEìÇD$UÔ@ÇD$T$<$D$è[XôÿÀMèMÐMðuÐA$Fé-ýÿÿuÐ@;FÅûÿÿMÉt}t
>}®ûÿÿEìÇD$@ÇD$<$D$EÔD$èíWôÿÀu-UðMèB0MÐuÐAB$AJB FéYûÿÿt&D$Eè@éÈúÿÿMèMÐé9ûÿÿ}ã*ýÿÿvéSþÿÿEØÀ¶uMÐy´&ÛFuMÐD$4$L$èEôÿÆénùÿÿfQ4A8MÐAé]üÿÿºÿÿÿÿéýÿÿEìÇD$@ÇD$<$D$EÔD$èWôÿÀBÿÿÿUèMUÐuÐAFé{úÿÿöu
UÐzÓýÿÿA4UD$EÐ$D$è©ôÿÆéÒøÿÿMÐB;A=ýÿÿUÒEá}À}áÆuÀ$EìÇD$UÔ@ÇD$T$<$D$èZVôÿÀþÿÿMèMÐMðUÐABðÀu!}áu}tuMÐFAé³üÿÿQ(A,MÐAé üÿÿÉu
EÐx®EÈÀ(éþÿÿEìÇD$@ÇD$<$D$EÔD$èÁUôÿÀýýÿÿuMðUèöA0Eá}UÐBÀÆéSÿÿÿU|Àùÿÿ@<Àùÿÿöøôøÿÿ¶éñýÿÿ}´&èûÿÿféÄþÿÿU|ÀÀûÿÿ@<Àµûÿÿöø¨ûÿÿfé"ÿÿÿt&¼'UåWVSèÜ\ôÿÃìLr EÔEðUÐEÄD$ÐUÀ ÇEðÇEìÇD$ÇD$D$$èAôÿÀts=õÿÿÀMÐuD$A 4$D$èÛ&ôÿÆUìÒtMAT$D$E$èÉNôÿUðÒtMAT$D$E$è©NôÿÄLð[^_]ÃvEÐ@ Àâ}ðUÇEÜ792ÞôÇEàEÐ;pôf¹}Â}ÀÐt	ùÿ*ÉuÀt&J}àÿt&u$uö}}t&zEÐuìuÈt$ÇD$ÀD$EÇD$$èÇ?ôÿÀÆÔþÿÿUÐMäÇD$MÌB$$D$è-DôÿMì1ö|E;0¡±¿Eä9ÆEØpÂº}ó}´&âÿu,EÀÂ}¶²}¶¢Ét#UBL$MD$$èùLôÿÀÆþÿÿUðÇEìÒt#uFT$D$E$èÈLôÿÀÆÕýÿÿÇEð1öéÇýÿÿt&}ðU792}Ü"þÿÿMGÇEà9AþÿÿþÿÿEÐÇEàÿÿÿÿ;pþÿÿUÐ1ÉB9Gþÿÿýýÿÿ¹ÿÿÿÿéøýÿÿt&ö¶@þÿÿUÐÇD$õÿÿMB $D$è	$ôÿÆé)ýÿÿ¶öu
>bEÐuÔ|$À4$D$èuôÿÆéõüÿÿfUÇD$MÄuBÇD$L$4$D$èPQôÿÀìEÜÀðMÐuÜ}ðAFE@GéýÿÿuÇD$UFÇD$$D$EÄD$èðPôÿÀ´MÜÉeUÐMÜuÐB@UðANF
>Bé%ýÿÿ´&QÒyýÿÿ1ÿéýÿÿ¶Eè1Ò9AýÿÿféýÿÿvUA9BtÐt&Oýÿÿ¿ÿÿÿÿt&éEýÿÿvD$Eð@D$E$è"ôÿÆé³ûÿÿMÔ|Àeüÿÿ@<ÀZüÿÿöøMüÿÿ´&éiþÿÿvúÿt&BÒt.EØÀýÿÿEèÀõüÿÿUÐ;r÷vàüÿÿfUÇD$MÈuBÇD$L$4$D$èOôÿÀMÐUìuAÇBfÇBBA@BÆBfBEìÆ@EMì@Aéüÿÿt&ºÿÿÿÿé9üÿÿ¶D$Eð@4$D$èn!ôÿÆéúÿÿvUÇD$MÈuBÇD$L$4$D$èèNôÿÀu`UÐB$R(D$EìT$$è2ôÿEÀ¾Mìéÿûÿÿö¶uyfvruÌEÔL$t$$è|ôÿÆéüùÿÿD$Eìé#þÿÿuÐMðF@AFVAF9A ¿úÿÿA é·úÿÿUÐ}ðB;G G
>ýÿÿG éýÿÿUÔ|À-þÿÿ@<À"þÿÿöøþÿÿvé]ÿÿÿUìuÐ·BNDÂFHL$$D$è1ôÿéÿÿÿuÐA;Fãúÿÿt&éûýÿÿvUåì8EìD$E]ôèUôÿÃÀuø}ü}ÇEìÇEð<$D$èYKôÿÀÆuKEÀ¬EMìQBÇD$AD$EðD$A<$D$èÕôÿÀt-=NÿÿtUÆMìÉtL$<$èBôÿð]ôuø}üì]ÃfMðEÇD$UìD$A $D$ED$øèË÷ÿÿÆMìUABAë¶MìéZÿÿÿ´&Uåì8EìD$E]ôèoTôÿÃ°uø}ü}ÇEìÇEð<$D$èiôÿÀÆuKEÀ¬EMìQBÇD$AD$EðD$A<$D$èÅôÿÀt-=NÿÿtUÆMìÉtL$<$èAôÿð]ôuø}üì]ÃfMðEÇD$UìD$A $D$ED$øè»öÿÿÆMìUABAë¶MìéZÿÿÿ´&UåWVSì\EðD$Eè_SôÿÃ ÇEèÇEäÇEðÇEìD$E$èá1ôÿÀøÆÂ×ÇE¼UäÒtEì@T$D$E¼$èxEôÿUèÒtEì@T$U¼D$$èXEôÿùÉt1À}Àè!ÆEðÀtD$E$èN@ôÿÄ\ð[^_]ÃEÀtiuMðQBÇD$AD$EìD$AD$E$è'ôÿÀÆ=NÿÿÇE¼ßøÂ×ÇE¼éÿÿÿvMðë vUèM:99U¸uu¸UÇEÀF9Bt
.ÇEÀÿÿÿÿMð;y+v¾}Â}ÀÂUÏt	þÿ_öu}Ï´&EÀÀt&u$EÀË}Á}t&²A(D$E¼uäu´t$ÇD$ÇD$$èÒ5ôÿÇEÄÀÏMäE190AÇEÈEðx EÐ9þ3ºöuAÀt&ÿuEÐ@$Àuþpv}Ï®úÿvÒUÐz,vwJ,¸¾Óà©`u1öEìÇD$M´@ÇD$L$D$E¼$èHôÿÀEðñUä@(ÇBÇBfÇBBEìJfBEðP,EäPuMäFAÉt
ÀuHyÿuAUðr öu-B$Àu&EÀÿ}õ}t&æfÉ¶t#EìU¼@L$$D$è1BôÿÀÆ¬Eìu¼ÇEä@4$D$EèD$èBôÿÀÆÇEè´&Eð1ö1ÿMP@Aé:üÿÿ¶EìMèÇEàM°@ L$ÇD$ÇD$E¼u¼EàD$4$è3ôÿÀÜüÿÿ}t}fuD$EàD$Eì$èTôÿÆþÀÇé½ûÿÿÇEÀéÍüÿÿt&U¸1öA9BÄüÿÿéÍüÿÿfUAÇEÈ9BcýÿÿféiýÿÿvUÐB$1Ò9Afýÿÿ´&éeýÿÿAÀýÿÿ1Ò¶é{ýÿÿv¾ÿÿÿÿvéfüÿÿU|Àt@<ÀtöøfEÀt}t}´&êýÿÿfEÈÀvÊEìÇD$U¼@ÇD$$D$E´D$èêEôÿÀÃMðUäA(ÇBfÇBBA0BEìÆBfBEäÆ@EðMäP @$Aé]ýÿÿt&EðU¼t$ÇD$À(ÇD$D$$èË1ôÿÇEÄÀùûÿÿUÒ¬}¢}´&D$Eð@(D$Eì$èmôÿÆþÁÏéÖùÿÿfÇEÈÿÿÿÿéºûÿÿt&ºÿÿÿÿéÈûÿÿ¶EìÇD$u°@ÇD$t$D$E¼$èÀDôÿÀ$MðuèAQFA Àuy$ÿ÷úÿÿA(Féìúÿÿ¶ÿu
u¸~AuM¸D$4$L$èJ	ôÿÆéQýÿÿ´&EÄÀüÿÿt&é!þÿÿvEìÇD$U°M¼@ÇD$T$$D$èDôÿÀUuèMðRVA0FA(;F =úÿÿF é5úÿÿöuy´&WýÿÿEÐL$MÀ D$$éFÿÿÿøfþÿÿMäéXûÿÿD$Eè@D$Eì$èËôÿÆþÂ×é4øÿÿD$EäëÖD$Eè@éAüÿÿU|Àuùÿÿ@<Àjùÿÿöø]ùÿÿ´&é¬þÿÿD$Eä@éäýÿÿÇD$B(uD$Bt$D$E$èôÿÀÆeÿÿÿEðP(Eè;P wMäéÔúÿÿEìÇD$M°u¼@ÇD$L$4$D$èBôÿÀuEðP(EèP ëºD$Eè@D$Eì$èÁôÿøÆÀÇé*÷ÿÿ¶UåWVSì\EðD$EèJôÿÃ`ÇEðÇEìÇEèD$E$è¨7ôÿÀEÀ¹uMðQBÇD$AD$EìD$AD$E$èoôÿÀÆ=Nÿÿu4MðuQAF1öë"D$Eà@D$Eì$èàôÿt&ÆMðÉtEL$$èô6ôÿEèÀt$è*ôÿÀt	övuÆÄ\ð[^_]ÃfMðéMÿÿÿEèD$EìÇD$ÇD$$èb/ôÿÀÆuEèMðuì,A0V EÀ¸«ªªªU¼÷a4Áê}UÐY}ORUÀuàu¸×9Â×éQÒEèÇD$M¸u¼@ÇD$L$4$D$è@ôÿÀÔþÿÿEÐUÀ@Dô9Ç¬GEÜUàÇBBEÜfÇBBEìÆBfBEàÆ@MàWGAEì@L$M¼D$$èl:ôÿÀÆxþÿÿEÐÇuÀ@9Ç?u¸E¼ÇD$ÇD$t$|$$è%,ôÿÀÆ1þÿÿMàÀòþÿÿU;uA;Bvÿÿÿ´&éÞþÿÿvA,UÀ4$ÇD$EÜEÇD$T$ÇD$D$EÜD$EÐD$èÊ1ôÿÀÆ¶ýÿÿMð}äA ÀtvA M¼|$ÇD$ÇD$D$$èm+ôÿÀÆuäUð;B$uF;B(`Eì@t$u¼D$4$è19ôÿÀÆ=ýÿÿMðÇEäAD$E¼|$ÇD$ÇD$$è÷*ôÿÀÆýÿÿuäUð;B-EÀM¼EÔ}Ø|$D$$è¨ôÿÀÆÄüÿÿEØÀtZu¼EÐEÔ|$4$D$è	ôÿÀÆüÿÿEÐUÀ@9Âs'MÀuØÁEÔÀUÀEÔEÐ@9ÁrßuäEìM¼@t$$D$è18ôÿÀÆ	üÿÿé8üÿÿ¶ÇEÜéMýÿÿvMðq }äötuA D$E¼|$ÇD$ÇD$$èÙ)ôÿÀÆóuäU;uF;BoEìM¼@t$$D$è7ôÿÀÆªûÿÿMðÇEäu¼A|$ÇD$ÇD$4$D$èd)ôÿÀÆpûÿÿuäU;nþÿÿF;BbþÿÿEèÇD$M¼@ÇD$|$$D$èµ<ôÿÀMðuäA,F Q ÒuUÀFQAFéþÿÿ¶=õÿÿçúÿÿé8ÿÿÿ=õÿÿvÔúÿÿMð´&éýÿÿF;Bt&ÂýÿÿEèÇD$U¼@ÇD$|$$D$è<ôÿÀu{Eðp öÂuäEÜF E@FélýÿÿEèÇD$M¼@ÇD$$D$EàD$è¼;ôÿÀúÿÿUÀuäFEðP$@(Fé?þÿÿD$EäéèùÿÿEèÇD$u¼@ÇD$|$4$D$èa;ôÿÀuÇuäEÇF@FéWüÿÿMÐÉuuäÇFé+ÿÿÿMÀuäFéÿÿÿë
UåWVSìL}EðD$EèÌBôÿÃ
þÇEðÇEì<$D$è-ôÿÀÆuSEÀÚEMðQBÇD$AD$EìD$A<$D$è+ôÿÀ§=Nÿÿ|ÆMðÉtL$<$èã/ôÿÄLð[^_]Ãt&EðMàÇD$MÀ@$D$è$+ôÿEèU092EÄuMÄUÇEÐA9Bt
þÇEÐÿÿÿÿ;uàþ¶²¹}Â}ÀÐt	ùÿ±ÉÀúMÄy
vÂUìzÀ¶ðÆÇD$BUÌÇD$D$EÈ$D$èu9ôÿÀAUèñEìÇBÇBz
fÇBBfBEèHMEèEÄAMÄAEìUÄMÌ@T$$D$èk3ôÿÀÆþÿÿt&MðEQPQésþÿÿfMðé,þÿÿEìUèUÈ@ T$ÇD$ÇD$EÌEðMÌÀD$$è%ôÿÀÆFþÿÿEÀtW}tQ}t&tFEÈUÌÇD$ÇD$D$Eð$ÀD$è¶$ôÿÀúýÿÿD$Eð@ë¶þõÿÿ4ÿÿÿEðt$@D$Eì$èg
>ôÿÆéýÿÿt&ÇEÐéýýÿÿt&UÄ1ÉEä9Bñýÿÿéýýÿÿ|Àt@<Àtöø¼t&EÐÀþÿÿEÀt}t}t&wþÿÿEìÇD$UÌ@ÇD$$D$EÈD$èr7ôÿÀuBEðP@T$D$Eè$èôÿMðq8öuiMèMÄéþÿÿ¹ÿÿÿÿéIýÿÿ¶D$Eè@é÷þÿÿöu
MÄy&ÿÿÿEÀUÄ<$D$T$èæûóÿMðÆéyüÿÿ¾
UìéAýÿÿEè·PÐQ4t$$T$èôÿEèEÄéýÿÿ¶¿Uåì(EðD$E]ôèo>ôÿÃ°ùuø}ü}<$D$è7&ôÿÀÆuööt$Eð<$D$èÙ+ôÿð]ôuø}üì]Ã¶XÂþÿD$<$è2ôÿÇD$ÿÿ<$èÒûóÿÆë¶fUåW×VSìlèç=ôÿÃ(ùE°1Àz ÇEðÇEìÀEÄEðE D$B UÇD$ÇD$D$$è"ôÿÀtm=õÿÿòD$G MD$$èèôÿÆUìÒtMAT$D$E$èÖ/ôÿUðÒtMAT$D$E$è¶/ôÿÄlð[^_]ÃO É%MðEÇE¼190!7ÇEÀ;w7Eº}EË¶EË}EÓ
>EÓt	úÿKÒu
Àt&EÀÀt&¶UÄU·¶EË
>EÓEÒuMÄÉEð@ ;GýMUìGU¤T$ÇD$ÇD$D$$èÍ ôÿÀÆý=õÿÿÂþÿÿ}·ú}Ò¶êMðG9A ÞMÇD$D$$èôÿÀÆxþÿÿfMìt&Ét#UBL$MD$$èG.ôÿÀÆGþÿÿuÇEìöu{G;GDtsEäD$Euèu¨t$$èûôÿÀÆþÿÿMèÉtFUÄÇEàÒMàEä9ÁËU¨èMD$T$$èÁþóÿÀÆÁýÿÿvMðÉt#uFL$D$E$è-ôÿÀÆýÿÿÇEð1öéýÿÿMðE190M¼ßýÿÿUAÇEÀ9BÖýÿÿÉýÿÿ;wÇEÀÿÿÿÿÉýÿÿG1Ò9AÆýÿÿ»ýÿÿºÿÿÿÿé¶ýÿÿvuÄövÂÇD$õÿÿféõüÿÿvGD$Euìu¤t$ÇD$ÇD$$èÐôÿÀÆÐüÿÿG$UØÇD$U¬$D$è9#ôÿMì1öE;0=MÇEÌÿÿÿÿEØ9ÆE¸²f
>ºöu
>yÀ÷Ð!Â}Òúÿ¬Ò\EÄÀ´&JEðW9P >GD9Â½9ÐðMÇD$u¤AÇD$t$D$E$è1ôÿÀDUìGMÇBBG@fÇBBÆBfBEìÆ@uMìFAé/ýÿÿ´&EÀt}t}´&HüÿÿUÇD$M uBÇD$L$4$D$èâ0ôÿÀEÄÀ+MðG9A sA G@AéfQÒmþÿÿÇEÌéyþÿÿö¶uyfGD$E°L$$è`õóÿÆéÓúÿÿt&EÜ1Ò9A@þÿÿféFþÿÿvUÇD$M uBÇD$L$4$D$è 0ôÿÀuPG;GDÌUÄÒ9MðAuFAé'ûÿÿ}ÆE·EË}EÓéûÿÿ´&D$Eð@D$E$èôÿÆéúÿÿU°|Àt@<Àtöøe´&E¸ÀuEÜÀu;w¦ýÿÿfEÌÀvRûÿÿEÀt&u~UÇD$M¤uBÇD$L$4$D$è/ôÿÀD$EìéEÿÿÿ¶ºÿÿÿÿvéîüÿÿvUA9B<þÿÿ³üÿÿÇEÌvé«üÿÿv}t&tÿÿÿ}¶ªúÿÿfé]ÿÿÿvG@U¼MðBWGAéÂùÿÿt&WGDéÅüÿÿt&u°|Àùÿÿ@<Àùÿÿöøuùÿÿ´&é¹ýÿÿvö¶uyfzþÿÿu¬t$véýÿÿvG$W(D$EìT$$è;ôÿEÀäùÿÿUìOH·BL$ÂGL$D$èôÿéÀùÿÿU¼MðBé¿ýÿÿfuÇD$UFÇD$$D$E¤D$è-ôÿÀuxEìÆ@Ç@Ç@Ç@fÇ@fÇ@EìÆ@MìÇÇAéDùÿÿt&MðèA é7ýÿÿfD$EìU@$D$èkÿóÿÆé~÷ÿÿD$Eì@4$D$èNÿóÿÆéa÷ÿÿUÇD$L$$è@'ôÿÀÆ@÷ÿÿÇEìGéøÿÿA;GWýÿÿ´&éÏúÿÿUè)ÈüÿÿÿD$DD$$è#ôÿEäé
>ùÿÿEàD$EäD$EèD$G$è4ôÿé×øÿÿvUåì8EìD$E]ôè4ôÿÃ`ïuø}ü}ÇEìÇEð<$D$èùôÿÀÆuKEÀ¬EMìQBÇD$AD$EðD$A<$D$èuñóÿÀt-=NÿÿtUÆMìÉtL$<$è5!ôÿð]ôuø}üì]ÃfMðEÇD$UìD$A $D$ED$øè[õÿÿÆMìUABAë¶MìéZÿÿÿ´&Uåì8EìD$E]ôè3ôÿÃPîuø}ü}ÇEìÇEð<$D$èi-ôÿÀÆuKEÀ¬EMìQBÇD$AD$EðD$A<$D$èeðóÿÀt-=NÿÿtUÆMìÉtL$<$è% ôÿð]ôuø}üì]ÃfMðEÇD$UìD$A $D$ED$øèKôÿÿÆMìUABAë¶MìéZÿÿÿ´&UåWVSì\EðD$Eèÿ1ôÿÃ@íÇEèÇEäÇEðÇEìD$E$èq(ôÿÀøÆÂ×ÇE¼UäÒtEì@T$D$E¼$è$ôÿUèÒtEì@T$U¼D$$èø#ôÿùÉt1À}Àè!ÆEðÀtD$E$èîôÿÄ\ð[^_]ÃEÀtauMðQBÇD$AD$EìD$AD$E$èÇîóÿÀÆt-=NÿÿøÂ×ÇE¼é*ÿÿÿ¶Mðë¨vEìMèÇEàM°@ L$ÇD$ÇD$E¼u¼EàD$4$èôÿÀt@}ö}fêEð1ÿuP@F1öé¬þÿÿÇE¼ëÝ´&UèM:99U¸eOÇEÀÿÿÿÿMð;ytt&¾}Â}ÀÂUÏt	þÿOöu}Ï´&"EÀÀt&±EÀG}=}2A(D$E¼uäu´t$ÇD$ÇD$$è
>ôÿÇEÄÀïEÀ¼}²}¶¢EðU´M¼ÇD$À(T$ÇD$D$$èªôÿÇEÄÀD$Eð@(t&D$Eì$èmùóÿÆþÀÇé6ýÿÿfÇEÀé¬þÿÿt&u¸UÇEÀF9BþÿÿþÿÿëÏ´&U¸1öA9Bt&vþÿÿfé~þÿÿvD$Eàé|ÿÿÿt&EìÇD$u°@ÇD$t$D$E¼$èx&ôÿÀMðuèAQFA ÀuA$ÀtA(FA4F }ÿdþÿÿq öuQ$ÒRþÿÿM¼EØ}Ü|$D$$è_ôÿÀÆêþÿÿEÜÀ³EØU¼|$ÀD$$èAñóÿÀÆðUØÒØMðEÜQ(éæýÿÿ¾ÿÿÿÿéyýÿÿ¶uäU9
>OÇEÈEðx EÐ9ùºÉuFÀ¶:ÿuEÐ@$Àuùv}Ïtúÿ´&ïÒ EÀt&}¶z}¶jfö¶tÒfuLFÀuEMðA Àu-A$Àu&EÀ}~}t&ofö¶Eì@t$u¼D$4$èÝôÿÇEäÀÆt\øÀÇé«úÿÿUÐB$1Ò9FÔþÿÿéÚþÿÿUFÇEÈ9Bþÿÿvé þÿÿFÀàþÿÿ1Ò¶éÓþÿÿvEìU¼@$D$EèD$èXôÿÇEèÀÆIûÿÿþÁÏéúÿÿ¶uäéØþÿÿÿuu¸~t&QAuM¸D$4$L$èèóÿøÆÀÇé¶ùÿÿf}ÈÿûEìÇD$u´@ÇD$t$D$E¼$èU#ôÿÀwMðUäA(ÇBfÇBBA0BEìÆBfBEäÆ@EðuäP @$FéþÿÿÇEÈÿÿÿÿéiýÿÿt&ºÿÿÿÿéwýÿÿ¶EìÇD$U°M¼@ÇD$T$$D$è¸"ôÿÀUuèMðRVA0FA(;F Füÿÿé>üÿÿMÄÉýÿÿ´&éîþÿÿD$Eè@D$Eì$è¦ôóÿøÆÂ×éoøÿÿMðéiúÿÿÉu
~vsEÐMt$À D$$ésþÿÿD$Eè@éÚúÿÿEìÇD$U´M¼@ÇD$T$$D$èÚ!ôÿÀuð~,w`N,¸Óà¹©`tJUäF(ÇBBEìÇBfÇBJfBEðP,EäPMuäAFéuüÿÿ1Éë²U|ÀNùÿÿ@<ÀCùÿÿöø6ùÿÿéýÿÿöt+M¼t$ÇD$$è{ôÿÀÆöùÿÿMðÇEäEèQ(9P vuuäéPüÿÿEÜÁâT$D$À$èÛôÿé
>ûÿÿD$EäébþÿÿD$Eä@éùÿÿU|Àûÿÿ@<Àyûÿÿöølûÿÿ¶éYþÿÿT$U¼ÇD$$è`ôÿÀÆüÿÿéeÿÿÿt&UåW1ÿVSì<EðD$Eè(ôÿÃ^ãÇEèÇEðÇEìD$E$èvôÿÀÆuTMÉ}MðQBÇD$AD$EìD$AD$E$èoåóÿÀtW=NÿÿÆ1ÿUèÒtEì@T$<$D$èÿôÿEðÀt}D$<$è	ôÿÄ<ð[^_]ÃvMðëvEìUèUÔx EðT$ÇD$ÇD$ÀD$<$è¢ôÿÀÆt0=õÿÿíD$Eð@D$Eì$èhñóÿÆéUÿÿÿt&MèE190MØuUØMÇEÜB9At
¾ÇEÜÿÿÿÿEð;pEà¸Ò¹}Â}ÀÐt	ùÿÉuÀt&2UÜÒt&u$EÀ}}t&Eì@<$D$EØD$èôÿÇEèÆEðMP@Aérþÿÿf1ÿëät&ÇEÜé=ÿÿÿt&Uà1ÉBUØ9B4ÿÿÿé:ÿÿÿ´&¹ÿÿÿÿé)ÿÿÿ¶EìÇD$@ÇD$<$D$EÔD$è»ôÿÀUèEðUØMØP@Aé1ÿÿÿvöu	MØyvzEàMØÀD$EL$$è[âóÿÆé¨ýÿÿEìÇD$UÔ@ÇD$T$<$D$è;ôÿÀuMèEMØMØ@Aé¶þÿÿD$Eè@éæýÿÿU|Àfþÿÿ@<À[þÿÿöøNþÿÿéXÿÿÿvUåì(EðD$E]ôè$ôÿÃàßuø}ü}ÇEðÇ$D$èÌôÿÀÆuEðHPWD$Ç$èøôÿð]ôuø}üì]Ã¶¼'UåW1ÿVSì<EðD$Eè$ôÿÃ^ßÇEèÇEðÇEìD$E$èFôÿÀÆuPEÀ¡uMðQBÇD$AD$EìD$AD$E$èoáóÿÀÆtm1ÿ=NÿÿtDUèÒtEì@T$<$D$èôÿEðÀtD$E$è
ôÿÄ<ð[^_]Ã´&1ÿEð1öMP@Aë¥MðéeÿÿÿEìUèUØx EðT$ÇD$ÇD$ÀD$<$èôÿÀt*=õÿÿt¥D$Eð@D$Eì$èVíóÿÆé?ÿÿÿvuèEð;HEàMÜt}sk¹ÿÿÿÿ}Â}ÀÐt	ùÿóÉu
Àt&EUÜ;t`Eì@t$<$D$èöôÿÇEèÀÆâþÿÿéÿÿÿt&¹vë¶Uà1ÉB 9FyÿÿÿnÿÿÿëÖ¶@;FfuEÀt}t}t&zÿÿÿEìÇD$uØ@ÇD$t$<$D$èýôÿÀEðuèPf)VP@ Fé,ÿÿÿt&EÜÀu~v~Eàt$uÀ4$D$èÞóÿÆéçýÿÿvEìÇD$@ÇD$<$D$EØD$è{ôÿÀuEðuèM@fFAFé¬þÿÿD$Eè@é4þÿÿM|Àþÿÿ@<Àwþÿÿöøjþÿÿt&éPÿÿÿt&¼'UåW1ÿVSì\EðD$EèÍ ôÿÃÜÇEèÇEðÇEìD$E$èöûóÿÀÆuPEÀ¡uMðQBÇD$AD$EìD$AD$E$èÞóÿÀÆtm1ÿ=NÿÿtDUèÒtEì@T$<$D$è³ôÿEðÀtD$E$è½
ôÿÄ\ð[^_]Ã´&Mð1ÿQ1öAMAë¥MðéeÿÿÿEìUèU¸x EðT$ÇD$ÇD$ÀD$<$è:ôÿÀt:=õÿÿ7Mðqö1ÇEèA ÀgÇEèéxÿÿÿvMèEM´	9%ÇEÈÿÿÿÿEð;H@EÐ1J¾}Â}ÀÂU¿t	þÿ_öu#}¿´&tEÐx´&rfEÈÀu!EÀÂ}ÀÂò}èöu}¿tuÐ~´&ñfEìu´@t$<$D$èôÿÇEèÀÆWþÿÿMðyÕþÿÿéqþÿÿt&D$Eð@D$Eì$èËèóÿÆéþÿÿÇEÈéìþÿÿt&U´uÇEÈB9FÏþÿÿÂþÿÿëÏ´&UÐ1öBDU´9B»þÿÿéÂþÿÿ´&¾ÿÿÿÿé±þÿÿ¶MÐAø´&JÒ{øñþÿÿEìÇD$@ÇD$<$D$E¸D$è¼ôÿÀèUèU´}¿¥Mu´AFé»þÿÿvE¸ÇD$ÇD$<$D$AD$èÆôÿÀv=õÿÿMðt&éýÿÿvE¸ÇD$ÇD$<$D$A D$è~ôÿÀC=õÿÿsMðt&éØüÿÿEðM´P@@DAéþÿÿt&Éu
M´yåEÐuM´À@4$D$L$è§ÙóÿÆé@üÿÿt&EìÇD$u¸@ÇD$t$<$D$èôÿÀ¯UðMèBfÇAABAB UìAÆAfAEèÆ@EðxMèp(@$öÆfÇAfqEÀ¸@uâúÀàúÀ UÀt$$T$è<÷óÿEðMè@M´Aé:þÿÿUèM291U´Ë!ÇEÌEð;pHEÔÍt&¹}Â}ÀÂUÛt	ùÿÉu!}Û´&tMÔy´&§MÌÉu#UÒø}î}fâfEìu´@t$<$D$è
ôÿÇEèÀÆ¿úÿÿMðéMûÿÿU´MÇEÌB9Aÿÿÿé$ÿÿÿUÔ1ÉBLU´9Bÿÿÿé*ÿÿÿUèM291U´¼1ÇEÄEð;pPEÜ¾!¹}Â}ÀÂUãt	ùÿ¹Éu}ã´&¼EÄÀt&u$EÀè}Þ}t&ÏEìu´@t$<$D$è}ôÿÇEèÀÆ¹ùÿÿMðéYúÿÿU´MÇEÄB9A+ÿÿÿé3ÿÿÿUÜ1ÉBTU´9B.ÿÿÿé4ÿÿÿD$Eè@é3ûÿÿD$Eð@é$ûÿÿÇEÌÿÿÿÿéÚýÿÿ¹ÿÿÿÿéïýÿÿD$Eð@ éÿúÿÿÇEÄÿÿÿÿéÊþÿÿ¹ÿÿÿÿéÚþÿÿ}vxûÿÿfékúÿÿvMÔyþÿÿEìÇD$u¸@ÇD$t$<$D$è%ôÿÀQÿÿÿEèMð}ÛE´U´A BQHALM´Aé²ýÿÿU|ÀÁùÿÿ@<À¶ùÿÿöø©ùÿÿéìûÿÿEìÇD$u¸@ÇD$t$<$D$èôÿÀÂþÿÿEèE´EðU´@BMu´AFé+ýÿÿEìÇD$@ÇD$<$D$E¸D$è>ôÿÀjþÿÿEðUè@U´B}ãtMu´AFéÖýÿÿEðM´PP@TAéÀýÿÿöu
M´y~EÔÀHD$UE´$D$è¹ÔóÿÆéR÷ÿÿöuM´yvv{EÜÀPëËEìÇD$M¸@ÇD$L$<$D$èôÿÀýÿÿuèu´ÇFé@ÿÿÿu|Àðûÿÿ@<ÀåûÿÿöøØûÿÿféRÿÿÿu|ÀÀüÿÿ@<Àµüÿÿöø¨üÿÿféUÿÿÿt&¼'UåW1ÿVSì<EðD$Eè½ôÿÃþÑÇEäÇEðÇEìÇEèD$E$è?ÖóÿÀÆuZMÉºuMðQBÇD$AD$EìD$AD$E$èÔóÿÀÆ1ÿ=NÿÿU1ÿUäÒtEè@T$<$D$èôÿEðÀtD$E$èôÿEèÀt$èöóÿÀt	övuÆÄ<ð[^_]ÃfuäE9uUFÇEØ9Bt
´ÇEØEð;H\Eà|¶¢ÇEÜ}Â}ÀÂU×t
>}Üÿ8UÜÒu}×tEàxKEØÀu!EÀÂ}ÀÂO}EEÜÀu}×t&tEàxFEè@t$<$D$ènôÿÀÆµþÿÿÇEäEðuP@F1öéþÿÿMðéLþÿÿEèD$EìÇD$ÇD$$èúúóÿÀÆ_þÿÿEèUäUÐ,Eìx EðT$ÇD$ÇD$ÀD$<$èÑøóÿÀuþÿÿ=õÿÿbÿÿÿD$Eð@D$Eì$èÞóÿÆéïýÿÿUàÇEÜB`9Fnþÿÿé|þÿÿ´&ÇEØÿÿÿÿéGþÿÿt&ÇEÜÿÿÿÿéXþÿÿMàAøÎÒVèþÿÿEèÇD$UÐ@ÇD$T$<$D$è¶ôÿÀ
UðB D$BD$EäD$Eè$è»ÝóÿÀÆ2ýÿÿ}×tMuäAFéBþÿÿEðuäP\@`Fé,þÿÿÉu
>~ÆEàt$uÀ\4$D$èÐóÿÆéÓüÿÿEèÇD$uÐ@ÇD$t$<$D$èù
>ôÿÀuTMðyDq@Q$À÷Ð!Æy(t$À÷Ð!ÂT$A D$AD$EäD$Eè$èöóÿÀÆWüÿÿé ÿÿÿD$Eä@é>þÿÿ}fþÿÿfé;ýÿÿvM|Àÿüÿÿ@<Àôüÿÿöøçüÿÿ´&éÿÿÿUåìU]øuüuèôÿÃAÍBøt3øt.t$E$è£ÛóÿÀÁu	EÇ]øÈuüì]Ãt&1ÉF;BuÂ]øÈuüì]Ã¶¿UåWVSì<}èôÿÃÇÌG EàEðEÜEEØ´&EÜÇEìÇD$D$ED$EØD$Eà$è½õóÿÀuBUðBExÿÿÿ9EtYEìD$ET$<$D$ÿUÀÆuUìÒtEÀuðÄ<[^_]ÃvGD$EðD$Eà$èSôÿÀtÏëÖfzvtÇE´&ë¶UåWVSìuUMèôÿÃÎË·FR ÇfEªU¤~
v&FD$}G$è	ôÿÄ[^_]Ã¶¶FÂþÿØÿàf}ªtU1É´&UxºBöÄuàøÒâúÂ"·ÁB·0¶DÀxàøt}GÁf9Mªw´EPú@;Fú¿u¿EÇD$BD$BD$ED$U¤$è£ôÿÀÿÿÿMEÇAÀþ@°pöëö-Þ|Àt@<Àt
öøÀU¸1ÀU U ÇÀørîEÔE1ÀUÇÀørîUuxº@u¸öÄuàøÒâúÂ ·FBUE¼·FEEÔ+EEØED$U T$FÇD$t$D$AD$M$èDôÿÀþÿÿuëvuÇÇFUùÇFù
ÇFfÇFFfFEHuE8UMAt$D$}¤<$èôÿÀýÿÿUÇÄ[^_]Ã´&1Éf}ªtL·Eªè·À|Uxº@öÄuàøÒâúÂ ·|xE@Á9ùuÃU@;FNÿÿÿé¸ýÿÿ}ÇD$BD$BD$ED$E¤$è_ôÿÀÚüÿÿJÉ@°pösö-f|Àt@<Àt
öøHUÇD$ÿÿÿÿT$BÇD$T$L$D$U$èÛôóÿÀVüÿÿué´&f}ª}òfÇE²}XUxÏç}¬ºB·E²<>·¶<8ú,RFD$UB$èqôÿÄ[^_]Ãf1Éf}ªtX·Eªè·À|Uxº@öÄuàøÒâúÂ ·|xE@Á9ùuÃE8«ýÿÿt$U$èrÕóÿÄ[^_]ÃvuÇÇF·FèfÀfF\ýÿÿMÇéZýÿÿ¶ÈàøÒâúÂ"ééþÿÿv<t\<ÿÿÿfE²·M²f9Mª¨þÿÿF¿
Àuûÿÿéüüÿÿt&E¬ÀuAá¶·D>"Á÷ÑfL7 ë0fEfE²·M²@f9MªMþÿÿë£t&·D>BÁ÷ÑfL7@·ÀfÉElÿÿÿ1Ò¶}·ÂG}·D}Tf9ÊfrßfE²·M²f9Mªëýÿÿé>ÿÿÿ´&·D>Á÷ÑfL7ëUåì(E]ôuøu}üPè:
>ôÿÃ{ÅöÂ t @E9ÆM)Æðq9ðÒyE1ÿöpuhø]ôuø}üì]ÃöÂ§öÂ@tzUÀtRÒt1ÿ9Ö¸ EUt$D$$èAùóÿÀÇÀé~1öët&UMÇD$t$T$UÇD$$ÿR,Çéjÿÿÿfæts1ÿö´&tSMÀt;qv-¿éÿÿë>MEt$L$$èNÚóÿÀÇÀötÀtUMt$L$$ègäóÿEpéøþÿÿÆéáþÿÿUÒtQEÀtJöt.UÀt9Æv!MEt$L$$èîóÿÀÇu$U2U1ÿM¸éwÿÿÿf¿ëMÇë´&¼'UåìH}ü}]ôuøè`ôÿÃ¡Ã
v%GUD$B$èôÿ]ôuø}üì]Ãv¾O¸Óà©`tnU¹@xöÄ÷UQ·8¶B$øk·
>BU L$MD$T$UL$T$UB$èÞÓóÿéuÿÿÿt&© PÿÿÿE°xòâUÜtg¹@UW·Eà8©MÉurU·MÜº@ÉuæþÒâúÂ Mèf+J·ÈEàÀéJÿÿÿ´&ðàøÉáúÁ ë¶àøÉáúÁ éöþÿÿt&UÜ¸>ÒuðàøÀàúÀM·Héiÿÿÿt&ÁEèQUìAM T$UEðL$MD$ET$L$MD$$èÊóóÿéAþÿÿM EL$MD$BD$BUL$D$ET$$èóóÿéþÿÿUåìØ]ôè&ôÿÃgÁ}üÇe¡Eð1ÀÄýÿÿuøhýÿÿÇØýÿÿÇÔýÿÿÇÐýÿÿÇÄýÿÿD$ÇD$ÇD$T$ÇD$<$èôÿÀÆt$Uðe3ð¯]ôuø}üì]Ãt&ÄýÿÿUÜTýÿÿT$ÇD$D$<$èeßóÿÀÆÔýÿÿÀt$è	æóÿÀtö´&uÆt&ØýÿÿÀt&ÇD$ÇD$$èòÖóÿÀt
>öuÆt&ÐýÿÿÀtD$<$è^çóÿÀtöuÆÄýÿÿÀ&ÿÿÿD$<$èjòóÿéÿÿÿÐýÿÿD$ÄýÿÿÇD$ÇD$ÇD$D$<$è`ùóÿÀÆt&Äýÿÿt$<$D$ç
þÿD$èÚ÷óÿé
>ÿÿÿÜýÿÿ\ýÿÿµÈýÿÿD$Ðýÿÿµ`ýÿÿt$ÇD$D$<$èôóÿÀÆÅþÿÿ½Èýÿÿt*Äýÿÿf¾<$D$(èýÿD$èßóÿéþÿÿè¾ØýÿÿÇD$|$$èpûóÿÀÆkþÿÿEÀt ØýÿÿÇD$$èéÍóÿÀÆDþÿÿÄýÿÿ\ýÿÿÇD$ÇD$D$ØýÿÿT$<$D$èIóóÿÀÆþÿÿEÜµýÿÿØýÿÿÇ°ýÿÿµXýÿÿþÿÿEàþÿÿEäþÿÿEèþÿÿEì þÿÿx´ýÿÿBt$ÇD$<$¸ýÿÿ°ýÿÿýÿÿ\ýÿÿD$èñóÿÀÆrýÿÿÐýÿÿÇD$ÇD$ÇD$D$<$èsåóÿÀÆ>ýÿÿµ\ýÿÿ`ýÿÿÐýÿÿÇD$t$T$D$<$è{ìóÿÀÆýÿÿÐýÿÿ<$D$èÝóÿÀÆêüÿÿhýÿÿÇD$ÇD$ÇD$D$ØýÿÿÇD$ÇD$ÇD$$èÍÔóÿÀÆüÿÿØýÿÿö{üÿÿ@ lýÿÿ1ÀXýÿÿÇÀørëµxýÿÿ1ÀµdýÿÿdýÿÿÇÀørëÔýÿÿD$ØýÿÿÇD$ÇD$$èÕçóÿÀpýÿÿtµpýÿÿéüÿÿÌýÿÿPýÿÿXýÿÿµdýÿÿÇD$D$Ôýÿÿt$$è:ÏóÿÀÆ
>xýÿÿµPýÿÿèûøóÿÀuU¶¶µÍýÿÿ¶Îýÿÿ¼ýÿÿð½ýÿÿ¶Ïýÿÿ¾ýÿÿPýÿÿ¿ýÿÿ¶ÎýÿÿòÎýÿÿÏýÿÿÍýÿÿÀýÿÿµPýÿÿD$lýÿÿÇD$ÇD$t$$èåóÿÀÆûÿÿµTýÿÿÀýÿÿJ4B4FAFAFAFAÔýÿÿ@D$ÀýÿÿD$lýÿÿ$è¥òóÿÀÆÇþÿÿé»úÿÿ=óÿÿt&«úÿÿféþÿÿvUåì(U]ôuøu}üðè×ÿóÿÃ»Àj@@ÀuPô©×ötSþtKUÀÂþÿÇD$D$$è:áóÿ¶]ôuø}üì]ÃvUôöÄ@u¨$èáóÿëØE¸¼ÿ÷UEðÇD$D$$è!ÐóÿÀu©U|Àt@<Àt
>øÉu[UÁîEæ4$è¿øÿÿÇUðøÒhÿÿÿÇBøéZÿÿÿfÀÂþÿD$EÇD$$èOúóÿé6ÿÿÿ¶ÇD$$è$ßóÿÀÇu¥UÁîEæ4$èNøÿÿÇE$è½ßóÿÀtÿxÿÿÿÇvénÿÿÿvUt&éþÿÿvÇEðéÿÿÿUåWVSì<Uè&þóÿÃg¹ðÀ»@@ÀuIô©(}ÿtQ}tHÕÂþÿÇD$D$U$èßóÿÄ<[^_]ÃvUôöÄ@u¯$èîßóÿÄ<[^_]ÃfE°¼ö?EðÇD$D$U$èiÎóÿÀu¦U|Àt@<ÀtøÉ§ÇEàÇD$ED$Eì$èÒôóÿÀÇ,÷EtÇD$Eì$èLÇóÿÀÆØÇD$ÇD$ÇD$ÇD$ÇD$UÇD$T$Eì$èÏóÿÀÆrEìUäÇEäUÜx EèEØë5´&EèÇÇ@ÇD$D$<$èðîóÿÀÆu@EäEØÇD$ÇD$D$UÜ<$T$èÀàóÿÀÆt¦1ÀþõÿÿÀè!ÆÇD$ÇD$Eì$èïÍóÿÀÇ¡öEàÀtqE$è*ÝóÿÀtbÿu^Çt&ëV¶ÕÂþÿÇD$D$E$èG÷óÿÄ<[^_]ÃvÇD$$èÜóÿÇEàÀÇ?þÿÿ´&UðøÒ¨ýÿÿÇBøÄ<[^_]Ãf÷éaÿÿÿUéGýÿÿÇEðéÒýÿÿvEt$D$ç
þÿD$U$èîóÿéõþÿÿU¸%åUú Dú@¸C6ú¸%ú¸ú¸	ú¸òú¸áú¸Ðú ¸ÿ¿ú@¸ý?®ú¸ú¸ú¸ÿÿ{ú¸jú¸ùÿYú¸ÿÿHú¸ÿÿ7ú¸ýÿ&ú¸ú ¸ ú0¸ùÿ/óú@¸ýÿ?âú`¸ùÿ_Ñú¸	ÀúÀ¸À¯ú¸ýÿÿú¸õÿú¸Ùÿÿ|ú¸voú¸ûÿÿvbú¸ûÿÿvUú¸vHú¸v;ú¸v.ú¸v!ú ¸ýÿÿvú0À%òÿÿï@f]Ã¶UåMUÉt1ÀÇÂÿÿÿÿÇDÂÀ9Áwê]ÃUåì8}üÇEðD$]ôèkøóÿÃ¬³uøD$GUà$èuØóÿÀÆtð]ôuø}üì]Ãt&ÇD$D$ED$EàD$G$èåÚóÿÀÆtEðD$G$èåóÿë¬´&EìEÜD$D$EðD$EàD$G$è+èóÿÀÆu¶Eðf@ÇD$D$ED$EàD$G$èfÚóÿÀÆuEÜD$D$EðD$EàD$G$èzáóÿÆéTÿÿÿ´&UåWVSìÜUEàD$è<÷óÿÃ}²ÇEàÇEäÇEÔD$BÇEÜ$è.×óÿÀtvUÜÆÒtT$UB$èäóÿEÔÀtMD$A$èväóÿEäÀtUD$B$è]äóÿEàÀtMD$A$èDäóÿÄÜð[^_]ÃvM9ÿ5EÜÇdÿÿÿÇpÿÿÿÇtÿÿÿLÿÿÿé,´&EÜdÿÿÿU<MÇD$|$L$D$B$èñØóÿÀÆ3UEÐD$MTÿÿÿL$D$EàD$B$èHæóÿÀÆúUà·BfZÿÿÿÆB}ÇÇBÀàúÀBUÇD$M|$L$D$B$èYØóÿÀÆTÿÿÿUMD$L$D$EàD$B$ècßóÿÀÆui·ZÿÿÿtÿÿÿEàdÿÿÿxÿtSdÿÿÿ9pÿÿÿÉþÿÿpÿÿÿpÿÿÿLÿÿÿUÁàL$D$B$èÑÚóÿÀÆþÿÿvUÜé×ýÿÿ½dÿÿÿ}EÔUD$dÿÿÿÁàD$B$èÍÔóÿÀÆuÃEØMD$UEL$$D$è·ìóÿÀÆuMEäD$D$A$èÔóÿÀÆxÿÿÿEäÇxÿÿÿÇ@EÈPÿÿÿfÇbÿÿÿÇhÿÿÿÇlÿÿÿé¬¨Ø·Ww ¹ ·GÀ)Â)Êú	EUÇD$MD$GL$D$B$èÖóÿÀÆÞþÿÿTÿÿÿUMD$L$D$EäD$B$è¦ÝóÿÀÆ¨þÿÿfÇbÿÿÿhÿÿÿ9dÿÿÿf½bÿÿÿuoEØUäMBÇBÇBfÇBfB¶xÿÿÿBUä}À÷ÐÀBEälÿÿÿUÔÇÇ@EØÁÀlÿÿÿEØUÇD$hÿÿÿD$EÜD$ED$B$èÕóÿÀÆ×ýÿÿMTÿÿÿT$D$EàD$ED$A$èïâóÿÀÆ¡ýÿÿEÀu=EàU}äE°xöÄFþÿÿw@·W¹@éIþÿÿUÜ1öMé<ûÿÿE·bÿÿÿMà}ä°x\ÿÿÿM¬òâè¸@M¬|ÿÿÿ¶A<à<U¬MBD$A$èëóÿÀÆéüÿÿ}äfbÿÿÿhÿÿÿfGé.þÿÿM°AL$EÈE$èÙ½óÿ·bÿÿÿEÌ·GèfGfVUxº@öÄuàøÒâúÂ Pÿÿÿ·QPépÿÿÿw·W¹é#ýÿÿðàøÀàúÀ éÿÿÿÒk÷ÆU¬·O·B fM¶Ð·ÑE¹ E·ÀfE·GÀ)Â·E)Ê%üÿÀ9ÂÆüÿÿ·E\ÿÿÿ·M¶àüÒf)Á÷ÆÈfO|ÿÿÿDÿÿÿ\ÿÿÿfQº@uæþÒâúÂ DÿÿÿM¬·4U47·fE¸¶BàEºAL$E¼E$ès¼óÿEÀE¸E¼FEÀFUÆ·ÂT$4$D$ècËóÿM¶A$ø$þÿÿA$UEèT÷ÿÿÀÆ	þÿÿéíúÿÿÒ¸@¶uðàøÀàúÀ M¬·ÈE¶@$øøýÿÿ·OÒfM´¹@uðàøÉáúÁ ·G·U´À)Â)Êú`ûÿÿ\ÿÿÿ\ÿÿÿ|ÿÿÿÀDÿÿÿ·E´è÷ÆfGfQº@uæþÒâúÂ DÿÿÿM¬·4UfÇE¸47¶BàEºAL$E¼E$è»óÿVEÀE¸E¼FEÀFMFABABAé¶þÿÿU¬·O·B@fM¶Ð·ÑE¹@éýÿÿ·GÒ¹@fEªuðàøÉáúÁ U··UªÀfE·GÀ)Â·E)Ê%üÿÀ9Â=úÿÿ·E\ÿÿÿ·UªàüÉf)Â÷ÆÐfW|ÿÿÿDÿÿÿ\ÿÿÿfJº@uæþÒâúÂ DÿÿÿM¬·4U47·fE¸¶BàEºAL$E¼E$èê¹óÿEÀE¸E¼FEÀFUÆ·ÂT$4$D$èÚÈóÿé¨ûÿÿU¬·O·BfM¶Ð·ÑE¹émüÿÿ½lÿÿÿ}äMÇD$D$GD$ED$A$èêÏóÿÀÆ,øÿÿMTÿÿÿT$D$EäD$ED$A$èôÖóÿÀÆö÷ÿÿEÜUÔ½lÿÿÿEÔUÜrúÿÿlÿÿÿxÿÿÿdÿÿÿéjøÿÿ}ätÿÿÿWéTÿÿÿUåEW1ÿVuÀtb´&¶ÒtEú tkú	teú
>Áu(¶ëU¶ú t&tNú	vtFú
>vt>Á¶ÒuÜ1Ò8uÐÀu¥Çø^_]ÃÇÆÿ	tèÐëàÁ´&ÆQëÆUåWVSèÜëóÿÃ§ìEeUð1ÒÇìþÿÿÇD$þÿÿìþÿÿD$VþÿD$þÿÿÇD$ÇD$$èLèóÿÀÆ¶ìþÿÿÒ¨Ôþÿ$D$è²¶óÿþÿÿ$þÿÿìþÿÿD$èÔØóÿþÿÿÀjðþÿÿÃþÿþÿÿÃþÿþÿÿ$Ãþÿþÿÿ2ÃþÿÇ þÿÿþÿÿþÿÿt&þÿÿþÿÿÇD$D$$è\µóÿÀêþÿÿÇD$
>$è³óÿÀìþÿÿkÆþÿÿìþÿÿèÌÁóÿ·â ëvÀìþÿÿìþÿÿ8uìÒuè¶ðþÿÿÀ	<#°þÿÿD$þÿÿ$èÕÊóÿøÆêþÿÿ½°þÿÿ$|$èBÍóÿÀ>þtV8Æþÿ þÿÿD$þÿÿ|$T$$èïÄóÿ¾þÿÿ$èlÂóÿUðe3ð&Ä[^_]ÃØþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$þÿÿ$èÕ¬óÿÀuØþÿÿþÿÿD$$è)¹óÿÆöuÿÿÿv þÿÿéTþÿÿ½°þÿÿé0ÿÿÿþÿÿÁÿþþþ÷Ð!Ââté÷ÂuÁêÁÒÙ+þÿÿùÿVþÿÿçÂþÿ¾D$þÿÿ$èæÃóÿé÷þÿÿt&þÿÿ|$$èêËóÿÀujþ¨þÿÿØþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$$èÓ«óÿÀþÿÿØþÿÿD$þÿÿ$èS°óÿÆéõþÿÿþÿÿ|$$èjËóÿÀujþ(þÿÿØþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$þÿÿ$èS«óÿÀþÿÿØþÿÿþÿÿD$$èóÒóÿÆéuþÿÿþÿÿ|$$èêÊóÿÀujþ¨ýÿÿØþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$$èÓªóÿÀýÿÿØþÿÿD$þÿÿ$èSãóÿÆéõýÿÿfþÿD$<$èjÊóÿÀþ$ýÿÿµ´þÿÿFÃþÿD$4$èAÊóÿÀÄOÃþÿD$4$è'ÊóÿÀ_ÃþÿD$4$è
ÊóÿÀtJnÃþÿD$4$è÷ÉóÿÀºüÿÿþÿÿÇD$ÇD$$è¾óÿÆéCýÿÿ¶èSxþÿÿÇD$ÇD$$èQ¾óÿÆéýÿÿþÿÿÇD$ÇD$$è,¾óÿÆéîüÿÿþÿÿÇD$ÇD$$è¾óÿÆéÉüÿÿkæýÿD$<$è>ÉóÿÀþøûÿÿèþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$$è#©óÿÀÜûÿÿäþÿÿD$¸þÿÿÇD$ÿÿÿÿÇD$ÇD$D$þÿÿ$èá¨óÿÀûÿÿàþÿÿþÿÿD$¼þÿÿÇD$ÿÿÿÇD$ÇD$D$$è³óÿÀÆ[ûÿÿàþÿÿD$äþÿÿD$èþÿÿD$þÿÿ$è©¸óÿÆé«ûÿÿyÃþÿD$<$è ÈóÿÀu(þÞúÿÿ´þÿÿþÿÿD$$èëÇóÿÆémûÿÿÃþÿD$<$èâÇóÿÀtÂìþÿD$<$èÌÇóÿÀutþúÿÿàþÿÿD$´þÿÿÇD$ÿÿÿÇD$ÇD$D$þÿÿ$èµ²óÿÀÆqúÿÿàþÿÿþÿÿÇD$D$$èËÒóÿÆéÍúÿÿ=æýÿD$<$èBÇóÿÀ"þüùÿÿµ´þÿÿÃþÿD$4$èÇóÿÀu¡ÃþÿD$4$èÿÆóÿÀ6®ÃþÿD$4$èåÆóÿÀ÷»ÃþÿD$4$èËÆóÿÀ¸ÉÃþÿD$4$è±ÆóÿÀyÕÃþÿD$4$èÆóÿÀ:âÃþÿD$4$è}ÆóÿÀûôÃþÿD$4$ècÆóÿÀ¼ÄþÿD$4$èIÆóÿÀ9ÄþÿD$4$è/ÆóÿÀú!ÄþÿD$4$èÆóÿÀ»+ÄþÿD$4$èûÅóÿÀ|6ÄþÿD$4$èáÅóÿÀCÄþÿD$4$èÇÅóÿÀÜRÄþÿD$4$èÅóÿÀ`ÄþÿD$4$èÅóÿÀÇnÄþÿD$4$èyÅóÿÀ~ÄþÿD$4$è_ÅóÿÀÃÄþÿD$4$èEÅóÿÀøÿÿþÿÿÇD$ÇD$$èï óÿÆéøÿÿ¦þÿ|$$èÅóÿÀ´þÀ÷ÿÿØþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$$èë¤óÿÀ¤÷ÿÿØþÿÿD$þÿÿ$è¦óÿÆé
øÿÿþÿÿÇD$ÇD$$èF óÿÆéè÷ÿÿþÿÿÇD$ÇD$$è! óÿÆéÃ÷ÿÿþÿ|$$è8ÄóÿÀ¼þòöÿÿØþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÇD$ÇD$D$$è¯óÿÀÆÙöÿÿØþÿÿD$þÿÿ$èÛÉóÿÆé=÷ÿÿþÿÿÇD$ÇD$$èvóÿÆé÷ÿÿþÿÿÇD$ÇD$$èQóÿÆéóöÿÿþÿÿÇD$ÇD$$è,óÿÆéÎöÿÿþÿÿÇD$ÇD$$èóÿÆé©öÿÿþÿÿÇD$ÇD$$èâóÿÆéöÿÿþÿÿÇD$ÇD$$è½óÿÆé_öÿÿþÿÿÇD$ÇD$$èóÿÆé:öÿÿþÿÿÇD$ÇD$@$èsóÿÆéöÿÿþÿÿÇD$ÇD$$èNóÿÆéðõÿÿþÿÿÇD$ÇD$@$è)óÿÆéËõÿÿþÿÿÇD$ÇD$$èóÿÆé¦õÿÿþÿÿÇD$ÇD$ $èßóÿÆéõÿÿþÿÿÇD$ÇD$$èºóÿÆé\õÿÿÇD$þÿÿÇD$ $èóÿÆé7õÿÿþÿÿÇD$ÇD$$èpóÿÆéõÿÿþÿÿÇD$ÇD$$èKóÿÆéíôÿÿéþÿ|$$èbÁóÿÀujþ ôÿÿØþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$$èK¡óÿÀôÿÿØþÿÿD$þÿÿ$èµóÿÆémôÿÿoþÿ|$$èâÀóÿÀujþ óÿÿØþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$$èË óÿÀóÿÿØþÿÿD$þÿÿ$è[ÛóÿÆéíóÿÿÄþÿD$<$èbÀóÿÀu(þ óÿÿ´þÿÿþÿÿD$$è¬óÿÆé¯óÿÿ©ÄþÿD$<$è$ÀóÿÀtÂ+£þÿD$<$èÀóÿÀubþÌòÿÿµ´þÿÿ´ÄþÿD$4$èé¿óÿºÀtÄÄþÿD$4$èÎ¿óÿºÀþÿÿT$$èóÿÆé!óÿÿ£þÿ|$$è¿óÿÀHþPòÿÿØþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$$è{óÿÀ4òÿÿØþÿÿD$þÿÿ$èK¿óÿÆéòÿÿÓÄþÿD$4$è¿óÿºÀDÿÿÿäÄþÿD$4$èó¾óÿºÀ%ÿÿÿõÄþÿD$4$èÔ¾óÿºÀÿÿÿÅþÿD$4$èµ¾óÿºÀçþÿÿÅþÿD$4$è¾óÿºÀÈþÿÿ&ÅþÿD$4$èw¾óÿºÀ©þÿÿ5ÅþÿD$4$èX¾óÿÀñÿÿº	éþÿÿ÷¢þÿ|$$è4¾óÿÀujþòðÿÿØþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$$èóÿÀÖðÿÿØþÿÿD$þÿÿ$è]¬óÿÆé?ñÿÿÜ¢þÿ|$$è´½óÿÀujþrðÿÿØþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$$èóÿÀVðÿÿØþÿÿD$þÿÿ$è}ÄóÿÆé¿ðÿÿFÅþÿD$<$è4½óÿÀurþòïÿÿèþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$$èóÿÀÖïÿÿÇD$èþÿÿD$þÿÿ$èÁóÿÆé7ðÿÿ5+þÿ|$$è¬¼óÿÀulþjïÿÿØþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÇD$ÇD$D$$è§óÿÀÆQïÿÿØþÿÿD$þÿÿ$è3ÔóÿÆéµïÿÿWÅþÿD$<$è*¼óÿÀºþäîÿÿàþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÇD$ÇD$D$$è§óÿÀÆËîÿÿÜþÿÿD$¸þÿÿÇD$ÿÿÿÇD$ÇD$D$þÿÿ$èË¦óÿÀÆîÿÿÜþÿÿþÿÿD$àþÿÿ$D$è¿¡óÿÆéáîÿÿhÅþÿ|$$èV»óÿÀujþîÿÿØþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$þÿÿ$è?óÿÀøíÿÿØþÿÿþÿÿD$$èËóÿÆéaîÿÿxÅþÿD$<$èÖºóÿÀumþíÿÿàþÿÿD$´þÿÿÇD$ÿÿÿÇD$ÇD$D$þÿÿ$è¿¥óÿÀÆ{íÿÿàþÿÿøîÿÿÀÀ¶ÀD$éøÿÿþÿD$<$èSºóÿÀulþíÿÿàþÿÿD$´þÿÿÇD$ÿÿÿÇD$ÇD$D$þÿÿ$è<¥óÿÀÆøìÿÿàþÿÿþÿÿD$$èzóÿÆé\íÿÿ8Ãþÿ|$$èÑ¹óÿÀujþìÿÿØþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$þÿÿ$èºóÿÀsìÿÿØþÿÿþÿÿD$$è:ÒóÿÆéÜìÿÿÅþÿD$<$èQ¹óÿÀu(þìÿÿ´þÿÿD$þÿÿ$èüÔóÿÆéìÿÿÅþÿD$<$è¹óÿÀtÂ{>þÿ|$$èý¸óÿÀujþ»ëÿÿØþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$$èæóÿÀëÿÿØþÿÿD$þÿÿ$èFóÿÆéìÿÿÅþÿD$<$è}¸óÿÀuXþ;ëÿÿèþÿÿþÿÿD$´þÿÿÇD$ÿÿÿÿÇD$ÇD$D$$èfóÿÀëÿÿÇD$éDûÿÿ¯ÅþÿD$<$è¸óÿÀufþÍêÿÿµ´þÿÿ»ÅþÿD$4$èê·óÿºÀtÌÅþÿD$4$èÏ·óÿºÀuHT$þÿÿÇD$$èÜÒóÿÆéëÿÿþÿÿþÿÿD$`ÆþÿD$$èc¯óÿéoêÿÿÜÅþÿD$4$èl·óÿºÀtðÅþÿD$4$èQ·óÿºÀtÆþÿD$4$è6·óÿºÀcÿÿÿÆþÿD$4$è·óÿº ÀDÿÿÿ&ÆþÿD$4$èø¶óÿÀ»éÿÿº@é ÿÿÿUåWVSèÓóÿÃÍì,EìD$ÇD$E$è³óÿÀÆtÄ,ð[^_]ÃfÇD$ED$Eì$èróÿÇD$ÇD$ÇD$ED$E$èèµóÿÀÆ¢UÒtEEðEà¿EàÇD$D$EìD$ED$E$èä¼óÿÀÆubïuÍmuÁEÀtjEðEàë¶)}tW}ÿv¿Eà|$D$EìD$ED$E$è¼óÿÀÆtÁEìD$E$èú¿óÿÄ,ð[^_]ÃED$E$èóÿÆëÎ´&¼'Uåì8]ôEðèÒóÿÃW}ü}D$EuøÇD$ÇD$@ÇD$|$$è±ÆóÿÀÆu2EèD$EìD$EðÇD$|$D$E$èóÿÀÆtEç
þÿD$E|$t$$èüÄóÿEðÀtD$E$èæ³óÿð]ôuø}üì]ÃvEèÇD$ÿD$EìD$EðD$E$è<óÿÀÆuªEèÇD$D$EìD$EðD$E$èóÿÀÆxÿÿÿEèÇD$ÿD$EìD$EðD$E$èÜóÿÆéIÿÿÿö¼'Uåì8]ôEìè¶ÐóÿÃ÷}ü}uøD$ÇD$ÇD$ <$è «óÿÀÆtð]ôuø}üì]Ã´&UÇD$<$ê Ð%ÿÿD$EÁêT$D$è³óÿÀtEì<$D$èÏ½óÿë£EðD$EìÇD$ <$D$ED$èºóÿëÇUåUVÖu9òtB¶JÀt.1Òt&iÒÙ<Æc¶À9Î=Ã9t¶ÁÀuâ9ñvÞÐ^]Ã9ñ¶vÈ1Òt&ëè¶U1ÀåìU$èÏóÿÃÅt$ÒtrâMÆþÿÁîØÿà$t$ì]Ãt&¶1ÒÁÐiÐ?¶ÁÐiÐ?¶ÁÐiÐ?¶ÁÐiÐ?¶ÁÐiÐ?¶ÁÐiÐ?¶ÐîtiÐ?Á¶ÁÐiÐ?¶ÁÐiÐ?ë1ÒëÝt&1ÒëÂt&1Ò¶ë¦¶1Ò¶ë¶1Ò¶égÿÿÿv1Ò¶éIÿÿÿv1Ò¶é+ÿÿÿvU1ÒåEVSèXÎóÿÃÀtpàM¤ÆþÿÁîØÿàÐ[^]Ãf¶1ÒÁÐÂÁâÂ¶ÁÐÂÁâÂ¶ÁÐÂÁâÂ¶ÁÐÂÁâÂ¶ÁÐÂÁâÂ¶ÁÐÂÁâÂ¶îtÐÁÁà¶ÁÐÂÁâÂ¶ÁÐÂÁâÂé|ÿÿÿv1ÒëÖt&1Òë¸t&1Ò¶ë¶1Ò¶éyÿÿÿv1Ò¶éZÿÿÿv1Ò¶é;ÿÿÿv1Ò¶éÿÿÿvU1ÉåUVÖu9òs¶iÉ¶Â1Á9ÖwîÈ^]ÃUåE]¾ÃUåWVSèìÌóÿÃ-ìE$èÝ¨óÿpEðD$t$U$èä¬óÿÀÇt
>Äø[^_]Ãt$ED$Eð$èþ§óÿUð¶BrÀuëEfÆ¶Àt6</t&uîÆÇD$EðD$U$èm¡óÿÀu-Æ/Æ¶ÀuÊUð1ÿT$E$èØ¹óÿÄø[^_]ÃfUäD$Eð$D$è §óÿÀÇt±Uðë¾UåSìEèèËóÿÃ)D$E$èhµóÿÄ[]Ã¶UåWVSìüEMUèËóÿÃî@RHÿÿÿ ÿÿÿöö®
z4½Lÿÿÿ ÿÿÿukA84LÿÿÿÇEðÌöTÿÿÿt}G\À(E ÿÿÿÀá½ ÿÿÿ¸ÍÌÌÌMÇXÿÿÿÇdÿÿÿ÷ghG@Çø½@ÿÿÿI}ìÁê)Ð ÿÿÿlÿÿÿEð(ÿÿÿÇhÿÿÿÂðDÿÿÿÇpÿÿÿÇtÿÿÿÇxÿÿÿÇ|ÿÿÿÇE½$ÿÿÿÿÿÿ$ÿÿÿT$ML$}<$èZóÿÀÆ4|ÿÿÿÀ¦½ ÿÿÿGhÀdÿÿÿ1ÉtÿÿÿÇ`ÿÿÿt&½ ÿÿÿG<kÐ4ÀLÿÿÿ9TÿÿÿG<PÿÿÿwLÿÿÿÇG<Pÿÿÿ½ ÿÿÿQdÿÿÿ;O8"½PÿÿÿÿWúÿxÿÿÿÀ ÿÿÿHDÉtø+LÿÿÿÁøiÀÅNìÄ9ÁÂ@;lÿÿÿÉµXÿÿÿö®ÉnXÿÿÿ+LÿÿÿÁøiÀÅNìÄ9ÁQXÿÿÿA@9ÂJÇXÿÿÿUBÀ½PÿÿÿÀµPÿÿÿPÿÿÿARøÿUðÁÏÇPÿÿÿ,ÿÿÿÀ(<ÿÿÿt&MhÿÿÿQööÜG\ÿÿÿG$úøÿtk4·f;w¶F;Gw÷F$øÿtÆ·f;väF$øÿuî9þTfÒJöG ¶²öF ¶¢÷òf?,µxÿÿÿöÁ9×ÎtÉtE;GöG´&Ú ÿÿÿ\ÿÿÿHTÉtpUÒå$ÿ5ñÉÁöG t&²f?¶¢ÿÿÿ|$D$PÿÿÿT$ML$E$èóÿÀf?föG ffÇÇD$|$PÿÿÿL$}|$E$èqóÿÀÆ½PÿÿÿÇEðGøÿ
>½,ÿÿÿÇé-þÿÿ½Xÿÿÿ;W¶ýÿÿXÿÿÿPÿÿÿé¥ýÿÿt&ROÊ\ÿÿÿéþÿÿPÿÿÿXÿÿÿ ÿÿÿAhÀüÿÿdÿÿÿélüÿÿt&N ùÿ¬PÿÿÿHÿÿÿ@(0ÿÿÿB4ÿÿÿô%ÿÿÿùT0ÿÿÿ;B<ÿÿÿÀÐD0ÿÿÿ;H<ÀÀÞýÿÿUÒtIf?òØýÿÿt&PÿÿÿÀUBÀ1½(ÿÿÿ9½`ÿÿÿÿÿÿé7ûÿÿ<ÿÿÿL$Hÿÿÿ$èäóÿÀuN ùÿ·	HÿÿÿPÿÿÿR(E @Uô%ÿÿÿCE P,TE;B<CÿÿÿÀmDM;H<ÀÀqòÇEéîüÿÿt&fÇÇD$|$\ÿÿÿT$PÿÿÿL$E$è³óÿf/À<xÿÿÿÉÖþÿÿPÿÿÿBøÿÓ
>µ,ÿÿÿRÆñ)Â|
>ô9÷©þÿÿNùÿ
>ðF)ÐDðF ÿÝ<$èóÿÂPÿÿÿ,ÿÿÿÇFÿÿÿÿAÏ)ðFIÉð½Pÿÿÿ)ÈÀ+,ÿÿÿDPÿÿÿF+,ÿÿÿAF$Vøÿ$½Pÿÿÿ,ÿÿÿGx ÿu
>x$ÿ$$èóÿPÿÿÿPÿÿÿBÀäýÿÿD$½Hÿÿÿ<$è«óÿÀÊýÿÿ¾ÿÿÄüð[^_]Ã ÿÿÿé©ûÿÿW UÂ4HÿÿÿPÿÿÿI(E¸@M´ô%ÿÿÿzME´Tÿÿÿÿÿÿ;A<ÿÿÿÑÀuE¸ÑH,U´;Q<ÀÀt2<ÿÿÿL$Hÿÿÿ$è.óÿÇEv$ÿûÿÿW U}ÿvHÿÿÿPÿÿÿI(EÐ@MÌô%ÿÿÿgMEÌTÿÿÿÿÿÿ;A<oÿÿÿÑÀuEÐÑH,UÌ;Q<úÿÿéíúÿÿt&4ÿÿÿP,T0ÿÿÿ;B<þûÿÿPÿÿÿ@,8ÿÿÿÿÿÿÀÑTÑ8ÿÿÿ;A@òûÿÿÿÿÿÑÀu4ÿÿÿH,Ñ8ÿÿÿ;Q@ÀéÂûÿÿfVÒùÿÿHÿÿÿPÿÿÿI(E@Mô%ÿÿÿäÿÿÿÿÿÿM;H<ìÿÿÿÑÀuEÑH,U;Q<ÀéFûÿÿ¶4ÿÿÿB,Dé"ûÿÿ4ÿÿÿTH,Ñé!ÿÿÿEMÐTA,ÐÿÿÿÿÿÿEÌ;A<þÿÿPÿÿÿÿÿÿÿÿÿI,ÀMÔwÿÿÿMÔ;H@ùÿÿÿÿÿÑÀuEÐÑH,UÔ;Q@öøÿÿéLùÿÿEH,ÑÿÿÿÿÿÿM;H<ÿÿÿPÿÿÿÿÿÿÿÿÿI,ÀMíÿÿÿM;H@RúÿÿÿÿÿÑÀuEÑH,U;Q@Àé(úÿÿUðÒÚEÀtU\ÿÿÿB\;A\ê	\ÿÿÿ`ÿÿÿB\D,`ÿÿÿÇD$|$½Pÿÿÿ|$ED$U$èTóÿÀÆ!üÿÿ½xÿÿÿÙùÿÿUÇxÿÿÿBÀÏùÿÿD$Hÿÿÿ$èóÿÀµùÿÿéÖûÿÿPÿÿÿÀËûÿÿD$Hÿÿÿ$è²¦óÿÀ¬ûÿÿé¬ûÿÿWÒvâ÷ÿÿHÿÿÿPÿÿÿI(EÜ@MØô%ÿÿÿ´EÜH,ÑÿÿÿÿÿÿMØ;H<¬ÿÿÿÑÀuEÜÑH,UØ;Q<÷ÿÿéh÷ÿÿEM¸TA,ÐÿÿÿÿÿÿE´;A<~ûÿÿPÿÿÿÿÿÿÿÿÿI,ÀM¼uE¸H,ÑÿÿÿÿÿÿM¼;H@cûÿÿÿÿÿÑÀuE¸ÑH,U¼;Q@Àé=ûÿÿWÒØöÿÿHÿÿÿPÿÿÿI(EÄ@MÀô%ÿÿÿ`ÿÿÿÿÿÿMÀ;H<ÌÿÿÿÑÀuEÄÑH,UÀ;Q<ÀéÃúÿÿE ÿÿÿ@R4ÐLÿÿÿé?òÿÿ`ÿÿÿÀóÿÿUBÀ*xÿÿÿ½xÿÿÿð½xÿÿÿt" ÿÿÿ½pÿÿÿÇxÿÿÿ9¹è~UBÀ¸òÿÿD$Hÿÿÿ$è|óÿÀòÿÿéqùÿÿvTE;B<¶½÷ÿÿPÿÿÿ@,E¤ÿÿÿÀ/TÑE¤;A@´÷ÿÿÿÿÿÑÀuE H,ÑU¤;Q@ÀÀ÷ÿÿ÷òÇEé{ôÿÿð+,ÿÿÿGéløÿÿ$ÿøÿÿWéøÿÿEH,ÑÿÿÿéüÿÿEÐH,ÑÿÿÿévûÿÿÿÿÿÿÿÿMØ;H<TýÿÿPÿÿÿÿÿÿÿÿÿI,ÀMàuEÜH,ÑÿÿÿÿÿÿMà;H@JôÿÿÿÿÿÑÀuEÜÑH,Uà;Q@ôÿÿé%ôÿÿÆéÆ÷ÿÿVÒt&ÿÿÿHÿÿÿPÿÿÿI(E¬@M¨ô%ÿÿÿE¬H,ÑÿÿÿÿÿÿM¨;H<,ÿÿÿÑÀuE¬ÑH,U¨;Q<Àé)öÿÿÇD$|$PÿÿÿD$UT$M$è¯óÿÀÆ|÷ÿÿUBÀ& ÿÿÿ@ÿÿÿÇÿÿÿÿüÑ)øGüÒ)ø+@ÿÿÿø ÿÿÿø\ÿÿÿw+@ÿÿÿüA\L QG89Âð)ù+DÿÿÿQÏE¸«ªªª÷âÁêRÁâT8ë)Eð ÿÿÿFÆ0+DÿÿÿE09ÖôtE ÿÿÿDÿÿÿÇFÿÿÿÿôÏ)ðFôÉt¸½Dÿÿÿ)È+DÿÿÿëÇEðé\óÿÿPÿÿÿð+,ÿÿÿFBFÇÿÿÿÿéiõÿÿ½Pÿÿÿ1É1ö¸ÿÿÿÿWé#õÿÿU B,Déôÿÿø@ÿÿÿ+@ÿÿÿ)ÐéÍþÿÿEÄH,Ñÿÿÿéûÿÿÿÿÿéþýÿÿ½xÿÿÿüÿÿÇD$ÇD$ÇD$ÇD$ÇD$Hÿÿÿ$è6ªóÿÇD$ÇD$Hÿÿÿ$èh}óÿéÕûÿÿPÿÿÿÿÿÿÿÿÿI,ÀMÈuEÄH,ÑÿÿÿÿÿÿMÈ;H@áõÿÿÿÿÿÑÀuEÄÑH,UÈ;Q@Àé»õÿÿ@éÜôÿÿE TH,ÑéÆûÿÿUBÀÄÆþÿD$½Hÿÿÿ<$è´óÿÄüð[^_]ÃD$Hÿÿÿ$èµóÿÀ¯ôÿÿ½PÿÿÿÀKïÿÿD$Hÿÿÿ$è«wóÿÀ1ïÿÿéôÿÿfMÉvt
> ÿÿÿ@hUBÀQUÒ>}öörUìÐ}Etÿÿÿdÿÿÿt  ÿÿÿ;ÔvÔ ÿÿÿÐhÿÿÿ1öÀõóÿÿ½ ÿÿÿhÿÿÿ;ÜvÜ ÿÿÿ1öhÿÿÿØéÂóÿÿ´&½ ÿÿÿ¿è½pÿÿÿéÑýÿÿPÿÿÿÿÿÿÿÿÿI,ÀM°uE¬H,ÑÿÿÿÿÿÿM°;H@ëñÿÿÿÿÿÑÀuE¬ÑH,U°;Q@ÀéÁñÿÿD$Hÿÿÿ$èMvóÿÀÀûÿÿé"óÿÿÇ|ÿÿÿféqùÿÿUìéÖþÿÿD$Hÿÿÿ$èõóÿÀþÿÿéêòÿÿD$Hÿÿÿ$èÖóÿÀÐòÿÿéÝýÿÿUìMÐ+AéþÿÿD$Hÿÿÿ$è§óÿÀ¼øÿÿéòÿÿD$Hÿÿÿ$è¨uóÿÀëÿÿé}òÿÿÇD$|$PÿÿÿD$UT$M$èóÿÀÆPòÿÿ}ìééýÿÿUåWVSì,EMèãµóÿÃ$q@QEèööVuvuìU$èÖóÿMuIV$~ Eà1ÀMäñÑúÿÀè!ÁÿÿÛþuðM1ÀÑúÿÀ1öè!ÁÿÿtuÈþ)ðùÒ	ÐF$Étð)ÈþÒ	ÐA EUä9UàÇ@$ÿÿÿÿÇ@ ÿÿÿÿKMQÒt
>öEß1ööEöE´&u
UÀöEt=UBÀED$UìT$M$è¢óÿUBhhÀðUìÀmUìBèÀBt1UìÀlÄ,ð[^_]ÃfER@ÂUìé þÿÿt&BÀuÈT$M$è¶óÿÀtÂöu¾Æëº¶Eèu>ÖAööuÖq,t$|$Uè$è@róÿMöEÇAÆãþÿÿ1öÄ,ð[^_]ÃfUðÒMðL$ut$Eè$èH¥óÿéþÿÿ´&ÉtPUBøÿv*ÂE)ÊQp1Àúÿt¸)ÐUD2EÊ+UP1Àúÿt¸)ÐAuVúÿFMð)ÐDðFV$~ é©ýÿÿ´&M1ÀQúÿtuDx ÿt$è"óÿUBéÐýÿÿvx$ÿuä@´&ëàD$Mè$èóÿÀÞýÿÿ´&¾ÿÿé:þÿÿD$Mè$èëóÿÀùýÿÿëÝt&UuMðB+UTøVUBÖÇÿÿÿÿR$~ éêüÿÿÈu+EÇAÿÿÿÿÀFéÞþÿÿ¶D$Mè$èqóÿÀ^ýÿÿélÿÿÿD$Mè$èqóÿÀ|ýÿÿéPÿÿÿD$Mè$èEóÿÀ}ýÿÿé4ÿÿÿ¶¿UåWVSìLMEèÓ±óÿÃmI@y@tEÄMÌÿÿUÈMUÈ1ÒÀxMÈqöu
>ëf6öt9~´&uîÒt&+öúUÌ1ÀÉt'EÈPööîUÌEØEØMÜMÉt}VÒ²D$EÀ(D$MAD$EÄ$ÿÒÀÆt>E»ÿ0þÿ@EÐM$èvóÿUÐ|$T$D$ùÆþÿD$MÄ$èâóÿÄLð[^_]Ãt&VÒt9D$EÀ(D$MAD$EÄ$ÿÒÀÆtÅU»óÆþÿRUÐëf1öÄLð[^_]Ãt&réæþÿÿBUÌé
>ÿÿÿT$EÄ$è|óÿÀ¾þÿÿ¾ÿÿéhÿÿÿD$MÄ$è{oóÿÀuãEÈékþÿÿUåWVSì<EUèó¯óÿÃ4k@zUEÜEO\fHÀMàÀYEÇEðÒMàEðD$ EÇD$L$L$MÀ(D$AT$ÇD$D$EÜ$ètóÿÀÆtRUÀ
EM·PÐà¿öfAuâ?fQUB0¨tàþB0BÀ|Ä<ð[^_]ÃfUà;Uðw0Gp@1öÿtMEÇD$L$$è=óÿÆéxÿÿÿfE¾õÿÿÀfÿÿÿW|úÿtHET$ÇD$À($èâyóÿGlëMÜD$$èÝóÿÀmÿÿÿ¾ÿÿébÿÿÿ¶Uàt&ë®¶MÜD$$è¥óÿÀþÿÿëÇ´&MÜD$$è¥móÿÀÜþÿÿë§ë
UåWV1öSìL}è®óÿÃUiÒEØUÔtEÔpUfO@ÀöN8ÉEØpÒthVxúÿt`|Àt@<Àtø%=t=D PMèUè@ÒEìuèt!EØL$$è«óÿÇEÜÀEà«F@Àt
>öGôÇEÜV\EðD$ G(MÔD$ÇD$T$T$GD$ÇD$D$EØ$è
óÿÀEàÎFtG;Fv8ÒIFÒt'T$UØ$èóÿÀtéáÇEÜÇEàMÀõEÜÀtfOEàÀuUfgùjMfg¿fÇGA0¨t
àþA0AÀulEàÄL[^_]ÃUÔÇD$|$$èóÿÇEÜÀEàêþÿÿéxÿÿÿfUÔw$è¶óÿMØt$$D$ÇþÿD$è)óÿéFÿÿÿD$EØ$è5óÿÀtt&ÇEàÿÿépÿÿÿt&MØD$$è
óÿÀÔýÿÿë×´&D$EØ$è
kóÿÀôþÿÿë·EØT$$èôjóÿÀu¤G;Fw	féþÿÿéþÿÿt&¼'UåWVSì,uEèS«óÿÃfV8@ÒEàÍU1ÒÀåMAÀEðuë/´&@À9pfuîö°uå@Eð¶Ò¼UðÒÀ£ML$E$EàèüÿÿuðöÇt(U1ÉÀUðBøtKèBÉÊÄ,ø[^_]ÃvÇEðë´&UT$M1Ò$è4üÿÿÄ,[^Çø_]Ã°ë²EÀôöÄóFLÀèF@ÀøvMU1ÒÀ5Myÿt F@9Guët&9Gt&t?ÿfuîÒt& ÿEðD$Uà$è<lóÿÀÇ!ÿÿÿF\ÇD$ÇD$ÇD$D$t$Eð$èôóÿÀÇ«ÇD$Eð$èÇóÿF8ÀËþÿÿÇEð1Òéwþÿÿf¨ÿÿÿ¿é£þÿÿFLÀMÀuzMàôÇD$T$ÇD$àøÀ÷ÐàD$ÇD$$è²¥óÿÇUÀàÿuaUðéðýÿÿL$Uà$èøóÿÀþÿÿ¿ÿÿéþÿÿD$Eà$è÷góÿÀuãUð1ÿÀu¨écÿÿÿ´&j¿éÝýÿÿ4ÇþÿD$Eà$èyóÿEðhé¼ýÿÿD$Mà$ègóÿÀuEéþüÿÿT$Eà$èaóÿÀ-ýÿÿédÿÿÿD$Mà$èegóÿÀMÿÿÿEéIýÿÿD$Mà$è$óÿÀ	ÿÿÿé'ÿÿÿD$Mà$è(góÿÀÿÿÿEéªýÿÿT$Eà$èçóÿÀÉýÿÿéêþÿÿUåWVSìLU}Mèp§óÿÃ±bGUÜê(ÉEØBUÔEÄEèu±ö°UÒ»WUÈUØtpNyMàuìôÇç0EÈUàJ(ºùvt&ÒÊ9Êr÷iÀý3EÄ!Ð9ÈrÑê!ÐÿMàQ4kÀ4EðÀMÔ·A¨´UðÀÝ1öÄLð[^_]ÃvUëvÂBÀu÷GEÈ@TÀ)ÿÿÿEÔpöt1RUÌUØBUÐòööuEÐòP,9UÌîþÿÿUEèL$T$MD$<$L$è~óÿÀÆ¨=íÿÿt!<$èuóÿD$\ÇþÿD$EØ$èìóÿMÜðU
>ÄL[^_]Ã¶<$¾
è7óÿD$&þÿD$UØ$è®óÿÄLð[^_]ÃEðD$EìD$UÄ<$T$èfóÿÀÆ¶þÿÿÄLð[^_]Ã´&ED$UÜ<$T$è¶óÿÀÆt¢<$è¸óÿD$ÇþÿD$MØ$è/óÿED$U<$D$èwóÿMÇé[ÿÿÿt&UðÈMÔBfAé9þÿÿfEÈ+FéÈýÿÿt&MàVQ4éôýÿÿD$EØ$èßóÿÀþÿÿ¾ÿÿéÿþÿÿD$EØ$èÞcóÿÀÏýÿÿëÝUåW1ÿV¾dSEìì,èO¤óÿÃ_Eàë7t&è¿óÿÇ$èUjóÿøtøtøt&tøvuîvtÇD$Uà$è¿uóÿÀu·ÿuEìUiEðèBÄ,[^_]Ã©ÇþÿD$ç
þÿ|$D$E$èióÿ<$èÑióÿD$U$èraóÿÄ,[^_]ÃUåWVSìUèv£óÿÃ·^Òt
>öB0óÈÇþÿ1ÿ¾dEðvEð$èióÿD$E$èzcóÿÀt4è±óÿÇ$èGióÿøtøtø¶tøvuîvu®ÿt&unEÀtZ¾dë8¶è_óÿÇ$èõhóÿøtøtøt&tøvuîvtED$E$è0qóÿÀu¸ÿuÄø[^_]Ãf<$è¤hóÿÄ[^Çø_]Ãt&E$D$¶ÇþÿD$è;óÿéïþÿÿUåSè>¢óÿÃ]ìÇ$Tè®cóÿÀ~øtkÀ2Ä[]Ã´&Ä¸[]ÃU¸ûÿÿÿå]Ã¶UºþÿÿÿåSì$èÖ¡óÿÃ]}}Ä$Ð[]ÃvtºûÿÿÿëëEøD$E$è¨óÿºúÿÿÿÀuÐEôD$ED$Eø$èÖóÿ1ÒÀu±EôD$ED$Eø$èóÿ1Òë´&UåSèN¡óÿÃ\ì4EøD$E$è8óÿºúÿÿÿÀtÄ4Ð[]Ãv÷E¸ue}À÷ÐÀD$EôD$EÇEôÇD$D$ED$Eø$èAóÿºýÿÿÿÀuUôë´&U¸þÿÿÿåì(]ôè¤ óÿÃå[}uø}ü}]ôuø}üì]Ã¶t¸ûÿÿÿëä´&EðD$E$èbóÿÀujEð@ÒE$èóÿuð@ÇÒu+ëEt&B8A8B8T$4$èµóÿuð@ÒtJ4ÉuÕB8DëÐf1ÀéVÿÿÿÇD$4$ÿÀuÿtß¸ýÿÿÿfé0ÿÿÿR¸úÿÿÿÒjÿÿÿvéÿÿÿvUºþÿÿÿåì(]øèóÿÃÕZ}uü}]øÐuüì]Ãftºûÿÿÿëé´&Euôt$$èZóÿ1ÒÀtÊÇD$4$è$óÿºýÿÿÿÀu±EôUÇD$ÇD$.$T$ÿ´ÀuEôD$E$èróÿÀtEôÇD$$ÿºýÿÿÿéVÿÿÿEô@D1ÒÇ@é6ÿÿÿt&U1Éåì(uøu]ô}ü}èóÿÃÜY@Àt]ôÈuø}üì]Ãv|$ÇD$ÇD$4$èpyóÿÀÁuÌ@ÀÇBB4t'@EðÀ4B8Eð@@B8ëEðÀ4DëÚUºþÿÿÿåì(uøu]ôèîóÿÃ/Y}üöy]ôÐuø}üì]Ãv÷Æÿÿÿ¯ºûÿÿÿuáEðD$E$èµóÿÀtºúÿÿÿëÄEèD$ED$Eð$èáóÿºüÿÿÿÀu¢MðBööt^}èGlºføyÿÿÿøºhkÿÿÿæ@ø¶upEìÇD$D$$èSmóÿÀtºýÿÿÿé/ÿÿÿz,}èvëEì|$D$Eð$èÄyóÿÀuÑEìÇD$$ÿPlÀu¼Eì1ÒÇ@éäþÿÿøÿÿÿt&ëøvýþÿÿfémÿÿÿt&¼'Uºþÿÿÿåì(]øèóÿÃÅW}uü}]øÐuüì]ÃftºûÿÿÿëéEôD$E$èQóÿÀtºúÿÿÿëÌEìD$ED$Eô$è}óÿºüÿÿÿÀuªMôBöötYuìFlºføtøtøu¨EðÇD$D$$èlóÿÀuEðt$D$Eô$èxóÿÀtºýÿÿÿé<ÿÿÿr,uìt&ëUEðÂT$$ÿP|ÀuÓEð1ÒÇFlÇ@éÿÿÿë
Uºþÿÿÿåì(]øèTóÿÃV}uü}]øÐuüì]ÃftºûÿÿÿëéEôD$E$è!óÿÀtºúÿÿÿëÌEìD$ED$Eô$èMóÿºüÿÿÿÀuªMôBöötZuìFlºføtøºhwÿÿÿøtøt&tøvuEðÇD$D$$èÃjóÿÀtºýÿÿÿé;ÿÿÿr,uìvëEðt$D$Eô$è4wóÿÀuÑEð$ÿPhÀuÃEð1ÒÇ@é÷þÿÿt&Uåì(uøu]ôè#óÿÃdU}üöt
÷Æ&ºûÿÿÿtEðD$E$èüóÿÀtºúÿÿÿ]ôÐuø}üì]ÃEèD$ED$Eð$èóÿºüÿÿÿÀuÏEìD$EðÇD$$èØióÿºýÿÿÿÀu¬EðBöötVMè}ì;OuAlºfø{ÿÿÿy\ºhlÿÿÿø^ÿÿÿæþÀ1ÒàýÀAlÇGéAÿÿÿJ,Mèë¥Uåì(]øèóÿÃZT÷Eÿÿßguütºûÿÿÿ]øÐuüì]Ã´&uæ þ t×MºþÿÿÿÉxÐEôD$E$èÅóÿºúÿÿÿÀuµEìD$ED$Eô$èóóÿÀt5öºüÿÿÿuEðD$EôÇD$$è¬hóÿÀ©ºýÿÿÿécÿÿÿöºøÿÿÿ´&OÿÿÿMôBöötnuìFløtøºf!ÿÿÿèºhÿÿÿEðÇD$D$$è3hóÿÀuEðt$D$Eô$è¹tóÿÀmÿÿÿÇFl1ÒéÌþÿÿr,uìëEðD$Eô$èóÿÀ=ÿÿÿEð@D$ED$Eô$èUóÿEð1Ò@Ç@lézþÿÿUåVSEèjóÿÃ«R³püÿÿÒt#9Huëe´&9Ht8Òuî¸[^]Ãt&8Ét?<<<É8t*8<²<E1À[^]Ã<FëÈ8Fë×UåSEè»óÿÃüQUÇ8HpüÿÿQ<8A1À[]Ã¶¼'UåVSEèjóÿÃ«Q³püÿÿ9Htt&89Huò8Ét <<<1À[^]Ã¶<F1À[^]Ãë
UåEW}úAööuúQ,zp¹ 1Àó«_]Ã´&¼'UåìU]ôuø}üèóÿÃÛP@0Àu|}¹ uÇpÆó¥UBUðUBUôUUøU@0Àu1À]ôuø}üì]Ãt&D$$è`|óÿÀtÝ¸ÿÿëØD$$èhTóÿÀpÿÿÿëâfUåSì$EèèóÿÃ)PD$EøD$EÀD$E$ècóÿÄ$[]ÃUåWVìEMPqUìuðòuì9òvòÒ9Eôt9¶0¶ñ8ÁEëu9Jÿ1ÒëfEôé¶t¶DÂEëð:EëuÉußUì+UðÄ^_Ð]Ã¶EëñÄ¶Ñ^_)ÂÐ]Ãt&UåWVìEUHrMðuôñuð9ñvñÉ82t%¶º:tëZt&Â¶Dÿ:Dÿu:9ÑuîEô9Eðruð9uôUôEôÄ^_]ÃfMðÁMôEôÄ^_]Ãt&UôEôÄ^_]ÃÇEôëÆfUåìHM]ôuøu}ü}¶AèfóÿÃ§N<w}<xº@öÄ	EB·
>¶BÑ$ø1ÀU;³àûÿÿÀè!ÆE t$D$AD$AT$<$D$ED$èhóÿëf<tAD$G$èóÿ]ôuø}üì]Ãt&<uØEÀxº@öÄuàøÒâúÂ EB·
>¶BJ$øIÿÿÿÇEìBEØ·U<$EÜEØT$D$ÿÖU 1ÀépÿÿÿfàøÒâúÂ éäþÿÿt&E Ç1ÀéFÿÿÿÇEìBë¢UåWVSèìóÿÃ-Mìu4$è}óÿ¶~L¶FO¶NM¶VNFLø¶~PFO¶FSVM¶VRNN¶NQFPø¶~TFS¶FWVQ¶VVNR¶NUFTø¶~XFW¶F[VU¶VZNV¶NYFXø¶¾ÌF[¶ÏVY¶ÎNZ¶ÍÌøÏ1ÀÍÎÄ[^_]Ãö¼'UåSì$EèóÿÃILM1ÀöBt1y	t8ÇD$L$D$ED$ED$E$èÉóÿÄ$[]Ã´&$èDbóÿÄ$[]ÃfUåSì$EèóÿÃÙKM1ÀöBt1y	t8ÇD$L$D$ED$ED$E$èYóÿÄ$[]Ã´&$èÔaóÿÄ$[]ÃUåWVSìEè&óÿÃgK@EðÂ,ÀºMMìëvMBH;AHuUìUìÜ@ÒuàUìMBH;AH¶UB$À2Eì°èöué¸;Etkvö¶¢¾Ètæ¾ÌG;EuÓFÀÀö³PÒ¨U4$T$è=aóÿÀG;EuFÀt)öt @ÀtU4$T$èaóÿÀgÿÿÿfvMöOeÿÿÿ´&UB$ÀuIEìØÀEìtM@H;AHÿþÿÿUð,ÀuR1ÀÄ[^_]ÃM·EfGOéúþÿÿMðD$$èÒuóÿÀt¤ë0MðD$$èÝMóÿÀ·þÿÿë´&D$$è uóÿÀt¸ÿÿëD$$è©MóÿÀ2þÿÿëãvUåWVSìEè&óÿÃgI@EðÂ,À4}ë¶MBH;AHu×Ü@ÒuäUGH;BH¨MA$ÀÅ·èöuévöÌU9PuçFÀt ötHÉtT$4$èp_óÿÀuÀM¾A$ÀuMö¿ØtMð,ÀuiE01ÀÄ[^_]ÃvÿtÝUGH;BHXÿÿÿ1öëÊM1öA$Àt³D$Eð$èQtóÿÀt ¸ÿÿë·D$Eð$èWLóÿÀ$ÿÿÿëàD$$è!tóÿÀtëÎD$$è/LóÿÀ¸þÿÿë¸ö¼'UåWVSìEè¦óÿÃçG@EìÂ,ÀMMèëvMBH;AHuUèUèÜ@ÒuàUèMÇEðBH;AH¸´&UB$ÀÛEè°èöuëkvvöta¾ÌU9Wuë·G;EuâFÀt#öt@ÀtT$4$èÓ]óÿÀu»vEÀtqÌvEðöu¦´&MA$ÀuuUèØÒUètMBH;AHOÿÿÿUì,Àubu1Àöt
>EðM1ÀÄ[^_]Ã´&§ÌþëMìD$$è¬JóÿÀÿÿÿ¸ÿÿëÊD$Eì$ènróÿÀtÿÿÿëàD$$èXróÿÀtëÎ¶D$$è`JóÿÀiþÿÿë²v¼'UåWVSì\EMèÓóÿÃFIPÉEÐMÜUØt
yÀ÷Ð!ÁMÜUØ,À;MÐMÔëvMÐBH;AHuUÔUÔÜ@ÒuàUÔMÐÇEàBH;AHÔ´&UÐB$ÀÂEÔ°èöuévöty¾Èftî¾ÌU9WuàFÀt!öt@ÀtT$4$èá[óÿÀu¹EÜÀtMÜ;NtÇEà·G;EEÀtvEöGuUÐB$ÀEÔØÀEÔtMÐ@H;AH3ÿÿÿUØ,À2}àÿ©MQÒ@°pöö-u|Àt@<Àt	öøue}À÷Ð!EÇD$(EÇD$ D$$ML$ED$MEìÇD$ÇD$D$L$T$EÐ$èºGóÿÄ\[^_]Ã1ÀÄ\[^_]Ãt&U·Mf)OWémþÿÿD$MØ$èÒoóÿÀäþÿÿë8t&D$MØ$èÕGóÿÀ'þÿÿë´&D$$è¸GóÿÀ±ýÿÿ¸ÿÿët&D$$èxoóÿÀºþÿÿëÞfUåWVSìLEMèóÿÃTCIPÉEÔMÜUØt
yÀ÷Ð!ÁMÜUØ,À}Ôë¶MÔBH;AHu×Ü@ÒuäUÔGHÇEà;BHÅ¶MÔA$À·èöuë~¶vötq¾ÈftîÌU9PuàVÒt)öt RÒtM4$L$è&YóÿÀu¶ÌUPEÜÀt£MÜ;NtvÇEàöut&UÔB$ÀÝ¿ØÿtUÔGH;BHAÿÿÿMØ,À}àÿEPÒÁ@°pötö-uv|Àt@<Àt	öøu\ÇD$(ÇD$$ÇD$ ÇD$ED$MEìÇD$ÇD$D$L$T$EÔ$èEóÿÄL[^_]Ã1ÀÄL[^_]ÃD$MØ$èJmóÿÀÿÿÿë8t&D$EØ$èMEóÿÀWþÿÿë´&D$$è0EóÿÀéýÿÿ¸ÿÿë t&D$$èðlóÿÀÜþÿÿëÞv¼'UåWVSì\EMèóÿÃÄ@IPÉEÐMÜUØt
yÀ÷Ð!ÁMÜUØ,À+MÐMÔëvMÐBH;AHuUÔUÔÜ@ÒuàUÔMÐÇEàBH;AHì´&UÐB$À²EÔ°èöuévö¾È¶tæ¾ÌU9WuØ·W·Â;ErÌ;ut/FÀt(öt@ÀtM4$L$èuVóÿÀu·W·M
>fGEÜÀtEÜ;FzÿÿÿvÇEàösÿÿÿUÐB$ÀàEÔØÀEÔtMÐ@H;AHÿÿÿUØ,À
>}àÿMQÒ@°pöt~ö-uu|Àt@<Àt	öøu[ÇD$(ED$$MÇD$ÇD$L$ EÇD$ÇD$T$D$EìD$UÐ$è`BóÿÄ\[^_]Ã1ÀÄ\[^_]ÃD$MØ$èjóÿÀ	ÿÿÿë5D$MØ$èBóÿÀ7þÿÿë´&D$$èxBóÿÀÁýÿÿ¸ÿÿë£t&D$$è8jóÿÀâþÿÿëÞfUåWVSìEèÖóÿÃ>@EðÂ,ÀMMìëMBH;AHuUìUìÜ@ÒuàUìMBH;AHÿUB$À«Eì°èöuéÁvöµ¾ÌU9Wuç·G;EuÞÀtØÌ·@;EuÉFÀt öt@ÀtT$4$èúSóÿÀu¢MA$À¤$è®bóÿÀÆud·UÇfWUB$ÀUÿÿÿMðD$$èAóÿÀEì°èöKÿÿÿMA$Àu-UìØÒUìòþÿÿ1öUð,ÀuWÄð[^_]ÃD$Eð$èhóÿÀtÀë1t&D$Eð$èhóÿÀEÿÿÿëD$$è@óÿÀhþÿÿ¾ÿÿë©D$$èThóÿÀtëçfUåWVSì\EMèóóÿÃ4<IPÉEÌMØUÔt
yÀ÷Ð!ÁMØUÔ,ÀõMÌMÐëvMÌBH;AHuUÐUÐÜ@ÒuàUÐMÌÇEÜÇEàBH;AHEðEÈfUÌB$ÀEÐ¸èÿué(ÿ·ÌU9Vuç·F;EuÞGÀt'öt@ÀtT$<$è÷QóÿÀu·´&ÀuªMÌA$À·ÌUÈMÇEðT$L$<$D$è`óÿÀEàÄMðEÌB·EfBEÌ@ÀöÌ\EØ·UÀfVÿÿÿMØ;OõþÿÿUÌÇEÜB$ÀîþÿÿMÔD$$è>óÿÀEÐ¸èÿãþÿÿUÌB$ÀEÐØÀEÐtMÌ@H;AHþÿÿÇEàUÔ,À5}Üÿ£MQÒ@°pöö-uy|Àt@<Àt	öøu_EMT$UÌÇD$D$(EL$$MÇD$ÇD$D$ EL$$D$EèD$è/=óÿÀt
>UàÒuEàEàÄ\[^_]ÃÌ¦ÌþéþÿÿMÔD$$èDeóÿÀæþÿÿëD¶EÀÄéTþÿÿD$EÔ$èeóÿÀäýÿÿëD$$è=óÿÀ÷üÿÿÇEàÿÿéyÿÿÿD$$èÞdóÿÀ·þÿÿëÞUåWVì}ÌEôAUðÀuBAA(ÇAÇA$ÀóA,º@ÇÇ@Eô0xöÄuàøÒâúÂ ö,ÇEìuEð@ÀEì)Ö1Òð÷uìÇÄÇÈÇÌö,@öfÀu¿ÈtUôözt,ÇÌö,u#Eô÷xPt
>ÇÌÄ1À^_]Ã¿ÈtãEô÷xPuÔëÜ¶Q4ÀA0ÐQ(é÷þÿÿfUåEÌEÌ·ÀfÀÄÄÌÌ1À]ÃUåì8}ü}Eð]ôuøD$ÇD$GèÎ{óÿÃ7D$ED$@ $è5`óÿÀÆu"Uðfzu)GT$D$@ $è
nóÿð]ôuø}üì]Ãf¾ìÿÿëÐö¼'UåWVSìLEMèS{óÿÃ6ÌP EÔMÐUØÒ°EÐ}ÇD$ÀD$GD$ÌÀD$EØ$è_óÿÀu[UÐz¶WúEBý<ªútE·}àEà}UMÐ}ØBD$A<$D$è+móÿUÐÇBÄL[^_]Ãt&·GfÑè·ÀEàë³}ÈÀD$ÇD$GD$ÈÀD$EØ$èÕ^óÿÀu°UÐ·RfÒ·òfUÜÌMxxÂàâUðEÄë7´&UÄÒtI·uÜ¸6·L f;ÅfmÜ¸MðÉtÉ·uÜ¸<6·L@ëÎ¶·uÜ¸6·Lëµt&MÔ1ö·GÇEàxè·ÀEÈÑâáMäv}äð¹@uúÉáúÁ ·ÀA·|EÈUàÆÀ9ÆuÈéeþÿÿv}àéWþÿÿt&1öMÐ}ÔIx·AMÌèfEÞÐ%Eè1ÀyÇEàÀâEìë2´&¨6¹$·t f;4èýÿÿfEÜ·uÜEè¹@ÀuúÉáúÁ }ì>·}ÞAMÌ·|Uàf9}Ü¡ýÿÿMÌxxöÄzÿÿÿ6¹D·t@ëv6¹·tékÿÿÿ¶UåWVÖSìLEÔMÔÌèxóÿÃL3,EØÑáEØfÇEÞÇEà@À-öÏUØRUÐMðMÌëk¶uöÅEÔ¹@ÌrxöÄuàøÉáúÁ 1À·R~ÀÐA·0|x·EÞUØøfBEØUÐ·xf;zrBÀMÔ±Ì;FtÇFUÔEðVx Ò5MÔAT$<$D$è{ióÿÇFÀÄL[^_]ÃEÔ¸ÈÀâ¶ÀÀúfEÞEØÒÂUà@ÀÓþÿÿUÔÉx uT@öôuHlÀt>EØÇD$ÀD$MàL$UØBÇD$D$MÔ$èOóÿÀbÿÿÿEØÇD$ÀD$UÔBD$EØ<$ÀD$è ZóÿÀ,ÿÿÿEàMØA$é/þÿÿ¶MØ·EÞQfAUÐé$þÿÿfÄL1À[^_]Ã¶EÔö,uTÂ@öôuDlÀt:FD$ÇD$MàL$EðÇD$$D$èINóÿÀþÿÿt&FD$ÇD$UÔBD$MÌ<$L$èÔYóÿÀ`þÿÿEðUØFEàJfÇBF$MÐéÕýÿÿ¸óÿÿé6þÿÿ¶UåWÇVSì<,ÌèûtóÿÃ<0ÑáEÔXEÔfÇEÚÇEÜ@ÀoEðEÐëVt&UÔ¹@f+EÚfBÌxröÄuàøÉáúÁ 1À·R~ÀÐA·0|ygUÔ·BfÀu£B@Àï·Ì;FtÇFEðV@ ÒEàt9GT$D$Eà$èfóÿÇFÀtÄ<[^_]ÃÄ<1À[^_]Ã¶ö,(FD$ÇD$GD$EÐD$Uà$èGXóÿÀu¯EðUÔFEÜF$B·@fÀfB-ÿÿÿé×þÿÿ´&1À¿ÈÀâÀúfEÚEÔÒÂUÜ@ÀþÿÿÉp uQ@öôuElÀt;EÔÇD$ÀD$UÜT$UÔBÇD$<$D$èÐKóÿÀôþÿÿEÔÇD$ÀD$GD$EÔ4$ÀD$è]WóÿÀÁþÿÿUÜEÔP$éöýÿÿ@öôÆþÿÿlÀ¸þÿÿFD$ÇD$UÜT$EðÇD$<$D$è:KóÿÀþÿÿÄ<[^_]Ã¸óÿÿéKþÿÿvUåìh]ôèIróÿÃ-uøÆ}üèýÿÿÀÂuÌHE°yt]ôÐuø}üì]Ã¿BxöÄuàøÿçúÇ"E°·@<G·Á¶A$øu¶U°T$D$A4$D$èRóÿÀÂuU°U¼T$UØT$ÇD$ÇD$$ÿ Âéaÿÿÿ´&Uåì(}ü}]ôuøè`qóÿÃ¡,·Ì~$t	ö,t1À]ôuø}üì]Ã´&@öôuÜlÒtÒ~NFD$Ò÷ÒâÇD$ÇD$L$T$<$è§IóÿÀuÇF$ë´&¼'UåVSìuè·póÿÃø+ÌÉPGØûÿÿ}ôÐÀûÿÿøÔ|ûÿÿüØüÿÿÜ üÿÿàûÿÿèøûÿÿìtc¸óûÿüÿ°üÿÿXëûÿ¤ýÿÿ lÿÿÿ$HÓûÿ(1ÀÄ[^]Ã¶¸óûÿüÿøüÿXëûÿ¸âûÿ ýûÿ$HÓûÿ(Ä1À[^]ÃvÌD$ÇD$ÐÇD$$èJJóÿÀþÿÿédÿÿÿUåWVSìlEÀU¼UÀèoóÿÃO*ÇEðHÌE°EÐÉU¬UÌMÄ¬U¬E¬r·@·NfEÖf9ÈfMØ@·MÖE°M´xÈÀL MàLD@×EÈ·EÖâçMÜU¨fEÚë=´&E¨À5Uà¸ ·
>·UÚPf;u/fEÚ·MÚf9MØ2ÿtÆUÈ¸@·
>·UÚPf;tÑBþ9E´+U´ÐÁèÐÇÑïfÿj·uÖEðE¸fuÔë.v}ðþ~U¬wÿfÑî·BÀfEÔfö7÷·UÔþfÑîM¬rU¸fA·ÀÀT$M°QD$T$U¬BD$M¼L$UÀBD$M°$èEZóÿÀÁwÿÿÿÄlÈ[^_]Ãt&ÉºD·t@Ðf;4G}ÌfGU°¹@}¬xwöÄuàøÉáúÁ }¬1À~·WÀÐA·0|xLEðD$àûÿÿD$UÌ·BÀD$BD$M¼L$uÀFD$}Ð<$èYóÿÀÁ<ÿÿÿEðÀ£uÌEÌV·x·R·ÏA9ÐÑuÀEÀ6ÌxE¬@u°öÆûþÿÿât&Éº$·t éñþÿÿt&EÜ·¸éÆýÿÿÉº·téËþÿÿ´&·ÑBþ9E´çýÿÿEðD$}ÄBÿD$t$|$E¼D$UÀBD$M°$è XóÿÀÁ[þÿÿ}ðQþÿÿ}}
>fCþÿÿf¹óÿÿÄlÈ[^_]Ã·MÖfMÔ}tâ·}ÔuÌf9}Úf~vÑEÀUÀÌE°U¬ëvfEÔ·uÔMÌf9uÚfqv¢U°¹@}¬xwöÄuàøÉáúÁ }¬1À~·WÀÐA·0|x£·EÚf9EÔMÿÿÿ1ÉÄlÈ[^_]ÃEÀuÀ¶Ìxu¬~¾@öÄt41ÀÀE¤E¬·PE¤ÐF·8|
>ÿÿÿÄlÈ[^_]ÃàøöæúÆ ë¼·øfEÚú}´éIüÿÿ´&UåWVSìlE°U¬U°èNjóÿÃ%ºÌEÀM´H WÒtuu°FT$$D$è\óÿÇGÀEÔtQGÀuXEÔÀupwöuÇG$EèøvjEUÀD$ÒÇþÿD$B$è÷QóÿÆë7´&GÇEÔÀt¨GD$E°$èÜ0óÿÀtÆEÔÀtuÔÄlð[^_]Ã¶ÈþÿØÿàt&u°UìMÇD$U¨4$T$L$è[óÿÀÆu¶U°u¨M,t$L$ÇD$%øÀD$$è:óÿÀÆtgéqÿÿÿU°,%øÉÁMÐt&uEÐUM¬t$u°ÇD$ÇD$D$4$T$L$èe0óÿÀÆÿÿÿW,
>}AOG·BfGBGBGBGBG BG$9}ÄþÿÿfytPM°u°¹@ÌxröÄuàøÉáúÁ 1À·R~ÀÐA·0|mþÿÿE°èØòÿÿÆéaþÿÿu°,%øÀEÐéðþÿÿU°,%øÉÁMÐéÏþÿÿ´&U°,%øÉÁMÐé§þÿÿ´&u°,%øÀEÐéþÿÿÇEÐ1u°ö,iþÿÿU´B$ÀEðXþÿÿ¶Ì;FtÇFU°V@ ÒEØ`M°AT$D$EØ$èsYóÿÇFÀEà5Eàyøq}àõÿÿduàU°M°ÌUÜRH Òt*E°@T$$D$èYóÿUÜÇBÀtöuÆMÜAÀ±öuUÜBÀuÇB$GÇGÀ·öbýÿÿéüÿÿt&ÇEÐ2éÒþÿÿvfyvt?M°Ì¹@xröÄt@1À·R~ÀÐA·0|LüÿÿE°1ÒÇ$èíÿÿÆé7üÿÿ´&àøÉáúÁ ë°U°ö,uT@öôuFlÉt<FD$EðÇD$ÇD$ÇD$D$$è>óÿÀEànþÿÿvM°FD$ÇD$AD$EðD$EØ$è¡IóÿÀEà5þÿÿWMÀEðÇF$UÄFx¹@öÆuÐàøÉáúÁ uÄ~þÿÿ·FfÀfEºÿýÿÿâtU´B(;éýÿÿB,;FÝýÿÿMÄMÌMÄQÒ5EÄ@À»ýÿÿU´EèD$MÄuBU°L$MÀt$D$ÇD$B$D$èQóÿÀÆxýÿÿ}ènýÿÿf¢}
¶uÄ·FÁféUÌ·f;BofÇEÊë´&·UÊuÌ·Vf;DVäfEÊf9MÊrßéÔfÈÀD$E°$èè*óÿÀ3ýÿÿö@ýÿÿÆfé7ýÿÿM°GD$@$èx4óÿÀ*ýÿÿöÜùÿÿÆféÓùÿÿ1öéüÿÿ·uºU´î·ÆE¼EèM¼D$BfuÊU°uÄL$MÀD$Et$D$B$D$èÛOóÿÀÆAüÿÿ}èkþÿÿvtv·uºfuÊ1ÀU}èÀG(;G0G,ÂÇÇ@uÄ0·EÊfB·FfBGBGBGBG BG$BéîùÿÿffÇEÊë}tf}Êt&tU¼MÌ·DQüf;Qtéjÿÿÿ·UÊuÌ·DVüf;VTÿÿÿfmÊuãéHÿÿÿMÀ|$A$è°\óÿÀÆøÿÿW,ÐéNÿÿÿUåWVSì\E}èóaóÿÃ40ÌV EÈUÌP·@UÐfEÖGúøvOàÇþÿ|$D$F$èâIóÿÁt&uÈÌ¨t}Ð9~§uÈàþÌÄ\È[^_]Ã\ÈþÿØÿàt&EÐÀEðD$ÇD$Ç$E1ÒèÕöÿÿÀÁuEÀt}Ìr~rÿÿÿ}¿BxöÄÙ·BG·0¶B$ø<ÿÿÿBUé/ÿÿÿ´&MÐÉEðD$ÇD$Ç$écÿÿÿfEºÇ$èlèÿÿÀÁâþÿÿ}ö,ÒþÿÿÌEÐ9BÀ¹óÿÿé¶þÿÿ¶UÐÒt·EÖÀEÜEºÇ$èèÿÿÀÁþÿÿ}ö,uÖÌEÐ9BÕþÿÿuzxöÄý¨
·BÇEÄ ·tG UÜ}Äf;48téþÿÿUEðD$EÇD$$1ÒèAõÿÿÀÁ÷ýÿÿuÈV·Ff;BtPu}¾@ÌxzöÄuàøöæúÆ 1À·RÀÐF·8|þÿÿÇ$1ÒEèçÿÿÀÁ|ýÿÿéèýÿÿ´&Et&èóéÿÿÀÁ´&RýÿÿEö,BýÿÿÌuÐ9rpþÿÿzxöÄ3¨ª·Bº ·tG ·EÖBf;485þÿÿéðüÿÿEÐÀ0ýÿÿ·EÖÀEàt&Eè`éÿÿÀÁÆüÿÿ}ö,uâÌEÐ9BýÿÿuzxöÄ)¨i·BÇEÄ ·tG Uà}Äf;48téÖüÿÿt&EðD$E|$$é«üÿÿfEö,PUEðD$E|$$1Òè]óÿÿÀÁüÿÿÿ4uÈV·Ff;BtPu}¾@ÌxzöÄuàøöæúÆ 1À·RÀÐF·8|ªûÿÿEºÇ$èåÿÿÁéûÿÿ´&EÈ}ÇD$ÀD$GD$EÈÀD$EÌ$èAóÿÀÁMûÿÿö,éVÒ*T$UÈEìD$}·BD$BU|$D$B4$D$è{IóÿÀÁõúÿÿuìö*üÿÿu}ÈFD$GD$EÌ$è÷NóÿÀÁÁúÿÿUEèÇGD$ðÇD$$1ÒèÜñÿÿÁéúÿÿt&UÈ¹ëÿÿöÌ úÿÿEÈuÇD$}ÌÀD$F<$D$EÈÀD$èv@óÿÁéCúÿÿv·UÖf;VKúÿÿféPúÿÿvEt&è«æÿÿÀÁ´&
>úÿÿfétúÿÿvÇ$ºt&é]üÿÿvEð1ÒD$E|$$Eè
ñÿÿÀÁèùÿÿEðÀøúÿÿEÀtuÌBE¸xÒUE<$è
>ìÿÿÁéùÿÿvàøÿçúÇ"éúÿÿt&·BÇEÄ@·tG@éÚüÿÿv·BÇEÄ@·tG@éûÿÿv·BÇEÄ·tGéîúÿÿv·BÇEÄ·tGéüÿÿàûÿÿéËýÿÿuzxöÄÍûÿÿ·Bº@·tG@éÐûÿÿEðÀúÿÿéÆøÿÿ6ÇEØBxöÄEÀueÀ}ÀöæúÆ"uØ·BuØ4FE¸·u¸Æ¶F$øßþÿÿFuéëøÿÿ·Bº·tGéQûÿÿuÈV·~·R·ÏA9Ð{ùÿÿUÌpxöÄuB¨tM	º$·L f;DùÿÿuÈGUfFEÇ$èhêÿÿÁéá÷ÿÿ	ºD·L@ëÀ	º·Lë±fUåì}ü}]ôuøèPYóÿÃ·ÌV(F49ÂtT$@$èÎFóÿt$@$è½Fóÿ]ô1Àuø}üì]ÃfUåìhE]ôuø}üèîXóÿÃ/P E¼EUÀU¸ÌÇD$GD$BD$GD$EÀ$è0=óÿÀÆtð]ôuø}üì]Ã´&UÐ1ÀU¸U¸ÇÀørîET$UÀDD$EÀ<D$·GD$GD$BD$E¼$è>TóÿÀÆUBD$GD$EÀ$èJóÿÇGÀÆ]ÿÿÿU}ð,|$ÇD$ÇD$%øÒÂEìD$E¸T$UD$$èzóÿÀÆt0EÇD$$èQTóÿÀïþÿÿöçþÿÿÆvéÝþÿÿvEPÇD$|$BT$UD$T$U¼B$èr#óÿÆëfU1ÀåìH]øMUÜè1WóÿÃruüuÇÀørñEÇD$ÇD$L$EÜET$MôD$FMäD$$èDóÿ]øuüì]Ãt&UåWVSìEUè°VóÿÃñ²Ì|ÿÿÿÀEðßMðU ÇE UUEÌE°EUUEE°·@fE1ÒÈÇ$èÞÿÿÀE¨5U°|ÿÿÿ·JzfMx¸@öÅuÈàøÀàúÀ EÇE¤é´&º@·Etÿÿÿ1ÀÀtÿÿÿBU ·|öº@uáùÒâúÂ tÿÿÿmO·4E ÀEÂÀÀ Â{ÿÿÿtmE 9M¹·ÆE¶@$øAEE¬E¤Àt7·Gu)Æ9uIt$D$M$èx0óÿE)uuEu¬½{ÿÿÿtUMBüAüéMEºtÿÿÿÇE¤·0·G)ÂE+U·HEÊUè0èEE$À"U¬U1ÒMðfE¹Èt=·Ef;GsG|ÿÿÿU xÎævþÿÿÈàøÒâúÂ éfþÿÿM°·EÄf;Gr¹u$ö)M°·EfAM¨ÉU Mðé¸ýÿÿEp9u3½{ÿÿÿòtUMBüAüEéMPML$MAT$D$E$èÆ#óÿÀ¸UE+EM)uÐèñ0èEE$M¬ÀÞþÿÿUE MEUM¬
>f}uM}¨óÿÿuÇE¨Mð$è4óÿÀÂ
E¨ÀMúóÿÿÌÇtU¨vE¨Ä[^_]ÃfMU E}¨éÿÿ
>UMEusMð¹Èf}¶M°E¨fiÄ[^_]Ã¶U ÇE¨éÿÿúaþÿÿE¤+MÇE¨éÿÿÀMIþÿÿ·GM)ÁMé8þÿÿU}¨óÿÿÀÒÀòþÿÿéæþÿÿU°ÄèÀÄæþÿÿéÿÿÿUÌÇE¨Ä[^_]ÃÈèïÜÿÿ=óÿÿ¯þÿÿÀfâþÿÿE¨E¨Ä[^_]ÃUMÇE¨éÿÿUU éýÿÿU MÇE¨éÿÿé}ýÿÿEðD$ÇD$M$L$èg2óÿÀE¨xþÿÿEðU¸T$UÔÇD$ÇD$T$$ÿ ÀE¨ôýÿÿé¼úÿÿÀfÞýÿÿE°ÇE¨fhEð¸ÈþÿÿU°ÇE¨ªÄéýýÿÿt&UåWVSìEèóPóÿÃ4u¸ÌE
>}M¸ME¬yMD8ü¹ÈEØvðñÁèáÿàEÔ1ÀùÀEÌÇEÀÇEÄGüu¬}ØEè1ÀùÀEÐEèuì}ðu°ÇE¤ÇE´ÇE¼EM¸@u·IvfM xuöÅuÈàøÀàúÀ EfÇE¢·} EEÄÀu·} E·xfE¢ÇEÈéBº@ExÀ¶ÀBU·|NEÄÀ3U?ÂUÜ·fUâ·U¢f9Uâtoöº@uáùÒâúÂ Eu·Æ¶F$øÕMÈÉz·MâfM¢Mº·6ÇEÈ·Au´)Â·E¢+U¬ÂU°U¤Uè¸)ÂÐUèUÔÒtèEèuMè9N(Uº>xöÄuàøÒâúÂuÀEþpuuE·Æ¶F$ø1øEÈÀt?EìUE°·BU¸)Â9ÑU¼¯M¼EL$D$}°<$èÏ)óÿE¼)EèEì}ÄÿEðU¤M´HüèEðE}MðÇEÈ·P¸)ÐU+E¬·TWþÐE°·AüéMðM¹ÈUÐÒE·MÀ·@fEfM ·}f9} EÌ·} ÀuE·U¢f9xUxÎæ±ýÿÿÈàøÒâúÂ é¡ýÿÿt&Uè¸éSþÿÿvM¹ÈP·r·MÀfM fu·}f9} tÿÿÿ¸1Ò¶MÌÀ¹É±M·u f;q©·E 1Ò}fGÇ$EèÒÔÿÿÀÂ0Méüÿÿ¶U·MÀ·R·ú;}fUåþÿÿMu·Nf;U¢·MÀtéÌþÿÿt&uf;FufM ·E EÀ9ÇèfU¢é§þÿÿ´&EÄÀUUðM¤E´
>JøBüM¨MðEÐD$MEìD$EðD$T$L$E¬D$FD$U$è>óÿÀÂþÿÿ=éÿÿÁíuèE¨9EðÇEèu¼EÀEðéf}u·MÀ·Äf}éêýÿÿfMÔÉzýÿÿ}EðÄèEðéaýÿÿt&V9ÑU¼½EìD$FT$D$M$èóÿÀÂJEÄu¼)uèÀ"Eð}¤U´8PüèEðUìEðu¼Ñ+M¬U¼püèUìEðéýÿÿfEð1ÒE¨éµþÿÿvEÄEÔÀëU·MÀ·RfUéýÿÿ´&EìUM¸E°·B)Á;MèM¼âU¼ET$D$M°$è
&óÿUÜE¼)EèEì·fU¢é?ûÿÿN;MèM´EìD$FD$u´t$E$èuóÿÀÂ6Eì)uèu¼Âð+U¬EìU¤éûÿÿt&EÔÀçþÿÿMEðÄèEðéÎþÿÿt&EèMè;AEèw*uEð·MÀ·vÇÇ@üèEðfuéõûÿÿ1É9}À>ÊM·uÀf)u ¹ÈaMÄEØÉtEØè;Eð}ö-÷ÒÀÀ¶MÌGüÿÿÒtbúéÿÿÀÉ¨À ·E }·U¢f9G·E }è}ÔfGEð1ÒÇÄÐ[^_]Ã1É1Òu·} f9~vEö-t·E u·}¢f9<FpÿÿÿEUèu@E¼)U¼ºéÿÿM¼Në¢v=óÿÿu·u M}ÔfqxÿÿÿEð1ÒÇÿÿÿÿÄÐ[^_]ÃEè,ÖÿÿÀÂt=óÿÿRÿÿÿ}EM·@¹Èf} Eþÿÿu®ÄéþÿÿðÁèàEÄt.ñáÿùt!ÇEÀÇEÄÇEÌÇEÔé{÷ÿÿñáÿÇEÀÇEÌÇEÔéY÷ÿÿM¼uØ9uðtwf} tfm 1Ò¸é>þÿÿEè`ÕÿÿÀÂþÿÿu¸}·vfu }éþÿÿUBÿ+EèE¼%üÿÿBºéÿÿéLþÿÿ¹1Òé^þÿÿU¼}¸M:ÿºéÿÿ%üÿÿAéþÿÿ´&UåWVSì¬MEÇ|ÿÿÿ}èGóÿÃTÌÇD}¤}èM¬u¬P E°AÁM¶MÆÓ¥|ÿÿÿEðEuµ|ÿÿÿU´½tÿÿÿÀ<æ`E¨µxÿÿÿ}¯}ëÇþÿD$|$U°B$è¼.óÿÇE¼ÆE°öu1ÿU¬r~à1öÇA$÷E¼Àt(U¬B,;B(tèÀB,tÇD$M$èÚBóÿu¬¦ÌþÀt
Ì ÌþÄ¬ø[^_]Ãt&½xÿÿÿÿö|ÿÿÿ
>íUö,ºÌu@öô¡uÇD$t$}GD$ED$U´$è*óÿÀÆEÇE¸ÇE¼ÇD$D$ML$ut$}<$è²óÿ=PÿÿÆÂþÿÿ}ß}vÒ}¶ÂUEö,EÀE¼ÀE¸ÌWH Òt%E@T$$D$èR7óÿÇGÀGÀö¡GÀùE¸ÀuM¬ÇAfÇAEðD$uÀt$}<$èe3óÿÀÇ¶ýÿÿÄ¬ø[^_]Ãf}Ì1ÀÇÀørñE¤D$U¨|$ÇD$T$M¬AD$uFD$E°$è@óÿÀÆöE¼}ÀÀúþÿÿÇD$M$è@óÿÀÆ5ÿÿÿéÆMö,ø}
t&tM°¸QÒt¸
u¬öÌúV½tÿÿÿD$|$E$EèÙÿÿÀÇaEèÀ¸
ÇE¸ÇE¼éÓýÿÿ¶öyþÿÿÆGÀwþÿÿGD$U$è]
>óÿÀ]þÿÿöuÆE°éüÿÿt&Eééýÿÿö|ÿÿÿ@<üÿÿE¬öÌöüÿÿ¿óÿÿéÀüÿÿu¬öÌ(Uð½tÿÿÿ|$ED$M$Eè.ØÿÿÀÆMèÉU°¹@}¬xwöÄuàøÉáúÁ }¬1À~·WÀÐA·0|C¸ÇE¸ÇE¼é«üÿÿ¶°löQüÿÿ$GüÿÿOGD$Ò÷ÒâÇD$ÇD$L$T$M$èóÿÀÆ&}°ÇE¼éKûÿÿÇG$éûüÿÿt&UðéþÿÿVt&éÎþÿÿvEè
øûÿÿöÌûÿÿE°x÷Ât@pÀâúÿÿæ@ÙúÿÿFÀ©E¬·P·Fè9ÂU¬BA$E°ö{ªúÿÿFQ(A,éúÿÿ´&¸ÇE¸ÇE¼é]ûÿÿ}E°¸xþÿÿEÀtUÌURz
>}°UìUGÀu8éA¨È	¸$·L f;ÆM¬Gu°fAFuD$t$}¬·GÀD$GD$ED$UBD$M°$èæ,óÿÀÆ`}ìÿÿÿ¶M¬q·y·F·ÏQ9Â>U°xöÄDÿÿÿ	¸D·L@éGÿÿÿf	¸·Lé3ÿÿÿ¶ÇG$éÓùÿÿu¹B6xöÄuàøÉáúÁ"u·FA·Â¶B$ø´þÿÿBu°UÇE¼é½øÿÿt&MU	ÌxUrÊâUº@¶F<E£À¶ÀpÿÿÿE·@EpÿÿÿEB·|øýÿÿEÀt
>}£H¾ìÿÿÇE¼éûÿÿt&¸ÇE¸ÇE¼é
ùÿÿÇE¼éiûÿÿÈàøÒâúÂ égÿÿÿw¹@}°xöÄëûÿÿéØûÿÿ}
Nýÿÿ}¬M¬w·I·VfM·ÉA9Â{ÿÿÿEUÌEUëFt&ât_	¹$·T f;AÿÿÿfE·MU¬fJ·F·ÉQ9ÂÿÿÿExExöÆt«	¹D·T@ë®	¹·TëFÀ÷ÿÿU¬fzTüÿÿ1öé÷ÿÿU¸BÒuáùÀàúÀ"UP·¶B$øþÿÿBMD$u4$è¼óÿÀÆHüÿÿéaþÿÿÆÇE¼´&éèùÿÿED$U°$èÕóÿÇE¼ÆéTöÿÿt&¼'UåìhEM]ôuø¾ëÿÿ}ü¹Ìè <óÿÃá÷P E¼ÌUÀ¨ux¨ÀWÒ
MAT$D$EÀ$èà.óÿÇGÀÆãöÌtBW,öGªUÇD$$èÓ8óÿöÇGXð]ôuø}üì]ÃWÒtÚMAT$D$EÀ$èd.óÿÀt½öuÆÇG´&ë¶¶UEìD$MÀÇD$B$D$GD$è óÿÀÆ@ÿÿÿEÌE¸1ÀU¸ÇÀørîEMT$ÇD$ÀDD$EÀ<D$EìD$AD$E¼$è97óÿÀÆuBU¸EèMÇEèD$ÇD$ÇD$ÇD$1T$ÇD$$è³óÿÆUMÀB$D$EìD$èU-óÿÀIötðÆépþÿÿvEðU¼D$ÇD$·GD$G$D$èã&óÿÆéxþÿÿEÇD$ÿÿÿÿ$èéøòÿÆé<þÿÿ¶Uö,u@öôBUOL$ÇD$M´MÀB$D$GD$è óÿÀÆÇýÿÿÇG$UÇD$M´BD$BL$D$EÀ$è2óÿÀÆýÿÿUJÉtt@°pöteö-u\|Àt@<Àt	öøuBG·WD$T$PL$M¼ÇD$D$T$$è-)óÿÀÆýÿÿWëfWÇÇBzM¼xöÄux¨È·G·DB t&H1öéÂüÿÿt&lÀ°þÿÿGD$ÇD$ÇD$GÇD$$D$èóÿÀÆwüÿÿésþÿÿt&·G·DB@ëfM¼xöÄuR¨t_·G·DB"émÿÿÿt&ö-üÿÿG,GGE´éZþÿÿt&·G·DBé7ÿÿÿ´&·G·DBBéÿÿÿ·G·DBéÿÿÿ´&¼'UåWVSè8óÿÃMóì\EÀUÔU¼EÄ1ÀU¼ÇÀørîEÀ¸Ì1ÀOy·QÀÀ9ÂÀ¶ÀÀEÌ³ÇEÈÇD$UÀBD$BD$GD$UÄB $è¢/óÿÀÆukWzë·GT$D$EÀ$è*óÿÀEÐu=EÌ§ÌþÀóUÀöztGÀ
>ÇG$EÈÀuÐÄ\ð[^_]ÃvUÀö,uEÄöz1ÿÿÿG;G%ÿÿÿEÀÀDD$EÀÀ<D$U¼ÇD$L$T$UÀBD$EÄ$è 2óÿÇEÈÀÆßþÿÿÄ\ð[^_]Ã·GT$D$EÀ$è)óÿÀÆRÿÿÿUÌÒWéáþÿÿt&ÇD$ÿÿÿÿ·GD$G@D$UÀ$è7óÿÀÆÞþÿÿéÿÿÿt&EðD$ÇD$ÇD$ÇD$E¼ÇD$D$UÀ$èýòÿÀÆõEÀ¸ÌWH Òt#EÀ@T$$D$è&(óÿÇGÀtÆGÀöªGÀuÇG$ÇD$ÇD$UÀ$è}óÿÆéEþÿÿfÇD$ÿÿÿÿ·GD$G@D$UÀ$è?óÿÀÆÍþÿÿéþÿÿt&GD$$èMüòÿÀÆòýÿÿéØýÿÿfGD$UÀ$è*üòÿÀTÿÿÿöuÆÇD$EÀ$èy1óÿé³ýÿÿ´&UåWVSì\Eè¦4óÿÃçïÇEÌÌ09V uÐMÈÿUÜ}ÔtEÔÌEÌUÈöÌt]MÈøø*D$öÇþÿD$F$è¥óÿÇEàÇEÔÀu=EUÌ2EÈévEÔÀÍMÌ1ÿÇEàöÌMÔ±ÌVH Òt)EÔ@T$$D$è=&óÿÇFÀtÿþFÀÿ9FÀ'uE¶ÌuÈ0N uÈVÒt(uFT$$D$è×%óÿUÈÇBÀtÿtaMÈAÀucÿuEÈpöuÇ@$MàÉt*EUÐÇD$ÇD$´D$B$è¥
>óÿÄ\ø[^_]Ã´&MÈÇAÀtuÈÀD$4$èúòÿÀtÿuÇ¶ë¶ÇFÀÿÿÿUÔFD$$èÍùòÿÀæþÿÿÿu$MÇEÌ0MÈéïþÿÿt&ÇF$UMÌ1UÈéÍþÿÿv}ÈEìD$ÇD$·GD$G4$D$èkóÿÀÇ-EìÀ"EEØMØVÌöôMÄ@}ö,<7Föô*°löEÈUÈÇD$ÇD$ÀD$B<$ÇD$D$è@
>óÿÇEàÀÇvMØ¹ÈJEØö, ýÿÿMÉýÿÿUEðD$MÜÇD$B$D$ED$èóÿÀÇàüÿÿUðfz?EØ°ÌVH Òt#EØ@T$$D$èS#óÿÇFÀtÇVÒÿüÿÿFÀuÇF$EðMD$$èSúòÿÀÇ]üÿÿEÔÀEÈ}ÇD$ÀD$GD$EÈÀD$EÜ$èÍóÿÀÇ[üÿÿEèøÿÿÇéLüÿÿÇEà1ÿé¬üÿÿfE1ÿÇEàö,ßûÿÿUÈEìD$B4$D$èüòÿÀÇ×ýÿÿt&EÔÇEàÀêûÿÿé¨ûÿÿ}EðD$ÇD$GD$EÈÀD$EÜ$èóÿÀÇÈxºBMðöÄÁ}È·GBU·DEBL$MÜD$$èÏ!óÿÀÇu}}ÔÈøt9ø¨}ÈD$öÇþÿD$F$èóÿÇEàÇéûÿÿUÌEìD$ÇD$·BD$B4$D$è)óÿÀÇth´&ÇEàéØúÿÿt&àøÒâúÂ"é,ÿÿÿt&uö-u?ÇEà1ÿéýÿÿMÌEìD$A4$D$èúòÿÀÇuEìÀuUÔUØéYüÿÿð´D$è8ÇD$D$ÇD$ Fx$D$è(óÿÇEàÀÇ«üÿÿé.þÿÿEÄuÇD$}ÜÀD$F<$D$EÄÀD$èaóÿÀÇ«ùÿÿEØè³õÿÿÀÇùÿÿécüÿÿMuÜAT$4$D$è& óÿÇésùÿÿUØFD$$èÍôòÿÀÊüÿÿÿQùÿÿÇ´&éCùÿÿM}UÌ71ÿÇMÈéÔùÿÿUåWVSìl}MÇEÔÇEÄè#-óÿÃdèÇEìÇEðP E¸ÇE¼UÀQÒÝE1ÉPÒ]WÒú@°pöçö-Ú|Àt@<Àt
öø¼E¼D$$uFL$D$ FD$ED$FÇD$T$D$EäD$U¸$èÈ(óÿÀÆt|¶UðÒtGT$D$MÀ$è¯óÿUÔÒUìÒtGT$D$EÀ$èóÿEÄÀtEÄD$<$è1óòÿÄlð[^_]ÃvÇEäÇEèuðötEäUèVMìÉtEäUèQötBEÀMAFGt$D$UÀ$èóÿÆEÔÀ{ö#ÿÿÿMì1öÉqÿÿÿuöKEAGL$D$UÀ$è»óÿMÄÉÆböÚþÿÿÄlð[^_]ÃEÔD$ÇD$ÇD$T$ÇD$<$è±óÿÀÆþÿÿEðD$ÇD$GD$EÀD$uÀ4$è<óÿÀuðu¼é°ýÿÿt&EÔD$<$èÕñòÿélþÿÿt&EÄD$ÇD$ÇD$T$ÇD$<$è!óÿÀÆþÿÿEìD$ÇD$GD$EÀD$UÀ$è¬óÿÀMìé3ýÿÿEFféuþÿÿvuFAéþÿÿfEÔD$<$è-ñòÿÀnþÿÿöýÿÿÆ´&éýÿÿvEÄD$<$èýðòÿÀuÔéþÿÿD$UBD$M¸$èôòÿÆéHýÿÿD$MAD$u¸4$èëóòÿÆé(ýÿÿ´&UåWV¾@Sì,MèQ)óÿÃäxöÄuàøöæúÆ yÿtBB¸pt6ö-u-|Àß@<ÀÔöøÇ´&EÇÇ@}E÷Àt\UM·W·A;EfUòÙu+EöÀD$7D$UDW$è±óÿE·Mòf7f@Ä,1À[^_]ÃvU·BèfB·Ð1À;Ut"+UD$MDOD$O$è\óÿ1ÀÄ,[^_]Ã¶ED$ ML$ED$ML$AÇD$L$|$D$$èîòÿÀ
ÿÿÿÄ,[^_]Ãt&uöéAÿÿÿ¶UåìHE]ôuø}ü8è®'óÿÃïâxÊâUàt>uº@¶Fè<	vIuFD$G$è² óÿ¶]ôuø}üì]ÃvuÈàøÒ¶FâúÂ è<	w·¶À¸ÈþÿØÿàt&EÀEØuà¸@ö`UØU·EUä¶Pâúúoê¦UBD$G$è
 óÿé\ÿÿÿt&öE.UEUðUÀEì·B9Eì§uUðEöuØuì·Bf;r¼EÀ¥EðUuØê·40f;4PUè0ÿÿÿÇD$T$EUuD$T$4$èïóÿé¾þÿÿ¶¸D$UEuT$D$4$èRðòÿéþÿÿUà¸@ÒtTUuP·ð¶Pâúïþÿÿú·À%üÿë´&ÈàøÀàúÀ éþÿÿváùÀàúÀ ëuöuØé[þÿÿvUà¸@ÒuäU·uD4$D$èÏóÿÀÛýÿÿ¸éÿÿÿ·À%üÿé
ÿÿÿúAþÿÿ·0@D$E$èóÿÀýÿÿF%üÿéÚþÿÿt&EÀEØékþÿÿváùÀàúÀ éeÿÿÿt&ÇEØéýÿÿEÇD$ÀD$éaþÿÿ¶¼'UåWVSì,}è$óÿÃÇßÌBMìEðA,pä1À;q(seé¶·FD$<$D$èóÿÀumfnÇD$FÇD$t$<$D$ED$èêòÿÀuCUìî9r(w/ÇD$GD$Gt$D$B $èýóÿÀyÿÿÿÄ,[^_]Ã=PÿÿvuíUð@D$@($D$àÈþÿD$è»þòÿMðÇD$$èXáòÿë±v¼'UåWVSìÌEMè`#óÿÃ¡ÞÇEèÌP lÿÿÿEhÿÿÿpÿÿÿÀ¬A,q(µtÿÿÿyøUÇD$tÿÿÿµpÿÿÿBD$BL$4$D$èóÿÀ|ÿÿÿõfÇzÿÿÿhÿÿÿ|ÿÿÿy(9½tÿÿÿEþwé£vÆ9µtÿÿÿvpUpÿÿÿBD$$D$èóÿÀt|ÿÿÿÒu|ÿÿÿNÇÉt¶FD$E$èéòÿÀt |ÿÿÿÒuÆ9µtÿÿÿ|ÿÿÿwú¸%I$÷ÒtÿÿÿÁê÷âÂkÒ×|ÿÿÿUµ|ÿÿÿöÅhÿÿÿÇ;x,èMÇD$µpÿÿÿAD$A|$4$D$èáóÿÀ|ÿÿÿu~fzt*·GT$D$E$è×óÿÀ|ÿÿÿuTfzuKT$U$è5ëòÿhÿÿÿ|ÿÿÿA;jOÇÉ|ÿÿÿÀAÿÿÿvÇhÿÿÿ9z,rBÒtMµpÿÿÿAT$4$D$èóÿGÀtÉGD$E$è3èòÿëµt&hÿÿÿµ|ÿÿÿA(uA,ÇÇ@EÄÌ[^_]ÃuGD$4$èêçòÿÀUÿÿÿ|ÿÿÿÒXÿÿÿ|ÿÿÿéMÿÿÿt&hÿÿÿhÿÿÿ@,Q(tÿÿÿ9Âµtÿÿÿfyvé.ýÿÿt&µtÿÿÿfxýÿÿtÿÿÿ;tÿÿÿrÞyýÿÿEÇD$L$$èyçòÿÀ|ÿÿÿ"ýÿÿéÞüÿÿfÇAéþÿÿvtÿÿÿM·BD$$D$èóÿÀ|ÿÿÿÞüÿÿµtÿÿÿÇD$ÿÿÿÿ·FD$@D$E$èîòÿÀ|ÿÿÿ¦üÿÿEÀtf~©tÿÿÿMP·pUèQfµzÿÿÿµpÿÿÿD$T$4$è¸óÿ|ÿÿÿtÿÿÿxÿ*|ÿÿÿÉCüÿÿ½tÿÿÿéÌýÿÿt&hÿÿÿB(Ç@z9}èB,Çþÿÿf½zÿÿÿþÿÿMÈuì`ÿÿÿµXÿÿÿé¶¾EÈÀ}UìÒt1MAT$D$pÿÿÿ$èóÿÀtUÒu
>E´&MØÉ
>UðÒt.MAT$D$pÿÿÿ$è¾óÿÀtMÉuEt&öZýÿÿ`ÿÿÿUÇEðÇEìÇEÈÇEØ}èD$ÇD$ÇD$|$ÇD$$èöòÿÀEÿÿÿXÿÿÿuÇD$pÿÿÿL$F$D$Eè\ÿÿÿD$èóÿÀEÓþÿÿMìfyÅþÿÿ¶A<è<±þÿÿµlÿÿÿ¸@xöÆuâúÀàúÀ ·EèEØD$EèÇD$ÇD$ÇD$D$E$èÆõòÿÀEGþÿÿUEðD$\ÿÿÿÇD$µpÿÿÿBL$4$D$èJóÿÀEþÿÿEpöqÂ@pÉ\ö-O|Àt@<Àt
öø1u¬1ÀÇÀørñEðlÿÿÿE¬E°Edÿÿÿ1ÀdÿÿÿÇÀørëlÿÿÿMìx¸@öÆuâúÀàúÀ ·¸Uyt·À%üÿE¶QBý<ÖúÛ·AdÿÿÿL$$D$T$ AMðt$uD$AÇD$L$D$FD$lÿÿÿ$è»õòÿÀE¼üÿÿUðé8t&¶é5øÿÿUEØD$$èâòÿÀÜüÿÿUÒÑüÿÿEvéÆüÿÿ`ÿÿÿUD$$èRâòÿÀfüÿÿMÉ[üÿÿEéSüÿÿUÀD$$è%âòÿÀ¼ûÿÿµ|ÿÿÿö¼ûÿÿ|ÿÿÿé±ûÿÿtÿÿÿhÿÿÿr,J,D$E$è!æòÿhÿÿÿr,À|ÿÿÿ±÷ÿÿéûÿÿµlÿÿÿ¸@xöÆuâúÀàúÀ ·4¶F$ø×FEèé	ýÿÿUðÇÇBhÿÿÿöÌñzçMì¶qFý<îð<Õ·qlÿÿÿT$$D$è;õòÿEìhÿÿÿxöÌutUð|$MB$D$èóÿÀEîúÿÿEðuD$4$èPãòÿÀEt~ÇEð¾éÉúÿÿt&FD$E$èâúòÿÀE£úÿÿéÿÿÿUðz´&{ÿÿÿp´&élÿÿÿv1öMìé/ÿÿÿ·AfÑè·ðé ÿÿÿqéÿÿÿÇEð1öéNúÿÿA¶é)ýÿÿ·AfÑè·ÀéýÿÿUº@åWVSìEè¾óÿÃÿÓE¤xöÄuàøÒâúÂ MEuÉÈMN·EÉE tBU¤BpÒt2ö-u)|À3@<À(öøvuÇÇFU¤¿@xöÄÙMU·IfMM ·pBæüPâüf9Öt·E·öM}Á·Â)Æ;M E L$)ÈD$1$èØóÿE1ÒM·GfyfEªðt%v·ÂG·f9EªrðfEÂf9PwàðUM fBñÆAuFfÁD$T$$è¬òòÿÄ1À[^_]ÃvàøÿçúÇ éÿÿÿt&M u·	vMÈ9ñu\fE¨Ef}¨8OU ¶B:M·E¨Ñ1ÒÁè·ðë¶¶DÁÂ8uB9òfE²uæ·U²f)U¨:u MLuM¬|7ÿU¬1ö1É¶:téE¬¶Tÿ¶Dÿé8Âu	Æf;u¨rã·U²·ÆÆÏ)MME )}MÜMDEØÐE¼EEÀE¼D$$EØt$,T$(D$ U ¶B%D$ML$ut$FÇD$t$D$UBD$M¤$èÿóÿÀýÿÿÄ[^_]ÃMðf4é4þÿÿfðéþÿÿ1Ò1É1ÿ1öéGÿÿÿU EfÇE²DUE¬|ÿééþÿÿ·U²1öÑ×éÿÿÿ·Ò1öÑ×éÿÿÿUåVÆSÐìPàèCóÿÃÐúEîtfEÇEôEðUÐ1ÀÇÀørñEìEÐET$UÇEÔÇD$ÇD$T$D$4$èRøòÿÄP[^]Ã´&EðD$E4$D$èÛòÿÀuØUBEôëvUåWVSì\EuèóÿÃÑÏ¶ÌH Pøþÿÿ¸ðµôþÿÿvüþÿÿøþÿÿðþÿÿ·P½èþÿÿuìxfÿÿÿÂâ}öG ùI9Ï´þÿÿ!}ÏMAAÒt!½èþÿÿ9ø½lÿÿÿöEUlÿÿÿöB /MuU}ì6E¨Aµ8ÿÿÿE¬AE°AE´AE¸AE¼AlÿÿÿEÀ9J`@ÿÿÿþ8ÿÿÿ1Òöyt	µ@ÿÿÿVMµlÿÿÿAXt$T$$èdÞòÿöEÀ t
>} E}¸PXE¬ú4ÿÿÿD$E¨D$4ÿÿÿ$èWîòÿ8ÿÿÿE¬öyz}GXW\ÇGdÇGhÇGpE¨U¬G`ÇE´ÇE¸E°GlÇEÀE¼E¨E}
½ôþÿÿ1À·À;lÿÿÿÀ}ÿÿÿ
}ýu{²þÿD$t$½ðþÿÿ<$èbúòÿÆÄ\ð[^_]Ã´&}öG þÿÿuFé
>þÿÿ·ÿÿÿ·µÿÿÿf9wÌþÿÿ"ÆEæuäfÇEäÇ<ÿÿÿ¶F$ø·E¸}9ÂOXvÂFT$$D$èûìòÿE}¸M´PXù|ÿÿÿ·ú9|ÿÿÿ4ÿÿÿTE¬éXþÿÿt&µ@ÿÿÿVéxþÿÿf;lÿÿÿýÿÿénýÿÿ´&}t&*
}
¶ÍþÿÿEH1À9ÊºÀÀÿÿÿuA%üÿPÿÿÿÀMÂMìhÿÿÿøþÿÿØþÿÿxpÿÿÿâ`ÿÿÿµ`ÿÿÿº@Øþÿÿö·HupÿÿÿàøÒâúÂ µØþÿÿ·É·vðÀ)ÁÈ)Ð9hÿÿÿµ(ÿÿÿ¾Pÿÿ.þÿÿ½pÿÿÿy½Øþÿÿ1öÇÿÿÿfÇÿÿÿ}ÿ½Àþÿÿ@ÇD$}GD$ÀþÿÿD$EìD$üþÿÿ$èóÿÀÆ±ýÿÿôþÿÿQ,;Aáuì½ôþÿÿ}µØþÿÿw}
>ß}PýÿÿØþÿÿzvÕôþÿÿ1ö1ÿfÿÿÿ·ÿÿÿfAÌþÿÿÿÿÿ1ÒÀ~öE*ÒÅML$ÌþÿÿD$ØþÿÿT$M$èþòÿÿÿÿÿÿÿÀ	îÁµÿÿÿÄ\[ð^_]Ã¶|$L$µðþÿÿ4$èöáòÿÄ\[Æð^_]Ãv8ÿÿÿxº@öÄuàøÒâúÂ 1ÀÀÌþÿÿB·84µ<ÿÿÿéüÿÿøþÿÿJÉâûÿÿ·µÿÿÿEèUìµÌþÿÿD$1ÀL$zT$ÀðD$}|$UBD$øþÿÿ$èîúòÿÀÆäûÿÿEèÀôþÿÿ·À;lÿÿÿÀ¶ÀÿÿÿøþÿÿEìxØþÿÿpÿÿÿâ`ÿÿÿaº@Øþÿÿ1ÀyÎÀÌþÿÿB1Ò·¹Æ¶F$èf·1ÒÀ%üÿHéQÐÀXD$L$F$è4óòÿÀÆ~lÿÿÿEP`éÏùÿÿt&öÄº@uàøÒâúÂ 1À·½ÿÿÿ~ÀøB·0¶B$ø½·U$T$èoòòÿøþÿÿxâéÎøÿÿt&|$D$ðþÿÿ$è^ßòÿÄ\[Æð^_]Ãv·lÿÿÿÀ%üÿDUìhÿÿÿøþÿÿØþÿÿxpÿÿÿ%`ÿÿÿéûÿÿt&}FøþÿÿºuìxµØþÿÿpÿÿÿá`ÿÿÿ1É½ÿÿÿBÿu·lÿÿÿÀ%üÿD9ÁÇhÿÿÿÇÿÿÿ'ûÿÿ)Èhÿÿÿéûÿÿ´&}ÇG`ÇGXéùÿÿfU0ÀÇÀørñEÀ`D$EÀXD$<ÿÿÿAD$AT$D$uFD$½8ÿÿÿ<$èøòÿÀÆ"ùÿÿEµ<ÿÿÿ}¸PXE´Nú4ÿÿÿ89ÑºùÿÿÎ)ÖU¬9Ðt!t$4ÿÿÿD$4ÿÿÿÐ$è!úòÿE¬÷éç÷ÿÿvÉþÿD$µðþÿÿ4$¾è÷åòÿé¢øÿÿ¶}´}
feøÿÿÿÿÿÉªE·½ÿÿÿD$|$ØþÿÿÇ$T$EºèõÿÿÀÆ>øÿÿÇD$|$Eì@D$U$è]ÙòÿÀÆøÿÿfÿÿÿ1ÿ·ÿÿÿEìÌþÿÿØþÿÿé´úÿÿf|ÿÿÿ4ÿÿÿU¬+|ÿÿÿDD$L$$èSåòÿ·<8+½|ÿÿÿérøÿÿ¶üþÿÿ@xìþÿÿÿ¦ùÿÿøþÿÿ¸@
>`ÿÿÿÒu¥pÿÿÿ½pÿÿÿÀàúÀ )ÁÿÿÿÀtlÿÿÿ1Òè÷ñtÿÿÿÀtUB1Òè÷ñtìþÿÿ+y9þ0ùÿÿµøþÿÿ4$ènëòÿÆé÷ÿÿvBé>üÿÿ}
t&Ùøÿÿ`ÿÿÿ¸@ÒupÿÿÿàøÀàúÀ øþÿÿ+hÿÿÿ)ÁÑè9Áøÿÿu·ÿÿÿ6Ìþÿÿÿÿÿ¾xµ ÿÿÿ½0ÿÿÿç½,ÿÿÿ	¸@½ÌþÿÿØþÿÿÿÿÿÿÌþÿÿÌþÿÿÿÿÿ½ÌþÿÿÀdÿÿÿ·Qïf;yf^ÿÿÿu{ÌþÿÿÿÿÿdÿÿÿµÿÿÿµdÿÿÿLBøë9·é·îfºþÿÿdÿÿÿèf;ºþÿÿxÿÿÿÄdÿÿÿïÿ½ÿÿÿu¾ÇdÿÿÿfÇ^ÿÿÿµ,ÿÿÿ¸@öu0ÿÿÿàøÀàúÀ Øþÿÿ¹dÿÿÿµØþÿÿ·Æ¶F$è×hÿÿÿ1À}ÿÿÿÿÿÿÀ9(ÿÿÿfÿÿÿµÿÿÿ·^ÿÿÿ½dÿÿÿ·Ff;>f&ÿÿÿö0ÿÿÿÁ½ÿÿÿÎöÐþÿÿà÷Äþÿÿë\ÿÿÿÐþÿÿfÿÿÿ9(ÿÿÿ°·Çf9&ÿÿÿVµdÿÿÿØþÿÿÖdÿÿÿÐþÿÿÁÐþÿÿ,ÿÿÿ¸BÉu½ÄþÿÿÀàúÀ"·ºØþÿÿÁ¶A$èfÿÿÿ·À%üÿPéSÿÿÿvpÿÿÿàøÒâúÂ éøÿÿ´&f½ÿÿÿéõÿÿµ ÿÿÿÇÿÿÿ¾Áè;ÿÿÿØõÿÿé¾õÿÿ´&}tVÇD$ÌþÿÿD$Eì@D$U$èßÔòÿÀÆóÿÿEìôþÿÿxÀ¶Àf)ÿÿÿ·µÿÿÿfqôþÿÿöÌt'}ªÇD$U$èäÃòÿÀÆ:óÿÿÿÿÿÀÍu¾ÈGöÿÿ½èþÿÿ1öÇG0éóÿÿt&Øþÿÿzù·ÿÿÿ1ö1ÿÌþÿÿé¤õÿÿÇD$ÇD$·ÿÿÿÌþÿÿT$ØþÿÿAD$µøþÿÿ4$è"ñòÿÀÆòÿÿ}ì½Øþÿÿ¶Oùßøþÿÿxº@öÄuàøÒâúÂ µÌþÿÿ½Øþÿÿr·8øùÒ1ÿùÇÿÿÿÒu¶@1öº$èëôÿÿÌþÿÿD$ØþÿÿT$M$èf÷òÿÀÆìñÿÿEì¾Øþÿÿéôÿÿt&·½ÿÿÿ½Ìþÿÿéöÿÿ¶Eìéôÿÿ¶UT$ÌþÿÿºL$ØþÿÿÇ$D$EèQîÿÿÿÿÿéôÿÿ¶0ÿÿÿàøÀàúÀ éãúÿÿEÇD$D$ÂBÀ%üÿD$ÌþÿÿL$ØþÿÿD$U$è´æòÿÿÿÿéôÿÿ·ÿÿÿf^ÿÿÿéOûÿÿUÆEòBÇEÈfEðEðEÄEÄT$D$ëM·½ÿÿÿÇD$L$A|$À%üÿD$µØþÿÿt$E$è0æòÿÀÆHøÿÿéðÿÿ·À%üÿHéûÿÿ¶xçé*þÿÿ}º@Ìþÿÿuì?éHÿÿÿµtÿÿÿG ½TÿÿÿPÿÿÿxöÄuàøÒâúÂ HÿÿÿÀtYHÿÿÿµHÿÿÿtÿÿÿé·rf;J¼þÿÿu41öë&¶¼þÿÿ½Ìþÿÿòî·Dzúf;Dzöu
éÉHÿÿÿuÖTÿÿÿUàxT$ÀàúÀD$U$èúêòÿÀÆïÿÿEà}µTÿÿÿ·ÿÿÿÇ@Ç@DÿÿÿfÇ@Æ@fP1À½ÜþÿÿÜþÿÿÇÀørë·Hÿÿÿ·µHÿÿÿfÇNÿÿÿÔþÿÿÁfuÈþÿÿ·½Nÿÿÿ½Xÿÿÿ|$Eà@D$HÿÿÿD$tÿÿÿBD$ÔþÿÿL$u4$èÝòÿÀÆe½TÿÿÿºBxöÄuàøÒâúÂ"tÿÿÿ¹·}Ðtÿÿÿ·x4?ÂU¶B$èTÿÿÿM@À§ÇD$ÜþÿÿL$D$XÿÿÿT$EàD$M$èµãòÿÀÆ¿fNÿÿÿ½DÿÿÿEÇD$µÈþÿÿ|$t$tÿÿÿD$U$è»÷òÿÀÆuyE|$D$tÿÿÿL$u4$è%ÊòÿÀÆuSHÿÿÿDÿÿÿþÿÿÇD$ÔþÿÿºÀD$½tÿÿÿ|$Eà@$Eè*êÿÿÀÆ=UBD$EàD$Pÿÿÿ$èÝñòÿÀöñùÿÿéíÿÿvÇD$ÿÿÿÿÌþÿÿÀD$Eì@D$M$è*ÎòÿÀÆðÿÿ8ÉþÿD$t$½ðþÿÿ<$èdòòÿt$<$è¸¼òÿÆé±ìÿÿfE·}éÞþÿÿfÿÿÿ·ÿÿÿÌþÿÿéúÿÿ·ÿÿÿÇD$T$xD$|$M$èPöòÿÀÆVìÿÿÇD$|$Eì@D$u4$èuÍòÿÀÆ+ìÿÿfÿÿÿ½ôþÿÿ·ÿÿÿUìfG1ÿÌþÿÿØþÿÿéÁîÿÿ·½ÿÿÿÇD$|$|$µØþÿÿt$E$è¿õòÿÀÆÅëÿÿéóÿÿ·ÀÁáüÿéRýÿÿÿkøÿÿéIøÿÿ¶BÀ¶Gýÿÿàøt&{ýÿÿTÿÿÿxºBöÄuàøÒâúÂ"tÿÿÿtÿÿÿð·DD$u4$èåÞòÿÀÆ(ýÿÿéÚýÿÿfö¶tðÆféëÿÿÔþÿÿÀÂ+HÿÿÿD$T$GD$E$è$ÌòÿÆéýÿÿUåìH]ôuøu}üÇÌèèüòÿÃ)¸¿ÈEàtGð$øv.ÇD$@$èºòÿÂ´&]ôÐuø}üì]Ã`ÉþÿØÿàt&ñÉy"ÒtJÉCEàÇÄæÿÿÿþw³xÉþÿØÿà¹vÒtBÀuÉEðD$ET$UàÇD$L$D$B<$D$èÓÃòÿÂéXÿÿÿ¹ë±¹vë¦¶¹vë¶¹vë¶¹vésÿÿÿvºÇEEðMD$EàT$<$L$ÄD$èÍòÿÀÂÔþÿÿMàA,·@)Äé¿þÿÿ´&ºëºë¥ºvë¶ºvë¶EàT$ÇD$<$ÄD$èlíòÿÀÂ þÿÿéYþÿÿUåìÈ]ôuø}üÇxÿÿÿxÿÿÿUðT$èÙúòÿÃ¶Etÿÿÿ¶@<$ÌD$èúãòÿÀÆu1MðÉt*µxÿÿÿA;Bv)yufÇAL$<$èEÄòÿÆð]ôuø}üì]ÃGUÇD$D$GD$tÿÿÿD$B $èfòòÿÀÆ¨OÉ@pÒö-õ|Àt@<Àt
öø×Uxÿÿÿxº@1öÄu¸uàøÒâúÂ U¼~Y·VMEÔ)Ðº@EØxöÄuàøÒâúÂ E·FÀE EUðD$(EÔD$$E¸t$D$ FT$uD$B4$ÇD$T$D$GD$èmîòÿÀÆMðëfMðÇÇAAqExÿÿÿUET$$D$èAÔòÿEðUMpµxÿÿÿPUGÇD$t$D$GD$B $èÂðòÿÀÆxÿÿÿ1~UfÇFfFUðMEzNwG¾J¸Óà©àt5BÀuJÉt'Bt$<$D$è ¿òÿÀÆxÿÿÿ2fÌt$<$|ÿÿÿèÄÁòÿxÿÿÿÆEðölýÿÿEÀaýÿÿ|ÿÿÿGuI,D$GÇD$pÿÿÿéD$L$F M$èÇïòÿÀÆýÿÿpÿÿÿHä¶A<t<oUxº@öÄuàøÒâúÂ u·FB·PUPwö@¸pö-ø|Àt@<Àt
öøÚEð@T$UD$ ·BL$D$AL$Mt$ÇD$D$$èBÌòÿÀÆ5üÿÿEðu|ÿÿÿPQ,1öéüÿÿ´&GUD$EðD$B $èøèòÿéðûÿÿ´&fÇFéêýÿÿMº@xöÄuàøÒâúÂ EÔ·FÇE EØé®üÿÿÇÇAé]ÿÿÿuº@xöÄuàøÒâúÂ u·FB·Eéþÿÿ¶¼'UåWÇVSìLUÐUðT$UÄEÌGUÌèõòÿÃà°ÇD$D$EÐEÈD$B ÇEðÇEà$èïÙòÿÀÆ1EàEÀvUðBÀEÐ'GT$UÌD$B $è²çòÿÀÆôEÄUÈÇD$D$GT$UÌD$B $è}ÙòÿÀÆ¿UB ;EÐsEÀt;EÀUÇD$ÇD$D$T$ÇD$<$èsÍòÿÀÆu"ÇEUÄøÇ$èùÿÿÀÆ/ÿÿÿUðÒt(GT$UÌD$B $èëæòÿÀtötC´&EàÀvtEàD$@$è>ÅòÿÀtöuÆÄLð[^_]Ã¶1öëÆëÀUåW×VSìlE´èôòÿÃC¯ÇEìÇEðE¼zJU¼xº@öÄ[MJ·8E¸ÀEÀU´EðD$MÀÇD$E¬BU¼L$D$B $èØòÿÀÆÒEðxU¬E´Ç$èSøÿÿÀÆ©UðMÀBEì;E´PÒçÁ@¸pÓö-Æ|Àt@<Àt
öø¨EìMÀD$ T$U¼|$ÇD$D$E|$$D$GD$è7ÈòÿÀÆnUðÒt&M´AT$U¼D$B $è	åòÿÀtöuÆÄlð[^_]ÃàøÒâúÂ éþÿÿt&fxàþÿÿM¸AD$E´$èÜÙòÿÀÆuUÐ1ÀU°M°ÇÀørîU¸EÔL$D$BD$BL$M´D$AD$E¼$è'ßòÿÀÆuU°EìM´D$T$$è¨¸òÿÆEÐÀtU¼D$B$èMßòÿödþÿÿéôþÿÿt&xº@öÄt0MJ·8¶B$øtHÂUÀÇE¸é©ýÿÿ¶àøÒâúÂ ëÀÇÇGEìMÀéþÿÿ¶BÂE¸UÀébýÿÿë
UåW×V1öì fzEìÇEôué¶Æf9wUìº@xöÄuàøÒâúÂ ·ÎJ·¶B$øu¸EÂUðR;P vD$Eìú$è^üÿÿÀEôu'EðPEÇ$D$EìèúÿÿÀEôhÿÿÿEôÄ ^_]Ã¶UåWÇVSìÌhÿÿÿµhÿÿÿèðòÿÃW«ÌP ¶ÌtÿÿÿlÿÿÿxÿÿÿU¸F,µpÿÿÿEð1ÀÇÀørñEðfxØpÿÿÿpÿÿÿB(B;AtwÇE1öMEðQ ;PvBÿA hÿÿÿhÿÿÿ¸È$ÇD$À¶ÀD$èÔòÿÀÂuMAiöTÄÌÐ[^_]Ã´&fzuÇD$<$èÍëòÿÀÂuÏµpÿÿÿpÿÿÿF(¶pB,@ä@EéOÿÿÿt&GlÿÿÿÇD$tÿÿÿD$GD$B,D$A $èØæòÿÀÂfÿÿÿGµpÿÿÿÇD$tÿÿÿD$GD$F,D$B $èæòÿÀÂ(ÿÿÿlÿÿÿA,|ÿÿÿF,µtÿÿÿ6·PEEð)Öuwöü@pÉéö-Ü|Àt@<Àt
öø¾EÐtÿÿÿEÔxº@öÄuàøÒâúÂ EMµ|ÿÿÿÐE·AÀE EQNwEØED$(EÔD$$ET$|ÿÿÿL$tÿÿÿÇD$ D$T$T$ÇD$t$$èâòÿÀÂþÿÿf|ÿÿÿMðÆ@·VA·A+UÁEò$L$D$èuÈòÿtÿÿÿxöÄÜ¨ô|ÿÿÿMð·BDB E¸ 1ÒfyÇ`ÿÿÿtHµtÿÿÿ1ÒE6µ`ÿÿÿfµ|ÿÿÿ·FufVuf+`ÿÿÿfV·AÂ9ÐÖ`ÿÿÿµ|ÿÿÿ·Ef)FfAlÿÿÿfVfÇAöÌu
ö,üÿÿ|ÿÿÿyX`ÿÿÿµhÿÿÿ÷ØD$4$èªòÿÀÂÐüÿÿ`ÿÿÿ<$D$èvªòÿÀÂ8üÿÿé¯üÿÿvGUðT$ÇEðÇD$D$pÿÿÿÀD$xÿÿÿ$è<ÐòÿÀÂjüÿÿUð¶BT$xÿÿÿ9ðÀ¶Àè!ÆG$D$èÞòÿÀÂ3üÿÿö+üÿÿMA AA9EsèA uFÀüÿÿèFéùûÿÿt&µ|ÿÿÿÇÇFéØýÿÿ|ÿÿÿ·ADA@MðE¸@é'þÿÿf|ÿÿÿ·ADAMðE¸éþÿÿfÑú`ÿÿÿéþÿÿt&¼'UåWVSìlìþÿÿìþÿÿèþÿÿµèþÿÿèêòÿÃÝ¥Ìüþÿÿ¶ÌA,ðþÿÿµøþÿÿôþÿÿÿÿÿF,0·~fÿ¶N1ÒEùÂÂÀE@Àìþÿÿ¸ÈÍùÌðþÿÿ@ÿÿÿMì·ÒäþÿÿL$ÿÿÿt$D$·Ç)ÐD$UT$ìþÿÿAD$½üþÿÿ<$èÖòÿÀÂEìÀí
>½ìþÿÿ¿Èô½üþÿÿÿÿÿx·AöÆuYâøÿÿÿHà·BÀ)Á·FPà·FÀ)Â¸ ëN}<$èþÿÿìþÿÿèñøÿÿÂÄlÐ[^_]ÃfÿÿÿHÀ·BÀ)Á·FPÀ·FÀ)Â¸@µüþÿÿÐ+È;E}¢½ìþÿÿìþÿÿµèþÿÿ?Ì¶ÌGµ8ÿÿÿ½4ÿÿÿ½8ÿÿÿ0ÿÿÿA,Tÿÿÿ<ÿÿÿ0G,Eèxÿÿÿàþÿÿ1ÀàþÿÿÇÀørë}èU·N·G½Ìþÿÿfdÿÿÿf&ÿÿÿB Àt	;GQ
>·½dÿÿÿ4ÿÿÿxÐþÿÿ%PÿÿÿöÐþÿÿ	Ìþÿÿ·VÁ pÿÿÿ¹ ÌþÿÿxÀ¶ÀÀf½&ÿÿÿf*ÿÿÿ·Ç·½&ÿÿÿÀ)Â)Ê·*ÿÿÿlÿÿÿ¶VµÐþÿÿ½´þÿÿ)Ï[ÿÿÿæfÇ(ÿÿÿÔþÿÿµ¸þÿÿ½°þÿÿëe´&½Ôþÿÿ½[ÿÿÿ½¤þÿÿ/;lÿÿÿ#lÿÿÿ)È9Eê·¤þÿÿf(ÿÿÿ·(ÿÿÿf9&ÿÿÿðlÿÿÿPÿÿÿ¸@Éu½¸þÿÿÀàúÀ ·µ(ÿÿÿ¹Ìþÿÿ6·pLÿÿÿÌþÿÿÂ¶B$èNÿÿÿ·À%üÿHé;ÿÿÿvøþÿÿB,èfxõüÿÿfxýÿÿéåüÿÿ½ÿÿÿHæ·GÀ)Á·FPæ·FÀ)Â¸éSýÿÿ¶üþÿÿ@Àÿÿÿ,üÿÿàûÿÿÿÿÿéüÿÿPÿÿÿ¸BÒu½¸þÿÿÀàúÀ"ÌþÿÿLÿÿÿ½Ìþÿÿ·¶D$øLÔþÿÿÁ¤þÿÿ;µ°þÿÿrþÿÿ½pÿÿÿLÿÿÿpÿÿÿ·½Ôþÿÿffÿÿÿ÷f;xCþÿÿÔþÿÿT2<P`ÿÿÿÔþÿÿ½\ÿÿÿD24ëFf½´þÿÿÑ¤þÿÿ9½`ÿÿÿþýÿÿ\ÿÿÿÆ`ÿÿÿ·Âf9fÿÿÿ\ÿÿÿÕýÿÿPÿÿÿ¸@Òu½¸þÿÿÀàúÀ ½ÌþÿÿÌþÿÿ÷·½Øþÿÿ¶Dº$èqÿÿÿ½Pÿÿÿ¸@ÿu½¸þÿÿÀàúÀ ½ØþÿÿÌþÿÿ··À%üÿPé/ÿÿÿ´&½Pÿÿÿ°Bÿu½¸þÿÿÀàúÀ"·Ìþÿÿ½Ôþÿÿ·½¤þÿÿÀ%üÿLé}þÿÿfulÿÿÿ+U1+lÿÿÿ9Âv·½¤þÿÿf½(ÿÿÿf½(ÿÿÿÚ½[ÿÿÿõ½[ÿÿÿè·µ(ÿÿÿf9µ&ÿÿÿúÿÿÇD$½ìþÿÿGD$GD$<ÿÿÿB,D$4ÿÿÿA $èÆÛòÿÀÂqúÿÿÇD$GD$GD$µ8ÿÿÿF,D$½4ÿÿÿG $èÛòÿÀÂ3úÿÿ<ÿÿÿxB,öÅhÿÿÿF,¸@uÈàøÀàúÀ  ÿÿÿ·(ÿÿÿuUèÇÿÿÿÇÿÿÿè·ÀÀÇÿÿÿÇÿÿÿµÈþÿÿÄþÿÿ·½dÿÿÿ¸@f½ÿÿÿöÅUèuáùÀàúÀ ·4·B¨mføv ÿÿÿ·f;B¤	ÿÿÿÇÿÿÿÀt*ÇÿÿÿÇÿÿÿ·×öÂÇÿÿÿ@¶F$ø2|øfµhÿÿÿFD$ÉþÿD$½0ÿÿÿ<$è!½òÿºéÌøÿÿvÌþÿÿ¹@Â@pÿÿÿ·Véïùÿÿ<ÿÿÿöÌuìþÿÿö,tXhÿÿÿyuÑ½ÿÿÿÿÿÿ÷ØD$µèþÿÿ4$èýòÿÀÂXøÿÿ½ÿÿÿ|$ìþÿÿ$èÛòÿÀÂ6øÿÿèþÿÿºÈuhÿÿÿ$L$èÀ¬òÿÀÂøÿÿfÇD$µèþÿÿ4$èÎÝòÿÄl[^_]ÂÐÃv8ÿÿÿ8ÿÿÿ4ÿÿÿR,I(Üþÿÿê9Êÿÿÿ,ÿÿÿDÿÿÿ¶µÐþÿÿ×æµ¼þÿÿfPÿÿÿº@7É·Fu½¼þÿÿÒâúÂ ·È·FÀ)Á)Ñ;ÿÿÿs[Pÿÿÿº@Àu½¼þÿÿÒâúÂ ·GfJÿÿÿ·ÀB·0·À%üÿD9ÿÿÿvÿÿÿf½Jÿÿÿuï;½Dÿÿÿ]ÿÿÿ·(ÿÿÿf9&ÿÿÿXPÿÿÿº@É#·µ(ÿÿÿÌþÿÿ6Èf½(ÿÿÿ·þÿÿ½Ìþÿÿ·ÀÇ·ÀÂâüÿ9ÿÿÿ@ÿÿÿw(ìþÿÿö,X4ÿÿÿàûÿÿ9BÞÇÿÿÿpÿÿÿ+µÔþÿÿ·
>f;r¦·*ÿÿÿ·µ*ÿÿÿf)µ(ÿÿÿ÷Ùf®þÿÿë?´&·(ÿÿÿµpÿÿÿ·(ÿÿÿf®þÿÿÂ+Ôþÿÿ·Ff;VNf(ÿÿÿf½(ÿÿÿu¾é¹ýÿÿÌþÿÿ¹·VÀpÿÿÿéçöÿÿÐþÿÿàøÒâúÂ éÄþÿÿEäþÿÿÇT$ÿÿÿÇD$t$L$}|$ìþÿÿBD$üþÿÿ$è;ËòÿÀÂ6õÿÿ}ìÿ³ôÿÿfé$õÿÿvEðÇD$D$UT$ìþÿÿ$èxÐòÿÀÂóôÿÿ½øþÿÿÄ;EðfôÿÿEôþÿÿÇÄ;EðHôÿÿé»ôÿÿÇ$èþÿÿUèèÅâÿÿÀÂôÿÿMè·~Ìþÿÿéõÿÿ@ÿÿÿ9ÿÿÿÃùÿÿUÌÀþÿÿ¶G$èÜ´&·µ*ÿÿÿ·½*ÿÿÿf)½(ÿÿÿ÷Þfµ®þÿÿëf(ÿÿÿf½(ÿÿÿ·(ÿÿÿµpÿÿÿ·(ÿÿÿf®þÿÿÂ+Ôþÿÿ<·Ff;Vt»÷Ðþÿÿº@uÐþÿÿàøÒâúÂ Ìþÿÿøf½(ÿÿÿ·¬ûÿÿ½Ìþÿÿ·ÀÇ·À%üÿ9ÿÿÿÞøÿÿ¶G$è+ÿÿÿÿÿÿÀÿÿÿ÷Ðþÿÿº@uÐþÿÿàøÒâúÂ ·(ÿÿÿ+ÔþÿÿÌþÿÿB·ÊÂ¶B$øËþÿÿ0ÀµÀþÿÿÇÀørë·EÐBEÌU°1ÀÇÀørñ·E´GE°T$½Àþÿÿ|$4ÿÿÿ$ÿÿÿÿÀ%üÿÀ9ÿÿÿø÷ÿÿ4ÿÿÿUèxÌþÿÿÐþÿÿé4þÿÿt&1ÿéþÿÿ,ÿÿÿfyXòÿÿfyMòÿÿµÜþÿÿ¸BVäµPÿÿÿöuÐþÿÿàøÀàúÀ"··À%üÿÀ;ÿÿÿòÿÿ·&ÿÿÿf+*ÿÿÿf(ÿÿÿé'ûÿÿÿÿÿÀÜøÿÿÿÿÿÀÎøÿÿÇÿÿÿé©øÿÿ·µxÿÿÿÇ|ÿÿÿEFEÈþÿÿD$àþÿÿT$·À%üÿD$·ÇD$hÿÿÿL$½ìþÿÿ<$è¾òÿÀÂnñÿÿ½ÿÿÿÿìÇÿÿÿUèöBÌþÿÿY¶Fº$è2T$ÇD$ÌþÿÿT$èþÿÿ$è¤òÿÀÂñÿÿÿÿÿµÄþÿÿ9µÿÿÿ<øÿÿ½4ÿÿÿxé-÷ÿÿBþT$ÇD$D$hÿÿÿL$½ìþÿÿ<$èÑòÿÀÂ¢ðÿÿÿÿÿÇÿÿÿÀ4ÿÿÿ½ÿÿÿÇÿÿÿ½ÿÿÿEèÌþÿÿé#ÿÿÿÇEuÇD$ÈþÿÿÇD$D$·ÇD$hÿÿÿT$ìþÿÿ$è¾¼òÿÀÂ«þÿÿéðÿÿvTÿÿÿRÿÿÿé³ùÿÿ·ÀÂâüÿé»þÿÿT$ÇD$ÇD$ÇD$èþÿÿ$è«ÐòÿÀÂµþÿÿé±ïÿÿÿÿÿÇÿÿÿÀlöÿÿÇÿÿÿÇÿÿÿÇÿÿÿé_öÿÿ þÿÿÿÿÿéùÿÿt&UåWV1öSì|E U} èlØòÿÃÇEðPH E°E¿ÌU´M¸}¬fxE¼Uì1öÇEäfÇEÂUëP¶U0ÀÒuU¼BMW$L$E è,âÿÿÀÆJ}}¼fEÂ·EÂf9G.M°º@xöÄuàøÒâúÂ ·}ÂM¼}¤yÏ·Ç¶G$èt©EU@G;B ðMMÉ}¬G,ÇD$ÇD$ÀD$U¼BÇD$D$M $èð¯òÿÀÆÇD$} GD$GD$ED$U°B $èÏòÿÀÆJMÇE	M¼}|$E¤$U¼E è«âÿÿÀÆU°xº@öÄuàøÒâúÂ E¼M¤}¼Ð·HÇ¶G$ø`þÿÿEÇD$D$U BD$GD$M¸$èÑºòÿÀÆ£UìM ¶BE«AT$D$E¸$è¤ÈòÿÀÆv}«(þÿÿEðD$ÇD$GD$U $è¿¶òÿÀÆ1EÀM¬A,ÇD$ÇD$ÀD$}¼GÇD$D$E $è`®òÿÀÆòÇD$U BD$BD$ML$}°G $èÍòÿÀÆºEÇEE¼UMÈ1ÀM}ÇÀørîEèE}äfUEðT$M|$L$UÇ$T$Uè}ÀÆuEèÀtÈEÈÀtD$M´$èvÂòÿöu.Eð$èµòÿÇEðÀÆÎüÿÿfÄ|ð[^_]Ã¶EðÀté$èUµòÿÀtÝövuÖÆÄ|ð[^_]ÃfUåWVSì\àþÿÿEÜþÿÿàþÿÿèQÔòÿÃÇEð@ ÇEìÇEäÇEÜÀÀö,¶ÀÇEØÿÿÿ»	àþÿÿ	Ðþÿÿ½ÿÿÿ½ÿÿÿÐþÿÿÐþÿÿàþÿÿ@R ÌÇD$üþÿÿàþÿÿÿÿÿÜþÿÿäþÿÿÇ$èÖÿÿÀÆç1ÀþóÿÿÀè!ÆÇEÜàþÿÿÇD$$èÐòÿÀB	EðÀt3ÇD$$èÿÏòÿÀtö÷	Eð$èø³òÿÀtöà	UìÒvt'½àþÿÿGT$D$ÿÿÿ$èÅòÿÀg	UäÒt'àþÿÿ½ÿÿÿAT$<$D$èUÅòÿÀ!	EÜUÄ\ð[^_]Ãt&½äþÿÿMìÇÿÿÿ¸þÿÿW,EìÄÇÄ½ðþÿÿ}ìÇÜþÿÿÿÿÿGÂèþÿÿÀEàµE@½ÿÿÿ	Ðþÿÿ·Gÿÿÿx¹@ìþÿÿ·GöÆuâúÉáúÁ ìþÿÿ·ÀÒ)Ð)È;EPÿÿÿÀnEØµäþÿÿìþÿÿ ÿÿÿÿÿÿÄÀt:UEØD$MàþÿÿÇD$T$¸þÿÿ$èùÿÿÀÆþÿÿ}ìGµàþÿÿEàF|$½ÿÿÿD$<$èÞÃòÿÀÆÐýÿÿäþÿÿ ÿÿÿµàþÿÿÇEìB,1Ò;MØ4$ÇD$ÂÀD$EàÂÇD$T$D$èÃ©òÿÀÆuýÿÿ½¸þÿÿàþÿÿÇD$ÿÿÿ|$B$D$EàD$èEµòÿÀÆ7ýÿÿ}ìÇÿÿÿGÀEàLþÿÿ·GÀÿÿÿt9àþÿÿºÈsÜþÿÿAÀ
}àÿªÇÿÿÿäþÿÿB,PÒqµàþÿÿ½ÿÿÿF<$D$EìD$è£ÂòÿÀhÿÿÿùäþÿÿB(ÇB,Ç@ÿÿÿÇEìÀ1ÀÜþÿÿ½ÿÿÿÇD$ÀÀ$ðè´ÒÿÿÀÆ2üÿÿäþÿÿA,fzUìùBEà}ØµàþÿÿÀàD$4$è,ÌòÿÀÂV
UðÒt}Ø$ÀàD$èÌòÿÀÂ0
EàÇEìÀÆ}GÀ¸EÜÀ}Øÿt
E0öäþÿÿ}Øµÿÿÿ½àþÿÿA,ÒÂ±ÄÇD$ÀD$EàÇD$T$<$D$è§òÿÀÆ1ûÿÿ¸þÿÿÇD$ÿÿÿD$G$D$EàD$è³òÿÀÆÂýÿÿéôúÿÿt&ÇEÜ1ö´&éÛúÿÿvU:ÿûuðöEð½ÿÿÿÜþÿÿ°Ì¾ÄµøþÿÿÇD$Ç$èÑÿÿÀÆúÿÿàþÿÿ¸Èæ½øþÿÿW,àþÿÿÇD$µÐþÿÿAD$AT$D$F $èØÅòÿÀÇÿÿÿÉøþÿÿB,@;BeB(Üþÿÿ¶@Ç$D$àþÿÿèXÐÿÿÀÆÖùÿÿäþÿÿuA,ÇfxEìÔÿÿÿÒt}@;G Û
>àþÿÿÇD$äþÿÿµÐþÿÿBD$BD$A,D$F $èÅòÿÀü½äþÿÿW,Eì@EàÿÿÿÀ/½Ðþÿÿ¹@uìx·VöÄ>
>·F·ÒÀ)Â)Ê9UíüÿÿäþÿÿH,Aä·Qè·@è9ÂÎüÿÿäþÿÿR(9Ñÿÿÿ MÀÇÿÿÿ¼þÿÿéf½àþÿÿÇD$Lÿÿÿ@ÿÿÿGD$GD$B,$D$èÄòÿÀÂ?Çÿÿÿ8ÿÿÿLÿÿÿ½4ÿÿÿµHÿÿÿH,~,Ò§	ÿÿÿÀ1äþÿÿÿÿÿÿÿÿ9P,]
>µÿÿÿ½äþÿÿB;GtÎàþÿÿ½àþÿÿEð	¿ÌlÿÿÿÌq DÿÿÿO,Hÿÿÿ¸½Lÿÿÿµ@ÿÿÿ8ÿÿÿ¶R)ÐÊHÿÿÿkÀÂW,½Hÿÿÿ,·rUÔøA,fµ0ÿÿÿ½4ÿÿÿ·p9ÐEÐfu´þÿÿ1ÒÇÿÿÿéîþÿÿvàþÿÿÀD$@$èºòÿÀÆkúÿÿé'÷ÿÿ´&BµäþÿÿEàB;F0½àþÿÿÇD$ÇD$<$è¯òÿÀÆàöÿÿE@éûÿÿt&µàþÿÿÇÿÿÿ6¾xµÐþÿÿ:öÿÿé)öÿÿ¶ö¶öÿÿÆ¶é©öÿÿvøþÿÿQ,fzèüÿÿuÇEðÇD$$èÆòÿÀÆNöÿÿEð$èªòÿÀÆ9öÿÿUÇéêöÿÿvö×öÿÿf¾t&éÊöÿÿvö¶öÿÿf¾¶é|öÿÿvUG;B Åøÿÿé}÷ÿÿvÇEÜé¸ùÿÿvÆ¶éöÿÿvàþÿÿºÈéöÿÿfÞöÿÿµÜþÿÿèþÿÿ|$½ÐþÿÿÇD$t$t$L$B<$D$èåÄòÿÀÆWõÿÿ}ìéöÿÿuÐf~µÌþÿÿ\B(½HÿÿÿB;GÇ,ÿÿÿ1ö1ÿUÌþÿÿB ;AvèB lÿÿÿlÿÿÿ¸È$ÇD$À¶ÀD$èvòÿMAÀÂüøÀòàþÿÿEÐD$@ÿÿÿÇD$B$D$HÿÿÿÀD$è¬òÿÀÂ2UÐ½àþÿÿ¶B9ÆÀ¶Àè!ÆGT$D$@ÿÿÿ$èGºòÿÀÂõöÇEÐt.UB BB9,ÿÿÿsèB MAÀtèAfäþÿÿEØA,À~ýÿÿEì¶@EàéÂ÷ÿÿt&ÜþÿÿàþÿÿÇD$Ç$è(ÊÿÿÀÆ¦óÿÿ½äþÿÿG,PfxEìUàt÷ÿÿàþÿÿÇD$ÐþÿÿBD$BD$G,D$A $è÷¾òÿÀÆIóÿÿW,µÿÿÿöEì@EàM	äþÿÿEì@;BíÿÿÿÉt4M;A v,¸þÿÿàþÿÿEØÇ$è`ËÿÿÀÂF¶½Ðþÿÿ¹@uìx·VöÄç·F·ÒÀ)Â)Ê9UöÿÿEðÀt$èÖ¦òÿÀÂðEðD$àþÿÿÇD$$è¿±òÿÀÂÉEð}ìÌøþÿÿøþÿÿ·GÄøþÿÿUäÈþÿÿÀôþÿÿEÜÀuàöÐþÿÿ·Wx¹@öÄuàøÉáúÁ ·G·ÒÀ)Â)Ê9UCE@À5äþÿÿA,·Pè@ä·@è9Â]àþÿÿôþÿÿÇD$ÇD$$D$t$ÇD$è¶òÿÀÂÐÈþÿÿµàþÿÿÇD$½ÿÿÿL$F<$D$EàD$è8©òÿÀÂEèäþÿÿD$ÇD$FD$B,@ä<$ÀD$èý¨òÿÀÂWµøþÿÿN,;N0ÉµäþÿÿUè½øþÿÿÇAF,ÇAÇA·@èÇAÇAÀfA·BfAA;G0G,µøþÿÿEäN,fÇA·@fAFAFAFAF ÇAA½øþÿÿEÿÿÿÇEäÇG@Òt3UØuT$UEðÇD$4$T$ÊèöêÿÿÀÂ\O,Uð}M@|$$EàEÜD$ED$àþÿÿèxØÿÿÀÂµäþÿÿEØF,À4ùÿÿ}ìG;EàiýÿÿäþÿÿG·äþÿÿÄEà×½ÿÿÿ¹ÄéNóÿÿµèþÿÿ|$½àþÿÿL$L$t$ÇD$GD$Ðþÿÿ$è«¾òÿÀÆ3òÿÿéïÿÿøþÿÿMØuP,L$EðM4$ÇD$L$èãéÿÿÀÆÅôÿÿéÜîÿÿt&àøÉáúÁ é¯õÿÿt&¸þÿÿàþÿÿEØÇ$èÇÿÿÀÂÿôÿÿfÇEìÖéîÿÿfµÜþÿÿèþÿÿ½ðþÿÿÐþÿÿt$t$L$ÇD$|$B$èñòÿÀÆYñÿÿé>îÿÿ¶àþÿÿEðÇD$D$$èoòÿÀÆQóÿÿéîÿÿt&EØMD$EÇD$$D$àþÿÿèÙèÿÿÀÂ ôÿÿé:ÿÿÿfàøÉáúÁ éûÿÿt&ÿÿÿÀªùÿÿµøþÿÿUð}MF,@|$$EàEÜD$ED$àþÿÿè(ÖÿÿÀÂÎþÿÿµäþÿÿEØF,8ÿäöÿÿ}ì·GÄG;EàYùÿÿéòúÿÿÇD$GµHÿÿÿD$G½@ÿÿÿD$F,<$D$è£¸òÿÇÿÿÿÀÂôÿÿLÿÿÿHÿÿÿB,A,UÔEÐz+ÇpÿÿÿÇPÿÿÿ¼þÿÿUÇÇ@Ç@Ç@1ÀØþÿÿØþÿÿÇÀørëu¤1ÀµÔþÿÿ½ÔþÿÿÇÀørëÇ(ÿÿÿÇÿÿÿéü´&¨·B ¹ }Ô4·W·GÀ)Â)Êú	ÇEF(ÿÿÿu¾ÔþÿÿØþÿÿ·0ÿÿÿ|$½àþÿÿT$L$t$D$<$è©¢òÿÀÂFóÿÿpÿÿÿÒtPÿÿÿ·ÀÆæüÿEÐlÿÿÿt$ÇD$D$$è@òÿÀÂýòÿÿfmäf0ÿÿÿÇÿÿÿÇpÿÿÿàþÿÿ¸Èt4µDÿÿÿUÐxöÄäþÿÿ·B@¹@}Ô4·Wéçþÿÿt&µDÿÿÿMÐxÖæS¸@·½pÿÿÿÿPÿÿÿpÿÿÿ·Ààü}Ôö·OfM¹@uâúÉáúÁ ·W·ð·EÒ)Ð)ÈV9ÐpÿÿÿÉpÿÿÿ·E¨ÈÀE¤PÿÿÿE¨¼þÿÿfEÀ¶BMàEÂBEÄBÇEEÈLÿÿÿöÌuàþÿÿö,
þÿÿPÿÿÿI(ÿÿÿéùýÿÿvEØuD$}àþÿÿÇD$t$<$è±äÿÿÀÂûÿÿäþÿÿP,étöÿÿ·B¹}Ô4·WésýÿÿÐàøÀàúÀ éþÿÿÇÿÿÿuV Òt7EÔ;Ps/½LÿÿÿG,;G(t!àþÿÿUÔÇ$è¬ÁÿÿÀÂÅðÿÿfUÐfzt<MA Àt2;Bs-µHÿÿÿF,;F(tlÿÿÿUÐÇ$èdÁÿÿÀÂ}ðÿÿÿÿÿ1ÒÀmðÿÿ(ÿÿÿÀ8ÿÿÿLÿÿÿJ,ëvHÿÿÿ4ÿÿÿ4ÿÿÿ;J,Eóÿÿµàþÿÿ½4ÿÿÿFD$D$@ÿÿÿ$èq®òÿÀÂu#GÀt°øÀD$@$èÎòÿÀÂtÇÿÿÿéÐïÿÿÿÿÿÉ}GÇEÜéèÿÿ½üþÿÿt$<$è¶òÿÀÂMøþÿÿA,éQùÿÿüþÿÿ|$$èëµòÿÀK÷ÿÿøþÿÿJ,éx÷ÿÿPÿÿÿ·E¨ÐÀE¤é\ýÿÿ·Ààüéîüÿÿuàþÿÿ4$èÊÿÿÀÂïÿÿUÐàþÿÿ4$èæÉÿÿÀÂõîÿÿuÔ~úÿÿDÿÿÿ·~x`ÿÿÿ%\ÿÿÿ¹@·F·ÿµHÿÿÿÀ)Çv()ÏHÿÿÿµdÿÿÿI,<ÿÿÿé;dÿÿÿrfytî¾@Xÿÿÿ\ÿÿÿÀu`ÿÿÿàøöæúÆ ·AXÿÿÿF·ÈpÿÿÿÆ·ÀàüÀ·À9ÇÉMÐfÇ2ÿÿÿ·qÌþÿÿpÿÿÿfþfµVÿÿÿPÿÿÿ)Ç`ÿÿÿ¾fÇ2ÿÿÿàÀþÿÿë"t&f2ÿÿÿÆ·2ÿÿÿf9VÿÿÿvK)Ç\ÿÿÿ¹@Àu½ÀþÿÿÉáúÁ Ìþÿÿð·ÌþÿÿPÿÿÿ·ÀàüÀ·À9ÇsµÌþÿÿ·½2ÿÿÿ·vf9þfua<ÿÿÿètÿÿÿµDÿÿÿ½dÿÿÿ9½tÿÿÿ6µ$ÿÿÿÞ`ÿÿÿtÿÿÿá|ÿÿÿÄþÿÿfµ|ÿÿÿ¹@>µ\ÿÿÿ·Göu½ÄþÿÿÉáúÁ ·ð·GÀ)Æ)Î;µ$ÿÿÿsi\ÿÿÿ¹@Àu½ÄþÿÿÉáúÁ |ÿÿÿ·@fzÿÿÿ·ÀA·8Pÿÿÿ·À%üÿD9$ÿÿÿv$ÿÿÿf½zÿÿÿu|ÿÿÿµdÿÿÿ9µ|ÿÿÿ?ÿÿÿ·½2ÿÿÿf9}b\ÿÿÿ¹@Àu`ÿÿÿàøÉáúÁ ·2ÿÿÿµÌþÿÿ·½2ÿÿÿA·0f}ðPÿÿÿf}ÒëÿÿPÿÿÿ·À%üÿÀ9$ÿÿÿp÷ÿÿµ`ÿÿÿæë+¶·ÀÈPÿÿÿ·À%üÿÀ;$ÿÿÿ:÷ÿÿ\ÿÿÿ¹@fmÀuþÉáúÁ ·Ef}AÌþÿÿ·u¤é@ëÿÿ`ÿÿÿàøÉáúÁ éküÿÿEØuD$MUìàþÿÿÇD$4$L$èdÞÿÿÀÆbãÿÿé6ûÿÿÂvé»ôÿÿ<ÿÿÿéfytÿÿÿöÿÿéýÿÿtÿÿÿ0f~pöÿÿ\ÿÿÿ¹BÀu`ÿÿÿàøÉáúÁ"½tÿÿÿ·GA·0PÿÿÿéþÿÿµÌþÿÿ½lÿÿÿt$<$èËòÿÂÇÿÿÿéoêÿÿ½Lÿÿÿàþÿÿ(ÿÿÿo,$D$ètòÿÀÂFúÿÿHÿÿÿ÷(ÿÿÿµ(ÿÿÿ½lÿÿÿi,t$<$èVtòÿÀÂúÿÿHÿÿÿ@,éùÿÿuÇG¹ÄEà½ÿÿÿéæÿÿ1ÒéóÿÿfzóìÿÿàþÿÿÇD$$è5²òÿÀÂ³ùÿÿG(MÐ¶pG,Ìþÿÿö@äÂ×@,ÿÿÿé´ìÿÿf}ÐµPÿÿÿfÇ2ÿÿÿ½ÌþÿÿéÙûÿÿN,éÆðÿÿvþéáÿÿµhÿÿÿféáÿÿvUåWVSìEèó´òÿÃ4pUMÿÿÿ@ÿÿÿ1ÀÿÿÿÇÀørë|ÿÿÿÿÿÿ1ÀÿÿÿÇÀørëÒÇEðÇEèÇEìÇEäÇEàÇEÜtDE ÿÿÿD$ÿÿÿD$BD$ÿÿÿ$D$T$è_òÿÀÿÿÿë}Ç ÿÿÿÿèf÷EÀÇ$ÿÿÿÒ÷E@tMµ ÿÿÿö´ÿÿÿE1ÿÇD$D$ÇD$$è¡òÿÇ$ÿÿÿÀÿÿÿu1öEÀæµÿÿÿÇD$$è zòÿÿÿÿÿÿÿÇEÒ½EÀtD$ÿÿÿ$èë òÿ|ÿÿÿÀtÿÿÿD$$èÏ òÿf}ÞEÔÿÿÿÿÿÿMØÇEÔÇEìÿÿÿÀEäÀtD$ÿÿÿ$è} òÿÿÿÿEÿÿÿÇD$T$UD$L$B $è,òÿÀÿÿÿÒuÿÿÿEÇE´ÇEÄÀEÈL1öUB $èhªòÿE´ÀùEÄÀt$èòÿöÿÿÿÄ[^_]ÃEàMD$EÜUD$EäD$EL$$D$ED$è_òÿÀceÿÿÿÿÿÿ ÿÿÿÉÿÿÿÀt~1ÿ1öÇ$ÿÿÿ ÿÿÿÀþÿÿÿÿÿÒDþÿÿEìÀE À.þÿÿE U ÿÿÿÀD$ET$T$$D$ED$è}òÿÿÿÿéòýÿÿfE÷E@@$ÿÿÿþÿÿ´&U1ÿUHæÀMAÀuÇAÿÿÿÿEUM@ RI(ÿÿÿED$ÿÿÿ,ÿÿÿÿÿÿ0ÿÿÿÿÿÿD$ET$$D$ED$èÑ|òÿÀÿÿÿ?ýÿÿµ ÿÿÿöteED$ÿÿÿÇD$ÇD$$èTòÿÀÿÿÿýÿÿUBÀt(D$EÇD$$èusòÿÀÿÿÿüÿÿvEðM1öD$EÇD$$D$èqòÿÀÿÿÿ?þÿÿUìMT$UEð|$$T$UèT$ÿÿÿèZÛÿÿ=íÿÿÿÿÿ1öEð$èxòÿÀìýÿÿÿÿÿÒÞýÿÿÿÿÿéÓýÿÿvÊÏM¯Ð¸ëQ÷âAÁê)×Àgþÿÿé[þÿÿf÷E@iüÿÿL$EÿÿÿMÇD$D$T$A $è´òÿÀqEìÀ+üÿÿE`ÿÿÿÇEÄÿÿÿEÈ1ÀÿÿÿÇÀørëEÈÀaÇ@ÿÿÿEÈÇDÿÿÿÇHÿÿÿüþÿÿ@ÿÿÿÀt2üþÿÿMÇD$ÇD$T$A$èmòÿÀÆ¿EÄD$EÈÇD$D$E$èÂòÿÀÆEÄMÌ1ÿÿÿÿÌLÿÿÿfDÿÿÿHÿÿÿT$ÿÿÿ$è±ÿÿÀÆH=óÿÿE`ÿÿÿÀtUD$B$èòÿDÿÿÿ1ÀÿÿÿÇÀørëÇHÿÿÿLÿÿÿR9úPÿÿÿª½Pÿÿÿ½PÿÿÿEÄé^ÿÿÿ¶}Üÿ÷E@øeÿÿÿÇÿÿÿé|ûÿÿfE´D$EÄ@$èM~òÿéëúÿÿt&EÈ$èoòÿt&ééúÿÿvMö{¤úÿÿEÈ1öÇD$D$ÇD$A$èØòÿÀEÄD$EÈÇD$D$E$è/òÿÀúÿÿE´D$EÄÇD$ÇD$ÇD$ÇD$$èUòÿÀ%úÿÿéúÿÿt&MEÐD$uä|$A $èòÿÀÿÿÿþÿhúÿÿUÐvÆÂïUÐuîéKúÿÿExÁèà ÿÿÿéþ÷ÿÿ¶UØMà$ÿÿÿMB )$ÿÿÿ$ÿÿÿAEð@T$UD$B $èWòÿÀ;ùÿÿé&ùÿÿ¶EÇD$$èÑròÿÀtÿÿÿÒuÿÿÿÇEéµùÿÿt&$èdmòÿÀøÿÿÿÿÿÉô÷ÿÿÿÿÿéé÷ÿÿ´&1À½ÿÿÿÀè!ÿÿÿéXùÿÿ ÿÿÿÉoûÿÿE¾0ÿÿÿ,ÿÿÿ@P(ÿÿÿHÿÿÿP E D$EL$L$D$|ÿÿÿD$ÿÿÿ$èùvòÿÿÿÿéûÿÿfELÿÿÿ@B,EÌ@;BPÿÿÿ±uÄEH ¾ÈB4ÿÿÿÌ8ÿÿÿB,8_4ÿÿÿ¹>xöÄuàøÉáúÁ·GA·8¶B$øÎÿÿÿhÿÿÿD$L$·L$D$BD$8ÿÿÿ$èvòÿÆö0EÄÇD$$è¦òÿÀÆLÿÿÿPÿÿÿ;J®EÇHÿÿÿ;H üÿÿDÿÿÿEÄÇ$T$ÿÿÿè¬ÿÿÀÆ¿LÿÿÿUA,EÌ@;B PÿÿÿD¸D$EÄ$èü¥òÿÀÆ~½@ÿÿÿÿtMPÿÿÿ;A w½PÿÿÿÇHÿÿÿéPûÿÿÇHÿÿÿ¶EÄ$è¹òÿÀÇu-µ@ÿÿÿÇEÄöúMPÿÿÿ9PúÿÿþEÄÀt9ÇD$$è]¥òÿÀÇöu{EÄÀtl$èPòÿÀÆt^ÿuZf@ÿÿÿÉtEÈÀt$èKjòÿÀÿÿÿtötµÿÿÿ`ÿÿÿÀRõÿÿMD$A$èÖòÿé;õÿÿt&þë¤t&÷¶éxÿÿÿv9PÿÿÿfwZ·OfÉf>ÿÿÿtJ1öt&4ÿÿÿx¹@öÄuàøÉáúÁ ·ÆÆA·DÄf9µ>ÿÿÿu¼hÿÿÿ8ÿÿÿD$ÿÿÿÇD$$D$ÄÿÿÿD$T$èsòÿÆéoýÿÿ´&ÿÿÿÂhÿÿÿD$L$BD$BL$D$FD$4ÿÿÿ$èfòÿÆé#ýÿÿvEÄÿÿÿÇ$èû«ÿÿÀÆ9þÿÿM1ÀPÿÿÿ;Q ýÿÿéýÿÿEÈÇD$$èñmòÿÀÆþÿÿÇEÈéÝýÿÿUØ1ÀzÀEìEð@T$UD$B $èòÿÿÿÿéY÷ÿÿMö{÷ÿÿÇEÈÇ@ÿÿÿé÷ÿÿEÈ¾ÇD$UÇD$@D$B$èòòÿEÈÇD$MÇD$@D$A$èÊòÿéùÿÿUåEÌEÌB@A@BDAD·BHfAH·BJfAJ·BLfALB`¨tI`B`¨tI`1À]Ã¶¼'UåVìE°ÌE$D$ED$ÿQV8#BL;BHv#BPÄ^]ÃUåWVSìUEèC¥òÿÃ`RÇ,UèÀMMäët&MBH;AHuUäUäÜ@ÒuàUä1ÿMÇEðBH;AHÂt&UB$ÀBEä°èöuësvvötiÌU9Puë}ÿÿt	·@;EuÙFÀt*öt!@ÀtM4$L$è_vòÿÀu¯´&9}ðv{M4¸vÇöuUB$ÀÛMäØÉMätUAH;BHCÿÿÿMè,À29}ðÁUÇEìÇ¸EìÄ[^_]ÃvEEð
>D$EðÁàD$UB$è¡òÿÀEìWÿÿÿMA$ÀåUè,À¢EìÄ[^_]ÃD$Mè$èÝbòÿÀ§þÿÿÇEìÿÿEìÄ[^_]ÃD$B$èòÿÀÿÿÿëÕ¶ED$UðD$MA$èòÿÀEìÿÿÿEìÄ[^_]ÃD$$è_bòÿÀÏýÿÿëD$$è)òÿÀJÿÿÿégÿÿÿD$$èòÿÀºþÿÿéNÿÿÿD$A$èôòÿÀÿÿÿé2ÿÿÿt&¼'UåWVSì|EMè¢òÿÃÄ]ÌPE¼EM¸UÄ@ÀEÈtxÀ÷Ð!EÈUÄ,ÀU}w}o¸Ä|[^_]¶Ã}5}uÝÇEÐM¼MÀëM¼BH;AHuUÀUÀÜ@ÒuàUÀM¼ÇEØÇEàBH;AHëU¼B$ÀbEÀ°èöuévö;uftî¾Èuå¾ÌöG`tÙM¸Q;WuÎ·Af;GuÄO\;MØr¼EÀt
E¸·@Hf;GHu¨FÀt#öt@ÀtT$4$èsòÿÀuO\vÁMØöxÿÿÿt&U¼B$ÀEÀØÀEÀtM¼@H;AHÿÿÿEØEàMØU¸ÇEÔJ\E¼EÜët&M¼BH;AHuUÜUÜÜ@ÒuàUÜM¼ÇEÌBH;AH,·EfE¶´&U¼B$ÀBEÜ°èöuéÐvöÅ;uftî¾Èuå¾ÌU¸O;JuÔ·GføÿtÊVÒt+öt"RÒtL$4$èãqòÿÀu£·G´&UÈÒtMÈ;NtÇEÌMÉ?}Ô·U¸f9BèfGf;BOÿÿÿöG`EÿÿÿvMàO\ö?ÿÿÿt&M¼A$ÀrUÜØÒUÜtM¼BH;AHãþÿÿUÄ,À0}Ìÿ£Mqö@pÒö-uy|Àt@<Àt	öøu_EàD$(UT$$ML$ U¸·BHD$ML$·BD$BÇD$D$EìD$EÈD$U¼$è8òÿÄ|[^_]ÃÄ|1À[^_]ÃfU¸f9B+þÿÿ}ÔÉ·M¶f)OLM¸·GH·QHf9Ðvvf+E¶fGHf;AH÷ýÿÿöG`íýÿÿEàG\éâýÿÿfÚýÿÿG`¨t&ÊýÿÿÈàïG`EàG\é¶ýÿÿU¸f9B¡£ýÿÿÀfGt&éýÿÿMÐÉ¶ýÿÿf9ÐyýÿÿG`¨nýÿÿUàÈG`W\é]ýÿÿt&·M¶fOL·BH·OHf9Áåf9Áv·E¶ÈfGHé+ýÿÿUÐÒ ýÿÿf9Áýÿÿ´&ëÔ¶W`öÂfWÿÿÿM¸G\I\9ÈM¬½àüÿÿ+E¬fGG\éÐüÿÿD$MÄ$èm\òÿÀ§üÿÿét&D$EÄ$è-òÿÀwýÿÿéæt&ÇEÐÇEàÇEÔvéþûÿÿÇEÐt&é«úÿÿÇEÐëÑöB`¶ÿÿÿW`öÂt&ÿÿÿG\E°E¸H\9M°uIâýW`éüÿÿD$MÄ$èòÿÀ]ûÿÿëWt&D$MÄ$è[òÿÀúÿÿë9´&ÚûÿÿE°·U¶fWHÀ)ÈG\éÂûÿÿD$$èBòÿÀ¼üÿÿ¸ÿÿéÇùÿÿD$$èD[òÿÀùÿÿëà´&¼'U1Àåì]ôè·òÿÃøVuøu}ü}ÇÀørñE98r U~1À]ôuø}üì]Ã´&UE|$T$$è>òÿÀuE8ë¿´&UÇë¹t&Uåìuøu]ô}üè òÿÃaV¾ÌG<ÀtD$@$è¡òÿ|$@$èòÿ]ô1Àuø}üì]Ãt&Uåì8}ü}]ôuøèÀòÿÃV@ÇD$dÇD$EàEðD$Eà$è¥uòÿÀÆtð]ôuø}üì]Ãt&EðÀ<D$D$Eà$èzòÿÀÆñEðÌØûÿÿôÐÀûÿÿøÔ|ûÿÿüØüÿÿÜ üÿÿàûÿÿèøûÿÿì¾üÿX¼üÿx®üÿ©üÿx¸üÿ HËüÿ$x«üÿ(<$èÒòÿÆéÜþÿÿ´&EðD$Eà$èòòÿé¾þÿÿUåì(uüu]øè3òÿÃtTö,u}@öôuolÀteÌJÉtz$tRBEèBEìBEðB ÇD$4$Eôè¶òÿÀu(}ôt"UèÒvtEèD$@$è®iòÿë1À]øuüì]Ãt&UåWVSèòÿÃÍSì\EÌUÈUÌEàºÌ$èlòÿÀÂt
>Ä\Ð[^_]ÃUÈMOPBD$D$MÌ$èKòÿÆG@G8EÐF$èuXòÿUÐMt`wL$EÌ$è©kòÿÀÂuUfÿÇ+WMðUÜMÀGÀEØ!OPÉMÔëGTÀàGMàEÄÆ·Px¹@öÄuàøÉáúÁ EÄ·Ò·@E¼À)Â)Ê9UÔsUØuÄfÇGXÿÿWTt&MÜL$EÀÇD$D$UÈt$T$MÌAD$Eà$èÞkòÿÀÂ¾þÿÿGT;GtHEðÀtqG@ÀtWfÇGD$EÌ$èòÿÀÂ	ÿÿÿÄ\Ð[^_]Ã¶wépÿÿÿ·GfGXë®¶fÇGg`ïéÆþÿÿO`@ºóÿÿé@þÿÿfMàO`wx¹BöÄuàøÉáúÁ"·GA·08üýÿÿ@Méïýÿÿö¼'UåìXE]ôuø¾óÿÿ}ü8Ìè#òÿÃdQW öA`MÈUÄtð]ôuø}üì]ÃE$è©[òÿÀÆtWMÈQÒt-MAT$D$EÄ$èPòÿÀtöuÆUÈÇBM$èáòÿÀtöuÆvë¶EÇD$$è)iòÿÀÆuEÈ¹BPxöÄEÈ·@A·<dÿÿÿUÇD$MÄBD$B$D$EÈÀD$èCòÿÀÆ%UÈöB``·JHfÉfMÂ*·BJxrÀEÌ·BÊâUÐAöÁm·Àº<·D>èf+:·À9EÌ'·EÂUÌÇEð ÇEÜEèEÐUäºBÀuáùÒâúÂ"MÈ·AB·0ÇD$D0EØEØD$E$èàtòÿÀÆCþÿÿUÈM·BLJ`èf+BJfBLÇD$ÇD$·BJ$ÀD$èTòÿÆt&EÈPéüýÿÿt&àøÉáúÁ"éhþÿÿUÈx·BJrÀEÌÈ%EÐéÿÿÿUÇD$$è¹mòÿÆéýÿÿ·ÀºB<·D>@éÃþÿÿMÇD$$èmòÿÆEÈPépýÿÿ·Àº"<·D> éþÿÿ¶¿Uåì]ôè)òÿÃjN}ü}uø<$èÇXòÿÀÆtð]ôuø}üì]Ã¶<$è¨ùÿÿÀÆt"<$èòÿÀtÑöt&uÉÆt&ëÁ¶ÇD$<$èÜlòÿÆëÊ¶¿UåìHE]ôuø}ü0èòÿÃÏM¸ÌV }ÌÇD$$UÜèfòÿÀEàuQO·Gf;AfEÒrRUÇU}ÌBD$GD$EÜ$è®òÿÀt
>UàÒuEàUÌÇBEà]ôuø}üì]Ãf¾xø%EÔtFºB·EÒÀEØÈ·¶<tR<t>,t:UÌBD$F$èùòÿEàédÿÿÿt&øàøÒâúÂ"ë¶¹}é8ÿÿÿuÔötA}Ø·t9B·ÆT·D9@è1Éf)ð·À49ò}òsÅ·ÁT9Öfwïë²t&çuUØ}Ø·t·ÆT·D9ëµfEØ}Ø·t"·ÆT·D9 ë´&UåWVSì|E°U¬U°èÞòÿÃLE¸x²Ìº@öÄ~·N}¨uàøÒâúÂ }¨A·ÀE´B·8¶út$}t}	t}
>t&t1ÒÄ|Ð[^_]ÃfF`¨UEèø¼F`¨M¸V¹xU¼ø%EÀôºB·FE¼È·U¼E¤:XBEÄEÀÀçU¼·D
>ºM¤è}¸f+W·ÀEÈÒûM¬EÄ}¸D$L$<$ÿÒEà}àºóÿÿÿÿÿÿE°ö,ÿÿÿM¬QöÂýþÿÿöF`Ï/U°M´BL$M¸|$PT$U°D$E¨D$B$D$è3òÿÀÂ±þÿÿM¬IGAéþÿÿ´&ú¢þÿÿÈF`E¸¸x÷ÇU¨·Á·D
>@ºBU¨èf+
>÷ÇºBfFLuçÿÒâúÂ"·FM¨B·ÏÇ}tx}tr}tl·GfEòfÇFH·EòfFJEèøÍþÿÿéþÿÿf÷ÇU¨·Á·D
>ºécÿÿÿt&øàøÒâúÂ"éüýÿÿvEòfÇFHE t&·FHU ·DfÂÁfVHBf;FLfFHrÜf)ÊfVHébÿÿÿ}¼ºB·D@éíýÿÿ¶U¨·Á·D
> º"é×þÿÿBM¬}°EäBU¸EìEàD$BL$D$EäD$EìD$G$D$èèòÿÀÂ¸ýÿÿéáüÿÿt&}¼º"·D éeýÿÿ¶M¬}ÄEÄAEÈAEÌAEÐAEÔAUÜEØÐ¨ tUÔ·NJ9ÊÇEÐë¶È 1ÒEÜ·FJÇEÔEÐ·FHDEÔé[ýÿÿfE¬<$D$EÄD$èOòÿéýÿÿ}	tGEàMD$Eè}¬D$E°L$|$$èXòÿEèf`þfFHéÆüÿÿÐEÐ9Ás)ÑMÐëÈF`ë±´&UåWVSì<Eè6òÿÃwGÂ°ÌH@ MÜEà,$%øÀÀEäè±QòÿÀÇ¶UÇFPêúUÔªU¸ÉþÿMÜD$T$$èòsòÿÇë:fN` MÌ@ÀEUäMD$T$$è+pòÿÇt&EÔÁàEÐÿEËÿóÿÿÂÒÀ}Ë¶U$èwòÿÀtÿuÇf`ÛÄ<ø[^_]ÃvðÉþÿØÿàt&N`EUäMD$T$$èòÿÇé|ÿÿÿt&N` UÌ@Àt$MEäUL$D$$è/gòÿÇéDÿÿÿt&MEäUL$D$$è[oòÿÇé ÿÿÿF`Àå¨@v}Ô¶ÿÿÿMÐHÊþÿØÿàt&¿ëÿÿéÿÿÿÇF´&¿óÿÿéðþÿÿ¶UMàBD$F$D$è¨|òÿÇFÇF@Àt¶n@F8V@f`ïEØÐÀfÇFÿÿUè$èAJòÿMØL`MèÿEèF^þÿÿUMäET$L$$è@òÿÇé>þÿÿt&UMàBD$F$D$è|òÿF@V@f`ïÇFÇF8fÇFÿÿUðEìÐÀ$è¸IòÿMìV8L`MðEðFF@;BHçþÿÿÿÆýÿÿUMäET$L$$èeòÿÇé¦ýÿÿt&EäMUÇ$D$EL$è`ðÿÿÇéqýÿÿN`éþÿÿ´&öF`t&jþÿÿUMäET$L$$èÍeòÿÇé2ýÿÿfUÀMýÿÿMUE$è÷ÿÿÇé5ýÿÿvÐÉþÿ¿D$EÜ$ècòÿéýÿÿUåì8U]ôuø1ö}ü1ÿÌèDòÿÃCÇEð@ MàÒEÜ5u4$èÎMòÿÀÆt$M$èmòÿÀtöuÆð]ôuø}üì]ÃUöznºMT$$èn[òÿÀÆ8UuàºBNxöÄuàøÒâúÂ"uà·FB·85ÇEUàUðT$U$T$ÿÀÆÈEðÀ½MÇD$uÜAD$A4$D$EàÀD$è;òÿÀÆE¿ÇD$$èaòÿÆvMàQÒt&MAT$D$EÜ$èQyòÿÀt	öuÆvÿ¶þÿÿU$èÛròÿÀþÿÿöþÿÿÆt&éwþÿÿvMà¿QÒuë·´&ÌºÌöÌwþÿÿémþÿÿv@EéÇþÿÿt&UåWVSìÌEUè òÿÃaAfÇEòÇEàp xÿÿÿEMµ|ÿÿÿÌEÐÁèàE¬#¶ÂøÇE´UøMÀ¶ÀE¸fÇEfÇEÇEUuUØQMÇEäÇE¼tü,uÄuè%øEöêÆUÜUäuE `ÿÿÿMxÿÿÿq·yx¸@uöÅuÈàøÀàúÀ EÇE°E´&E¬ÀUu·×UÀÒUÈÖµhÿÿÿöÅ¸BuáùÀàúÀ"hÿÿÿ·EEÌ¶<ô&<ïE°À©UuØ·BUu )Â;UÜUàlt&fÿWxÿÿÿïxÖæuÐw¸BE·Ï4	·HEE¤8îufÇEòfÇEfÇEf`ïuÄ;uè¡Eö-U·Eò·M·ufzfBJfJHfrLEèÇE¼ÇÿÿÿÿE¼ÄÌ[^_]Ãt&¶ÂÇE´éáýÿÿÎæª¸@·×UÀÒUÈUUÈhÿÿÿ·UÂ:äE°ÀÜEØUE ·BU)Â;UÜUàMÄ9Mè¿þÿÿuàuEUÇE¼éÿÿÿ%üÿÿBéHÿÿÿfET$D$M $è^^òÿEà)EÜEØuF`¨ó·FJ·VLÇE¨fEò·FHfUfEEuÀtpEòµtÿÿÿdÿÿÿvu¬EÜöjºèUàUEÜ;BjU¬ÒtEèu0UäPüèEèE¨À¢tÿÿÿ¸+Euè·M·I)ÊU ÐxÿÿÿFüTÿÿÿEèxöÄ5¨õEMÈÇ\ÿÿÿ·LfZÿÿÿ·Zÿÿÿhÿÿÿ\ÿÿÿèf+·ÀFüTÿÿÿèEèuÇE°f`ïE´À³ýÿÿMÇf;ydµxÿÿÿxéüÿÿv<uÍUÌuMÜBVEìAø9ÐEÜìüÿÿE¬ÀÑAð9ÂEÜÓüÿÿUèErøEäuèBüM¸EÜD$EØD$EèD$L$T$ED$EìD$U$èbsòÿÀE¼<ÿÿÿ=éÿÿýÿÿEÜÇEÜEàE¬À»üÿÿ;uè²üÿÿFEèéDüÿÿt&ET$D$M $è\òÿµxÿÿÿEà)EÜEØxÎæfÿ·Et#ö¸>uÈàøÀàúÀhÿÿÿ·öº@uáùÒâúÂ hÿÿÿèuÈÇE°f+UM·ÀEä·2·Qµxÿÿÿ)ÐU +UxTUéûÿÿ´&ÈàøÀàúÀ éFüÿÿvÐàøÀàúÀ"éyûÿÿv}¬UÜMÀàøÀ)Â;QUÜ(ûÿÿuÌFEàFUà;UÜEì
ûÿÿEØD$EìT$D$E$è|OòÿÀE¼ûÿÿE¬ÀtEèUUäPüèEèUèEØ+EEàBüêEàUèEØ)EÜéfýÿÿt&·EòU·M·ufBJEìfJHfrLpÿÿÿD$UT$M$èbtòÿÀE¼:=óÿÿþúÿÿuFD$UBD$|ÿÿÿ$è*qòÿÀE¼Ñúÿÿu~@ÇFÿvfÇFÿÿuÄ¿ÿÿÿÿ;uèfúÿÿ´&UÇE¼éÿÿBEàÿ+EÜ%üÿÿBE¼ÄÌ[^_]ÃfUE·u·Mfx·EòfrLu¼fJHfBJö1úÿÿEf;x$úÿÿUìlÿÿÿT$ML$u4$èCZòÿÀ=óÿÿUBD$MAD$@ $è/pòÿÀE¼ÖùÿÿuEÇF$è?CòÿÀE¼¶ùÿÿUF@z8pr@;wHB@ÇE¼óÿÿM$èiòÿÀM¼É¨ÇE´éä÷ÿÿvºèUàUEÜ;BúÿÿM¨Éøÿÿf}øÿÿEè·Mf+HÈèfEéÒøÿÿ´&UEÈÇ\ÿÿÿB·D@fZÿÿÿéÎúÿÿ´&tÿÿÿº+Uuè·M·I)È·ME ÂT
>UÌFüEè·D
>dÿÿÿf·U·MT·ÀFüîf9ÊfUuèúÿÿE¸Àùÿÿé{úÿÿEÐÀvrâ´&ªE·T0"¸$é]E$è¹AòÿÀE¼0øÿÿUB@z8pÿr@$è7<òÿMfÇAÿÿt`qu4$èügòÿÀE¼ó÷ÿÿpÿÿÿD$U4$T$è(qòÿÀE¼Ï÷ÿÿM·yéx÷ÿÿt&B`ÿÿÿBUä;UÜEìUà%øÿÿEØD$EìT$D$u4$è_KòÿÀE¼v÷ÿÿEØUäµxÿÿÿ)UÜÁ+MÐEØMxé2öÿÿUEÈÇ\ÿÿÿ"·D fZÿÿÿéùÿÿ´&MÌ9ÄfÇEòfÇEfÇEÇE¨éøÿÿ¶E·T0B¸DEê·4Hf)òfUU¤·M·BfMfEòéuöÿÿfuè1ÒéGùÿÿ¶E·T0¸ë¶À$è±:òÿMòµlÿÿÿfÇAÿÿT`a`ïQt$ED$U$èVòÿE¼éÅüÿÿvuÈxÿÿÿF`·AfEòxöÄt6u¸BMÈ·T@hÿÿÿêfÇEÇE¨·f)ÊfUé÷ÿÿ¨tu¸"MÈ·T ëÄE¼éàõÿÿu¸MÈ·Tëª}¼óÿÿÁõÿÿé¬õÿÿ´&¼'UåWVSì<EMè`yòÿÃ¡4ÌP öA`ÿÿÿÿÿÿÿÿÿt(}
t"}¾óÿÿt´&Ä<ð[^_]Ãvu4$è¹>òÿÀÆuß}uuÃÉþÿD$t$ÿÿÿB$èaòÿÇÿÀÿÿÿuÇATfÇAXÿÿÒDÀ<ÇD$UBD$BD$ÈÀD$ÿÿÿ$èpòÿÀÇ}t/Eè
øÍµÿÿÿ¾xÄEö@·Uu¶ÌJöF`$ÿÿÿµÿÿÿ ÿÿÿÓEö@ X	µÿÿÿE·VL·~J)úPF8@Áè9ÂH$ÿÿÿPÒx¹BÿÿÿöÄruàøÉáúÁ"ÿÿÿ½tÿÿÿ·PH·@A·1TpÿÿÿpÿÿÿD$UT$$ÿÿÿ$ÿQÀµ$ÿÿÿvµ ÿÿÿEUÀ`D$EÀXD$øþÿÿT$ML$µ ÿÿÿ4$èîJòÿÀÇÿÿÿu·BH·RJEBEF9Ð(
)ÐÇD$ÇD$D$E$èÞ6òÿÀÇuLÿÿÿVÐf+AJfALµÿÿÿøþÿÿfVJE¶ÇD$ED$U$èWòÿÇt&ÿÿÿQÒt`uFT$D$ÿÿÿ$èÃhòÿÀt3ÿuÇþM$è\bòÿÀýÿÿöøüÿÿÆÄ<ð[^_]ÃÿÿÿÇBÿuÂÿÿÿöA`t¶uU6ÌF µ@ÿÿÿHÿÿÿ<ÿÿÿÇD$M$èCòÿÀÆ[ÿÿÿ``÷þeÿÿÿUBÀWÿÿÿéPÿÿÿt&¶M¸Óà¨J½©`müÿÿÿÿÿuB8N¾PÁê9ÑwqEH¸9ÊrAUðÇD$$T$UEèxÜÿÿ=óÿÿÇ}(üÿÿÿÿÿöA`üÿÿu¿ìÿÿÀoþÿÿD$E$èlIòÿÇ¸ÿíûÿÿéLþÿÿt&UÇD$T$M$èªQòÿÀÇÀé¾ûÿÿf})üÿÿML$ut$ED$U$èr4òÿÇéïýÿÿ´&µHÿÿÿÇEÄÇEäV8BrPUèEÜBH;BLµDÿÿÿHÀ¶À4ÿÿÿ,ÿÿÿ$èX4òÿ,ÿÿÿÒ8ÿÿÿHÿÿÿ8ÿÿÿr8DdµLÿÿÿÀ@ÿÿÿÇ0ÿÿÿö{Eè¹@ ÇEÔÇEØÀEàE@ÀXÿÿÿ7U@¸p"ö-|Àt@<Àt
öø÷UèB L$,MÔL$(D$0Eàt$ D$$FT$D$EÜD$FHÇD$L$D$XÿÿÿL$µ@ÿÿÿ4$èöIòÿÀ\ÿÿÿÄHÿÿÿp8vEÔUØ,ÿÿÿVÀt8ÿÿÿÂÿÿÿÀÑMØEäUÔHMQD$T$µ<ÿÿÿ4$èódòÿÀ\ÿÿÿuUHÿÿÿ4ÿÿÿÇEäP8,ÿÿÿJHÀtBLBP	ÈBLµ4ÿÿÿt$Dÿÿÿ!Æt$U$èêcòÿ\ÿÿÿµ0ÿÿÿöt6MAD$EèD$µ<ÿÿÿ4$èkdòÿÀÆt\ÿÿÿÉt
´&µ\ÿÿÿUÄÒëµ`ÿÿÿUäÒt0MAT$D$µ<ÿÿÿ4$èdòÿÀÆt`ÿÿÿÀ×ûÿÿµ`ÿÿÿéÌûÿÿ´&ÿÿÿATÀtK;AtFuFD$AD$ÿÿÿ$èÃcòÿÀÆûÿÿÿÿÿBTÇBfÇBÿÿBt&MöA tQÒ¯EÇD$D$ED$U$è÷bòÿÇétúÿÿHÿÿÿ@8Lÿÿÿ4ÿÿÿÀ$è1òÿµLÿÿÿD`4ÿÿÿEàEäD$ÇD$UBD$EàD$<ÿÿÿ$èÿTòÿÀÆ§þÿÿEä1ÉÇ0ÿÿÿ@UÔEØHÿÿÿp8é¶üÿÿÇEÔÇEØémýÿÿUöB  ùÿÿMµÿÿÿøþÿÿEBEBEBEBEBE BÇEE¤$ÿÿÿM¤ ~°xòâTÿÿÿºBÿÿÿ·A·üþÿÿ89TÿÿÿÀyæ·D º"üþÿÿèµøþÿÿf+u·ÀEéÍøÿÿE}¨À`D$EÀXD$Q|$T$µÿÿÿF$èfFòÿÀÆåøÿÿUBÇD$D$E¨$è/:òÿMU¨ÎQF	$D$L$è?JòÿøéÓýÿÿEÄD$E$è6òÿÀ`ÿÿÿõüÿÿöóüÿÿt&éäüÿÿU1ÀÿÿÿÿÿÿÇÀørëÇ$EÊèzÝÿÿÀÇøÿÿMuQµÿÿÿ·ÿÿÿfµ*ÿÿÿ9ÖfEòl·AÐfEòµÿÿÿ·MòV8·FLR+ÿÿÿÁê9ÐE$è0òÿÀÇ÷ÿÿÇD$UT$MÇD$$L$ÿ$Çé`÷ÿÿFHEàEäD$ÇD$MAD$EàD$µ<ÿÿÿ4$èRòÿÀ\ÿÿÿvûÿÿHÿÿÿuàÿÿÿP8ð+4ÿÿÿ+BHMèq EÔUØEäQpµ@ÿÿÿÇ@Ç@fÇ@Æ@fPEäÆ@
éúÿÿEÄÇEÜD$ÇD$ÇD$ÇD$ÇD$M$èªEòÿÀÆûÿÿEèD$ÇD$uFD$EÜD$<ÿÿÿ$è2QòÿÀÆÚúÿÿHÿÿÿÇ0ÿÿÿr8éÚøÿÿU$è.òÿÀÇöÿÿÇD$ML$uÇD$$t$ÿ$ÇéßõÿÿÉþÿ¿D$ ÿÿÿ$èNGòÿé½õÿÿðàøÒâúÂ"éSüÿÿ·D@ºBéüÿÿEìD$AD$µ$ÿÿÿF$èLòÿÀÇpõÿÿpÿÿÿÿÿÿ1ÀÿÿÿÇÀørëUì·EòM zfMuA9ÆvÆt$E47<$D$èãFòÿUBU9Ðv)Ð4$D$ÇD$è6òÿMq+uE@4$T$D$èFòÿEpP@µPÿÿÿu<9÷s#})Ö)Æt$|$Pÿÿÿ$èfFòÿµPÿÿÿ·EòPÿÿÿf$ÿÿÿqöt8EìµÿÿÿÀpÿÿÿ·Eòtÿÿÿt$ÿÿÿ$D$ÿQÀzEìÿÿÿpÿÿÿ·EòÀtÿÿÿ·BHE·BJÀ|ÿÿÿÇD$ÿÿÿL$u4$èKòÿÆEì÷D$ ÿÿÿ$èèWòÿöÔóÿÿ·Eò9ÿÿÿ-ÇD$ÇD$+ÿÿÿD$U$è+*òÿÀÇóÿÿÿÿÿ·Eòf+*ÿÿÿfAL·Eò1ÿÿÿÿfAJékóÿÿuN9ÿÿÿsx·FÐfEòé~ûÿÿ)ÂÇD$ÇD$T$u4$è¶)òÿÀÇ óÿÿEÿÿÿPÐf+AJfALéÌòÿÿ·Dºéèùÿÿ@øþÿÿEUéÂòÿÿU·*ÿÿÿfBf)ÈfEòéûúÿÿEìD$ ÿÿÿ$è¿VòÿML$µ$ÿÿÿ4$èú2òÿÇéòÿÿÇD$ÇD$)ÿÿÿµÿÿÿt$E$èø(òÿÀÇbòÿÿÿÿÿ·Eòf+*ÿÿÿfBLéÈþÿÿUåWVSèhòÿÃÝ#ì,u4$è-dòÿEðEÐUñ¶~HEòUÔ¶NIEØ¶VJ¶FKNJ¶NMVIú¶~LFH¶FOVK¶VNNN¶NQFLø¶~PVM¶VRFO¶FSNR¶NUVQú¶~TFP¶FWVS¶VVFTøVUNV¶~X¶VZ¶NYFW¶F[VYú¶~\NZFXV[øEð¶N]Mñ¶V^Uò¶F_EóV]úF\~`N^EóV_Æà}àEÜuÌ¶7EÐòUÔ¶O
>UØ¶GUÜ¶Gò¶GWOGÇ;}ÌuÂ}à¶·l¶o¶m¶nlðo1ÀmnÄ,[^_]Ã´&UåSì$EègòÿÃI"M1ÀöBt1yt8ÇD$L$D$ED$ED$E$èÉ[òÿÄ$[]Ã´&$è4SòÿÄ$[]ÃfUåì(U]øEuüèfòÿÃÑ!¶J0ùtBÀtI1ÀöFt0ùttÇD$T$D$ED$ED$E$èE[òÿ]øuüì]Ã´&EÇBÇBfÇBBÆBÆB
fB1À]øuüì]Ãt&$ètRòÿ]øuüì]ÃUåì8}ü}]ôuøèÀeòÿÃ!GöG ÂfEòtfWfUòED$ED$·EòÀ·ÀD$ED$E$èº<òÿÀEàtEà]ôuø}üì]Ã´&GUÈ B·EòÇBfröG u3G4$T$D$è@òÿ·EòwfUGÇBBëfG4$ÇD$D$è0òÿwë±¶¿UåWVSìLEèÆdòÿÃ ÌrUÄEÈöuÌeUÈ1ÿ1ÉöB`t
>uÈ·~H·ÏEÈUÄpxöÄu2¨
>UÈ·BÀ·T"·D fUÒ·ÒTë(´&UÈ·BÀ·TB·D@fUÒ·ÒTuÈèf+EÒ·VJf9ÇfFLfUòs|EòUÔE¼UÀë¶·EòUÈ|8f9zLvW·ÀL·u¼EØfEÀqUuÔD$EÄT$$ÿUÌUøt}³EÄ@Àt©}
>t&td¶U·ÇuÈ·EòN`f~HfFJÄL[^_]Ãt&UÈ·BÀ·T·DfUÒ·ÒTéÿÿÿfàûÿÿEÌéþÿÿÇëfUåWVSì,EuècòÿÃQ}¶ÌxPH (ÿÿÿÀàúÀ,ÿÿÿUè0ÿÿÿµÿÿÿT$D$<$èLòÿÀ8ÿÿÿt8ÿÿÿÄ,[^_]ÃEè(ÿÿÿÇ@Ç@fÇ@Æ@fPEìD$·FD$F@$D$èD&òÿÀ8ÿÿÿr(ÿÿÿÇE¼~°xòâ ÿÿÿÈ¹Bÿÿÿ·@ÂÒÿÿÿ·¶<y<×,¡ÿÿÿ,ÿÿÿB$D$è[òÿÀ8ÿÿÿãuÇD$½0ÿÿÿFD$F<$D$ÿÿÿÀD$è³YòÿÀ8ÿÿÿ¡Eèÿÿÿ6P·AyÆEØµLÿÿÿÀ$ÿÿÿEUÜ@ÀFpÉ}Uö-m|Àt@<Àt
öøOµLÿÿÿMØ¸@ÇEÿÿÿMxöÆuÐàøÀàúÀ $ÿÿÿÉPÿÿÿùöÆ·ÿÿÿlÿÿÿâÉPÿÿÿ¸ ·Tÿÿÿµ$ÿÿÿ·ÇD$(LÿÿÿÇD$ÿÿÿÿ|$)ÂED$$lÿÿÿpÿÿÿUD$ t$GÇD$|$D$B$D$èÃ)òÿÀ-µLÿÿÿxÈ%üþÿÿ¤öÁÕµPÿÿÿ¸ ·T7µÿÿÿ·)ÂêHÿÿÿüþÿÿ¸@ÒuáùÀàúÀ ·O4Pÿÿÿøþÿÿ·)ÈøþÿÿD$ÊHÿÿÿL$$èNòÿ·Hÿÿÿ·$ÿÿÿfOf9Wa·ÂÂfFf;WrðLÿÿÿxÎæµüþÿÿµüþÿÿ¸@öuáùÀàúÀ ÿÿÿÿÿÿ·QP1À8ÿÿÿt&u½0ÿÿÿF<$D$EèD$èEQòÿÀt58ÿÿÿÉu8ÿÿÿEìÀéûÿÿ,ÿÿÿD$$è4LòÿéÒûÿÿv8ÿÿÿÒuÑÿÿÿfÇ@JfÇ@HfÇ@Lë·t&ðàøÉáúÁ"é(üÿÿ ÿÿÿÉÚæ·D¹ÿÿÿèµ(ÿÿÿf+JºB·ÀE¨xöÄuàøÒâúÂ"ÿÿÿuJ·8ÇD$ÇD$4$D8E¤E¤D$E¨À%üÿD$EèD$èAòÿ8ÿÿÿ½8ÿÿÿÿ°þÿÿUìÒÂûÿÿuNÉ°}@°pöö-|Àt@<Àt	öøusqötlÿÿÿÇD$ ·BD$Eè@D$B@L$(ÿÿÿÇD$ÇD$D$EàD$$è$2òÿÀ8ÿÿÿòýÿÿUìÒûÿÿÇTÿÿÿÒu]éïúÿÿÌx½@ÿÿÿfÇ@WÒöF`tÌf`ýEìÀ±úÿÿTÿÿÿÁTÿÿÿÒúÿÿ2Eèµ@ÿÿÿ²Ìxt$|$$D$è=òÿÀ8ÿÿÿBýÿÿékÿÿÿ ÿÿÿ¸BÒuæþÀàúÀ"ÿÿÿM·PUÀPUÄP¶EÀÇE¨ÇD$UÈàEÎEÄUÔÇD$ÇD$EÐEÌE¤E¤D$Eè$D$è?òÿ8ÿÿÿéåýÿÿ ÿÿÿÀüæ-·t·ÆL8·Dèf)ð·À9È<ÿÿÿ~ùÿÿu¤}òEàfÇ4ÿÿÿfÇ6ÿÿÿµÿÿÿ½ÿÿÿÿÿÿt&·ÁµÿÿÿM¤·ÂE¨À%üÿf·µ4ÿÿÿD$Eè½ÿÿÿXÿÿÿf^ÿÿÿD$E|$ÇD$t$$è$>òÿÀ8ÿÿÿÂûÿÿMìÉ}WÒ±}@¸pö-|Àt@<Àt	öøuuzÿtnÿÿÿt$ ½ÿÿÿ·AD$Eè@D$A@ÇD$ÇD$|$D$(ÿÿÿT$$è8/òÿÀ8ÿÿÿûÿÿMìÉÓv¿ÒÁÆµÿÿÿë¶É¨9ÇÒ²Ì·6ÿÿÿf9FHu×Eè
>@t$Dÿÿÿ`ÿÿÿ$D$`ÿÿÿD$è3:òÿÀ8ÿÿÿqúÿÿ`ÿÿÿ·4ÿÿÿÌPDÿÿÿfHRÒt`öF`tÌf`ýMìÉ\ÿÿÿt&·^ÿÿÿµXÿÿÿL·Eò9<ÿÿÿ$÷ÿÿ·½6ÿÿÿf4ÿÿÿ|8f½6ÿÿÿé¸ýÿÿÿÿÿÄëµ$ÿÿÿEØÇÇGÿÿÿö7µPÿÿÿÿÿÿéqøÿÿÇÄééûÿÿ·tB·ÆL8·D@éýÿÿ·D@¹Bé*úÿÿµPÿÿÿ¸@·T7>é`øÿÿ·t"·ÆL8·D éÎüÿÿ·D ¹"éðùÿÿµPÿÿÿ¸·T7é&øÿÿµPÿÿÿ¸@·T7>ée÷ÿÿµLÿÿÿxÈ%üþÿÿé¬øÿÿPÿÿÿ·T¸é2÷ÿÿt&UåWVSì\Eu}èWòÿÃÞ¶ÌPH äþÿÿ1ÀöG èþÿÿWìþÿÿµðþÿÿtMATäþÿÿ½ðþÿÿôþÿÿxw<ÿÿÿ%µÿÿÿµ ÿÿÿµ$ÿÿÿ(ÿÿÿáºBðþÿÿ·I·ÁÀ,ÿÿÿðÔþÿÿ·f
>ÿÿÿøþÿÿ¶Aý<E(ÿÿÿÀ¯½,ÿÿÿ¸B·T>@½Ôþÿÿ·)Âôþÿÿù|ÿtÇðþÿÿA8@Áè9øÚ(ÿÿÿ·FÇÿÿÿ@Éf6ÿÿÿßù·F)Ñ·6ÿÿÿÀ)Â+ÿÿÿ9Ñ®Çf½
>ÿÿÿï(ÿÿÿ¸>Òu<ÿÿÿàøÀàúÀÔþÿÿ·éÅUèðþÿÿBQA·EòfAA`ÈàýöA`µäþÿÿ·Aÿÿÿ ÿÿÿ¶xÀ$ÿÿÿ,ÿÿÿµ<ÿÿÿæµ(ÿÿÿ(ÿÿÿ¸BÒ$ÿÿÿ,ÿÿÿ½ ÿÿÿ·Ç¶7ð<tôþÿÿ(ÿÿÿÀ$ÿÿÿ,ÿÿÿ·T@fÊþÿÿºBð·<<D·Êþÿÿðþÿÿèf)ÐQ8·ÀôþÿÿRÁê9Ðÿÿÿ¹@·B(ÿÿÿÒu¥<ÿÿÿ½<ÿÿÿÉáúÁ ·Ðÿÿÿ·@ÄþÿÿÀ)Â)Ê9ôþÿÿÃð<Ú	äþÿÿGÇEÌ½ðþÿÿE´x·GwöÅá#	·À¹"·D é|t&<ÿÿÿàøÒâúÂ"éýÿÿ´&ö<ÿÿÿs,ÿÿÿ·T ¸"é?ýÿÿ¶<ÿÿÿàøÀàúÀ"éZþÿÿ´&U$èÙòÿÀÆÄ\ð[^_]Ã¶úþÿÿ(ÿÿÿ·~Àf½ÿÿÿ¿@u<ÿÿÿàøÿçúÇ ¹·F)Ñ·ÿÿÿÀ)Â)ú¿9Ñ¼ýÿÿf½
>ÿÿÿýÿÿäþÿÿ(ÿÿÿ¸@Éu¥<ÿÿÿ½<ÿÿÿÀàúÀ <:ÔþÿÿÇEè·)ÇFÀEäÀMè1öÌþÿÿëFÀEä¥öt&UìþÿÿBt$$D$è6EòÿÀÆíþÿÿµÌþÿÿUÇD$ìþÿÿt$B$D$EäD$èû6òÿÀÆ²þÿÿäþÿÿuèx¹@·VöÄuàøÉáúÁ ·F·ÒÀ)Â)Ê9×MÿÿÿuÇD$FD$FD$ðþÿÿÀD$ìþÿÿ$èJòÿÀÆ4þÿÿEèUèÐþÿÿÀLUÇD$µìþÿÿÐþÿÿBD$B4$L$D$èÎIòÿÀÆ äþÿÿuèx¹@·VöÄ>·F·ÒÀ)Â)Ê9×Qu~ÿ@pÉö-t|Àt@<Àt
öøVäþÿÿÇEðþÿÿÇxÿÿÿxxÎæµ8ÿÿÿ
>º@µðþÿÿ·F4G·<Ã
>8ÿÿÿ¸@ÒuÈàøÀàúÀ ·D½ðþÿÿ|ÿÿÿ·wföL
>äþÿÿÏç·ðþÿÿrÿº@uáùÒâúÂ èf+ºÇüþÿÿ ·ÀEEòMD$EàµäþÿÿD$EèT$|ÿÿÿT$ÜþÿÿD$A4$D$èª$òÿÀÆ1üÿÿ½øþÿÿ?¤
>äþÿÿ½ðþÿÿxwÊâ@ÿÿÿf
>ºB½ðþÿÿ·G<F·<uüþÿÿ@ÿÿÿ¸BÒuÈàøÀàúÀ"·öÅðþÿÿD`ÿÿÿ·BRë	á¯·À¾"·D
> Êèf+2·Àdÿÿÿ`ÿÿÿUèD$$½Üþÿÿ·EòäþÿÿT$|$ D$BUÇD$D$üþÿÿD$EØD$B$D$èòÿÀÆ>¶UÇD$µìþÿÿÐþÿÿBD$B4$L$D$è«FòÿÀÆýMèUÜEØµäþÿÿQðþÿÿEòL$MD$·BD$BD$A4$D$è«:òÿÀÆÜM½ðþÿÿAD$GD$ìþÿÿ$è@òÿÀøÿÿöuÆðþÿÿEèA@A·EòfAA`ÈàýA`éúÿÿ´&ö<ÿÿÿu_$ÿÿÿ,ÿÿÿ·TfÊþÿÿºésøÿÿt&½,ÿÿÿ¸·T>éÌöÿÿv<ÿÿÿàøÉáúÁ ÿÿÿé÷ÿÿ$ÿÿÿ,ÿÿÿ·D º"fÊþÿÿéøÿÿ¶ðþÿÿu}t$ÇD$|$ÇD$$ÿ$ÆéGùÿÿfµ(ÿÿÿ¸Bö·1öÿÿÿMDéùÿÿv·À¹B·D@è}f+
>MuµØþÿÿ·ÀÇXE¸E´D$èþÿÿÁ`t$àþÿÿL$|$$èX òÿÀÆ¯øÿÿØþÿÿMÇD$T$$èñ,òÿÀÆøÿÿäþÿÿµðþÿÿxºBNöÄuàøÒâúÂ"µðþÿÿ·FB·ÆN`E¸fÇFHfFJÀfFLµèþÿÿàþÿÿØþÿÿM4$D$|$T$L$è òÿÀÆ÷÷ÿÿ}ÇE¤E ÊþÿD$èþÿÿ$èMòÿÆéÇ÷ÿÿf}GD$EèD$ìþÿÿ$èå=òÿé¡÷ÿÿ¥<ÿÿÿ½<ÿÿÿÀàúÀ"éTþÿÿàøÉáúÁ é¯ùÿÿ·À¹·DéYþÿÿ½ÐþÿÿEt$ÇD$|$$èÌòÿÀÆùÿÿUìþÿÿB$D$EèD$èS=òÿé÷ÿÿfÇEØÇEÜfÇEòÿÿé÷ûÿÿUuMµØþÿÿÂ`àþÿÿyXé¦þÿÿðþÿÿuT$ÇD$A4$D$è?òÿÀÆøÿÿé¡öÿÿ}»°ÊþÿØÿàäþÿÿ@ÀÓUEìMuD$E¨T$D$L$4$èªòÿ}ìÿUÇD$ìþÿÿBD$B$D$ðþÿÿÀD$èûAòÿÀÆöÿÿµØþÿÿ}ÇD$t$<$èT*òÿÀÆëõÿÿ}À½èþÿÿ ÊþÿD$<$èHòÿÆéÂõÿÿµðþÿÿ·FHE¨é`ÿÿÿ½ðþÿÿ·GH·WJDE¨éFÿÿÿEèM·}ò@	f½FÿÿÿHÿÿÿðþÿÿyPÿÿÿ·p@½ÿÿÿ@ÿÿÿE@ÀÿÿÿtxÀ÷Ð!ÿÿÿÿÿÿ,ÀPÿÿÿÿÿÿë½PÿÿÿBH;GHuÿÿÿ½ÿÿÿÜ@Òu×ÿÿÿ·öPÿÿÿµLÿÿÿÇÿÿÿBH;AHt&PÿÿÿB$À«½ÿÿÿ·èöué²fvö¥9uftî¾Èuå¾ÌöG`uÙÿÿÿ;GuÎFÀt'öt@Àtÿÿÿ4$T$èéòÿÀu¡·G9Lÿÿÿu·FÿÿÿHÿÿÿfGÿÿÿOÀrÿÿÿÿÿÿ;VcÿÿÿÇÿÿÿéTÿÿÿt&PÿÿÿA$À÷½ÿÿÿ¿Øÿ½ÿÿÿtPÿÿÿGH;BHïþÿÿÿÿÿ,ÀùÿÿÿÀ¦uFÀ@¸pÿö-u||Àt@<Àt	öøub·FÿÿÿµPÿÿÿ½LÿÿÿÿÿÿD$ Hÿÿÿÿÿÿ4$|$D$EÐT$ÇD$ÇD$D$L$èíòÿÀÆrøÿÿuÇD$4$è° òÿ}ö,Æu}@öôulÉ2øÿÿðþÿÿB8@Xé øÿÿÈàøÒâúÂ éYõÿÿ½ðþÿÿ½0ÿÿÿÏç£º>0ÿÿÿ·ö4p·éõÿÿ8ÿÿÿ¸@ÒuáùÀàúÀ ·ºÇEÇüþÿÿ!|ÿÿÿéõÿÿÿÿÿD$$èòÿÀ;ýÿÿ¾ÿÿék÷ÿÿµÿÿÿD$4$èÊ,òÿÀïýÿÿëÚt&ÈàøÒâúÂéMÿÿÿ·À¾B·D
>@éöÿÿÈàøÒâúÂ"éõÿÿðþÿÿäþÿÿHxºBöÄuàøÒâúÂ"µðþÿÿüþÿÿÇdÿÿÿ·FB·`ÿÿÿé¹õÿÿ¶M¸Óà©`ô¨"ûÿÿµðþÿÿ}·FHfFJWÀfFH·FLfVJDfFLEÇD$ÇD$D$E$èòÿÆé¯ðÿÿðþÿÿäþÿÿ·BzxöÆâ¾·Àº·DpÿU½ðþÿÿf+4BO`}
fwLfGJðþÿÿ·ÆE¨fqHéãùÿÿ}äþÿÿ|$$èÍ
òÿÆéðÿÿðþÿÿMµðþÿÿ·BLQDfFLfVJéÿÿÿ·ÀºB·D@égÿÿÿ·À¾·D
>éLôÿÿ·Àº"·D é=ÿÿÿÇE¨fÇGHéOùÿÿD$$è*òÿÀóûÿÿéýÿÿD$$èòÿÀOúÿÿéýÿÿUåì(uøu]ô}üèCòÿÃQþ¾ÌÇD$ÇD$EðUðG(D$ÇD$4$D$èòÿÀu*EUðD$FD$FD$G8D$B $èÀ:òÿ]ôuø}üì]Ã´&Uåì}ü}]ôuøèpBòÿÃ±ý·ÌV8H ÒtGT$$D$èÊ4òÿÀuÇF8V(1ÀÒu]ôuø}üì]Ãt&F(D$<$èU	òÿëÝ´&Uåì8U]ôuø}üèîAòÿÃ/ýP UìEðE¸ÌÇD$ÇD$W(T$UèUðÇD$D$E$è_òÿÀÆtð]ôuø}üì]Ã¶UG8D$ÇD$BUìD$Eð$D$èÙ%òÿÀÆtºO(Ét³EèUD$@$è5òÿëUåWVSì,UèAòÿÃWüxÈ%EèC¸@uEöEð·:u}è¸@uÈàøÀàúÀ ·}ÿfEìRUè¸@Ò·}èºBuáùÒâúÂ"·Uf+}ì·uÇ·Bf)Ïf}î·þè9Çt6·JÊUäUMÜMð·DQ+EÜUäD$EäD$·EîÂ$èM/òÿU·Mî·BfJèf9ÆfBr	ë#t&·þUðÆ·EîMfDzfzf9qwáÄ,[^_]ÃEèÇEà>ÀtJE}4GEà·<éÞþÿÿt&ÈàøÀàúÀ éþÿÿvÈàøÀàúÀ ééþÿÿvÈàøEÿçúÇ}à}4GEà·<éþÿÿ·éºþÿÿUåì(E]ôuø}üÌè:?òÿÃ{úx8EðÿuKU$èÔòÿÀu,Mðy@q8G$è\ÿñÿt`E$è-+òÿ>Àt)f]ôuø}üì]ÃvMðq@F$è#ÿñÿòT`EðT$UÇD$ÇD$ÀD$E$D$è]òÿUMðQ$ë¶Uåì8}ü}]ôuøèp>òÿÃ±ù·ÌV@ ÒEàtGT$D$Eà$èÄ0òÿÀÂuGEðÇFD$ÇD$GD$ED$Eà$è"òÿÀÂuEðfÇFFEF]ôÐuø}üì]Ã¶¿U1ÀåVSìUèÅ=òÿÃù²ÌNÉtFD$$èèòÿÇF@ÿÿÿÿÇFDÿÿÿÿÇFÇF$fÇFHfÇFJfÇFLÇFPÇFTfÇFXÿÿÇF`ÇFfÇFÿÿÇFÄ[^]Ã´&Uåì}ü}]ôuø1öè=òÿÃ_øH ÌPÒtGT$$D$èx/òÿÆ<$èN5òÿÀtöuÆð]ôuø}üì]Ãö¼'Uåì8E]ôuø}ü0è®<òÿÃï÷¸ÌÇEäö,V UàuuFöôuilÀt_GD;G@toGÀÇGUET$$è/5òÿÀu8G@UGDEäW$ÀtEäD$F$è&
òÿÀu¶w1Àöt_]ôuø}üì]ÃfGÀt$t	özt*}¶uGEäGEèGEìG Eðé]ÿÿÿUG@W$GDëfGÀt1UGD$ÇD$BD$GD$Eà$è òÿéjÿÿÿG8w@EÜF$è¸ûñÿUÜt`wë¯GD$E$èòÿÀ/ÿÿÿéÕþÿÿUåìXE]ôM}üuø0Eðè;òÿÃYöV D$ÇD$
$Uàè=$òÿÀÇ¿EPÒÁÁ@¸pÿ¬ö-|Àt@<Àt
öøEðÇD$(ÇD$$D$ @D$ED$@ÇD$@ÇD$T$D$EèD$4$è6	òÿÀÇt:UMBL$D$Eà$è´,òÿø]ôuø}üì]ÃÇEèÇEìEè1ÿUìuðÁÐVUBF
>BBFEÀuM1ë¬t&MUàA$D$ED$è@,òÿuðÇëÒ¶¼'UåWVSì,UEè9òÿÃÔôxÏçEèµ¸@uU4ruàuöGuEUEä·FÆÒuì|EU·uèÀUàt)ÿ¸>uÈàøÀàúÀuU4ruà·4ÿº@ýFÿuàf+·À9EWÿ¸@uáùÀàúÀ uàUÇEð·uDÆ+uìEÀ}ì+}Mìt$<$L$è«'òÿEðÀE·U·Mf;Prë4uä·ÂÂf)FEf9PvEÀuãuä·ÂÂfFEf9PwãEÀUuf)JxÏçEÀxcE ÿp¸@uáùÀàúÀ Mà·MDEt$T$$è/òÿÄ,[^_]ÃvÈàøÀàúÀ é;þÿÿvE ÿp¸@³Mà·ë¬fÿ¸@uÈàøÀàúÀ uà·u·Eèötÿ¸>÷uà·ÿ¾@uáùöæúÆ Màè·ÒÇEðf+1u·ÀTEÖ+uìÀdþÿÿ}ì}é_þÿÿÈàøÒâúÂ éîýÿÿváùMàÀàúÀ ·éèþÿÿ¶UMäÇEð·4Q)ÆEPEàéôýÿÿ´&EUfHxÏçéiþÿÿv7uÇD$$t$èòÿéÝýÿÿÈàøÀàúÀéôþÿÿ¶¿UåWVSì\è)6òÿÃjñEÀ1ÀMÀ}U¼·UÀ	è!ÐUÀfEÖAMÄREÌÒUÐt
zÀ÷Ð!ÂUÐMÌ,ÀßEÄEÈë´&MÄBH;AHuUÈUÈÜ@ÒuàUÈMÄÇEØBH;AHÏ´&UÄB$ÀEÈ°èöuë{vvötq;uÀ¶tî¾Èuå¾ÌU9Wu×FÀt öt@ÀtT$4$èòÿÀu°·MÖf;Ou¦öG`ftG\;EØrvÀEØöuUÄB$ÀaEÈØÀEÈtMÈUÄAH;BH8ÿÿÿUÄUàëMÄBH;AHuUàMàÜ@ÒuàUàMÄÇEÜBH;AHìUÄB$À>Eà°èöué´&vö;uÀftî¾Èuå¾ÌU¼9Wu×FÀt öt@ÀtT$4$èøòÿÀu°}o}fM}¶ËþÿD$UÌ$èùñÿÄ\[^_]Ãt&UÄB$ÀEàØÀEàtMÄ@H;AHÿÿÿUÌ,À£EÜÀMÀAÀt@¸pÿtpö-ug|Àt@<Àt	öøuMEØD$ ·EÖD$UT$M¼L$EÇD$D$EìD$UÐT$MÄ$è2òÿÀ!ÿÿÿEUØÄ\1À[^_]ÃM·EÖf;GOEÐÀeþÿÿMÐ;NYþÿÿÇEÜéMþÿÿU·MÖEØG\WfOëÇMEØG\Oë¹D$MÌ$è®òÿÀýÿÿ¸ÿÿéþÿÿD$MÌ$èññÿÀÏüÿÿëÝ´&UØW\fékÿÿÿD$MÌ$èññÿÀ«ýÿÿë°fD$MÌ$èEòÿÀOþÿÿë´&D$$èHññÿÀ
üÿÿéuÿÿÿD$$èòÿÀIþÿÿé\ÿÿÿ¶UåWVSì<EUè£1òÿÃäì²ÌEàF`¨t,MàLËþÿD$A$èòÿ¸Ä<[^_]Ã´&$?UF`E$D$èíòÿÀuÖNJMÜé:fNTÉ;MàVÇEÔ@xUÌ×Uä·RöÄuàøÀàúÀ EÔEÌ·Ò·H·ÁÀ)Â+UÔ9UÐs}ÌFfÇFXÿÿ·OFT}ä·Vf9ÊfUês8EàxEì%EðÁºB·EêÀEØø·<ÛöF`tPUà¹BxöÄuàøÉáúÁ"·Eê·VHAMÜ·8T·fV·F·JfEêUäf;Mêw_MäAÀtefÇFD$E$è,-òÿÀþÿÿFPÀEÐºþÿÿ~}ä·OéÿÿÿvEìàøÒâúÂ"é.ÿÿÿfN`1ÀéKþÿÿfN`@¸óÿÿé;þÿÿfUð¸BÒueì}ìÀàúÀ"UØM·D1ÀN`éüýÿÿvUåì(]ôEèV/òÿÃêU}üuø°ÌT$$èÚòÿÀÇN`öÁ·FfEæfÀt<öÁt7VUèUºBxöÄN·EæBUè·<ÞV`Ðàøåâ0ú0áýN`MEUL$D$$è®òÿÇø]ôuø}üì]Ã·FføÿtvöÁ ªöÁf·VLfÒfUð·FH·VJfEò·ÀfUî·ÒD·Uð9ÐröÁuR·Mò·UîDf;FLfFHeÿÿÿf`ïfFéWÿÿÿffÇFf`ïéFÿÿÿ·FLf;FHÿÿÿöÁt-t&áÉ@N`é:ÿÿÿföÁuëÀfFf`ïéÿÿÿvÈàïF`ÁfFéëþÿÿt&àøÒâúÂ"éþÿÿt&Uåì(]ôèy-òÿÃºèuøu}ü¾Ì4$èaòÿÀu@G8O`ÇG@EðÇ$èíñÿUðD`UGET$4$D$è}	òÿ]ôuø}üì]Ãt&Uåì8E]ôUuø}ü°Ìèç,òÿÃ(è8f`=ÿÿÿT$$èqòÿÀÁF`à0øF`¨àïF`·FfÀu1F@ÀFYD$E$è)òÿÀÁu<F·@fFføÿèMfFUEL$$D$èS	òÿÁt&]ôÈuø}üì]Ã¿xFúâEìUðûÇEàB·VEìUèPUà·Eì<ë·FHfÀfEæÿÿÿEðºBÀuçÿÒâúÂ"MèUì·Eæ·JMìDÿ·fVJ·EæMèf)ÐUfFHE$T$D$èòÿÁé5ÿÿÿt&UD$$è}(òÿÀÁÿÿÿV·BfFBÀuÕ·FfÀÑþÿÿN`@¹óÿÿéêþÿÿf$È@F`éÛþÿÿvøàøÀàúÀ"EàéôþÿÿUð¸BÒuçÿÀàúÀ"UèEì·PUìDUN`éþÿÿt&Uåì(]ôEè¦*òÿÃçåuø}ü¸Ì$èòÿÀuAW8rHUðw@F$èÆêñÿUðt`EO`UwD$ET$$èÌòÿ]ôuø}üì]ÃvUåWVSìÌMEè *òÿÃaåÇEìÌÇEèÇEðyP ·qtÿÿÿÿxÿÿÿ|ÿÿÿfuÆtÿÿÿxÊâdÿÿÿº@·uµpÿÿÿö7·µlÿÿÿ<µdÿÿÿ¸BöuÈàøÀàúÀ"pÿÿÿ·P¶<ö<Þ<ÖUrö8@pÉ%ö-|Àt@<Àt
öøútÿÿÿ¸@xöÆuÐàøÀàúÀ µpÿÿÿf}·pE ötÿÿÿÖæö¸@uâúÀàúÀ pÿÿÿ·P)Á¸BM¤tÿÿÿxöÆuÐàøÀàúÀ"µpÿÿÿöÆ·pE¼£â2µlÿÿÿ¸"·T7 ét&ÈàøÒâúÂ éRþÿÿvÇEØÇEÜUÜEØtÿÿÿWpÿÿÿ|$$T$èoòÿµ|ÿÿÿF`È$F`Eö,u@öôMÇD$$èíôñÿÀÆµ|ÿÿÿF8hX1ööEfEÇD$ÇD$ÇD$$ègçñÿÀÆ9öE/ff"GÀt&'UEèD$xÿÿÿÇD$B$D$GD$èhòÿÀÆàGÀFÇEðÇdÿÿÿÇhÿÿÿGMèAhÿÿÿÀtAµhÿÿÿFEPÒ0F°pöÿuö-ï|Àt@<Àt
öøÑdÿÿÿD$(G|$ D$$GL$D$GT$tÿÿÿÇD$PÇD$D$EØD$$èÚôñÿÀÆòMðhÿÿÿMèµhÿÿÿEØUÜöQtEØUÜµhÿÿÿVEØUÜGWÀ¬A|ÿÿÿÇEB·AfBµ|ÿÿÿGUÇFE$|$è+ïñÿMÆAD$EèD$xÿÿÿ$èÊòÿÀtöuÆUðÒÖMAT$D$xÿÿÿ$èòÿÀ²öu	Æ´&ÄÌð[^_]Ãvdÿÿÿ¸@ÒtapÿÿÿM·PD$EäD$èBòÿÀÆu¸µtÿÿÿxÈ%dÿÿÿéûÿÿflÀýÿÿééüÿÿt&áùÀàúÀ ë|ÿÿÿ``ïéûÿÿdÿÿÿ¸BÒuáùÀàúÀ"pÿÿÿu·HD4$EäD$è¤òÿÀÆÐúÿÿéÿÿÿUÈÀD$ÇD$BD$ÈxÿÿÿÀD$$èbòÿÀÆÔþÿÿµ|ÿÿÿ~éðùÿÿ¶Öæ¸>pÿÿÿ·Aéõúÿÿvlÿÿÿ¸B·T@pÿÿÿu·H|$L$)ÂE¼D$$E D$ UÀGÇD$0ÇD$D$EØD$FD$tÿÿÿ$ènññÿÀÆ.ûÿÿéþÿÿvÐàøÀàúÀéVÿÿÿvlÿÿÿ·T¸écÿÿÿGÀàýÿÿUEðD$xÿÿÿÇD$B$D$GD$è6òÿÀÆ¨ýÿÿuðFµhÿÿÿÀ·EpöþÂ@pÉéö-Ü|Àt@<Àt
öø¾µtÿÿÿhÿÿÿUM E¤E D$(EìD$$AL$D$ A|$D$GÇD$D$EØD$B4$D$èj
>òÿÀÆâMðhÿÿÿEØUÜµhÿÿÿWEØUÜFVÀ¡MìÉt5GUABL$xÿÿÿD$$èòÿÀÆäuðµhÿÿÿGtÿÿÿwE<$UD$hÿÿÿD$è¨üñÿUEðMwWPEàÇGD$ÇD$ÇD$G$EèÌêÿÿÀÆ½UðÒtMAT$D$xÿÿÿ$è[òÿUìÒtMAT$D$xÿÿÿ$è8òÿUèÒ©ûÿÿMAT$D$xÿÿÿ$èòÿéûÿÿÇEØÇEÜé¢þÿÿÇEØÇEÜ´&é{úÿÿöSûÿÿUEà|ÿÿÿD$T$U·AD$A$EèîéÿÿÀÆûÿÿ|ÿÿÿEàB\éûÿÿMìEØUÜQéOþÿÿ|ÿÿÿÇEAfÇAéTúÿÿUEìD$xÿÿÿÇD$B$D$ðÀD$è1òÿÀÆ©þÿÿuðµhÿÿÿéýÿÿÇEìéþÿÿuEðD$ÇD$FD$GD$xÿÿÿ$èßòÿÀÆWþÿÿUðhÿÿÿdÿÿÿéøÿÿGµ|ÿÿÿFEàF\EðfÇFD$E$è×èñÿÀÆ	úÿÿÇEðé&þÿÿt&UåWVSìMEUèÝòÿÃÚ·@RMIfEUÉt
1ÀÄ[^_]Ã}·x÷Æu%÷ÆM·Q}·ÂDE·ëEM}·P@·ÂDE·f}vèf)Ð·ÀE·EfÇEè·ÀDEéX¶º@·EÁEEÉÈ·Uf}DE E·fxÿÿÿÿ=÷ÆÁEfÇ~ÿÿÿÿÿ·D f)~ÿÿÿ·~ÿÿÿfxÿÿÿ·ÀE¸UEM·P<yÿ¸<uðàøÀàúÀMEU·H<qÿ¸@uðàøÀàúÀ ME}·H<QME9ÁvÁu9É} ó¦ÀÂ(Ð¾ÀEèEèÀÂÀyUfE·Mf9M1þÿÿ}E U·xEU÷ç þÿÿðàøÒâúÂ éþÿÿvÇEèEM9ÈvÈD$
Ëþÿu }D$Et$|$»EËþÿ$èTòÿU+ËþÿMD$T$$è8òÿu;ËþÿD$4$1öè!òÿt&Uxº@öÄuàøÒâúÂ EMðÆ·|$$D$èÜ
>òÿ;uu»u3þÿD$4$èÂ
>òÿ}EÇD$|$$èóñÿÀýÿÿ·UfUé±þÿÿ´&EfÇ~ÿÿÿÿÿ·D@f)~ÿÿÿ·~ÿÿÿfxÿÿÿ·ÀE¸<éÊýÿÿfÿ¸>uðàøÀàúÀUE·PfxÿÿÿéTýÿÿU9Uþÿÿ,þÿÿÇEèÿÿÿÿ´&éþÿÿvÿ¸@uðàøÀàúÀ UEM·P<VýÿÿUÌ1ÀÇÀørñM°1ÀÇÀørñ÷Æ¸<ÇE´ÇEÐtt}E·xE÷ÆEÌ¸@uæþÀàúÀ uE}·pEE°EèD$GT$UL$D$E$D$èBÞñÿÀ)ýÿÿéyûÿÿðàøÀàúÀéwÿÿÿvEfÇ~ÿÿÿÿÿ·Df)~ÿÿÿ·~ÿÿÿfxÿÿÿ·ÀE¸é:üÿÿfUÌ1ÀÇÀørñE÷ÆEÐ¸@uðàøÀàúÀ ME·HE÷ÆEÌ¸@uðàøÀàúÀ }E÷ÆM·xDEì¸@uæþÀàúÀ uE}M·puD}EðEèD$AT$t$<$D$EìD$EðD$èòÿÀïûÿÿé?úÿÿ´&U°1ÀÇÀørñM÷Æ¸@M´uðàøÀàúÀ }E·xE÷ÆE°¸<uðàøÀàúÀME÷Æ}·HDEì¸<uæþÀàúÀMEu}·HDEðEèD$GT$UD$Eì$D$EðD$ED$èòÿÀÿúÿÿéOùÿÿM·Q érùÿÿvUåWVSìEèãòÿÃ$ÓxôuMÇEàÇE°·FfÇEÂfÑè·ÀÀM´E¬}Ä}¶uE¬·U°xÑèBE¼ÏçfUÂþöÁÍ·UÂÖUUö·D2 TU¨U<õf}ÂsU·U42ÿº@uáùÒâúÂ èf+}·ÀEEè~u´FÀ1À}ÇÀørîE¨EÄEèEÈ|$UT$M$u´ÿVEàEàÀ¨À~U¬EêÀÑêE°U¼}¼ÿhM¼M¬éÝþÿÿt&·EÂUÆöE·D2@TU¨U<ÿÿÿÿº@uáùÒâúÂ EMð·ÁA}EèAEðEàD$U´BD$EèD$EðD$ML$ut$}<$èRòÿÀ ÿÿÿÄ[^_]Ãvÿ¸>uÈàøÀàúÀu·étþÿÿv·uÂUuö·D2TU¨é0þÿÿvM¨uEÈMÄBEðBEäEàD$}´GD$EäD$EðD$ED$UT$M$è¢òÿÀPÿÿÿ÷]àéhþÿÿ¶uPUìA9ÂEðus·uÂ1À}M Çf1Ä[^_]ÃvE}E½|ÿÿÿ9øvø}¨9ÀÖÁó¦ÀÂ(Â¾ÂÀEàúýÿÿ|ÿÿÿ°9UvhEàéÚýÿÿ1À}ÇÀørîEàMÄÇEÈD$U´B|$D$ML$ut$}<$è8ØñÿÀýÿÿéaþÿÿ´&ÀEàvémýÿÿvuàöv~fEÂ·}Âu Ef>ÇÄ1À[^_]ÃM·P1ÀÇEìÇE ÒUM¤®uÄu}x×çtL¸@M Eu ·HMöÁ¶<<t<UBD$MA$è òÿÄ[^_]ÃÐàøÀàúÀ ë§¶uAVEð9Â-EìÀgE u 9uZÿÿÿð} Uf1À}ìÀ1Àé&ýÿÿt&E¤@Àt91ÀUÇÀørîAMEÄAEÈT$L$u4$}¤ÿWëE@E¸E Àÿ¸>uÐàøÀàúÀu·ufzÿÿÿÿ¾@uâúöæúÆ ·zÿÿÿUèf+2·À9E¸ÿÿÿ}E¸7y9ÀÁó¦ÀÂ(Ð¾ÀEìéëþÿÿE·fzÿÿÿE40uëAEèEìD$}¤GT$D$Eèt$D$ED$U$èC
òÿÀþÿÿéìûÿÿ·E ¶éþÿÿt&¼'UåWV¾@Sì\}Uè~òÿÃ¿Ì·GfEÊxöÄuàøöæúÆ } NUBÀEÐ}$(UBÀEÔEÀÁM·føÿ±fEòMÔ47MÐf}ÊuÌMØ³·G·MòUÌf+EÐ·uØfJ·Gf)ðfDJf)w} UxöÄ ·DO@¶M Ur
>Dt$L$$èìëñÿ}$MxöÄ|¨·Uò¶M$Ò·D"Ep·D"éh·Eòf;EÊ?ÿÿÿ·WfÀ4rMx¹>öÆuâúÉáúÁ·ÀA·)ðEÜEÜt$D$+uØ4$èýþñÿ·UÊUÀ·UòEÀ)ÐÀD$MÌQTQ$D$èÑþñÿ·Eò·uØÂEÄEÀÂÀ9Â MÌEÀ·uØ+EÄQ1ÉÁf)2Â9Áuó·EÜ·MòUÌfEº·EÔfGfEºf)ðfJ·GfEºf)uº·EºfDJf)w} lþÿÿUER0UàUxº@öÄJMà·t$L$$èPêñÿ}$dþÿÿUMxºBq	öÄ#·EòB·t$L$$è	êñÿ1ÀfGÄ\[^_]Ã¶¨	¶M ·D Ep·D éËýÿÿ´&EòD$EìD$E D$U|$T$ML$E$èââñÿÀuEÀýÿÿ·EòUféýÿÿMIMÔéÖüÿÿfMIMÐé°üÿÿf·Eò¶M$·DGBUr
>Dt$L$$è(éñÿ1ÀfGÄ\[^_]Ãt&M	)ÑMÜé²ýÿÿàøÒâúÂ"éÊþÿÿt&àøÒâúÂ élþÿÿt&·DOé»üÿÿ¶·Eò¶U$·DGMq	ékÿÿÿt&¼'UåWVSè,
òÿÃmÈì|MEØE 1ÀU ÇÀørîu¼1ÀuUÇÀørîu¾xø%E¤\u	·D@¶E¬¸BE}¬q·U¶fuªE°u¤º@öuøàøÒâúÂ E·ñfÉ4p·UDEØ/E·E¤º@ÀuøàøÒâúÂ Aÿf+·ÀEÜ}°M¤º@ÉuøàøÒâúÂ ·Eªuf}ªF·DE¼U·u¤º@öuçÿÒâúÂ èf+·ÀEÀE¬u°UD$Et$u T$D$Et$D$ED$E$èÕñÿÄ|[^_]Ã÷Ç\u	·D ¶E¬¸"éþÿÿU¤¸>Òp·éSÿÿÿ´&U¤¸>Ò0·é¾þÿÿ´&M¤º@Éu·MªN·ðf}ªE¼ZU¤¸>ÒuøàøÀàúÀE·Hu¤¸@öuçÿÀàúÀ E·H)ÂUÀé×þÿÿt&u¤º@öàE·ñp·UfÉUØ´U¤¸>ÒuøàøÀàúÀE·pM¤¸@ÉuøàøÀàúÀ E·p)ÂUÜéäýÿÿt&u	·D¶E¬¸é7ýÿÿt&øàøÀàúÀ·é~ýÿÿ´&øàøÀàúÀ·éÓýÿÿ´&Eéeÿÿÿ¶øàøÒâúÂ éÿÿÿvEé¿þÿÿ¶øàøÒâúÂ écþÿÿt&¼'UåWVSì,EèF	òÿÃÄÀ·UEðU1ö1ÿD$ED$Eð$èväñÿUfÇBUUfBÆBÆB
Uðfzuë?UðÆf9rv2ET$UÇD$D$·ÆD$ET$$è$õñÿÀÇtÂEÀt
>Ä,ø[^_]ÃEðUD$B$è(öñÿëßUEðD$D$B$èèñÿÀÇ,ÿÿÿë¸vUåìhuøÆN]ô}üè<òÿÃ}Ã¾ÌÉU¼EÀt@pÒt	ö-tYÇEìÇEðEìM¼UðfÇGXÿÿG<QÇGTD$FL$D$EÀ$èÏÓñÿ]ôuø}üì]Ã¶|Àt@<Àt	öøuMÀU¼EÔE¼D$EÐEÐD$BÇD$ÇD$$D$EìD$FD$èÕñÿÀJÿÿÿëvUåWVSìÜEMè0òÿÃqÂÌP dÿÿÿATlÿÿÿhÿÿÿÀuAEðlÿÿÿHÉÐUErlÿÿÿHB81Ò@Áè9ÁÂ9ÆÀÒ¶ÀE¸UuAUÇpÿÿÿÒçpÿÿÿxÿÿÿë@¹@·Jÿÿÿ·ú?)Ð)È9xÿÿÿ£TÿÿÿMT$$è}òÿÀlÿÿÿB·PfúvNHÉTÿÿÿtAdÿÿÿ·@±xfJÿÿÿð%EzÿÿÿðàøÉáúÁ éjÿÿÿt&dÿÿÿ·ú·@±xfJÿÿÿñáME¹@ÀuæþÉáúÁ ·Jÿÿÿ?Ç|ÿÿÿ)Ð)È9xÿÿÿåMIÉDÿÿÿÑdÿÿÿB xwöºMM®¹@XÿÿÿxöÄuàøÉáúÁ XÿÿÿEÇtÿÿÿ)ÊÀÑtpÿÿÿ1Òè÷ñÀtÿÿÿEÀtPU+wB1Òè÷ñtÿÿÿD9ðv2dÿÿÿ$èçñÿt&ÄÜ[^_]Ãt&ÆµpÿÿÿéþÿÿfUÇD$DÿÿÿBL$D$lÿÿÿÀD$hÿÿÿ$èüñÿÀu¥lÿÿÿMÇE·BXb`ý\ÿÿÿfBEÀ[}UMÿ`ÿÿÿMlÿÿÿJyÎlÿÿÿA;BTtTÐ\ÿÿÿÀXD$EìD$EL$MT$D$AD$dÿÿÿ$è|ØñÿÀøþÿÿlÿÿÿJABTExÿËÂ@°pö¶ö-©|Àt@<Àt
öø}EöæþÆ"ÀtÎ}R\ÿÿÿ`ÿÿÿL$T$ lÿÿÿD$$·BXD$Adÿÿÿt$ÇD$D$EäD$|$$è5ÑñÿÀ!þÿÿElÿÿÿxJëÇEäÇEèEäUèEQM`ÿÿÿD$lÿÿÿL$\ÿÿÿT$lÿÿÿÀXL$dÿÿÿD$B|$$D$èuÌñÿÀ¡ýÿÿxÿÿÿUÇD$ÇD$D$$èhÂñÿÀÆlÿÿÿA@A·AXfAEö,õ@öôãlÀÕ½|ÿÿÿÿu)lÿÿÿA8PTÒ°A·@fÑè·À9ÂlÿÿÿH`1Àéçüÿÿ´&UÇD$µlÿÿÿhÿÿÿBÆD$Bt$$D$èùñÿÀ¤üÿÿlÿÿÿt$MÇD$B$D$èÒñÿÀxüÿÿlÿÿÿÇ|ÿÿÿB@BéûÿÿfUÀD$hÿÿÿÇD$B$D$EðD$èvåñÿÀúùÿÿéüÿÿEÐUD$EuÌÆEÌ$D$è©ÇñÿÀõûÿÿMu°ÇEAÇE´EÔE°\ÿÿÿéUüÿÿEÜUD$EuØÆEØ$D$èYÇñÿÀ¥ûÿÿMuÇEAÇEEàE`ÿÿÿéüÿÿEÊèã÷ÿÿÀkûÿÿlÿÿÿHéüÿÿðéVûÿÿMÇD$$èoÍñÿÀ;ûÿÿlÿÿÿB8@XéþýÿÿÎé¦üÿÿUåWVSìüEuèÐÿñÿÃ»ÇEì¾ÌÇEÜÇEäPH XÿÿÿEw8\ÿÿÿ`ÿÿÿÀÇEàÇEÔÇE°$èÄ¿ñÿMU°,ÿÿÿD`ET$ÇD$EØÇD$D$ÇD$$èö×ñÿÀÆUäÒtMAT$D$`ÿÿÿ$èññÿUÜÒtPEÔXÿÿÿÇBÇBBÆBfÇBfBEÜÆ@
U`ÿÿÿB$D$EÜD$è2ññÿUàÒtB;EØu/}°ÿuKEìÀtD$\ÿÿÿ$è#ìñÿÄüð[^_]ÃfMAT$D$`ÿÿÿ$èØðñÿ}°ÿtµ,ÿÿÿMT$$è|ÅñÿÀtöuÆ¶ë¶Uuät$`ÿÿÿÇD$µ4ÿÿÿB$D$EØD$èpâñÿÀÆºþÿÿUäzEw8À$è¾ñÿT`uÜUUMt$ÇD$BMÔ`ÿÿÿµ8ÿÿÿD$EÔD$$èâñÿÀÆQþÿÿUÜEÔµXÿÿÿÇBBÇBÆBfÇBfBEÜÆ@
W<D$EäUà$D$èØñÿEpöñÂ@pÉÜö-Ï|Àt@<Àt
öø±XÿÿÿUäuT$xÿÿÿ|ÿÿÿxÿÿÿD$BÇD$ÇD$D$EÀD$F$D$è»ÊñÿÀÆUýÿÿt&MäUÄEÀÇAQXÿÿÿÇAfÇAÆAfAEäMÆ@
1ÀÇEÌÇEÈDÿÿÿµDÿÿÿÇÀørëEàÀkUìMÌ0ÿÿÿ$ÿÿÿµ0ÿÿÿÇD$ÿÿt$@D$Xÿÿÿ$è±¿ñÿÀÆüÿÿ}àf¶UÈxÿÿÿfÇjÿÿÿ<ÿÿÿ(ÿÿÿ´&·µjÿÿÿ$ÿÿÿ<ÿÿÿDÿÿÿt$µLÿÿÿuD$T$L$|$FD$Xÿÿÿ$èI÷ñÿÀÆüÿÿEUD$E$D$è6öñÿ;EiEÜ8ÿÿÿTÿÿÿdÿÿÿXÿÿÿ}à±xð%Hÿÿÿ÷ÆvLÿÿÿ¸É·T·)Âf½jÿÿÿµXÿÿÿPÿÿÿHÿÿÿÀiæøB·T Tÿÿÿ)ÐPÿÿÿ·Q¹ lÿÿÿµTÿÿÿ·FÀ)Â)Ê;lÿÿÿùEpöùÂ@pÉäö-×|Àt@<Àt
öø¹Xÿÿÿµdÿÿÿ(ÿÿÿM|ÿÿÿT$µXÿÿÿD$xÿÿÿ@ÇD$ÇD$D$EÀD$A4$D$èÍÇñÿÀÆgúÿÿdÿÿÿUÄEÀQdÿÿÿL$MÇD$T$$è/ÊñÿÀÆ)úÿÿ}àµdÿÿÿEòD$UXÿÿÿfÇEòÿÿ|$D$LÿÿÿD$B$D$èåñÿÀÆÝùÿÿ}àG;EØ¡uEèÇD$D$FD$Xÿÿÿ$è3ßñÿÀÆùÿÿµdÿÿÿMèÌ@ÇB\B·EòfÇBHfBlÿÿÿÇD$ÇD$$D$è¸ñÿÀÆEùÿÿEè$è&ÙñÿÀÆ0ùÿÿ}àuìö2À(Çpÿÿÿ¹ë´&ÁÀtFÌB;Guè·jÿÿÿf9BuÛdÿÿÿÇpÿÿÿ@B·EòfBÁÀu»pÿÿÿÀ²MQÒ¤@°pöö-|Àt@<Àt	öøujBÀtc·EòµLÿÿÿdÿÿÿD$ t$µXÿÿÿ@D$G4$ÇD$ÇD$D$EÀD$T$ènÌñÿÀÆø÷ÿÿ}àt&fjÿÿÿ·jÿÿÿf9GoûÿÿGEÐG;EØtU|$$è¦ÀñÿÀÆEÐÀºÇEàEìÀtD$\ÿÿÿ$èQäñÿEàÇEìÀ§úÿÿEÈÀ\ÿÿÿD$$è"äñÿUàÒoB;EØcMT$$èÀñÿÀÆJÇEàé÷ÿÿfÇEÀÇEÄéüÿÿt&B·T@Tÿÿÿ)ÐPÿÿÿ·Q¹@lÿÿÿéûÿÿ¶½Hÿÿÿ¸>uðàøÀàúÀ·Pÿÿÿé)ûÿÿLÿÿÿ¸BÉ·T@éíúÿÿMäµ4ÿÿÿTÿÿÿµdÿÿÿéúÿÿ¶B·T¹µTÿÿÿ)ÐPÿÿÿ·Vlÿÿÿéûÿÿ¶Lÿÿÿ¸"É·T éúÿÿEèèìÿÿÀÆa÷ÿÿ¶é¬öÿÿÇEÀÇEÄt&éøÿÿMEàD$µ`ÿÿÿÇD$A4$D$EÐD$èiÙñÿÀÆ³õÿÿEàÀ
>þÿÿExÿ®Â@°pöö-|Àt@<Àt	öøurXÿÿÿUàuT$xÿÿÿ|ÿÿÿxÿÿÿD$BÇD$ÇD$D$EÀD$F$D$èeÂñÿÀÆÿôÿÿEÀUÄMàQéNýÿÿÇEÀÇEÄëÝuNÉk@pÒXö-K|Àt@<Àt
öø-Xÿÿÿ½xÿÿÿuMÀ@ÿÿÿ|$|ÿÿÿEäD$xÿÿÿ@ÇD$ÇD$L$D$F$D$èÁñÿÀÆ+ôÿÿEÀMäUÄEÜQU|$XÿÿÿD$xÿÿÿ@ÇD$ÇD$D$@ÿÿÿD$B$D$è/ÁñÿÀÆÉóÿÿUÄMÜEÀQUäuFT$D$`ÿÿÿ$èHåñÿU`ÿÿÿÆB$D$EÜD$è'åñÿÀüóÿÿöôóÿÿÆéìóÿÿUäEÜÇÇBÇÇ@ëUåWVSììEuMèMòñÿÃ~ÌÇEàPDÿÿÿF`ÿÿÿÇEì\ÿÿÿ9øÇEð½@ÿÿÿÚ)øhÿÿÿÇtÿÿÿµDÿÿÿ`ÿÿÿxyÐ%TÿÿÿÀ¹Bµ`ÿÿÿ·vµPÿÿÿö7·|ÿÿÿ8À¶ÀÀpÿÿÿ*TÿÿÿÀ·D7@ºBPÿÿÿèf+J·ÀEèu}MèvòWµ<ÿÿÿ9ÊÀ¶øÿtÿÿÿÀ)ÊhÿÿÿhÿÿÿÊ`ÿÿÿA8@Áè9Â`tÿÿÿÀqDÿÿÿ·Vx¹@öÄ·F·ÒÀ)Â)Ê9hÿÿÿàu~ÿELÿÿÿ1ÀLÿÿÿÇÀørëEÀDD$ET$À<D$`ÿÿÿ·AD$AD$uFD$½Dÿÿÿ<$èIìñÿÀÆóÄìð[^_]Ã¶@ÿÿÿÇtÿÿÿ)ÂhÿÿÿéþÿÿvÐàøÉáúÁ"é0þÿÿvâ¿·D7 º"éfþÿÿ½pÿÿÿ,µDÿÿÿ`ÿÿÿxJºBöÄuàøÒâúÂ"½`ÿÿÿ·GBU·RÒhµDÿÿÿVºpÿQ}ö-A|ÒtR<Òt
öø#·ÀuD`ÿÿÿ<ÿÿÿE¼@ÿÿÿQEÀE¼t$(}D$ |$$<ÿÿÿT$D$·AÀD$BÇD$D$EØD$UBD$Dÿÿÿ$èa¸ñÿÀÆxþÿÿµ`ÿÿÿNét&tÿÿÿÀÚýÿÿéãýÿÿt&tÿÿÿÀÒÊÇtÿÿÿ+hÿÿÿéLýÿÿv½|ÿÿÿGEèéóüÿÿ´&`ÿÿÿB·J@XÿÿÿdÿÿÿEðD$L$µdÿÿÿ<$t$èó±ñÿÀÆMìÉt$èºÎñÿÀt
>öuÆt&EðÀtD$½\ÿÿÿ<$èsÛñÿEàÀýÿÿD$\ÿÿÿ$èVÛñÿÄìð[^_]Ãt&Ð)È9hÿÿÿX+hÿÿÿÇtÿÿÿhÿÿÿéVüÿÿt&½`ÿÿÿE`pçö½lÿÿÿuÂ@;Eèæµ|ÿÿÿ¶Çxÿÿÿ<t	¶Àxÿÿÿ} 1À½HÿÿÿHÿÿÿÇÀørëEäÇEäD$EàD$T$`ÿÿÿ·AÀD$AD$uFD$½Dÿÿÿ<$èÁèñÿÀÆ®þÿÿtÿÿÿÉeEM }¤pòPE99Es>9×v:ø)ÐtÿÿÿEèÒ©UhÿÿÿD$M$L$èuÛñÿ}M wEñ@$T$D$èÇñÿtÿÿÿÀH½hÿÿÿ}¤½HÿÿÿÇD$U$è"ÆñÿÀÆïýÿÿEìÇD$D$M$è®×ñÿÀÆËýÿÿµxÿÿÿ|$t$½Lÿÿÿ|$E$èÁÝñÿÀÆýÿÿ`ÿÿÿlÿÿÿ	J`×MìRÌ9PÇEðÀ8ÿÿÿðÀæ¾ëvWÌ½`ÿÿÿP·W``ýfP8ÿÿÿ2ÆÀuÒuVÒ @¸pÿö-|Àt@<Àt	öøufröt_½`ÿÿÿ·GD$ XÿÿÿD$GD$dÿÿÿEØÇD$ÇD$D$L$T$µDÿÿÿ4$èÍ¿ñÿÀÆzüÿÿMìÇD$ÇD$ÇD$$èªñÿÆéPüÿÿt&àøÉáúÁ élùÿÿt&È)Ðhÿÿÿé¯ûÿÿ·D7ºé§øÿÿÇEØÇEÜEØUÜ}Q|$tÿÿÿD$hÿÿÿT$GD$`ÿÿÿ·AÀD$AD$µDÿÿÿ4$1öè	ÔñÿÄìð[^_]ÃÇtÿÿÿézøÿÿ½DÿÿÿG PBÀ×øÿÿ;BÎøÿÿ<$è¤ËñÿÆ¶é(ùÿÿv½lÿÿÿ×ÉÁxÿÿÿé6ýÿÿ´&HÿÿÿD$hÿÿÿE¤D$\ÿÿÿ$èÿÎñÿÀÆÖøÿÿU hÿÿÿE¤hÿÿÿUàU¤EäL$ÇD$$è´ñÿé8üÿÿt&hÿÿÿ)E¤½Hÿÿÿé³üÿÿU+hÿÿÿéRüÿÿ·@f;G+ýÿÿé¡úÿÿUåWV1öSì<EèèñÿÃÅ£UðMìÇEà@ UÐMÔEØEèEÌVUÜ$è¦¨ñÿMt`uìEÐÇD$ÇD$D$UÔT$MØ$è£ÌñÿÀÆ¿Uð¶B<
tz<tvÇEìMAT$D$EØ$èjÚñÿÀÇUEì9Br+Àt'MÌD$L$E$è{¿ñÿÀÆu[EèÀ^ÿÿÿUMÜ9JHrCÎé4ÿÿÿt&EEàMà;Hw5EìD$U$èÃÚñÿÀÆuEUðBEìé\ÿÿÿvþÄ<ð[^_]ÃM¾ÿÿAT$D$EØ$è²ÙñÿÄ<ð[^_]ÃMAD$EðD$EØ$èÙñÿÄ<ð[^_]Ã¶UåWVSì<EèææñÿÃ'¢UM@T$$EÔEðD$èf³ñÿÀEØUÀ¦xÿUðöB<@¡ÇEÜöE]MUAH;BS1ÒÀ¾ÿÿÿÿäMAL9ÂÆMá@MàèÇEÜMAP9ðt}àÇEÜÿîMUðATB,AX=BMàÉùÇB0ÇEÜMA0¨tJ<¨tJ<MÌþÿ1ÿEÐA`Àäfù¸Óàpÿ$èø¥ñÿUMt`;qvEàÇEÜÀEÇD¸`ÀáuUðæ@T$MÔU$T$èßñÿÀt
>}ØÿuEØöìUØÒu
}ÜuÇEØÿÿEØÄ<[^_]Ãt&uæ@TÇEÜUðëUð»¨üÿÿöB<@_þÿÿMEUL$MD$ET$L$$èÊ©ñÿÀEØ-þÿÿ=ÿÿÇEÜ"þÿÿuÇEÜUðæ@é,ÿÿÿt&ÿÏþÿÿéÿÿÿfEUÐMÔ|$D$T$$è¿ñÿÇEÜéÔþÿÿ´&EUD$$èòÜñÿÀúþÿÿMØÉÿÿÿEØéûþÿÿvUKNþÿMr\ÇD$D$$ÿ×9Æ{ýÿÿuæ@àþÿÿEUÔD$xËþÿ$D$èô¾ñÿUðÇEÜéYþÿÿB0éÏýÿÿD$ÈËþÿMD$EÔL$$è¼¾ñÿUðÇEÜé!þÿÿEà@EàéBýÿÿfÀ$èÁ£ñÿÁ¸ÓàPÿÑèpÿéûüÿÿD$ET$UÔD$üËþÿD$$èW¾ñÿéïüÿÿD$EUÔt$D$0ÌþÿD$$è.¾ñÿÇEÜéâüÿÿD$EUÔD$`Ìþÿ$D$è¾ñÿUðéßüÿÿuæ@écýÿÿvUåWVSì\Eè¶âñÿÃ÷UÔUÄ@ EÈ1ÀUÄÇÀørîEðMì@D$EÇD$ÇD$D$EÈ$èèÆñÿÀEÌ)EÇEÐÀ×¸Ìþÿ1ÿÇEÐ1öUÀëÇ·÷;u±ÇD$ÇD$EÄt$D$EðÇD$D$U$èðÝñÿÀEÌuuEØD$EÔD$E$ÿU U#BL;BHv#BP;EtöE@ÇEÐzÿÿÿt$EÇ·÷D$EÀD$UB$è¨¼ñÿ;uÇEÐSÿÿÿt&EÔÀtD$UB$èëºñÿUBD$EðD$EÈ$è¿ÓñÿÀuEÌÀt EÌÄ\[^_]Ãt&EÌEÌÄ\[^_]Ãf}ÐuÚÇEÌÿÿEÌÄ\[^_]ÃUåWVSì¼EUMèèÝàñÿÃM@ RL$EEU$D$èz¸ñÿÀÆu#EèÀEMD$$èçÓñÿÀÆt
Ä¼ð[^_]ÃEðD$ED$EÇD$ÇD$$èÛÄñÿÀÆuÄEðUà¨üÿÿUÍþÿÇE EÄÍþÿÇE¼lÿÿÿhÿÿÿdÿÿÿë6þÿÿÄÇE¤ÿÿÇE MðE¼QHÀ;U¼MÄÛE¼U¼MÇEÜÇEÔêUÐUIM´lÿÿÿÀM¨t@ÀE¨?UMÄT$AD$E$è¬ñÿÀÆE¤^ÿÿÿU¼$è·ñÿMÄUÐT`EMÜMU¬L$T$$èá«ñÿÇE°ÀÇu2UM¬;JwUÜ¶<
U<MöE@ÌÇE°EÔÀt$è£ÒñÿÀEÌtÿt}ÌEàÀt#UM´D$T$$èØñÿÀÆtEÌÀtuÌEÜÀt-D$U´E$D$è[ØñÿÀtö{þÿÿÆésþÿÿvö¶bþÿÿ}°¶lþÿÿféWþÿÿv¨üÿÿE¨´&é¬þÿÿÆ}ðUMB|$$D$è¨ÐñÿÀ¼} ýÿÿö}ýÿÿféEìrEfNMÀ$è>ñÿøv
}ðu¤ë t&}ðD`ÀtëEÀ$èñÿMT`EL$<|$$èIªñÿÀZÿÿÿUì¶b<ÿÿÿÀÀ<
t<<t8öE@t&çT$E1öUD$B$è×ñÿÇE éÿÿÿvfzrEU|$D$$èë´ñÿÀÆÝþÿÿEèÀ5E|$$èWÐñÿÀÆ¹þÿÿEìD$UMT$A$è¡ÖñÿÀÆþÿÿE¤uÀéÐþÿÿT$ëÐBÇE°À½EàP<ÐàøÉâ÷ÑáúUÀ÷Ð%	Ñ	ÁMÈá@M¸MØMÔÍþÿUÔ,ÎþÿxÿÿÿtÿÿÿpÿÿÿE¸ÀïE¬MUD$L$B$èï³ñÿÀÇ#ýÿÿEØÀU¬MT$A$èUÏñÿÀÇùüÿÿEÜ`<ÿÿÿö@<Eàö@<u}¸ÇE°ÿBö@<t"EÜö@<tu¸ÇE°öô´&tÿÿÿUD$$è¿¨ñÿÀÇüÿÿEÜMäL$M@D$EÔ$è¶Ññÿu°ÀEÈ
|ÿÿÿë,´&ètsu°UEÔT$$èª¸ñÿÀÞu°UäBøuÐ|ÿÿÿL$BD$UD$E$D$èk²ñÿÀÇt¦ÿÿÿ×ûÿÿ¾ë¶MÈL$UD$E$D$èÝñÿÀuÐEÈÇD$ MÇD$ÇD$
¢D$EäÇD$ÇD$L$D$E$è¸ñÿÀÇÿÿÿéfÿÿÿ´&u°EÔ$èæÍñÿÀÇãM°ÇEÔÉÕöEÈ³EÜMpD$E´L$$è´ÓñÿÇEÜÀÇáúÿÿöÙúÿÿU;rlUMt$T$$èY¦ñÿÀÇúÿÿEÜU¬;PtE¸ÇE°Àu¬é4ýÿÿE¬dÿÿÿM´D$T$$è´ñÿÇE°vEàéýÿÿEUD$$èñÿéúüÿÿu°é-ÿÿÿEÐU¬hÿÿÿD$E´T$L$$è:´ñÿÇE°éúÿÿöE@ä¾ÿÿvéføÿÿöE@ÇE°2üÿÿ<ÍþÿUÐM¬D$E´T$L$$èã³ñÿÇE°éüÿÿE¬xÿÿÿM´D$T$$è»³ñÿÇE°éëüÿÿUTÎþÿt$|$D$B$è³ñÿUìéñúÿÿvÆéÌ÷ÿÿEÈM¨U¬D$EÄL$MÐT$UD$EÜL$·@$D$èÀñÿÀÇ
>þÿÿ=ÿÿ
ùÿÿÇE°t&éïýÿÿpÿÿÿE´t$L$$è³ñÿéOþÿÿöE@UìéYúÿÿöE@´&HúÿÿMÎþÿt$|$D$A$è¾²ñÿUìé úÿÿE¸ÀøÿÿM¬tÍþÿL$D$E´$è²ñÿÇE°éaøÿÿU¸ÒOøÿÿM¬ÎþÿL$ëËu°é?øÿÿM¸Îþÿ|$D$A$èE²ñÿéIÿÿÿE¾ÿÿUD$àÌþÿD$B$è²ñÿéföÿÿt&¼'UåWVSèÜÖñÿÃEÈì¼xÿÿÿ1ÀxÿÿÿÇÀørëM¬1ÀÇEà@tÿÿÿµtÿÿÿÇÀørëaþÿ}äE¬ÇE°½lÿÿÿ|$UD$B$è}¶ñÿÀÆ¤M} ÇEÇEç}ÇEEèD¦þÿhÿÿÿt&EÀuU·B9EEèÇD$D$M ÇD$L$ut$}|$ED$U$è×Àñÿ=ZÿÿÆÎÀµEÀM¹x·}ç}EÀöE&}M·D f)ÂfÒtc·ÊdÿÿÿM99½dÿÿÿwM·ÀEEdÿÿÿ+E9Çr7M¶<<'<
>fú¶fÇEÿÿEEéÔþÿÿt&EäD$UB$èwÂñÿML$}<$èuÍñÿÀöu
>EÀtuÄ¼ð[^_]Ã¶ExE%EtJ¸>UU·EÀèþÿÿ}M·D@f)Âéíþÿÿt&}M·Df)ÂéÕþÿÿt&EàøÀàúÀë¨t&ÆÄ¼ð[^_]Ã,¬}ÿÿÿÿt&éóþÿÿfú´&âþÿÿ}U GEìT$lÿÿÿL$µxÿÿÿD$t$}|$E$èlñÿÀÆ	|$ÇD$UT$ML$½hÿÿÿÇD$|$tÿÿÿ$èØ·ñÿuécþÿÿMøu}É7t'}¸>ÿuEàøÀàúÀUU·u¹@ö·4
>èf)ðfEE·uÀt$D$Eä$èL®ñÿEä}uÌEÈ|$ÇD$ED$UT$hÿÿÿÇD$L$µxÿÿÿ4$è·ñÿÀÆýÿÿuéýÿÿMø}9MÉt'U¸>ÒuEàøÀàúÀUU·}¹@ÿ·<
>èf)øöEfEêf}$ýÿÿ·Uuò1Éµpÿÿÿ|ÿÿÿ1Òt&EÁfM¢pÿÿÿ|·f·E¢Ð9|ÿÿÿ}·Ef+E¢fEò·ÐGT$D$Eä$èñÿ·EòuEÌEäEÈt$ÇD$}|$ED$hÿÿÿÇD$T$xÿÿÿ$èåµñÿÀÆtE·Eò·}¢L·ÑB9|ÿÿÿBÿÿÿéLüÿÿUÇEÒ.þÿÿEEé/üÿÿe}ÉáúÁ éÌþÿÿe}ÉáúÁ éëýÿÿUMB9AEìÂr
>öEuÇD$t$}|$ED$hÿÿÿÇD$T$tÿÿÿ$èµñÿÀÆþÿÿéûÿÿUÇD$T$ML$ut$½hÿÿÿÇD$|$xÿÿÿ$èÌ´ñÿÀÆ¶ýÿÿéPûÿÿE 
D$ut$}|$xÿÿÿT$D$UT$M$èc¯ñÿÀÆmýÿÿéûÿÿ´&UåWVSììEèãÏñÿÃ$@LÿÿÿEèD$UT$M$è`ñÿÀÇufu¶F<
tk<tgmËþÿD$Lÿÿÿ$èSñÿÇ\ÿÿÿÇvEèD$UT$Lÿÿÿ$è(ÉñÿÀ´ÿuÇ¶Äìø[^_]ÃvUT$ML$ut$ED$U$èÝ«ñÿÇ\ÿÿÿÀÇMº@xöÄuàøÒâúÂ MufyÊ·2XÿÿÿÇPÿÿÿ9ðµpÿÿÿ¦Xÿÿÿ+U9ÐTÿÿÿÏMä1ö@ÿÿÿÏþÿpÏþÿ@ÏþÿÇPÿÿÿ0ÿÿÿ,ÿÿÿ(ÿÿÿ¶@ÿÿÿD$UT$M$èàñÿÀÇ²þÿÿExÑá$ÿÿÿÅ¸@EM·0¶<R$,ÍöE@Uä¿ÿÿT$ut$UB$èÇñÿÀÿtøÇé+þÿÿvÿ¶Jþÿÿ½\ÿÿÿ=þÿÿ¿ÿÿÄìø[^_]Ãv=ÿÿÇ\ÿÿÿãýÿÿÇ\ÿÿÿéOþÿÿt&ÐàøÀàúÀ é+ÿÿÿvÿ°ýÿÿMPÿÿÿ·A;PÿÿÿÆPÿÿÿXÿÿÿµPÿÿÿ·Hö;pÿÿÿêTÿÿÿð;pÿÿÿpÿÿÿé{þÿÿv<<¶Îþÿÿ$ÿÿÿ¸@ÉuâúÀàúÀ E·0EUÜU@Eà;BlUäöE@þÿÿPÿÿÿ¿ÿÿL$BD$ÔÏþÿD$uF$èe§ñÿUäé_þÿÿ½$ÿÿÿ¸@ÿuâúÀàúÀ E·0EUÐPUÔ@EØÐU;BJUäöE@þÿÿD$Pÿÿÿ¿ÿÿL$BD$øþÿD$uF$è×¦ñÿUäéÑýÿÿvöPÿÿÿcöE@´&úPÿÿÿÀ2EÑá$ÿÿÿ·fjÿÿÿ$ÿÿÿÀVâÚE·T0 Ð÷Ðfjÿÿÿfhÿÿÿ·ÂUf½hÿÿÿD ÿÿÿ:·hÿÿÿuòEðµ8ÿÿÿ4ÿÿÿlÿÿÿ1Éë6´&µ ÿÿÿ·D4ÿÿÿf;EòfLf;hÿÿÿáµ ÿÿÿ·Á·µ8ÿÿÿfB9lÿÿÿsöE@©üÿÿPÿÿÿ¿ÿÿD$Eä@D$,ÿÿÿT$MA$è~¥ñÿUäéxüÿÿfPÿÿÿ¿ÿÿT$Eä@D$ÐþÿD$MA$èC¥ñÿUäé=üÿÿ´&Uä;BýÿÿÀfýÿÿU´1ÀÇÀørñEàÇE¸E´T$Eä@D$E$ètñÿÀÇuUäJ<éÔûÿÿ¶Uä;BýÿÿÀ¥ýÿÿU´1ÀÇÀørñEÔÇE¸E´EØEÀT$Eä@D$E$èñÿUäÇépûÿÿÑá$ÿÿÿt&$ÿÿÿ¸>ÉuÐàøÀàúÀE·0fjÿÿÿ$ÿÿÿÀªýÿÿE·T0@Ð÷Ðfjÿÿÿfhÿÿÿé®ýÿÿ¶UäJ<öEíúÿÿM1ÀHÿÿÿµHÿÿÿÇÀørë|ÿÿÿDÿÿÿ1ÀDÿÿÿÇÀørëMIÉdÿÿÿu³àûÿÿµdÿÿÿf½hÿÿÿEîfÇbÿÿÿ<ÿÿÿ)þÿÿ·bÿÿÿ ÿÿÿµ<ÿÿÿ·D|ÿÿÿEfÀUt(DÿÿÿD$HÿÿÿT$M$ÿdÿÿÿÀ|ÿÿÿ·µbÿÿÿEEE·Eît·hÿÿÿfµbÿÿÿf9ÆuÿÿÿéýÿÿöE@ÌùÿÿPÿÿÿ¿ÿÿL$Eä@D$µ0ÿÿÿt$UB$è¡¢ñÿUäéùÿÿt&M·T1Ð÷Ðfjÿÿÿfhÿÿÿé!üÿÿöEÆ÷ÿÿu~
¹÷ÿÿt$ÇD$E$èF°ñÿÀÇ÷ÿÿÇ\ÿÿÿé÷ÿÿöE@uêPÿÿÿàÎþÿT$MD$L$µLÿÿÿ4$èý¡ñÿÇ\ÿÿÿéJ÷ÿÿföE@uªED$ÏþÿD$Lÿÿÿ$èÇ¡ñÿÇ\ÿÿÿé÷ÿÿt&PÿÿÿD$Eä@D$(ÿÿÿT$MA$è¡ñÿExéÌúÿÿUäJ<épøÿÿUåWVSè<ÆñÿÃ}ìu4$èÍÁñÿ¶~H¶FK¶NI¶VJFHø¶~LFK¶FOVI¶VNNJ¶NMFLø¶~PFO¶FSVM¶VRNN¶NQFPø¶~TFS¶FWVQ¶VVNR¶NUFTø¶~XFW¶F[VU¶VZNV¶NYFXø¶~\F[¶F_VY¶V^NZ¶N]F\ø¶¾ÌF_¶ÏV]¶ÎN^¶ÍÌøÏ1ÀÍÎÄ[^_]Ã¶¼'U1ÒåVSì EèÅñÿÃVuö@ti~
>toNÐÁèÐÁèFÐVVfÁèFÐÁèFÐÁèAÐfÁèAQVNÐÁèFÐÁèAÐfÁèQ1ÒAÄ Ð[^]Ãv4$èL±ñÿÂëèUåWVSì,UEècÄñÿÃ¤xUèP4@8ÀEìtpEèr1ÉUæü}%EðEè:1ÒàEäë¶¨üuQÁò;Mìs7}ð¸@u}äÀàìÀ0ÐE9ørÏöE@tU¸ÿÿÄ,[^_]Ãt&Ä,1À[^_]Ã¶öE@uÙD$L$ED$XÐþÿD$UB$è¿ñÿ¸ÿÿë°L$U$ÐþÿD$T$UB$èñÿ¸ÿÿëfUåWVSì\MEèSÃñÿÃ~ @rEÄ1ÀöuÐ2JzUuB@1Òè÷÷1ÒÈEÈFDè÷÷È9EÈEÌEÔüMEð1ÿuÇEðÇEìIHæ@uàuÈÇEØMÜEÀf9uÔsMÌ9MÈMÔ¾9uÔMÈräEàÀtUt$$è5¡ñÿÀumMÀEÇD$ÇD$ÇD$L$ÇD$t$$èÁñÿÀt[ø"=õÿÿt&MàÉt&t.ÿt&uÇt&ÆéPÿÿÿUàÒ}ØÀøÄ\[^_]ÃEàÀÝEUMt$D$EðT$UL$D$E$D$è¿£ñÿÀtÿÇEØuÇfUÇD$BÇD$ÇD$t$D$Eð$D$è'ÀñÿÀKÿÿÿé,ÿÿÿ¶EÜÀvEÿÿÿumÜMÜVLF<¯ÐrEÔéfþÿÿ¶Fÿ1ÒMÐ÷uÐtÿ)ÖéòþÿÿfEðMUt$D$EL$$D$è ±ñÿ=ÿÿÇ÷À"MEL$$èñÿUEìD$t$$èSñÿÀÇ¢þÿÿEìx<x_¶<µUt$B$èÓ³ñÿÀÇÀEðMUt$D$EL$$D$èeñÿ=ÿÿÇt8ÀEìD$MEÄL$$èë¹ñÿÀÇulÇEìémþÿÿt&ÇEØEìëÇt&¸þÿÿÿ1Ò÷÷ÈEÔéñüÿÿt&ÇEØéÿÿÿMÄ¶ÀD$Ðþÿt$D$$èàñÿÇEØUÇD$BÇD$ÇD$t$D$Eð$D$è4¾ñÿÀu)EìÀdýÿÿMuÄD$L$4$è¹ñÿÀFýÿÿÿKýÿÿøéCýÿÿ¸ÿÿ¶ëã´&¼'Uåì8]ôEðè¿ñÿÃWz}ü}uøEÜD$ÇD$<$èñÿÀu=Uð:
>tEöE@¾T$U|$B$è¸ñÿÀuîÊf]ôuø}üì]ÃvÇD$G$èá±ñÿÀGÀ¢E¾à@EàëefEðU|$D$B$è¸ñÿÀuEÜt$<$D$èÜñÿÀuUðz<x¶<t$G$èe±ñÿÀu5Æ9wr-EàÀuU|$$èCñÿët&¸ÿÿé.ÿÿÿ¶1öUðvéöþÿÿvU¼Ðþÿ¾ÇD$D$B$èÇñÿUðéÆþÿÿMàÉ¶þÿÿU¶ÀD$Ðþÿt$¾D$B$èñÿUðéþÿÿ´&UåWVSìlEUÇEèÇEì@ ÇEäÇEàE¸EðU°D$Mè½ñÿÃOxL$u4$èñÿÀEÈEðö@<@Eà@EÌE1ÿuM@PQXE¤x¾@öÄu1ÿ¨¾0^E¤MÀàü÷âð1ú1ÿ9úEÌ1öÇEÈZÿÿÀnEðD$ML$E¸$è¶ñÿÀtUÈÒîUàÒtEèT$D$U¸$è½©ñÿEäÀtD$M¸$è·©ñÿ}ÈÿtEìÀtD$E¸$è©ñÿMÌÉ#EÈÀuîtG´&EÈÄl[^_]Ãt&Uâ@UÌàþÿÿMèÐþÿD$L$u¸4$èÁñÿé¿þÿÿÇEÈÿÿEÈÄl[^_]Ã¶9ðöþÿÿMuU°ATF0ATBAPF4BAXF8BA\F<BFP¨MÈUu°ÇE¼ÇEÀBPA\UFAMÈÀM°FuE~Hx@VLPDAU´ÀtCu1Ò Hp@îE¨Gÿ÷ñ1Ò<0ø÷u¨1ÒE¼E´è÷ñ1Ò0È÷u¨EÀuät$ÇD$ÇD$M°AhÇD$D$E¸$èC·ñÿÀEÈÌ1öéïýÿÿt&EÈt&éþÿÿv¾1ÿéýÿÿvEÌ¾ÀºýÿÿM`ÑþÿD$L$u¸4$¾è+ñÿéýÿÿfu¤t$E1öD$ÑþÿD$U¸$èÿñÿÇEÈZÿÿéaýÿÿ´&UT$M$èj²ñÿÀÃýÿÿUÈÒËýÿÿEÈéÃýÿÿvEèD$EàD$EäD$U¸$è,ñÿÀEÈ	ÿÿÿEäD$M¸$èÿ¦ñÿU°ÇEäBd$èJñÿt$1öx
>|$M¸$èRñÿÀEÈµüÿÿu°Fd|$1ÿÇD$ÿÿÿÿÇD$D$ÁÑþÿD$Eä$èr¯ñÿÇEÄEÐEèÀÆEìE¬ë
Ç9}èEàUÐ4¸T$Eä4$D$èl®ñÿÀuÔÇD$
>ÇD$MÐ$èzñÿÆE°@ÀtUÀ9U¼s,9u¼À9òÂ!ÂÒuEìÀtdUÄEì4ÂUÄévÿÿÿ9u¼À9uÀÂ	ÂëÑMÄÉtMÄÑþÿD$L$u¸4$è7ñÿEÄ1öUÇEÈBHEìBLéûÿÿM¬L$Eè)øÁàD$E¸$èüñÿÀEÈsÿÿÿ1öéXûÿÿ´&¼'UåWVSè¬·ñÿÃírEÐìE1ÀUÇÀørîM´1ÀMuÇÀørîUMB  @ÎMIP\EìE´EMÔÇE¸)Êè¯FUÀEìEU xE¸@÷EE9E ÁD¦þÿÇE¤ÇE¨ÇE¬U¶öÂü¼öÂ³öE uâf¢MÀEÐuEUL$MÇD$t$D$T$ÇD$$èññÿÀtE¨uEUMt$uÇD$D$T$L$ÇD$4$è³ñÿÀE¤ÔEU xEUt&Eì¿@E¬÷EuEàøÿçìÇ0M1ÒAÀÆE¬ÒæüÑ¯M¬÷æUÊEUUE9E Öþÿÿ}¤u¨MEL$$èR®ñÿÀuM¤Éu	U¨ðÒuøÄ[^_]Ãt&EàøÀàìÀ0éXþÿÿfuEM¤¶ xM¨uEé%ÿÿÿÇE¤1ÿ1öÇE¨évÿÿÿUåì8}ü}uø]ôèµñÿÃApþuG9Æs¸]ôuø}üì]Ãt&EG9ÆrÝUG9ÆWrÐMG9ÆOrÃE GG9Ær¶U$G9ÆWr©M(G9ÆOrE,EìGU0Ò¡W 9ÖUÜzÿÿÿM0AGQEÜÐ9ÆaÿÿÿT$D$EÜ$èñÿU0MÜJE4ÀtnA9ÆEà.ÿÿÿU4BM4EàQÐ9ÆÿÿÿT$D$Eà$èQñÿM4UàQE)ú1ÀéìþÿÿO 9ÎÜþÿÿ1ÀÇEðGëQ9ÖÃþÿÿ1ÀÇEðëÁ¶¼'UåìUuø}ü}ÑMr9ñrÿtNGBF9Ásuø¸}üì]Ã¶EBF9ÁrÞEFEÇ1Àuø}üì]ÃÇÇBëUåì(]ôEðè³ñÿÃGnD$Euøu}üÇD$T$èñÿÀÁt]ôÈuø}üì]Ãt&~UðFBFBFBFBFBFEìBÂ1ÀÇÀørñVEðP EðWÖP1Òp À8ÇÂúrñEðP<UðFuB8B<EéZÿÿÿ¶¼'Uåì(]øEôè²ñÿÃWmD$EuüuÇD$$èñÿÀÁu)UôFBFUôBFBFuE]øÈuüì]ÃUåì]ôè©±ñÿÃêl}ü}uøÇD$<$è¿¢ñÿÀÆ¡EU<$D$T$èßñÿÀÆ|@<ÀEÇ¤Ç¨ ÀtD$<$èÅñÿEÇ |U@<¢øÿÿþÿÀt8D$<$è0ñÿÀt(¾ÿÿë!ÌÑþÿD$<$èòñÿt$<$ènñÿÆð]ôuø}üì]ÃD$<$è	pñÿÀOÿÿÿë³vUåì8uøu]ô}ü}ìè}°ñÿÃ¾k|@<|$4$EàED$ED$ED$èzñÿ=Sÿÿt]ôuø}üì]Ã´&E|$4$D$EàD$èÚñÿëÐ¶¿UåWVSì\Uèö¯ñÿÃ7k}upH<EàEÀ³FUìEðöE¦ØÀöt;ÄUð¾
EìÜºØ1Éþøxt$%øÀ÷ÐàD$EìT$L$D$GD$U$è+ñÿÄ\1À[^_]Ãt&ÜÒjÿÿÿfÈÌ}ÀØÜt:9ÀÀt+öú°´ØÜ¶ØÒª¾
UÐ1ÀÇÀørñöEØÑEÐºÇEÔòþÿÿþ²ðþÿÿÇD$ÇD$ÇD$ÇD$ÇD$ÇD$ÿÿÿÿE$è%ñÿÄ\1À[^_]Ã´&øüUìEðéAþÿÿÜ¾ÀHÿÿÿé>ÿÿÿ;VÀéöþÿÿt&F;Ü-þÿÿé´þÿÿt&ÇØÇÜéïþÿÿ´&UåìXU]ôMuø}ü}è|èñÿÃÅhÇEð@<EÐp@<|$L$$EÌEðD$ED$ED$èÕñÿ=ÿÿÿÆtò=Sÿÿt&Àè}ðÿt&ØMyË}ÐGwÀ2MÌ}øüEàOUä9ÁÀÀtUMàBEäþþµEÌ°ÈöuÌÉuUÐMÌB\ðEà}ÐD$EÇD$|$$èÚ~ñÿÆGÀt+UD$$èñÿÀt¾ÿÿëv=úÿÿvÿÿÿð]ôuø}üì]Ãv|$EÐ}UD$|$$èÇñÿÀÆuËéîþÿÿMÐAÀu1öt&ë´}D$<$èñÿÀu1öë´&E9PÀéôþÿÿD$E$èkñÿÀ·þÿÿéTÿÿÿ¶Uåì]ô}üÇuøU pEÌèr«ñÿÃ³fE1Àr<MÇÀørîJ<ÀF4V0EìUèÀUB9Eèw¾óÿÿð]ôuø}üì]ÃMÀU EèEèÇEìÇD$L$ED$$èsñÿÀt{öG0 uMEöùt¤E1öUÇD$ÇD$ÀÇD$D$ÇD$T$<$èñÿéiÿÿÿMAD$A<$D$ÒþÿD$èIñÿëvMEU ÇD$L$D$$èÓñÿÀ\ÿÿÿM AEìEðED$$èuñÿÀÆòþÿÿU°1ÀÇÀørñMT$EUÇE´M°ÇD$ÇD$D$ÇD$T$<$è³ñÿéþÿÿfD$<$èiñÿÀu$pH<éTþÿÿfD$<$èÐñÿÀTþÿÿ¾ÿÿéZþÿÿfUåWVSìÌUèc©ñÿÃ¤d}|@<\ÿÿÿEÀt
>MAÀucU 1ÀXÿÿÿXÿÿÿÇÀørëWGUÜEàEÜUàEÔEðD$EUØ$èUjñÿÀÆtSÄÌð[^_]Ã¶öB0 tBD$D$GD$GD$0ÒþÿD$E$èñÿé`ÿÿÿvXÿÿÿMÜEðÇD$TÿÿÿT$L$$èñÿÀÆt0=óÿÿ%Eð$èñÿÀ_ÿÿÿöWÿÿÿÆéPÿÿÿvXÿÿÿTÿÿÿMÇD$D$EÇD$@T$ÇD$L$$èîñÿ\ÿÿÿôà`ÿÿÿt<EèMD$EìD$dÿÿÿD$EÇD$L$$èÅñÿÀÆJÿÿÿU¼1ÀPÿÿÿPÿÿÿÇÀørëE|B<À\ÿÿÿAPEÈATÇEÐEÌXÿÿÿEÄB<À¿}ÿXUröJ}Ð@EðMäLÿÿÿvXÿÿÿPÿÿÿÇD$$T$L$èñÿÀÇâMU¼;:ÀÀ=;UÔtxLÿÿÿD$Eð$èqñÿÀÆÃU1ÀÇÀørñEÔLÿÿÿT$UD$EÇEMÇD$ÇD$ÇD$D$$è>ñÿ`ÿÿÿÉ¼PÿÿÿEUÇD$ÇD$L$D$$èDdñÿÆö.E¼UÀMEÔEðPUØQÒt
>}ÐÐþÿÿ`ÿÿÿÀuýÿÿdÿÿÿD$EÇD$@$èIlñÿÀPýÿÿöHýÿÿÆvé>ýÿÿv@9EÀf¸þÿÿþë¦¶PÿÿÿXÿÿÿUÇD$@D$D$dÿÿÿL$D$$èÏwñÿ=QÿÿÆ0ÿÿÿéýþÿÿ\ÿÿÿMUð|$$EL$èùÿÿ=óÿÿÆtMÀýÿÿé¦üÿÿv=óÿÿÆhÿÿÿ\ÿÿÿöùÿþÿÿ1öéøþÿÿþÿÿìþÿÿþféãþÿÿ\ÿÿÿöùSüÿÿG¾MD$G$D$XÒþÿD$è¬ñÿé&üÿÿD$E$è¸ñÿÀ*ýÿÿ¾ÿÿéwûÿÿUD$$è·cñÿÀuãM|éÐüÿÿö¼'UåWVSìÌUè#¤ñÿÃd_|@<$XÿÿÿEðD$èdeñÿÀÆtÄÌð[^_]Ãt&} 1À½TÿÿÿTÿÿÿÇÀørë½Xÿÿÿôà\ÿÿÿtaEèUD$EìD$EÇD$$D$dÿÿÿD$èñÿÀt+ÆEð$è"ñÿÀlÿÿÿödÿÿÿÆt&éYÿÿÿv}¼1À½PÿÿÿPÿÿÿÇÀørë}|A<ÀJXÿÿÿ}BPEÈBTEÌGWÇEÐEÀEØTÿÿÿU¼UÔEÄA<ÀEÜ½TÿÿÿD$EðÇD$|$$èFñÿÀ`ÿÿÿt=óÿÿõµ`ÿÿÿéÿÿÿfUzó¿TÿÿÿPÿÿÿ|$D$EðT$$èïñÿÀÆq}¼t	ÿÊ1ÿ}Ðt&EäLÿÿÿEÔ9E¼t{LÿÿÿEðT$$èðlñÿÀÆ,U1ÀÇÀørñEÔ½LÿÿÿT$UD$EÇE}ÇD$ÇD$ÇD$D$$èñÿE¼9EÜ½XÿÿÿöùuÀz\ÿÿÿ¿ÀwPÿÿÿE|$ÇD$T$UD$$ès_ñÿÆöueU¼EÀUÔUðBÇD$$EØTÿÿÿD$PÿÿÿD$èñÿÀÆu)}Ðt?ÿt&Áþÿÿfë.¶=óÿÿvtn1ÿþóÿÿ¶tþÿÿt¶µ`ÿÿÿ\ÿÿÿÀþÿÿUÏ@dÿÿÿ|$D$$ègñÿÀãýÿÿÆ`ÿÿÿÀ÷üÿÿéÎýÿÿv}EUð|$½XÿÿÿD$E<$è®ôÿÿÀÆ>þóÿÿö¶àýÿÿfé¢üÿÿvEà9EÀfsþÿÿfkþÿÿf\ÿÿÿ1ÿÀþÿÿøPÿÿÿÈ@D$TÿÿÿT$T$D$dÿÿÿD$E$è>rñÿ=QÿÿÆpþÿÿéAþÿÿXÿÿÿöùüÿÿéóüÿÿR¿Òýÿÿéøüÿÿv½PÿÿÿEUÇD$ÇD$ÇD$|$ÇD$D$$è0ñÿé¾ûÿÿUD$$èlñÿÀJüÿÿ¾ÿÿéûÿÿ½XÿÿÿöùfüÿÿéûÿÿTÿÿÿPÿÿÿÇD$D$EðT$$èkñÿÆéþÿÿD$<$è(^ñÿÀu |éûÿÿUåWVSìLEèñÿÃ×YÇEð@ EÐEÀU;BüMuðÇEàuÌáMÜéøfEðuxÑáMÈCöÂRp ·x¸ uØu9ÈvuÈ¸@öuâúÀàúÀ Ï)ÇEàUMøEÔT$D$A$è´ñÿÀÆuEØ6uàUà|$D$$èyñÿUðMÐBÇD$T$$EèñÿÀÆÄEÇEðÀu;FøUÔUàD$E$èÿñÿÀÆUÌEMÐÇD$ÇD$T$D$$èñÿÀÆuR}Üÿ·þÿÿEðxþÿÿ¾ÿÿëSvp@·x¸@uØéÁþÿÿt&H·x¸MØé©þÿÿt&EàEÔEÜÀtEÔMUAEðÀt!MÐÇD$D$$è	ñÿÀtöuÆÄLð[^_]ÃÇEÔf1öë±¶¿UåìXEUM]ô}ü}uø@Rè1ñÿÃrW9yEÐUÌs¾ÿÿð]ôuø}üì]Ãt&EðEÄD$|$$èhñÿÀÆuÐUðJ4MÜ¶<tlöE@¾ÿÿÇEØMEÐT$L$$ètñÿÀtöuÆ¶ë¶ö¶nÿÿÿ}Ø¶^ÿÿÿféRÿÿÿvBUìÇEØUÈÀhÓþÿMÀé¡fUðEìÀtÿÿÿMB8)Eá@MàíJÉMÔ£E;HöMEÐT$L$$è¹ñÿÀÆÏþÿÿUÄMÔET$L$$èvgñÿÀÆ¬þÿÿEð@9øtUàÇEØÒ}ÔEÈUÌ|$D$$èWrñÿÀÆYMÜ;MìUUÌ|$$èÂñÿÀÆ4÷EÿÿÿUðB<öÄdÌB<éøþÿÿt&UE$D$èz_ñÿUðéùþÿÿ¶D$UÔMÀEÐ|$T$L$$èuñÿéFÿÿÿföE@MìÇEØMÈþÿÿD$¨ÒþÿD$EÐ|$$èàtñÿUìÇEØUÈéRþÿÿf¶À¾ÿÿD$|ÒþÿD$EÐ|$$è§tñÿUðÇEØé®ýÿÿEÀ£ýÿÿEàÇEØÀýÿÿUÐÌÓþÿ|$D$$èbtñÿÇEØ´&UðébýÿÿöE@tjUð¾ÿÿéOýÿÿuàöuïUÐ\Óþÿ¾ÿÿL$|$D$$ètñÿUðéýÿÿöE@u¿MÐ Óþÿ¾ÿÿ|$D$$èäsñÿUðéòüÿÿäÒþÿ¾ÿÿD$EÐ|$$è¾sñÿéeÿÿÿ¶¼'Uåì8]ôEðèvñÿÃ·S}ü}D$Euø|$$èùdñÿÀÆtð]ôuø}üì]ÃUME|$T$UL$D$$èàtñÿÇEàÀÆt=ÿÿtÇEàUðë&t&ÇEàMUð·AÀB4t`M·AB8T$EUD$B$èñÿÀu)öbÿÿÿ}àt&Sÿÿÿ¾ÿÿt&éDÿÿÿvÆ¶é4ÿÿÿvöE@ÇEàt&uUðÓþÿ|$D$B$èvrñÿUðÇEàécÿÿÿU1ÀåUât¸)Ð]Ãv¼'UÁåB	SìèñÿÃGRøv$=Õþÿ¶D$$èrñÿÄ[]Ã¶TÕþÿØÿàt&ÂÔþÿëÐ+ÕþÿëÈ
ÕþÿëÀxÔþÿë¸øÔþÿë°LÔþÿë¨ßÔþÿë $ÔþÿëUåWVSìEèsñÿÃ´QUhÿÿÿe¡Eð1ÀhÿÿÿPlÿÿÿhÿÿÿ¸L¸ÿ§R(u4$pÿÿÿèoxñÿlÿÿÿ4$|$T$èùhñÿÔþÿD$4$ÇD$)èßhñÿlÿÿÿ4$|$D$èÉhñÿt$u4$èkñÿpÿÿÿt$ÇD$ÇD$0$èÓfñÿøt*Âhÿÿÿèuþÿÿ¸Uðe3uIÄ[^_]Ãpÿÿÿt$ÇD$ÇD$$èfñÿÂ1Àút½hÿÿÿè"þÿÿ¸ë«è'¶UåìhEU]ôèñÿÃTPEÀEU¼eUð1ÒuøuE¸E¼}üÀt
>ötöEt$¿Uðe3ø¨]ôuø}üì]ÃUÀEÌE´D$$èG[ñÿÀÇuÆE´UßÇD$U°$D$èDñÿÀxLEt$t$ÁàD$E¼0D$E°$èfñÿÀx7EÌU¸EÐBEÔBEØBéYÿÿÿÂEÀf¿è
>ýÿÿéFÿÿÿèð%ÂEÀ¿èñüÿÿé-ÿÿÿ¶¿UåìHE]ôeUð1ÒèÚñÿÃOEÐEuøu}ü}Àt
>ötöEt%¸Uðe3¶uz]ôuø}üì]ÃD$EßÇD$EÌ$è:ñÿÀx:EUÌt$t$Áà$D$|$èUñÿÂ1ÀÒyEÐè)üÿÿ¸ëfÂEÐèüÿÿ¸étÿÿÿè÷$´&UåSìEèñÿÃIND$E$èñÿÄ1À[]Ãt&UåVSèÝñÿÃNì uÿÿÿÿÿÿFÐÿÿÿFüÿÿFýÿÿFEôD$EÇD$dÇD$$èmñÿÀÂuEôF(Ä Ð[^]ÃUåWVSì<UèVñÿÃMXÀdM`ÀUðÇEØUÔt&M\=oT=qYM¹`1öët&uà7T>FEàâÿÿÿ%	ÂÐâÑè3743xÕþÿ}àuÁ¾ëfuÜ7VUÜT>%âÿÿÿ	ÂÐâÑè37tüÿÿ3xÕþÿ}Ü¼	uÁ¼	M%âÿÿÿ	ÐÂàÑê303xÕþÿ1ÀÇ\¼	ÀM\ÐMÁè1ÐÂÁââV,1ÂÐÁà%Æï1ÐÂÁê1ÂEØÒÄþÿÿÀøEØµþÿÿUXÀ1ÀÄ<[^_]ÃfUº`ët&uèt&Et$$è5RñÿUÔÇD$ÇD$t$T$Ç$è¾lñÿMðÉtÃE1ö¸`iÑÍ
f1ÉÂÐÁèiÒÍ
	È·ÆþpJuÖUÇ\pé$þÿÿÈ`D$ÇD$À	ÇD$$è
kñÿÀ/ÿÿÿEÇ\qéýÿÿD$$è7OñÿÀýÿÿ¸ÿÿéÿþÿÿD$$èùvñÿÀéþÿÿëàUºüÿÿÿåì4$u|$M}Fÿøw,ðÉºtWGABABABºÐ4$|$ì]Ãt&UåìXuøue¡Eð1ÀU¸ýÿÿÿ]ôè ñÿÃaJö}üu$Uðe3ß]ôuø}üì]Ã´&}¸ÿÿÿÿwÑ¶E}t}Àt}¸þÿÿÿu«´&EÒ}ÐFt'EÇD$ T$<$ÁøÁèEÁøD$èX[ñÿEÀu=UFP|$$T$è{QñÿFLU@|$$T$è_Qñÿ¸é-ÿÿÿE|$D$FP$è.oñÿFLëÁèø´&UåìUE]ôèñÿÃAIUeUð1ÒÀuøu}ü}t,öt(>t#ÿt=UÒ~5öEft6¸øÿÿÿë¶¸ûÿÿÿUðe3u]ôuø}üì]Ã1Àëâè`UÁúU¶úØúu¾UÐUP@EÐBEÔBEØBEÜEèÀE¤UäU°UìUÀUEàEEèE´FPE}¨U¬EU¨D$T$FLD$E$èI|ñÿUEÐ1U°EÔ1U´EØ1UÀEÜ1U¨UU¨BUBU¨BUBU¨BUBUU¬UBU¬BUBU¬BUBU¬BÂm¤E¨U¬U¤ÒKÿÿÿEèÁàEÇEU|$D$FL$D$è{ñÿUEÐ1U°EÔ1U´EØ1UÀEÜ1¶uïFÿøGþÿÿ¹)ñùt;¶D
à}ðE¼E9u¼Ttéþÿÿt&¶Â;E¼þÿÿ9ú´&uæUEL$T$$ègñÿEÁà)ðéðýÿÿEVPUèÀE~JÇE EU E D$D$FLD$E$è¯zñÿmME ÉËEèÁàEÇUàT$|$FLUD$E$èrzñÿ¶uïþSýÿÿ¹)ñùCÿÿÿ¶T
à}ðEU¸9u¸Tté'ýÿÿt&¶Â;E¸ýÿÿ9ú´&uæ¶éýþÿÿUàEäUUèE°EìU´VPEÀUéFþÿÿUåWVSì|E}UMè}ñÿÃ¾EEe¡Eð1ÀÿUMÂuö·¶< MÉtUÒtxMÁé<M¬<l,}E¬Àf~?E1ö}¬ÀPE EïUM ðD$EðÆD$BL$D$è'yñÿÿÏE¬Áàë	´&1ÀUðe3öÄ|[^_]ÃU:Tÿÿÿ¸ûÿÿÿëÕEÐEGWEÐBEÔBEØBEÜE¬À~Uàu¬UUMäEèM¼}ìEÀÂPU´MîEUL$M´D$BL$D$èxxñÿUM¼EÐ1UÀEÔ1EØM1EÜ1UABABABMUABABABÂEöUsÿÿÿééþÿÿèE¬OM°ÀÓþÿÿEMàU¬M@E¤U¸U1öMBABABAt&EMU°D$T$ALD$E¤$è©Zñÿ1Év¶T¶DÒÀè	ÐDÁùuãMòÁúU¨¶G¶ñ÷ÑáÀÓúñâá	ÂÆW¶EàU¨%ÓèM0þmÿÿÿm¸u¸ö÷ýÿÿÁMEé,ÿÿÿë
UåWVSì|EUuèñÿÃÑBEEUeUð1ÒöE£EÀE8EÀEÀUÁêU¨¶<<|,uVE¨À~?E1ö}¨ÀPEEïUðD$EðÆD$BLD$E$è?YñÿÿÏE¨Áàë´&¸ûÿÿÿUðe3uÄ|[^_]Ã1Àëèè~E¨VU¼À~ÂEU¨@E EàUÀEUUUBUBUBUBUBUBÇE¤t&U¼ET$UD$BLD$E $èXñÿE¤}M¤ÁøÇ¶Eàá%Óè1É0t&¶T¶DÒÀè	ÐDÁùuãM¤¶¶V÷ÑáÓøÒà	ÐFE¤}¤oÿÿÿmÀ}ÀÿÑþÿÿEEéÿÿÿE¨À¹þÿÿEàEEäE¬EèE°EìE´EV}Ðu¨ÀPE¸ëEîBGBGBGUEÐ3UUEÔ3BU¬UEØ3BU°UEÜ3BU´UET$UD$BLD$E¸$èRWñÿEEUÀöuÿÿÿéýýÿÿ¶¿Uåì¨EU]ôe
Mð1Éè¤ñÿÃå?Àuøu}ü}Uèÿà?×öt&èUÒt&ØUÁúU¶úÌúUÀE OPEàMÒEÔUäU¸UMèM¼EìMÐEÀU¬ÇE¨xÿÿÿU EE¨xÿÿÿE´BABABAU¨EÐM3EÔ3DU¸M¨U¼EØ3DEÜ3DMÀUE´D$T$GLMD$$èÞUñÿE´E¨m¬E oÿÿÿEUÁàDðUE ÁâUÖE¹Ê+UÁà)ÁÉE°tÿÿÿ~&1ÒM ¶M2Â;tÿÿÿ|å½tÿÿÿ3u Eðtÿÿÿ¶U°µtÿÿÿM|ÿÿÿÐ2ÆÁ;|ÿÿÿuìUMT$L$GLD$E$èUñÿEÀÁàë
>t&¸ûÿÿÿUðe3u]ôuø}üì]Ã1ÀëãèQOPMMÉtHEÇE¤EEU¤E¤MD$D$GL$D$èTñÿE¤muÐEÁàEÆE¹Ê+UÇD$Áà)ÁEEàML$t$E$è¿NñÿUEET$T$$èMñÿEMUD$L$GL$D$èTñÿéýþÿÿUåì8]ôèñÿÃÚ<}ü}uøÇ$èScñÿEðÇD$
>D$<$è\]ñÿøÿÆÅ?u8uöýÕþÿD$E|$$ÿ¸]ôuø}üì]ÃEð¶Àt<
>uº;us5MÉ2E|$D$øÕþÿD$E$ÿ¸"ë¬fUÒt);u¶vEÀE|$D$HÖþÿë·E01Àénÿÿÿt&è§zñÿø"-ÿÿÿEÀt&teç
þÿD$E|$ÇD$"$ÿ¸"é$ÿÿÿfE|$ÇD$D$¬ÕþÿD$´ýÿÿ$è7Eñÿ¸éëþÿÿÇ$"è@ñÿ|$D$ED$ÕþÿD$´ýÿÿÇD$$èðDñÿ¸"é¤þÿÿfE|$D$ED$ÐÕþÿë¾E|$D$ED$Öþÿë¤t&Uåì8]ôèñÿÃÊ:}ü}uøÇ$èCañÿEðÇD$
>D$<$èQñÿÆÿÿÿøý?u:EÀ÷ÕþÿD$E|$$ÿ¸]ôuø}üì]ÃvEð¶Àt<
>u¸;uEÀt&*E|$D$ÖþÿD$E$ÿ¸"ë¢fèÇxñÿø"cÿÿÿEÀt&ç
þÿD$E|$ÇD$"$ÿ¸"éVÿÿÿ¶;u~[EÀ¶tZE|$D$èÖþÿéoÿÿÿE|$ÇD$D$¬ÕþÿD$´ýÿÿ$è'Cñÿ¸éñþÿÿE01ÀéäþÿÿE|$D$ED$¼ÖþÿD$´ýÿÿÇD$$èÜBñÿ¸"é¦þÿÿ¶E|$D$ED$pÖþÿëº¶Ç$"è>ñÿ|$D$ED$ÕþÿëUåWVS}uèV}ñÿÃ8¶¶WÁà1Â¶GÁà1Â¶GÁà1Â¶W¶GÁâÁà1Â¶G1Â¶GÁà1ÂV¶W¶G	ÁâÁà1Â¶G1Â¶G
>Áà1ÂV¶O¶G
ÁáÁà1Á¶G1Á¶GÁà1ÁN}.¶W¶GÁâÁà1Â¶G1Â¶GÁà1ÂV¶O¶GÁáÁà1Á¶G1Á¶GÁà1ÁN}ÀE¶W¶GÁâÁà1Â¶G1Â¶GÁà1ÂV¶O¶GÁáÁà1Á¶G1Á¶GÁà1Á1ÀN}1ÿëj¶È¶ÑÁè¶ûþÿûþÿ%ÿ1ÐÊÁêâÿûþÿ3Fðâÿ1Ð¶Õûþÿâÿ1ÐF3FôF3FøF3FüFÁ¶ÁÆ ÿþÿûþÿÇ3Và%ÿ1ÂÈÁè¶ûþÿ1ÂÈÁè%ÿûþÿ%ÿ1Â¶Åûþÿ%ÿ1Â3VäV3VèÑ3NìÿVN$ÿÿÿ¸[^_]Ãf1ÿët&3FøF3FüFÁ¶ÁÆÿþÿûþÿÇ3Vè%ÿ1ÂÈÁè¶ûþÿ1ÂÈÁè%ÿûþÿ%ÿ1Â¶Åûþÿ%ÿ1Â3VìV3VðÐ3Fôÿ VFzÿÿÿ¸[^_]Ã1ÿët&Á¶ÁÆÿþÿûþÿÇ3Vð%ÿ1ÂÈÁè¶ûþÿ1ÂÈÁè%ÿûþÿ%ÿ1Â¶Åûþÿ%ÿ1Â3VôV3VøÐ3Füÿ(VFu¸
>[^_]ÃUåWVSì,EèöyñÿÃ75}D$E<$D$èï<ñÿEàÁàÀEäEà1öÇEìÁàEèEäDEðvMè·mè·MðT·mðD·EìL·mìEäDD·EäLDL·D·EäÆL)ð9ð }ào¾ÇÆ¶Á¶ûþÿÈÁè¶ûþÿãþÿ3×þÿÈÁè¶Í%ÿ¶ûþÿ3Ûþÿ¶ûþÿO3ßþÿ¶Á¶ûþÿÈÁè¶ûþÿãþÿ3×þÿÈÁè¶Í%ÿ¶ûþÿ3Ûþÿ¶ûþÿO3ßþÿ¶ÁW¶ûþÿÈÁè¶ûþÿãþÿ3×þÿÈÁè¶Í%ÿ¶ûþÿ3Ûþÿ¶ûþÿO3ßþÿ¶ÁW¶ûþÿÈÁè¶ûþÿãþÿ3×þÿÈÁè¶Í%ÿ¶ûþÿ3Ûþÿ¶ûþÿ3ßþÿW9uàþÿÿEàÄ,[^_]Ã¶¿UåWVSìUMè£wñÿÃä2¶	ÁàEØ¶B1EØ1MØ¶BMÁà1EØ¶BIÁà1EØ¶B1ÈEÜ¶BÁà1EÜ¶BÁà1EÜ¶BÁà1EÜE¶r¶J3p¶BÁà1Æ¶B	Áà1Æ¶B
>Áà1ÆE3H¶BÁà1Á¶B
Áà1Á¶BÑ}UÁà1ÁEUðEìé	fEàúuðâÿ÷þÿÁèëþÿ61ÈMè1ðEØEäÁè%ÿïþÿ¶Å´óþÿEä1UØ¶Uà1uØuðÁèëþÿ÷þÿv1ÈùÁï1ðEÜEèÁè%ÿïþÿ¶Å´óþÿEè1UÜ¶Uä1uÜÁè´ëþÿEð3´÷þÿUà3pø%ÿ3´ïþÿ¶Æ3´óþÿ¶EèÁï»ëþÿÁê3÷þÿEð3H¶ÂUä3ïþÿ¶Æ3óþÿEØ¶ÑÁèëþÿEà÷þÿ1EàEÜUðÁèR%ÿ1Uàïþÿ1Uàò¶ÆóþÿEÜ1Uà¶UØÁèëþÿEä÷þÿUð1EäðÁè%ÿR1Uäïþÿ¶Å1UäóþÿðÁè1UäëþÿÁé¶UÜEè÷þÿUð1Eè¶ÁÁé¼ëþÿR1Uèïþÿ1UèUØÁmØMð¶Æóþÿð%ÿ3¼÷þÿ1Uè¶EØUÜ3yÁ Mð3¼ïþÿ¶Æ3¼óþÿmì×ýÿÿEàÁeMMÁèûþÿø%ÿ¶ûþÿâÿ1ÂEä3Áè%ÿûþÿ%ÿ1ÂEè¶ô³ûþÿu%ÿ1ÂÐÁèÐÁèFÐÁèVFEäÁèûþÿ¶Eàâÿ¶ûþÿ1ÂEè3QÁè%ÿûþÿ%ÿ1Âø¶ô³ûþÿu%ÿ1ÂÐÁèFÐÁèFÐÁèVFEèÁèûþÿ¶Eäâÿ¶ûþÿ1ÂÁïø%ÿûþÿÁï3Q%ÿ1ÂEà¶ô³ûþÿu%ÿ1ÂÐÁèFÐÁèF	ÐÁèV»ûþÿF
>¶EèÁmàâÿ¶ûþÿ1Â¶Eà3QMäûþÿ%ÿ1Â¶Åûþÿ%ÿ1ÂÐÁèFÐÁèF
ÐÁèFVÄ[^_]ÃvUåWVSìUMèãrñÿÃ$.¶	ÁàEØ¶B1EØ1MØ¶BMÁà1EØ¶BIÁà1EØ¶B1ÈEÜ¶BÁà1EÜ¶BÁà1EÜ¶BÁà1EÜE¶r¶J3p¶BÁà1Æ¶B	Áà1Æ¶B
>Áà1ÆE3H¶BÁà1Á¶B
Áà1Á¶BÑ}UÁà1ÁEUðEìé	fEà¶UäuðÁèãþÿ×þÿ61ÈMè1ðEØøÁè%ÿÛþÿ¶Å´ßþÿEä1UØ¶Ñ1uØuðÁèãþÿ×þÿv1Èù1ðEÜEàÁè%ÿÛþÿ¶Å´ßþÿEè1UÜú1uÜâÿÁïÁè»×þÿ´×þÿEð3´ãþÿUà3pEäÁè%ÿ3´Ûþÿ¶Æ3´ßþÿ¶Â3ãþÿEð3HÁmè¶EèUä3Ûþÿ¶Æ3ßþÿEØ¶UÜÁè×þÿEàãþÿUð1EàÈÁè%ÿR1UàÛþÿ1Uàò¶ÆßþÿEÜ1UàòâÿÁè×þÿEäãþÿ1EäEØUðÁèR%ÿ1UäÛþÿ¶Å1UäßþÿðÁè×þÿÁî1Uä¶ÑÁéEèãþÿ1EèEÜUð¼×þÿMðÁè%ÿR1UèÛþÿ1UèUØ¶Æßþÿ¶EØ1UèUÜ3¼ãþÿð%ÿ3yÁ 3¼Ûþÿ¶Æ3¼ßþÿmìMðÏýÿÿEàÁeMMÁèçþÿ¶Eäâÿ¶çþÿ1ÂøÁè%ÿçþÿ3%ÿ1ÂEè¶ô³çþÿu%ÿ1ÂÐÁèÐÁèFÐÁèVFEäÁèçþÿ¶Eèâÿ¶çþÿ1ÂEà3QÁè%ÿçþÿ%ÿ1Âø¶ô³çþÿu%ÿ1ÂÐÁèFÐÁèFÐÁèVFEèÁèçþÿø%ÿ¶çþÿâÿ1ÂEä3QÁïÁè%ÿçþÿ%ÿ1ÂEà¶ô³çþÿu%ÿ1ÂÐÁèFÐÁèF	ÐÁèV»çþÿF
>¶EàÁmèâÿ¶çþÿ1Â¶Eè3QMäçþÿ%ÿ1Â¶Åçþÿ%ÿ1ÂÐÁèFÐÁèF
ÐÁèFVÄ[^_]ÃUåSènñÿÃ_)è¸WñÿUåVSèýmñÿÃ>)ñÿÿøÿt³ñÿÿ´&îÿÐøÿuô[^]ÃUåSìè[Ã)èmñÿY[ÉÃsasldbParameter Error in plugin_common.c near line %dOut of Memory in plugin_common.c near line %dUnexpectedly missing a prompt resultencoded packet size too big (%d > %d)make_prompts() called with no actual promptsAuthorization NameAuthentication Name%s@%s: %s
>*userPasswordBad Key in _sasldb_parse_keyNo secret pointer in _sasldb_getsecretOut of Memory in _sasldb_getsecret_sasldb_getkeyhandle has failedKey is too large in _sasldb_parse_keyKey is too large in _sasldb_getnextkeyDB failure in _sasldb_getnextkey/etc/sasldb2sasldb_pathverifyfile failedUnable to open DBerror closing sasldb: %sDatabase not checkederror updating sasldb: %sCouldn't update dbunable to open Berkeley db %s: %sDatabase not OK in _sasldb_getkeyhandleMemory error in _sasldb_gethandleBad parameter in db_berkeley.c: _sasldb_getdataCould not allocate key in _sasldb_getdatauser: %s@%s property: %s not found in sasldberror fetching from sasldb: %sBad parameter in db_berkeley.c: _sasldb_putdataCould not allocate key in _sasldb_putdataerror deleting entry from sasldb: %sUnknown error: %dSuccessful return: 0%s: Thread/process %s failed: %s%s: file limited to %lu pagesRecord length error%s: Unknown flag: %#xcombination DB_DONOTINDEX: Secondary index callback returns nullDB_BUFFER_SMALL: User memory too small for return valueDB_KEYEMPTY: Non-existent key/data pairDB_KEYEXIST: Key/data pair already existsDB_LOCK_DEADLOCK: Locker killed to resolve a deadlockDB_LOCK_NOTGRANTED: Lock not grantedDB_LOG_BUFFER_FULL: In-memory log buffer is fullDB_NOSERVER: Fatal error, no RPC serverDB_NOSERVER_HOME: Home unrecognized at serverDB_NOSERVER_ID: Identifier unrecognized at serverDB_NOTFOUND: No matching key/data pair foundDB_OLDVERSION: Database requires a version upgradeDB_PAGE_NOTFOUND: Requested page not foundDB_REP_DUPMASTER: A second master site appearedDB_REP_HANDLE_DEAD: Handle is no longer validDB_REP_HOLDELECTION: Need to hold an electionDB_REP_IGNORE: Replication record ignoredDB_REP_ISPERM: Permanent record writtenDB_REP_JOIN_FAILURE: Unable to join replication groupDB_REP_LEASE_EXPIRED: Replication leases have expiredDB_REP_LOCKOUT: Waiting for replication recovery to completeDB_REP_NEWSITE: A new site has entered the systemDB_REP_NOTPERM: Permanent log record not writtenDB_REP_UNAVAIL: Unable to elect a masterDB_RUNRECOVERY: Fatal error, run database recoveryDB_SECONDARY_BAD: Secondary index inconsistent with primaryDB_VERIFY_BAD: Database verification failedDB_VERSION_MISMATCH: Database environment version mismatch%s: attempt to modify a read-only databaseLog sequence error: page LSN %lu %lu; previous LSN %lu %lu%s: replacement length %lu differs from replaced length %lu%lu larger than database's maximum record length %luDB environment not configured for transactions%s%sprevious transaction deadlock return not resolvedTransaction not specified for a transactional databaseCDS groups can only be used in a CDS environmentTransaction specified for a non-transactional databaseOperation forbidden while secondary index is being createdTransaction and database from different environmentsTransaction that opened the DB handle is still active%s: Unexpected code path error%s: Unexpected database type: %sPANIC: fatal region error detected; run recovery%s: DB_READ_COMMITTED, DB_READ_UNCOMMITTED and DB_RMW require lockingillegal flag %sspecified to %spage %lu: illegal page type or formatunable to create/retrieve page %lu±vïÿ¦vïÿvïÿvïÿvïÿzvïÿovïÿdvïÿYvïÿNvïÿCvïÿ8vïÿ-vïÿ"vïÿvïÿvïÿvïÿöuïÿëuïÿãuïÿÛuïÿÓuïÿËuïÿÃuïÿ»uïÿ³uïÿ«uïÿ£uïÿDB->get_typeDB->get_multipleDB->get_dbnameDB->get_byteswappedDB->set_pagesizeDB->set_append_recnoDB->set_lorderDB_NOT_DURABLEDB->set_flagsDB->dup_compareDB->set_encryptDB->set_cachesizeDB->set_allocDB->get_encrypt_flagsDB->get_cachesizedb_createpage sizes may not be smaller than %lupage sizes may not be larger than %lucall implies an access method which is inconsistent with previous callsDatabase environment not configured for encryptionXA applications may not specify an environment to db_create@ @%s: metadata page checksum error%s: unexpected file type or formatInvalid subdatabase type %d specifiedDB_CREATE must be specified to create databases.DBTYPE of unknown without existing file%s: Invalid type %d specifiedDB->get_open_flags__db_dbopenâ¢ïÿØ¤ïÿ8¥ïÿ¥ïÿè£ïÿ°¤ïÿShared/readNot grantedExclusive/writeWait for eventIntent exclusive/writeIntent shared/readIntent to read/writeRead uncommittedWas writtenUNKNOWN LOCK MODEDATA=END
>queueUNKNOWN TYPE\\%c%clen: %3lu data: %#.2x...duplicate: page: %4lu	magic: %#lx	version: %lu	pagesize: %lu	type: %lu	keys: %lu	records: %lu	free list: %lu%s%lu	last_pgno: %lu	flags: %#lx (	uid: VERSION=3
>format=print
>format=bytevalue
>database=type=btree
>DB->get_flagsrecnum=1
>DB->get_bt_minkeybt_minkey=%lu
>type=hash
>DB->get_h_ffactorh_ffactor=%lu
>DB->get_h_nelemh_nelem=%lu
>type=queue
>DB->get_re_lenre_len=%lu
>DB->get_re_padre_pad=%#x
>DB->get_q_extentsizeextentsize=%lu
>type=recno
>renumber=1
>__db_prheaderchksum=1
>duplicates=1
>dupsort=1
>db_pagesize=%lu
>keys=1
>HEADER=END
>DB->dumpduplicatehash unsortedhash metadatabtree internalrecno internalbtree leafrecno leafoverflowqueue metadata LSN [%lu][%lu]: records: %lu	minkey: %lu	re_len: %#lx re_pad: %#lx	root: %lu	max_bucket: %lu	high_mask: %#lx	low_mask:  %#lx	ffactor: %lu	nelem: %lu	h_charkey: %#lx	spare points: %lu 	first_recno: %lu	cur_recno: %lu	re_len: %#lx re_pad: %lu	rec_page: %lu	page_ext: %lu       D[%03lu] %4lu %sprev: %4lu next: %4lu%sref cnt: %4lu %sentries: %4lu offset: %4lu%4lu [offpage dups]Duplicates:		ILLEGAL HASH PAGE TYPE: %luILLEGAL BINTERNAL TYPE: %luentries %4lu pgno %4luILLEGAL PAGE TYPE: %lubtree metadatapage %lu: %s:In-memory DB structure:%s: %#lxbt_meta: %lu bt_root: %lubt_minkey: %lubt_lpgno: %lumeta_pgno: %luh_ffactor: %luh_nelem: %luh_hash: %#lxq_meta: %luq_root: %lure_pad: %#lx re_len: %lubtree:recnumrecno:fixed-lengthrecno:renumbermultiple-databasessorted duplicateschecksummingdatabase createdencompassing file createddbm/ndbm errorvariable lengthdiscard cached pagesencryptedfixed-length recordsin-memoryfile is being renamedchanges not loggedopen calledpad valuedefault page sizeread-onlyread-uncommittedBtree record numbersopened for recoveryno reverse splitssecondaryload on opensubdatabasesneedswaptransactionalverifierh¦ïÿP¦ïÿp¦ïÿx¦ïÿ¦ïÿ¦ïÿ¦ïÿ¦ïÿ`¦ïÿÍ·ïÿ{»ïÿ»ïÿÈ¹ïÿo¸ïÿS¸ïÿÓÉïÿÅïÿÈÉïÿ½Éïÿ²Éïÿ§ÉïÿÉïÿÉïÿÉïÿéÉïÿÞÉïÿ{ÉïÿpÉïÿnÅïÿ¨Èïÿ¨ÈïÿpÒïÿÑïÿÑïÿ{Ðïÿ{Ðïÿ¨Èïÿ¨Èïÿ¨Èïÿ¨Èïÿ¨Èïÿ{ÐïÿpÒïÿ0123456789abcdefoverflow: total len: %4lu page: %4luUnable to retrieve free-list page: %lu: %sILLEGAL PAGE TYPE: page: %lu type: %luILLEGAL PAGE OFFSET: indx: %lu of %lucount: %4lu pgno: %4lu type: %lu ILLEGAL DUPLICATE/LBTREE/LRECNO TYPE: %lubt_compare: %#lx bt_prefix: %#lxre_pad: %#lx re_delim: %#lx re_len: %lu re_source: %sre_modified: %d re_eof: %d re_last: %lucreated by compensating transactionRemove on temporary files invalid__db_subdb_removeDB->removeDB_ENV->dbremoveRename on temporary files invalidDB->renameDB_ENV->dbrenameDBC%#lx	%sAssociated dbpAssociated txnInternalDefault locker IDLocker!SetType%s	%sOff-page duplicate cursorReferenced pageRootPage numberPage indexLock mode	Flags%.24s	Local timeDB handle information:Page size!Append recno%sSet	%sFeedbackDup compareApp privateDbEnvThread mutexFileDatabase	File IDCursor adjust IDMeta pgnoLocker IDHandle lockAssociate lockRPC remote IDSecondary callbackPrimary handleapi internalBtree/Recno internalHash internalQueue internalXA internalFile naming informationDB handle cursors:Active queue:Join queue:Free queue:DB->stat_printDB->statDB_AM_CHKSUMDB_AM_COMPENSATEDB_AM_CREATEDDB_AM_CREATED_MSTRDB_AM_DBM_ERRORDB_AM_DELIMITERDB_AM_DISCARDDB_AM_DUPDB_AM_DUPSORTDB_AM_ENCRYPTDB_AM_FIXEDLENDB_AM_INMEMDB_AM_IN_RENAMEDB_AM_NOT_DURABLEDB_AM_OPEN_CALLEDDB_AM_PADDB_AM_PGDEFDB_AM_RDONLYDB_AM_READ_UNCOMMITTEDDB_AM_RECNUMDB_AM_RECOVERDB_AM_RENUMBERDB_AM_REVSPLITOFFDB_AM_SECONDARYDB_AM_SNAPSHOTDB_AM_SUBDBDB_AM_SWAPDB_AM_TXNDB_AM_VERIFYINGDBC_ACTIVEDBC_DONTLOCKDBC_MULTIPLEDBC_MULTIPLE_KEYDBC_OPDDBC_OWN_LIDDBC_READ_COMMITTEDDBC_READ_UNCOMMITTEDDBC_RECOVERDBC_RMWDBC_TRANSIENTDBC_WRITECURSORDBC_WRITER%.24s	Replication handle timestampDB->truncateDB->truncate forbidden on secondary indicesDB->truncate not permitted with active cursors%s: unrecognized file typeDB->upgrade%s: file size not a multiple of the pagesize%s: unsupported btree version: %luAttempt to upgrade an encrypted database without providing a password.%s: unsupported hash version: %lu%s: unsupported queue version: %lu%s: DB->upgrade only supported on native byte-order systems@ðÿ@ðÿðÿQðÿuðÿ
ðÿLogging region out of memory; you may need to increase its size__dbreg_register_recoverWarning: Improper file close at %lu/%luo4ðÿà6ðÿ`6ðÿ6ðÿ6ðÿð4ðÿ6ðÿDB handle FNAME contents:log ID%ld	%screate txnLOG FNAME list:File name mutexFid maxNo DBPDB_FNAME_DURABLEDB_FNAME_NOTLOGGEDID	Name	Type	Pgno	Txnid	DBP-info%ld	%s	%s	%lu	%lx	%s %d %lx %lxrw-------Region allocations: %lu allocations, %lu failures, %lu frees, %lu longest%llu%s/%sDB_ENV->failchkis_alive method specified but no thread region allocatedthread table must be allocated when the database environment is createdunable to allocate a thread status blockDB_ENV->failchk requires DB_ENV->is_alive be configuredThread died in Berkeley DB library=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=è`ðÿÐ`ðÿÐ`ðÿè`ðÿÐ`ðÿè`ðÿè`ðÿè`ðÿÐ`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿÐ`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿÐ`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿè`ðÿÐ`ðÿ8aðÿ aðÿ aðÿ8aðÿ aðÿ8aðÿ8aðÿ8aðÿ aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ8aðÿ aðÿ@ @  @@  @ @@ @ @loggingmemory pool<unspecified>beforeafterDB_ENV->set_shm_keyDB_ENV->set_allocDB_ENV->set_thread_countDB_ENV->set_app_dispatchDB_ENV->get_homeDB_ENV->set_intermediate_dirDB_ENV->set_flagsEnvironment panic setDB_ENV->set_encrypt%s interface requires an environment configured for the %s subsystem%s: method not permitted %s handle's open method%s: method not permitted when environment specifiedBerkeley DB was not configured for RPC supportDB_ENV->set_intermediate_dir: mode may not be set to 0DB_ENV->set_flags: direct I/O either not configured or not supportedDB_ENV->set_flags: DB_CDB_ALLDBDB_ENV->set_flags: DB_PANIC_ENVIRONMENTDB_ENV->set_flags: DB_REGION_INITDB_ENV->set_flags: DB_LOG_INMEMORYEmpty password specified to set_encrypt/temporary open: %sBerkeley DB 4.6.19: (August 10, 2007)Database handles still open at environment closeFile handles still open at environment closeThe DB_RECOVER flag was not specified, and recovery is neededBerkeley DB library does not support DB_REGISTER on this systemregistration requires transaction supportBerkeley DB library does not support replication on this systemreplication requires locking supportreplication requires transaction supportrecovery requires the create flagrecovery requires transaction supportarchitecture lacks fast mutexes: applications cannot be threadedDB_ENV->get_open_flagsunnamedOpen database handle: %s%s%sOpen file handle: %sDB_ENV->closeDB_HOMErw-rw----DB_ENV->removeDB_ENV->openUnknown version %luLast log record not foundFirst log record not foundforwardRecovery complete at %.24sRecovery checkpointMaximum transaction ID%s %lx %s [%lu][%lu]backwardRecovery function for LSN %lu %lu failedLog file corrupt at LSN: [%lu][%lu]Invalid recovery timestamp %s; earliest time is %sInvalid checkpoint record at [%ld][%ld]Checkpoint LSN record [%ld][%ld] not foundRecovery starting from [%lu][%lu]Recovery function for LSN %lu %lu failed on %s passBü©ñÒMbP?no room remaining for additional REGIONsenvironment reference count went negative%s: unable to read system-memory information%s: existing environment not created in system memoryProgram version %d.%d doesn't match environment version %d.%dconfigured environment flags incompatible with existing environmentunable to create new master region array%s: unable to find environment%s: unable to write out public environment IDunable to join the environment__db.%03dprocess-private__db.001__db__dbq.__db.register__db.rep%lu: recovery completed, unlockingDB_REGISTER limits processes to one open DB_ENV handle per environment%lu: locking slot %02u at offset %lu%s: exclusive file unlockX                      0
>%lu: register environment%lu: creating %s%24lu
>%lu: adding self to registry%02u: EMPTY%02u: %s: FAILED%02u: %s: LOCKED%lu: recovery required%luM	%s (%lu)%s REGINFO information:LockEnvironmentLogMpoolMutexTransactionInvalidUnknownRegion typeRegion IDRegion nameOriginal region addressRegion addressRegion primary addressRegion maximum allocationRegion allocated	Region flags%luGB%s%luMB%s%luKB%s%luB%luM	%s (%d%%) (%d%% %s)file-handle.mutexfile-handle.reference countfile-handle.file descriptorfile-handle.file namefile-handle.page numberfile-handle.page sizefile-handle.page offset	file-handle.flagsDB_ENV->stat_printMagic numberPanic value%d.%d.%d	Environment versionBtree versionHash versionLock versionLog versionQueue versionSequence versionTxn version%.24s	Creation timeEnvironment IDReferences	Initialization flagsRegion slots	Replication flags%.24s	Operation timestamp%.24s	Replication timestamp%s Region:Segment IDSizeDB_ENV handle information:ErrfileErrpfxErrcallEventPanicMallocReallocFree	Verbose flagsApp dispatchHomeLog dirTmp dir%s	Data dir%#oMode	Open flagsLockfhpRecovery tableRPC clientRPC client IDDB reference countShared memory keyDB_ENV handle mutexDB handle mutexapi1 internalapi2 internalcrypto handleMT mutexThread blocks allocatedThread allocation thresholdThread hash bucketsThread status blocks:blockedunknown	process/thread %s: %sREGION_CREATEREGION_CREATE_OKREGION_JOIN_OKDB_FH_NOSYNCDB_FH_OPENEDDB_FH_UNLINKDB_REGENV_REPLOCKEDDB_VERB_DEADLOCKDB_VERB_FILEOPSDB_VERB_FILEOPS_ALLDB_VERB_RECOVERYDB_VERB_REGISTERDB_VERB_REPLICATIONDB_VERB_WAITSFORDB_CREATEDB_FORCEDB_INIT_CDBDB_INIT_LOCKDB_INIT_LOGDB_INIT_MPOOLDB_INIT_REPDB_INIT_TXNDB_LOCKDOWNDB_NOMMAPDB_PRIVATEDB_RDONLYDB_RECOVERDB_RECOVER_FATALDB_SYSTEM_MEMDB_THREADDB_TRUNCATEDB_TXN_NOSYNCDB_USE_ENVIRONDB_USE_ENVIRON_ROOTDB_ENV_AUTO_COMMITDB_ENV_CDBDB_ENV_CDB_ALLDBDB_ENV_DBLOCALDB_ENV_DIRECT_DBDB_ENV_DIRECT_LOGDB_ENV_DSYNC_DBDB_ENV_DSYNC_LOGDB_ENV_RECOVER_FATALDB_ENV_LOCKDOWNDB_ENV_LOG_AUTOREMOVEDB_ENV_LOG_INMEMORYDB_ENV_NOLOCKINGDB_ENV_NOMMAPDB_ENV_NOPANICDB_ENV_OPEN_CALLEDDB_ENV_OVERWRITEDB_ENV_PRIVATEDB_ENV_REGION_INITDB_ENV_RPCCLIENTDB_ENV_RPCCLIENT_GIVENDB_ENV_SYSTEM_MEMDB_ENV_THREADDB_ENV_TIME_NOTGRANTEDDB_ENV_TXN_NOSYNCDB_ENV_TXN_NOWAITDB_ENV_TXN_WRITE_NOSYNCDB_ENV_YIELDCPUÔðÿ(ÔðÿÒðÿ8ÔðÿHÔðÿXÔðÿÔðÿoïðÿdïðÿïðÿzïðÿYïðÿNïðÿîðÿDefault database environment information:Primary region allocation and reference count mutexPer region database environment information:Number of recovery table slotsrename: file %s exists__fop_file_setup:  Retry limit (%d) exceededTransactional create on replication client disallowedmac derivation key magic valueUnencrypted checksum with a supplied encryption keyEncrypted checksum: no encryption key specifiedIn-memory log buffer is full (an active transaction spans the buffer)Ignoring log file: %s: magic number %lx, not %lxUnacceptable log file %s: unsupported log version %luSkipping log file %s: historic log version %luWarning: truncating to point beyond end of logunable to allocate log region memoryFinding last valid log LSN: file: %lu offset %luignoring log file: %slog record size mismatchlog record checksum mismatchlog.Invalid log file: %s__log_archivelog file auto-removeDB_ENV->log_archiveno absolute path for the current directoryDB_ENV->log_archive: bad log recordDB_ENV->log_archive: unable to read log recordfile %s has LSN %lu/%lu, past end of log at %lu/%luCommonly caused by moving a database from one database environmentto another without clearing the database LSNs, or by removing all ofthe log files from a database environmentLogging not currently permittedDIAGNOSTICDB_ENV->log_printfDB_LOGC->getDB_LOGC->get: %s__logc_get_intDB_LOGC->closeDB_ENV->log_cursorDB_LOGC->get: unset cursorDB_LOGC->versionDB_LOGC->get: LSN %lu/%lu: invalid log record headerDB_LOGC->get: LSN: %lu/%lu: readDB_LOGC->get: LSN: %lu/%lu: short readDB_LOGC->get: log record LSN %lu/%lu: checksum mismatchDB_LOGC->get: catastrophic recovery may be requiredEncountered zero length records while traversing backwardsDB_LOGC->get: invalid LSN: %lu/%lulog_rep_split: Processing LSN [%lu][%lu]log_rep_split: p %#lx ep %#lx logrec data %#lx, size %lu (%#lx)log_split: rep_apply ret %d, tmp_lsn [%lu][%lu]P©ñÿE®ñÿÚ¨ñÿÚ¨ñÿÚ¨ñÿÚ¨ñÿÚ¨ñÿÚ¨ñÿÚ¨ñÿ¦®ñÿ8©ñÿÚ¨ñÿÚ¨ñÿÚ¨ñÿÚ¨ñÿÚ¨ñÿÚ¨ñÿ®ñÿÚ¨ñÿÚ¨ñÿÐ®ñÿÍ°ñÿº°ñÿÍ°ñÿÍ°ñÿÝ°ñÿin-memory log buffer must be larger than the log file sizeDB_ENV->set_lg_regionmaxlog region size must be >= %dDB_ENV->set_lg_bsizeDB_ENV->get_lg_regionmaxDB_ENV->get_lg_bsizeDB_ENV->set_lg_maxDB_ENV->get_lg_maxDB_ENV->set_lg_filemodeDB_ENV->get_lg_filemodeDB_ENV->log_newfh: %lulog.%010d%s: log file unreadable%s: log file open failedlog.%05dDB_ENV->log_filefrom another environment%s %s %sDB_ENV->log_flushDB_ENV->log_putShort read while restoring logDB_ENV->log_file is illegal with in-memory logs.DB_ENV->log_file: name buffer is too shortDB_ENV->log_flush: LSN of %lu/%lu past current end-of-log of %lu/%luhave been removed or incompatible database files importedDatabase environment corrupt; the wrong log files mayto modify a replicated environmentNon-replication DB_ENV handle attemptingDB_ENV->log_put: record larger than maximum file size (%lu > %lu)DB_ENV->log_put is illegal on replication clientsDefault logging region information:Log bytes written since last checkpointTotal log file I/O writes due to overflowMaximum commits in a log flushMinimum commits in a log flushThe number of region locks that required waitingtransactions waiting to commitLog magic numberLog version numberLog record cache size%#o	Log file mode%luMb	Current log file size%luKb	Current log file size%lu	Current log file sizeRecords entered into the logLog bytes writtenTotal log file I/O writesTotal log file flushesTotal log file I/O readsCurrent log file numberCurrent log file offsetOn-disk log file numberOn-disk log file offsetLog region sizeDB_LOG handle information:DB_LOG handle mutexLog file nameLog file handleLOG region mutexFile name list mutexpersist.magicpersist.versionpersist.log_size%#lolog file permissions modecurrent file offset LSN%lu/%lu	%sfirst buffer byte LSNcurrent buffer offsetcurrent file write offsetlength of last recordlog flush in progressLog flush mutexlast sync LSNcached checkpoint LSNlog buffer sizenext log file sizeLSN of first commitDB_ENV->log_stat_printDB_ENV->log_statDBLOG_RECOVERDBLOG_FORCE_OPENÈB%s: dirty flag set for readonly file page%s: page %lu: reference count overflowFile %s: freeing pinned buffer for page %luDB_MPOOLFILE->getmemp_fgetDB_MPOOLFILE->set_lsn_offsetDB_MPOOLFILE->set_ftypeDB_MPOOLFILE->set_clear_lenDB_MPOOLFILE->set_pgcookieDB_MPOOLFILE->set_fileidDB_MPOOLFILE->set_flagsget_fileid: file ID not setDB_ENV->memp_fcreateDB_MPOOLFILE->set_priority: unknown priority value: %dDB_MPOOLFILE->get_priority: unknown priority value: %dE/òÿ /òÿ°/òÿÀ/òÿÐ/òÿ/òÿX0òÿp0òÿ0òÿ 0òÿ0òÿ0òÿ0òÿ0òÿ0òÿ0òÿ0òÿ0òÿ@0òÿ%s: close: %lu blocks left pinned%s: clear length, page size or LSN location changedCannot open DURABLE and NOT DURABLE handles in the same fileDB_MPOOLFILE->open: page sizes must be a power-of-2DB_MPOOLFILE->open: clear length larger than page sizeDB_MPOOLFILE->open: temporary files can't be readonlyDB_MPOOLFILE->open: DB_MULTIVERSION requires transactionsDB_MPOOLFILE->closeDB_MPOOLFILE->open%s: page %lu: unpinned page returned-SòÿÝUòÿæUòÿ>SòÿÔUòÿ»UòÿDB_MPOOLFILE->putTruncate beyond the end of fileindividual cache size too large: maximum is 4GBDB_ENV->get_mp_max_mmapsizeDB_ENV->get_mp_max_writeDB_ENV->set_mp_max_openfdDB_ENV->get_mp_max_openfdDB_ENV->memp_get_configDB_ENV->memp_set_configDB_ENV->get_cachesize__db.freezer.%u.%u.%uK__memp_bh_thaw__memp_bh_freeze%s: non-transactional update to a multiversion fileUnable to allocate memory for mpool regionDB_ENV->memp_registerDB_ENV->set_cache_maxDB_ENV->get_mp_max_ncachecannot remove the last cachecannot resize to %lu cache regions: maximum is %luFile #%d: %sReference countBlock countLast page numberOriginal last page numberMaximum page numberPriorityPage's LSN offsetPage's clear length	ID%5lu, %lu, %5lu, #%d,  (sync-lock)%2lu%s, %lu/%lu (@%lu/%lu), %#08lx, %luMPOOL structure:MPOOL region mutexMaximum checkpoint LSNHash table entriesHash table last-checkedHash table LRU countPut counterDB_MPOOL handle information:DB_MPOOL handle mutexUnderlying cache regionsDB_MPOOLFILE structures:readonlyPinned block reference countClear lengthFile typeMax gbytesMax bytesCache prioritymmap addressmmap lengthFile handleCache #%d:(MVCC %lu/%lu/%lu)  next:	Total cache sizeNumber of cachesMaximum number of cachesPool individual cache sizeMaximum open file descriptorsPages created in the cachePages read into the cacheCurrent total page countCurrent clean page countCurrent dirty page countThe number of buffers frozenThe number of buffers thawedThreads waited on page I/OPool File: %sDB_ENV->memp_stat_printDB_ENV->memp_statDB_MPOOL_NOFILEDB_MPOOL_UNLINKcallpgindirtydiscardfreedtrashMP_CAN_MMAPMP_DIRECTMP_EXTENTdeadfilefile writtenno backing fileunlink on closenot durableMP_TEMPFile #%lu: %s: per-process, %sBH hash table (%lu hash slots)bucket #: priority, I/O wait, [mutex]	pageno, file, ref, LSN, address, priority, flagsbucket %lu: %lu, %lu (%lu dirty)Default cache region information:Maximum memory-mapped file sizeMaximum sequential buffer writesSleep after writing maximum sequential buffersRequested pages mapped into the process' address spaceRequested pages found in the cacheRequested pages not found in the cachePages written from the cache to the backing fileClean pages forced from the cacheDirty pages forced from the cacheDirty pages written by trickle-sync threadNumber of hash buckets used for page locationTotal number of times hash chains searched for a pageThe longest hash chain searched for a pageTotal number of hash chain entries checked for pageThe number of hash bucket locks that required waitingThe maximum number of times any hash bucket lock was waited forThe number of frozen buffers freedThe number of page allocationsThe number of hash buckets examined during allocationsThe maximum number of hash buckets examined for an allocationThe number of pages examined during allocationsThe max number of pages examined for an allocation%s: unable to flush%s: unable to flush page: %luDB_MPOOLFILE->syncmemp_syncmemp_sync: correcting dirty count %lu %lumemp_trickleDB_ENV->memp_trickle: %d: percent must be between 1 and 100malloc: %lurealloc: %luuser-specified malloc function returned NULLUser-specified realloc function returned NULLfileops: directory list %sstat: %sreleaseacquirefcntlfileops: flock %s %s offset %lufileops: flush %sfsync%s: buffer too small to hold environment variable %sfileops: close %sfcntl(F_SETFD)fileops: munmapmlockfileops: mmap %sshmdtshmctl: id %d: unable to delete system shared memory regionno base system shared memory ID specifiedshmget: key: %ld: shared system memory region already existsshmget: key: %ld: unable to create shared system memory regionshmat: id %d: unable to attach to shared system memory regionfileops: open %s__os_openfileops: rename %s to %srename %s %sfileops: write %s: %lu byteswrite: %#lx, %lufileops: read %s: %lu bytesread: %#lx, %lufileops: read %s: %lu bytes at offset %lufileops: write %s: %lu bytes at offset %lufileops: seek %s to %luseek: %lu: (%lu * %lu) + %luselectfstatTMPDIRTMPTempFolder/var/tmp/usr/tmpfileops: truncate %s to %luftruncate: %lufileops: unlink %sunlink: %sChild transaction is activenot a restored transactiontransaction already preparedtransaction already %sDB_TXN->set_timeouttxn_beginDB_TXN->commitoperation not permitted during recoverytransaction has active cursorsPrepare disallowed on child transactionsUnable to allocate memory for transaction nameUnable to allocate memory for transaction detailChild transaction snapshot setting must match parentDB_TXN->abort: in-memory log undo failedDB_TXN->abort: log undo failed for LSN: %lu %luDB_TXN->prepare: log_write failedtxn_checkpoint: failed to flush the buffer cachetxn_checkpoint: log failed at LSN [%ld %ld]txn_checkpointTransaction has in memory logsAborting txn %#lx: %sTransaction abort failedDB_ENV->set_tx_timestampDB_ENV->set_tx_maxDB_ENV->get_tx_maxtxnid %lx commit record found, already on commit listTransaction not in list %xtransaction not in list %lxInvalid checkpoint record at [%lu][%lu]operation not permitted while in recoveryNo log recordsDB_ENV->txn_recovertxn_id_setunable to discard txn %#lxCurrent ID value %lu below minimumMaximum ID value %lu below minimumunable to abort transaction %#lxError: closing the transaction region with active transactionsUnable to allocate memory for the transaction regionDB_ENV->txn_statNo checkpoint LSN0	No checkpoint timestamp%.24s	Checkpoint timestampActive transactionsMaximum active transactionsNumber of transactions begunSnapshot transactionsMaximum snapshot transactionsTransaction region sizeActive transactions:XA deadlockedXA abortedrunningXA endedXA preparedXA startedXA suspendedunknown state; parent: %lx; read LSN: %lu/%lu; mvcc refcount: %lu; "%s"
>	GID/XID:%#lx DB_TXNMGR handle information:DB_TXNMGR mutexDB_TXNREGION region mutexMaximum number of active txnsLast transaction ID allocatedCurrent maximum unused IDcheckpoint mutexLast checkpoint LSNXA information:XA RMIDDB_ENV->txn_stat_printTXN_IN_RECOVERYDefault transaction region information:File/offset for last checkpoint LSN%#lx	Last transaction ID allocatedMaximum number of active transactions configuredNumber of transactions abortedNumber of transactions committedNumber of transactions restored	%lx: %s; pid/thread %s; begin LSN: file/offset %lu/%luNumber of transactions discardedDB_TXNREGION handle information:%.24s	Last checkpoint timestampàÒóÿÕÒóÿÊÒóÿ¿Òóÿ´Òóÿ©ÒóÿÒóÿtransaction handles should not be directly specified to XA interfacesno XA transaction declaredfcntl lock failedDB->set_bt_compareDB->set_re_padDB->set_re_lenDB->set_re_delimDB->set_bt_prefixDB->set_re_sourceDB->set_bt_minkeyminimum bt_minkey value is 2prefix comparison may not be specified for default comparison routinebt_minkey value of %lu too high for page size of %lu%s: btree version %lu requires a version upgrade%s: DB_DUP specified to open method but not set in database%s: DB_RECNUM specified to open method but not set in database%s: DB_FIXEDLEN specified to open method but not set in database%s: DB_RENUMBER specified to open method but not set in database%s: multiple databases specified but not supported by file%s: duplicate sort specified but not supported in databaseopen method type is Btree, database type is Recnoopen method type is Recno, database type is BtreeDB->openVôÿLôÿ1ôÿ1ôÿÞôÿÞôÿÞôÿÞôÿÞôÿ1ôÿillegal record number of 0__ramc_getrbwbÈpôÿHoôÿèpôÿqôÿèpôÿÞlôÿÞlôÿÞlôÿÞlôÿ^môÿoôÿoôÿoôÿÞlôÿÞlôÿÞlôÿÞlôÿPmôÿ@môÿPmôÿxpôÿxpôÿ%s: write failed to backing fileÀ{ôÿ8|ôÿ°|ôÿ }ôÿ2{ôÿ2{ôÿ2{ôÿ2{ôÿ2{ôÿP{ôÿôÿèôÿ ôÿÐôÿ
>ôÿ
>ôÿ
>ôÿ
>ôÿ
>ôÿ ôÿØ¢ôÿ¨¢ôÿx¡ôÿ ¡ôÿE¡ôÿE¡ôÿE¡ôÿE¡ôÿE¡ôÿ ¡ôÿ¨ôÿP¨ôÿ(§ôÿf§ôÿó¦ôÿó¦ôÿó¦ôÿó¦ôÿó¦ôÿf§ôÿÀ®ôÿ`®ôÿp¬ôÿ`®ôÿ6¬ôÿ6¬ôÿ6¬ôÿ6¬ôÿ6¬ôÿp¬ôÿToo many btree levels: %dðÎôÿðÎôÿHÏôÿ0ÐôÿhÐôÿWÎôÿWÎôÿWÎôÿWÎôÿÎôÿÐÓôÿÓôÿ°Ôôÿ¨ÒôÿvÒôÿvÒôÿvÒôÿvÒôÿvÒôÿ¨ÒôÿOverflow sizeRecnoOrder	Internal Flags%lx	Btree magic number%lu	Btree version numberBig-endianLittle-endianUnrecognized byte order%s	Byte orderMinimum keys per-pageFixed-length record size%#x	Fixed-length record padUnderlying database page sizeOverflow key/data sizeNumber of levels in the treeNumber of records in the treeNumber of tree internal pagesNumber of tree leaf pagesNumber of tree overflow pagesNumber of empty pagesC_DELETEDC_RECNUMC_RENUMBERrecord-numbersDefault Btree/Recno database information:Number of unique keys in the treeNumber of data items in the treeNumber of bytes free in tree internal pagesNumber of bytes free in tree leaf pagesNumber of tree duplicate pagesNumber of bytes free in tree duplicate pagesNumber of bytes free in tree overflow pagesNumber of pages on the free listÈÂDB->set_h_compareDB->set_h_nelemDB->set_h_hashDB->set_h_ffactor%$sniglet^&%s: hash version %lu requires a version upgrade%s: multiple databases specified but not supported in file%s: duplicate sort function specified but not set in database%s: Invalid hash meta page %lu`õÿxõÿxõÿðõÿðõÿÀõÿõÿInvalid flag in __ham_curadj_recoverBucket traversingBucket lockedDuplicate set offsetCurrent duplicate lengthTotal duplicate set lengthBytes needed for addPage on which we can insert__ham_traverse%lx	Hash magic number%lu	Hash version numberSpecified fill factorNumber of hash bucketsNumber of overflow pagesNumber of duplicate pagesH_CONTINUEH_DELETEDH_DUPONLYH_EXPANDH_ISDUPH_NEXT_NODUPH_NOMOREH_OKDefault Hash database information:Number of keys in the databaseNumber of data items in the databaseNumber of bytes free on bucket pagesNumber of bytes free in overflow pagesNumber of bucket overflow pagesNumber of bytes free in bucket overflow pagesNumber of bytes free in duplicate pagesÝÊõÿÄÉõÿÊõÿ@Ëõÿ@Ëõÿ@Ëõÿ@ËõÿðÊõÿÄÉõÿÄÉõÿÄÉõÿÄÉõÿ@ËõÿÊõÿ__qamc_getDBC->puthåõÿ¡êõÿPåõÿ äõÿPåõÿ äõÿ äõÿ äõÿ äõÿáêõÿêõÿìõÿêõÿ äõÿ äõÿ äõÿ äõÿÐêõÿìõÿÐêõÿPåõÿPåõÿ%s: data offset plus length larger than record size of %lu%s%c__dbq.%s.%dQueue does not support multiple databases per fileExtent size must be at least 1DB->set_extentsizeRecord size of %lu too large for page size of %lu%s: queue version %lu requires a version upgrade%s: unsupported qam version: %luExtent size may not be specified for in-memory queue databaseMultiversion queue databases are not supported%lx	Queue magic number%lu	Queue version numberNumber of database pages%lu	First undeleted recordDefault Queue database information:Underlying database extent sizeNumber of records in the databaseNumber of bytes free in database pages%lu	Next available record number__db.rep.initNEXTINFO: Fileinfo read: %sMsg file %d != curfile %dWalk_dir: Dir %s has %d filesWalk_dir: File %d name: %sDB_CONFIGUpdate setup for %d files.qam_remove returned %dPAGE: Client_dbinit %spage_req: found %d in dbregpage_req: Open %d failedCleaning up interrupted internal initclean up interrupted internal initNEXTFILE: have %d files.  RECOVER_LOG nowNEXTFILE: LOG_REQ from LSN [%lu][%lu] to [%lu][%lu]Next file %d: pgsize %lu, maxpg %luPAGE_GAP: pgno %lu < ready %lu, waiting %luPAGE_GAP: pgno %lu, max_pg %lu ready %lu, waiting %lu max_wait %luPAGE_GAP: Set cursor for ready %lu, waiting %luPAGE_GAP: Next cursor No next - ready %lu, waiting %luPAGE_GAP: Next cursor ready %lu, waiting %luFILEDONE: have %lu pages. Need %lu.Queue fileinfo: first %lu, last %lu, empty %dQueue fileinfo: First req: first %lu, last %luQueue fileinfo: Wrap req: first %lu, last %lupage_fail: BEFORE page %lu failed. ready %lu, max %lu, npages %dpage_fail: AFTER page %lu failed. ready %lu, max %lu, npages %dWalk_dir: Getting info for in-memory named filesWalk_dir: Getting info for dir: %sWalk_dir: File %d %s: returned error %sWalk_dir: File %d (of %d) %s at 0x%lx: pgsize %lu, max_pgno %luRep_check_uid: Could not mallocCheck_uid: Found matching file.Update setup:  First LSN [%lu][%lu].Update setup:  Last LSN [%lu][%lu]QAM: Unlink %s via __qam_removeUpdate_setup: Error: Clear PAGE, set UPDATE again. %sPAGE: Received page %lu from file %dPAGE: Received duplicate page %lu from file %dPAGE: Write page %lu into mpoolrep_write_page: Calling fop_create for %srep_bulk_page: Processing LSN [%lu][%lu]rep_bulk_page: p %#lx ep %#lx pgrec data %#lx, size %lu (%#lx)rep_bulk_page: rep_page ret %dsendpages: file %d page %lu to %lusendpages: PAGE_FAIL on page %lusendpages: %lu, page lsn [%lu][%lu]sendpages: %lu, lsn [%lu][%lu]page_req: file %d page %lu to %lupage_req: Open %d via mpf_openTally found[%d] (%d, %lu), this vote (%d, %lu)Got enough votes to win; election done; winner is %d, gen %luNot in election gen %lu, at %lu, got voteReceived vote1 egen %lu, egen %luReceived old vote %lu, egen %lu, ignoring vote1Received VOTE1 from egen %lu, my egen %lu; resetIncoming vote: (eid)%d (pri)%d %s (gen)%lu (egen)%lu [%lu,%lu]Existing vote: (eid)%d (pri)%d (gen)%lu (sites)%d [%lu,%lu]Not in election, but received vote1 0x%xAfter phase 1 done: counted vote %d of %dDB_ENV->rep_elect: nsites must be zero if leases configuredDB_ENV->rep_elect: nsites may not be negativeDB_ENV->rep_elect: nvotes may not be negativeDB_ENV->rep_elect:WARNING: nvotes (%d) is sub-majority with nsites (%d)DB_ENV->rep_elect: nvotes (%d) is larger than nsites (%d)Start election nsites %d, ack %d, priority %dSetting priority 0, unelectable, due to internal init/recoveryEgen changed while waiting. Now %lu.  New timeout %lu, orig timeout %luNo electable site found: recvd %d of %d votes from %d sitesNot enough votes to elect: recvd %d of %d from %d sitesSkipping phase2 wait: already got %d votesWhile waiting egen changed to %lu.  Phase 2 New timeout %lu, orig timeout %luEgen ph2 changed from %lu to %luAfter phase 2: votes %d, nvotes %d, nsites %dEnded election with %d, sites %d, egen %lu, flags 0x%lxTallying VOTE%c[%d] (%d, %lu)Accepting new vote (master)We received a vote%sBad vote egen %lu.  Mine %luCounted vote %d of %dMaster received voteGrow sites returned error %dIn phase 2, ignoring vote1Tally returned %d, sites %dELECTABLEPhase1 election done(self)Voting for %d%sDB_ENV->rep_electBeginning an electionEnded election phase 1Egen changed from %lu to %luCounted my vote %dSending voteEnded election phase 2 %dwait_time: grant_expire %lu %lu lease_to %luwait_time: mytime %lu %lu, grant_expire %lu %lulease_grant: gi msg_time %lu %lulease_grant: eid %d, start %lu %lu, end %lu %lu, duration %lu %lulease_check: min_leases %d curtime %lu %lulease_check: valid %d eid %d, lease_lsn [%lu][%lu]lease_check: endtime %lu %luvalid %d, min %dDB_ENV->rep_set_requestDB_ENV->rep_get_requestDB_ENV->rep_set_limitDB_ENV->rep_get_limitDB_ENV->rep_syncDB_ENV->rep_set_leasepriority may not be negativeDB_ENV->rep_set_nsites__db.rep.db__db.reppg.dbDB_ENV->rep_get_configDB_ENV->rep_flushDB_ENV->rep_set_configDB_ENV->rep_startThread already in lockoutNew master gen %lu, egen %luFirst record not foundFinal log record not foundDB_ENV->rep_set_lease: must be called before DB_ENV->rep_startDB_ENV->rep_set_transport: no send function specifiedDB_ENV->rep_set_transport: eid must be greater than or equal to 0unknown timeout type argument to DB_ENV->rep_get_timeoutUnknown timeout type argument to DB_ENV->rep_set_timeoutDB_ENV->rep_set_nsites: nsites must be a positive numberDB_ENV->rep_set_nsites: must be called before DB_ENV->rep_startDB_ENV->rep_start: must specify DB_REP_CLIENT or DB_REP_MASTERDB_ENV->rep_set_transport must be called before DB_ENV->rep_startRep_start: Cannot become master without being elected when using leases.Rep_start: Cannot become master with outstanding lease granted.rep_start: Old log version was %lurestore_prep: No prepares. Skip.restore_prep: Prepare resolved. SkipCheckpoint record at LSN [%lu][%lu] not foundCheckpoint LSN record [%lu][%lu] not foundAttempt to get first log record failedrep_start: Found old version log %dcollect failed at: [%lu][%lu]Error syncing ckp [%lu][%lu]rep_apply: Set apply_th %dStart-up is done [%lu][%lu]DB_ENV->rep_process_messageUpdating gen from %lu to %lufailed to read the log at [%lu][%lu]transaction failed at [%lu][%lu]Rep_newfile: Old-style NEWFILE msg.  Use control msg log version: %luRep_newfile: File %lu vers %luError processing txn [%lu][%lu]process_rec: prepare at [%lu][%lu]rep_apply: In election. Ignoring [%lu][%lu]rep_apply: Decrement apply_th %dStarting delayed __memp_sync call [%lu][%lu]Returning ISPERM [%lu][%lu], cmp = %dReturning LOGREADY up to [%lu][%lu], cmp = %dReturning NOTPERM [%lu][%lu], cmp = %dReturning %d [%lu][%lu], cmp = %dDB_ENV->rep_process_message: control argument must be specifiedEnvironment not configured as replication master or clientDB_ENV->rep_process_message: error retrieving DBT contentsRacing replication msg lockout, ignore message.Received record %lu with old rep version %luConverted to record %lu with old rep version %luunexpected replication message version %lu, expected %dReceived record %lu with old log version %luunexpected log record version %lu, expected %dReceived ALIVE egen of %lu, mine %luClient record received on masterMaster record received on clientDelayed START_SYNC memp_sync due to missing records.ready LSN [%lu][%lu], ckp_lsn [%lu][%lu]DB_ENV->rep_process_message: unknown replication message: type %luALIVE: Completed sync [%lu][%lu]cg÷ÿ#p÷ÿxo÷ÿøs÷ÿps÷ÿ#s÷ÿs÷ÿcg÷ÿq÷ÿcg÷ÿ6q÷ÿ@t÷ÿ@t÷ÿp÷ÿ@u÷ÿr÷ÿn÷ÿFn÷ÿm÷ÿ8m÷ÿÃl÷ÿ8m÷ÿøk÷ÿk÷ÿ k÷ÿ¨j÷ÿ8j÷ÿ¤i÷ÿ
i÷ÿch÷ÿ?h÷ÿh÷ÿ__db.rep.gen__db.rep.egenRead in gen %luRead in egen %luDefault replication region information:Environment configured as a replication masterEnvironment configured as a replication clientEnvironment not configured for replicationLSN of first log record we have after missed log recordsNot waiting for any missed log recordsPage number of first page we have after missed pages.Not waiting for any missed pages.Number of duplicate master conditions detected.Current election generation numberNumber of duplicate log records receivedNumber of log records currently queuedMaximum number of log records ever queued at onceTotal number of log records queuedNumber of log records received and appended to the logNumber of log records missed and requestedNumber of times the master has changedNumber of messages received with a bad generation numberNumber of messages received and processedNumber of messages ignored due to pending recoveryNumber of failed message sendsNumber of new site messages receivedNumber of environments believed to be in the replication groupNumber of outdated conditions detectedNumber of duplicate page records receivedNumber of page records received and added to databasesNumber of page records missed and requestedNumber of transactions appliedNumber of startsync messages delayed%lu.%.6lu	Duration of last election (seconds)%lu/%lu	Maximum LSN of election winnerNumber of sites expected to participate in electionsNumber of votes needed to win an electionVotes received this election roundNumber of bulk buffer sends triggered by full bufferNumber of single records exceeding bulk buffer sizeNumber of records added to a bulk bufferNumber of re-request messages receivedNumber of request messages this client failed to processNumber of request messages received by this clientLimit on data sent in a single callRecords to wait before requestingRecords received while waitingNext LSN expectedNext LSN to be usedNext page number expected.Current environment IDNo current environment IDCurrent environment priorityCurrent generation numberCurrent master IDNo current master IDNumber of messages sentTransmission limitedStartup incompleteStartup completeNumber of elections heldNumber of elections wonNo election in progressCurrent election phaseElection winnerElection generation numberElection priorityElection tiebreaker valueNumber of bulk buffers sentDB_REP handle information:Bookkeeping databaseReplication region mutexBookkeeping database mutexMaster environment IDElection generationLast generation number in logSpace allocated for sitesSites in groupVotes needed for electionPriority in electionRequest gapMaximum gapCallers in rep_proc_msgLibrary handle countMulti-step operation count%.24s	Recovery timestampSites heard fromCurrent winnerWinner priorityWinner generationWinner LSNWinner tiebreakerVotes for this siteLOG replication information:First log record after a gapLSN waiting to verifyMaximum LSN requestedDB_ENV->rep_stat_printDB_ENV->rep_statDBREP_OPENFILESREP_F_CLIENTREP_F_EPHASE1REP_F_EPHASE2REP_F_INREPELECTREP_F_MASTERREP_F_MASTERELECTREP_F_NOARCHIVEREP_F_READY_APIREP_F_READY_MSGREP_F_READY_OPREP_F_RECOVER_LOGREP_F_RECOVER_PAGEREP_F_RECOVER_UPDATEREP_F_RECOVER_VERIFYREP_F_TALLYREP_UNDEFalive_reqaliveall_reqbulk_logbulk_pagedupmasterfile_failfile_reqlease_grantlog_morelog_reqmaster_reqnewclientnewfilenewmasternewsitepage_failpage_morepage_reqrerequeststart_syncupdateupdate_reqverify_failverify_reqvote2NOTYPE any nogroup lease nobuf perm rereq resend logendmsg_thapply_thop_cnthandle_cntElection done; egen %lurep_send_messageEgen: %lu. RepVersion %luresend_req ret is %lu%s %s: msgv = %lu logv %lu gen = %lu eid %d, type %s, LSN [%lu][%lu] %sOperation locked out.  Waiting for replication lockout to complete__op_rep_enter waiting %d minutes for lockout to completeopen DB and DBcursor handles must be closedreplication recovery unrolled committed transactions;DB_ENV handle waiting %d minutes for replication lockout to completeElection finished in %lu.%09lu secrep_send_msg: rtype %lu to version %lu record %lu.rep_send_message: Unknown rep version %lu, my version %lurep_send_function returned: %dUpdating gen from %lu to %lu from master %dClient too far ahead of master; unable to join replication groupNo commit or ckp found.  Truncate log.send_bulk: Send %d (0x%x) bulk buffer bytesbulk_msg: Record %d (0x%x) larger than entire buffer 0x%xbulk_msg: Record %lu (%#lx) doesn't fit.  Send %lu (%#lx) now.bulk_msg: Record %lu (0x%lx) hit throttle limit.bulk_msg: Copying LSN [%lu][%lu] of %lu bytes to %#lxbulk_msg: Send buffer after copy due to PERM¢÷ÿ§÷ÿø¦÷ÿè¦÷ÿØ¦÷ÿÈ¦÷ÿ¸¦÷ÿ¨¦÷ÿ¦÷ÿ¦÷ÿx¦÷ÿh¦÷ÿX¦÷ÿH¦÷ÿ8¦÷ÿ(¦÷ÿ¦÷ÿ¦÷ÿø¥÷ÿè¥÷ÿØ¥÷ÿÈ¥÷ÿ¸¥÷ÿ¨¥÷ÿ¥÷ÿ¥÷ÿx¥÷ÿh¥÷ÿX¥÷ÿH¥÷ÿ8¥÷ÿ(¥÷ÿ	
	
	
	
>
	
>
	
>
Skip sync-up rec.  Truncate log to [%lu][%lu], ckp [%lu][%lu]Client was never part of master's environmentlibrary build did not include support for the Replication ManagerPage %lu: entries listing %lu overlaps dataPage %lu: bad offset %lu at page index %luPage %lu: unaligned offset %lu at page index %luPage %lu: item %lu of unrecognizable typePage %lu: item %lu extends past page boundaryPage %lu: sorted duplicate set in unsorted-dup databasePage %lu: unsorted duplicate set in sorted-dup databasePage %lu: %s is of inappropriate type %luPage %lu: duplicate page of inappropriate type %luPage %lu: invalid prev_pgno %luPage %lu: invalid next_pgno %luPage %lu: too many entries: %luPage %lu: btree leaf page has incorrect level %luPage %lu: nonzero level %lu in non-btree databasePage %lu: invalid magic numberPage %lu: magic number does not match database typePage %lu: unsupported database version %lu; extraneous errors may resultPage %lu: invalid pagesize %luPage %lu: bad meta-data flags value %#lxPage %lu: nonempty free list on subdatabase metadata pagePage %lu: nonsensical free list pgno %luPage %lu: last_pgno is not correct: %lu != %luMetadata page %lu cannot be readPage %lu: Incomplete metadata pagePage %lu: metadata page corruptedPage %lu: could not check metadata pagePage %lu: pgno incorrectly set to %luPage %lu: bad magic number %luPage %lu: unsupported DB version %lu; extraneous errors may resultDB_SALVAGE requires a an output handleDB_ORDERCHKONLY requires a database nameSubdatabase entry of invalid sizePage %lu: DB->h_internal field is NULLPage %lu: incorrect hash function for databasePage %lu: database metapage of bad type %luPage %lu: old-style duplicate pagePage %lu: unknown page type %luSubdatabase entry not page-number sizeSubdatabase entry references invalid page %luSubdatabase entry references page %lu of invalid type %luPage %lu: invalid next_pgno %lu on free list pagePage %lu: page %lu encountered a second time on free listPage %lu: non-invalid page %lu on free listPage %lu: overflow refcount %lu, referenced %lu timesduplicate pagePage %lu: totally zeroed pagePage %lu: bad btree level %luPage %lu: bad page number %luPage %lu: bad page type %lu__db_vrfy_metaPage %lu: bad page size %luDB->verify__db_vrfy_structurePage %lu: unreferenced pageUNKNOWNqæ÷ÿqæ÷ÿhç÷ÿÐç÷ÿÈç÷ÿàç÷ÿàç÷ÿqæ÷ÿqæ÷ÿqæ÷ÿqæ÷ÿqæ÷ÿàç÷ÿhç÷ÿì÷ÿì÷ÿpî÷ÿì÷ÿì÷ÿ(î÷ÿî÷ÿøí÷ÿÈí÷ÿí÷ÿí÷ÿÐì÷ÿ°ì÷ÿpî÷ÿøÿøÿøÿøÿøÿÐøÿPøÿÐøÿøÿnøÿ=øÿøÿøÿøÿÛøÿªøÿyøÿHøÿøÿæøÿøÿ=øÿ__OTHER____bam_salvage_walkdupintUNKNOWN_KEYUNKNOWN_DATA__bam_salvage__bam_vrfy_itemorderbtree or recno page__bam_vrfy_subtree__bam_vrfy_treeorderPage %lu: linked twice__bam_vrfy_inpPage %lu: duplicated item %lu__bam_vrfy__ram_vrfy_inp__ram_vrfy_leafPage %lu: nonsensical bt_minkey value %lu on metadata pagePage %lu: nonsensical root page %lu on metadata pagePage %lu: Btree metadata page has both duplicates and multiple databasesPage %lu: Btree metadata page illegally has both recnums and dupsPage %lu: metadata page has renumber flag set but is not recnoPage %lu: recno metadata page specifies duplicatesPage %lu: re_len of %lu in non-fixed-length databasePage %lu: error %lu in fetching overflow item %luPage %lu: out-of-order key at entry %luPage %lu: non-dup dup key at entry %luPage %lu: database with no duplicates has duplicated keysPage %lu: unexpected page type %lu found in leaf chain (expected %lu)Page %lu: incorrect next_pgno %lu found in leaf chain (should be %lu)Page %lu: incorrect prev_pgno %lu found in leaf chain (should be %lu)Page %lu: recno leaf page non-recno treePage %lu: non-recno leaf page in recno treePage %lu: duplicates in non-dup btreePage %lu: btree or recno page is of inappropriate type %luPage %lu: recno page returned bad re_len %luPage %lu: record count incorrect: actual %lu, in record %luPage %lu: recno level incorrect: got %lu, expected %luPage %lu: overflow page %lu referenced more than twice from internal pagePage %lu: item %lu has incorrect record count of %lu, should be %luPage %lu: Btree level incorrect: got %lu, expected %luPage %lu: internal page is empty and should not bePage %lu: first item on page sorted greater than parent entryPage %lu: first item on page had comparison errorPage %lu: last item on page sorted greater than parent entryPage %lu: last item on page had comparison errorPage %lu: bad record count: has %lu records, claims %luPage %lu: unterminated leaf chainPage %lu: btree metadata page observed twicePage %lu: btree metadata page has no rootPage %lu: recno database has bad re_len %luPage %lu: duplicate tree referenced from metadata pagePage %lu: btree root of incorrect type %lu on metadata pagePage %lu: item %lu marked deletedPage %lu: duplicate page referenced by internal btree page at item %luPage %lu: duplicate page referenced by recno page at item %luPage %lu: impossible tlen %lu, item %luPage %lu: offpage item %lu has bad pgno %luPage %lu: item %lu of invalid type %luPage %lu: gap between items at offset %luPage %lu: offset %lu unalignedPage %lu: overlapping items at offset %luPage %lu: bad HOFFSET %lu, appears to be %luPage %lu: bad offset %lu at index %luPage %lu: RINTERNAL structure at offset %lu referenced twicePage %lu: item order check unsafe: skippingPage %lu: Recno database has dupsPage %lu: nonsensical type for item %lußføÿÌhøÿßføÿÌhøÿThøÿThøÿThøÿThøÿThøÿhøÿlock_downgradeDB_LOCK->lock_putobject entriesLocker does not existUnexpected lock status: %dDB_ENV->lock_getNot a child transactionParent locker is not validInvalid lock operation: %dDB_ENV->lock_vecNo space for lock object storageDB_ENV->lock_get: invalid lock mode %lu# øÿ´ øÿ° øÿð¡øÿÈ¡øÿ ¡øÿh¢øÿ ¡øÿP¡øÿ¡øÿ ¡øÿ%s: Lock is no longer validLocker is not valid%lu lockersAborting locker %lxDB_ENV->lock_detectwarning: unable to abort locker %lxDB_ENV->lock_detect: unknown deadlock detection mode specifiedÀ¾øÿ¼øÿÀ¾øÿÁøÿ?ÁøÿÂøÿÂøÿªÁøÿ¼øÿÂøÿlocker has write locksFreeing locks for locker %#lx: %sFreeing locker with locksLocker still has lockslocker entrieslock_id_setDB_ENV->lock_id_freeDB_ENV->lock_id(%lx %lx %lx %lx %lx)%-25sDB_ENV->get_lk_max_objectsDB_ENV->get_lk_max_lockersDB_ENV->get_lk_maxlocksDB_ENV->get_lk_conflictsDB_ENV->get_lk_detectDB_ENV->set_env_timeoutDB_ENV->set_timeoutDB_ENV->get_env_timeoutDB_ENV->get_timeoutDB_ENV->set_lk_max_objectsDB_ENV->set_lk_max_lockersDB_ENV->set_lk_max_locksDB_ENV->set_lk_detectDB_ENV->set_lk_conflictsDB_ENV->set_lk_detect: unknown deadlock detection mode specifiedDB_ENV->set_lk_detect: incompatible deadlock detector modeunable to allocate memory for the lock tablelock_open: incompatible deadlock detector modeDB_ENV->lock_statIWRIREADIWRITEWAS_WRITEEXPIREDABORTFREEHELDPENDING%8lx %-10s %4lu %-7s (%lx %lx %lx %lx %lx) %-25s %-7s %7lu0x%lx Lock region parameters:Lock region region mutexlocker table sizeobject table sizeobj_offlocker_offneed_dd%m-%d-%H:%M:%Snext_timeout: %s.%09lunext_timeout: %lu.%09luLock conflict matrix:%lu	Locks grouped by lockers:StatusCount%-8s %-10s%-4s %-7s %s   (D) lk timeout %u lk expires %s.%09lu lk expires %lu.%09luLocks grouped by object:Last allocated locker IDNumber of lock modesNumber of current locksNumber of current lockersNumber of deadlocksLock timeout valueTransaction timeout valueThe size of the lock regionDB_ENV->lock_stat_printüøÿ üøÿ°üøÿÀüøÿÐüøÿàüøÿðùøÿðüøÿüøÿúøÿ üøÿ0üøÿ@üøÿPüøÿ`üøÿpüøÿ----------------- Object ---------------%8lx dd=%2ld locks held %-4d write locks %-4d pid/thread %sDefault locking region information:%#lx	Current maximum unused locker IDMaximum number of locks possibleMaximum number of lockers possibleMaximum number of lock objects possibleMaximum number of locks at any one timeMaximum number of lockers at any one timeNumber of current lock objectsMaximum number of lock objects at any one timeTotal number of locks requestedTotal number of locks releasedTotal number of locks upgradedTotal number of locks downgradedLock requests not available due to conflicts, for which we waitedLock requests not available due to conflicts, for which we did not waitNumber of locks that have timed outNumber of transactions that have timed outLock table is out of available %sunable to allocate memory for mutex; resize mutex regionFreeing mutex for process: %sDB_ENV->set_mutex_maxDB_ENV->set_mutex_incrementDB_ENV->set_mutex_alignDB_ENV->mutex_allocDB_ENV->mutex_set_align: alignment value must be a non-zero power-of-twoUnable to allocate memory for the mutex regionUnable to allocate memory for mutexes from the regionUnable to acquire/release a mutex; check configurationdb handleapplication allocatedenv dblistenv regionlogical locklog filenamelog flushlog handlelog regionmpoolfile handlempool filehandlempool file bucketmpool handlempool hash bucketmpool buffer I/Ompool regionreplication databasereplication regionsequencetwistertxn active listtxn committxn mvcctxn regionunknown mutex type[!Set][/%luM %d%% %s] !Own]%lu	%s DB_ENV->mutex_statMutex region sizeMutex alignmentMutex test-and-set spinsMutex total countMutex free countMutex in-use countMutex maximum in-use countMutex counts%d	UnallocatedDB_MUTEXREGION structure:DB_MUTEXREGION region mutexSize of the aligned mutexNext free mutex%5lu	, %sDB_ENV->mutex_stat_printlogicalself-block#ùÿx$ùÿp$ùÿh$ùÿ#ùÿ`$ùÿX$ùÿP$ùÿH$ùÿ@$ùÿ8$ùÿ0$ùÿ($ùÿ $ùÿ$ùÿ$ùÿ$ùÿ$ùÿø#ùÿ#ùÿ#ùÿ#ùÿð#ùÿ#ùÿè#ùÿà#ùÿØ#ùÿÐ#ùÿ#ùÿÈ#ùÿÀ#ùÿ¸#ùÿDefault mutex region information:mutex	wait/nowait, pct wait, holder, flagsNo cipher structure givenInvalid passwordJoining non-encrypted environment with encryption keyEncryption algorithm not suppliedEncrypted environment: no encryption key suppliedEnvironment encrypted using a different algorithmEncrypted database: no encryption flag specifiedDatabase encrypted using a different algorithmUnencrypted database with a supplied encryption key__db.%s%x.%x%.*s%x.%x%.*s%s%srename: database %s existsClosing a primary DB while a secondary DB has active cursors is unsafeQfùÿhùÿ¸hùÿhùÿØfùÿ fùÿDB->cursorDB->put an index not configured to support duplicatesAppend results in a non-unique secondary key inunsupported byte order, only big and little-endian supportedDuplicate data items are not supported with sorted dataWrite attempted on read-only cursorPut results in a non-unique secondary key in an __dbc_count__dbc_idup__dbc_getcdsgroup_beginCDS groups do not support %sset_nameprepareabortCDS group has active cursors úÿúÿ8 úÿ@úÿÈ úÿ úÿ úÿ úÿúÿúÿúÿúÿ úÿ8 úÿÈ&úÿ&úÿÒ&úÿX'úÿX'úÿX'úÿX'úÿX'úÿÒ&úÿX'úÿ0'úÿ0'úÿX'úÿÒ&úÿè*úÿ(úÿX+úÿ +úÿ +úÿ +úÿ +úÿ +úÿX+úÿ +úÿø*úÿø*úÿ +úÿX+úÿchecksum error: page %lu: catastrophic recovery required__db_dispatchFlushing free list to disk%s: %s %sIllegal record type %lu in logmay not appear in the free listallocation flush failed, some free pagesFatal error in abort of an allocationp;úÿp;úÿ
>:úÿ¸:úÿ;úÿH:úÿf:úÿp;úÿDB_AUTO_COMMIT may not be specified along with a transaction handleDB_AUTO_COMMIT may not be specified in non-transactional environmentDB_THREAD mandates memory allocation flag on DBT %sDBcursor->put forbidden on secondary indicesCursor position must be set before performing this operationDB_READ_UNCOMMITTED is not supported with DB_CONSUME or DB_CONSUME_WAITDB_MULTIPLE/DB_MULTIPLE_KEY require DB_DBT_USERMEM be setDB_MULTIPLE/DB_MULTIPLE_KEY do not support DB_DBT_PARTIALaligned, at least page size and multiples of 1KBDB_MULTIPLE/DB_MULTIPLE_KEY buffers must be DBcursor->pget may only be used on secondary indicesDB_MULTIPLE and DB_MULTIPLE_KEY may not be used on secondary indices%s requires both a secondary and a primary keyDB_GET_BOTH on a secondary index requires a primary keyDB->put forbidden on secondary indicesa partial put in the presence of duplicates requires a cursor operation%s is not supported with DB_CONSUME or DB_CONSUME_WAITDB_MULTIPLE requires DB_DBT_USERMEM be setDB_MULTIPLE does not support DB_DBT_PARTIALDB_UNKNOWN type specified with DB_CREATE or DB_TRUNCATEdatabase environment not yet openedenvironment did not include a memory poolenvironment not created using DB_THREADDB_MULTIVERSION illegal without a transaction specifiedDB_MULTIVERSION illegal with queue databasesDB_TRUNCATE illegal with %s specifiedQueue databases must be one-per-filefiles containing multiple databases may only be opened read-onlyAt least one secondary cursor must be specified to DB->joinAll secondary cursors must share the same transactionDatabase does not have a valid file handleDB->pget may only be used on secondary indicesDatabases may not become secondary indices while cursors are openSecondary index handles may not be re-associatedSecondary indices may not be used as primary databasesPrimary databases may not be configured with duplicatesRenumbering recno databases may not be used as primary databasesThe primary and secondary must be opened in the same environmentThe DB_THREAD setting must be the same for primary and secondaryCallback function may be NULL only when database handles are read-onlyDBcursor->putkey DBTDBcursor->getDBcursor->pgetDB_GET_BOTH_RANGEDB_GET_BOTHprimary keyDB->closeDBcursor->dupDBcursor->delDBcursor->countClosing already-closed cursorDB->syncDB->compactDB->getDB_READ_COMMITTEDDB_READ_UNCOMMITTEDDB_MULTIPLE buffers must be unknown type: %luDB->joinDB->fdDB->delDB->pgetDB->key_rangeDB->associateDB->existsÝXúÿ`ZúÿÝXúÿ`ZúÿÝXúÿÝXúÿPZúÿÝXúÿÝXúÿÝXúÿÝXúÿÝXúÿÝXúÿTYúÿTYúÿÝXúÿÝXúÿÝXúÿÝXúÿHYúÿø\úÿø\úÿè[úÿè[úÿº\úÿ°\úÿº\úÿÀ[úÿ\[úÿ\[úÿ\[úÿH]úÿè[úÿè[úÿè[úÿ\[úÿ\[úÿ\[úÿ\[úÿH]úÿH]úÿH]úÿÔ\úÿÔ\úÿ]úÿôsúÿPsúÿPsúÿPsúÿtúÿtúÿPsúÿPsúÿØsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿPsúÿàtúÿÚwúÿjzúÿ\zúÿczúÿzúÿæyúÿSecondary index corrupt: not consistent with primaryDB_DBT_PARTIAL may not be set on key during join_getAllocation failed for join key, len = %luDBC->get%s page %lu is on free list with type %luÇúÿÇúÿÇúÿÇúÿÇúÿíÅúÿíÅúÿôÅúÿôÅúÿÇúÿÇúÿChecksum failure requires catastrophic recoveryä4ûÿR4ûÿR4ûÿä4ûÿä4ûÿ4ûÿè6ûÿX7ûÿR4ûÿR4ûÿR4ûÿR4ûÿ 8ûÿ 8ûÿDB_ENV->fileid_resetDB_ENV->lsn_resetDB_CONFIG: line too longmutex_set_alignmutex_set_incrementmutex_set_maxmutex_set_tas_spinsrep_bulkrep_delayclientrep_noautoinitrep_nowaitset_data_dirdb_data_dirdb_auto_commitdb_cdb_alldbdb_direct_dbdb_direct_logdb_dsync_dbdb_dsync_logdb_log_autoremovedb_log_inmemorydb_multiversiondb_nolockingdb_nommapdb_nopanicdb_overwritedb_region_initdb_txn_nosyncdb_txn_nowaitdb_txn_snapshotdb_txn_write_nosyncdb_yieldcpuset_lg_dirdb_log_dirdb_lock_defaultdb_lock_expiredb_lock_maxlocksdb_lock_maxwritedb_lock_minlocksdb_lock_minwritedb_lock_oldestdb_lock_randomdb_lock_youngestset_lock_timeoutset_mp_max_writeset_mp_mmapsizeset_region_initset_tmp_dirdb_tmp_dirset_txn_timeoutset_verbosedb_verb_deadlockdb_verb_fileopsdb_verb_fileops_alldb_verb_recoverydb_verb_registerdb_verb_replicationdb_verb_waitsforline %d: %s: incorrect name-value pairunrecognized name-value pair: %søuûÿvûÿvûÿvûÿ(vûÿ8vûÿHvûÿpuûÿ(wûÿ0wûÿ8wûÿHwûÿXwûÿhwûÿxwûÿvûÿunable to allocate space from the buffer cachepgout%s: %s failed for page %lu%s: write failed for page %luunable to create temporary backing file%s: error getting a page for writing%s: error releasing a read-only pagegettimeofdayfileops: mkdir %srwx------__bamc_search__bamc_get__bamc_put__bamc_closeÈÛûÿøÜûÿÞÚûÿØÜûÿÞÚûÿÞÚûÿhÝûÿÞûÿHÝûÿÞÚûÿÞÚûÿÞÚûÿÞûÿhÝûÿÞÚûÿÞÚûÿÞÚûÿÞÚûÿÞÚûÿøÜûÿ ÝûÿXÛûÿèûÿûãûÿÐæûÿçûÿÐæûÿùâûÿùâûÿùâûÿùâûÿcãûÿðãûÿäûÿhäûÿùâûÿùâûÿùâûÿùâûÿXãûÿ¨åûÿ(æûÿ¸æûÿøäûÿ¸æûÿÈüÿ üÿüÿüÿ=üÿ=üÿ=üÿ=üÿ=üÿüÿNot enough room in parent: %s: page %luExisting data sorts differently from put datacursor adjustment after delete failed¸HüÿhHüÿðHüÿàHüÿÐHüÿÀHüÿxIüÿhIüÿ`IüÿXIüÿXIüÿIüÿUnknown record format, page %lu, indx 0__hamc_get__hamc_putH_NOMORE returned to __hamc_getà»üÿºüÿ¨»üÿÐ»üÿ¨»üÿæ¸üÿæ¸üÿæ¸üÿæ¸üÿ ¹üÿÌ¹üÿÐ»üÿÈ¹üÿæ¸üÿæ¸üÿæ¸üÿæ¸üÿ¹üÿ ¹üÿ¹üÿ¨»üÿ¨»üÿXºüÿ»üÿpºüÿpºüÿpºüÿX¹üÿX¹üÿX¹üÿX¹üÿºüÿ»üÿpºüÿ»üÿX¹üÿX¹üÿX¹üÿX¹üÿºüÿºüÿºüÿpºüÿpºüÿ__ham_add_dupùüÿUûüÿùüÿCûüÿùüÿùüÿùüÿùüÿùüÿùüÿùüÿùüÿùüÿrúüÿrúüÿùüÿùüÿùüÿùüÿrúüÿ__hamc_delpgkey1: %s, key2: %s, len: %lu
>curroffset %lu
>indexes: %04X, Attempt to return a deleted item__ham_vrfyPage %lu: database has custom hash function; reverify with DB_NOORDERCHK setPage %lu: Impossible max_bucket %lu on meta pagePage %lu: incorrect high_mask %lu, should be %luPage %lu: incorrect low_mask %lu, should be %luPage %lu: suspiciously high nelem of %luPage %lu: spares array entry %d is invalidPage %lu: item %lu hashes incorrectlyPage %lu: Hash meta page referenced twicePage %lu: impossible first page in bucket %luPage %lu: first page in hash bucket %lu has a prev_pgnoPage %lu: hash page referenced twicePage %lu: duplicates present in non-duplicate databasePage %lu: unsorted dups in sorted-dup databasePage %lu: hash page has bad next_pgnoPage %lu: hash page has bad prev_pgnoPage %lu: hash bucket %lu maps to non-hash pagePage %lu: non-empty page in unused hash bucket %luPage %lu: above max_bucket referencedPage %lu: item %lu is out of order or nonsensicalPage %lu: entries array collided with dataPage %lu: hash key stored as duplicate item %luPage %lu: duplicate item %lu has bad lengthPage %lu: duplicate item %lu has two different lengthsPage %lu: offpage item %lu has bad page numberPage %lu: item %lu has bad typePage %lu: queue record %lu extends past end of pagePage %lu: queue record %lu has bad flags (%#lx)Page %lu: queue database page of incorrect type %luPage %lu: queue database has no meta pagePage %lu: queue databases must be one-per-filePage %lu: queue record length %lu too high for page size and recs/pagePage %lu: database contains multiple Queue metadata pagesWarning: %d extra extent files found__dbq.%s.Client initialization failed.  Need to manually restore clientUnable to get prev of [%lu][%lu][%lu][%lu]: LOG_REQ max lsn: [%lu][%lu]Request for LSN [%lu][%lu] failsPage %lu: overflow page of invalid type %luPage %lu: first page in overflow chain has a prev_pgno %luPage %lu: encountered too many times in overflow traversalPage %lu: overflow page linked twice from leaf or data pagePage %lu: bad next_pgno %lu on overflow pagePage %lu: bad prev_pgno %lu on overflow page (should be %lu)Page %lu: overflow item incompletePage %lu: overflow page has zero reference countAES key material not of correct lengthAES cipher in wrong state (not initialized)AES cipher instance is invalidencryption and decryption key value magicAES key direction is invalidAES key passwd not validAES bad block lengthAES data contents are invalidAES unknown errorAES error unrecognized®ýÿ®ýÿ®ýÿ®ýÿÄýÿ ®ýÿ(®ýÿ0®ýÿøýÿß°%s: %s: %s
>%s: Invalid numeric argument%s: %s: Invalid numeric argument
>%s: %s: Less than minimum value (%lu)
>%s: Less than minimum value (%lu)%s: %s: Greater than maximum value (%lu)
>%s: Greater than maximum value (%lu)%s: %s: Less than minimum value (%ld)
>%s: Less than minimum value (%ld)%s: %s: Greater than maximum value (%ld)
>%s: Greater than maximum value (%ld)P§ôQSeA~Ã¤^':Ëk«;ñE«Xú¬ãKUú0 ömvvÌ%Lõü×åO×Ë*ÅD5&£bµIZ±Þgº%êEáÀþ]u/ÃðL£FÆùÓkç_ëzm¿ÚYR-¾ÔÓ!tX)iàIDÈÉjÂuxyôk>XÝq¹'¶Oá¾ðf¬ É´:Î}Jßc1å`3QESbàwd±®k» þ+ùXhHpýElÞ·ø{R#Ós«âKrWã*«Uf(ë²Âµ/{Å¥7Óò(0²¥¿#ºj\í+Ï´y§ðòó¡âiNÍôÚeÕ¾b4Ñþ¦ÄS.4 Uó¢2áuëö¤9ìªï`@q^Qn½ù!>=Ý®>ÝF½æMµT]ÄqoÔÿP`$ûé½ÖÌC@wÙg½Bè°8[çÛîÈyG
>|¡éB|Éø	Hí+2¬pNrZlûÿýV8Õ®='9-6dÙ
>!¦\hÑT[:.6$±g
>çWÒî´OÅÀ¢ ÜaiKwZ
>ºâå* ÀCà"<
	Çò¹¨¶-È©ñWLu¯»Ýîý`£&÷¼õr\Å;fD4~û[v)CÜÆ#Ëhüí¶cñä¸ÊÜ1×cB@" Æ}$Jø=»Ò2ù®m¡)ÇK/ó0²ÜìR
ÐãÁwl³+¹p©úH"déGÄü¨?ð Ø,}Vï3"ÇNIÁÑ8Ùþ¢Ê6ÔÏõ¦(Þz¥&·Ú¤¿?ä:,
xPÌ_jbF~TÂöè¸Ø^÷9.õ¯Ã¾]|Ði©-Õo³%Ï;¬È§}ncè{»;Û	x&ÍôYn·ì¨Oenæ~æÿªÏ¼!æèïÙçºÎ6oJÔ	êÖ|°)¯²¤11#?*0¥ÆÀf¢57¼Nt¦Êü°ÐàØ§3Jñ÷ÚìAPÍ/öÖMvM°ïCTMªÌßäãµÑjL¸,ÁQeFê^]5stú.AûZg³RÒÛ3VéGÖma×z¡7øY<ëî'©Î5Éa·íåá<±GzYßÒ?sòUyÎ¿7ÇsêÍ÷S[ªý_o=ßÛDxó¯Ê>Äh¹,4$8_@£ÂrÃ%â¼I<(A
ÿq¨9Þ³ä´ØÁVdaË{p¶2Õt\lHBW¸Ð§ôQPeA~S¤Ã^':k«;ËEñXú¬«ãKú0 UmvövÌLõ%×åOüË*Å×D5&£bµZ±ÞIº%gêEÀþ]áu/ÃðLF£ùÓkÆ_çzm¿ëYRÚ¾Ô-!tXÓiàI)ÈÉDÂujyôx>Xkq¹'ÝOá¾¶ð¬ Éf:Î}´Jßc1å3Q`SbEwd±à®k» þ+ùhHpXýElÞø{R·Ós«#KrâãW«Uf*(ë²Âµ/{Å7Ó¥(0ò¥¿#²jºí\Ï+´y§òóðâiN¡ôÚeÍ¾Õb4Ñþ¦ÄS.4Uó¢ á2ëö¤uì9ï`@ªq^n½Q!>ùÝ=>Ý®½æMFTµ]ÄqÔoP`ÿû$é½ÖC@ÌÙgwBè°½[ç8îÈyÛ
>|¡GB|éøÉ	í+2Hp¬rZlNÿýû8VÕ®=9-6'Ù
>d¦\h!T[Ñ.6$:g
>±çWî´ÒÅÀO Üa¢KwZiºâ
>* Àåà"<C
	Çò¨¶-¹©ÈñWu¯LÝî»`£ý&÷õr\¼;fDÅ~û[4)CvÆ#ËÜüí¶hñä¸cÜ1×ÊcB"@Æ $J}=»Òø2ù®¡)Çm/K0²ÜóR
ìãÁwÐ³+l¹p©HúdéG"ü¨Ä?ð ,}VØ3"ïNIÇÑ8ÙÁ¢ÊþÔ6õ¦ÏÞz¥(·Ú&¿?¤:,äxP
Ì_jF~TböÂ¸Øè÷9.^¯Ãõ]¾Ði|-Õo©%Ï³¬È;}§cèn»;Û{x&Í	Ynô·ìO¨næeæÿª~Ï¼!èïæçºÙ6oJÎ	êÔ|°)Ö²¤1¯#?*1¥Æ0f¢5À¼Nt7Êü¦Ðà°Ø§3ñJÚìA÷PÍö/ÖMv°ïCMMªÌTäßµÑãjL,Á¸QeFê^5]túsAû.g³ZÒÛRVé3GÖma×¡7zøY<ë'©ÎîÉa·5åáí±Gz<ßÒYsòU?Îy7Çs¿Í÷Sêªý_[o=ßÛDxó¯ÊÄh¹>4$8,@£Â_Ãr%â¼I<(
ÿA¨9q³Þä´ØÁVdË{a¶2Õp\lHtW¸ÐBôQP§A~SeÃ¤':^«;ËkñEú¬«XãK0 UúvömÌvõ%LåOü×*Å×Ë5&Dbµ£±ÞIZº%gêEþ]áÀ/ÃuLðF£ÓkÆùç_m¿ëzRÚY¾Ô-tXÓ!àI)iÉDÈÂujôxyXk>¹'Ýqá¾¶Oð Éf¬Î}´:ßcJå1Q`3SbEd±àwk»®þ ù+HpXhEýÞl{R·øs«#ÓKrâãWUf*«ë²(µ/ÂÅ{7Ó¥(0ò¿#²¥ºjí\Ï+y§´óðòiN¡âÚeÍôÕ¾4Ñb¦Äþ.4Só¢ U2áö¤uë9ì`@ªïq^n½Q!>ùÝ=>Ý®æMF½TµÄq]oÔP`ÿ$û½Öé@ÌCÙgwè°½Bç8[ÈyÛî|¡G
>B|éøÉ	+2Hí¬pZlNrýûÿV8®=Õ-6'9
>dÙ\h!¦[ÑT6$:.
>±gWçî´ÒÀOÅÜa¢ wZiKâ
>º Àå*"<Cà	
òÇ¶-¹¨È©ñWu¯Lî»Ý£ý`÷&r\¼õfDÅ;û[4~Cv)#ËÜÆí¶hüä¸cñ1×ÊÜcB@"Æ J}$»Òø=ù®2)Çm¡K/²Üó0
ìRÁwÐã³+lp©¹úHéG"dü¨Äð ?}VØ,3"ïIÇN8ÙÁÑÊþ¢Ô6õ¦Ïz¥(Þ·Ú&?¤¿:,äxP
_jÌ~TbFöÂØè¸9.^÷Ãõ¯]¾Ði|Õo©-%Ï³¬È;§}ènc;Û{»&Í	xYnôì·O¨æenÿª~æ¼!ÏïæèçºÙoJÎ6êÔ	°)Ö|¤1¯²?*1#¥Æ0¢5ÀfNt7¼ü¦Êà°Ð§3ØñJìA÷ÚÍP/öMvÖïCM°ªÌTMäßÑãµjL,Á¸eFQ^ê]5ústû.Ag³ZÛRÒé3VÖmG×a¡7zøYë<©Îî'a·5ÉáíåGz<±ÒYßòU?syÎÇs¿7÷SêÍý_[ª=ßoDxÛ¯Êóh¹>Ä$8,4£Â_@rÃâ¼%<(I
ÿA¨9qÞ³´ØäVdÁË{a2Õp¶lHt\¸ÐBWQP§ô~SeAÃ¤:^';Ëk«ñE¬«XúKã Uú0ömvvÌõ%LOü×åÅ×Ë*&D5µ£bÞIZ±%gºEê]áÀþÃu/ðL£FkÆùÓç_¿ëzmÚYRÔ-¾XÓ!tI)iàDÈÉujÂôxyk>X'Ýq¹¾¶OáðÉf¬ }´:ÎcJßå1`3QbES±àwd»®kþ ù+pXhHýElÞR·ø{«#ÓsrâKãWf*«U²(ë/Âµ{ÅÓ¥70ò(#²¥¿ºjí\+Ï§´yóðòN¡âieÍôÚÕ¾Ñb4Äþ¦4S.¢ Uó2á¤uëö9ì@ªï`^q½Qn>ù!=ÝÝ®>MF½æµTq]ÄoÔ`ÿP$ûÖé½ÌC@gwÙ°½Bèç8[yÛîÈ¡G
>||éBøÉ	2Hí+¬plNrZýûÿV8=Õ®6'9-
>dÙh!¦\ÑT[$:.6±g
>çW´ÒîOÅÀa¢ ÜZiKwâ
>ºÀå* <Cà"
	òÇ-¹¨¶È©Wñ¯Luî»Ý£ý`÷&\¼õrDÅ;f[4~ûv)CËÜÆ#¶hüí¸cñä×ÊÜ1Bc@" Æ}$JÒø=»®2ùÇm¡)K/Üó0²
ìRwÐãÁ+l³©¹púHG"dé¨Äü ?ðVØ,}"ï3ÇNIÙÁÑ8þ¢Ê6Ô¦Ïõ¥(ÞzÚ&·?¤¿,ä:P
xjÌ_TbF~öÂè¸Ø.^÷9õ¯Ã¾]i|Ðo©-ÕÏ³%È;¬§}èncÛ{»;Í	x&nôYì·¨Oæenª~æÿ!Ï¼ïæèºÙçJÎ6oêÔ	)Ö|°1¯²¤*1#?Æ0¥5Àf¢t7¼Nü¦Êà°Ð3Ø§ñJA÷ÚìPÍ/övÖMCM°ïÌTMªäßãµÑLjÁ¸,FQeê^]5ústû.A³ZgRÒÛé3VmGÖa×7z¡Yøë<Îî'©·5Éaáíåz<±GYßÒU?sòyÎs¿7ÇSêÍ÷_[ªýßo=xÛDÊó¯¹>Äh8,4$Â_@£rÃ¼%â(I<ÿA
9q¨Þ³Øä´dÁV{aËÕp¶2Ht\lÐBW¸RRRR				jjjjÕÕÕÕ00006666¥¥¥¥8888¿¿¿¿@@@@££££óóóó××××ûûûû||||ãããã9999////ÿÿÿÿ4444CCCCDDDDÄÄÄÄÞÞÞÞééééËËËËTTTT{{{{2222¦¦¦¦ÂÂÂÂ####====îîîîLLLLBBBBúúúúÃÃÃÃNNNN....¡¡¡¡ffff((((ÙÙÙÙ$$$$²²²²vvvv[[[[¢¢¢¢IIIImmmmÑÑÑÑ%%%%rrrrøøøøööööddddhhhhÔÔÔÔ¤¤¤¤\\\\ÌÌÌÌ]]]]eeee¶¶¶¶llllppppHHHHPPPPýýýýíííí¹¹¹¹ÚÚÚÚ^^^^FFFFWWWW§§§§ØØØØ««««¼¼¼¼ÓÓÓÓ
>
>
>
>÷÷÷÷ääääXXXX¸¸¸¸³³³³EEEEÐÐÐÐ,,,,ÊÊÊÊ????ÁÁÁÁ¯¯¯¯½½½½kkkk::::AAAAOOOOggggÜÜÜÜêêêêòòòòÏÏÏÏÎÎÎÎðððð´´´´ææææssss¬¬¬¬tttt""""çççç5555ââââùùùù7777èèèèuuuußßßßnnnnGGGGññññqqqq))))ÅÅÅÅoooo····bbbbªªªª¾¾¾¾üüüüVVVV>>>>KKKKÆÆÆÆÒÒÒÒyyyy    ÛÛÛÛÀÀÀÀþþþþxxxxÍÍÍÍZZZZôôôôÝÝÝÝ¨¨¨¨3333ÇÇÇÇ1111±±±±YYYY''''ìììì____````QQQQ©©©©µµµµJJJJ

----ååååzzzzÉÉÉÉïïïï    àààà;;;;MMMM®®®®****õõõõ°°°°ÈÈÈÈëëëë»»»»<<<<SSSSaaaa++++~~~~ººººwwwwÖÖÖÖ&&&&ááááiiiiccccUUUU!!!!}}}}¥ccÆ||øwwî{{ö
òòÿ½kkÖ±ooÞTÅÅP00`©ggÎ}++Vþþçb××µæ««MvvìEÊÊ@ÉÉ}}úúúïëYY²ÉGGððûìAgÔÔ³ý¢¢_ê¯¯E¿#÷¤¤Srrä[ÀÀÂ··uýýá®=j&&LZ66lA??~÷÷õOÌÌ\44hô¥¥Q4ååÑññùqqâsØØ«S11b?*RÇÇe##F^ÃÃ(0¡7
>µ/	6$=ââß&ëëÍi''NÍ²²uuê		t,,X.4-6²nnÜîZZ´û  [öRR¤M;;vaÖÖ·Î³³}{))R>ããÝq//^õSS¦hÑÑ¹,ííÁ`  @üüãÈ±±yí[[¶¾jjÔFËËÙ¾¾gK99rÞJJÔLLèXX°JÏÏkÐÐ»*ïïÅåªªOûûíÅCC×MMU33fÏEEùùéþðPP D<<xº%ã¨¨KóQQ¢þ££]À@@?¼!H88põõñß¼¼cÁ¶¶wuÚÚ¯c!!B0 ÿÿåóóýmÒÒ¿LÍÍ5&/ììÃá__¾¢5ÌDD9.WÄÄò§§U~~üG==z¬ddÈç]]º+2ssæ ``ÀÑOOÜÜ£f""D~**T«;ÊFF)îîÇÓ¸¸k<(yÞÞ§â^^¼vÛÛ;ààÛV22dN::t
>
>ÛII
>l$$Hä\\¸]ÂÂnÓÓ½ï¬¬C¦bbÄ¨9¤17ääÓyyò2ççÕCÈÈY77n·mmÚdÕÕ±ÒNNà©©I´llØúVV¬ôôó%êêÏ¯eeÊzzôé®®GÕººoxxðo%%Jr..\$8ñ¦¦WÇ´´sQÆÆ#èèË|ÝÝ¡ttè!>ÝKKÜ½½a
ppàB>>|ÄµµqªffÌØHHöö÷£aaÂ_55jùWW®Ð¹¹iXÁÁ':¹'8ááÙøøë³+3"»iiÒpÙÙ©§3¶-"< ééÉIÎÎÿUUªx((Pzßß¥ø¡¡Y

Ú¿¿e1ææ×ÆBB¸hhÐÃAA°)w--ZË°°{üTT¨Ö»»m:,ccÆ¥||øwwî{{öòòÿ
kkÖ½ooÞ±ÅÅT00`PggÎ©++V}þþç××µb««MævvìÊÊEÉÉ@}}úúúïYY²ëGGÉððûAìÔÔ³g¢¢_ý¯¯Eê#¿¤¤S÷rräÀÀ[··uÂýýá=®&&Lj66lZ??~A÷÷õÌÌO44h\¥¥QôååÑ4ññùqqâØØ«s11bS*?ÇÇR##FeÃÃ^0(7¡
>/µ	$6ââß=ëëÍ&''Ni²²Íuuê		,,Xt4.6-nnÜ²ZZ´î  [ûRR¤ö;;vMÖÖ·a³³}Î))R{ããÝ>//^qSS¦õÑÑ¹hííÁ,  @`üüã±±yÈ[[¶íjjÔ¾ËËF¾¾gÙ99rKJJÞLLÔXX°èÏÏJÐÐ»kïïÅ*ªªOåûûíCCÅMM×33fUEEÏùùéþPP ð<<xD%º¨¨KãQQ¢ó££]þ@@À?!¼88pHõõñ¼¼cß¶¶wÁÚÚ¯u!!Bc 0ÿÿåóóýÒÒ¿mÍÍL&5ììÃ/__¾á5¢DDÌ.9ÄÄW§§Uò~~ü==zGddÈ¬]]ºç2+ssæ``À OOÑÜÜ£""Df**T~;«FFÊîîÇ)¸¸kÓ(<ÞÞ§y^^¼âÛÛvààÛ;22dV::tN
>
>IIÛ
>$$Hl\\¸äÂÂ]ÓÓ½n¬¬CïbbÄ¦9¨1¤ääÓ7yyòççÕ2ÈÈC77nYmmÚ·ÕÕ±dNNÒ©©IàllØ´VV¬úôôóêêÏ%eeÊ¯zzô®®GéººoÕxxð%%Jo..\r8$¦¦Wñ´´sÇÆÆQèèË#ÝÝ¡|ttè>!KKÝ½½aÜ
ppà>>|BµµqÄffÌªHHØöö÷aaÂ£55j_WW®ù¹¹iÐÁÁX:''¹ááÙ8øøë+³"3iiÒ»ÙÙ©p3§-¶<"ééÉ ÎÎIUUªÿ((Pxßß¥z¡¡Yø

¿¿eÚææ×1BBÆhhÐ¸AAÃ)°--Zw°°{ËTT¨ü»»mÖ,:cÆ¥c|ø|wîw{ö{òÿ
òkÖ½koÞ±oÅTÅ0`P0gÎ©g+V}+þçþ×µb×«Mæ«vìvÊEÊÉ@É}ú}úïúY²ëYGÉGðûðAìÔ³gÔ¢_ý¢¯Eê¯#¿¤S÷¤rärÀ[À·uÂ·ýáý=®&Lj&6lZ6?~A?÷õ÷ÌOÌ4h\4¥Qô¥åÑ4åñùñqâqØ«sØ1bS1*?ÇRÇ#Fe#Ã^Ã0(7¡
>/µ	$6âß=âëÍ&ë'Ni'²Í²uêu		,Xt,4.6-nÜ²nZ´îZ [û R¤öR;vM;Ö·aÖ³}Î³)R{)ãÝ>ã/^q/S¦õSÑ¹hÑíÁ,í @` üãü±yÈ±[¶í[jÔ¾jËFË¾gÙ¾9rK9JÞJLÔLX°èXÏJÏÐ»kÐïÅ*ïªOåªûíûCÅCM×M3fU3EÏEùéùþP ðP<xD<%º¨Kã¨Q¢óQ£]þ£@À@?!¼8pH8õñõ¼cß¼¶wÁ¶Ú¯uÚ!Bc! 0ÿåÿóýóÒ¿mÒÍLÍ&5ìÃ/ì_¾á_5¢DÌD.9ÄWÄ§Uò§~ü~=zG=dÈ¬d]ºç]2+sæs`À `OÑOÜ£Ü"Df"*T~*;«FÊFîÇ)î¸kÓ¸(<Þ§yÞ^¼â^ÛvÛàÛ;à2dV2:tN:
>
>IÛI
>$Hl$\¸ä\Â]ÂÓ½nÓ¬Cï¬bÄ¦b9¨1¤äÓ7äyòyçÕ2çÈCÈ7nY7mÚ·mÕ±dÕNÒN©Ià©lØ´lV¬úVôóôêÏ%êeÊ¯ezôz®Gé®ºoÕºxðx%Jo%.\r.8$¦Wñ¦´sÇ´ÆQÆèË#èÝ¡|Ýtèt>!KÝK½aÜ½
pàp>|B>µqÄµfÌªfHØHö÷öaÂ£a5j_5W®ùW¹iÐ¹ÁXÁ:''¹áÙ8áøëø+³"3iÒ»iÙ©pÙ3§-¶<"éÉ éÎIÎUªÿU(Px(ß¥zß¡Yø¡

¿eÚ¿æ×1æBÆBhÐ¸hAÃA)°-Zw-°{Ë°T¨üT»mÖ»,:Æ¥ccø||îwwö{{ÿ
òòÖ½kkÞ±ooTÅÅ`P00Î©ggV}++çþþµb××Mæ««ìvvEÊÊ@ÉÉú}}ïúú²ëYYÉGGûððAì³gÔÔ_ý¢¢Eê¯¯#¿S÷¤¤ärr[ÀÀuÂ··áýý=®Lj&&lZ66~A??õ÷÷OÌÌh\44Qô¥¥Ñ4ååùññâqq«sØØbS11*?RÇÇFe##^ÃÃ0(7¡
>/µ	$6ß=ââÍ&ëëNi''Í²²êuu		Xt,,4.6-Ü²nn´îZZ[û  ¤öRRvM;;·aÖÖ}Î³³R{))Ý>ãã^q//¦õSS¹hÑÑÁ,íí@`  ãüüyÈ±±¶í[[Ô¾jjFËËgÙ¾¾rK99ÞJJÔLL°èXXJÏÏ»kÐÐÅ*ïïOåªªíûûÅCC×MMfU33ÏEEéùùþ ðPPxD<<%ºKã¨¨¢óQQ]þ££À@@?!¼pH88ñõõcß¼¼wÁ¶¶¯uÚÚBc!! 0åÿÿýóó¿mÒÒLÍÍ&5Ã/ìì¾á__5¢ÌDD.9WÄÄUò§§ü~~zG==È¬ddºç]]2+æssÀ ``ÑOO£ÜÜDf""T~**;«ÊFFÇ)îîkÓ¸¸(<§yÞÞ¼â^^vÛÛÛ;ààdV22tN::
>
>ÛII
>Hl$$¸ä\\]ÂÂ½nÓÓCï¬¬Ä¦bb9¨1¤Ó7ääòyyÕ2ççCÈÈnY77Ú·mm±dÕÕÒNNIà©©Ø´ll¬úVVóôôÏ%êêÊ¯eeôzzGé®®oÕººðxxJo%%\r..8$Wñ¦¦sÇ´´QÆÆË#èè¡|ÝÝètt>!ÝKKaÜ½½
àpp|B>>qÄµµÌªffØHH÷ööÂ£aaj_55®ùWWiÐ¹¹XÁÁ:''¹Ù8ááëøø+³"3Ò»ii©pÙÙ3§-¶<"É ééIÎÎªÿUUPx((¥zßßYø¡¡

eÚ¿¿×1ææÆBBÐ¸hhÃAA)°Zw--{Ë°°¨üTTmÖ»»,:cccc||||wwww{{{{òòòòkkkkooooÅÅÅÅ0000gggg++++þþþþ××××««««vvvvÊÊÊÊÉÉÉÉ}}}}úúúúYYYYGGGGððððÔÔÔÔ¢¢¢¢¯¯¯¯¤¤¤¤rrrrÀÀÀÀ····ýýýý&&&&6666????÷÷÷÷ÌÌÌÌ4444¥¥¥¥ååååññññqqqqØØØØ1111ÇÇÇÇ####ÃÃÃÃââââëëëë''''²²²²uuuu				,,,,nnnnZZZZ    RRRR;;;;ÖÖÖÖ³³³³))))ãããã////SSSSÑÑÑÑíííí    üüüü±±±±[[[[jjjjËËËË¾¾¾¾9999JJJJLLLLXXXXÏÏÏÏÐÐÐÐïïïïªªªªûûûûCCCCMMMM3333EEEEùùùùPPPP<<<<¨¨¨¨QQQQ££££@@@@8888õõõõ¼¼¼¼¶¶¶¶ÚÚÚÚ!!!!ÿÿÿÿóóóóÒÒÒÒÍÍÍÍìììì____DDDDÄÄÄÄ§§§§~~~~====dddd]]]]ssss````OOOOÜÜÜÜ""""****FFFFîîîî¸¸¸¸ÞÞÞÞ^^^^ÛÛÛÛàààà2222::::
>
>
>
>IIII$$$$\\\\ÂÂÂÂÓÓÓÓ¬¬¬¬bbbbääääyyyyççççÈÈÈÈ7777mmmmÕÕÕÕNNNN©©©©llllVVVVôôôôêêêêeeeezzzz®®®®ººººxxxx%%%%....¦¦¦¦´´´´ÆÆÆÆèèèèÝÝÝÝttttKKKK½½½½pppp>>>>µµµµffffHHHHööööaaaa5555WWWW¹¹¹¹ÁÁÁÁááááøøøøiiiiÙÙÙÙééééÎÎÎÎUUUU((((ßßßß¡¡¡¡

¿¿¿¿ææææBBBBhhhhAAAA----°°°°TTTT»»»» @6;ð.ÝEðÿ/Fðÿ,/8HðÿP/Jðÿt/ØJðÿ/øKðÿ´/HLðÿÔ/Lðÿð/ÈMðÿ0èNðÿ80øOðÿX0Pðÿt0¨Pðÿ0Qðÿ¼0Rðÿà0XRðÿü0XSðÿ 1UðÿD1hWðÿd1Yðÿ18Yðÿ¤1øZðÿÄ1\ðÿä1¸_ðÿ2`ðÿ 2h`ðÿ<2øaðÿ`2(cðÿ2¸dðÿ¨2hgðÿÈ2Èhðÿì2Hiðÿ3øjðÿ,3ÈkðÿP38lðÿp3hmðÿ38pðÿ¸3(sðÿÜ3¸sðÿ4Xtðÿ$4XuðÿH4uðÿd4øuðÿ4wðÿ¤4yðÿÈ4(zðÿì4Èzðÿ5h{ðÿ45¸{ðÿP5ø{ðÿl5X|ðÿ5¨|ðÿ¤5è|ðÿÀ5(}ðÿÜ5}ðÿø5¸ðÿ6øðÿ86HðÿT6ðÿp6øðÿ68ðÿ¬6ðÿÈ6Øðÿä6(ðÿ7Èðÿ$7hðÿH7èðÿh78ðÿ7ðÿ¨7¨ðÿÄ7¸ðÿà7Øðÿü7èðÿ8ðÿ48ðÿP88ðÿl8ðÿ8ðÿ¤8ðÿÄ8øðÿà8Èðÿü8hðÿ9Øðÿ89xðÿX9ðÿx9hðÿ9ðÿÀ98ðÿä9xðÿ:¨ðÿ :Øðÿ<:ðÿX:8ðÿt:hðÿ:ðÿ¬:hðÿÌ:øðÿè:ðÿ;¸ðÿ ;èðÿ<;ðÿX;hðÿt;Èðÿ;hðÿ´;ðÿØ;(ðÿü;èðÿ<ðÿ<<x ðÿ`<h¡ðÿ<È¡ðÿ <È¦ðÿÀ<è¦ðÿÜ<h§ðÿø<§ðÿ=ø§ðÿ0=X¨ðÿT=È¬ðÿt=(®ðÿ=¯ðÿ´=h°ðÿØ=¨µðÿø=èµðÿ>XÀðÿ4>ÈÃðÿT>xÅðÿt>Øðÿ>ÈØðÿ¸>øÝðÿØ>Hàðÿü>Hæðÿ?èæðÿ@?èèðÿ`?ìðÿ?èððÿ¤?ñðÿÈ?óðÿè?÷ðÿ@Øùðÿ0@¨ñÿP@Hñÿp@Xñÿ@Hñÿ´@èñÿÔ@8ñÿô@
ñÿA8ñÿ8Axñÿ\AñÿA(ñÿ¤AhñÿÈAñÿèAøñÿBø ñÿ,BH!ñÿLB#ñÿlB%ñÿB8'ñÿ¬B(ñÿÐBX)ñÿôBÈ*ñÿCØ,ñÿ<C(-ñÿXCØ0ñÿxCè1ñÿCè4ñÿ¼C¸:ñÿÜCÈ;ñÿüC>ñÿDè>ñÿ<D?ñÿ\D@ñÿD¸Añÿ DBñÿÀDCñÿàDXCñÿüDØDñÿEØEñÿ@EøFñÿdEØJñÿEØLñÿ¤E(MñÿÀEØNñÿàEèOñÿFøOñÿFPñÿ8FhPñÿTFxSñÿtFøVñÿFØWñÿ¸FØZñÿØFØ\ñÿøF_ñÿGØ_ñÿ4Gø_ñÿPG`ñÿlG(`ñÿGH`ñÿ¤GX`ñÿÀGh`ñÿÜGx`ñÿøG`ñÿH¸`ñÿ0HØ`ñÿLHè`ñÿhHø`ñÿHañÿ Hañÿ¼H(añÿØHHañÿôHhañÿI¸añÿ,IbñÿHI¨bñÿdIøbñÿIHcñÿI¨cñÿ¸IdñÿÔIXdñÿðI¸dñÿJødñÿ(J8eñÿDJeñÿ`JøeñÿJxfñÿJgñÿÀJjñÿàJ¨lñÿKmñÿ(KuñÿHKxvñÿhKwñÿKwñÿ°K(~ñÿÐKh~ñÿìKÈ~ñÿLñÿ,L(ñÿPLøñÿpL¸ñÿLøñÿ¸LèñÿÜL¸ñÿüLXñÿ MHñÿ@MñÿdMèñÿM(ñÿ¤Mè¯ñÿÄM°ñÿàM8°ñÿüMø°ñÿ N¨²ñÿ@Nx´ñÿ`NµñÿNx¶ñÿ¤N8·ñÿÈNÁñÿèNxÂñÿOèÇñÿ,O¸ÈñÿPOÉñÿtOxÒñÿOèÒñÿ°O8ÕñÿÐOh×ñÿðOØñÿPØÙñÿ0PxÛñÿPPHññÿpPxòñÿPXöñÿ´P8úñÿÔPúñÿðPøúñÿQ¨þñÿ,Q8òÿLQxòÿlQ¨òÿQÈòÿ´QèòÿØQè	òÿüQÈ
>òÿ R
òÿ@RXòÿ`R8òÿRòÿ¤RòÿÄRòÿèRØòÿSòÿ(S(òÿHSHòÿlS¨ òÿSè"òÿ°S¨#òÿÔS¸$òÿøS8'òÿT8)òÿ@Tø;òÿ`TÈAòÿTFòÿ Tè[òÿÀT\òÿäTH_òÿU(`òÿ(UèaòÿHUbòÿdUxbòÿUbòÿ U8còÿÄUØcòÿèUhdòÿVèfòÿ,VhòÿLVhlòÿlVøpòÿVhtòÿ¬VvòÿÌV¸{òÿìVh~òÿWÈòÿ0WØòÿPWòÿlWøòÿWòÿ´WØòÿÔWØòÿôWxòÿXxòÿ8XÈòÿTXx¡òÿtX£òÿX(£òÿ´X¤òÿØXØ¤òÿôXX¦òÿYØ¦òÿ<Y©òÿ`YØ·òÿYø¸òÿ¨YÈ¹òÿÌY»òÿìYè¼òÿZh¾òÿ4Z¿òÿXZØÀòÿxZhÃòÿZÃòÿ´ZÃòÿÐZ¸ÃòÿìZÄòÿ[hÄòÿ$[ÅòÿH[hÅòÿh[èÅòÿ[8Æòÿ [¸Æòÿ¼[8ÇòÿØ[8Èòÿü[Éòÿ \ØÉòÿD\¸Êòÿh\Ëòÿ\Ìòÿ°\èÍòÿÔ\8Ïòÿô\hÒòÿ](Õòÿ4]¨×òÿX]¨àòÿx]háòÿ]ÈâòÿÀ]xåòÿà]Xéòÿ^Hôòÿ ^XöòÿD^ø÷òÿd^hóÿ^èóÿ¨^hóÿÌ^Ø$óÿì^Ø&óÿ_ø&óÿ(_H'óÿD_h'óÿ`_'óÿ|_è'óÿ_((óÿ¸_¨(óÿØ_h)óÿü_8*óÿ`*óÿ8`ø*óÿT`X+óÿp`¸,óÿ`¨-óÿ°`8.óÿÐ`¨.óÿì`h/óÿaè/óÿ,a¨0óÿHax1óÿdaÈ2óÿaH5óÿ¨ah8óÿÈa¨<óÿìaØ=óÿbh@óÿ0bhOóÿTbØQóÿtb¸WóÿbYóÿ¸bHYóÿÔbXYóÿðbÈYóÿcxZóÿ0cX[óÿPcø\óÿpc^óÿceóÿ°cØeóÿÔc¸fóÿøcgóÿdhóÿ@dXióÿdd8jóÿdÈjóÿ¨dxkóÿÈdHlóÿìdmóÿeØmóÿ,eróÿLeróÿheXóÿeHóÿ¨eXóÿÈeøóÿìeóÿføóÿ0f(óÿLfxóÿhfÈóÿf8¥óÿ¨f¦óÿÈf¨óÿìfh¨óÿg©óÿ$gÈ²óÿDgèµóÿdgh¹óÿg¸¹óÿ g¿óÿÄgø¿óÿàgXÀóÿhÁóÿ$hhÄóÿDhØÆóÿhhÒóÿhxÚóÿ¨høÛóÿÌhÝóÿðhØÝóÿi¨ßóÿ,iøàóÿLiØãóÿliXåóÿiñóÿ¬iòóÿÐiòóÿìixôóÿj¸õóÿ0jX÷óÿTj(úóÿtjHúóÿjúóÿ¬jØúóÿÈj(ûóÿäjèûóÿkÈüóÿ,k8ýóÿPk¸ýóÿtk¨þóÿk¸ÿóÿ¼kÈÿóÿØkØÿóÿôkèÿóÿløÿóÿ,lxôÿLlôÿllôÿløôÿ¬lHôÿÌlôÿìl¨ôÿmÈôÿ$môÿHmØôÿhm	ôÿm¨	ôÿ°mèôÿÐmxôÿôm¨ôÿnèôÿ8nxôÿ\nèôÿnxôÿ n¨ôÿ¼nôÿØnhôÿønØôÿoxôÿ@ohôÿdoôÿoÈôÿ oôÿ¼oXôÿÜoôÿøo!ôÿp$ôÿ<p(&ôÿ\p('ôÿp(ôÿ px)ôÿÀpH,ôÿäpx-ôÿq.ôÿ(q8/ôÿHq¨/ôÿlqø/ôÿq80ôÿ¤qØMôÿÄqÈNôÿäq8PôÿrHPôÿ rhPôÿ<r¨PôÿXrQôÿtrøQôÿrXRôÿ°rÈSôÿÐrTôÿôrÈVôÿsØWôÿ8s¨Xôÿ\shYôÿs8`ôÿ saôÿÄs(bôÿäs¸fôÿtxgôÿ$t(hôÿ@txkôÿ`t¸môÿtXoôÿ¤tètôÿÄt¸uôÿètzôÿuh{ôÿ,uÈ~ôÿLuØôÿpu¨ôÿuxôÿ°uôÿÐuØôÿðuôÿv¸ôÿ4vØôÿXvxôÿ|v8ôÿ vøôÿÄvØôÿèv¸ôÿwxôÿ0wôÿPwøôÿpwhôÿwøôÿ´w¢ôÿÔw(¢ôÿðw8¢ôÿxX¢ôÿ(x¸¢ôÿDx£ôÿ`x£ôÿ|x¤ôÿ xX¦ôÿÄx§ôÿèx¨©ôÿy(ôÿ(y¸ôÿLy°ôÿlyØ²ôÿy´ôÿ°yÈ¶ôÿÐyX»ôÿðy¨»ôÿz½ôÿ0z¨½ôÿLz¾ôÿlzø¿ôÿz(Áôÿ°zØÁôÿÔzxÃôÿøzèÄôÿ{(Èôÿ8{HÈôÿT{èËôÿt{hÍôÿ{èÙôÿ¸{hÛôÿÜ{XÝôÿü{(ßôÿ|¸ßôÿ<|xàôÿ`|øàôÿ|¨áôÿ |ÈâôÿÄ|Hæôÿä|Èæôÿ}(çôÿ(}ØçôÿL}Øèôÿp}(éôÿ}xéôÿ¨}ÈéôÿÄ}êôÿà}hêôÿü}xêôÿ~¸êôÿ4~ÈêôÿP~xìôÿp~Øìôÿ~íôÿ¨~íôÿÈ~øíôÿè~Hîôÿîôÿ(èîôÿHxïôÿlðôÿ¸ðôÿ¬XñôÿÌèñôÿìxòôÿØóôÿ0XôôÿTxõôÿtöôÿ¸öôÿ´høôÿÔÈùôÿôýôÿxþôÿ8hõÿ\õÿ|õÿ õÿÀøõÿà¸$õÿ'õÿ$)õÿDØ,õÿhX1õÿè7õÿ°(<õÿÔxCõÿø(RõÿhXõÿ@ØXõÿ`ØYõÿ\õÿ¤¸aõÿÄØdõÿäxeõÿlõÿ(XmõÿLhrõÿltõÿèwõÿ°È{õÿÔø}õÿô(õÿ¸õÿ8õÿXÈõÿ|(õÿ8õÿ¼x¡õÿÜ¦õÿüx¬õÿ ¶õÿ@¸Îõÿ`hÒõÿØõÿ ÚõÿÀÛõÿä¨áõÿ8çõÿ$ØèõÿDxéõÿdøéõÿ8ìõÿ¨ðõÿÈõõÿèúõÿHýõÿ(öÿHXöÿhøöÿÈöÿ¨¨öÿÈöÿèöÿ¨öÿ(höÿL¸ öÿp!öÿh"öÿ¸#öÿÜØ#öÿ$öÿ$¨%öÿHX&öÿl'öÿØ'öÿ´ø(öÿØ*öÿüØ+öÿ /öÿ@H2öÿ`(6öÿh;öÿ è@öÿÀxEöÿàIöÿ¸Nöÿ 8Söÿ@èSöÿd¨TöÿhUöÿ¬VöÿÐWöÿôèWöÿøXöÿ<Zöÿ`[öÿè[öÿ¨ø\öÿÌ]öÿèh]öÿø]öÿ(^öÿH_öÿh¨_öÿø_öÿ¨¨`öÿÈØböÿèhgöÿ¸iöÿ,hköÿP¨oöÿpxvöÿ¸öÿ°öÿÐØöÿðöÿHöÿ0ø£öÿTÈ¨öÿxè²öÿx¸öÿÀø¼öÿä½öÿ¨¾öÿ,ÀöÿL8Ãöÿl¨ÅöÿXÊöÿ¬hÍöÿÌÍöÿèØÍöÿÎöÿ$ÏöÿDøÐöÿhxÓöÿÓöÿ¤¨ÕöÿÄøÜöÿä¸âöÿ(ãöÿ$¨ãöÿD8ùöÿdèûöÿ(ýöÿ¨hýöÿÄ÷ÿäX	÷ÿ÷ÿ$è÷ÿDø÷ÿh(÷ÿ¸÷ÿ¨"÷ÿÈ&÷ÿè¨)÷ÿ*÷ÿ,¸+÷ÿPh,÷ÿt8-÷ÿØ-÷ÿ¼8.÷ÿØx5÷ÿü6÷ÿè6÷ÿ@¸8÷ÿ`HE÷ÿ¸G÷ÿ¤èJ÷ÿÈK÷ÿä(K÷ÿhK÷ÿ8M÷ÿ@xM÷ÿ`¨M÷ÿ|èN÷ÿP÷ÿ¼R÷ÿÜR÷ÿüS÷ÿT÷ÿ<V÷ÿ`X÷ÿ¸X÷ÿ¤¨[÷ÿÈc÷ÿèi÷ÿp÷ÿ(èv÷ÿHØ}÷ÿhX÷ÿ¨÷ÿ¬ø÷ÿÈ÷ÿè÷ÿH÷ÿ,8÷ÿP8÷ÿpè÷ÿ8÷ÿ°÷ÿÔÈ÷ÿø÷ÿø÷ÿ@£÷ÿ`x¥÷ÿ¸±÷ÿ¤(³÷ÿÄ8½÷ÿäè¿÷ÿHÁ÷ÿ,Ç÷ÿPÈÈ÷ÿp8Ó÷ÿxÖ÷ÿ°¨×÷ÿÐ(Ø÷ÿðÚ÷ÿØÚ÷ÿ88Þ÷ÿXæ÷ÿxøè÷ÿü÷ÿ¸hý÷ÿØèý÷ÿø¨þ÷ÿÈøÿ88øÿXøÿ|øÿÈøÿ¼	øÿØH	øÿô
>øÿ¨øÿ<
øÿ`(øÿHøÿ¤¨øÿÈèøÿìèøÿ øøÿ, høÿH Xøÿh xøÿ øÿ¬ høÿÌ øÿì øÿ¡(øÿ(¡¸øÿL¡8"øÿl¡X8øÿ¡¨8øÿ¨¡9øÿÈ¡h;øÿè¡ø<øÿ¢È=øÿ0¢ø?øÿP¢ØDøÿp¢xNøÿ¢Haøÿ°¢¨øÿÔ¢Øøÿø¢øÿ£xøÿ<£¸øÿ\£øøÿ|£høÿ£¸øÿÀ£(øÿà£Xøÿ¤X øÿ$¤X¡øÿH¤x¡øÿd¤¡øÿ¤¢øÿ¤¤£øÿÈ¤è§øÿè¤¨¨øÿ¥ø¨øÿ(¥H©øÿD¥Ø©øÿh¥hªøÿ¥øªøÿ°¥x¬øÿÐ¥¨®øÿð¥±øÿ¦ø±øÿ4¦(´øÿT¦hµøÿx¦øµøÿ¦(ºøÿ¼¦H»øÿÜ¦X¼øÿü¦¾øÿ§Éøÿ<§XÊøÿ`§Ëøÿ§ØÎøÿ¤§èÑøÿÄ§8Óøÿè§Ôøÿ¨¸Ûøÿ(¨àøÿH¨àøÿd¨(àøÿ¨hàøÿ¨¨àøÿ¸¨èàøÿÔ¨(áøÿð¨háøÿ©¨áøÿ(©èáøÿD©(âøÿ`©âøÿ©åøÿ ©æøÿÄ©Øéøÿä©Xëøÿªíøÿ(ª¸ïøÿLªØóøÿlªHüøÿª8ýøÿ¬ªÈùÿÐª*ùÿðªØ*ùÿ«¨+ùÿ0«ø+ùÿL«8,ùÿh«-ùÿ«H-ùÿ¤«X.ùÿÈ«ø0ùÿì«1ùÿ¬X2ùÿ,¬83ùÿP¬4ùÿt¬È4ùÿ¬85ùÿ¬¬¸5ùÿÈ¬H6ùÿä¬(8ùÿ9ùÿ(H:ùÿHh;ùÿhx<ùÿØ=ùÿ¨¸>ùÿÌCùÿìØIùÿ®¨Qùÿ,®øfùÿL®Xjùÿl®sùÿ®¨yùÿ°®|ùÿÐ®(ùÿô®¨ùÿ¯Xùÿ4¯xùÿX¯ùÿx¯Øùÿ¯ÈùÿÀ¯¸ùÿä¯ùÿ°øùÿ,°ØùÿL°ùÿl°èùÿ°H ùÿ´°«ùÿØ°ùÿü°¨®ùÿ ±èÅùÿ@±¨Çùÿd±Êùÿ±¨Êùÿ ±¸ËùÿÀ±ØÌùÿä±¨Íùÿ²XÐùÿ$²8ÒùÿD²ØÒùÿh²8Óùÿ²XÕùÿ¤²×ùÿÄ²Øùÿè²Úùÿ³øÛùÿ,³(ßùÿL³¸ßùÿl³Øßùÿ³Xàùÿ¤³ØàùÿÀ³XáùÿÜ³âùÿ´Øâùÿ$´XäùÿD´Øåùÿd´(æùÿ´xæùÿ´Èæùÿ¸´8èùÿÜ´xèùÿü´8éùÿ µHéùÿ<µÈëùÿ\µ8õùÿ|µèøùÿµhúùÿÀµþùÿàµØúÿ¶¸úÿ ¶8úÿD¶¸úÿh¶Húÿ¶xúÿ°¶xúÿÔ¶(úÿø¶húÿ·Øúÿ0·XúÿL·Xúÿl·¨úÿ·Xúÿ¨·úÿÌ·úÿì·¸úÿ¸Øúÿ$¸úÿ@¸8úÿ\¸úÿx¸èúÿ¸Húÿ°¸ÈúÿÌ¸(úÿè¸úÿ¹Húÿ$¹HúÿH¹èúÿl¹H$úÿ¹H%úÿ¨¹x%úÿÄ¹¨%úÿà¹è'úÿº¸(úÿ$º(*úÿHºx+úÿlº¸1úÿº3úÿ°ºh3úÿÌº4úÿðº4úÿ»H5úÿ0»h8úÿP»¸:úÿp»;úÿ»<úÿ¸»¨=úÿÜ»(Aúÿü»øDúÿ¼Húÿ<¼¨Lúÿ\¼¨Múÿ¼Núÿ¤¼XOúÿÈ¼hPúÿì¼Túÿ½HXúÿ,½XúÿL½HZúÿp½cúÿ½Ødúÿ´½fúÿÔ½¸fúÿô½júÿ¾Ønúÿ4¾uúÿT¾(uúÿp¾Huúÿ¾8vúÿ°¾vúÿÌ¾wúÿð¾È}úÿ¿èúÿ0¿øúÿP¿Húÿt¿¸úÿ¿Húÿ¼¿(úÿÜ¿èúÿü¿(úÿÀHúÿ<ÀØ£úÿ\À¦úÿ|ÀØªúÿÀh¯úÿ¼À(³úÿÜÀØ¶úÿüÀ¨ºúÿÁÀúÿ<ÁÄúÿ\ÁÅúÿÁÆúÿ¤ÁÇúÿÈÁ(ÈúÿìÁHÉúÿÂhÊúÿ4ÂXËúÿXÂHÌúÿ|ÂÍúÿ ÂèÍúÿÄÂÎúÿèÂÈÏúÿÃ¨Ðúÿ0ÃXÑúÿTÃhÒúÿxÃÓúÿÃÓúÿ¸Ã8ÔúÿØÃÔúÿøÃÕúÿÄÖúÿ@ÄH×úÿ`Ä×úÿ|Äè×úÿÄØúÿ´ÄÈÙúÿÔÄÈÜúÿôÄÈÞúÿÅhßúÿ<Åxáúÿ\ÅHìúÿ|Åíúÿ ÅèôúÿÀÅúúÿàÅ(þúÿÆûÿ Æûÿ@Æûÿ\Æ¸ûÿÆûÿÆXûÿ¸Æ¨ûÿÔÆøûÿðÆHûÿÇ8ûÿ0ÇØûÿPÇhûÿpÇ¨ûÿÇØ&ûÿ°Ç(ûÿÔÇ,ûÿôÇø,ûÿÈh-ûÿ,È(.ûÿLÈø.ûÿpÈ80ûÿÈÈ1ûÿ´È¸2ûÿÔÈX3ûÿøÈ4ûÿÉX6ûÿ8É¨6ûÿTÉè6ûÿpÉè7ûÿÉ:ûÿ°É¸>ûÿÔÉøNûÿôÉ(QûÿÊSûÿ4Ê¨SûÿPÊ¨TûÿpÊXUûÿÊVûÿ¸ÊVûÿØÊ(WûÿôÊøWûÿË[ûÿ8Ë(_ûÿ\ËØaûÿ|Ë¸cûÿË(eûÿ¼ËfûÿàË¨gûÿÌ¸hûÿ ÌèiûÿDÌxkûÿdÌhnûÿÌxsûÿ¤Ì¨vûÿÈÌØ}ûÿèÌûÿÍèûÿ(ÍûÿHÍ8ûÿhÍXûÿÍ¸ûÿ¬ÍûÿÌÍûÿðÍèûÿÎ¨ûÿ0ÎûÿPÎØûÿpÎxûÿÎ¸ûÿ°ÎûÿÌÎxûÿèÎXûÿÏH£ûÿ(Ï¤ûÿHÏø¤ûÿhÏx¯ûÿÏ¨¯ûÿ¤Ï(°ûÿÄÏH°ûÿàÏx±ûÿÐX¶ûÿ(Ð¸¸ûÿHÐX½ûÿhÐ¨ÂûÿÐ8Ïûÿ¨ÐhÐûÿÌÐ¸ÒûÿìÐÕûÿÑ¸Øûÿ,ÑØÜûÿLÑßûÿlÑßûÿÑ(ßûÿ¤ÑèûÿÈÑèïûÿèÑøðûÿÒòûÿ0ÒHûûÿPÒüÿpÒøüÿÒüÿ´ÒHüÿØÒXüÿüÒhüÿ ÓHüÿ@ÓÈ üÿdÓH!üÿÓ$üÿ¬Ó¨.üÿÐÓh3üÿôÓè3üÿÔØ4üÿ4Ô(;üÿTÔ=üÿxÔH?üÿÔEüÿÀÔHGüÿäÔhJüÿÕÈLüÿ ÕøLüÿ<Õ(Nüÿ`ÕøXüÿÕYüÿ ÕèqüÿÀÕXsüÿàÕ¸tüÿÖuüÿ(ÖèuüÿDÖwüÿdÖHxüÿÖxxüÿ Öxüÿ¼ÖyüÿÜÖ¸yüÿøÖüÿ×üÿ8×xüÿX×Xüÿx×üÿ×øüÿ¼×¡üÿÜ×ø¡üÿØ8£üÿ Ø£üÿ<Ø£üÿXØ(¤üÿtØÈ¤üÿØØ¥üÿ´ØÈ¦üÿÔØx§üÿøØè¨üÿÙªüÿ<ÙH«üÿ\ÙX¬üÿÙ®üÿ Ù¸®üÿÀÙ¯üÿÜÙ¯üÿüÙÈ¯üÿÚ°üÿ8ÚÈ°üÿTÚX±üÿtÚø±üÿÚ³üÿ¸Úh´üÿØÚØ´üÿôÚHµüÿÛH·üÿ0ÛÈ¸üÿPÛºüÿpÛX½üÿÛè¿üÿ°ÛÂüÿÐÛxÄüÿðÛøÇüÿÜHÉüÿ0ÜÉüÿLÜÊüÿpÜXÍüÿÜhÐüÿ´Ü(ÓüÿØÜÔüÿüÜ¸Ôüÿ ÝXÖüÿ@ÝÛüÿ`ÝxãüÿÝìüÿ ÝxìüÿÄÝ8îüÿäÝ¸îüÿÞxôüÿ$ÞHþüÿDÞ¸ýÿdÞh
ýÿÞÈýÿ¨Þ8ýÿÈÞýÿèÞ¸ýÿßè ýÿ,ß"ýÿLß¨,ýÿlß(0ýÿßØ0ýÿ¬ßxHýÿÌßxJýÿðß¸OýÿàhQýÿ4àxTýÿXàHUýÿxà¸Zýÿàølýÿ¼àqýÿààxýÿáýÿ áèýÿ<á( ýÿXáè¢ýÿxá¸©ýÿáHªýÿ¼á¨ªýÿàá8¬ýÿâè¬ýÿ$â8¯ýÿDâH²ýÿhâØ²ýÿâ´ýÿ¬â8¹ýÿÌâ½ýÿìâH¿ýÿãÌýÿ0ãØÜýÿPãhÞýÿpãØÞýÿã¨ßýÿ¬ã¨àýÿÐãXâýÿðãÈíýÿäXþÿ0äøþÿTäxþÿxäXþÿä(þÿ¸äøþÿØä¨þÿüäHþÿå¸þÿ@åH
>þÿ`åØþÿåHþÿ åÈþÿÀåþÿàåøþÿæxþÿ(æÈþÿHæHþÿlæ&þÿæ-þÿ¬æè3þÿÌæH8þÿðæ(<þÿç(=þÿ0ç8>þÿTçEþÿtçSþÿçè\þÿ´ç^þÿØç¸bþÿøçdþÿènþÿ8èuþÿXè8þÿxèXþÿèþÿ¸èþÿØèXþÿøè(þÿéÈþÿ<éhþÿ\éèþÿéhþÿ éXþÿÄéÈþÿäéèþÿêxþÿ,êØþÿLêèþÿlêþÿêH¡þÿ°êØ¦þÿÐê(©þÿðêø¬þÿëH®þÿ8ëh®þÿTëø®þÿpëX°þÿë±þÿ´ëh²þÿØë²þÿôë³þÿìØµþÿ4ì8¶þÿTìh·þÿxìèºþÿìØ½þÿ¼ì¸ÀþÿÜìØÃþÿíèÅþÿ$íÈþÿHíxËþÿhíÈÍþÿíÒþÿ¨íX×þÿÈízR|tðÿAB
FF <äðÿAB
FI `àðÿUAB
IF[ðÿ?AB
D  @ðÿAB
INHÄ<ðÿGAB
FFälðÿ>AB
 ðÿ5AB
FFN $¬ðÿAB
FFNH¨ðÿAB
FFhðÿAB
 ðÿAB
INI ¨ ðÿaAB
INH ÌT ðÿäAB
FNFð !ðÿOAB
A T!ðÿAB
INH 00"ðÿ£AB
INHT¼#ðÿZAB
F tü%ðÿAB
FIx'ðÿ+AD
´'ðÿ±AB
FÔ,)ðÿAB
Fô*ðÿ$AB
I¬-ðÿEAB
D0à-ðÿZAD
F L$.ðÿAB
Of p/ðÿ*AB
FFN 0ðÿAB
FFN¸2ðÿ©AB
I Ø4ðÿUAB
INJüÔ5ðÿ}AB
FF46ðÿ¯AB
F <Ä7ðÿÂAB
FFN`p8ðÿeAB
FN À8ðÿ)AB
IS ¤Ì9ðÿÏAB
IFN Èx<ðÿíAB
AJ ìD?ðÿAB
INS °?ðÿAB
FIN 4,@ðÿùAB
LNZXAðÿ8AB
Dt,Aðÿ]AB
FQlAðÿAB
FN ´ÜBðÿzAB
OaF Ø8DðÿAB
Ri ü4EðÿAB
FFN  °EðÿAB
dFYD,FðÿIAB
D``Fðÿ9AB
A|FðÿRAB
DÈFðÿJAB
D´üFðÿ@AB
DÐ Gðÿ2AB
AìDGðÿjAB
A GðÿAB
FI,Iðÿ9AB
AH¸IðÿHAB
AdìIðÿ@AB
DJðÿgAB
B `Jðÿ9AB
A¼JðÿPAB
AØ¸JðÿHAB
DôìJðÿBAD
D  KðÿAB
FFN 4KðÿAB
FFNXLðÿ}AB
ExxLðÿMAB
FQ¨LðÿRAB
FQ¸èLðÿAB
ÔÜLðÿAB
ðÐLðÿAB
	ÔLðÿAB
(	ÈLðÿAB
D	ÌLðÿAB
`	ÀLðÿAB
|	ÄLðÿSAB
D	MðÿsAB
D´	lMðÿwAB
OÔ	ÌMðÿ[AB
Dð	NðÿÂAB
D
>ÄNðÿAB
D(
>HOðÿoAB
FFH
>OðÿAB
FFh
>PðÿAB
FF 
>PðÿGAB
FI ¬
>ÄQðÿ¢AB
FI Ð
>PRðÿAB
BFô
>LSðÿ=AB
FlXðÿ-AB
D0Xðÿ-AB
DLXðÿ-AB
Dh¨Xðÿ-AB
D¼Xðÿ-AB
D ÐXðÿ-AB
D¼äXðÿÌAB
FFÜYðÿAB
DøZðÿAB
D|Zðÿ-AB
D0Zðÿ-AB
DL¤Zðÿ-AB
Dh¸ZðÿPAB
DìZðÿ`AB
D  0[ðÿAB
FI Ä¬[ðÿAB
FI è(\ðÿAB
FFN
$]ðÿ¸AB
F,
Ä_ðÿ'AB
F L
Ôbðÿ]AB
FI p
dðÿáAB
FL
ÜdðÿSAB
D°
 eðÿùAB
FÐ
jðÿLB
ì
jðÿxAM
hjðÿ+AB
A$|jðÿSAM
 @Àjðÿ`AB
FNFdüjðÿbAB
ILoðÿ\AB
F¤pðÿlAB
C ÄÜqðÿÇAB
FKèrðÿ4AB
F¨wðÿ3AB
A$Ìwðÿm
>AB
FDðÿbAB
Idlðÿ¥AB
OüðÿAB
I ¤|ðÿ¢AB
FIÈðÿ(AB
F èðÿDAB
FFND¡ðÿûAB
F ,$§ðÿAB
INMP §ðÿôAB
O p©ðÿAB
FIü¬ðÿSAB
F ´<±ðÿAB
INMØ¸±ðÿôAB
O ø³ðÿAB
FI ·ðÿ³AB
BF@ ¹ðÿÎAB
C`PÁðÿAB
O ÐÂðÿ
AB
FI¤¼ÃðÿäAB
OÄÅðÿAB
FäÇðÿOAB
F<ËðÿÏAB
R $ìËðÿ0AB
INE HøÌðÿ=AB
AG lÏðÿAB
Ot ×ðÿAB
FI ´|×ðÿ7AB
LFØÚðÿAB
EøÛðÿâAB
F èÝðÿûAB
FI<ÄÞðÿJAD
FF\ôÞðÿDAB
F|$áðÿåAB
Iôâðÿ¡AB
F ¼äðÿÞAB
FI à@åðÿ3AD
OF \æðÿlAB
LF (¨çðÿAB
OELéðÿCAB
AhÈéðÿ§AB
F XíðÿAB
FXF¬DîðÿôAB
LÌ$ñðÿÆAB
FìÔöðÿAB
CÄ÷ðÿPAB
F,ôùðÿÁAB
FL¤úðÿAB
F l$ûðÿAD
FIûðÿAB
O°ýðÿÌAB
FÐÀýðÿAB
Lð þðÿKAB
DTþðÿzAB
F ,´ÿðÿüAB
AG PñÿAB
FItñÿÓAB
FLñÿñAD
O´,ñÿGAB
DÐ`ñÿ¢AB
IððñÿAB
Eà	ñÿ
>AG
,Ô	ñÿAB
HÈ	ñÿWAB
Dd
>ñÿAB
FüñÿyAB
F ¤\ñÿÖAB
INLÈñÿõAB
FèøñÿúAB
OØñÿ·AB
F(xñÿ5AB
DñÿAB
` ñÿAB
|¤ñÿAB
ñÿAB
´ñÿAB
ÐñÿAB
ìñÿAB
xñÿAB
$|ñÿAB
@ñÿAB
\ñÿAB
xxñÿAB
lñÿAB
°`ñÿAB
ÌTñÿAB
èHñÿAB
LñÿAB
 PñÿGAB
<ñÿPAB
AX¸ñÿAB
At<ñÿPAB
ApñÿPAB
D¬¤ñÿXAB
DÈèñÿXAB
Dä,ñÿPAB
D`ñÿXAB
D¤ñÿ9AB
A8Èñÿ2AB
ATìñÿ]AB
Dp0ñÿSAB
FFpñÿ{AB
D ¬ÔñÿAB
FIÐÀñÿAB
F ð°ñÿAB
FI !ñÿpAB
FNF8è!ñÿiAB
EX8*ñÿèAB
F x+ñÿAB
FFN t+ñÿAB
FFNÀà+ñÿAB
FàP2ñÿ?AB
Düt2ñÿXAB
D ¸2ñÿÅAB
AG <d7ñÿAB
AI`Ð7ñÿÅAB
F 9ñÿ½AB
FI ¤;ñÿ9AB
L[F È8<ñÿêAB
FQFì=ñÿÅAB
F ´DñÿAB
FNF00GñÿðAB
B PHñÿÁAB
FQFt¬JñÿÊAB
F\Lñÿ=AB
C´|NñÿÀAB
IÔbñÿAB
ð bñÿ%AB
 4bñÿ±AB
FI0Ðbñÿ®AB
FP`dñÿÌAB
FpfñÿAB
F gñÿÙAB
FI ´Ìgñÿ·AB
FIØhhñÿK
>AB
C ørñÿêAB
FQE dsñÿaAB
I < ´xñÿÎAB
FIN ` `yñÿÄAB
LR zñÿçAB
I¤ ÜñÿpAB
DÀ 0ñÿKAB
Cà `ñÿ$AB
F!pñÿAB
F !pñÿEAB
F@! ñÿAB
F`! ñÿÃAB
I !Ð ñÿ.AB
FNF¤!Ü¡ñÿÜAB
FÄ!¥ñÿ×AB
Fä!\©ñÿ\AB
D" ©ñÿ\AB
D"ä©ñÿ§AB
F<"tñÿAB
F\"ä°ñÿ7AB
F |"´ñÿ%AB
F[  "µñÿAB
F[ Ä"¶ñÿAB
F[ è"·ñÿõAB
F[ #ä·ñÿÑAB
F[0# ¸ñÿ6AB
CP#ÀºñÿLAB
C p#ð¼ñÿÔAB
ITM#¬¾ñÿÈAB
C´#\ÀñÿöAB
I Ô#<ÄñÿAB
RNUø#¨Éñÿ;AB
J$ÈÉñÿ;AB
J8$èÉñÿ	AB
V X$ØÊñÿAB
PQ |$ÔËñÿ^AB
PQ $Íñÿ4AB
F À$0ÏñÿºAB
Ia ä$ÌÏñÿAB
FFT %¸ÐñÿsAB
BF ,%ÓñÿüAB
RFP%ðÔñÿ½AB
Ip%çñÿÅAB
I%@íñÿ;AB
F°%`ññÿÕAB
I Ð% òÿ¯AB
LNLô%¬òÿ¬AB
I &<
>òÿÙAB
FX8&ø
>òÿ±AB
FX&òÿAB
t&òÿaAB
B&ìòÿAB
 °&ðòÿAB
OF Ô&l
òÿAB
OF ø&è
òÿAB
FI'TòÿzAB
F<'´òÿAB
O\'4òÿÙAB
F|'ôòÿAB
F'dòÿpAB
F¼'´òÿAB
FÜ'´òÿ%AB
I ü'Ä$òÿ°AB
F[ (P'òÿ]AB
O@()òÿ
	AB
C`(2òÿ.AB
D |(2òÿêAB
FTE  (`3òÿAB
BFÄ(L4òÿÍAB
Fä(ü5òÿ÷AB
I)ÜDòÿAB
C $)\EòÿùAB
FIH)8GòÿBAB
d)lGòÿ¡AB
F )üHòÿAB
IT[¨)hJòÿ AB
 Ä)lJòÿdAB
FIè)¸Kòÿ8AB
D *ÜKòÿrAB
FMP (*8MòÿvAB
FI L*Mòÿ;AB
IE p*°OòÿµAB
AJ *L^òÿAB
LF ¸*H_òÿÉAB
FQFÜ*ô_òÿ5AB
O ü*aòÿÕAB
LF  +ÐbòÿyAB
FI D+,dòÿAB
FIh+(eòÿEAB
O+XfòÿAB
C¨+ÈhòÿAB
Ä+ÌhòÿAB
à+ÀhòÿAB
ü+ÄhòÿXAB
,iòÿFAB
 4,<iòÿAB
FLX,¸iòÿSAB
FFx,øiòÿAB
D,\jòÿPAB
D°,jòÿ|AB
DÌ,ôjòÿ|AB
D è,XkòÿöAB
FI -4lòÿÎAB
FI 0-àlòÿËAB
FI T-mòÿÖAB
FI x-HnòÿÁAB
LF -ônòÿAB
ACF À-àoòÿLAB
FKä-qòÿJAB
F.<ròÿ&AB
F$.LuòÿµAB
F D.ìwòÿrAB
FIh.HzòÿùAB
F .(òÿ¼AB
II ¬.ÄòÿTAB
FIÐ.òÿ«AB
Ið.òÿØAB
I/Pòÿå
>AB
I 0/ òÿAB
FIT/òÿAB
Ft/òÿn	AB
F /Ü¢òÿyAB
FI ¸/8¤òÿyAB
FIÜ/¥òÿj AB
Iü/äÅòÿúAB
O0ÄÇòÿAB
80ÈÇòÿDAB
T0üÇòÿAB
p0ÈòÿAB
0ÈòÿSAB
IO¬0DÈòÿ3AB
DÈ0hÈòÿrAB
O è0ÈÈòÿµAB
LF1dÉòÿÎAB
O,1ÊòÿSAB
DH1XÊòÿSAB
Dd1ÊòÿSAB
D1àÊòÿRAB
B 1 ÌòÿìAB
OÀ1ðÌòÿAB
FFà1`ÍòÿdAB
Aü1´ÍòÿÀAB
LQ2TÎòÿ|AB
L<2´Îòÿ²AB
DX2XÏòÿÉAB
D t2ÐòÿEAB
FI28Ñòÿ|AB
F¸2ÓòÿAB
F Ø2Öòÿ1AB
AG ü2´Úòÿ$AB
IFP 3ÀÛòÿAB
F @30ÞòÿøAB
BFd3íòÿcAB
O3\ïòÿÕAB
F ¤3õòÿ]AB
FIÈ3Xöòÿ(AB
ä3löòÿAB
4`öòÿfAB
IG 4°öòÿ§AB
R@4@÷òÿßAB
O`4øòÿAB
O4ùòÿAB
F 4ûòÿpAB
F À4PóÿËAB
FI ä4üóÿÓAB
FI 5¸óÿÛAB
FI ,5tóÿëAB
FI P5@óÿËAB
FI t5ìóÿÓAB
FI5¨óÿAB
L¸5óÿ¬AB
FF Ø5¨óÿÌAB
OF ü5Tóÿ3AB
IQH 6póÿPAB
D<6¤óÿ!AB
F\6´óÿAB
x6¨óÿ@AB
I6Èóÿæ
AB
I¸6+óÿAB
F Ø6-óÿAB
LSü6.óÿAB
F 7t2óÿiAD
IF@7À2óÿ-AD
D\7Ô2óÿIAB
Dx73óÿFAB
F788óÿmAB
C¸7>óÿ\AB
F Ø7È?óÿlAB
FIü7AóÿXAB
D8XAóÿAB
D48ÜAóÿ¹	AB
IT8|KóÿAB
Ft8|NóÿyAB
F8ÜQóÿHAB
D °8RóÿÚAB
BIÔ8ÌWóÿ_AB
A ð8XóÿZAB
FLN9LXóÿ,AB
O49\YóÿÑAB
F T9\óÿiAB
AGx9h^óÿ:AB
I9ióÿRAB
F ¸9ÈqóÿyAB
FI Ü9$sóÿAB
FI:tóÿBAB
:ÄtóÿÎAB
F<:tvóÿDAB
F\:¤wóÿÕAB
O|:dzóÿ}AB
C:Ä{óÿ5AB
I ¼:äóÿ{AD
FIà:@óÿxAB
Dü:¤óÿÝAB
O ;dóÿ5AB
FI @;óÿAB
FId;üóÿÏAB
F;¬óÿAB
 ;°óÿ1AB
D¼;ÔóÿFAB
DØ;óÿJAB
D ô;<óÿ²AB
FFF <ØóÿÒAB
FFF <<óÿkAB
FQQ `<àóÿzAB
FW <<óÿâAB
FFN ¨<óÿ
>AB
FFFÌ<ôóÿAD
è<èóÿAD
=Üóÿ
>AG
 =Ðóÿ
>AG
<=Äóÿ}AB
C\=$óÿ
AB
I|=óÿAB
 =óÿRAB
FQF¼=DóÿDAB
GFÜ=tóÿ<AB
FNü=óÿAB
A>óÿAB
A 4>óÿÐAB
ACLX>Hóÿ:AB
F x>hóÿ"AB
AG >tóÿAB
FNFÀ>ðóÿ8AB
F à>óÿAB
F[?| óÿ'AB
F $?¡óÿ=AB
FQF H?¨¢óÿAB
IFV l?£óÿkAB
LF?`¤óÿAB
O°?Ð§óÿ(AB
Ì?ä§óÿåAD
è?¸¨óÿÂAB
F @hªóÿaAB
FFQ ,@´ªóÿAB
LF P@0«óÿîAB
FIt@ü«óÿ$AB
F@óÿ%AB
A°@ óÿ=AD
DÌ@DóÿDAB
Fì@t¯óÿ?AB
DA¯óÿôAB
F (Ax±óÿìAB
FFGLAD´óÿAB
F lAÄµóÿñAB
INLA ¶óÿnAB
C°Að·óÿÕAB
C ÐA°¸óÿÆAB
L]FôA\»óÿ%AB
F Bl¼óÿAB
FQF8BØ¼óÿ/AB
F XBè½óÿpAB
FFN|B4¾óÿAAB
ABh¾óÿ8AB
´B¾óÿAB
IÔBÜóÿäAB
FôBÜÜóÿcAD
FC,ÞóÿAB
0C ÞóÿAB
LC$Þóÿ<AB
hCHÞóÿZAB
DCÞóÿáAD
O¤C\ßóÿXAB
DÀC ßóÿoAD
L àCðàóÿ¹AB
II Dáóÿ>AB
LT(D¨ãóÿAB
O HDäóÿËAB
FFT lDDåóÿ¼AB
IEDàåóÿÊAB
F °DìóÿÊAB
FIÔD<íóÿAB
FôD<îóÿAB
FE¬òóÿ¸AB
E4ELóóÿ¦AB
DPEàóóÿAAB
F pE÷óÿ7AB
FIE,ùóÿAB
I´E¬úóÿAB
I ÔEôÿÊAB
FIøEÈôÿÍAB
F FxôÿÒAB
FI<F4ôÿUAB
R \Ft	ôÿAB
FNFF`
>ôÿÏAB
F F
ôÿÌAB
FÀFÀôÿAB
FàF°ôÿCAB
FGàôÿ1AB
F  GôÿAB
F[ DG|ôÿAB
FXF hGxôÿ AB
F[ Gôôÿ¸AB
F[ °Gôÿ²AB
F[ ÔG,ôÿØAB
F[ øGèôÿÒAB
F[ H¤ôÿ¶AB
LF@H@ôÿAB
O`HÀôÿØAB
FH ôÿeAB
F  HÐ$ôÿAB
FIÄH<&ôÿ	AB
IäH,*ôÿAB
I0*ôÿAB
I$*ôÿAB
8I(*ôÿXAB
DTIl*ôÿPAB
DpI *ôÿ|AB
D I+ôÿAB
PNF °Ip+ôÿ<AB
PQ ÔI-ôÿ±AB
PQøI(.ôÿAB
OJ0ôÿ{AB
V 8Jø3ôÿAB
PNF\Jd4ôÿÖAB
V |J$7ôÿ<AB
PQ J@9ôÿ%AB
FÀJP:ôÿµAB
CàJð<ôÿAB
FK`AôÿGAB
D KAôÿ×AB
FI@KPCôÿAB
\KTCôÿpAB
FF |K¤CôÿÚAB
LF K`Eôÿ+AB
F ÀKpFôÿ¤AB
FL äKüFôÿAB
BFLxHôÿcAB
F(LÈIôÿ3AB
CHLèLôÿAG
dLìLôÿAB
F LlPôÿyAB
FI¨LÈQôÿuAB
I ÈL(^ôÿyAB
FIìL_ôÿçAB
FMTaôÿÐAB
F,McôÿAB
F LMtcôÿ·AD
LFpMdôÿxAB
BMpdôÿ«AB
F °MeôÿAB
FQFÔMüeôÿyAB
FôM\iôÿAB
FI N¼iôÿWAB
FI 8Nøiôÿ¡AB
IE \NjôÿôAB
LNLN`kôÿFAB
DNkôÿMAB
D¸NÈkôÿMAB
DÔNükôÿFAB
DðN0lôÿFAB
DOdlôÿAD
(OXlôÿ3AB
DO|lôÿAD
`Oplôÿ¯AB
FOnôÿ^AB
ODnôÿ6AB
¸OhnôÿjAB
FNØO¸nôÿjAB
FNøOoôÿJAB
FNP8oôÿJAB
FN8PhoôÿJAB
FN XPoôÿAB
FI|PpôÿAB
FFPpôÿAB
FF¼PqôÿAB
FFÜPqôÿAB
FFüPôqôÿAB
FF Qdrôÿ^AB
LF @Q sôÿtAB
FIdQüsôÿAB
EQütôÿAB
FF¤Q|uôÿAB
FFÄQüuôÿ§AB
OäQwôÿYAB
BRÌxôÿMAB
F $Rü{ôÿYAB
IQ HR8}ôÿîAB
FLlRôÿAB
I RôÿAB
AG°RðôÿâAB
FÐRÀôÿe
>AB
F ðRôÿ½AB
AGS¬¢ôÿAAB
F4SÜ¤ôÿAB
F TSÌ¦ôÿµAB
AG xShªôÿrAB
AG SÄ®ôÿAB
AG ÀS0µôÿ=AB
AG äSL¹ôÿEAB
AG TxÀôÿ¥AB
AG ,TÏôÿ=AB
AGPT ÕôÿeAB
B pTpÕôÿ÷AB
PXTLÖôÿ@AB
F´TlØôÿAB
FÔTìÝôÿAB
F ôTìàôÿAB
OFUháôÿAB
F 8Uhèôÿ±AG
FNF\UéôÿAB
F|UôíôÿAB
O UtïôÿÝAB
OE ÀU0óôÿÕAB
RHäUìöôÿ&AB
F Vüøôÿ,AB
FL(VúôÿAB
FHVxüôÿOAB
F hV¨õÿ¹AB
FIVDõÿ_AB
F¬VõÿAB
FÌVt	õÿ5AB
IìVõÿAB
F W õÿnAB
BI0WP&õÿ
>AB
IPWP0õÿ AB
IpWPHõÿ¤AB
FWàKõÿ%AB
F°WðQõÿeAB
C ÐW@SõÿûAB
FIôWTõÿAB
FXZõÿAB
F4X`õÿAB
FTXaõÿAB
EtXbõÿ{AB
E Xlbõÿ<AB
FNF¸XdõÿÞAB
FØXHhõÿpAB
FøXmõÿAB
FYrõÿ/AB
F8Yuõÿ=AB
FXY8xõÿÆAB
FxYè{õÿAB
FYhõÿÎAB
F¸YõÿÞAB
FØYØõÿÞAB
FøYõÿrAB
FZøõÿAB
F 8ZxõÿµAB
F[ \ZõÿEAB
FXF Z@õÿÊAB
FXF ¤Zìõÿ×AB
FXF ÈZ¨õÿ¦AB
F[ ìZ4õÿ»AB
FXF [Ðõÿ¬AB
F[ 4[\õÿAB
FXF X[Xõÿ©AB
F[ |[äõÿµAB
F[  [õÿµAB
F[ Ä[õÿAB
FXF è[õÿAB
FXF \õÿµAB
FNF0\° õÿ/AB
FP\À£õÿ=AB
Fp\à¦õÿÖAB
F\ ªõÿ=AB
F°\À¯õÿsAB
FÐ\ µõÿAB
Fð\¹õÿAB
F]½õÿ"AB
F0]Âõÿ|AB
F P]ðÆõÿ¬AB
F[ t]|Çõÿ»AB
FXF ]ÈõÿµAB
F[ ¼]´Èõÿ¯AB
F[ à]@ÉõÿæAB
FXF ^ÊõÿàAB
FXF (^ÈÊõÿAB
FXF L^´ËõÿAB
FXF p^°ÌõÿéAB
F[ ^|ÍõÿÝAB
FXF ¸^8ÎõÿAB
FXFÜ^$ÏõÿAB
ø^(ÏõÿJAB
FN_XÏõÿAB
FF8_ÈÏõÿAB
FFX_8ÐõÿAB
FFx_¨ÐõÿAB
FF_ÑõÿIAB
FF¸_HÑõÿ¬AB
EØ_ØÑõÿ0AB
Fø_èÓõÿAB
F `XØõÿHAB
FI <`Úõÿ¬AB
FI``Üõÿ@AB
I`0àõÿÆAB
F `àæõÿ5
>AB
FÀ`ñõÿÇAB
Fà`°õõÿHAB
Faà÷õÿ3AB
F aÿõÿ+AB
F @aöÿ¥AB
AG daöÿÌAB
AG aHöÿ
>AB
AG ¬aD"öÿAB
AG Ða°'öÿ}AB
AG ôa,öÿAB
FNF b,öÿAB
PX<bt-öÿlAB
F\bÄ.öÿAB
F|bÄ1öÿbAB
Ob4öÿ¦AB
F¼b¤8öÿAB
IÜb;öÿAB
øb;öÿCAB
DcÌ;öÿ¶AB
E4cl<öÿêAB
F Tc<=öÿdAB
IIQxc>öÿuAG
Icè@öÿAB
´cì@öÿAB
UÔcÜBöÿEAB
IôcJöÿ½AB
Id¬OöÿlAB
O4düOöÿrAD
LTd\PöÿAB
I tdÌeöÿªAB
AGdXhöÿ;AB
E¸dxiöÿ4AB
DÔdiöÿAB
IôdqöÿNAB
IeLuöÿ-AB
U4e\{öÿ]AB
F TeöÿAB
FNFxeöÿ#AB
FeöÿAB
F¸eöÿÖAB
FØeÈöÿæAB
FøeöÿAB
F föÿåAB
FXF <fdöÿAB
FXF `f`öÿ¯AB
F[ fìöÿÄAB
FXF ¨föÿAB
F[ÌföÿUAB
 èfXöÿ3AB
gEgtöÿAB
FF ,gäöÿÚAB
FIPg  öÿÃAB
OpgP¢öÿAB
I gÀ®öÿpAB
FL ´g±öÿ)AB
LQØg´öÿAB
ôg´öÿ AB
h ´öÿ6AB
D ,hD´öÿÌAB
IEPhðµöÿ;AB
Jph¶öÿ+AB
Ah$¶öÿ3AB
F¬hD·öÿAB
FÌhÄ¸öÿuAB
Fìh$ºöÿvAB
FIiºöÿ{AB
D (ièºöÿAG
BF LiT¼öÿøAB
FI pi0¾öÿjAB
FLi|¿öÿ©AB
O ´iÀöÿìAB
FIØiØÂöÿQAB
FøiÊöÿtAB
FjxÐöÿuAB
I8jØÖöÿÖAB
FXjÝöÿïAB
F xjhäöÿxAB
BIjÄêöÿNAB
F¼jôìöÿEAB
Øj(íöÿAB
E øjíöÿAB
FQJkîöÿ0AB
F <kïöÿåAB
AG`kàðöÿòAB
CkÀôöÿ¯AB
R kPõöÿGAB
F ÀkööÿFAB
BF äk¬÷öÿ4AB
BF lÈùöÿÇAB
AJ ,ltüöÿSAB
FIPl°ÿöÿAB
I pl°÷ÿZAB
LElì	÷ÿ>AB
I´l÷ÿlAB
FÔl\÷ÿ
>AB
U ôlL!÷ÿ¦AB
IFN mØ#÷ÿWAB
IZH <m%÷ÿµAB
OH`m°*÷ÿ¿AB
CmP,÷ÿj
>AB
I m 6÷ÿ<AB
FÀmÀ9÷ÿ+AB
FàmÐ:÷ÿwAB
I n0;÷ÿêAD
FI $nü<÷ÿ²AB
IEHn=÷ÿ_AB
FhnØ@÷ÿLAB
InI÷ÿhAB
F¨nXK÷ÿAB
IÈnX^÷ÿFAB
Oèn_÷ÿyAB
Loè_÷ÿ¿AB
F(o`÷ÿAB
FHob÷ÿkAB
F hoØc÷ÿAAB
FIoe÷ÿAB
F¬oth÷ÿ°AB
FÌoj÷ÿ4AB
èo(j÷ÿ4AB
 pLj÷ÿHAB
FI (pxk÷ÿAB
LF Lpdl÷ÿbAB
FI pp°m÷ÿAB
LFpn÷ÿAB
F ´pq÷ÿ]AB
FI ØpØr÷ÿ?AB
INHüpôs÷ÿúAB
FIqÔt÷ÿAB
FI<qÄu÷ÿcAB
DXqv÷ÿçAB
IN xqèv÷ÿAB
FIqäx÷ÿAB
E¼qdy÷ÿDAB
FFÜqy÷ÿ0AD
Küq¤z÷ÿôAB
Dr{÷ÿAB
FQ 8rø{÷ÿAB
FI\rd}÷ÿqAB
F|rÄ÷ÿAB
RrÄ÷ÿBAB
¸rø÷ÿpAB
MØrH÷ÿIAB
O ørx÷ÿAB
IE sä÷ÿÇAB
FK@s÷ÿ-AB
C`s ÷ÿÚAB
Is`¢÷ÿ	AB
I sà«÷ÿÃAB
I Às¾÷ÿU!AB
II äsÌß÷ÿ&AB
FQJ tØà÷ÿ&AB
FQJ,täá÷ÿdAB
LLt4â÷ÿ7AB
RltTã÷ÿ3AB
Rttè÷ÿmAB
O ¬tÄé÷ÿPAB
FNFÐtðé÷ÿiAB
Fðt@í÷ÿ&AB
F uPû÷ÿüAB
FI 4u,ü÷ÿüAB
FIXuý÷ÿ AB
tuý÷ÿ AB
 uý÷ÿaAB
FQF ´u\ý÷ÿøAB
FIØu8þ÷ÿÓAB
I øuøøÿ±AB
BCvøÿBAB
A8vÈøÿBAB
A TvüøÿAB
FNF xvhøÿAB
FI vÔøÿAB
FIÀv@øÿsAB
Fàv øÿ*AB
Ow°øÿ[AB
F  wð
>øÿðAB
FIDw¼øÿ!AB
F dwÌ
øÿ@AB
FI wèøÿAD
FNF¬wTøÿ,AB
IÌwdøÿAB
FìwdøÿAB
FxTøÿ¡AB
L,xäøÿAB
F LxÄ!øÿCAB
FI pxð"øÿªAB
FIx|#øÿÎAB
F´x,'øÿAB
O Ôx*øÿDAB
FIøxH+øÿÁAD
Cyø+øÿ°AB
U8y3øÿKAB
FXy¸7øÿAD
ty¬7øÿ
>AG
y 7øÿ2AB
A¬yÄ7øÿ2AB
AÈyè7øÿ2AB
Aäy8øÿ2AB
Az08øÿ2AB
AzT8øÿ2AB
A8zx8øÿ2AB
ATz8øÿ2AB
ApzÀ8øÿlAB
Ez9øÿpAB
F °z`;øÿAB
INFÔzÌ<øÿ3AB
Fôzì?øÿzAB
F {LAøÿ¦AB
FI 8{ØBøÿ£AB
LF\{dEøÿAB
F|{dIøÿgAB
I{´QøÿèAB
L ¼{Røÿ
>AB
BIà{ð\øÿ¸"AB
I|øÿIAB
A |ÄøÿÁAB
FFN@|pøÿMAB
D\|¤øÿ6AB
Dx|ÈøÿßAB
FQ|øÿ#AB
A ´|øÿAB
FQF Ø|øÿAB
FTü|øÿAB
FT}øÿµAB
B <}$øÿÚAD
INF `}àøÿØAD
FNF}øÿ¨AD
A }0øÿkAD
A¼}øÿxAD
AØ}èøÿAD
Aô}\øÿ×AB
I ~øÿðAB
FI8~èøÿ%AB
CX~øøÿ AB
Fx~øøÿAB
F~èøÿ[AB
F ¸~(øÿÚAB
FNFÜ~äøÿÏAB
Fü~øÿMAB
IÄøÿËAB
I<t£øÿOAB
I\¤¸øÿSAB
O|ä»øÿÀAB
C ÄøÿAB
LWÀðÊøÿáAB
F àÀÍøÿAB
IW,ÐøÿAB
B$ÐøÿAB
F DÓøÿAB
FIhÔøÿAB
O ÖøÿGAB
LE ¬4×øÿåAB
IE ÐÚøÿëAD
KE ôÌÚøÿÒAB
FI ÛøÿTAB
FI<ÄÜøÿÖAB
F\ßøÿ7
AB
F |¤ìøÿÊAB
FI  PíøÿXAB
FI Äïøÿ8AB
BI è¨úøÿòAB
FI üøÿAB
BF0ýøÿ=AB
I P ùÿ·AB
FIt<ùÿÙAB
IüùÿAB
°ùÿAB
E ÐðùÿAB
LIôìùÿÂAB
Rùÿ¥AB
F4,ùÿÖAB
O TìùÿAB
FIxh ùÿTAB
D¬ ùÿAB
F´¬"ùÿ¾AB
F ÔL$ùÿdAB
FIø%ùÿxAB
F ø&ùÿãAB
AG<Ä(ùÿ*AD
F\Ô+ùÿAB
J|D,ùÿAB
H,ùÿ|AB
D´¬,ùÿ|AB
DÐ-ùÿ|AB
D ìt-ùÿ¤AB
FL .ùÿÎAB
FI4¬.ùÿqAB
OT0ùÿyAB
Otl1ùÿPAB
D 1ùÿPAB
D¬Ô1ùÿPAB
D È2ùÿbAB
FIìT3ùÿ>AB
FF t3ùÿ¾AB
FI04ùÿAB
L4ùÿvAB
Fld6ùÿl	AB
C´?ùÿ£AB
C ¬DCùÿyAB
FIÐ Dùÿ¨AB
Fð0Hùÿ¼
>AB
IÐRùÿ×AB
F 0VùÿyAB
FI TìWùÿ~AB
FI xHXùÿAB
FI ´Xùÿ%AB
OF ÀÀYùÿúAB
LF äZùÿ¢AB
LR([ùÿ9AB
A$L[ùÿpAB
D@ [ùÿrAB
D\\ùÿòAB
O|ä\ùÿJAB
D]ùÿ¤AB
F ¸¨^ùÿ/AB
FIÜ´_ùÿüAB
Iüaùÿ,AB
¨aùÿAB
4¬aùÿ,AB
PÀaùÿ,AB
lÔaùÿFAG
bùÿXAB
D¤LbùÿXAB
DÀbùÿxAB
DÜôbùÿ_AB
Dø8cùÿ_AB
D|cùÿ¹AB
FF 4dùÿòAB
FI XødùÿAB
FI|teùÿZAB
F´jùÿøAP
¸kùÿ+AB
Ô¬kùÿ)AB
ðÀkùÿ>AB
I àmùÿÇAB
FFN 4nùÿoAB
AG XØoùÿEAB
FI|qùÿ6AB
I $wùÿEAB
FIÀPxùÿ[AB
D ÜxùÿAB
FIyùÿvAB
O pyùÿ¼AB
O@zùÿAB
R`}ùÿGAB
I @ùÿÔAB
FNF ¤üùÿíAB
F[ ÈÈùÿAB
F[ìÄùÿtAB
F$ùÿÄAB
F,ÔùÿAB
FLTùÿAB
F lDùÿöAB
FXF  ùÿãAB
F[ ´ìùÿ³AB
PQ ØùÿAB
SFütùÿAB
Fôùÿ5AB
F<ùÿ9AB
FF \4ùÿ´AB
FQFÐùÿ7	AB
F  ð¥ùÿIAB
IIÄ§ùÿ,AB
Oä,¨ùÿ®AB
L¼¨ùÿÇAB
F$l¬ùÿEAB
FD°ùÿ=AB
Id¼¶ùÿAB
°¶ùÿAB
 ´¶ùÿáAB
FIÀ·ùÿGAB
D Ü´·ùÿAB
FI ¸ùÿ£AB
F °¾ùÿAB
C@°ÀùÿAB
I ` ÆùÿIAB
II ÌÌùÿiAB
FNF ¨ÏùÿAB
F[ÌÏùÿÑAB
FìDÔùÿ¾AB
Fä×ùÿ4AB
F,ÜùÿAB
FLßùÿAB
Fltãùÿ¿AB
Fæùÿ4AB
F¬4êùÿAB
FÌ¤îùÿ¾AB
FìDòùÿ¢AB
FÔõùÿÆAB
F,ùùÿbAB
FLÔþùÿqAB
F l4úÿôAB
FXF úÿôAB
FXF ´ìúÿçAB
FXF Ø¸úÿAB
F[ ü4úÿAB
FXF  0úÿAB
FXF D,úÿíAB
FXF høúÿçAB
FXF Ä	úÿÍAB
FXF °p
>úÿÇAB
FXF Ôúÿ¦AB
F[ ø¨úÿ+AB
F[ ´úÿÝAB
FXF @p
úÿ¬AB
F[ dü
úÿAB
FXF èúÿAB
FXF¬äúÿAD
ÈØúÿAB
FNèXúÿHAB
J úÿAB
FI ,ôúÿòAB
FIPÐúÿ!AB
Opàúÿ@AB
DúÿSAB
D¨HúÿAB
DÄÌúÿ>AB
FäìúÿùAB
F ÌúÿòAB
AG (¨úÿAB
FFIL$úÿAB
FlúÿÆ
>AB
F Ä&úÿ¸AB
FQF°`'úÿÕAB
IÐ /úÿAB
Ið 4úÿAB
R 8úÿáAB
I0ð<úÿkAB
IP@NúÿAB
 l4NúÿAB
FI0PúÿAAB
A¬dPúÿAAB
AÈPúÿAAB
AäÌPúÿAAB
AQúÿAAB
A 4QúÿåAB
FI@RúÿAB
IF`RúÿAB
EðSúÿ;AB
R Uúÿ%
>AB
F À _úÿ¥AB
XLä¬`úÿÿAB
IdúÿbAB
D àdúÿbAB
A<4eúÿ¶AB
F \ÔeúÿËAB
F[fúÿ6AB
C   gúÿAB
INJÄiúÿïAB
F äÜiúÿAB
IIXjúÿ¾AB
E(øjúÿ<AB
FHmúÿNAG
dLmúÿ?AB
pmúÿóAG
FF PnúÿAB
F ÀàpúÿAB
FIäÜtúÿ5AB
Iüúÿ+AB
F$úÿXAB
FDLúÿAG
`Púÿ÷AB
F 0úÿ¥AB
FFN ¤¼úÿÀAB
FFNÈXúÿqAB
FFè¸úÿAB
D ,úÿÍAB
FHN(ØúÿAB
F HXúÿAB
IFlÄúÿ¬AB
OTúÿÚAB
F¬úÿfAB
O ÌdúÿâAB
FIð0úÿAB
O úÿAB
E 0úÿ-AB
FITúÿAB
OtúÿãAB
OÜ¡úÿAB
O ´Ì¦úÿ%AB
FIØØ©úÿ%AB
Føè°úÿ?AB
F³úÿÌAB
O8¸´úÿ%AB
FXÈ·úÿAB
F xÈ¹úÿAB
FFNÄºúÿQAB
O¼¾úÿÊAB
O Ü´ÀúÿAB
FFN ÁúÿPAB
O ÐÄúÿ¿AB
O@pÇúÿâAB
F`@Éúÿ2AB
O `ÍúÿAB
FNF¤ÜÍúÿ5AB
AÀÎúÿVAB
DÜDÎúÿVAB
DøÎúÿÙAB
F HÐúÿïAB
F8 Ôúÿ5AB
OX 8ÕúÿcAB
Lx Õúÿs
>AB
I èßúÿ#AD
´ üßúÿ|AB
EÔ \àúÿAG
 ð `àúÿ*AB
FI ¡láúÿßAB
II8¡(æúÿ`AB
FX¡hèúÿAB
Ix¡èìúÿBAB
I¡òúÿAB
I ¸¡þúÿ+AB
FIÜ¡ÿúÿAAB
Fü¡ÄûÿÚAB
I¢ûÿAB
F<¢ûÿ AB
I\¢ûÿ/AB
F|¢
ûÿAD
¢
ûÿAD
 ´¢|
ûÿe	AB
AGØ¢ÈûÿMAB
C ø¢øûÿAB
PQ £äûÿAB
PQ@£Ðûÿ:	AB
F`£ð(ûÿAAB
F£ 0ûÿTAB
F  £`4ûÿAB
PQ Ä£Ì4ûÿ½	AB
AG è£h>ûÿAB
PQ ¤T?ûÿAB
PQ0¤@@ûÿÛ	AB
F P¤Jûÿ}AB
AG t¤\MûÿsAB
PQ ¤¸MûÿEAB
AG ¼¤äPûÿ
>AB
AG à¤ÐZûÿµAB
AG¥l_ûÿtAB
L$¥Ì_ûÿêAB
FD¥`ûÿPAB
I d¥ÌfûÿÒAB
LF ¥hûÿ2AB
FI ¬¥¤jûÿ=AB
INV Ð¥ÀpûÿµAB
LFô¥\rûÿAB
F¦\uûÿZAG
0¦ wûÿ(AB
 L¦´wûÿ)AB
FNNp¦ÀxûÿÄ
>AB
I¦pûÿ AB
DC°¦ðûÿFAB
CÐ¦ ûÿbAB
C ð¦pûÿWAB
FQM §¬ûÿÇAB
FQF8§XûÿZAB
DT§ûÿ-AD
IOt§¬ ûÿ-AD
E§¼¡ûÿ/AD
D°§Ð¡ûÿAB
Ì§Ä¡ûÿ÷AB
Cì§¤¢ûÿ*AB
D¨¸¢ûÿËAB
I(¨h¸ûÿAB
FH¨X¼ûÿßAB
Fh¨¾ûÿÑAB
F ¨Ø¿ûÿµAB
BF¬¨tÂûÿÒAB
FÌ¨4ÆûÿAB
F ì¨4ÉûÿÒAB
ACL©ðÉûÿ6AB
F0©ËûÿCAB
AL©DËûÿ
>AG
h©8ËûÿAG
D©¬ËûÿAB
A  ©0Ìûÿ
AG
FUÄ©ÍûÿìAG
FR ä©ìÍûÿ¯AD
FI ªxÎûÿeAG
FFN,ªÄÏûÿ!AG
FRLªÔÐûÿ+AG
FR lªäÑûÿAB
FFNªÐÒûÿ«AB
FU°ª`Ôûÿ¯AB
BÐªðÔûÿCAB
Aìª$ÕûÿqAB
B«Õûÿ2AB
D(«¨Õûÿ¾AB
OH«HÖûÿ;AB
Dd«lÖûÿAB
E«ÜÖûÿAB
E ¤«\×ûÿAB
LFÈ«ÈØûÿ×AB
Cè«ÙûÿnAB
D¬ÜÙûÿnAB
D ¬0ÚûÿýAB
F@¬ÜûÿwAB
F`¬pÝûÿÆAB
F¬ ßûÿ¾AB
F ¬ÀáûÿAB
FÀ¬0äûÿ®AB
Fà¬ÀæûÿÞAB
FèûÿxAB
F àëûÿNAB
E@íûÿ?AB
 \4íûÿAB
FL íûÿ:AB
F  Àðûÿ
>AB
BF Ä¬óûÿ½AB
AG èHöûÿØAB
FNE ®÷ûÿ¢AB
FI0®÷ûÿAB
EP®ùûÿ¹AB
Fp®°ýûÿ`AB
F®ðüÿAB
F °®püÿ^AB
FIÔ®¬üÿ¾AB
Oô®Lüÿ{AD
FT¯¬üÿ»AB
I4¯LüÿÉ	AB
IT¯üüÿe
>AB
I t¯L*üÿ¢AB
OH¯Ø.üÿXAB
C¸¯2üÿnAB
FØ¯h9üÿØAB
F ø¯(=üÿAB
BI°¤>üÿ#AB
O<°´AüÿAB
F\°´Büÿ
>AB
I|°4MüÿAG
I°PüÿAB
AH¼°$QüÿAB
I Ü°¤hüÿÿAB
IF±jüÿ3AB
O  ± oüÿ°AB
AG D±,qüÿAB
AGh±tüÿÊAB
AC ±ÈtüÿeAB
AJ¬±züÿ<AB
I Ì±4üÿAB
BFð± üÿmAB
I²p¯üÿAB
I0²`¾üÿSAB
L²¤¾üÿ@AB
Dh²È¾üÿµAB
F²hÁüÿÂAB
F ¨²ÈüÿAD
FNF Ì²Èüÿ[AB
FI ð²ÀÈüÿAB
FI³,Êüÿ¬AB
FF4³¼ÊüÿGAB
C T³ìÌüÿAB
LH x³ØÏüÿAB
FNF³DÐüÿ©AB
O¼³ÔÑüÿ¨AB
FÜ³dÖüÿßAB
F ü³$Úüÿ+AB
LE ´0Üüÿ²AB
I@´ÐèüÿÈAB
I`´ùüÿAB
C´ðúüÿnAB
D´DûüÿÂAB
O ¼´ôûüÿôAB
FIà´Ðüüÿ®AB
Fµ`þüÿkAB
I µ°	ýÿAB
I @µ ýÿAB
FI dµýÿyAB
FIµøýÿÙAB
O¨µ¸ýÿÐAB
FÈµh!ýÿÊAB
O èµ"ýÿ¤AB
FI¶¤"ýÿAD
E ,¶$#ýÿgAB
FIP¶p#ýÿAB
Op¶à$ýÿAB
R¶P&ýÿdAB
F°¶ )ýÿzAB
FÐ¶.ýÿMAB
F ð¶00ýÿÛAB
FW ·ì1ýÿ|AB
FNF8·H2ýÿLAB
R X·x4ýÿ}AB
FT|·Ô4ýÿ;AB
I·ô?ýÿýAB
I¼·ÔFýÿUAB
I Ü·MýÿUAB
BI¸PQýÿÕAB
C ¸UýÿýAB
F @¸ðUýÿ
AB
FKd¸ÜVýÿ_AB
I¸^ýÿ
AB
I¤¸|kýÿÅ	AB
I Ä¸,uýÿAB
BFè¸¨výÿ-AB
F¹¸zýÿÐAB
F(¹h|ýÿ
>AB
IH¹XýÿèAB
Ch¹(ýÿ®	AB
I¹¸ýÿAB
C¨¹¸ýÿ¤AD
EÈ¹HýÿAB
Fè¹8ýÿ2AB
F ºXýÿÈAB
FQF,ºýÿAB
FLº¤ýÿAB
C lº§ýÿsAB
FIº`¨ýÿAB
L °ºÀ¨ýÿãAB
FXFÔº©ýÿoAB
FX ôºÜ©ýÿAB
FNF »ØªýÿAB
FI<»D«ýÿYAB
F\»ýÿ
>AB
R |»t¯ýÿAB
LE »p±ýÿ7AB
IÀ»¶ýÿAB
Ià»¼ýÿDAB
F ¼0¾ýÿÃAB
RF $¼ÜÁýÿEAB
FQMH¼ÃýÿAD
d¼ÃýÿAD
G¼ÃýÿZAB
I  ¼ÀÄýÿ$AB
LcL Ä¼ÌÅýÿÙAB
I`Fè¼Æýÿ,AB
D½ÆýÿyAB
B$½üÆýÿ½AB
FD½Éýÿ\AG
FG d½ÜÉýÿ(AB
FYP ½èÊýÿAB
O_F¬½DÎýÿáAB
FÌ½ÑýÿÔAB
F ì½ÔÓýÿAB
O\F ¾ÐÖýÿAB
FNF 4¾¼Øýÿ#AB
FNFX¾ÈÚýÿ`AB
Cx¾ÞýÿDAB
F¾8àýÿ½AB
F¸¾ØäýÿÅAB
FØ¾éýÿAB
AÿÿÿÿÿÿÿÿV^¼c
^^-^ <^@O^V^<^O^a^bn^^^ ¨^@¸^V^O^Í^×^ì^ ö^@__+_5_G_Q_b_ w_@3^__§_´_Á_Ê_ Ø_:eGeXefeye e@e§e±e¿eÍeÜe èe@øe
>ff&f2f?fVf cf@qfff¢f±f½fÈf Òfâfífúfgg  g@,g?gTg`ghgvggjjP^o~¥¹ÊÚîÿ @$5?HTam{ @© ´@¾ÉÚèòþ@/BM^m ~@ ±ÆÖì @.AR a@t®¼Óå@÷ÏÝCScl^rz Ì@æ½¦ ¯@¼ÌÜè±ÔºÞºçºV^¼còº ^3^ <^@O^¿¿¿#¿,¿ 4¿@A¿J¿V^<^O^ì)ì6ì DìRìcìpììì@¢ì²ìÁìÓìæìûì@íº~æ½Ïy×Berkeley DBpðÀ Ð@0ph»¶Ê¶Ø¶·ìo
XEõþÿo|´(
>d·hn !ÌNd>hþÿÿoä=ÿÿÿoðÿÿox3úÿÿoàøh2pBpRpbprppp¢p²pÂpÒpâpòpqq"q2qBqRqbqrqqq¢q²qÂqÒqâqòqrr"r2rBrRrbrrrrr¢r²rÂrÒrâròrss"s2sBsRsbsrsss¢s²sÂsÒsâsòstt"t2tBtRtbtrttt¢t²tÂtÒtâtòtuu"u2uBuRuburuuu¢u²uÂuÒuâuòuvv"v2vBvRvbvrvvv¢v²vÂvÒvâvòvww"w2wBwRwbwrwww¢w²wÂwÒwâwòwxx"x2xBxRxbxrxxx¢x²xÂxÒxâxòxyy"y2yByRybyryyy¢y²yÂyÒyâyòyzz"z2zBzRzbzrzzz¢z²zÂzÒzâzòz{{"{2{B{R{b{r{{{¢{²{Â{Ò{â{ò{||"|2|B|R|b|r|||¢|²|Â|Ò|â|ò|}}"}2}B}R}b}r}}}¢}²}Â}Ò}â}ò}~~"~2~B~R~b~r~~~¢~²~Â~Ò~â~ò~"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò"2BRbr¢²ÂÒâò  " 2 B R b r   ¢ ² Â Ò â ò ¡¡"¡2¡B¡R¡b¡r¡¡¡¢¡²¡Â¡Ò¡â¡ò¡¢¢"¢2¢B¢R¢b¢r¢¢¢¢¢²¢Â¢Ò¢â¢ò¢££"£2£B£R£b£r£££¢£²£Â£Ò£â£ò£¤¤"¤2¤B¤R¤b¤r¤¤¤¢¤²¤Â¤Ò¤â¤ò¤¥¥"¥2¥B¥R¥b¥r¥¥¥¢¥²¥Â¥Ò¥â¥ò¥¦¦"¦2¦B¦R¦b¦r¦¦¦¢¦²¦Â¦Ò¦â¦ò¦§§"§2§B§R§b§r§§§¢§²§Â§Ò§â§ò§¨¨"¨2¨B¨R¨b¨r¨¨¨¢¨²¨Â¨Ò¨â¨ò¨©©"©2©B©R©b©r©©©¢©²©Â©Ò©â©ò©ªª"ª2ªBªRªbªrªªª¢ª²ªÂªÒªâªòª««"«2«B«R«b«r«««¢«²«Â«Ò«â«ò«¬¬"¬2¬B¬R¬b¬r¬¬¬¢¬²¬Â¬Ò¬â¬ò¬"2BRbr¢²ÂÒâò®®"®2®B®R®b®r®®®¢®²®Â®Ò®â®ò®¯¯"¯2¯B¯R¯b¯r¯¯¯¢¯²¯Â¯Ò¯â¯ò¯°°"°2°B°R°b°r°°°¢°²°Â°Ò°â°ò°±±"±2±B±R±b±r±±±¢±²±Â±Ò±â±ò±²²"²2²B²R²b²àµEÀ³lllibsasldb.so.2.0.22.debug]*9B.shstrtab.note.gnu.build-id.gnu.hash.dynsym.dynstr.gnu.version.gnu.version_r.rel.dyn.rel.plt.init.text.fini.rodata.eh_frame_hdr.eh_frame.ctors.dtors.jcr.data.rel.ro.dynamic.got.got.plt.data.bss.gnu_debuglinkôô$öÿÿo'(´(´(`S0||d·8ÿÿÿox3x3l
>Eþÿÿoä=ä=T	d>d>h]	ÌNÌN !
>fìoìo0appPBlp²p²èrXEXExEE(( ¨m¨mô.ô¾````¦``« ` `Ø ¸øhøhØÁÐiÐiÆhnhnÏ  ¼ ÕÜÜÚÜ üégÁ.`..lÁ
advanced.html4eehÁAUTHORSiÁCOPYINGjÁNEWSkÁREADMEvÁ programming.html03004e4emÁappconvert.htmlnÁcomponents.htmloÁgssapi.htmlpÁ
>index.htmlqÁinstall.htmlrÁmacosx.htmlsÁmechanisms.htmltÁoptions.htmluÁ
plugprog.htmlxÁ
sysadmin.html803004ewÁ4readme.htmlzÁ windows.html;4803004e4eyÁupgrading.htmlzÁHwindows.htmlRob Siemborski <rjs3+@andrew.cmu.edu> wrote and tested the conversion
>to the SASLv2 API.
>
>Ken Murchison <ken@oceana.com> worked on the OTP, NTLM, SRP and SQL
>plugins, as well as helping to track down bugs as they appear.
>
>Rob Earhart <earhart@cmu.edu> wrote the build/installation procedure,
>wrote and tested some of the code, and provided general guidance and
>coding advice.
>
>Leif Johansson <leifj@matematik.su.se> wrote the GSSAPI plugin, with
>contributions from Sam Hartman <hartmans@fundsxpress.com>.
>
>Leandro Santi <lesanti@sinectis.com.ar> added Courier authdaemon support.
>
>Alexey Melnikov <mel@isode.com> wrote the first pass of the
>DIGEST-MD5 plugin and continues to work on it.  He also wrote
>a good deal of the current Windows support.
>
>Rainer Schoepf <schoepf@uni-mainz.de> contributed the LOGIN plugin,
>based on Tim Martin's PLAIN plugin.
>
>Simon Loader <simon@surf.org.uk> wrote the MySQL auxprop module.
>
>Rolf Braun <rbraun@andrew.cmu.edu> wrote the MacOS ports.
>
>Howard Chu <hyc@highlandsun.com> put a good deal of work into OS/390
>portability, correct building of static libraries, and a slew
>of misc. bugfixes.
>
>Tim Martin <tmartin@andrew.cmu.edu> wrote, debugged, and tested
>most of the SASLv1 code.
>
>Larry Greenfield <leg+sasl@andrew.cmu.edu> complained. a lot.
>
>Chris Newman <chris.newman@sun.com> wrote the initial version of the
>SASL API, as well as the version 2 SASL API (documented in sasl.h,
>saslutil.h, saslplug.h, and prop.h).
>
>Ryan Troll <ryan@andrew.cmu.edu> started the Windows port,
>and both Larry Greenfield and Alexey Melnikov have done more work on it.
>
>getaddrinfo.c was written by Hajimu UMEMOTO <ume@mahoroba.org>
>which is based on the IPv6 code written by KIKUCHI Takahiro
><kick@kyoto.wide.ad.jp>
>
>$Id: AUTHORS,v 1.17 2004/01/08 15:30:25 ken3 Exp $
>/* CMU libsasl
> * Tim Martin
> * Rob Earhart
> * Rob Siemborski
> */
>/* 
> * Copyright (c) 1998-2003 Carnegie Mellon University.  All rights reserved.
> *
> * Redistribution and use in source and binary forms, with or without
> * modification, are permitted provided that the following conditions
> * are met:
> *
> * 1. Redistributions of source code must retain the above copyright
> *    notice, this list of conditions and the following disclaimer. 
> *
> * 2. Redistributions in binary form must reproduce the above copyright
> *    notice, this list of conditions and the following disclaimer in
> *    the documentation and/or other materials provided with the
> *    distribution.
> *
> * 3. The name "Carnegie Mellon University" must not be used to
> *    endorse or promote products derived from this software without
> *    prior written permission. For permission or any other legal
> *    details, please contact  
> *      Office of Technology Transfer
> *      Carnegie Mellon University
> *      5000 Forbes Avenue
> *      Pittsburgh, PA  15213-3890
> *      (412) 268-4387, fax: (412) 268-7395
> *      tech-transfer@andrew.cmu.edu
> *
> * 4. Redistributions of any form whatsoever must retain the following
> *    acknowledgment:
> *    "This product includes software developed by Computing Services
> *     at Carnegie Mellon University (http://www.cmu.edu/computing/)."
> *
> * CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO
> * THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
> * AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE
> * FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
> * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
> * AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
> * OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
> */
>New in 2.1.22
>-------------
>
>* Added support for spliting big data blocks (bigger than maxbuf)
>  into multiple SASL packets in sasl_encodev
>* Various sasl_decode64() fixes
>* Increase canonicalization buffer size to 1024 bytes
>* Call do_authorization() after successful APOP authentication
>* Allow for configuration file location to be configurable independently
>  of plugin location (bug # 2795)
>* Added sasl_set_path function, which provides a more convenient way
>  of setting plugin and config paths. Changed the default
>  sasl_getpath_t/sasl_getconfpath_t callbacks to calculate
>  the value only once and cache it for later use.
>* Fixed load_config to search for the config file in all directories
>  (bug # 2796). Changed the default search path to be
>  /usr/lib/sasl2:/etc/sasl2
>* Don't ignore log_level configuration option in default UNIX syslog
>  logging callback
>* (Windows) Minor IPv6 related changes in Makefiles for Visual Studio 6
>* (Windows) Fixed bug of not setting the CODEGEN (code generation option)
>  nmake option if STATIC nmake option is set.
>* Several fixed to DIGEST-MD5 plugin:
>  - Enable RC4 cipher in Windows build of DIGEST-MD5
>  - Server side: handle missing realm option as if realm="" was sent
>  - Fix DIGEST-MD5 to properly advertise maxssf when both DES and RC4
>    are disabled
>  - Check that DIGEST-MD5 SASL packet are no shorter than 16 bytes
>* Several changes/fixed to SASLDB plugin:
>  - Prevent spurious SASL_NOUSER errors
>  - Added ability to keep BerkleyDB handle open between operations
>    (for performance reason). New behavior can be enabled
>    with --enable-keep-db-open.
>* Better error checking in SQL (MySQL) auxprop plugin code
>* Added support for HTTP POST password validation in saslauthd
>* Added new application ("pluginviewer") that helps report information
>  about installed plugins
>* Allow for building with OpenSSL 0.9.8
>* Allow for building with OpenLDAP 2.3+
>* Several quoting fixes to configure script
>* A large number of other minor bugfixes and cleanups
>
>New in 2.1.21
>-------------
>* Fixes DIGEST-MD5 server side segfault caused by the client not sending
>  any realms
>* Minor Other bugfixes
>
>New in 2.1.20
>-------------
>* Fixes to cram plugin to avoid attempting to canonify uninitialized data.
>* NTLM portability fixes.
>* Avoid potential attack using SASL_PATH when sasl is used in a setuid 
>  environment.
>* A trivial number of small bugfixes.
>
>New in 2.1.19
>-------------
>* Fixes to saslauthd to allow better integration with realms (-r flag to
>  saslauthd, %R token in LDAP module)
>* Support for forwarding of GSSAPI credentials
>* SQLite support for the SQL plugin
>* A nontrivial number of small bugfixes.
>
>New in 2.1.18
>-------------
>* saslauthd/LDAP no longer tagged "experimental"
>* Add group membership check to saslauthd/LDAP
>* Fix Solaris 9 "NI_WITHSCOPEID" issue
>* Fix missing "getaddrinfo.c" and other distribution problems
>* Significant Windows enhancements
>* A large number of other minor bugfixes and cleanups
>
>New in 2.1.17
>-------------
>* Allow selection of GSSAPI implementation explicitly (--with-gss_impl)
>* Other GSSAPI detection improvements
>* Now correctly do authorizaton callback in sasl_checkpass()
>* Disable KERBEROS_V4 by default
>* Continued Win32/Win64 Improvements
>* Minor Other bugfixes
>
>New in 2.1.16-BETA
>------------------
>* Significantly improved Win32 support
>* Writable auxprop support
>* Expanded SQL support (including postgres)
>* Significantly improved documentation
>* Improved realm/username handling with saslauthd
>* Support for modern automake and autoconf
>
>New in 2.1.15
>-------------
>* Fix a number of build issues
>* Add a doc/components.html that hopefully describes how things
>  interact better.
>
>New in 2.1.14
>-------------
>* OS X 10.2 support
>* Support for the Sun SEAM GSSAPI implementation
>* Support for MySQL 4
>* A number of build fixes
>* Other minor bugfixes
>
>New in 2.1.13
>-------------
>* Add a configure option to allow specification of what /dev/random to use.
>* Addition of a saslauthd credential cache feature (-c option).
>* Unification of the saslauthd ipc method code.
>* Fix a number of autoconf issues.
>* A significant number of fixes throughout the library from Sun Microsystems.
>* Other minor bugfixes.
>
>New in 2.1.12
>-------------
>* Distribute in Solaris tar (not GNU tar format)
>* Fix a number of build/configure related issues.
>
>New in 2.1.11
>-------------
>* Add the fastbind auth method to the saslauthd LDAP module.
>* Fix a potential memory leak in the doors version of saslauthd.
>* NTLM now only requires one of LM or NT, not both.
>* Fix a variety of Berkeley DB, LDAP, OpenSSL, and other build issues.
>* Win32 support compiles, but no documentation as of yet.
>
>New in 2.1.10
>-------------
>* Further DIGEST-MD5 DES interoperability fixes.  Now works against Active
>  Directory.
>* Fix some potential buffer overflows.
>* Misc. cleanups in the saslauthd LDAP module
>* Fix security properties of NTLM and EXTERNAL
>
>New in 2.1.9
>------------
>* Include missing lib/staticopen.h file.
>
>New in 2.1.8
>------------
>* Support for the NTLM mechanism (Ken Murchison <ken@oceana.com>)
>* Support libtool --enable-shared and --enable-static
>  (Howard Chu <hyc@highlandsun.com>)
>* OS/390 Support (Howard Chu <hyc@highlandsun.com>)
>* Berkeley DB 4.1 Support (Mika Iisakkila <mika.iisakkila@pingrid.fi>)
>* Documentation fixes
>* The usual round of assorted other minor bugfixes.
>
>New in 2.1.7
>------------
>* Add SASL_AUTHUSER as a parameter to sasl_getprop
>* Allow applications to require proxy-capable mechanisms (SASL_NEED_PROXY)
>* Performance improvements in our treatment of /dev/random
>* Removal of buggy DIGEST-MD5 reauth support.
>* Documentation fixes
>* Assorted other minor bugfixes.
>
>New in 2.1.6
>------------
>* Security fix for the CRAM-MD5 plugin to check the full length of the
>  digest string.
>* Return of the Experimental LDAP saslauthd module.
>* Addition of Experimental MySQL auxprop plugin.
>* Can now select multiple auxprop plugins (and a priority ordering)
>* Mechanism selection now includes number of security flags
>* Mac OS X 10.1 Fixes
>* Misc other minor bugfixes.
>
>New in 2.1.5
>------------
>* Remove LDAP support due to copyright concerns.
>* Minor bugfixes.
>
>New in 2.1.4
>------------
>* Enhancements and cleanup to the experimental LDAP saslauthd module
>  (Igor Brezac <igor@ipass.net>)
>* Addition of a new sasl_version() API
>* Misc. Bugfixes
>
>New in 2.1.3-BETA
>-----------------
>* Significant amount of plugin cleanup / standardization.  A good deal of code
>  is now shared between them. (mostly due to Ken Murchison <ken@oceana.com>)
>* DIGEST-MD5 now supports reauthentication.  Also has a fix for DES
>  interoperability.
>* saslauthd now supports the Solaris "doors" IPC method
>  (--with-ipctype=doors)
>* Significant GSSAPI fixes (mostly due to Howard Chu <hyc@highlandsun.com>)
>* Auxprop interface now correctly deals with the * prefix indicating 
>  authid vs. authzid.  (May break some incompatible auxprop plugins).
>* We now allow multiple pwcheck_method(s).  Also you can restrict auxprop
>  plugins to the use of a single plugin.
>* Added an experimental saslauthd LDAP module (Igor Brezac <igor@ipass.net>)
>* Removed check for db3/db.h
>* Misc. documentation updates.  (Marshall Rose, and others)
>* Other misc. bugfixes.
>
>New in 2.1.2
>------------
>* Mostly a minor-bugfix release
>* Improved documentation / cleanup of old references to obsolete
>  pwcheck_methods
>* Better error reporting for auxprop password verifiers
>
>New in 2.1.1
>------------
>* Many minor bugfixes throughout.
>* Improvements to OTP and SRP mechanisms (now compliant with
>  draft-burdis-cat-srp-sasl-06.txt)
>* API additions including sasl_global_listmech, and a cleaner handling of
>  client-first and server-last semantics (no application level changes)
>* Minor documentation improvements
>
>New in 2.1.0
>------------
>* The Cyrus SASL library is now considered stable.  It is still not backwards
>  compatible with applications that require SASLv1.
>* Minor API changes occured, namely the canon_user callback interface.
>* saslauthd now preforks a number of processes to handle connections
>* Many bugfixes through the entire library.
>
>New in 2.0.5-BETA
>-----------------
>* THIS IS A BETA-QUALITY RELEASE THAT IS NOT INTENDED FOR PRODUCTION USE.
>  IT *WILL BREAK* ANY APPLICATION EXPECTING THE SASLv1 API.
>* Improved performance of security layers in KERBEROS_V4, GSSAPI, and DIGEST.
>* This release includes an OTP plugin that requires libopie.
>* SRP plugin now in alpha stage.
>* Includes many significant bugfixes throughout the library.
>
>New in 2.0.4-BETA
>-----------------
>* THIS IS A BETA-QUALITY RELEASE THAT IS ONLY INTENDED FOR USE BY
>  DEVELOPERS WHOSE APPLICATIONS MAKE USE OF THE CYRUS SASL LIBRARY.
>  IT *WILL BREAK* ANY APPLICATION EXPECTING THE SASLv1 API.
>* This release now includes Mac OS 9 and Mac OS X support.
>* Significant new features include 
>  * DES and 3DES Encryption should now be working for DIGEST-MD5
>  * Improved configuration system
>  * Improved documentation (now includes plugin writers guide)
>  * Many other bugfixes (see ChangeLog)
>
>New in 2.0.3-BETA
>-----------------
>* THIS IS A BETA-QUALITY RELEASE THAT IS ONLY INTENDED FOR USE BY
>  DEVELOPERS WHOSE APPLICATIONS MAKE USE OF THE CYRUS SASL LIBRARY.
>  IT *WILL BREAK* ANY APPLICATION EXPECTING THE SASLv1 API.
>* This library should be fairly close to the core features that will be
>  released in a final version of Cyrus SASLv2.  It very likely has bugs.
>* Major new features included in this release:
>  - The glue code now correctly handles client-send-first and server-send-last
>    situations based on what the protocol and mechanism each support.
>  - The sasldb code has been extracted from the main library and now resides
>    in a separate libsasldb.la that is available at build time.
>  - SASLdb now supports multiple auxiliary properties, though as distributed
>    only userPassword is implemented and used.
>  - Much improved configure checking for various items, including
>    Berkeley DB, Kerberos, and GSSAPI.
>  - Better (more standard) handling of realms in DIGEST-MD5.
>  - A new Plugin Programmer's guide.
>  - IPv6 support.
>  - Error reporting now works in the GSSAPI plugin.
>* See the ChangeLog for a more detailed list of changes.
>
>New in 2.0.2-ALPHA
>------------------
>* THIS IS AN ALPHA-QUALITY RELEASE THAT IS ONLY INTENDED FOR DEVELOPERS
>  WHOSE APPLICATIONS MAKE USE OF THE CYRUS SASL LIBRARY.  
>* This release is intended to show developers that use Cyrus SASL what
>  direction we are planning on taking the library so that they can make
>  plans to migrate their applications accordingly
>* Major new features included in this release:
>  - Ability to compile a static library including all mechanisms.  This
>    means lower memory usage and faster mechanism loading time, but
>    is not for everyone (or even many people). See doc/advanced.html,
>    as well as the '--with-staticsasl' configure flag.
>  - Man pages should now all be present and are close to being correct.
>  - Can now build libsfsasl and the smtptest program (using the --with-sfio
>    configure flag)
>  - Reverted to the v1 entry points for mechanisms, to allow v1 mechanisms
>    to fail loading cleanly.
>  - Auxprop and canon_user plugins can now load from DSOs
>  - Java code now compiles (but is not well tested, or up to date with the
>    current Java API draft)
>  - Error handling and use of sasl_errdetail has been fleshed out and
>    should now work in most cases.
>* Still Coming:
>  - Cleanup of the client-send-first and server-send-last situation
>  - Error reporting in GSSAPI plugin
>  - Move the sasldb code out of the main library and into plugins and
>    utilities only.
>
>New in 2.0.0-ALPHA
>------------------
>* THIS IS AN ALPHA-QUALITY RELEASE THAT IS ONLY INTENDED FOR DEVELOPERS
>  WHOSE APPLICATIONS MAKE USE OF THE CYRUS SASL LIBRARY.  
>* This release is intended to show developers that use Cyrus SASL what
>  direction we are planning on taking the library so that they can make
>  plans to migrate their applications accordingly
>* This release implements the SASLv2 API.
>  Some of the major improvements in the API include:
>  - Memory management is now sane (whoever allocates the memory is responsible
>    for freeing it)
>  - Auxiliary Property plugin support (ability to interface with directory
>    services as part of authentication)
>  - Username canonification plugin support
>  - Improved error reporting (not fully implemented in this release)
>  - Database support has been simplified.  We now maintain only a single
>    store of plaintext passwords that is shared by all supplied plugins
>    (using the auxiliary property interface).
>  The new API is more fully documented in the header files sasl.h, saslplug.h
>  saslutil.h, and prop.h.  The man pages, programmers guide, and system
>  administrators guide have also been rewritten to deal with the new API.
>* There is still a good amount of work to be done, and as this code is alpha
>  quality, it has bugs, known and unknown.  Please either use our bugzilla at
>  http://bugzilla.andrew.cmu.edu, or email cyrus-bugs@andrew.cmu.edu with
>  questions, comments, or bug reports.
>  - Most notably, the Java bindings have not been converted to work with
>    the new API, and thus will not compile successfully.
>  - The current development branch with this source is in our
>    cvs repository as the "sasl-v2-rjs3" branch of the "sasl" collection.
>    (see http://asg.web.cmu.edu/cyrus/download/anoncvs.html for more info)
>$Id: README,v 1.32 2002/04/06 03:44:52 rjs3 Exp $
>
>This is the Cyrus SASL API implentation. It can be used on the client
>or server side to provide authentication and authorization services.
>See RFC 2222 for more information.
>
>The latest version is available at:
>ftp://ftp.andrew.cmu.edu/pub/cyrus-mail
>
>There's a mailing list for Cyrus SASL.  Subscribe by sending a message
>to majordomo@lists.andrew.cmu.edu with the body "subscribe
>cyrus-sasl". The mailing list is available via anonymous IMAP at
>imap://cyrus.andrew.cmu.edu/archive.cyrus-sasl or via the web at
>http://asg.web.cmu.edu/archive/mailbox.php3?mailbox=archive.cyrus-sasl.
>
>If you are looking to port SASLv1 applications to SASLv2, please see
>doc/appconvert.html
>
>Bugs can be searched/reported at: http://bugzilla.andrew.cmu.edu
>
>DOCUMENTATION
>--------------
>Please see doc/index.html for the remainder of the documentation.
><HTML><head>
><TITLE>Cyrus SASL Library -- Advanced Usage</TITLE>
></head>
><body>
><h1>Cyrus SASL library, version 2.0</h1>
><h2>Notes for Advanced Usage of libsasl</h2>
>
><h3>Using Cyrus SASL as a static library</h3>
>As of v2.0.2-ALPHA, Cyrus SASL supports the option to compile all of the
>supported mechanisms and glue code into a single static library that may
>be linked into any application.  In practice, this saves memory by avoiding
>the need to have a jump table for each process's reference into the shared
>library, and ensures that all the mechanisms are loaded when the application
>loads (thus reducing the overhead of loading the DSOs).<P>
>
>However, this is not a recommended procedure to use in general.  It loses
>the flexibility of the DSOs that allow one to simply drop in a new mechanism
>that even currently-running applications will see for each new connection.
>That is, if you choose to use the static version of the library, not only
>will you need to recompile the library each time you add a mechanism (provided
>the mechanisms even support being compiled staticly), but you will need to
>recompile every application that uses Cyrus SASL as well.<P>
>
>However, if you are sure you wish to use a static version of Cyrus SASL,
>compile it by giving <tt>configure</tt> the <tt>--enable-static</tt> option.
>This will compile <b>both</b> a dynamic and a static version.  Then, whenever
>an application links to libsasl, it will also need to explicitly pull in
>any dynamic libraries that may be needed by Cyrus SASL.  Most notably, these
>might include the GSSAPI, Kerberos, and Database libraries.  To avoid compiling
>the dynamic version, pass <tt>--disable-shared</tt>.<P>
>
><hr>
>Back to the <A href=index.html>index</a>
>
></body>
><HTML>
><HEAD>
><TITLE>Converting Applications from SASLv1 to SASLv2</TITLE>
><BODY>
><H1>Application Conversion Guide for SASLv2</H1>
>
><p>This documents our conversion experience with Cyrus IMAPd, an application
>that uses almost every part of SASL, so it should give a good idea what caveats
>need to be looked for when one is converting an application which uses SASLv1
>to use SASLv2.</P>
>
><P>The major changes in the SASLv2 API have to do with memory management.
>That is, the rule "If you allocate it, you free it" is now enforced.  That
>means that if the application allocates something (for example, an interaction
>or callback response), it must free it.  Likewise, the application does
>NOT free anything handed to it by the SASL library, such as responses
>given by sasl_client_step or sasl_decode.</P>
>
><UL>
><LI>Tips for both clients and servers:<P>
><UL>
><LI>Change configure scripts to search for libsasl2 and include files
>prefixed with sasl/ (sasl/sasl.h, sasl/saslutil.h, etc)</LI>
><LI><tt>sasl_decode64</tt> now takes an
>additional parameter that is the size of the buffer it is passed.</LI>
><LI>External authentication properties are no longer handled by a
><tt>sasl_external_properties_t</tt>.  Instead you make 2 separate calls to
><tt>sasl_setprop.</tt>
>One with SASL_SSF_EXTERNAL to tell the SASL library what SSF is being
>provided by the external layer. The other sets SASL_AUTH_EXTERNAL to indicate
>the authentication name.</LI>
><LI>
><tt>sasl_getprop</tt> now returns its value in a <tt>const void **</tt>
></LI>
><LI><tt>sasl_encode</tt> and <tt>sasl_decode</tt> now return a constant output buffer, which
>you do not need to free (it is only valid until the next call for this sasl_
>conn_t, however)</LI>
><LI>The SASL_IP_REMOTE and SASL_IP_LOCAL properties are now SASL_IPLOCALPORT
>and SASL_IPREMOTEPORT and take strings instead of sockaddrs. These strings
>may also be passed to the sasl_[client/server]_new functions.  They
>are in one of the following formats:
><UL>
><LI>a.b.c.d;p (IPv4, with port)</LI>
><LI>e:f:g:h:i:j:k:l;p (IPv6, with port)</LI>
><LI>e:j:k:l;p (IPv6, abbreviated zero fields, with port)</LI>
></UL></LI>
><li>Error handling and reporting is different. All of the functions that used
>to return a "reply" string no longer do.  Now you should (always) check
><tt>sasl_errdetail</tt>.  Callbacks MUST likewise use <tt>sasl_seterror</tt>
>instead of setting their (now nonexistent) reply parameter.</li>
><li>Be very careful about your handling of maxoutbuf.  If you claim that
>you can only read 4096 bytes at a time, be sure to only pass at most
>that much at a time to the SASL library!</li>
></UL></LI>
>
><LI>Tips for clients:</LI>
><OL>
><LI>In <tt>sasl_client_new</tt> you can now pass ip address strings as
>parameters 3 and 4 instead of calling setprop later on sockaddr's.
>This is preferred but not required (not passing them by either method disables
>mechs which require IP address information).   You might find the iptostring()
>function in utils/smtptest.c to be useful for this.  If the protocol supports
>the server sending data on success you should pass SASL_SUCCESS_DATA as a
>flag.</LI>
><LI><tt>sasl_client_start</tt> loses the 3rd "secret" parameter.
>Also, NULL clientout and clientoutlen indicates that the protocol does not
>support client-send-first.  A NULL return value indicates that there is no
>first client send. (as opposed to an empty string, which indicates that
>the first client send is the empty string).</LI>
><LI>
>Both <tt>sasl_client_start</tt> and <tt>sasl_client_step</tt> now take
>const clientout parameters that you are no longer responsible for freeing
>(it is only valid until the next call for this <tt>sasl_conn_t</tt>, however)
></LI>
><LI>When interactions and callbacks happen you are responsible for freeing
>the results.</LI>
></OL></LI>
>
><LI>Tips for Servers:</LI>
><OL>
><LI>SASL_SECURITY_LAYER flag no longer exists, whether or not to use a
>security layer is solely determined by the security properties information,
>namely, the <tt>maxbufsize</tt> member of the
><tt>sasl_security_properties_t</tt></LI>
><LI><tt>sasl_server_new</tt> now can take ip address strings.</li>
><LI><tt>sasl_checkpass</tt> no longer has a "reply" parameter.  There
>are also considerably fewer possible values for the pwcheck_method
>option (now only auxprop, saslauthd, authdaemond, and pwcheck).</li>
><li><tt>sasl_server_start</tt> / <tt>sasl_server_step</tt> have same
>output parameter deal as their equivalents on the client side</li>
><li><tt>sasl_listmech</tt> has a constant output parameter</li>
><li>If you used to canonicalize the username in a SASL_CB_PROXY_POLICY
>callback you should now separate the functionality of authorization and
>canonicalization.  That is, only do authorization in SASL_CB_PROXY_POLICY,
>and do canonicalization in the SASL_CB_CANON_USER callback</li>
></OL></LI>
>
></UL>
></BODY>
></HTML>
><HTML><HEAD>
><title>SASL Components</title>
>
></HEAD>
><BODY>
><H1>SASL Components</H1>
>
><p>As the SASL library is a 'glue layer' between many different parts of the
>authentication system, there are a lot of different components
>that often cause confusion to users of the library who are trying to
>configure it for use on their system.  This document will try to provide
>some structure to all of these components, though you will also need
>to read the <a href=sysadmin.html>System Administration</a> to have a full
>understanding of how to install SASL on your system.</p>
>
><p>The first thing to realize is that there is a difference between SASL,
>the protocol, and Cyrus SASL, the library.  The first is a specification
>that describes how authentication mechanisms can be plugged into an application
>protocol <i>on the wire</i>.  The later is an implementation that aims
>to make this easier for application developers to integrate authentication
>mechanisms into their application in a generic way.  It is quite possible
>to have an application that uses SASL (the specification) without using
>Cyrus SASL (the implementation).</p>
>
><p>The remainder of this document will refer to components of the Cyrus
>SASL implementation, though some of these will necessarily have a broader
>scope.</p>
>
><h3>The Application</h3>
>The application is a client of the SASL library.  It can be a client or server
>application (or both, in the case of a proxy).  It takes care of the
>on-the-wire representation of the SASL negotiation, however it performs no
>analysis of the exchange itself.  It relies on the judgment of the SASL
>library whether authentication has occurred or not.  The application is also
>responsible for determining if the authenticated user may authorize as another
>user id (For more details on authentication and authorization identities
>and their differences, see
><a href=sysadmin.html>Cyrus SASL for System Administrators</a>)</p>
>
><p>Examples of applications are Cyrus IMAPd, OpenLDAP, Sendmail, Mutt, 
>sieveshell, cyradm, and many others.</p>
>
><h3>The SASL Glue Layer</h3>
>
><p>The first component of the SASL library is affectionately called the
>&quot;glue&quot; layer.  It takes care of ensuring that the application and
>the mechanisms can work together successfully.  To this end, it does a
>variety of basic tasks:</p>
>
><ul>
><li>Loading of any plugins (more on these below)</li>
><li>Ascertaining necessary security properties from the application to aid
>in the choice of mechanism (or to limit the available mechanisms)</li>
><li>Listing of available plugins to the application (mostly used on the server
>side)</li>
><li>Choosing the &quot;best&quot; mechanism from a list of available mechanisms
>for a particular authentication attempt (client-side)</li>
><li>Routing the authentication (and in the case of a mechanism with a security
>layer, encrypted) data packets between the application and the
>chosen mechanism.</li>
><li>Providing information about the SASL negotiation back to the application
>(authenticated user, requested authorization identity, security strength of
>any negotiated security layer, and so on).</li>
></ul>
>
><p>The Cyrus SASL implementation also provides several other services to
>both its plugins and applications.  Some of these are simply general utilities,
>such as MIME Base-64 encoding and decoding, and random number generation.
>Others are more specific to the task of authentication, such as providing
>password verification services.  Such services are capable of taking
>a username and a plaintext password and saying &quot;yes&quit; or
>&quot;no&quot;.  Details of available password verification services are
>discussed below.</p>
>
><p>Finally, the glue code allows the mechanisms and applications access to
>two special types of plugins, Auxiliary Property or &quot;auxprop&quot;
>plugins, which provide a simple database interface and can return properties
>about the user such as password, home directory, or mail
>routing address, and Username Canonicalization, which might provide
>site-specific ways to canonicalize a username or perform other tasks.</p>
>
><p>In the Cyrus SASL Implementation, the glue code is entirely contained
>within <tt>libsasl2.so</tt> (or <tt>libsasl2.a</tt>)</p>
>
><h3>Plugins (General)</h3>
>
><p>The Cyrus SASL architechure is very modular, using loadable modules for
>things such as the mechanism profiles and the database access done by the
>auxillary property plugins.  This means that it is easy to limit what
>parts are loaded by a given application, and that third parties can write
>their own modules to provide services, just by adhering to the API description
>in <tt>saslplug.h</tt>.</p>
>
><h3>Plugins (SASL Mechanisms)</h3>
>
><p>The simplest types of plugins to understand are those which provide
>SASL mechanisms, such as CRAM-MD5, DIGEST-MD5, GSSAPI, PLAIN, SRP, and so on.
>These mechanisms take care of both server-side and client-side parts
>of the SASL negotiation.  If the given mechanism supports a security layer
>(that is, makes guarantees about privacy or integrity of data after the
>negotiation is complete), the plugin provides that functionality as well.</p>
>
><p>SASL mechanisms are generally defined by the IETF standards process,
>however, some mechanisms are not (For example, NTLM).  This is in contrast
>to the other types of plugins, which provide database and username
>canonicalization services to other plugins and thus aren't standardized in
>their behavior (they are specific to our implementation).  Password verifiers
>are also an implementation detail (though saslauthd makes use of
>standards such as PAM and LDAP to perform that verification)</p>
>
><p>There are several types of mechanisms, in broad strokes we have:</p>
><ul>
><li><b>Password Verification Mechanisms</b> - For example, PLAIN.  These receive a raw password from the remote and then pass it into the glue code for
>verification by a password verifier.  These require the existence of an
>outside security layer to hide the otherwise plaintext password from people
>who might be snooping on the wire.  These mechanisms do not require that
>the server have access to a plaintext (or plaintext-equivalent) version
>of the password.</li>
><li><b>Shared Secret Mechanisms</b> - For these mechanisms, such as CRAM-MD5,
>DIGEST-MD5, and SRP, there is a shared secret between the server and client
>(e.g. a password).  However, in this case the password itself does not travel
>on the wire.  Instead, the client passes a server a token that proves that
>it knows the secret (without actually sending the secret across the wire).
>For these mechanisms, the server generally needs a plaintext equivalent of
>the secret to be in local storage (not true for SRP).
><li><b>Kerberos Mechanisms</b> - Kerberos mechanisms use a trusted
>third party to authenticate the client.  These mechanisms don't require
>the server to share any secret information with the client, it is all performed
>through the Kerberos protocol.</li>
></ul>
>
><p>Mechanism plugins are generally contained in a .so file that has a name
>similar to the mechanism's name.  Though, in a static compilation they
>can also be a part of <tt>libsasl2.a</tt></p>
>
><h3>Plugins (Auxiliary Property)</h3>
>
><p>Auxiliary Property (or auxprop) plugins provide a database service for the
>glue layer (and through it, to the mechanisms and application).  Cyrus SASL
>ships with two auxprop plugins: SASLdb and SQL.  Though they can be use
>in much more generic ways, auxprop plugins are mostly only used by
>shared secret mechanisms (or by the auxprop password verify) to access the
>&quot;userPassword&quot; attribute.  This provides a plaintext copy of the
>password that allows for authentication to take place.</p>
>
><p>Like the mechanism plugins, these are named similarly to the databases
>that they implement an interface for.</p>
>
><h3>Plugins (Username Canonicalization)</h3>
>
>Username Canonicalization plugins are not widely used, however it may be
>useful to use as a hook if your site has specific requirements for how userids
>are presented to the applications.
>
><h3>Password Verification Services</h3>
>
><p>As described above, the password verifiers take a username and plaintext
>password, and say either &quot;yes&quot; or &quot;no&quot;.  It is not possible
>to use them to verify hashes that might be provided by the shared secret
>mechanisms.</p>
>
><p>Password verifiers are selected using the &quot;pwcheck_method&quot;
>SASL option.  There are two main password verifiers provided with Cyrus SASL:</p>
><ul>
><li><b>auxprop</b> - This uses an auxprop plugin to fetch the password and then
>compares it with the client-provided copy to make the determination.</li>
><li><b>saslauthd</b> - This calls out to the <tt>saslauthd</tt> daemon, which
>also ships with the distribution.  The <tt>saslauthd</tt> daemon has a number
>of modules of its own, which allow it to do verification of passwords in 
>a variety of ways, including PAM, LDAP, against a Kerberos database, and so on.
>This is how you would want to, for example, use the data contained in
><tt>/etc/shadow</tt> to authenticate users.</li>
></ul>
>
><hr>
>Back to the <a href=index.html>index</a>.
></BODY>
></HTML>
><HTML><HEAD>
><title>Configuring GSSAPI and Cyrus SASL</title>
>
></HEAD>
><BODY>
><h1>Configuring GSSAPI and Cyrus SASL</h1>
>
><p>This document was contributed by <a
>href="mailto:kenh@cmf.nrl.navy.mil">Ken Hornstein</a> and updated
>by <a href="mailto:Alexey.Melnikov@isode.com">Alexey Melnikov</a>.
>
><p>A couple of people have asked me privately, "Hey, how did you get the
>GSSAPI mechanism to work?  I tried, but the sample apps kept failing".
>(The short answer: I'm a tenacious bastard).
>
><p>I figured that it couldn't hurt to give a quick explanation as to
>how you get GSSAPI working with the sample apps, since it wasn't
>obvious to me, and I consider myself not completely ignorant of GSSAPI
>and Kerberos.
>
><ol>
><li> Compile the Cyrus-SASL distribution with the GSSAPI plugin
>  for your favorite GSS-API mechanism.  I personally use the GSSAPI
>  libraries included with the <a href="http://web.mit.edu/kerberos/www/">MIT</a>
>  Kerberos 5 distribution; <a href="http://www.pdc.kth.se/heimdal/">Heimdal</a>
>  and <a href="http://www.cybersafe.com/">CyberSafe</a> work as well.
>
><li> Start up the sample-server.  The command-line used for
>  sample-server needs to specify the GSSAPI service name and the
>  location of the plug-ins; your sample command line might look
>  something like this:
>
><pre>  ./sample-server -s host -p ../plugins/.libs
></pre>
>
>on UNIX and like
>
><pre>  sample-server -s host -p ..\plugins
></pre>
>
>on Windows.
>
>
><p> In this example, I am using "host", which already exists on my
>  machine, <i>but</i> only root can read it, so I an running this as root.
>  If you want to use an alternate service name, you will need to
>  create that service in Kerberos, place it in a keytab readable by
>  you, _and_ point your Kerberos library at it.
>
>  Unix: both MIT Kerberos and Heimdal, 
>  use /etc/krb5.keytab on Unix by default, but this can be changed
>  by setting the <tt>KRB5_KTNAME</tt> environment variable; the default
>  for CyberSafe Kerberos is /krb5/v5srvtab for UNIX systems and can be
>  changed by setting the <tt>CSFC5KTNAME</tt> environment variable.
>
>  Windows: the default service key table location for CyberSafe is
>  C:\Program Files\CyberSafe\v5srvtab, unless the
>  CyberSafe registry setting for the KeyTab key is set to an
>  alternate path. MIT Kerberos on Windows uses the keytab filename
>  krb5kt.
>
><p>  You should get a response similar to:
>
><pre>  Generating client mechanism list...
>  Sending list of 3 mechanism(s)
>  S: R1NTQVBJIFBMQUlOIEFOT05ZTU9VUw==
></pre>
>
><p>  Note that later on (assuming everything works) you might need to paste
>  in lines that are longer than canonical input processing buffer on your
>  system.  You can get around that by messing around with stty; while
>  the details vary from system to system, on Solaris you can do something
>  like:
>
><pre>  ( stty -icanon min 1 time 0 ; ./sample-server -s host -p ../plugins/.libs )
></pre>
>
><li> Obtain a Kerberos ticket for the user you want to authenticate as.
>
><pre>  kinit kenh
></pre>
>
>
><li> Start up the sample client.  You need to specify the service
>  name, the hostname, and the userid.  An example might be
>
><pre>  ./sample-client -s host -n your.fqdn.here -u kenh -p ../plugins/.libs
></pre>
>
><p>  You should get a response similar to this:
>
><pre>  Waiting for mechanism list from server...
></pre>
>
><li> Cut-and-paste the initial mechanism line from the server process
>  (this <i>includes</i> the "<tt>S: </tt>") into the client process.  You
>  should get something similar to:
>
><pre>  S: R1NTQVBJIFBMQUlOIEFOT05ZTU9VUw==
>  Choosing best mechanism from: GSSAPI PLAIN ANONYMOUS
>  Using mechanism GSSAPI
>  Preparing initial.
>  Sending initial response...
>  C: <.... lots of base 64 data ...>
>  Waiting for server reply...
></pre>
>
><p>  If GSSAPI isn't selected as the mechanism, there is a few things that
>  might have gone wrong:
>
><ul>
><li> The mechanism might not have been offered by the server.  The decoded
>     mechanism list offered by the server appears in the "<tt>Choosing best
>     mechanism</tt>" line.  If GSSAPI didn't appear in that list, then
>     something is wrong on the server.  Make sure that you specified the
>     correct plugins directory.  If the plugin directory is correct, but
>     the library fails to load, you <i>might</i> be running across a bug
>     in libtool on some platforms.  If you have your Kerberos/gssapi
>     libraries not installed in the system library path, those libraries
>     are likely not able to be found when the SASL GSSAPI plugin loads.
>     The solution varies from system to system; what I did was take
>     the linker line generated by libtool and run it by hand, adding
>     a <tt>-R/path/to/kerberos/libraries</tt> switch (this was on Solaris).
>     You can check with a system call tracer to see exactly what it is
>     trying to do.
>
><li> The client doesn't know about the mechanism.  The reasons for this
>     happening are the same as the server: check the -p switch, check
>     to make sure the correct libraries are being loaded with the GSSAPI
>     plugin.
></ul>
>
><p>  You can turn on a healthy amount of debugging information by changing
>  the definition in config.h of the VL macro to (and recompiling libsasl):
>
><pre>  #define VL(foo) printf foo;
></pre>
>
><p> There is a possibility
>you might get an error that looks like this:
>
><pre>  sample-client: Starting SASL negotiation: generic failure
></pre>
>
><p>  This can mean that you didn't provide all of the required information
>  to the sample-client (did you provide a service name with -s, the
>  hostname of the service with -n, and a username with -u ?), or that
>  GSSAPI has failed (unfortunately, on the client you cannot find out
>  the internal GSSAPI error; you will need to break out the debugger
>  for that).
>
><li> Cut and paste the client response (The _entire_ line that begins
>  with C:, <i>including</i> the initial "<tt>C: </tt>") to the server
>  process.  You should get a response back that starts with "<tt>S:
>  </tt>".  Cut and paste <i>that</i> to the client, and continue this
>  exchange until you either get "<tt>Negotiation complete</tt>", or an error.
>  If you get an error on the server you should get a complete error
>  message (including the GSSAPI error string); on the client you
>  unfortunately will only probably get "<tt>generic failure</tt>", which will
>  again require the use of a debugger (but the VL macro should help
>  with this).
>
><p>  One common thing that happens is that on your server you might see
>  the error:
>
><pre>  sample-server: Performing SASL negotiation: authentication failure
>	(Requested identity not authenticated identity)
></pre>
>
><p>  This comes from not having a requested identity (the -u option) that
>  matches the identity that you were authenticated to via the GSSAPI.
>  This is of course mechanism specific, but if for example you're using
>  Kerberos, the Cyrus SASL library strips out the @REALM from your
>  identity <i>if</i> you are in the same realm as the server.  So if your
>  Kerberos identity is user@SOME.REALM and the server is in SOME.REALM,
>  you need to specify "user" to the -u flag of the client.  If you're
>  accessing a server in a foreign realm, you need to pass the full
>  principal name via the -u option to make this work correctly.
>
><p>  If you complete the negotiation successfully, you should see something
>  that looks like (on both the client and server):
>
><pre>  Negotiation complete
>  Username: kenh
>  sample-server: realm: can't request info until later in exchange
>  SSF: 56
></pre>
>
><p> If you get to that, then you've done it, and GSSAPI works successfully!
>If you have questions about any of this, feel free to drop me a line.
>
><hr>
>Back to the <A href=index.html>index</a>
>
></body>
></html>
><!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
><HTML><head>
><TITLE>Cyrus SASL library</TITLE>
></head>
><body>
><h1>Cyrus SASL library, version 2</h1>
>
><p> SASL (Simple Authentication Security Layer) is an Internet
>standards-track method for remote computers to authenticate.  The
>Cyrus SASL library makes supporting various SASL mechanisms easy for
>both client and server writers.
>
><P>The Cyrus project is the implementation of an enterprise mail
>system by the Carnegie Mellon University Computing Services Department.
>We are interested in scalable, easy to administer systems.
>
><h2>The Cyrus SASL library distribution</h2>
>
><p><a href="http://asg.web.cmu.edu/cyrus/download/"><b>Cyrus SASL
>library distribution</B></A>
>
><h2>Documentation</h2>
>
><ul>
><li> <a href="readme.html"><b>Read Me First</b></A></li>
><li> <a href="install.html"><b>Installation Documentation</b></A></li>
><li> <a href="upgrading.html"><b>Information for upgrading from SASLv1</b></A></li>
><li> <a href="appconvert.html"><b>SASLv1 to SASLv2 Application Conversion Guide</B></A></li>
></ul>
>
><ul>
><li> <a href="components.html">A high-level overview of Cyrus SASL Components</a></li>
><li> <a href="sysadmin.html">The Cyrus SASL for System Administrators</A></li>
><li> <a href="options.html">Options for use with Cyrus SASL</A></li>
><li> <a href="programming.html">The SASL Application Programmer's Guide</A></li>
><li> <a href="plugprog.html">The SASL Plugin Programmer's Guide</A></li>
><li> <a href="advanced.html">Advanced SASL usage</A></li>
></ul>
>
><b>Special Platforms</b>
><ul>
><li> <a href="macosx.html"><b>Mac OS X Build Guide</b></a>
><li> <a href="os390.html"><b>OS/390 Build Guide</b></a>
><li> <a href="windows.html"><b>Win32 Build Guide</b></a>
></ul>
>
><b>RFCs and drafts</b>
>
><ul>
><li> <a href="rfc1321.txt">RFC 1321: The MD5 Message-Digest
>Algorithm</a></li>
><li> <a href="rfc1939.txt">RFC 1939: Post Office Protocol - Version
>3</a> (APOP/sasl_checkapop)</li>
><li> <a href="rfc2104.txt">RFC 2104: HMAC: Keyed-Hashing for Message
>Authentication</a></li>
><li> <a href="rfc2195.txt">RFC 2195: IMAP/POP AUTHorize Extention for
>Simple Challenge/Response</a>
><br>
><a href="draft-ietf-sasl-crammd5-xx.txt">
>draft-ietf-sasl-crammd5: The CRAM-MD5 SASL Mechanism</a> (CRAM-MD5)</li>
><li> <a href="rfc2222.txt">RFC 2222: Simple Authentication and
>Security Layer (SASL)</a> (KERBEROS_V4)
><br>
><a href="draft-ietf-sasl-rfc2222bis-xx.txt">
>draft-ietf-sasl-rfc2222bis: Simple Authentication and Security Layer
>(SASL)</a> (EXTERNAL)</li>
><li> <a href="rfc2243.txt">RFC 2243: OTP Extended Responses</a></li>
><li> <a href="rfc2245.txt">RFC 2245: Anonymous SASL Mechanism</a>
><br>
><a href="draft-ietf-sasl-anon-xx.txt">
>draft-ietf-sasl-anon: Anonymous SASL Mechanism</a> (ANONYMOUS)</li>
><li> <a href="rfc2289.txt">RFC 2289: A One-Time Password System</a></li>
><li> <a href="rfc2444.txt">RFC 2444: The One-Time-Password SASL
>Mechanism</a> (OTP)</li>
><li> <a href="rfc2595.txt">RFC 2595: Using TLS with IMAP, POP, and
>ACAP</a>
><br>
><a href="draft-ietf-sasl-plain-xx.txt">
>draft-ietf-sasl-plain: Plain SASL Mechanism</a> (PLAIN)</li>
><li> <a href="rfc2831.txt">RFC 2831: Using Digest Authentication as a
>SASL Mechanism</a>
><br>
><a href="draft-ietf-sasl-rfc2831bis-xx.txt">
> draft-ietf-sasl-rfc2831bis: Using Digest Authentication as a SASL
> Mechanism</a> (DIGEST-MD5)</li>
><li> <a href="rfc2945.txt">RFC 2945: The SRP Authentication and Key
>Exchange System</a></li>
><li> <a href="rfc3174.txt">RFC 3174: US Secure Hash Algorithm 1 (SHA1)</a></li>
><li> <a href="draft-burdis-cat-srp-sasl-xx.txt">
>draft-burdis-cat-srp-sasl: Secure Remote Password SASL
>Mechanism</a> (SRP)</li>
><li> <a href="draft-ietf-sasl-gssapi-xx.txt">
>draft-ietf-sasl-gssapi: SASL GSSAPI Mechanisms</a> (GSSAPI)</li>
><li> <a href="draft-ietf-sasl-saslprep-xx.txt">
>draft-ietf-sasl-saslprep: SASLprep: Stringprep profile for user names and passwords</a></li>
><li> <a href="draft-murchison-sasl-login-xx.txt">
>draft-murchison-sasl-login: The LOGIN SASL Mechanism</a> (LOGIN) -- <i>obsolete</i></li>
><li> <a href="draft-newman-sasl-passdss-xx.txt">
>draft-newman-sasl-passdss: DSS Secured Password Authentication Mechanism</a> (PASSDSS-3DES-1)</li>
><li> <a href="draft-newman-sasl-c-api-xx.txt">
>draft-newman-sasl-c-api: The SASL C API</a> (very rough draft)</li>
></ul>
>
><b>Other Documentation & Resources</b>
><ul>
><li><a href="http://www.oreillynet.com/pub/a/network/2002/04/09/sasl.html">
>Using SASL: Pluggable Security</a></li>
><li><a href="http://www.oreillynet.com/pub/a/network/2002/04/30/sasl2.html">
>Using SASL: CMU's Cyrus SASL Library</a></li>
><li><a href="http://www.melnikov.ca/mel/devel/SASL_info.html">Information on
>SASL mechanisms, profiles, servers and clients implementing SASL.</a></li>
><li><a href="http://www.sendmail.org/~ca/email/auth.html">FAQ</a> from
> Sendmail. </li>
><li><a href="http://www-cs-students.stanford.edu/~tjw/srp/ndss.html">
>The Secure Remote Password Protocol</a> paper by Thomas Wu</li>
><li><a href="http://beepcore-tcl.sourceforge.net/tclsasl.html">TCL extensions
>for SASL</A></li>
><li><a href="http://davenport.sourceforge.net/ntlm.html">
>The NTLM Authentication Protocol</a> (NTLM)</li>
><li><a href="http://www.snia.org/tech_activities/CIFS/CIFS-TR-1p00_FINAL.pdf">
>Common Internet File System (CIFS) Technical Reference</a> (SMB/NTLM)</li>
></ul>
>
><p><hr><p>
><A HREF="http://asg.web.cmu.edu/cyrus">Go</A> to the Project Cyrus Home Page<br>
><A HREF="http://asg.web.cmu.edu">Go</A> to the Andrew Systems Group homepage.
></body>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
>                      "http://www.w3.org/TR/html4/loose.dtd"> 
><html><head>
><title>Cyrus SASLv2 INSTALL Documentation</title>
>
></head>
><body>
><h1>Installation Procedure</h1>
>
>This document offers a general overview of installing the SASL library.
>
><h2>Quick and Dirty</h2>
><pre>
>  cd (directory it was untarred into)
>  ./configure
>  make
>  make install
>  ln -s /usr/local/lib/sasl2 /usr/lib/sasl2
></pre>
>
><p>If you're checking this directly out of CVS, you'll need to run "sh
>./SMakefile" to build the configure script first.
>
><p>Read <A HREF="sysadmin.html">the System Administrator's Guide</A> to
>learn how to configure libsasl in depth.  There is also a <A
>HREF="upgrading.html">document</A> that covers migrating from libsasl v1
>to libsasl v2 applications.
>
><p>You may also be interested in the contents of <tt>configure --help</tt>
>which can reveal the many possible configure options that can be used
>to build Cyrus SASL.
>
><h3>Details</h3>
>
><p>Note that the library looks for plugins in <tt>/usr/lib/sasl2</tt>,
>but installs them into <tt>${prefix}/lib/sasl2</tt>, where
><tt>${prefix}</tt> is usually something like <tt>/usr/local</tt>.
>This is intentional - we want the plugins installed with the rest of
>the package (wherever things get installed at your site), but we want
>the library to <em>always</em> be able to find its plugins under
><tt>/usr/lib/sasl2</tt>, no matter where you install things, so that
>the SASL plugin ABI on all platforms is roughly the same.
>
><p>If you don't want to do this for some reason, you can set the location
>where the library will look for plugins by setting the environment
>variable SASL_PATH to the path the library should use.
>
><h2>Slower and Cleaner</h2>
>
>Before reading this section, please be sure you are comfortable with
>the concepts presented in the <a href=components.html>components discussion</a>
>and in the <a href=readme.html>Read Me First</a> document.<p>
>
>You will want to have answered the following questions about your intended
>installation:<p>
>
><ol>
><li>What mechanisms do you want to support?  Are they plaintext (LOGIN, PLAIN),
>shared secret (DIGEST-MD5, CRAM-MD5), or Kerberos (KERBEROS_V4, GSSAPI)?
>Perhaps you will use some combination (generally plaintext with one of
>the other two types).</li>
><li>Given the answer to the previous question, how will the mechanisms
>perform user verification?
>  <ul>
>  <li>The Kerberos mechanisms just need your existing
>Kerberos infroastructure.</li>
>  <li>The shared secret mechanisms will need an auxprop
>plugin backend.</li>
>  <li>The plaintext mechanisms can make do with saslauthd, Courier authdaemond (not included),
>*or* by using an auxprop plugin backend.</li>
>  <li>To use Kerberos and Plaintext, you'll likely want to use saslauthd
>with a kerberos module for plaintext authentication.  To use Shared Secret
>and plaintext, you'll want to use the auxprop plugin for password verification.
>  </li>
>  </ul></li>
><li>If you are using an auxprop plugin, will you be using SASLdb (and
>if so, Berkeley DB [recommended], GDBM, or NDBM?), LDAP or an SQL backend
>(Postgres? MySQL?).</li>
><li>If you are using saslauthd, what module will you be using?  LDAP?
>Kerberos?  PAM?</li>
><li>Also if you are using saslauthd, what communication (IPC) method do
>you want to use?  On most systems, the correct answer is the default
>(unix sockets), but on Solaris you can use IPC doors, which have proven
>to be more stable than equivilant Solaris systems using unix sockets.</li>
></ol>
>
>Once you have answered these questions, properly configuring a working
>configuration of Cyrus SASL becomes significantly easier.
>
><h3>Requirements</h3>
>
><p>You'll probably need the GNU make program, available as of this
>writing <a href="ftp://ftp.gnu.org/pub/gnu/make/">here</a>.<p>
>
><p>If you are using SASLdb, you will need to pick your backend.
>libsasl2 can use gdbm, Berkeley db, or ndbm to implement its
>user/password lookup. Most systems come with ndbm these days; as of
>this writing, gdbm is available <a
>href="ftp://ftp.gnu.org/pub/gnu/gdbm/">here</a>.
>Berkeley DB is available from: <a
>href="http://www.sleepycat.com/">Sleepycat</a>
>
><p>If you are using SQL, you'll need to properly configure your server/tables,
>and build the necessary client libraries on the system where you will be
>building and using SASL.  Currently we support <a href=http://postgresql.org>
>PostgreSQL</a> v7.2 (or higher) and <a href=http://mysql.org>MySQL</a>.
>
><p>If you are using LDAPDB, you'll need SASL enabled OpenLDAP libraries.  <a
>href="http://www.openldap.org">OpenLDAP</a> 2.1.27 (or higher) or 2.2.6 (or
>higher) is support.</p>
>
><p>For Kerberos support, you'll need the kerberos libraries.  At CMU, the
>version we use comes from <a href="http://www.pdc.kth.se/kth-krb/">here</a>.
>
><p>For GSSAPI support you will need either <a href="http://web.mit.edu/kerberos/www/">MIT Kerberos 5</a>
>, the <a href="http://www.pdc.kth.se/heimdal">Heimdal</a> or
><a href="http://www.cybersafe.com/">CyberSafe</a> implementation.
>
><h3>Build Configuration</h3>
>
><p>Once you have ansered all the necessary questions and installed
>(and tested!) any required packages for your configuration, you are
>ready to build SASL.  Building SASL is done with the aid of
>an autoconf <tt>configure</tt> script, which has a <b>lot</b> of options.
>Be sure to read the outpit of <tt>configure --help</tt> to be sure you
>aren't missing any (they are all documented).  Note that often times
>a <tt>--enable-foo</tt> option has a counterpart like <tt>--disable-foo</tt>
>to not enable that feature.
>
><p>Some of the most important configuration options are those which allow
>you to turn off the comiplation of modules you do not need.  This is often
>the easiest way to solve compilation problems with Cyrus SASL.
>If you're not going to need a particular mechanism, don't build it!  Not
>building them can also add performance improvements as it does take system
>resources to load a given plugin, even if that plugin is otherwise unused
>(even when it is disabled via the <tt>mech_list</tt> <a href=options.html>option</a>).
>
><p>As of this writing, modules that are enabled by default but may not
>be applicable to all systems include CRAM-MD5, DIGEST-MD5, OTP, KERBEROS_V4,
>GSSAPI, PLAIN, and ANONYMOUS.  These can be disabled with
><tt>--disable-cram</tt>,
><tt>--disable-digest</tt>, <tt>--disable-otp</tt>,
><tt>--disable-krb4</tt>, <tt>--disable-gssapi</tt>,
><tt>--disable-plain</tt>, and <tt>--disable-anon</tt> respecively.
>
><p>If you are using an SQL auxprop plugin, you may want to specify one or more
>of <tt>--enable-sql</tt>, <tt>--with-mysql=PATH</tt>, and
><tt>--with-pgsql=PATH</tt>, note that PATH in the later two should be replaced
>with the path where you installed the necessary client libraries.
>
><p>If you are using LDAPDB auxprop plugin, you will need to specify
><tt>--enable-ldapdb</tt> and <tt>--with-ldap=PATH</tt>.  <b>Warning:</b> LDAPDB
>auxprop plugin (and LDAP enabled saslauthd) introduces a circular dependency
>between OpenLDAP and SASL.  I.e., you must have OpenLDAP already built when
>building LDAPDB in SASL.  In order for LDAPDB to work at runtime, you must have
>OpenLDAP already built with SASL support. One way to solve this issue is to
>build Cyrus SASL first without ldap support, then build OpenLDAP, and then come
>back to SASL and build LDAPDB.</p>
>
><p>Given the myriad of ways that Berkeley DB can be installed on a system,
>people useing it may want to look at the <tt>--with-bdb-libdir</tt> and
><tt>--with-bdb-incdir</tt> as alternatives to <tt>--with-dbbase</tt> for
>specifying the paths to the Berkeley DB Library and Include directories.
>
><p>In fact, if you're not planning on using SASLdb at all, it may be worth
>your time to disable its use entirely with the <tt>--with-dblib=none</tt>
>option.
>
><p>If you are planning on using LDAP with saslauthd, be sure to specify
>the <tt>--with-ldap=PATH</tt> option to <tt>configure</tt>.
>
><h3>Building and Installation</h3>
>
>After configure runs, you should be able to build SASL just by 
>running <tt>make</tt>.  If this runs into problems, be sure that you
>have disabled everything that your system doesn't need, and that you have
>correctly specified paths to any dependencies you may have.<p>
>
>To install the library, run <tt>make install</tt> as <tt>root</tt> followed by
><tt>ln -s /usr/local/lib/sasl2 /usr/lib/sasl2</tt> (modified for your
>installation path as appropriate).  Be sure to do this last step or
>SASL will not be able to locate your plugins!
>
><h3>Compilation Hints</h3>
>
><p>You may need to play with your CPPFLAGS and LDFLAGS a little if you're
>using vendor compilers. We use <tt>gcc</tt> extensively, but you'll
>probably have more luck if you use the same compiler for the library
>as you do for your applications. You can see what compilers we use on
>our platforms by looking at the "SMakefile".
>
><h3>Application Configuration</h3>
>
><p>Plesae read about the <a href=options.html>SASL Options</a> to learn what
>needs to be configured so that applications can successfully use the SASL
>library.  This is also covered in the <a href=readme.html>Read Me First</a>
>document.
>
><p>You will want to ensure that the settings of <tt>pwcheck_method</tt>
>and <tt>auxprop_plugin</tt> match the decisions you made about your
>authentication infrastructure.  (For example, if you are using
>saslauthd as a password verifier, you'll want to be sure to set
><tt>pwcheck_method: saslauthd</tt>).
>
><p>If you are using saslauthd, you will want to arrange for
><tt>saslauthd -a pam</tt> (or ldap, or kerberos4, etc) to be run
>at boot.  If you are not going to be using saslauthd, then this is
>not necessary.
>
><p>Many of these pieces are covered in more detail in the
><a href=sysadmin.html>SASL System Administrator's Guide</a>.
>
><h2>Supported platforms</h2>
>
><p>This has been tested under Linux 2.2, Linux 2.4, Solaris 2.7 and
>Solaris 2.8.  It should work under any platform where dynamic objects
>can be linked against other dynamic objects, and where the dynamic
>library file extension is ".so", or where libtool creates the .la
>files correctly.  There is also documentation for
><a href=windows.html>Win32</a>, <a href=macosx.html>MacOS X</a>, and
><a href=os390.html>OS/390</a>.
>
><hr>
>Back to the <a href="index.html">index</a>
>
></body>
></html>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
><html>
><head>
>  <title>Building and Using Cyrus SASL on Mac OS X</title>
>
></head>
><body>
><h1>Cyrus SASL v2 on Mac OS X (and 9)</h1>
><p>The Cyrus SASL v2 distribution now supports Mac OS X, including
>applications written to Apple's Carbon and Cocoa interfaces, as well
>as the standard Unix-like API. It includes the following
>components:</p>
><ul>
>  <li>A port of the Unix SASL library, which lives in <tt>/usr/local/lib/libsasl2.dylib</tt>
>(or something like that) and
>with plugins in <tt>/usr/lib/sasl</tt> (which should be a symlink to <tt>/usr/local/lib/sasl</tt>).
>  </li>
>  <li>A framework which lives in
><tt>/Library/Frameworks/SASL2.framework</tt>, and allows the use of the
><tt>-framework</tt> option to Apple's <tt>ld</tt>, or linking with the
>framework in Project Builder. This framework is in fact a wrapper for a
>symlink to <tt>/usr/local/lib/libsasl2.dylib</tt> with the necessary
>information to recognize it as a framework. This is what we expect many
>Cocoa and Carbon Mach-O applications will want to use, and the framework
>is required for CFBundle to work, which is used by the CFM glue library.
></li>
>  <li>A CFM glue library (<tt>/Library/CFMSupport/SASL2GlueCFM</tt>) which
>can be linked in by Carbon CFM applications, that uses CFBundle to bind
>the framework and thus load the Unix-level library. It automatically loads
>the important functions at <tt>sasl_client_init</tt> or
><tt>sasl_server_init</tt> time; it also automatically makes sure memory
>allocation works if you're using the metrowerks malloc; if you're not,
><tt>sasl_set_alloc</tt> works as usual. </li>
>  <li>A Carbon port of the existing CFM library for Mac OS 9. Note that
>this could probably be modified fairly easily to work on OS X, but
>there's not much point. The CFM glue layer to the Unix library
>supports many more functions, including the entire server API; also,
>the Unix implementation is mostly independent of Kerberos
>implementation, while the Mac OS 9 Carbon port specifically requires
>MIT Kerberos for Macintosh 3.5 or later in order to get Kerberos
>support. The Mac OS 9 code implements only the client API, but this is
>mostly what is wanted from SASL on OS 9 anyway. </li>
></ul>
><p>If you are building a Carbon CFM application and intend it to run on
>both OS 9 and OS X, you should link against the OS 9 Carbon SASL
>library, since it exports fewer APIs (client side only, specifically)
>than the OS X CFM glue. Your application should work seamlessly with
>both libraries if you do this, despite the different implementations
>underneath.</p>
><p>If you need a Carbon CFM application to support server-side SASL
>functionality, you need to link against the <tt>SASL2GlueCFM</tt>
>library, but be aware that your application will not run on OS 9.</p>
><h2>Compiling and Using the Unix library</h2>
>
>The Unix library is mostly ready to build on Mac OS X, but it does depend
>on the <tt>dlcompat</tt> package in order to load its plugins.
><tt>dlcompat-20010505</tt> is a relatively simple version known to work
>with SASL; it is provided with the distribution in a tarball. You should
><tt>make</tt> and <tt>make install</tt> the <tt>dlcompat</tt> library
>(which probably goes into <tt>/usr/local/lib/libdl.dylib</tt>) before
>attempting to <tt>./configure</tt> the SASL distribution itself. SASL will
>then pretend it's a real Unix <tt>libdl</tt>, and link against it. 
>
><p>Since there are, at this point, newer and far more complex versions of
>dlcompat, you may prefer to use those instead if other software requires
>their functionality. The dlcompat homepage is located <a
>href="http://www.opendarwin.org/projects/dlcompat/">on the OpenDarwin
>site.</a> Many users may want to install the <tt>/sw</tt> tree from <a
>href="http://fink.sourceforge.net/">the Fink project</a> to get this, as
>well as possibly newer autotools and other software.<br> </p>
>
><p>As of version 2.1.16, SASL uses and requires a recent version of GNU
>autotools (autoconf, automake, and libtool) to build its configuration scripts.
>If you are building from CVS, you will need to have the autotools installed
>on your system. The version included with all releases of the developer tools
>for OS X 10.2.x is too old for this; if you aren't using OS X 10.3 or later,
>you should upgrade to more recent patchlevels of these tools. The easiest way
>to do this is to <a href="http://fink.sourceforge.net/">install the Fink
>environment</a> and then <tt>apt-get
>install autoconf2.5 automake1.7 libtool14</tt>.<br>
></p>
><p>Recent versions of SASL ship with Kerberos v4 disabled by default.
>If you need Kerberos v4 for some reason, and you are using MIT Kerberos
>for Macintosh 4.0 or later, you should <tt>./configure</tt> with
>the added options <tt>"--enable-krb4=/usr --without-openssl
>--disable-digest"</tt> so that it finds the
>correct location for the header files, and does not use OpenSSL or
>build anything that depends on it (such as the digest-md5 plugin),
>since OpenSSL provides its own DES routines which do not work with
>Kerberos v4. <i>Please read the "Known Problems" section at the end of
>this
>document for more information on this issue.<br>
></i></p>
><p>You must be root to make install, since <tt>/usr/local</tt> is only
>modifiable by root. You need not enable the root account using
>NetInfo; the recommended (but underdocumented) method is to use
><tt>sudo -s</tt> from the Terminal window when you are logged into an
>administrator's account, and enter the password for that account. When
>building on Mac OS X, <tt>make install</tt> will automatically add the
>framework to <tt>/Library/Frameworks</tt>.</p>
><p>This does not build the CFM glue library. Building the CFM glue
>library requires Metrowerks CodeWarrior Pro 6 or later (tested with
>6), and the files necessary to build it are in the
><tt>mac/osx_cfm_glue</tt> folder.</p>
><h2>Changes to the Unix library to make it work on OS X</h2>
><p>This is provided for reference purposes only. The build system will
>automatically take care of all of these issues when building on Darwin
>or Mac OS X.</p>
><ul>
>  <li>The random code supports the preferred way to generate random
>numbers in Darwin. (In SASL v2, it does this on all unix-like
>platforms that lack jrand48). <i>Note that Mac OS X "Jaguar", version
>10.2,
>now has the standard jrand48 function, and that SASL will use this
>instead
>of the previous workaround.</i> </li>
>  <li>Symbols which are dlopened have an underscore prefixed. (This
>behavior is detected by configure in SASL v2.) </li>
>  <li>Plugins are linked with the <tt>-module</tt> option to <tt>libtool</tt>,
>which causes the <tt>-bundle</tt> option to be
>supplied to Apple's <tt>ld</tt>. (This is done on all platforms in
>SASL v2.) </li>
>  <li>The MD5 symbols are renamed to avoid library conflicts. This
>allows proper compilations against Heimdal and MIT's unix kerberos
>distribution, and prevents crashes when linked against MIT Kerberos
>for Macintosh (which also duplicates the symbols, but in a different
>way). Note that the MD5 symbols have local names on all platforms with
>SASL v2; this was only different in SASL v1. </li>
>  <li>MIT Kerberos for Macintosh 4.0 and later are fully supported. This
>was accomplished by using <tt>krb_get_err_text</tt> if available and
>checking for additional names for the krb4 libraries. </li> </ul>
><h2>Changes to the Mac OS 9 projects to support Carbon</h2>
><p><b><i>Please read these notes before you attempt to build SASL for OS 9
>Carbon!</i></b> </p> <ul>
>  <li><b>Important!</b> You must make sure that all files have their
>correct HFS filetype before starting to build this code! In
>particular, all source and text files must be of type <tt>'TEXT'</tt>,
>which is not the default if you use the Mac OS X cvs client to check
>out the projects. If you run into this problem, you may want to use a
>utility such as FileTyper to recursively change the type on all
>files. CodeWarrior is less picky about the projects' filetypes, but
>setting them to filetype <tt>'MMPr'</tt>, creator code <tt>'CWIE'</tt>
>may be helpful in opening the projects from the Finder. Users on Mac OS
>X familiar with the Unix <tt>find</tt>
>command should be able to rig <tt>/Developer/Tools/SetFile</tt>
>to do this job as well. </li>
>  <li>Many of the important projects (for <tt>libdes</tt>, <tt>libsasl</tt>,
>    <tt>build_plugins</tt>, and the sample client <tt>sc_shlb</tt>)
>have Carbon versions. </li>
>  <li>Plugins are loaded from a <tt>Carbon</tt> subfolder of the <tt>SASL
>v2</tt> folder in the Extensions folder. Plugins directly
>in
>the <tt>SASL v2</tt> folder are considered to be for the Classic
>libraries. </li>
>  <li>Note that when using the <tt>build_plugins</tt> project, you must
>generate the plugin init files using the <tt>makeinit.sh</tt> script in
>the <tt>plugins</tt> directory. The easiest way to do this is to run the
>script from a Unix shell, such as Mac OS X. You must then fix the
>filetypes of the generated source files (see above). </li>
>  <li>There is a new folder in <tt>CommonKClient</tt> called <tt>mac_kclient3</tt>
>which contains code compatible with MIT's new <a
> href="http://web.mit.edu/macdev/Development/MITKerberos/MITKerberosLib/KClient/Documentation/index.html">KClient
>3.0</a> API. This folder must be in your CodeWarrior access paths, the
>old <tt>mac_kclient</tt> folder must not, and it must precede the
>project's main folder. </li>
>  <li>The kerberos4 plugin uses this new code. The kerberos4 plugin
>also
>statically links the Carbon <tt>libdes</tt>, and no other part of
>Carbon SASL uses <tt>libdes</tt> directly. <i>Your application should
>    <b>not</b> link against</i> <tt>libdes.shlb</tt> <i>under Carbon!</i>
>(It causes problems due to DES symbols also existing in the MIT
>Kerberos library, which loads first.) </li>
>  <li>To build the projects, you should have the MIT Kerberos for
>Macintosh 3.5 installation disk images mounted, since the access paths
>include the absolute paths to the library directories from that
>image. It's easier than you having to find the paths yourself, and
>smaller than having to distribute the libraries with SASL. </li>
></ul>
><h2>Known Problems</h2>
><ul>
>  <li>The Kerberos v4 headers bundled with Mac OS X (and Kerberos for
>Macintosh) are not compatible with OS X's OpenSSL headers. (Kerberos v4
>support is disabled by default.) If you actually need krb4 support, the
>easiest solution is to build without using OpenSSL's
><tt>libcrypto</tt>. To do this, specify the <tt>--without-openssl</tt>
>option to <tt>configure</tt>. As of version 2.1.18, this automatically
>disables using <tt>libcrypto</tt> for DES as well. You will probably
>also need to specify <tt>--disable-digest</tt> since the digestmd5 plugin
>does not build against Kerberos v4's DES headers or library. Note that
>this disables several features (digestmd5, NTLM, OTP) which require
>OpenSSL. If both Kerberos v4 and functionality that requires OpenSSL are
>needed, it is probably possible to build the Kerberos v4 plugin against
>the correct K4 DES libraries, and everything else against OpenSSL;
>however, we do not support that configuration.<br>
>  </li>
>  <li>Versions of Cyrus SASL prior to 2.1.14 with support for Carbon
>CFM applications on Mac OS X have a known bug involving the CFM glue
>code (in <tt>mac/osx_cfm_glue</tt>). If <tt>sasl_done</tt> is called
>to unload the SASL library, and then one of the initialization
>functions (such as <tt>sasl_client_init</tt>) is called to
>reinitialize it from the same process, the application will crash. A
>fix for one obvious cause of this problem is included in 2.1.14;
>however, as of this writing, it has not been tested. It is possible
>that other bugs in Cyrus SASL, or deficiencies in Apple's libraries,
>will make this fix insufficient to resolve this issue. </li>
></ul>
></body>
></html>
>
><HTML>
><HEAD>
><TITLE>SASL Mechanism Properties/Features</TITLE>
></HEAD>
><BODY>
><h2>SASL Mechanism Properties/Features</h2>
>
>This table shows what security flags and features are supported by each
>of the mechanisms provided by the Cyrus SASL Library.<p>
>
><TABLE BORDER=1 CELLSPACING=1 CELLPADDING=2>
>
><TR>
><TH ROWSPAN=2><br></TH>
><TH ROWSPAN=2>MAX<br>SSF</TH>
><TH COLSPAN=7>SECURITY PROPERTIES</TH>
><TH COLSPAN=4>FEATURES</TH>
></TR>
>
><TR>
><TH><CENTER>NOPLAIN</CENTER></TH>
><TH><CENTER>NOACTIVE</CENTER></TH>
><TH><CENTER>NODICT</CENTER></TH>
><TH><CENTER>FORWARD</CENTER></TH>
><TH><CENTER>NOANON</CENTER></TH>
><TH><CENTER>CRED</CENTER></TH>
><TH><CENTER>MUTUAL</CENTER></TH>
><TH><CENTER>CLT FIRST</CENTER></TH>
><TH><CENTER>SRV FIRST</CENTER></TH>
><TH><CENTER>SRV LAST</CENTER></TH>
><TH><CENTER>PROXY</CENTER></TH>
></TR>
>
><TR>
><TH>ANONYMOUS</TH>
><TD><CENTER>0</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
></TR>
>
><TR>
><TH>CRAM-MD5</TH>
><TD><CENTER>0</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
></TR>
>
><TR>
><TH>DIGEST-MD5</TH>
><TD><CENTER>128</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER>reauth</CENTER></TD>
><TD><CENTER>initial auth</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
></TR>
>
><TR>
><TH>EXTERNAL</TH>
><TD><CENTER>0</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
></TR>
>
><TR>
><TH>GSSAPI</TH>
><TD><CENTER>56</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
></TR>
>
><TR>
><TH>KERBEROS_V4</TH>
><TD><CENTER>56</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
></TR>
>
><TR>
><TH>LOGIN</TH>
><TD><CENTER>0</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
></TR>
>
><TR>
><TH>NTLM</TH>
><TD><CENTER>0</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
></TR>
>
><TR>
><TH>OTP</TH>
><TD><CENTER>0</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
></TR>
>
><TR>
><TH>PLAIN</TH>
><TD><CENTER>0</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
></TR>
>
><TR>
><TH>SRP</TH>
><TD><CENTER>128</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER><br></CENTER></TD>
><TD><CENTER>X</CENTER></TD>
><TD><CENTER>X</CENTER></TD>
></TR>
>
></TABLE>
>
><h3>Understanding this table:</h3>
><ul>
><li><b>MAX SSF</b> - The maximum Security Strength Factor supported
>by the mechanism (roughly the number of bits of encryption provided, but may
>have other meanings, for example an SSF of 1 indicates integrity protection
>only, no encryption).</li>
><li><b>NOPLAIN</b> - Mechanism is not susceptable to simple passive
>(eavesdropping) attack.</li>
><li><b>NOACTIVE</b> - Protection from active (non-dictionary) attacks
>during authentication exchange.  (Implies <b>MUTUAL</b>).</li>
><li><b>NODICT</b> - Not susceptable to passive dictionary attack.</li>
><li><b>NOFORWARD</b> - Breaking one session won't help break the next.</li>
><li><b>NOANON</b> - Don't permit anonymous logins.</li>
><li><b>CRED</b> - Mechanism can pass client credentials.</li>
><li><b>MUTUAL</b> - Supports mutual authentication (authenticates the server
>to the client)</li>
><li><b>CLTFIRST</b> - The client should send first in this mechanism.</li>
><li><b>SRVFIRST</b> - The server must send first in this mechanism.</li>
><li><b>SRVLAST</b> - This mechanism supports server-send-last configurations.</li>
><li><b>PROXY</b> - This mechanism supports proxy authentication.</li>
></ul>
>
></BODY>
></HTML>
><HTML><HEAD>
><title>Options for Cyrus SASL</title>
>
></HEAD>
><BODY>
><h1>Options for Cyrus SASL</h1>
>
><p>This document contains information on what options are used by the
>Cyrus SASL library and bundled mechanisms.  The most commonly used
>options (and those that are therefore most commonly misunderstood
>are <b>pwcheck_method</b> and <b>auxprop_plugin</b>.  Please ensure
>that you have configured these correctly if things don't seem to
>be working right.  Additionally, <b>mech_list</b> can be an easy
>way to limit what mechanisms a given application will use.</p>
>
><TABLE BORDER WIDTH=95%>
><TR><TH>Option</TH><TH>Used By</TH><TH>Description</TH><TH>Default</TH></TR>
><TR>
><TD>authdaemond_path</TD><TD>SASL Library</TD> 
><TD>Path to Courier-IMAP authdaemond's unix socket.
>Only applicable when pwcheck_method is set to authdaemond.</TD><TD>/dev/null</TD>
></TR>
><TR>
><TD>auto_transition</TD><TD>SASL Library</TD> 
><TD>When set to 'yes' or 'noplain',
>and when using an auxprop plugin, automatically transition
>users to other mechs when they do a successful plaintext
>authentication.  When set to 'noplain', only non-plaintext secrets 
>will be written.  <I>Note that the only mechs (as currently
>implemented) which don't use plaintext secrets are
>OTP and SRP.</I></TD><TD>no</TD>
></TR>
><TR>
><TD>auxprop_plugin</TD><TD>Auxiliary Property Plugin</TD>
><TD>Name of auxiliary plugin to use, you may specify a space-separated
>list of plugin names, and the plugins will be queried in order</TD>
><TD>(null) - querys all plugins</TD>
></TR>
><TR>
><TD>canon_user_plugin</TD><TD>SASL Library</TD>
><TD>Name of canon_user plugin to use</TD><TD>INTERNAL</TD>
></TR>
><TR>
><TD>keytab</TD><TD>GSSAPI</TD> <TD>Location of keytab
>file</TD><TD><tt>/etc/krb5.keytab</tt> (system dependant)</TD>
></TR>
><TR>
><TD>ldapdb_uri</TD><TD>LDAPDB plugin</TD>
><TD>ldap server uri, you can specify a space-separated list of URIs - 
>ldapi:// or ldaps://ldap1/ ldaps://ldap2/</TD>
><TD>none</TD>
></TR>
><TR>
><TD>ldapdb_id</TD><TD>LDAPDB plugin</TD>
><TD>ldap SASL authentication id</TD>
><TD>none</TD>
></TR>
><TR>
><TD>ldapdb_mech</TD><TD>LDAPDB plugin</TD>
><TD>ldap SASL mechanism for authentication</TD>
><TD>none</TD>
></TR>
><TR>
><TD>ldapdb_pw</TD><TD>LDAPDB plugin</TD>
><TD>ldap password for SASL authentication id</TD>
><TD>none</TD>
></TR>
><TR>
><TD>ldapdb_rc</TD><TD>LDAPDB plugin</TD>
><TD>The filename specified here will be put into the server's LDAPRC
>environment variable, and libldap-specific config options may be set
>in that ldaprc file.  The main purpose behind this option is to allow
>a client TLS certificate to be configured, so that SASL/EXTERNAL may
>be used between the SASL server and the LDAP server. This is the most
>optimal way to use this plugin when the servers are on separate machines.</TD>
><TD>none</TD>
></TR>
><TR>
><TD>ldapdb_starttls</TD><TD>LDAPDB plugin</TD>
><TD>Use StartTLS.  This option may be set to 'try' or 'demand'.  
>When set to "try" any failure in StartTLS is ignored. 
>When set to "demand" then any failure aborts the connection.</TD>
><TD>none</TD>
></TR>
><TR>
><TD>log_level</TD><TD>SASL Library</TD>
><TD><b>Numeric</b> Logging Level (see <TT>SASL_LOG_*</TT> in <tt>sasl.h</tt>
>for values and descriptions</TD>
><TD>1 (SASL_LOG_ERR)</TD>
></TR>
><TR>
><TD>mech_list</TD><TD>SASL Library</TD>
><TD>Whitespace separated list of mechanisms to allow (e.g. 'plain
>otp').  Used to restrict the mechanisms to a subset of the installed
>plugins.</TD><TD>(use all available plugins)</TD>
></TR>
><TR>
><TD>ntlm_server</TD><TD>NTLM (server)</TD>
><TD>Name of server (WinNT, Win2K, Samba, etc) to which authentication
>will be proxied.</TD>
><TD>(null) - perform authentication internally</TD>
></TR>
><TR>
><TD>ntlm_v2</TD><TD>NTLM (client)</TD>
><TD>Send NTLMv2 responses to the server.</TD>
><TD>no (send NTLMv1)</TD>
></TR>
><TR>
><TD>opiekeys</TD><TD>OTP (with OPIE)</TD>
><TD>Location of the opiekeys file</TD><TD><tt>/etc/opiekeys</tt></TD>
></TR>
><TR>
><TD>otp_mda</TD><TD>OTP (w/o OPIE)</TD>
><TD>Message digest algorithm for one-time passwords, used by sasl_setpass
>(possible values: 'md4', 'md5', 'sha1')</TD><TD><tt>md5</tt></TD>
></TR>
><TR>
><TD>plugin_list</TD><TD>SASL Library</TD>
><TD>Location of Plugin list (Unsupported)</TD><TD><i>none</i></TD>
></TR>
><TR>
><TD>pwcheck_method</TD><TD>SASL Library</TD>
><TD>Whitespace separated list of mechanisms used to verify passwords,
>used by sasl_checkpass (possible values: 'auxprop', 'saslauthd',
>'pwcheck', 'authdaemond' [if compiled with <tt>--with-authdaemond</tt>])
>and 'alwaystrue' [if compiled with <tt>--enable-alwaystrue</tt>])
></TD><TD>auxprop</TD>
></TR>
><TR>
><TD>reauth_timeout</TD><TD>DIGEST-MD5</TD>
><TD>Length in time (in minutes) that authentication info will be
>cached for a fast reauth.  A value of 0 will disable reauth.</TD>
><TD>0</TD>
></TR>
><TR>
><TD>saslauthd_path</TD><TD>SASL Library</TD>
><TD>Path to saslauthd run directory (<b>including</b> the "/mux" named pipe)</TD>
><TD>system dependant (generally won't need to be changed)</TD>
></TR>
><TR>
><TD>sasldb_path</TD><TD>sasldb plugin</TD>
><TD>Path to sasldb file</TD><TD><tt>/etc/sasldb2</tt> (system dependant)</TD>
><TR>
><TD>sql_engine</TD><TD>SQL plugin</TD>
><TD>Name of SQL engine to use (possible values: 'mysql', 'pgsql', 'sqlite').</TD>
><TD><tt>mysql</tt></TD>
></TR>
><TR>
><TD>sql_hostnames</TD><TD>SQL plugin</TD>
><TD>Comma separated list of SQL servers (in host[:port] format).</TD>
><TD><i>none</i> (engine dependent)</TD>
></TR>
><TR>
><TD>sql_user</TD><TD>SQL plugin</TD>
><TD>Username to use for authentication to the SQL server.</TD>
><TD><i>none</i> (engine dependent)</TD>
></TR>
><TR>
><TD>sql_passwd</TD><TD>SQL plugin</TD>
><TD>Password to use for authentication to the SQL server.</TD>
><TD><i>none</i> (engine dependent)</TD>
></TR>
><TR>
><TD>sql_database</TD><TD>SQL plugin</TD>
><TD>Name of the database which contains the auxiliary properties.</TD>
><TD><i>none</i> (engine dependent)</TD>
></TR>
><TR>
><TD>sql_select</TD><TD>SQL plugin</TD>
><TD>SELECT statement to use for fetching properties.  This option is
><b>required</b> in order to use the SQL plugin.</TD>
><TD><i>none</i></TD>
></TR>
><TR>
><TD>sql_insert</TD><TD>SQL plugin</TD>
><TD>INSERT statement to use for creating properties for new users.</TD>
><TD><i>none</i></TD>
></TR>
><TR>
><TD>sql_update</TD><TD>SQL plugin</TD>
><TD>UPDATE statement to use for modifying properties.</TD>
><TD><i>none</i></TD>
></TR>
><TR>
><TD>sql_usessl</TD><TD>SQL plugin</TD>
><TD>When set to 'yes', 'on', '1' or 'true', a secure connection will
>be made to the SQL server.</TD>
><TD><tt>no</tt></TD>
></TR>
><TR>
><TD>srp_mda</TD><TD>SRP</TD>
><TD>Message digest algorithm for SRP calculations
>(possible values: 'md5', 'sha1', 'rmd160')</TD><TD><tt>sha1</tt></TD>
></TR>
><TR>
><TD>srvtab</TD><TD>KERBEROS_V4</TD>
><TD>Location of the srvtab file</TD><TD><tt>/etc/srvtab</tt> (system
>dependant)</TD>
></TR>
></TABLE>
>
><h2>Notes on SQL auxprop options</h2>
>
><p>The <tt>sql_insert</tt> and <tt>sql_update</tt> options are
>optional and are only needed if you wish to allow the SASL library
>(e.g., saslpasswd2) and plugins (e.g., OTP) to write properties to the
>SQL server.  If used, both statements MUST be provided so that
>properties can be added, changed and deleted.
><font color=red>NOTE: The columns for writable properites MUST accept NULL values.</font>
>
><p>The SQL statements provided in the <tt>sql_select</tt>,
><tt>sql_insert</tt> and <tt>sql_update</tt> options can contain
>arguments which will be substituted with the appropriate values.  The
>valid arguments are:
>
><DL compact>
><DT><tt>%u</tt> <DD>Username whose properties are being fetched/stored.
>
><DT><tt>%p</tt> <DD>Name of the property being fetched/stored.  This could
>     technically be anything, but SASL authentication will try
>     userPassword and cmusaslsecretMECHNAME (where MECHNAME is the
>     name of a SASL mechanism).
>
><DT><tt>%r</tt> <DD>Realm to which the user belongs.  This could be the
>     kerberos realm, the FQDN of the computer the SASL application is
>     running on or whatever is after the @ on a username.  (read the
>     realm documentation).
>
><DT><tt>%v</tt> <DD>Value of the property being stored (INSERT or
>     UPDATE only!). This could technically be anything depending on
>     the property itself, but is generally a userPassword.
></DL>
>
><font color=red>NOTE: DO NOT put quotes around the entire SQL
>statement, but each individual %u, %r and %v argument MUST be
>quoted.</font>
>
>
><h3>Examples:</h3>
>
><pre>
>     <tt>sql_select: SELECT %p FROM user_table WHERE username = '%u' and realm = '%r'</tt>
></pre>
>
>     would send the following statement to SQL for user "bovik" and
>     the default realm for the machine "madoka.surf.org.uk":
>
><pre>
>     <tt>SELECT userPassword FROM user_table WHERE username = 'bovik' and
>     realm = 'madoka.surf.org.uk';</tt>
>
>
></pre>
>
><pre>
>     <tt>sql_insert: INSERT INTO user_table (username, realm, %p) VALUES ('%u', '%r', '%v')</tt>
>
></pre>
>
>   would generate the following statement to SQL for user "bovik" in
>   realm "madoka.surf.org.uk" with userPassword "wert":
>
><pre>
>     <tt>INSERT INTO user_table (username, realm, userPassword) VALUES
>     ('bovik', 'madoka.surf.org.uk', 'wert');</tt>
>
>
></pre>
>
><p>Note that all substitutions do not have to be used. For instance,
><pre>
>     <tt>SELECT password FROM auth WHERE username = '%u'</tt>
></pre>
>is a valid value for <tt>sql_select</tt>.
>
><h2>Notes on LDAPDB auxprop options</h2>
>
><p>
></p>
>
><p>Unlike other LDAP-enabled plugins for other services that are common
>on the web, this plugin does not require you to configure DN search
>patterns to map usernames to LDAP DNs. This plugin requires SASL name
>mapping to be configured on the target slapd. This approach keeps the
>LDAP-specific configuration details in one place, the slapd.conf, and
>makes the configuration of remote services much simpler.</p>
>
><p>This plugin is not for use with slapd itself. When OpenLDAP is
>built with SASL support, slapd uses its own internal auxprop module.
>By default, without configuring anything else, slapd will fail to load
>the ldapdb module when it's present. This is as it should be. If you
>don't like the "auxpropfunc: error -7" message that is sent to syslog
>by slapd, you can stop it by creating /usr/lib/sasl2/slapd.conf with:
>
>    <pre>auxprop_plugin: slapd</pre>
>
>which will force the SASL library to ignore all other auxprop modules.</p>
>
><h3>Examples:</h3>
>
><pre>
>ldapdb_uri: ldap://ldap.example.com
>ldapdb_id: root
>ldapdb_pw: secret
>ldapdb_mech: DIGEST-MD5
></pre>
>
><p>The LDAP server must be configured to map the SASL authcId "root" into a DN
>that has proxy authorization privileges to every account that is allowed to
>login to this server. (See the OpenLDAP Admin Guide section 10 for
>details.)</p>
>
><pre>
>ldapdb_uri: ldapi://
>ldapdb_mech: EXTERNAL
></pre>
>
><p>This configuration assumes an LDAP server is on the same server that is
>using SASL and the underlying OS is *NIX based (ldapi:// requires UNIX domain
>sockets).  This is fast and secure, and needs no username or password to be
>stored.  The slapd.conf will need to map these usernames to LDAP DNs:
>
><pre>
>sasl-regexp uidNumber=(.*)\\+gidNumber=(.*),cn=peercred,cn=external,cn=auth
>    ldap:///dc=example,dc=com??sub?(&(uidNumber=$1)(gidNumber=$2))
></pre>
>
><pre>
>sasl-regexp uid=(.*),cn=external,cn=auth
>    ldap:///dc=example,dc=com??sub?(uid=$1)
></pre>
>
></p>
>
><hr>
>Back to the <A href=index.html>index</a>
>
></body>
></html>
>
><HTML><HEAD>
><title>SASL Plugin Programmer's Guide</title>
>
></HEAD>
><BODY>
><h1>SASL Plugin Programmer's Guide</h1>
>
><h3>NOTE: This is a work in progress. Any contributions would be
><i>very</i> appreciated</h3>
>
><ul><h2>Contents</h2>
>  <li><a href="#intro">Introduction</a></li>
>  <ul>
>    <li><a href="#about_this_guide">About this Guide</A></li>
>    <li><a href="#about_sasl">What is SASL</A></li>
>  </ul>
>  <li><a href="#common">Common Section</a></li>
>  <ul>
>    <li><a href="#overview">Overview of Plugin Programming</a></li>
>    <li><a href="#sasl_utils_t">Use of sasl_utils_t</a></li>
>    <li><a href="#error_reporting">Error Reporting</a></li>
>    <li><a href="#memory">Memory Allocation</a></li>
>    <li><a href="#cslssl">Client Send First / Server Send Last</a></li>
>  </ul>
>  <li><a href="#client">Client Plugins</a></li>
>  <li><a href="#server">Server Plugins</a></li>
>  <li><a href="#canon_user">User Canonicalization (canon_user) Plugins</a></li>
>  <li><a href="#auxprop">Auxiliary Property (auxprop) Plugins</a></li>
></ul>
>
><a name="intro"><h2>Introduction</h2></a>
>
>    <a name="about_this_guide"><h3>About this Guide</h3></a>
>
>    <p>This guide gives a <i>very</i> brief overview on the things that one
>       needs to know to write a mechanism for the SASLv2 API (and thus
>       Cyrus SASLv2).  Note that this page is a brief overview <i>only</i>
>       and that the authoritative documentation are the header files
>       included in the SASL distribution.  If you have any questions, please
>       feel free to contact the Cyrus development team at
>       <a href="mailto:cyrus-bugs@andrew.cmu.edu"><i>cyrus-bugs@andrew.cmu.edu
>	</i></a> or the cyrus-sasl mailing list at
>       <a href="mailto:cyrus-sasl@andrew.cmu.edu"><i>cyrus-sasl@andrew.cmu.edu
>	</i></a>.</p>
>
>    <p>Please note that this guide is only intended for developers looking
>       to write mechanisms for the SASLv2 API, and that application programmers
>       should be reading <a href="programming.html">this document</a> instead.
>    </p>
>   
>    <a name="about_sasl"><h3>What is SASL?</h3></a>
>    <p>A description of SASL is covered in detail in the
>      <a href="programming.html">programmer's guide</a>, which mechanism
>      developers should probably read first anyway to become familiar
>      with development using the SASL library.
>    </p>
>    
><a name="common"><h2>Common Section</h2></a>
>    <a name="overview"><h3>Overview of Plugin Programming</h3></a>
>
>    <p>The basic idea behind programming plugins for Cyrus SASL rests in
>       the ability to dlopen a shared library.  Thus, all plugins should
>       be shared libraries.  It is recommended that they are libtool
>       libraries for portability reasons (Cyrus SASL parses .la files to
>       get the appropriate name to dlopen), but they can have an extention
>       of .so as well.</p>
>    <p>All plugins should live in the same directory
>       (generally /usr/lib/sasl2), which the glue code (that is, the interface
>       layer that sits between the plugins and the application) scans
>       when one of the init functions (sasl_server_init or sasl_client_init)
>       is called.  Cyrus SASL then attempts to open each library and
>       run an initialization function.  If the initialization function
>       succeeds, and the versions match, then the glue code determines
>       that the load was successful and the plugin is available for use.</p>
>    <p>There are serveral types of plugins (note that a given plugin library
>       may contain any or all of the following in combination, though
>       such a plugin would be a beast!):</p>
>    <ul>
>      <li><b>Mechanism Plugins</b> - These plugins implement mechanisms
>	for authentication, and are the majority of the plugins included
>	with Cyrus SASL.  Generally implementing both a client and a server
>	side they take care of the authentication process.</li>
>      <li><b>User Canonicalization Plugins</b> - These plugins enable differing
>	ways of canonicalizing authentication and authorization IDs.</li>
>      <li><b>Auxiliary Property Plugins</b> - These plugins allow auxilliary
>	properties about user accounts to be looked up, such as passwords.
>	Cyrus SASL includes a plugin to read sasldb files, for example.</li>
>    </ul>
>      
>    <a name="sasl_utils_t"><h3>Use of sasl_utils_t</h3></a>
>
>    <p>Because of the way that shared library plugins are loaded for both
>       speed and namespace reasons, the symbol tables are not shared across
>       plugins.  Thus, the only interface that the plugin should assume it
>       has to the outside world is through the <tt>sasl_utils_t</tt> structure (or
>       through links that it specifically requires).  Likewise, the glue code
>       has no (and will use no) interface into the plugin other than the
>       contents of the structures that are passed back to it by the
>       initialization function.</p>
>    <p>This should be stressed again: do not assume you have access to any
>       functions except through links that your library explicitly makes
>       or through what is provided via the <tt>sasl_utils_t</tt> structure.</p>
>
>    <a name="error_reporting"><h3>Error Reporting</h3></a>
>    <p>Error reporting is very important for failed authentication tracking
>       and helping to debug installations or authentication problems.  For
>       that reason, in addition to the standard SASL return codes, the
>       glue code provides an interface to its seterror function (via
>       <tt>sasl_utils_t</tt>).  This function sets detailed error information for
>       a given connection.</p>
>    <p><i>In order to ensure consistency of this information, it is the
>	responsibility of the deepest function with access to the sasl_conn_t
>	make the call to set the errdetail string.</i></p>
>
>    <a name="memory"><h3>Memory Allocation</h3></a>
>    <p>Memory allocation in SASLv2 follows the simple paradigm that if you
>      allocate it, you free it.  This improves portability, and allows
>      for a large performance improvement over SASLv1.  To prevent memory
>      leaks (especially in the mechanism plugins), please ensure that you
>      follow this paradigm.</p>
>
>    <a name="cslssl"><h3>Client Send First / Server Send Last</h3></a>
>    <p>Mechanism plugins used to have to worry about the situation
>      where they needed clients to send first (or server to send last), yet
>      the protocol did not support it.  Luckily, this is now handled by
>      the glue code, provided that the plugin declares the appropriate flags
>      in the structure returned by its init function.  Thus, the step functions
>      will not have to worry about these issues and can be implemented
>      knowing they will be called only when the application actually has
>      data for them and/or will allow them to send data.  These flags are as
>      follows:</p>
>    <ul>
>      <li><B>SASL_FEAT_WANT_CLIENT_FIRST</B>: The mechanism has the client
>	side send first always.  (e.g. PLAIN)</li>
>      <li><B>SASL_FEAT_SERVER_FIRST</B>: The mechanism has the server side
>	send first always.  (e.g. CRAM-MD5)</li>
>    </ul>
>
><p>If neither flag is set, the mechanism will handle the client-send
>first situation internally, because the client may or may not send
>first.  (e.g. DIGEST-MD5).  In this case, the plugin must
>intelligently check for the presence (or absence) of clientin/serverin
>data.  Note that the optional client send-first is only possible when the
>protocol permits an initial response.
>
><p>The server send last situation is handled by the plugin intelligently
>setting *serverout when the step function returns SASL_OK.  For mechanisms
>which never send last (e.g. PLAIN), *serverout must be set to NULL.  For
>mechanisms which always send last (e.g. DIGEST-MD5), *serverout must
>point to the success data.  For mechanisms in which the server may or
>may not send last (e.g. SRP), *serverout must be set accordingly.
>
><a name="client"><h2>Client Plugins</h2></a>
>    <p>Client-side mechanism plugins are generally included in the same
>       plugin with their <a href="#server">server</a> counterpart, though
>       this is not a requirement.  They take care of the client-side of the
>       SASL negotiation.  For a simple example, see the ANONYMOUS plugin.</p>
>    <p>Client plugins must export <tt>sasl_client_plug_init</tt> which returns
>       a <tt>sasl_client_plug_t</tt> in order to load.  The structure has
>       several functional members and a global context (which applies to
>       all connections using the plugin).  The important ones are described
>       briefly here.</p>
>    <ul>
>      <li><b>mech_new</b> - Called at the beginning of each connection,
>	(on a call to sasl_client_start),
>	mech_new does mechanism-specific initialization, and if necessary
>	allocates a connection context (which the glue code keeps track
>	of for it).  mech_new does not actually send any data to the client,
>        it simply allocates the context.</li>
>      <li><b>mech_step</b> - Called from <tt>sasl_client_start</tt> and
>	<tt>sasl_client_step</tt>, this function does the actual work of
>	the client
>	side of the authentication.  If authentication is successful, it
>	should return SASL_OK, otherwise it should return a valid SASL
>	error code (and call seterror).  This should also set up the
>        oparams structure before returning SASL_OK, including any
>        security layer information (in the way of callbacks).  Note
>        that as soon as the client has both the authentication and
>        authorization IDs, it MUST call the canon_user function provided
>        in its params structure (for both the authentication and
>	authorization IDs, with SASL_CU_AUTHID and SASL_CU_AUTHZID
>        respectively).</li>
>      <li><b>mech_dispose</b> - Called to dispose of a connection context.
>	This is only called when the connection will no longer be used
>        (e.g. when <tt>sasl_dispose</tt> is called)</li>
>      <li><b>mech_free</b> - Called when the sasl library is shutting down
>	(by <tt>sasl_done</tt>).
>	Intended to free any global state of the plugin.</li>
>    </ul>
><a name="server"><h2>Server Plugins</h2></a>
>    <p>Server-side mechanism plugins are generally included in the same
>       plugin with their <a href="#client">client</a> counterpart, though
>       this is not a requirement.  They take care of the server-side of the
>       SASL negotiation, and are generally more complicated than their
>       client-side counterparts.  For a simple example, see the ANONYMOUS
>       plugin.</p>
>    <p>Server plugins must export <tt>sasl_server_plug_init</tt> which returns
>       a <tt>sasl_server_plug_t</tt> in order to load.  The structure has
>       several functional members and a global context (which applies to
>       all connections using the plugin).  The important ones are described
>       briefly here.</p>
>    <ul>
>      <li><b>mech_new</b> - Called at the beginning of each connection,
>	(on a call to sasl_client_start),
>	mech_new does mechanism-specific initialization, and if necessary
>	allocates a connection context (which the glue code keeps track
>	of for it).  mech_new does not actually send any data to the client,
>        it simply allocates the context.</li>
>      <li><b>mech_step</b> - Called from <tt>sasl_server_start</tt> and
>	<tt>sasl_server_step</tt>, this function does the actual work of
>	the server
>	side of the authentication.  If authentication is successful, it
>	should return SASL_OK, otherwise it should return a valid SASL
>	error code (and call seterror).  This should also set up the
>        oparams structure before returning SASL_OK, including any
>        security layer information (in the way of callbacks and SSF
>	information).  Also, as soon
>        as the mechanism has computed both the authentication and the
>        authorization IDs, it MUST call the canon_user function provided
>        in the server params structure (for both the authentication and
>	authorization IDs, with SASL_CU_AUTHID and SASL_CU_AUTHZID
>        respectively).  This action will also fill in its
>        propctx, so any auxiliary property <i>requests</i>
>        (for example, to lookup
>        the password) should be done before the request to canonicalize
>        the authentication id.  Authorization ID lookups do not occur until
>        after the plugin returns success to the SASL library.<p>
>
>        Before returning SASL_OK, <tt>mech_step</tt> must fill in the
>        oparams fields for which it is responsible, that is, <tt>doneflag</tt>
>        (set to 1 to indicate a complete exchange), <tt>maxoutbuf</tt>, or
>        the maximum output size it can do at once for a security layer,
>        <tt>mech_ssf</tt> or the supplied SSF of the security layer,
>        and <tt>encode</tt>, <tt>decode</tt>, <tt>encode_context</tt>,
>	and <tt>decode_context</tt>,
>        which are what the glue code will call on calls to <tt>sasl_encode</tt>,
>	<tt>sasl_encodev</tt>, and <tt>sasl_decode</tt>.</li>
>      <li><b>mech_dispose</b> - Called to dispose of a connection context.
>	This is only called when the connection will no longer be used
>        (e.g. when <tt>sasl_dispose</tt> is called)</li>
>      <li><b>mech_free</b> - Called when the sasl library is shutting down
>	(by <tt>sasl_done</tt>).
>	Intended to free any global state of the plugin.</li>
>      <li><b>setpass</b> - Called to set a user's password.  This allows
>	mechanisms to support their own internal password or secret
>	database.</li>
>      <li><b>mech_avail</b> - Called by the first call to
>	<tt>sasl_listmech</tt>,
>	it checks to see if the mechanism is available for the given
>	user, and MAY allocate a connection context (thus avoiding
>	a call to <tt>mech_new</tt>).  However it should not do this
>	without significant performance benefit as it forces the glue
>	code to keep track of extra contexts that may not be used.</li>
>    </ul>
><a name="canon_user"><h2>User Canonicalization (canon_user) Plugins</h2></a>
>    <p>User Canonicalization plugins allow for nonstandard ways of
>       canonicalizing the username.  They are subject to the following
>       requirements:</p>
>    <ul>
>      <li>They must copy their output into the provided output buffers.</li>
>      <li>The output buffers may be the same as the input buffers.</li>
>      <li>They must function for the case which is only an authentication
>	  ID (flags == SASL_CU_AUTHID) or only an authorization ID
>	  (flags == SASL_CU_AUTHZID) or both
>	  (flags == SASL_CU_AUTHID | SASL_CU_AUTHZID)
>    </ul>
>    <p>User canonicalization plugins must export a <tt>sasl_canonuser_init</tt>
>       function which returns a <tt>sasl_canonuser_plug_t</tt> in order
>       to load successfully.  They must implement at least one of
>       the <tt>canon_user_client</tt> or <tt>canon_user_server</tt> members
>       of the <tt>sasl_canonuser_plug_t</tt>.  The INTERNAL canon_user plugin
>       that is inside of the glue code implements both in the same way.</p>
><a name="auxprop"><h2>Auxiliary Property (auxprop) Plugins</h2></a>
>    <p>Perhaps the most exciting addition in SASLv2, Auxprop plugins
>       allow for an easy way to perform password and secret lookups (as well
>       as other information needed for authentication and authorization)
>       from directory services, and in the same request allow the application
>       to receive properties that it needs to provide the service.
>    </p>
>    <p>Auxprop plugins need to export the <tt>sasl_auxprop_init</tt> function
>       and pass back a <tt>sasl_auxprop_plug_t</tt> in order to load
>       successfully.  The sasldb plugin included with the Cyrus SASL
>       distribution would be a good place to start.</p>
>    <p>Interfacing with property contexts is extremely well documented in
>       <tt>prop.h</tt> and so that is omitted here.  The only important
>       note is to be sure that you are using the interfaces provided
>       through the <tt>sasl_utils_t</tt> structure and not calling
>       the functions directly.</p>
>    <p>To successfully implement an auxprop plugin there is only one
>       required function to implement, that is the <tt>auxprop_lookup</tt>
>       member of the <tt>sasl_auxprop_plug_t</tt>.  This is called
>       just after canonicalization of the username, with the canonicalized
>       username.  It can then do whatever lookups are necessary for any
>       of the requested auxiliary properties.</p>
></p>
><hr>
>Back to the <A href=index.html>index</a>
>
></body>
></html>
><!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
><html>
><head>
><meta name="generator" content="HTML Tidy, see www.w3.org">
><title>SASL Application Programmer's Guide</title>
></head>
><body>
><h1>SASL Application Programmer's Guide</h1>
>
><h3>NOTE: This is a work in progress. Any contributions would be
><i>very</i> appreciated</h3>
>
><h2>Contents</h2>
>
><ul>
><li><a href="#intro">Introduction</a> 
>
><ul>
><li><a href="#about_this_guide">About this guide</a></li>
>
><li><a href="#what_is_sasl">What is SASL?</a></li>
></ul>
></li>
>
><li><a href="#background">Background</a> 
>
><ul>
><li><a href="#world_before">How did the world work before
>SASL?</a></li>
>
><li><a href="#sasl_rescue">SASL to the rescue!</a></li>
></ul>
></li>
>
><li><a href="#briefly">Briefly</a> 
>
><ul>
><li><a href="#what_good_for">What is the Cyrus SASL library good
>for?</a></li>
>
><li><a href="#what_do">What does the Cyrus SASL library
>do?</a></li>
>
><li><a href="#what_doesnt">What doesn't the Cyrus SASL library
>do?</a></li>
></ul>
></li>
>
><li><a href="#client_only">Client-only Section</a> 
>
><ul>
><li><a href="#client_typical">A typical interaction from the
>client's perspective</a></li>
>
><li><a href="#client_code">How does this look in code?</a></li>
>
><li><a href="#sasl_client_init">sasl_client_init</a></li>
>
><li><a href="#sasl_client_new">sasl_client_new</a></li>
>
><li><a href="#sasl_client_start">sasl_client_start</a></li>
>
><li><a href="#sasl_client_step">sasl_client_step</a></li>
></ul>
></li>
>
><li><a href="#server_section">Server-only Section</a> 
>
><ul>
><li><a href="#server_typical">A typical interaction from the
>server's perspective</a></li>
>
><li><a href="#server_code">How does this look in code?</a></li>
>
><li><a href="#sasl_server_init">sasl_server_init</a></li>
>
><li><a href="#sasl_server_new">sasl_server_new</a></li>
>
><li><a href="#sasl_server_start">sasl_server_start</a></li>
>
><li><a href="#sasl_server_step">sasl_server_step</a></li>
>
><li><a href="#sasl_listmech">sasl_listmech</a></li>
>
><li><a href="#sasl_checkpass">sasl_checkpass</a></li>
></ul>
></li>
>
><li><a href="#common_section">Common Section</a> 
>
><ul>
><li><a href="#callbacks_interactions">Callbacks and
>Interaction</a></li>
>
><li><a href="#layers">Security layers</a></li>
></ul>
></li>
>
><li><a href="#example_section">Example applications that come with
>the Cyrus SASL library</a> 
>
><ul>
><li><a href="#sample_client"><tt>sample-client</tt> and
><tt>sample-server</tt></a></li>
>
><li><a href="#cyrus_imapd">Cyrus imapd v2.1.0 or later</a></li>
>
><li><a href="#imtest"><tt>imtest</tt>, from cyrus imapd 2.1.0 or
>later</a></li>
></ul>
></li>
>
><li><a href="#random_things">Miscellaneous Information</a> 
>
><ul>
><li><a href="#empty_exchanges">Empty exchanges</a></li>
></ul>
></li>
></ul>
>
><h2><a name="intro">Introduction</a></h2>
>
><h3><a name="about_this_guide">About this Guide</a></h3>
>
><p>This guide gives a tutorial on the use of the Cyrus SASL library
>for a client or server application. It complies with versions
>including and after 2.0.0. The following pages should only be
>considered a guide, not the final word on programming with the
>Cyrus SASL library. Consult the header files in the distribution in
>the case of ambiguities.</p>
>
><h3><a name="what_is_sasl">What is SASL?</a></h3>
>
><p>SASL stands for Simple Authentication Security Layer and is
>explained in <a href="http://ftp.ietf.org/rfc/rfc2222.txt">RFC
>2222</a>. That document is very difficult to understand however and
>it should be unnecessary to consult it.</p>
>
><h2><a name="background">Background</a></h2>
>
><h3><a name="world_before">How did the world work before
>SASL?</a></h3>
>
><p>Before SASL, when a new protocol was written which required
>authentication (users proving who they are to an entity), the
>protocol had to allow explicitly for each individual authentication
>mechanism. There had to be a distinct way to say "I want to log in
>with Kerberos V4". There had to be another distinct way to say "I
>want to log in with CRAM-MD5". There had to be yet a different way
>to say "I want to log in anonymously," and so on. This was
>non-ideal for both the protocol and application writers.</p>
>
><p>Additionally, many programmers were not very familiar with
>security, so the protocol did support many mechanisms, or worse,
>they were supported incorrectly. Moreover, when a new
>authentication method was invented the protocol needed to be
>modified to support that mechanism.</p>
>
><p>This system also was not ideal for application writer. She had
>to have a special case for each mechanism she wished her
>application to support. Also, the mechanisms were difficult to
>implement. Even with a good library, an understanding of how the
>mechanism worked was still necessary. Finally if an application
>used more than one protocol (for example a mail client might use
>IMAP, POP, and SMTP) then "Kerberos V4 for IMAP", "Kerberos V4 for
>POP", "Kerberos V4 for SMTP", "CRAM MD5 for IMAP", "CRAM-MD5 for
>POP", etc... would need to be written. This could quickly create a
>huge number of different mechanism-protocol pairs to implement.</p>
>
><h3><a name="sasl_rescue">SASL to the rescue!</a></h3>
>
><p>SASL hopefully solves all these problems. In practice it makes
>many of them easier to deal with.</p>
>
><p>Protocol designers simply have to support SASL (in particular
>RFC 2222). Consequently, any mechanism that supports SASL (just
>about anything you would want to use does now) is supported by the
>protocol. If a new authentication mechanism is invented the
>protocol automatically supports it without any modifications.</p>
>
><p>Application writers, instead of having to support every
>mechanism for every protocol, only need to support SASL for every
>protocol. Application writers do not need to understand the
>authentication mechanisms at all: the SASL library handles all
>that. Also with the Cyrus SASL library if a new mechanism is
>invented you do not have rewrite your application at all. You may
>not even have to restart your application if it is a long running
>process. This is because the Cyrus SASL library loads each
>mechanism from a shared library. Simply copying a shared library
>into a directory will magically make your application support a new
>mechanism.</p>
>
><p>Cyrus SASL version 2 supports a much improved API over version
>1, that allows for much smarter and faster memory allocation for
>the mechanisms as well as the applications. It is also provides for
>several new types of plugins to allow for greater overall
>flexibility. Unfortunately, though similar, this new API is
>completely incompatible with the old API, and applications will
>need to be rewritten.</p>
>
><h2><a name="briefly">Briefly</a></h2>
>
><h3><a name="what_good_for">What is the Cyrus SASL library good
>for?</a></h3>
>
><p>The Cyrus SASL library is good for applications that wish to use
>protocols that support SASL authentication. An non-exhaustive list
>of these are: IMAP, SMTP, ACAP, and LDAP. Also if you are making a
>proprietary system and wish to support authentication it is a good
>way of supporting many different authentication types.</p>
>
><h3><a name="what_do">What does the Cyrus SASL library do?</a></h3>
>
><p>From a client point of view, the Cyrus SASL library, given a
>list of mechanisms the server supports it will decide the best
>mechanism to use and tell you what to send to the server at each
>step of the authentication. From a server perspective, it handles
>authentication requests from clients.</p>
>
><h3><a name="what_doesnt">What doesn't the Cyrus SASL library
>do?</a></h3>
>
><p>The Cyrus SASL library is neither network nor protocol aware. It
>is up to the application to send the data over the wire as well as
>to send the data in the protocol specific manner. With IMAP this
>means putting it in the form: <tt>+ [base64'ed data]\r\n</tt>. LDAP
>just sends data in binary via bind requests. The Cyrus SASL library
>has utility base64 encode and decode routines to help with
>this.</p>
>
><h2><a name="client_section">Client-only Section</a></h2>
>
><h3><a name="client_typical">A typical interaction from the
>client's perspective</a></h3>
>
><ol>
><li>A client makes a few calls (explained later) to initialize
>SASL.</li>
>
><li>Every time the client application makes a new connection it
>should make a new context that is kept for the life of the
>connection.</li>
>
><li>Ask the server for the list of supported mechanisms</li>
>
><li>Feed this list to the library</li>
>
><li>Start the authentication with the mechanism the library
>chose</li>
>
><li>The server will return some bytes</li>
>
><li>Give these to the library</li>
>
><li>The library returns some bytes to the application</li>
>
><li>Application sends these bytes over the network</li>
>
><li>repeat the last 4 steps until the server tells you that the
>authentication is completed</li>
></ol>
>
><h3><a name="client_code">How does this look in code</a></h3>
>
><b>Initialize the library</b>. (done once). 
>
><pre>
>    
>        int result;
>
>        /* attempt to start sasl 
>         * See the section on Callbacks and Interactions for an 
>         * explanation of the variable callbacks
>         */ 
>
>        result=sasl_client_init(callbacks);
>            
>            /* check to see if that worked */
>            if (result!=SASL_OK) [failure]
>    
></pre>
>
><b>For every network connection, make a new SASL connection</b>: 
>
><pre>
>       
>            /* The SASL context kept for the life of the connection */
>            sasl_conn_t *conn;
>
> 
>            /* client new connection */
>            result=sasl_client_new("imap",     /* The service we are using */
>                       serverFQDN, /* The fully qualified domain
>                                                  name of the server we're
>                                                  connecting to */
>                       NULL, NULL, /* Local and remote IP
>                                                  address strings
>                                                  (NULL disables mechanisms
>                                                   which require this info)*/
>                                   NULL,       /* connection-specific
>                                                  callbacks */
>                       0,          /* security flags */
>                       &amp;conn);     /* allocated on success */
>
>            /* check to see if that worked */
>            if (result!=SASL_OK) [failure]
>
>     
></pre>
>
>Next get the list of SASL mechanisms the server supports. This is
>usually done through a capability command. Format the list as a
>single string separated by spaces. Feed this string into SASL to
>begin the authentication process. 
>
><pre>
>       
>            sasl_interact_t *client_interact=NULL;
>            const char *out, *mechusing;
>            unsigned outlen;
>
>            do {
>
>              result=sasl_client_start(conn,      /* the same context from
>                                                     above */ 
>                                       mechlist,  /* the list of mechanisms
>                                                     from the server */
>                                       &amp;client_interact, /* filled in if an
>                                                            interaction is needed */
>                       &amp;out,      /* filled in on success */
>                                       &amp;outlen,   /* filled in on success */
>                       &amp;mechusing);
>
>              if (result==SASL_INTERACT)
>              {
>                 [deal with the interactions. See interactions section below]
>              }
>
>
>           } while (result==SASL_INTERACT); /* the mechanism may ask us to fill
>                                               in things many times. result is 
>                                               SASL_CONTINUE on success */
>           if (result!=SASL_CONTINUE) [failure]
>
>       
></pre>
>
>Note that you do not need to worry about the allocation and freeing
>of the output buffer out. This is all handled inside of the
>mechanism. It is important to note, however, that the output buffer
>is not valid after the next call to <tt>sasl_client_start</tt> or
><tt>sasl_client_step</tt>.
>
><p>If this is successful send the protocol specific command to
>start the authentication process. This may or may not allow for
>initial data to be sent (see the documentation of the protocol to
>see).</p>
>
><pre>
>        For IMAP this might look like:
>          {tag} "AUTHENTICATE" {mechusing}\r\n
>          A01 AUTHENTICATE KERBEROS_V4\r\n
>           
>        SMTP looks like:
>         "AUTH" {mechusing}[ {out base64 encoded}]
>         AUTH DIGEST-MD5 GHGJJGDDFDKHGHJG=
>       
></pre>
>
><br>
> <a name="client_authentication_step"><b>Check Results</b></a> <br>
> Next, read what the server sent back. It can be one of three
>things: 
>
><ol>
><li>Authentication failure. Authentication process is halted. This
>might look like <tt>A01 NO Authentication failure</tt> in IMAP or
><tt>501 Failed</tt> in SMTP. Either retry the authentication or
>abort.</li>
>
><li>Authentication success. We're now successfully authenticated.
>This might look like <tt>A01 OK Authenticated successful</tt> in
>IMAP or <tt>235 Authentication successful</tt> in SMTP. Go <a href=
>"#client_authentication_success">here</a></li>
>
><li>Another step in the authentication process is necessary. This
>might look like <tt>+ HGHDS1HAFJ=</tt> in IMAP or <tt>334
>PENCeUxFREJoU0NnbmhNWitOMjNGNndAZWx3b29kLmlubm9zb2Z0LmNvbT4=</tt>
>in SMTP. Note it could be an empty string such as <tt>+ \r\n</tt>
>in IMAP.</li>
></ol>
>
>Convert the continuation data to binary format (for example, this
>may include base64 decoding it). Perform another step in the
>authentication. 
>
><pre>
>              do {
>                result=sasl_client_step(conn,  /* our context */
>                        in,    /* the data from the server */
>                        inlen, /* it's length */
>                        &amp;client_interact,  /* this should be
>                                                              unallocated and NULL */
>                        &amp;out,     /* filled in on success */
>                        &amp;outlen); /* filled in on success */
>
>                if (result==SASL_INTERACT)
>                {
>                   [deal with the interactions. See below]
>                }
>
>
>              } while (result==SASL_INTERACT || result == SASL_CONTINUE);
>
>              if (result!=SASL_OK) [failure]
>              
>         
></pre>
>
>Format the output (variable out of length outlen) in the protocol
>specific manner and send it across the network to the server. <br>
> Goto <a href="#client_authentication_step">here</a> (this process
>repeats until authentication either succeeds or fails. <br>
><br>
><br>
> <a name="client_authentication_success"><b>Authentication
>Successful</b></a><br>
><br>
> 
>
><p>Before we're done we need to call sasl_client_step() one more
>time to make sure the server isn't trying to fool us. Some
>protocols include data along with the last step. If so this data
>should be used here. If not use a length of zero.</p>
>
><pre>
>                result=sasl_client_step(conn,  /* our context */
>                        in,    /* the data from the server */
>                        inlen, /* it's length */
>                        &amp;client_interact,  /* this should be unallocated and NULL */
>                        &amp;out,     /* filled in on success */
>                        &amp;outlen); /* filled in on success */
>
>                if (result!=SASL_OK) [failure]
>       
></pre>
>
><p>Congratulations. You have successfully authenticated to the
>server.</p>
>
><p>Don't throw away the SASL connection object (sasl_conn_t *) yet
>though. If a security layer was negotiated you will need it to
>encode and decode the data sent over the network.</p>
>
><br>
> When you are finally done with connection to server, dispose of
>SASL connection. 
>
><pre>
>      
>               sasl_dispose(&amp;conn);
>
>         
></pre>
>
>If you are done with SASL forever (application quiting for
>example): 
>
><pre>
>            sasl_done();         
>     
></pre>
>
><h3>sasl_client_init</h3>
>
><pre>
>    int sasl_client_init(const sasl_callback_t *callbacks);
>   
></pre>
>
>Parameters: 
>
><ul>
><li>callbacks - List of callbacks. See Callbacks section</li>
></ul>
>
>This function initializes the SASL library. This must be called
>before any other SASL calls. See the callbacks section for complete
>description of callbacks. 
>
><h3>sasl_client_new</h3>
>
><pre>
>    int sasl_client_new(const char *service,
>                const char *serverFQDN,
>                        const char *iplocalport,
>                        const char *ipremoteport,
>                const sasl_callback_t *prompt_supp,
>                unsigned secflags,
>                sasl_conn_t **pconn);
>   
></pre>
>
>Parameters: 
>
><ul>
><li>service - the service name being used. This usually is the
>protocol name (e.g. "ldap")</li>
>
><li>serverFQDN - Fully qualified domain name of server</li>
>
><li>iplocalport and ipremoteport - a string of the format
>"a.b.c.d;p" detailing the local or remote IP and port, or NULL
>(which will disable mechanisms that require this information)</li>
>
><li>prompt_supp - List off callbacks specific to this
>connection</li>
>
><li>secflags - security flags ORed together requested (e.g.
>SASL_SEC_NOPLAINTEXT)</li>
>
><li>pconn - the SASL connection object allocated upon success</li>
></ul>
>
>This function creates a new SASL connection object. It should be
>called once for every connection you want to authenticate for. 
>
><h3>sasl_client_start</h3>
>
><pre>
>    int sasl_client_start(sasl_conn_t *conn,
>                  const char *mechlist,
>              sasl_interact_t **prompt_need,
>              const char **clientout,
>              unsigned *clientoutlen,
>              const char **mech);
>   
></pre>
>
>Parameters: 
>
><ul>
><li>conn - the SASL connection object gotten from
>sasl_client_new()</li>
>
><li>mechlist - the list of mechanisms to try (separated by
>spaces)</li>
>
><li>prompt_need - filled in when a SASL_INTERACT is returned</li>
>
><li>clientout - filled in upon success with data to send to
>server</li>
>
><li>clientoutlen - length of that data</li>
>
><li>mech - filled in with mechanism being used</li>
></ul>
>
>This function starts an authentication session. It takes a list of
>possible mechanisms (usually gotten from the server through a
>capability command) and chooses the "best" mechanism to try. Upon
>success clientout points at data to send to the server. 
>
><h3>sasl_client_step</h3>
>
><pre>
>    int sasl_client_step(sasl_conn_t *conn,
>         const char *serverin,
>         unsigned serverinlen,
>         sasl_interact_t **prompt_need,
>         const char **clientout,
>         unsigned *clientoutlen);
>   
></pre>
>
>Parameters: 
>
><ul>
><li>conn - the SASL connection object gotten from
>sasl_client_new()</li>
>
><li>serverin - data from the server</li>
>
><li>serverinlen - length of data from the server</li>
>
><li>prompt_need - filled in with a SASL_INTERACT is returned</li>
>
><li>clientout - filled in upon success with data to send to
>server</li>
>
><li>clientoutlen - length of that data</li>
></ul>
>
>This step preforms a step in the authentication process. It takes
>the data from the server (serverin) and outputs data to send to the
>server (clientout) upon success. SASL_CONTINUE is returned if
>another step in the authentication process is necessary. SASL_OK is
>returned if we're all done. 
>
><h2><a name="server_section">Server-only Section</a></h2>
>
><h3><a name="server_typical">A typical interaction from the
>server's perspective</a></h3>
>
>The server makes a few Cyrus SASL calls for initialization. When it
>gets a new connection it should make a new context for that
>connection immediately. The client may then request a list of
>mechanisms the server supports. The client also may request to
>authenticate at some point. The client will specify the mechanism
>it wishes to use. The server should negotiate this authentication
>and keep around the context afterwards for encoding and decoding
>the layers. 
>
><h3><a name="server_code">How does this look in code?</a></h3>
>
>Initialization (done once). The application name is used for
>reading configuration information. 
>
><pre>
>    
>    int result;
>
>    /* Initialize SASL */
>    result=sasl_server_init(callbacks,      /* Callbacks supported */
>                            "TestServer");  /* Name of the application */
>
>   
></pre>
>
>This should be called for each new connection. It probably should
>be called right when the socket is accepted. 
>
><pre>
>    sasl_conn_t *conn;
>    int result;
>
>    /* Make a new context for this connection */
>    result=sasl_server_new("smtp", /* Registered name of service */
>                   NULL, /* my fully qualified domain name; 
>                        NULL says use gethostname() */
>                           NULL, /* The user realm used for password
>                        lookups; NULL means default to serverFQDN
>                                    Note: This does not affect Kerberos */
>                       NULL, NULL, /* IP Address information strings */
>                   NULL, /* Callbacks supported only for this connection */
>                       0, /* security flags (security layers are enabled
>                               * using security properties, separately)
>               &amp;conn);
>
>   
></pre>
>
>When a client requests the list of mechanisms supported by the
>server. This particular call might produce the string: <i>"{PLAIN,
>KERBEROS_V4, CRAM-MD5, DIGEST-MD5}"</i> 
>
><pre>
>    result=sasl_listmech(conn,  /* The context for this connection */
>             NULL,  /* not supported */
>             "{",   /* What to prepend the string with */
>             ", ",  /* What to separate mechanisms with */
>             "}",   /* What to append to the string */
>             &amp;result_string, /* The produced string. */
>                         &amp;string_length, /* length of the string */
>                         &amp;number_of_mechanisms); /* Number of mechanisms in
>                                                the string */
>    
>   
></pre>
>
>When a client requests to authenticate: 
>
><pre>
>    int result;
>    const char *out;
>    unsigned outlen;
>
>    result=sasl_server_start(conn, /* context */
>                             mechanism_client_chose,
>                             clientin,    /* the optional string the client gave us */
>                             clientinlen, /* and it's length */
>                             &amp;out, /* The output of the library.
>                                      Might not be NULL terminated */
>                             &amp;outlen);
>
>    if ((result!=SASL_OK) &amp;&amp; (result!=SASL_CONTINUE))
>      [failure. Send protocol specific message that says authentication failed]
>    else if (result==SASL_OK)
>      [authentication succeeded. Send client the protocol specific message 
>       to say that authentication is complete]
>    else 
>      [send data 'out' with length 'outlen' over the network in protocol
>       specific format]
>   
></pre>
>
>When a response is returned by the client. <i>clientin</i> is the
>data from the client decoded from protocol specific format to a
>string of bytes of length <i>clientinlen</i>. This step may occur
>zero or more times. An application must be able to deal with it
>occurring an arbitrary number of times. 
>
><pre>
>    int result;
>   
>    result=sasl_server_step(conn,
>                            clientin,      /* what the client gave */
>                            clientinlen,   /* it's length */
>                            &amp;out,          /* allocated by library on success. 
>                                              Might not be NULL terminated */
>                            &amp;outlen);
>
>    if ((result!=SASL_OK) &amp;&amp; (result!=SASL_CONTINUE))
>      [failure. Send protocol specific message that says authentication failed]
>    else if (result==SASL_OK)
>      [authentication succeeded. Send client the protocol specific message 
>       to say that authentication is complete]
>    else 
>      [send data 'out' with length 'outlen' over the network in protocol
>       specific format]
>   
></pre>
>
>This continues until authentication succeeds. When the connection
>is concluded, make a call to <tt>sasl_dispose</tt> as with the
>client connection. 
>
><h3><a name="sasl_server_init">sasl_server_init</a></h3>
>
><pre>
>    int sasl_server_init(const sasl_callback_t *callbacks,
>                         const char *appname);
></pre>
>
>Parameters: 
>
><ul>
><li>callbacks - A list of callbacks supported by the application
>(see Interaction and Callbacks section)</li>
>
><li>appname - A string of the name of the application. This string
>is what is used when loading configuration options.</li>
></ul>
>
>sasl_server_init() initializes the session. This should be the
>first function called. In this function the shared library
>authentication mechanisms are loaded. 
>
><h3><a name="sasl_server_new">sasl_server_new</a></h3>
>
><pre>
>    int sasl_server_new(const char *service,
>            const char *serverFQDN,
>            const char *user_realm,
>                        const char *iplocalport,
>                        const char *ipremoteport,
>            const sasl_callback_t *callbacks,
>            unsigned secflags,
>            sasl_conn_t **pconn);
></pre>
>
>Parameters: 
>
><ul>
><li>service - The name of the service you are supporting. This
>might be "acap" or "smtp". This is used by Kerberos mechanisms and
>possibly other mechanisms. It is also used for PAM
>authentication.</li>
>
><li>serverFQDN - This is the fully qualified domain name of the
>server (i.e. your hostname); if NULL, the library calls
><tt>gethostbyname()</tt>.</li>
>
><li>user_realm - The realm the connected client is in. The Kerberos
>mechanisms ignore this parameter and default to the local Kerberos
>realm. A value of NULL makes the library default, usually to the
>serverFQDN; a value of "" specifies that the client should specify
>the realm; this also changes the semantics of "@" in a username for
>mechanisms that don't support realms.</li>
>
><li>iplocalport and ipremoteport - a string of the format
>"a.b.c.d;p" detailing the local or remote IP and port, or NULL
>(which will disable mechanisms that require this information)</li>
>
><li>callbacks - Additional callbacks that you wish only to apply to
>this connection.</li>
>
><li>secflags - security flags.</li>
>
><li>pconn - Context. Filled in on success.</li>
></ul>
>
><h3><a name="sasl_server_start">sasl_server_start</a></h3>
>
><pre>
>     int sasl_server_start(sasl_conn_t *conn,
>               const char *mech,
>               const char *clientin,
>               unsigned clientinlen,
>               const char **serverout,
>               unsigned *serveroutlen);
>   
></pre>
>
>Parameters: 
>
><ul>
><li>conn - The context for the connection</li>
>
><li>mech - The authentication mechanism the client wishes to try
>(e.g. <tt>KERBEROS_V4</tt>)</li>
>
><li>clientin - Initial client challenge bytes. Note: some protocols
>do not allow this. If this is the case passing NULL is valid</li>
>
><li>clientinlen - The length of the challenge. 0 is there is
>none.</li>
>
><li>serverout - allocated and filled in by the function. These are
>the bytes that should be encoded as per the protocol and sent over
>the network back to the client.</li>
>
><li>serveroutlen - length of bytes to send to client</li>
></ul>
>
>This function begins the authentication process with a client. If
>the program returns SASL_CONTINUE that means <tt>serverout</tt>
>should be sent to the client. If SASL_OK is returned that means
>authentication is complete and the application should tell the
>client the authentication was successful. Any other return code
>means the authentication failed and the client should be notified
>of this. 
>
><h3><a name="sasl_server_step">sasl_server_step</a></h3>
>
><pre>
>    int sasl_server_step(sasl_conn_t *conn,
>                 const char *clientin,
>                 unsigned clientinlen,
>                 const char **serverout,
>                 unsigned *serveroutlen);
>   
></pre>
>
>Parameters: 
>
><ul>
><li>conn - The context for the connection</li>
>
><li>clientin - Data sent by the client.</li>
>
><li>clientinlen - The length of the client data. Note that this may
>be 0</li>
>
><li>serverout - allocated and filled in by the function. These are
>the bytes that should be encoded as per the protocol and sent over
>the network back to the client.</li>
>
><li>serveroutlen - length of bytes to send to client. Note that
>this may be 0</li>
></ul>
>
>This function preforms a step of the authentication. This may need
>to be called an arbitrary number of times. If the program returns
>SASL_CONTINUE that means <tt>serverout</tt> should be sent to the
>client. If SASL_OK is returned that means authentication is
>complete and the application should tell the client the
>authentication was successful. Any other return code means the
>authentication failed and the client should be notified of this. 
>
><h3><a name="sasl_listmech">sasl_listmech</a></h3>
>
><pre>
>    int sasl_listmech(sasl_conn_t *conn,
>              const char *user,
>              const char *prefix,
>              const char *sep,
>              const char *suffix,
>              const char **result,
>              unsigned *plen,
>              unsigned *pcount);
>   
></pre>
>
>Parameters: 
>
><ul>
><li>conn - The context for this connection</li>
>
><li>user - Currently not implemented</li>
>
><li>prefix - The string to prepend</li>
>
><li>sep - The string to separate mechanisms with</li>
>
><li>suffix - The string to end with</li>
>
><li>result - Resultant string</li>
>
><li>plen - Number of characters in the result string</li>
>
><li>pcount - Number of mechanisms listed in the result string</li>
></ul>
>
>This function is used to create a string with a list of SASL
>mechanisms supported by the server. This string is often needed for
>a capability statement. 
>
><h3><a name="sasl_checkpass">sasl_checkpass</a></h3>
>
><pre>
>    int sasl_checkpass(sasl_conn_t *conn,
>                       const char *user,
>                       unsigned userlen,
>               const char *pass,
>               unsigned passlen);
>   
></pre>
>
>Parameters: 
>
><ul>
><li>conn - The context for this connection</li>
>
><li>user - The user trying to check the password for</li>
>
><li>userlen - The user length</li>
>
><li>pass - The password</li>
>
><li>passlen - The password length</li>
></ul>
>
>This checks a plaintext password <i>pass</i> for user <i>user</i>
>Some protocols have legacy systems for plaintext authentication
>where this might be used. 
>
><h2><a name="common_section">Common Section</a></h2>
>
><h3><a name="callbacks_interactions">Callbacks and
>Interactions</a></h3>
>
>When the application starts and calls sasl_client_init() you must
>specify for what data you support callbacks and/or interactions.
>These are for the library getting information needed for
>authentication from the application. This is needed for things like
>authentication name and password. If you do not declare supporting
>a callback you will not be able to use mechanisms that need that
>data. A callback is for when you have the information before you
>start the authentication. The SASL library calls a function you
>specify and your function fills in the requested information. For
>example if you had the userid of the user already for some reason.
>An interaction is usually for things you support but will need to
>ask the user for (e.g. password). sasl_client_start() or
>sasl_client_step() will return SASL_INTERACT. This will be a list
>of sasl_interact_t's which contain a human readable string you can
>prompt the user with, a possible computer readable string, and a
>default result. The nice thing about interactions is you get them
>all at once so if you had a GUI application you could bring up a
>dialog box asking for authentication name and password together
>instead of one at a time.
>
><p>Any memory that is given to the SASL library for the purposes of
>callbacks and interactions must persist until the exchange
>completes in either success or failure. That is, the data must
>persist until <tt>sasl_client_start</tt> or
><tt>sasl_client_step</tt> returns something other than
><tt>SASL_INTERACT</tt> or <tt>SASL_CONTINUE</tt>.</p>
>
><p><b>Memory management:</b>As in the rest of the SASLv2 API,
>whoever allocates the memory is responsible for freeing it. In
>almost all cases this should be fairly easy to manage, however a
>slight exception where the interaction sasl_interact_t structure is
>allocated and freed by the library, while the results are allocated
>and freed by the application. As noted above, however, <i>the
>results may not be freed until after the exchange completes, in
>either success or failure</i>.</p>
>
><p>For a detailed description of what each of the callback types
>are see the sasl.h file. Here are some brief explanations:</p>
>
><ul>
><li>SASL_CB_AUTHNAME - the name of the user authenticating</li>
>
><li>SASL_CB_USER - the name of the user acting for. (for example
>postman delivering mail for tmartin might have an AUTHNAME of
>postman and a USER of tmartin)</li>
>
><li>SASL_CB_PASS - password for AUTHNAME</li>
>
><li>SASL_CB_GETREALM - Realm of the server</li>
></ul>
>
>An example of a way to handle callbacks: 
>
><pre>
>    /* callbacks we support. This is a global variable at the 
>       top of the program */
>    static sasl_callback_t callbacks[] = {
>    {
>      SASL_CB_GETREALM, NULL, NULL  /* we'll just use an interaction if this comes up */
>    }, {
>      SASL_CB_USER, NULL, NULL      /* we'll just use an interaction if this comes up */
>    }, {
>      SASL_CB_AUTHNAME, &amp;getauthname_func, NULL /* A mechanism should call getauthname_func
>                                                   if it needs the authentication name */
>    }, { 
>      SASL_CB_PASS, &amp;getsecret_func, NULL      /* Call getsecret_func if need secret */
>    }, {
>      SASL_CB_LIST_END, NULL, NULL
>    }
>    };
>
>
>    static int getsecret_func(sasl_conn_t *conn,
>      void *context __attribute__((unused)),
>      int id,
>      sasl_secret_t **psecret)
>    {
>       [ask the user for their secret]
>
>       [allocate psecret and insert the secret]
>
>      return SASL_OK;
>    }
>
>    static int getauthname_func(void *context,
>                                int id,
>                                const char **result,
>                                unsigned *len)
>    {
>       if (id!=SASL_CB_AUTHNAME) return SASL_FAIL;
>
>       [fill in result and len]
>
>       return SASL_OK;
>     }
>
>    
>    in the main program somewhere
>    
>    sasl_client_init(callbacks);
>
>   
></pre>
>
><h3><a name="layers">Security layers</a></h3>
>
><p>All is well and good to securely authenticate, but if you don't
>have some sort of integrity or privacy layer, anyone can hijack
>your TCP session after authentication. If your application has
>indicated that it can support a security layer, one <i>might</i> be
>negotiated.</p>
>
><p>To set that you support a security layer, set a security
>property structure with <tt>max_ssf</tt> set to a non-zero
>number:</p>
>
><pre>
>   sasl_security_properties_t secprops;
>
>   secprops.min_ssf = 0;
>   secprops.max_ssf = 256;
>   secprops.maxbufsize = /* SEE BELOW */;
>
>   secprops.property_names = NULL;
>   secprops.property_values = NULL;
>   secprops.security_flags = SASL_SEC_NOANONYMOUS; /* as appropriate */
>
>   sasl_setprop(conn, SASL_SEC_PROPS, &amp;secprops);
></pre>
>
>The <tt>secprops</tt> variable will be copied during the call to
><tt>sasl_setprop</tt>, so you may free its memory immediately. The
><i>SSF</i> stands for <i>security strength factor</i> and is a
>rough indication of how "secure" the connection is. A connection
>supplying only integrity with no privacy would have an SSF of 1. A
>connection secured by 56-bit DES would have an SSF of 56. 
>
><p>To require a security layer, set <tt>min_ssf</tt> to the minimum
>acceptable security layer strength.</p>
>
><p>After authentication is successful, you can determine whether or
>not a security layer has been negotiated by looking at the SASL_SSF
>property:</p>
>
><pre>
>   const int *ssfp;
>
>   result = sasl_getprop(conn, SASL_SSF, (const **) &amp;ssfp);
>   if (result != SASL_OK) {
>       /* ??? */
>   }
>   if (*ssfp &gt; 0) {
>       /* yay, we have a security layer! */
>   }
></pre>
>
><p>If a security layer has been negotiated, your application must
>make use of the <tt>sasl_encode()</tt> and <tt>sasl_decode()</tt>
>calls. All output must be passed through <tt>sasl_encode()</tt>
>before being written to the wire; all input must be passed through
><tt>sasl_decode()</tt> before being looked at by the application.
>Your application must also be prepared to deal with
><tt>sasl_decode()</tt> not returning any data in the rare case that
>the peer application did something strange (by splitting a single
>SASL blob into two seperate TCP packets).</p>
>
><p>The only subtlety dealing with security layers is the maximum size
>of data that can be passed through <tt>sasl_encode()</tt> or
><tt>sasl_decode()</tt>. This must be limited to make sure that only
>a finite amount of data needs to be buffered. The simple rules to
>follow:</p>
>
><ul>
><li>Before starting authentication, set <tt>maxbufsize</tt> in your
>security properties to be the buffer size that you pass to the
><tt>read()</tt> system call&mdash;that is, the amount of data
>you're prepared to read at any one time.</li>
>
><li>After authentication finishes, use <tt>sasl_getprop()</tt> to
>retrieve the <tt>SASL_MAXOUTBUF</tt> value, and call
><tt>sasl_encode()</tt> with chunks of data of that size or less.
><tt>sasl_encode()</tt> will throw an error if you call it with a
>larger chunk of data, so be careful!</li>
></ul>
>
><p><b>Memory management:</b> As usual, whoever allocates the memory
>must free it. The SASL library will keep the data returned from
><tt>sasl_encode()</tt> until the next call to <tt>sasl_encode()</tt>
>on that connection. (<tt>sasl_decode()</tt> results persist until the
>next call to <tt>sasl_decode()</tt> on that connection.) The
>application must not attempt to free the memory returned from either
>function.</p>
>
><p><b>Internally:</b></p>
>
><ul>
><li>your application sets SASL_SEC_PROPS with the buffer size X of
>the amount of data it will be using to read() from the socket.</li>
>
><li>libsasl passes this number to the mechanism.</li>
>
><li>the mechanism passes this number to the other side. the other
>side gives the corresponding read() size to our side.</li>
>
><li>the mechanism subtracts the overhead of the layers from the
>size retrieved from the other side and returns it to the
>libsasl.</li>
>
><li>libsasl then returns (via SASL_MAXOUTBUF) this number as the
>maximum amount of plaintext material that can be encoded at any one
>time, Y.</li>
>
><li>sasl_encode() enforces the restriction of the length Y.</li>
></ul>
>
><h2><a name="example_section">Example applications that come with
>the Cyrus SASL library</a></h2>
>
><h3><a name="sample_client"><tt>sample-client</tt> and
><tt>sample-server</tt></a></h3>
>
>The sample client and server included with this distribution were
>initially written to help debug mechanisms. They base64 encode all
>the data and print it out on standard output. 
>
><p>Make sure that you set the IP addresses, the username, the
>authenticate name, and anything else on the command line (some
>mechanisms depend on these being present).</p>
>
><p>Also, sometimes you will receive a get "<tt>realm: Information
>not available</tt>" message, or similar; this is due to the fact
>that some mechanisms do not support realms and therefore never set
>it.</p>
>
><h3><a name="cyrus_imapd">Cyrus imapd v2.1.0 or later</a></h3>
>
>The Cyrus IMAP server now incorporates SASLv2 for all its
>authentication needs. It is a good example of a fairly large server
>application. Also of interest is the prot layer, included in
>libcyrus. This is a stdio-like interface that automatically takes
>care of layers using a simple "<tt>prot_setsasl()</tt>" call. 
>
><p>Cyrus imapd also sets a <tt>SASL_CB_PROXY_POLICY</tt> callback,
>which should be of interest to many applications.</p>
>
><h3><a name="imtest"><tt>imtest</tt>, from Cyrus 2.1.0 or
>later</a></h3>
>
><tt>imtest</tt> is an application included with Cyrus imapd. It is
>a very simple IMAP client, but should be of interest to those
>writing applications. It also uses the prot layer, but it is easy
>to incorporate similar support without using the prot layer.
>Likewise, there are other sample client applications that you can
>look at including <tt>smtptest</tt> and <tt>pop3test</tt> in the
>SASL distribution and the Cyrus IMAPd distribution, respectively. 
>
><h2><a name="random_things">Miscellaneous Information</a></h2>
>
><h3><a name="empty_exchanges">Empty exchanges</a></h3>
>
><p>Some SASL mechanisms intentionally send no data; an application
>should be prepared to either send or receive an empty exchange. The
>SASL profile for the protocol should define how to send an empty
>string; make sure to send an empty string when requested, and when
>receiving an empty string make sure that the "<tt>inlength</tt>"
>passed in is 0.</p>
>
><p>Note especially that the distinction between the empty string ""
>and the lack of a string (NULL) is extremely important in many
>cases (most notably, the client-send first scenario), and the
>application must ensure that it is passing the correct values to
>the SASL library at all times.</p>
>
><h3><a name="idle">Idle</a></h3>
>
>While the implementation and the plugins correctly implement the
>idle calls, none of them currently do anything. 
>
><hr>
>Please send any questions or comments to: 
>
><address><a href=
>"mailto:cyrus-bugs@andrew.cmu.edu">cyrus-bugs@andrew.cmu.edu</a></address>
>
><br>
> Back to the <a href="index.html">index</a>
></body>
></html>
>
><HTML><HEAD>
><title>Cyrus SASLv2 README</title>
>
></HEAD>
><BODY>
><H1>Read Me First</H1>
>
>This document offers a general overview of the Cyrus SASL library.
>The Cyrus SASL Libray provides applications with an implementation
>of the Simple Authentication and Security Layer (RFC2222), and
>several authentication mechanisms.  Users interested in the "big picture"
>of what is provided by the library should read about
><a href=components.html>Cyrus SASL Components</a>.
>
><H2>FEATURES</H2>
>
>The following <a href="mechanisms.html">mechanisms</a> are included in
>this distribution:
><ul>
><li>ANONYMOUS
><li>CRAM-MD5
><li>DIGEST-MD5
><li>EXTERNAL
><li>GSSAPI (MIT Kerberos 5, Heimdal Kerberos 5 or CyberSafe)
><li>KERBEROS_V4
><li>LOGIN
><li>NTLM (requires OpenSSL libcrypto)
><li>OTP (requires OpenSSL libcrypto)
><li>PLAIN
><li>SRP (work in progress; requires OpenSSL libcrypto)
></ul>
>
>The library also supports storing user secrets in either a hash
>database (e.g. Berkeley DB, gdbm, ndbm), LDAP, or in a SQL database 
>(MySQL, Postgres).
>
>
>Additionally, mechanisms such as PLAIN and LOGIN
>(where the plaintext password is directly supplied by the client)
>can perform direct password verification via the saslauthd daemon.  This
>allows the use of LDAP, PAM, and a variety of other password verification
>routines.
>
>The sample directory contains two programs which provide a reference
>for using the library, as well as making it easy to test a mechanism
>on the command line.  See <a
>href="programming.html">programming.html</a> for more information.<p>
>
>This library is believed to be thread safe IF:
><ul>
><li>you supply mutex functions (see sasl_set_mutex())
><li>you make no libsasl calls until sasl_client/server_init() completes
><li>no libsasl calls are made after sasl_done() is begun
><li>when using GSSAPI, you use a thread-safe GSS / Kerberos 5 library.
></ul>
>
><H2>TYPICAL UNIX INSTALLATION</H2>
>
>First, if you are upgrading from Cyrus SASLv1, please see <a
>href="upgrading.html">upgrading.html</a>.<p>
>
>Please see the file <a href="install.html">install.html</a> for instructions
>on how to install this package.<p>
>
>Note that the library can use the environment variable SASL_PATH to locate the
>directory where the mechanisms are; this should be a colon-separated
>list of directories containing plugins.  Otherwise it will default to the
>value of <tt>--with-plugindir</tt> as supplied to <tt>configure</tt> (which
>itself defaults to <tt>/usr/local/lib</tt>).
>
><H2>INSTALLATION ON MAC OS X</H2>
>Please read <A HREF="macosx.html">macosx.html</A>
>
><H2>INSTALLATION ON WINDOWS</H2>
>Please read <A HREF="windows.html">windows.html</A>.  This configuration
>has not been extensively tested.
>
><H2>CONFIGURATION</H2>
>There are two main ways to configure the SASL library for a given
>application.  The first (and typically easiest) is to make use
>of the application's configuration files.  Provided the application supports it
>(via the <tt>SASL_CB_GETOPT</tt> callback), please refer to that documetation
>for how to supply <a href=options.html>SASL options</a>.<p>
>
>Alternatively, Cyrus SASL looks for configuration files in
>/usr/lib/sasl/Appname.conf where Appname is settable by the
>application (for example, Sendmail 8.10 and later set this to
>"Sendmail").<p>
>
>Configuration using the application's configuration files (via
>the <tt>getopt</tt> callback) will override those supplied by
>the SASL configuration files.<p>
>
>For a detailed guide on configuring libsasl, please look at
><A HREF=sysadmin.html>sysadmin.html</A> and
><A HREF=options.html>options.html</A>
>
><H2>KNOWN BUGS</H2>
><ul>
><li>libtool doesn't always link libraries together.  In our environment,
>we only have static Krb5 libraries; the GSSAPI plugin should link
>these libraries in on platforms that support it (Solaris and Linux
>among them) but it does not.  It also doesn't always get the runpath
>of libraries correct.
><li>Also see our <A HREF=http://bugzilla.andrew.cmu.edu>bugzilla</A>.
></ul>
>
><H2>AUTHORS</H2>
>
>For any comments/suggestions/bug reports, please contact <a
>href="mailto:cyrus-bugs@andrew.cmu.edu">cyrus-bugs@andrew.cmu.edu</a>.
>Be sure to include the version of libsasl and your operating system;
>messages without this information will not be answered.<p>
>
>Major contributors to the libsasl code can be found in the top-level
>file AUTHORS.  Additionally saslauthd has an AUTHORS file that lists
>major contributors as well.<p>
>
>People considering doing binary distributions that include saslauthd
>should be aware that the code is covered by several slightly different
>(but compatible) licenses, due to how it was contributed.  Details can
>be found within the source code.<p>
>
><hr>
>Back to the <A href=index.html>index</a>
>
></body>
></html>
>
><HTML><HEAD>
><title>Cyrus SASL for System Administrators</title>
>
></HEAD>
><BODY>
><H1>Cyrus SASL for System Administrators</H1>
>
>This document covers configuring SASL for system administrators,
>specifically those administrators who are installing a server that
>uses the Cyrus SASL library.  You may want to read
><a href=components.html>this document</a> which presents an
>overview of the major components of the Cyrus SASL distribution
>and describes how they interact, as well as <a href=install.html>
>the installation guide</a>.
>
><h2><A NAME="saslintro">What SASL is</A></h2>
>
>SASL, the Simple Authentication and Security Layer, is a generic
>mechanism for protocols to accomplish authentication.  Since protocols
>(such as SMTP or IMAP) use SASL, it is a natural place for code
>sharing between applications.  Some notable applications that use the
>Cyrus SASL library include <a
>href="http://www.sendmail.org">Sendmail</a>,
><a href="http://web.asg.cmu.edu/cyrus">Cyrus imapd</a>,
>and <a href="http://www.openldap.org">OpenLDAP</a>.
>
><p> Applications use the SASL library to tell them how to accomplish
>the SASL protocol exchange, and what the results were.
>
><p> SASL is only a framework: specific SASL mechanisms govern the
>exact protocol exchange.  If there are n protocols and m different
>ways of authenticating, SASL attempts to make it so only n plus m
>different specifications need be written instead of n times m
>different specifications.  With the Cyrus SASL library, the mechanisms
>need only be written once, and they'll work with all servers that use
>it.
>
><h3><a name="authid">Authentication and authorization identifiers</a></h3>
>
>An important concept to become familiar with is the difference between
>an "authorization identifier" and an "authentication identifier".
>
><DL compact>
><DT>userid (user id, authorization id)<dd> The userid is the
>identifier an application uses to check allowable options.  On my Unix
>system, the user "<tt>bovik</tt>" (the account of Harry Q. Bovik) is
>allowed to write to "<tt>/home/bovik</tt>" and its subdirectories but
>not to "<tt>/etc</tt>".
>
><DT>authid (authentication id)<dd> The authentication identifier is
>the identifier that is being checked.  "bovik"'s password might be
>"qqqq", and the system will authenticate anyone who knows "qqqq" as
>"bovik".  However, it's possible to authenticate as one user but
><b>act as</b> another user.  For instance, Harry might be away on
>vacation and assign one of his graduate students, Jane, to read his
>mail.  He might then allow Jane to act as him merely by supplying her
>password and her id as authentication but requesting authorization as
>"bovik". So Jane might log in with an authentication identifier of
>"jane" and an authorization id of "bovik" and her own (Jane's)
>password.
></DL>
>
><p>Applications can set their own proxy policies; by default, the SASL
>library will only allow the same user to act for another (that is,
>userid must equal authid).  See your application's documentation for
>details about changing the default proxy/authorization policies.
>
><h3><a name="realms">Realms</a></h3>
>
>The Cyrus SASL library supports the concept of "realms".  A realm is
>an abstract set of users and certain mechanisms authenticate users in
>a certain realm.
>
><p>In the simplest case, a single server on a single machine, the
>realm might be the fully-qualified domain name of the server.  If the
>applications don't specify a realm to SASL, most mechanisms will
>default to this.
>
><p> If a site wishes to share passwords between multiple machines, it
>might choose it's authentication realm as a domain name, such as
>"CMU.EDU".  On the other hand, in order to prevent the entire site's
>security from being compromised when one machine is compromised, each
>server could have it's own realm. Certain mechanisms force the user
>(client side) to manually configure what realm they're in, making it
>harder for users to authenticate.
>
><p>A single site might support multiple different realms.  This can
>confuse applications that weren't written in anticipation of this; make
>sure your application can support it before adding users from different
>realms into your databases.
>
><p>To add users of different realms to sasldb, you can use the
><tt>-u</tt> option to saslpasswd2.  The SQL plugin has a way of
>integrating the realm name into the query string with the '%r' macro.
>
><p>The Kerberos mechanisms treat the SASL realm as the Kerberos
>realm.  Thus, the realm for Kerberos mechanisms defaults to the
>default Kerberos realm on the server.  They may support cross-realm
>authentication; check your application on how it deals with this.
>
><p>Realms will be passed to saslauthd as part of the saslauthd protocol,
>however the way each saslauthd module deals with the situation is
>different (for example, the LDAP plugin allows you to use the realm
>to query the server, while the rimap and PAM plugins ignore it entirely).
>
><p>Realms are represented in a username string by any text followinhg
>the '@' sign.  So, usernames like rjs3@ANDREW.CMU.EDU, is user 'rjs3'
>in the realm 'ANDREW.CMU.EDU'.  If no realm is provided, the server's
>FQDN is assumed (likewise when specifying a realm for saslpasswd2).
>
><h2><a name="saslhow">How SASL works</a></h2>
>
>How SASL works is governed by what mechanism the client and server 
>choose to use and the exact implementation of that mechanism.  This
>section describes the way these mechanisms act in the Cyrus SASL
>implementation.
>
><h3>The PLAIN mechanism, <tt>sasl_checkpass()</tt>, and plaintext
>passwords</h3>
>
>The PLAIN mechanism is not a secure method of authentication by
>itself.  It is intended for connections that are being encrypted by
>another level.  (For example, the IMAP command "STARTTLS" creates an
>encrypted connection over which PLAIN might be used.) The PLAIN
>mechanism works by transmitting a userid, an authentication id, and a
>password to the server, and the server then determines whether that is
>an allowable triple.
>
><p>The principal concern for system administrators is how the
>authentication identifier and password are verified.  The Cyrus SASL
>library is flexible in this regard:
>
><DL>
><dt><i>auxprop</i> 
><dd> checks passwords agains the <tt>userPassword</tt> attribute
>supplied by an auxiliary property plugin.  For example, SASL ships
>with a sasldb auxiliary property plugin, that can be used to
>authenticate against the passwords stored in <tt>/etc/sasldb2</tt>.
>Since other mechanisms also use this database for passwords, using
>this method will allow SASL to provide a uniform password database to
>a large number of mechanisms.
>
><dt><i>saslauthd</i>
>
><dd> contacts the <tt>saslauthd</tt> daemon to to check passwords
>using a variety of mechanisms.  More information about the various invocations
>of saslauthd can be can be found in <tt>saslauthd(8)</tt>.  Generally you
>want something like <tt>saslauthd -a pam</tt>.  If plaintext authentications
>seem to be taking some time under load, increasing the value of the <tt>-n</tt>
>parameter can help.<p>
>
>Saslauthd keeps its named socket in "/var/state/saslauthd" by default.
>This can be overridden by specifying an alternate value to
>--with-saslauthd=/foo/bar at compile time, or by passing the -m
>parameter to saslauthd (along with setting the saslauthd_path SASL
>option).  Whatever directory this is, it must exist in order for
>saslauthd to function.<p>
>
>Once you configure (and start) <tt>saslauthd</tt>, there is a
><tt>testsaslauthd</tt> program that can be built with <tt>make
>testsaslauthd</tt> in the <tt>saslauthd</tt> subdirectory of the
>source.  This can be used to check that that the <tt>saslauthd</tt>
>daemon is installed and running properly.  An invocation like
><tt>testsaslauthd -u rjs3 -p 1234</tt> with appropriate values for the
>username and password should do the trick.<p>
>
>If you are using the PAM method to verify passwords with saslauthd, keep in
>mind that your PAM configuration will need to be configured for each service
>name that is using saslauthd for authentication. Common service names
>are &quot;imap&quot;, &quot;sieve&quot;, and &quot;smtp&quot;.
>
><dt><i>Courier-IMAP authdaemond</i>
>
><dd> contacts Courier-IMAP's <tt>authdaemond</tt> daemon to check passwords.
>This daemon is simliar in functionality to <tt>saslauthd</tt>, and is shipped
>separately with the <a href="http://www.courier-mta.org">Courier</a> mail server.
>
><p>Note: this feature is <b>not</b> compiled in the library by default, and its 
>provided for sites with custom/special requirements only (because the
>internal authentication protocol its not documented anywhere so it could
>change at any time).  We have tested against the authdaemond included with
>Courier-IMAP 2.2.1.
>
><p>To enable <tt>authdaemond</tt> support, pass <tt>--with-authdaemon</tt> to the 
>configuration script, set pwcheck_method to ``authdaemond'' and point 
>authdaemon_path to <tt>authdaemond</tt>'s unix socket. Optionally, you can
>specify --with-authdaemond=PATH to the configure script so that
>authdaemond_path points to a default, static, location.
>
><dt><i>pwcheck</i>
>
><dd> checks passwords with the use of a separate,
>  helper daemon.  This feature is for backwards-compatibility
>  only. New installations should use saslauthd.<p>
>
><dt><i>write your own</i>
><dd> Last, but not least, the most flexible method of authentication
>for PLAIN is to write your own.  If you do so, any application that
>calls the "<tt>sasl_checkpass()</tt>" routine or uses PLAIN will
>invoke your code.  The easiest place to modify the plaintext
>authentication routines is to modify the routine
>"<tt>_sasl_checkpass()</tt>" in the file <tt>lib/server.c</tt> to
>support a new method, and to add that method to
><tt>lib/checkpw.c</tt>.  Be sure to add a prototype in
><tt>lib/saslint.h</tt>!
>
><p>However, the more flexible and preferred method of
>adding a routine is to create a new saslauthd mechanism.<p> </dl>
>
><p>The LOGIN mechanism (not to be confused with IMAP4's LOGIN command)
>is an undocumented, unsupported mechanism.  It's included in the Cyrus
>SASL distribution for the sake of SMTP servers that might want to
>interoperate with old clients.  Do not enable this mechanism unless
>you know you're going to need it.  When enabled, it verifies passwords
>the same way the PLAIN mechanism does.
>
><h3>Shared secrets mechanisms</h3>
>
>The Cyrus SASL library also supports some "shared secret"
>authentication methods: CRAM-MD5 and its successor DIGEST-MD5.  These
>methods rely on the client and the server sharing a "secret", usually
>a password.  The server generates a challenge and the client a
>response proving that it knows the shared secret.  This is much more
>secure than simply sending the secret over the wire proving that the
>client knows it.
>
><p>There's a downside: in order to verify such responses, the
>server must keep passwords or password equivalents in a database;
>if this database is compromised, it is the same as if all the
>passwords for the realm are compromised.
>
><p>Put another way, <i>you cannot use saslauthd with these methods</i>.  
>If you do not wish to advertise these methods for that reason (i.e. you
>are only using saslauthd for password verification), then either remove
>the non-plaintext plugins (those other than login and plain) from the
>plugin directory, or use the <tt>mech_list</tt> option to disable them.
>
><p>For simplicity sake, the Cyrus SASL library stores plaintext
>passwords only in the <tt>/etc/sasldb2</tt> database.  These passwords
>are then shared among all mechanisms which choose to use it.
>Depending on the exact database method
>used (gdbm, ndbm, or db) the file may have different suffixes or may
>even have two different files ("<tt>sasldb.dir</tt>" and
>"<tt>sasldb.pag</tt>").  It is also possible for a server to define
>it's own way of storing authentication secrets.  Currently, no
>application is known to do this.
>
><p>The principle problem for a system administrator is to make sure that
>sasldb is properly protected. Only the servers that need to read it to
>verify passwords should be able to.  If there are any normal shell
>users on the system, they must not be able to read it.
>
><p>This point is important, so we will repeat it: <b>sasldb stores the
>plaintext versions of all of its passwords. If it is compromised so
>are all of the passwords that it stores</b>.
>
><p>Managing password changes is outside the scope of the library.
>However, system administrators should probably make a way of letting
>user's change their passwords available to users.  The
>"<tt>saslpasswd2</tt>" utility is provided to change the secrets in
>sasldb.  It does not affect PAM, <tt>/etc/passwd</tt>, or any other
>standard system library; it only affects secrets stored in sasldb.
>
><p>Finally, system administrators should think if they want to enable
>"auto_transition".  If set, the library will automatically create
>secrets in sasldb when a user uses PLAIN to successfully authenticate.
>However, this means that the individual servers, such as imapd, need
>read/write access to sasldb, not just read access.  By default,
>"auto_transition" is set to false; set it to true to enable.  (There's
>no point in enabling this option if "pwcheck_method" is "auxprop",
>and the sasldb plugin is installed, since you'll be transitioning from
>a plaintext store to a plaintext store)
>
><h3>Kerberos mechanisms</h3>
>
>The Cyrus SASL library also comes with two mechanisms that make use of
>Kerberos: KERBEROS_V4, which should be able to use any Kerberos v4
>implementation, and GSSAPI (tested against MIT Kerberos 5, Heimdal
>Kerberos 5 and CyberSafe Kerberos 5).  These mechanisms make use of the kerberos infrastructure
>and thus have no password database.
>
><p>Applications that wish to use a kerberos mechanism will need access
>to a service key, stored either in a "srvtab" file (Kerberos 4) or a
>"keytab" file (Kerberos 5).  Currently, the keytab file location is
>not configurable and defaults to the system default (probably
><tt>/etc/krb5.keytab</tt>).
>
><p>The Kerberos 4 srvtab file location is configurable; by default it is
><tt>/etc/srvtab</tt>, but this is modifiable by the "srvtab" option.
>Different SASL applications can use different srvtab files.
>
><p>A SASL application must be able to read its srvtab or keytab file.
>
><p>You may want to consult the <a href="gssapi.html">GSSAPI Tutorial</a>.</p>
>
><h3>The OTP mechanism</h3>
>
>The Cyrus SASL library also supports the One-Time-Password (OTP)
>mechanism.  This mechanism is similar to CRAM-MD5 and DIGEST-MD5 in
>that is uses a shared secret and a challenge/response exchange.
>However, OTP is more secure than the other shared secret mechanisms in
>that the secret is used to generate a sequence of one-time (single
>use) passwords which prevents reply attacks, and that secret need
>not be stored on the system.  These one-time passwords are stored in the
><tt>/etc/sasldb2</tt> database.  See the <i>Shared secrets
>mechanisms</i> section for a discussion of the <tt>/etc/sasldb2</tt>
>database.
>
><h4>OTP via OPIE</h4>
>For sites with an existing OTP infrastructure using OPIE, Cyrus SASL
>can be configured to use OPIE v2.4 instead of using its own database
>and server-side routines.
>OPIE should be configured with the <tt>--disable-user-locking</tt> 
>option if the SASL server application will not be running as "root". 
>
><p>OPIE uses its own "opiekeys" database for storing the data necessary
>for generating the server challenges.  The location of the opiekeys
>file is configurable in SASL; by default it is <tt>/etc/opiekeys</tt>,
>but this is modifiable by the "opiekeys" option.
>
><p>A SASL server application must be able to read and write the
>opiekeys file.
>
><h2>Auxiliary Properties</h2>
>
>SASLv2 introduces the concept of Auxilliary Properties.  That is, the ability
>for information related to authentication and authorization to all be looked
>up at once from a directory during the authentication process.  SASL Plugins
>internally take advantage of this to do password lookups in directories
>such as the SASLdb, LDAP or a SQL database.  Applications can look up arbitrary properties through them.<p>
>
>Note that this means that if your password database is in a SASLdb, and
>you wish to use it for plaintext password lookups through the sasldb, you
>will need to set the sasl <a href=options.html>option</a>
><tt>pwcheck_method</tt> to be <tt>auxprop</tt>. 
>
><h2>How to set configuration options</h2>
>
>The Cyrus SASL library comes with a built-in configuration file
>reader.  However, it is also possible for applications to redefine
>where the library gets it's configuration options from.
>
><h3><a name="saslconf">The default configuration file</a></h3>
>
><p>By default, the Cyrus SASL library reads it's options from
><tt>/usr/lib/sasl2/App.conf</tt> (where "App" is the application
>defined name of the application).  For instance, Sendmail reads it's
>configuration from "<tt>/usr/lib/sasl2/Sendmail.conf</tt>" and the
>sample server application included with the library looks in
>"<tt>/usr/lib/sasl2/sample.conf</tt>".
>
><p>A standard Cyrus SASL configuration file looks like: 
><pre>
>srvtab: /var/app/srvtab
>pwcheck_method: saslauthd
></pre>
>
><h3>Application configuration</h3>
>
>Applications can redefine how the SASL library looks for configuration
>information.  Check your application's documentation for specifics.
>
><p>For instance, Cyrus imapd reads its sasl options from it's own
>configuration file, <tt>/etc/imapd.conf</tt>, by prepending all SASL
>options with "<tt>sasl_</tt>": the SASL option "pwcheck_method" is set
>by changing "sasl_pwcheck_method" in <tt>/etc/imapd.conf</tt>.
>
><h2>Troubleshooting</h2>
>
><dl compact>
><dt><b>Q:</b> Why doesn't KERBEROS_V4 doesn't appear as an
>available mechanism?
><dd>
><p><b>A:</b> Check that the <tt>srvtab</tt> file is readable by the
>user running as the daemon.  For Cyrus imapd, it must be readable by
>the Cyrus user.  By default, the library looks for the srvtab in
><tt>/etc/srvtab</tt>, but it's configurable using the <tt>srvtab</tt>
>option.
>
><p>
><dt><b>Q:</b> Why doesn't OTP doesn't appear as an available
>mechanism?
><dd>
><p><b>A:</b> If using OPIE, check that the <tt>opiekeys</tt> file is
>readable by the user running the daemon.  For Cyrus imapd, it must
>be readable by the Cyrus user.  By default, the library looks for the
>opiekeys in <tt>/etc/opiekeys</tt>, but it's configurable using the
><tt>opiekeys</tt> option.
>
><p>
><dt><b>Q:</b> Why don't CRAM-MD5 and DIGEST-MD5 work with my old sasldb?
><dd>
><p><b>A:</b> Because sasldb now stores plaintext passwords only, the old
>sasldb is completely incompatible.
>
><p>
><dt><b>Q:</b> I'm having performance problems on each authentication, there is
>a noticeable slowdown when sasl initializes, what can I do?
><dd>
><p><b>A:</b>libsasl reads from <tt>/dev/random</tt> as part of its
>initialization. <tt>/dev/random</tt> is a "secure" source of entropy,
>and will block your application until a sufficient amount of
>randomness has been collected to meet libsasl's needs.</p>
>
><p>To improve performance, you can change DEV_RANDOM in
><tt>config.h</tt> to be <tt>/dev/urandom</tt> and recompile
>libsasl. <tt>/dev/urandom</tt> offers less secure random numbers but
>should return immediately. The included mechanisms, besides OTP and
>SRP, use random numbers only to generate nonces, so using
><tt>/dev/urandom</tt> is safe if you aren't using OTP or SRP.
>
><p>
><dt><b>Q:</b> I've converted the sasldb database to the new format. 
>Why can't anybody authenticate?
><dd>
><p><b>A:</b> sasldb is now a plugin module for the auxprop method.
>Make sure you changed the /usr/lib/sasl2/*.conf files to reflect<br>
><tt>pwcheck_method: auxprop</tt><br>
><br>
>...and if you're using cyrus-imapd, /etc/imapd.conf must reflect:
><tt>sasl_pwcheck_method: auxprop</tt>
>
><p>
><dt><b>Q:</b> Is LOGIN supported?
><dd>
><p><b>A:</b> The LOGIN mechanism is a non-standard, undocumented
>plaintext mechanism.  It's included in the SASL distribution purely
>for sites that need it to interoperate with old clients; we don't
>support it.  Don't enable it unless you know you need it.
>
><p>
><dt><b>Q:</b> Is NTLM supported?
><dd>
><p><b>A:</b> The NTLM mechanism is a non-standard, undocumented
>mechanism developed by Microsoft.  It's included in the SASL
>distribution purely for sites that need it to interoperate with
>Microsoft clients (ie, Outlook) and/or servers (ie, Exchange); we
>don't support it.  Don't enable it unless you know you need it.
>
><p>
><dt><b>Q:</b> How can I get a non-root application to check plaintext
>passwords?
><dd>
><p><b>A:</b> Use the "saslauthd" daemon and setting "pwcheck_method"
>to "saslauthd".
>
><p>
><dt><b>Q:</b> I want to use Berkeley DB, but it's installed in
><tt>/usr/local/BerkeleyDB.3.1</tt> and <tt>configure</tt> can't find
>it.
><dd>
><p><b>A:</b> Try setting "CPPFLAGS" and "LDFLAGS" environment
>variables before running <tt>configure</tt>, like so:
><pre>
>env CPPFLAGS="-I/usr/local/BerkeleyDB.3.1/include" \
>  LDFLAGS="-L/usr/local/BerkeleyDB.3.1/lib -R/usr/local/BerkeleyDB.3.1/lib" \
>  ./configure --with-dblib=berkeley 
></pre>
>
><p>
><dt><b>Q:</b> It's not working and won't tell me why! Help!
><dd>
><p><b>A:</b> Check syslog output (usually stored in
><tt>/var/log</tt>) for more information. You might want to change your
>syslog configuration (usually <tt>/etc/syslogd.conf</tt>) to log
>"debug.*" to a file while debugging a problem.</p>
>
><p>The developers make heavy use of <tt>strace</tt> or <tt>truss</tt>
>when debugging a problem that isn't outputting any useful
>information.</p>
>
><p>
><dt><b>Q:</b> Is there a mailing list to discuss the Cyrus SASL
>library?
><dd>
><p><b>A:</b> <tt>cyrus-sasl@lists.andrew.cmu.edu</tt> is available for
>discussion.  To subscribe, send a message to
><a href=
>"mailto:majordomo@lists.andrew.cmu.edu?subject=subscribe cyrus-sasl">
><tt>majordomo@lists.andrew.cmu.edu</tt></a>
>with the body of 'subscribe cyrus-sasl'.
>
><p> An archive is available via
><ul>
> <li> anonymous IMAP at <a
>href="imap://cyrus.andrew.cmu.edu/archive.cyrus-sasl">imap://cyrus.andrew.cmu.edu/archive.cyrus-sasl</a>.
>  <li> HTTP at <a
>href="http://asg.web.cmu.edu/archive/mailbox.php3?mailbox=archive.cyrus-sasl">
>http://asg.web.cmu.edu/archive/mailbox.php3?mailbox=archive.cyrus-sasl</a>
></ul>
>
><p>Note: If you are not subscribed, your posts go through human
>approval before they go out to the list and so posting may be
>(greatly) delayed.
></dl>
>
><hr>
>Back to the <A href=index.html>index</a>
>
></body>
></html>
>
><HTML><HEAD>
><title>Upgrading from Cyrus SASLv1 to Cyrus SASLv2</title>
>
></HEAD>
><BODY>
><H1>Upgrading from Cyrus SASLv1 to Cyrus SASLv2</H1>
>
>This document covers issues with upgrading from SASLv1 to SASLv2.
>To upgrade:
>
><ul>
><li> Install Cyrus SASL v2 as normal according to <a
>href="install.html">the installation guide</a>.  This will overwrite
>some manpages, but will not affect your current applications.  Do NOT
>attempt to make it use the same directories, otherwise old Cyrus SASLv1
>applications will no longer function.</li>
>
><li> Install your new Cyrus SASL v2 applications. Applications that
>use Cyrus SASLv1 will <em>not</em> use the Cyrus SASL v2
>infrastructure (and vice-versa).
>
><li> If you used <tt>/etc/sasldb</tt> for authentication, you'll need
>to take the following steps to convert to using <tt>/etc/sasldb2</tt>
>with Cyrus SASL v2:
>      <ol>
>      <li> run <tt>utils/dbconverter-2</tt> after installation.</li>
>      <li> change the <tt>pwcheck_method</tt> in any config files to
>      <tt>auxprop</tt></li> 
>      <li> (optional) add <tt>auxprop_plugin</tt> to the config files,
>      set to <tt>sasldb</tt></li>
>      </ol>
>
><li> If you used <tt>passwd</tt>, <tt>shadow</tt>, <tt>pam</tt>,
><tt>kerberos_v4</tt> or <tt>sia</tt> as your <tt>pwcheck_method</tt>
>in libsasl v1, you'll need to convert to using
><tt>saslauthd</tt>. Arrange to start <tt>saslauthd -a
><i>method</i></tt> on boot. Change <tt>pwcheck_method</tt> in any
>configuration files to <tt>saslauthd</tt>.</li>
>
><li> If you used <tt>pwcheck</tt> with libsasl v1, you can either
>continue to use <tt>pwcheck</tt> with libsasl v1 or you can switch to
><tt>saslauthd</tt>, which offers more flexibility and a potentially
>much more efficient implementation.</li>
>
><li> If you are continuing to use some libsasl v1 applications, read
>onwards to understand the ramifications.</li>
>
><li> If you want to learn how to port applications from libsasl v1 to
>libsasl v2, you should read <A HREF=appconvert.html>this document</A>.
></ul>
>
><h2><A NAME="overview">Backwards Compatibility</A></h2>
>
>Cyrus SASLv2 is completely incompatible with applications that use
>Cyrus SASLv1.  This means that applications are unable to
>simultaneously link both versions of the library, and developers are
>encouraged to instead develop or upgrade their applications to link
>against the new libsasl.<p>
>
>Likewise, the format for the sasldb database has been completely
>revamped.  See <A HREF="#db">here</A> for a discussion of the relevant
>upgrade issues related to sasldb.  All new passwords stored in the
>sasldb database will be in plaintext, meaning that a compromised
>sasldb will compromise all services with the same passwords.  (This
>situation isn't significantly worse, cryptographicly speaking, than
>the old method and allows the database to be easy to transition to
>another format, when the need arises.)  Mechanisms requiring a more
>secure password database backend (e.g. SRP) should implement their own
>or use alternate property names within sasldb.<P>
>
><h2><A NAME="coexist">Coexistence with SASLv1</A></h2>
>
>The two library versions and the associated utilities should be able
>to coexist on the same system.  The man pages will be unable to
>coexist (but luckily the new manpages are much better!).  The libsasl
>v2-specific utilities have had a "2" appended to their name for this
>purpose (e.g. <tt>saslpasswd2</tt>, <tt>sasldblistusers2</tt>).  The
>new-style sasldb now defaults to the name <tt>/etc/sasldb2</tt>, but
>this is configurable.
>
><h2><A NAME="db">Database Upgrades</A></h2>
>
>While there does not seem to be any conflict with the keys stored in
>the database, it is not recommended for both versions of the library
>to use the same database file.  Included in the utils directory is a
>program called <tt>dbconverter-2</tt> which will allow you to convert
>from the old-format database to the new format.  Note that if you continue to
>run older applications that rely on Cyrus SASLv1, the databases for SASLv1
>and SASLv2 will not automatically be kept in sync.<p>
>
><hr>
>Back to the <A href=index.html>index</a>
>
></body>
></html>
>
><html><head>
><title>Building Cyrus SASL on Windows</title>
>
></head>
>
><body>
><h1>Building Cyrus SASL on Windows</h1>
>
>Note, that Cyrus SASL on Windows is still laregely a "work in progress".
>So far only the main library, plugins (SASLDB using SleepyCat, no MySQL)
>and several applications (see the list below) can be built. In particular,
>saslauthd doesn't compile on Windows.
>
><h2>Prerequisites</h2>
>
><ul>
><li>Visual Studio. We have tested Visual Studio 6 and Visual Studio 7 (.NET).
>By default we are using Visual Studio 7 (both 2002 and 2003 versions were tested). If you want to use Visual Studio 6,
>you need to remove the leading # character from the line containing "<tt>#VCVER=6</tt>" in win32/common.mak.
>
><li>The latest Platform SDK. We are currently using March 2006. (The earliest tested version was November 2001.)
>
><li>SleepyCat include files and libraries are required to buil SASLDB plugin,
>saslpasswd2.exe and sasldblistusers2.exe. We have tested SleepyCat 4.1.X-4.4.X.
>
><li>If you are building directly from CVS, you'll need the <a
>href="http://www.cygwin.com/">Cygwin</a> Unix-compatibility
>environment to create the <tt>_init.c</tt> files needed for dynamic
>loading. Cygwin is <em>not</em> required for building from our tar
>distribution.  
>
></ul>
>
><h2>Step by step</h2>
>
>These directions assume that you've untarred the library or used CVS
>and the sources are in <tt>C:\SASL</tt>.
>
><h3>preparing to build (cvs only!)</h3>
>
>Start a cygwin shell and create the dynamic loading stubs:
>
><pre>
>% cd /cygdrive/c/sasl/plugins
>% sh makeinit.sh
></pre>
>
><h3>building using NMake</h3>
>
>Open a "Windows 2000 build environment" from the SDK's Start Menu and
>use "<tt>nmake /f NTMakefile</tt>" to build.
>
><p>To build a debug verison, use "<tt>nmake /f NTMakefile
>CFG=Debug</tt>". For a production version, "<tt>nmake /f NTMakefile
>CFG=Release</tt>". If you don't specify CFG parameter, production
>version will be built by default.
>
><p>As Windows build requires SleepyCat, there are additional options
>that has to be provided to NMake on the command line.
>If SleepyCat sources are located in <tt>c:\packages\db\4.1.24</tt>
>and built library in <tt>c:\packages\db\4.1.24\build_win32\Release_static</tt>,
>you should add something like
><tt>DB_INCLUDE=c:\packages\db\4.1.24\build_win32</tt>
>and <tt>DB_LIBPATH=c:\packages\db\4.1.24\build_win32\Release_static</tt>.
><br>Also note, that the <tt>DB_LIB</tt> defines the name of the SleepyCat library
>to link against. It defaults to libdb41s.lib.
><br>If you don't pass the parameters described above, NMake will pick the
>defaults, which is probably not what you want. 
>
><p>Another option of interest is <tt>STATIC</tt>.
>It specifies which version of the standard C library
>to use. The default is "no", meaning that the standard C library
>from the MSVCRT.DLL will be used.
>
><p>Example:
><pre>
>Targeting Windows 2000 and IE 5.0 RETAIL
>
>C:\Program Files\Microsoft SDK> cd \sasl
>
>C:\sasl> nmake /f NTMakefile DB_INCLUDE=c:\packages\db\4.1.24\build_win32
>DB_LIBPATH=c:\packages\db\4.1.24\build_win32\Release_static
>
>No configuration specified. Defaulting to Release.
>Using MSVCRT.dll as C library by default.
>Defaulting SleepyCat library name to libdb41s.lib.
>Codegeneration defaulting to /MD.
>...
>
></pre>
>
><p>SASL NTMakefile also understands "clean" target that you can use to clean all files generated by the compiler.
>
><pre>
>C:\sasl> nmake /f NTMakefile clean
>
>Microsoft (R) Program Maintenance Utility Version 7.00.9466
>Copyright (C) Microsoft Corporation.  All rights reserved.
>
>        cd lib && nmake /f NTMakefile                    clean
>
>Microsoft (R) Program Maintenance Utility Version 7.00.9466
>Copyright (C) Microsoft Corporation.  All rights reserved.
>
>No configuration specified. Defaulting to Release.
>Using MSVCRT.dll as C library by default.
>Defaulting SleepyCat library name to libdb41s.lib.
>Defaulting SleepyCat include path to c:\work\isode\db\build_win32.
>Defaulting SleepyCat library path to c:\work\isode\db\build_win32\Release_static.
>...
>
></pre>
>
><h3>building additional plugins</h3>
>
><p>Specify "GSSAPI=&lt;type&gt;" parameter if you want to enable GSSAPI plugin.
>Currently only &lt;type&gt;=CyberSafe is supported and this will build the plugin
>that links against CyberSafe Kerberos.
>
>GSSAPI depends on <tt>GSSAPI_INCLUDE</tt> and <tt>GSSAPI_LIBPATH</tt> parameters.
>You can either specify them on the command line or edit the defaults in win32\common.mak
>
><p>Specify "SQL=&lt;type&gt;" parameter if you want to enable SQL plugin.
>Currently only &lt;type&gt;=SQLITE is supported and this will build the plugin
>that links against SQLITE (www.sqlite.org).
>
>SQL=&lt;SQLITE&gt; depends on <tt>SQLITE_INCLUDES</tt> and <tt>SQLITE_LIBPATH</tt> parameters.
>You can either specify them on the command line or edit the defaults in win32\common.mak
>
><p>Specify "NTLM=1" parameter if you want to enable NTLM plugin.
>I.e. "<tt>nmake /f NTMakefile NTLM=1</tt>"
>
><p>Specify "SRP=1" parameter if you want to enable SRP plugin.
>You can also specify "DO_SRP_SETPASS=1" if you want to enable SRP setpass functionality.
>
><p>Specify "OTP=1" parameter if you want to enable OTP plugin.
>
><p>NTLM, SRP and OTP plugins depend on OpenSSL. You can either specify
><tt>OPENSSL_INCLUDE</tt> and <tt>OPENSSL_LIBPATH</tt> parameters on the command
>line or edit the defaults in win32\common.mak
>Note, that unless you are building one of those plugins, OpenSSL is not required!
>
><p>If you want to build multiple additional plugins at once, you can specify
>multiple parameters described above, for example "<tt>nmake /f NTMakefile NTLM=1 SRP=1 OPT=1</tt>"
>
><h3>limitations</h3>
>
>Currently all plugins but KerberosV4 (kerberos4.c) and PASSDSS (passdss.c) can be built on Windows.
>However limited testings was done for some plugins as listed below:
>
><ul>
><li>GSSAPI - tested using CyberSafe,
><li>SASLDB - only SleepyCat version can be built,
><li>SQL - using SQLITE, not tested
></ul>
>
>The following executables were built and tested (to some extend):
>In sample:
><ul>
><li>sample-client
><li>sample-server
></ul>
>In utils:
><ul>
><li>sasldblistusers2
><li>saslpasswd2
><li>testsuite
><li>pluginviewer
></ul>
>
>Note that saslauthd is <em>NOT</em> in this list.
>
><h3>testing</h3>
>
>
><h3>creating an MSI</h3>
>
></body>
>
></html>
>{Á.`..~ÁRELEASE-DATE04e04e|Á	COPYRIGHT}Á(READMEÁVERSION;4803004eÁVERSIONCopyright (c) 1988-1997 Sam Leffler
>Copyright (c) 1991-1997 Silicon Graphics, Inc.
>
>Permission to use, copy, modify, distribute, and sell this software and 
>its documentation for any purpose is hereby granted without fee, provided
>that (i) the above copyright notices and this permission notice appear in
>all copies of the software and related documentation, and (ii) the names of
>Sam Leffler and Silicon Graphics may not be used in any advertising or
>publicity relating to the software without the specific, prior written
>permission of Sam Leffler and Silicon Graphics.
>
>THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, 
>EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY 
>WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.  
>
>IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR
>ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND,
>OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
>WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF 
>LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE 
>OF THIS SOFTWARE.
>$Header: /cvs/maptools/cvsroot/libtiff/README,v 1.5 2004/10/30 13:44:45 dron Exp $
>
>
>TIFF Software Distribution
>--------------------------
>This file is just a placeholder; all the documentation is now in
>HTML in the html directory.  To view the documentation point your
>favorite WWW viewer at html/index.html; e.g.
>
>    netscape html/index.html
>
>If you don't have an HTML viewer then you can read the HTML source
>or fetch a PostScript version of this documentation from the directory
>
>    ftp://ftp.remotesensing.org/pub/libtiff/
>
>If you can't hack either of these options then basically what you
>want to do is:
>
>    % ./configure
>    % make
>    % su
>    # make install
>
>More information, email contacts, and mailing list information can be 
>found online at http://www.remotesensing.org/libtiff/.
>
>
>Use and Copyright
>-----------------
>Silicon Graphics has seen fit to allow us to give this work away.  It
>is free.  There is no support or guarantee of any sort as to its
>operations, correctness, or whatever.  If you do anything useful with
>all or parts of it you need to honor the copyright notices.   I would
>also be interested in knowing about it and, hopefully, be acknowledged.
>
>The legal way of saying that is:
>
>Copyright (c) 1988-1997 Sam Leffler
>Copyright (c) 1991-1997 Silicon Graphics, Inc.
>
>Permission to use, copy, modify, distribute, and sell this software and 
>its documentation for any purpose is hereby granted without fee, provided
>that (i) the above copyright notices and this permission notice appear in
>all copies of the software and related documentation, and (ii) the names of
>Sam Leffler and Silicon Graphics may not be used in any advertising or
>publicity relating to the software without the specific, prior written
>permission of Sam Leffler and Silicon Graphics.
>
>THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, 
>EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY 
>WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.  
>
>IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR
>ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND,
>OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
>WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF 
>LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE 
>OF THIS SOFTWARE.
>20060323
>3.8.2
>Á.`$..ÁLICENCE;4803004eÁAUTHORSÁÀLICENCETHE MAIN PCRE LIBRARY
>---------------------
>
>Written by:       Philip Hazel
>Email local part: ph10
>Email domain:     cam.ac.uk
>
>University of Cambridge Computing Service,
>Cambridge, England.
>
>Copyright (c) 1997-2007 University of Cambridge
>All rights reserved
>
>
>THE C++ WRAPPER LIBRARY
>-----------------------
>
>Written by:       Google Inc.
>
>Copyright (c) 2007 Google Inc
>All rights reserved
>
>####
>PCRE LICENCE
>------------
>
>PCRE is a library of functions to support regular expressions whose syntax
>and semantics are as close as possible to those of the Perl 5 language.
>
>Release 7 of PCRE is distributed under the terms of the "BSD" licence, as
>specified below. The documentation for PCRE, supplied in the "doc"
>directory, is distributed under the same terms as the software itself.
>
>The basic library functions are written in C and are freestanding. Also
>included in the distribution is a set of C++ wrapper functions.
>
>
>THE BASIC LIBRARY FUNCTIONS
>---------------------------
>
>Written by:       Philip Hazel
>Email local part: ph10
>Email domain:     cam.ac.uk
>
>University of Cambridge Computing Service,
>Cambridge, England.
>
>Copyright (c) 1997-2007 University of Cambridge
>All rights reserved.
>
>
>THE C++ WRAPPER FUNCTIONS
>-------------------------
>
>Contributed by:   Google Inc.
>
>Copyright (c) 2007, Google Inc.
>All rights reserved.
>
>
>THE "BSD" LICENCE
>-----------------
>
>Redistribution and use in source and binary forms, with or without
>modification, are permitted provided that the following conditions are met:
>
>    * Redistributions of source code must retain the above copyright notice,
>      this list of conditions and the following disclaimer.
>
>    * Redistributions in binary form must reproduce the above copyright
>      notice, this list of conditions and the following disclaimer in the
>      documentation and/or other materials provided with the distribution.
>
>    * Neither the name of the University of Cambridge nor the name of Google
>      Inc. nor the names of their contributors may be used to endorse or
>      promote products derived from this software without specific prior
>      written permission.
>
>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
>AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
>IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
>ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
>LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
>CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
>SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
>INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
>CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
>ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
>POSSIBILITY OF SUCH DAMAGE.
>
>End
>Á.`$..ÁREADME;4803004eeÁAUTHORSÁCHANGESÁCOPYINGÁ READMEMonty <monty@xiph.org>
>
>and the rest of the Xiph.Org Foundation.
>
>Version 1.1.3 (2005 November 27)
>
> * Correct a bug in the granulepos field of pages where no packet ends
> * New VS2003 and XCode builds, minor fixes to other builds
> * documentation fixes and cleanup
> 
>Version 1.1.2 (2004 September 23)
>
> * fix a bug with multipage packet assembly after seek
>
>Version 1.1.1 (2004 September 12)
>
> * various bugfixes
> * important bugfix for 64-bit platforms
> * various portability fixes
> * autotools cleanup from Thomas Vander Stichele
> * Symbian OS build support from Colin Ward at CSIRO
> * new multiplexed Ogg stream documentation
>
>Version 1.1 (2003 November 17)
>
> * big-endian bitpacker routines for Theora
> * various portability fixes
> * improved API documenation
> * RFC 3533 documentation of the format by Silvia Pfeiffer at CSIRO
> * RFC 3534 documentation of the application/ogg mime-type by Linus Walleij
> 
>Version 1.0 (2002 July 19)
>
> * First stable release
> * little-endian bitpacker routines for Vorbis
> * basic Ogg bitstream sync and coding support
>
>Copyright (c) 2002, Xiph.org Foundation
>
>Redistribution and use in source and binary forms, with or without
>modification, are permitted provided that the following conditions
>are met:
>
>- Redistributions of source code must retain the above copyright
>notice, this list of conditions and the following disclaimer.
>
>- Redistributions in binary form must reproduce the above copyright
>notice, this list of conditions and the following disclaimer in the
>documentation and/or other materials provided with the distribution.
>
>- Neither the name of the Xiph.org Foundation nor the names of its
>contributors may be used to endorse or promote products derived from
>this software without specific prior written permission.
>
>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
>A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE FOUNDATION
>OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
>SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
>LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
>DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
>THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
>(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
>OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>********************************************************************
>*                                                                  *
>* THIS FILE IS PART OF THE OggVorbis SOFTWARE CODEC SOURCE CODE.   *
>* USE, DISTRIBUTION AND REPRODUCTION OF THIS LIBRARY SOURCE IS     *
>* GOVERNED BY A BSD-STYLE SOURCE LICENSE INCLUDED WITH THIS SOURCE *
>* IN 'COPYING'. PLEASE READ THESE TERMS BEFORE DISTRIBUTING.       *
>*                                                                  *
>* THE OggVorbis SOURCE CODE IS (C) COPYRIGHT 1994-2002             *
>* by the Xiph.Org Foundation http://www.xiph.org/                  *
>*                                                                  *
>********************************************************************
>
>WHAT'S HERE:
>
>This source distribution includes libogg and nothing else.  Other modules 
>(eg, the modules vorbis, vorbis-tools and vorbis-plugins for the Vorbis 
>codec) contain the codec libraries for use with Ogg bitstreams.
>
>Directory:
>
>./src  		The source for libogg, a BSD-license inplementation of 
>		the public domain Ogg bitstream format
>
>./include       Library API headers and codebooks
>
>./debian        Rules/spec files for building Debian .deb packages
>
>./doc           Ogg specification documents
>
>./win32		Win32 projects and build automation
>
>./mac		MacOS 9 projects and build automation
>
>WHAT IS OGG?:
>
>Ogg project codecs use the Ogg bitstream format to arrange the raw,
>compressed bitstream into a more robust, useful form.  For example,
>the Ogg bitstream makes seeking, time stamping and error recovery
>possible, as well as mixing several sepearate, concurrent media
>streams into a single physical bitstream.
>
>CONTACT:
>
>The Ogg homepage is located at 'http://www.xiph.org/ogg/'.
>Up to date technical documents, contact information, source code and
>pre-built utilities may be found there.
>
>BUILDING FROM REPOSITORY SOURCE:
>
>A standard svn build should consist of nothing more than:
>
>./autogen.sh
>make 
>
>and as root if desired :
>
>make install
>
>This will install the Ogg libraries (static and shared) into
>/usr/local/lib, includes into /usr/local/include and API manpages
>(once we write some) into /usr/local/man.
>
>BUILDING FROM TARBALL DISTRIBUTIONS:
>
>./configure
>make
>
>and optionally (as root):
>make install
>
>BUILDING RPMS:
>
>RPMs may be built by:
>
>make dist
>rpm -ta libogg-<version>.tar.gz
>
>BUILDING ON WIN32:
>
>Use the project file in the win32 directory.  It should compile out of the box.
>You can also run one of the batch files from the commandline.
>
>E.g.: build_ogg_dynamic
>
>BUILDING ON MACOS 9:
>
>Ogg on MacOS 9 is built using CodeWarrior 5.3.  To build it, first
>open ogg/mac/libogg.mcp, switch to the "Targets" pane, select
>everything, and make the project.  In ogg/mac/Output you will now have
>both debug and final versions of Ogg shared libraries to link your
>projects against.
>
>To build a project using Ogg, add access paths to your CodeWarrior
>project for the ogg/include and ogg/mac/Output folders.  Be sure that
>"interpret DOS and Unix paths" is turned on in your project; it can be
>found in the "access paths" pane in your project settings.  Now simply
>add the shared libraries you need to your project (OggLib at least)
>and #include "ogg/ogg.h" wherever you need to acces Ogg functionality.
>
>(Build instructions for Ogg codecs such as vorbis are similar and may
>be found in those source modules' README files)
>
>$Id: README 10478 2005-11-28 04:23:35Z giles $
>Á.`$..ÁREADME;4803004eeÁAUTHORSÁCOPYINGÁ°READMEMonty <monty@xiph.org>
>
>and the rest of the Xiph.org Foundation.
>Copyright (c) 2002-2004 Xiph.org Foundation
>
>Redistribution and use in source and binary forms, with or without
>modification, are permitted provided that the following conditions
>are met:
>
>- Redistributions of source code must retain the above copyright
>notice, this list of conditions and the following disclaimer.
>
>- Redistributions in binary form must reproduce the above copyright
>notice, this list of conditions and the following disclaimer in the
>documentation and/or other materials provided with the distribution.
>
>- Neither the name of the Xiph.org Foundation nor the names of its
>contributors may be used to endorse or promote products derived from
>this software without specific prior written permission.
>
>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
>A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE FOUNDATION
>OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
>SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
>LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
>DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
>THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
>(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
>OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>********************************************************************
>*                                                                  *
>* THIS FILE IS PART OF THE OggVorbis SOFTWARE CODEC SOURCE CODE.   *
>* USE, DISTRIBUTION AND REPRODUCTION OF THIS LIBRARY SOURCE IS     *
>* GOVERNED BY A BSD-STYLE SOURCE LICENSE INCLUDED WITH THIS SOURCE *
>* IN 'COPYING'. PLEASE READ THESE TERMS BEFORE DISTRIBUTING.       *
>*                                                                  *
>* THE OggVorbis SOURCE CODE IS (C) COPYRIGHT 1994-2007             *
>* by the Xiph.org Foundation, http://www.xiph.org/                 *
>*                                                                  *
>********************************************************************
>
>Vorbis is a general purpose audio and music encoding format
>contemporary to MPEG-4's AAC and TwinVQ, the next generation beyond
>MPEG audio layer 3. Unlike the MPEG sponsored formats (and other
>proprietary formats such as RealAudio G2 and Windows' flavor of the
>month), the Vorbis CODEC specification belongs to the public domain.
>All the technical details are published and documented, and any
>software entity may make full use of the format without license 
>fee, royalty or patent concerns.
>
>This package contains:
>
>* libvorbis, a BSD-style license software implementation of
>  the Vorbis specification by the Xiph.Org Foundation 
>  (http://www.xiph.org/) 
>
>* libvorbisfile, a BSD-style license convenience library
>  built on Vorbis designed to simplify common uses
>
>* libvorbisenc, a BSD-style license library that provides a simple,
>  programmatic encoding setup interface 
>
>* example code making use of libogg, libvorbis, libvorbisfile and
>  libvorbisenc
>
>WHAT'S HERE:
>
>This source distribution includes libvorbis and an example
>encoder/player to demonstrate use of libvorbis as well as
>documentation on the Ogg Vorbis audio coding format.
>
>You'll need libogg (distributed separately) to compile this library.
>A more comprehensive set of utilities is available in the vorbis-tools
>package.
>
>Directory:
>
>./lib  		The source for the libraries, a BSD-license implementation
>		of the public domain Ogg Vorbis audio encoding format.
>
>./include       Library API headers
>
>./debian        Rules/spec files for building Debian .deb packages
>
>./doc           Vorbis documentation
>
>./examples	Example code illustrating programmatic use of libvorbis, 
>		libvorbisfile and libvorbisenc
>
>./mac 		Codewarrior project files and build tweaks for MacOS.
>
>./macosx 	Project files for MacOS X.
>
>./win32		Win32 projects files and build automation
>
>./vq 		Internal utilities for training/building new LSP/residue 
>		and auxiliary codebooks.
>
>CONTACT:
>
>The Ogg homepage is located at 'http://www.xiph.org/ogg/'.
>Vorbis's homepage is located at 'http://www.xiph.org/vorbis/'.
>Up to date technical documents, contact information, source code and
>pre-built utilities may be found there.
>
>The user website for Ogg Vorbis software and audio is http://vorbis.com/
>
>BUILDING FROM TRUNK:
>
>Development source is under subversion revision control at 
>http://svn.xiph.org/trunk/vorbis/. You will also need the 
>newest versions of autoconf, automake, and libtool in order
>to compile vorbis from development source. A configure script
>is provided for you in the source tarball distributions.
>
>  [update or checkout latest source]
>  ./autogen.sh
>  make 
>
>and as root if desired:
>
>  make install
>
>This will install the vorbis libraries (static and shared) into
>/usr/local/lib, includes into /usr/local/include and API manpages
>(once we write some) into /usr/local/man.
>
>BUILDING FROM TARBALL DISTRIBUTIONS:
>
>  ./configure
>  make
>
>and optionally (as root):
>  make install
>
>BUILDING RPMS:
>
>after normal configuring:
>
>  make dist
>  rpm -ta libvorbis-<version>.tar.gz
>
>BUILDING ON MACOS 9:
>
>Vorbis on MacOS 9 is built using Metroworks CodeWarrior.  To build it, 
>first verify that the Ogg libraries are already built following the
>instructions in the Ogg module README.  Open vorbis/mac/libvorbis.mcp,
>switch to the "Targets" pane, select everything, and make the project.
>Do the same thing to build libvorbisenc.mcp, and libvorbisfile.mcp (in
>that order).  In vorbis/mac/Output you will now have both debug and final
>versions of Vorbis shared libraries to link your projects against.
>
>To build a project using Ogg Vorbis, add access paths to your
>CodeWarrior project for the ogg/include, ogg/mac/Output,
>vorbis/include, and vorbis/mac/Output folders.  Be sure that
>"interpret DOS and Unix paths" is turned on in your project; it can
>be found in the "access paths" pane in your project settings.  Now
>simply add the shared libraries you need to your project (OggLib and
>VorbisLib at least) and #include "ogg/ogg.h" and "vorbis/codec.h"
>wherever you need to access Ogg and Vorbis functionality.
>
>Á.`$..ÁREADME;4803004eeÁLICENSEÁÀREADME/*-
> * $Id: LICENSE,v 12.7 2007/05/17 15:14:46 bostic Exp $
> */
>
>The following is the license that applies to this copy of the Berkeley DB
>software.  For a license to use the Berkeley DB software under conditions
>other than those described here, or to purchase support for this software,
>please contact Oracle at berkeleydb-info_us@oracle.com.
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>/*
> * Copyright (c) 1990,2007 Oracle.  All rights reserved.
> *
> * Redistribution and use in source and binary forms, with or without
> * modification, are permitted provided that the following conditions
> * are met:
> * 1. Redistributions of source code must retain the above copyright
> *    notice, this list of conditions and the following disclaimer.
> * 2. Redistributions in binary form must reproduce the above copyright
> *    notice, this list of conditions and the following disclaimer in the
> *    documentation and/or other materials provided with the distribution.
> * 3. Redistributions in any form must be accompanied by information on
> *    how to obtain complete source code for the DB software and any
> *    accompanying software that uses the DB software.  The source code
> *    must either be included in the distribution or be available for no
> *    more than the cost of distribution plus a nominal fee, and must be
> *    freely redistributable under reasonable conditions.  For an
> *    executable file, complete source code means the source code for all
> *    modules it contains.  It does not include source code for modules or
> *    files that typically accompany the major components of the operating
> *    system on which the executable file runs.
> *
> * THIS SOFTWARE IS PROVIDED BY ORACLE ``AS IS'' AND ANY EXPRESS OR
> * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> * WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
> * NON-INFRINGEMENT, ARE DISCLAIMED.  IN NO EVENT SHALL ORACLE BE LIABLE
> * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
> * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
> * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
> * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
> * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
> * OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
> * IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> */
>/*
> * Copyright (c) 1990, 1993, 1994, 1995
> *	The Regents of the University of California.  All rights reserved.
> *
> * Redistribution and use in source and binary forms, with or without
> * modification, are permitted provided that the following conditions
> * are met:
> * 1. Redistributions of source code must retain the above copyright
> *    notice, this list of conditions and the following disclaimer.
> * 2. Redistributions in binary form must reproduce the above copyright
> *    notice, this list of conditions and the following disclaimer in the
> *    documentation and/or other materials provided with the distribution.
> * 3. Neither the name of the University nor the names of its contributors
> *    may be used to endorse or promote products derived from this software
> *    without specific prior written permission.
> *
> * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
> * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
> * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
> * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
> * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
> * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
> * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
> * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
> * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
> * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
> * SUCH DAMAGE.
> */
>/*
> * Copyright (c) 1995, 1996
> *	The President and Fellows of Harvard University.  All rights reserved.
> *
> * Redistribution and use in source and binary forms, with or without
> * modification, are permitted provided that the following conditions
> * are met:
> * 1. Redistributions of source code must retain the above copyright
> *    notice, this list of conditions and the following disclaimer.
> * 2. Redistributions in binary form must reproduce the above copyright
> *    notice, this list of conditions and the following disclaimer in the
> *    documentation and/or other materials provided with the distribution.
> * 3. Neither the name of the University nor the names of its contributors
> *    may be used to endorse or promote products derived from this software
> *    without specific prior written permission.
> *
> * THIS SOFTWARE IS PROVIDED BY HARVARD AND ITS CONTRIBUTORS ``AS IS'' AND
> * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
> * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
> * ARE DISCLAIMED.  IN NO EVENT SHALL HARVARD OR ITS CONTRIBUTORS BE LIABLE
> * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
> * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
> * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
> * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
> * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
> * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
> * SUCH DAMAGE.
> */
>Berkeley DB 4.6.21: (September 27, 2007)
>
>This is version 4.6.21 of Berkeley DB from Oracle.  To view release and
>installation documentation, load the distribution file docs/index.html
>into your web browser.
>Á.`..ÁBanners.MakefileÁBLURBÁ
>DISCLAIMER03004eÁCHANGESÁREADME.IRIX004e0Á,READMEÁREADME.NIS;4803004eeÁT
>README.NIS@(#) BLURB 1.28 97/03/21 19:27:18
>
>With this package you can monitor and filter incoming requests for the
>SYSTAT, FINGER, FTP, TELNET, RLOGIN, RSH, EXEC, TFTP, TALK, and other
>network services.
>
>The package provides tiny daemon wrapper programs that can be installed
>without any changes to existing software or to existing configuration
>files.  The wrappers report the name of the client host and of the
>requested service; the wrappers do not exchange information with the
>client or server applications, and impose no overhead on the actual
>conversation between the client and server applications.
>
>This patch upgrades the tcp wrappers version 7.5 source code to
>version 7.6.  The source-routing protection in version 7.5 was not
>as strong as it could be. And all this effort was not needed with
>modern UNIX systems that can already stop source-routed traffic in
>the kernel. Examples are 4.4BSD derivatives, Solaris 2.x, and Linux.
>
>This release does not introduce new features. Do not bother applying
>this patch when you built your version 7.x tcp wrapper without
>enabling the KILL_IP_OPTIONS compiler switch; when you can disable
>IP source routing options in the kernel; when you run a UNIX version
>that pre-dates 4.4BSD, such as SunOS 4. Such systems are unable to
>receive source-routed connections and are therefore not vulnerable
>to IP spoofing attacks with source-routed TCP connections.
>
>A complete change log is given in the CHANGES document.  As always,
>problem reports and suggestions for improvement are welcome.
>
>	Wietse Venema (wietse@wzv.win.tue.nl),
>	Department of Mathematics and Computing Science,
>	Eindhoven University of Technology,
>	The Netherlands.
>
>	Currently visiting IBM T.J. Watson Research, Hawthorne NY, USA.
># @(#) Banners.Makefile 1.3 97/02/12 02:13:18
>#
># Install this file as the Makefile in your directory with banner files.
># It will convert a prototype banner text to a form that is suitable for
># the ftp, telnet, rlogin, and other services. 
># 
># You'll have to comment out the IN definition below if your daemon
># names don't start with `in.'.
>#
># The prototype text should live in the banners directory, as a file with
># the name "prototype". In the prototype text you can use %<character>
># sequences as described in the hosts_access.5 manual page (`nroff -man'
># format).  The sequences will be expanded while the banner message is
># sent to the client. For example:
>#
>#	Hello %u@%h, what brings you here?
>#
># Expands to: Hello username@hostname, what brings you here? Note: the
># use of %u forces a client username lookup.
>#
># In order to use banners, build the tcp wrapper with -DPROCESS_OPTIONS
># and use hosts.allow rules like this:
>#
>#	daemons ... : clients ... : banners /some/directory ...
>#
># Of course, nothing prevents you from using multiple banner directories.
># For example, one banner directory for clients that are granted service,
># one banner directory for rejected clients, and one banner directory for
># clients with a hostname problem.
>#
>SHELL	= /bin/sh
>IN	= in.
>BANNERS	= $(IN)telnetd $(IN)ftpd $(IN)rlogind # $(IN)fingerd $(IN)rshd
>
>all:	$(BANNERS)
>
>$(IN)telnetd: prototype
>	cp prototype $@
>	chmod 644 $@
>
>$(IN)ftpd: prototype
>	sed 's/^/220-/' prototype > $@
>	chmod 644 $@
>
>$(IN)rlogind: prototype nul
>	( ./nul ; cat prototype ) > $@
>	chmod 644 $@
>
># Other services: banners may interfere with normal operation
># so they should probably be used only when refusing service.
># In particular, banners don't work with standard rsh daemons.
># You would have to use an rshd that has built-in tcp wrapper
># support, for example the rshd that is part of the logdaemon
># utilities.
>
>$(IN)fingerd: prototype
>	cp prototype $@
>	chmod 644 $@
>
>$(IN)rshd: prototype nul
>	( ./nul ; cat prototype ) > $@
>	chmod 644 $@
>
># In case no /dev/zero available, let's hope they have at least
># a C compiler of some sort.
>
>nul:
>	echo 'main() { write(1,"",1); return(0); }' >nul.c
>	$(CC) $(CFLAGS) -s -o nul nul.c
>	rm -f nul.c
>Request: after building the programs, please run the `tcpdchk' wrapper
>configuration checker. See the `tcpdchk.8' manual page (`nroff -man'
>format) for instructions. `tcpdchk' automatically identifies the most
>common configuration problems, and will save you and me a lot of time.
>
>Changes per release 7.6 (Mar 1997)
>==================================
>
>- Improved the anti source-routing protection. The code in version
>7.5 was not as strong as it could be, because I tried to be compatible
>with Linux. That was a mistake. Sorry for the inconvenience.
>
>- The program no longer terminates case of a source-routed connection,
>making the IP-spoofing code more usable for long-running daemons.
>
>- When syslogging DNS hostname problems, always stop after a limited
>number of characters.
>
>Changes per release 7.5 (Feb 1997)
>==================================
>
>- Optionally refuse source-routed TCP connections requests altogether.
>Credits to Niels Provos of Universitaet Hamburg.  File: fix_options.c.
>
>- Support for IRIX 6 (Lael Tucker).
>
>- Support for Amdahl UTS 2.1.5 (Richard E. Richmond).
>
>- Support for SINIX 5.42 (Klaus Nielsen).
>
>- SCO 5 now has vsyslog() (Bill Golden).
>
>- Hints and tips for dealing with IRIX inetd (Niko Makila, Aaron
>M Lee).
>
>- Support for BSD/OS (Paul Borman).
>
>- Support for Tandem (Emad Qawas).
>
>- Support for ISC (Frederick B. Cohen).
>
>- Workaround for UNICOS - it would choke on a setjmp() expression
>(Bruce Kelly). File: hosts_access.c, tcpdchk.c.
>
>- Increased the level of buffer overflow paranoia when printing
>unwanted IP options.  File: fix_options.c.
>
>Changes per release 7.4 (Mar 1996)
>==================================
>
>- IRIX 5.3 (and possibly, earlier releases, too) library routines call
>the non-reentrant strtok() routine. The result is that hosts may slip
>through allow/deny filters. Workaround is to not rely on the vendor's
>strtok() routine (#ifdef LIBC_CALLS_STRTOK). Credits to Th. Eifert
>(Aachen University) for spotting this one. This fix supersedes the
>earlier workaround for a similar problem in FreeBSD 2.0.
>
>Changes per release 7.3 (Feb 1996)
>==================================
>
>- More tests added to tcpdchk and tcpdmatch: make sure that the
>REAL_DAEMON_DIR actually is a directory and not a regular file;
>detect if tcpd recursively calls itself.
>
>- Edwin Kremer found an amusing fencepost error in the xgets()
>routine: lines longer than BUFLEN characters would be garbled.
>
>- The access control routines now refuse to execute "dangerous" actions
>such as `twist' when they are called from within a resident process.
>This prevents you from shooting yourself into the foot with critical
>systems programs such as, e.g., portmap or rpcbind.
>
>- Support for Unicos 8.x (Bruce Kelly). The program now closes the
>syslog client socket before running the real daemon: Cray UNICOS
>refuses to checkpoint processes with open network ports.
>
>- Support for MachTen UNIX (Albert M.C Tam).
>
>- Support for Interactive UNIX R3.2 V4.0 (Bobby D. Wright).
>
>- Support for SCO 3.2v5.0.0 OpenServer 5 (bob@odt.handy.com)
>
>- Support for Unixware 1.x and Unixware 2.x.  The old Unixware Makefile
>rule was broken. Sorry about that.
>
>- Some FreeBSD 2.0 libc routines call strtok() and severely mess up the
>allow/deny rule processing. This is very bad. Workaround:  call our own
>strtok() clone (#ifdef USE_STRSEP).
>
>- The programs now log a warning when they detect that a non-existent
>banner directory is specified.
>
>- The hosts_access.3 manual page used obsolete names for the RQ_*
>constants.
>
>Changes per release 7.2 (Jan 1995)
>==================================
>
>- Added a note to the README and manpages on using the IDENT service to
>detect sequence number spoofing and other host impersonation attacks.
>
>- Portability: ConvexOS puts RPC version numbers before the daemon path
>name (Jukka Ukkonen).
>
>- Portability: the AIX compiler disliked the strchr() declaration
>in socket.c.  I should have removed it when I included <string.h>.
>
>- Backwards compatibility: some people relied on the old leading dot or
>trailing dot magic in daemon process names.
>
>- Backwards compatibility: hostname lookup remains enabled when
>-DPARANOID is turned off. In order to disable hostname lookups you
>must turn off -DALWAYS_HOSTNAME.
>
>- Eliminated false complaints from the tcpdmatch/tcpdchk configuration
>checking programs about process names not in inetd.conf or about KNOWN
>username patterns.
>
>Changes per release 7.1 (Jan 1995)
>==================================
>
>- Portability: HP-UX permits you to break inetd.conf entries with
>backslash-newline.
>
>- Portability: EP/IX has no putenv() and some inetd.conf entries are
>spread out over two lines.
>
>- Portability: SCO with NIS support has no *netgrent() routines.
>
>Changes per release 7.0 (Jan 1995) 
>==================================
>
>- Added a last-minute workaround for a Solaris 2.4 gethostbyname()
>foulup with multi-homed hosts in DNS through NIS mode.
>
>- Added a last-minute defense against TLI weirdness: address lookups
>apparently succeed but the result netbuf is empty (ticlts transport).
>
>- Dropped several new solutions that were in need of a problem. Beta
>testers may recognize what new features were kicked out during the last
>weeks before release 7.0 came out. Such is life.
>
>- Got rid of out the environment replacement routines, at least for
>most architectures. One should not have to replace working system
>software when all that is needed is a 4.4BSD setenv() emulator.
>
>- By popular request I have added an option to send banner messages to
>clients. There is a Banners.Makefile that gives some aid for sites that
>are going to use this feature. John C. Wingenbach did some pioneering
>work here. I used to think that banners are frivolous. Now that I had
>a personal need for them I know that banners can be useful.
>
>- At last: an extensible functional interface to the pattern matching
>engine. request_init() and request_set() accept a variable-length
>name-value argument list.  The result can be passed to hosts_access().
>
>- When PARANOID mode is disabled (compile time), the wrapper does no
>hostname lookup or hostname double checks unless required by %letter
>expansions, or by access control rules that match host names.  This is
>useful for sites that don't care about internet hostnames anyway.
>Inspired by the authors of the firewalls and internet security book.
>
>- When PARANOID mode is disabled (compile time), hosts with a name/name
>or name/address conflict can be matched with the PARANOID host wildcard
>pattern, so that you can take some intelligent action instead of just
>dropping clients. Like showing a banner that explains the problem.
>
>- New percent escapes: %A expands to the server address; %H expands to
>the corresponding hostname (or address if no name is available); %n and
>%N expand to the client and server hostname (or "unknown"); %s expands
>to everything we know about the server endpoint (the opposite of the %c
>sequence for client information).
>
>- Symmetry: server and client host information is now treated on equal
>footing, so that we can reuse a lot of code.
>
>- Lazy evaluation of host names, host addresses, usernames, and so on,
>to avoid doing unnecessary work.
>
>- Dropping #ifdefs for some archaic systems made the code simpler.
>
>- Dropping the FAIL pattern made the pattern matcher much simpler.  Run
>the "tcpdchk" program to scan your access control files for any uses of
>this obscure language feature.
>
>- Moving host-specific pattern matching from string_match() to the
>host_match() routine made the code more accurate.  Run the "tcpdchk"
>program to scan your access control files for any dependencies on
>undocumented or obscure language features that are gone.
>
>- daemon@host patterns trigger on clients that connect to a specific
>internet address.  This can be useful for service providers that offer
>multiple ftp or www archives on different internet addresses, all
>belonging to one and the same host (www.foo.com, ftp.bar.com, you get
>the idea).  Inspired by a discussion with Rop Gonggrijp, Cor Bosman,
>and Casper Dik, and earlier discussions with Adrian van Bloois.
>
>- The new "tcpdchk" program critcizes all your access control rules and
>inetd.conf entries. Great for spotting obscure bugs in my own hosts.xxx
>files. This program also detects hosts with name/address conflicts and
>with other DNS-related problems. See the "tcpdchk.8" manual page.
>
>- The "tcpdmatch" program replaces the poor old "try" command. The new
>program looks in your inetd.conf file and therefore produces much more
>accurate predictions. In addition, it detects hosts with name/address
>conflicts and with other DNS-related problems. See the "tcpdmatch.8"
>manual page.  The inetd.conf lookup was suggested by Everett F Batey.
>
>- In the access control tables, the `=' between option name and value
>is no longer required.
>
>- Added 60-second timeout to the safe_finger command, to cover another
>potential problem. Suggested by Peter Wemm.
>
>- Andrew Maffei provided code that works with WIN-TCP on NCR System V.4
>UNIX. It reportedly works with versions 02.02.01 and 02.03.00. The code
>pops off all streams modules above the device driver, pushes the timod
>module to get at the peer address, and then restores the streams stack
>to the initial state.
>
>Changes per release 6.3 (Mar 1994)
>==================================
>
>- Keepalives option, to get rid of stuck daemons when people turn off
>their PC while still connected. Files: options.c, hosts_options.5.
>
>- Nice option, to calm down network daemons that take away too much CPU
>time. Files: options.c, hosts_options.5.
>
>- Ultrix perversion: the environ global pointer may be null. The
>environment replacement routines now check for this. File: environ.c.
>
>- Fixed a few places that still assumed the socket is on standard
>input. Fixed some error messages that did not provide access control
>file name and line number.  File: options.c.
>
>- Just when I was going to release 6.2 I received code for Dynix/PTX.
>That code is specific to PTX 2.x, so I'll keep around my generic
>PTX code just in case. The difference is in the handling of UDP
>services.  Files:  tli_sequent.[hc].
>
>Changes per release 6.2 (Feb 1994)
>==================================
>
>- Resurrected my year-old code to reduce DNS load by appending a dot to
>the gethostbyname() argument. This feature is still experimental and it
>may go away if it causes more problems than it solves. File: socket.c.
>
>- Auxiliary code for the Pyramid, BSD universe. Karl Vogel figured out
>what was missing: yp_get_default_domain() and vfprintf(). Files:
>workarounds.c, vfprintf.c.
>
>- Improved support for Dynix/PTX. The wrapper should now be able to
>deal with all TLI over IP services. File: ptx.c.
>
>- The try command now uses the hostname that gethostbyaddr() would
>return, instead of the hostname returned by gethostbyname(). This can
>be significant on systems with NIS that have short host names in the
>hosts map. For example, gethostbyname("wzv.win.tue.nl") returns
>"wzv.win.tue.nl"; gethostbyaddr(131.155.210.17) returns "wzv", and
>that is what we should test with. File: try.c.
>
>Changes per release 6.1 (Dec 1993)
>==================================
>
>- Re-implemented all environment access routines. Most systems have
>putenv() but no setenv(), some systems have setenv() but no putenv(),
>and there are even systems that have neither setenv() nor putenv(). The
>benefit of all this is that more systems can now be treated in the same
>way. File:  environ.c.
>
>- Workaround for a weird problem with DG/UX when the wrapper is run as
>nobody (i.e. fingerd). For some reason the ioctl(fd, I_FIND, "sockmod")
>call fails even with socket-based applications. The "fix" is to always
>assume sockets when the ioctl(fd, I_FIND, "timod") call fails. File:
>fromhost.c. Thanks to Paul de Vries (vries@dutentb.et.tudelft.nl) for
>helping me to figure out this one.
>
>- Implemented a workaround for Dynix/PTX and other systems with TLI
>that lack some essential support routines. Thanks to Bugs Brouillard
>(brouill@hsuseq.humboldt.edu) for the hospitality to try things out.
>The trick is to temporarily switch to the socket API to identify the
>client, and to switch back to TLI when done.  It still does not work
>right for basic network services such as telnet. File: fromhost.c.
>
>- Easy-to-build procedures for SCO UNIX, ConvexOS with UltraNet, EP/IX,
>Dynix 3.2, Dynix/PTX. File: Makefile.
>
>- Variable rfc931 timeout. Files: rfc931.c, options.c, log_tcp.h, try.c.
>
>- Further simplification of the rfc931 code. File: rfc931.c.
>
>- The fromhost() interface stinks: I cannot change that, but at least
>the from_sock() and from_tli() functions now accept a file descriptor
>argument.
>
>- Fixed a buglet: fromhost() would pass a garbage file descriptor to
>the isastream() call.
>
>- On some systems the finger client program lives in /usr/bsd. File:
>safe_finger.c.
>
>Changes per release 6.0 (Sept 1993)
>===================================
>
>- Easy build procedures for common platforms (sun, ultrix, aix, hpux
>and others).
>
>- TLI support, System V.4 style (Solaris, DG/UX).
>
>- Username lookup integrated with the access control language.
>Selective username lookups are now the default (was: no username
>lookups).
>
>- A safer finger command for booby traps. This one solves a host of
>possible problems with automatic reverse fingers. Thanks, Borja Marcos
>(borjam@we.lc.ehu.es) for some inspiring discussions.
>
>- KNOWN pattern that matches hosts whose name and address are known.
>
>- Cleanup of diagnostics. Errors in access-control files are now shown
>with file name and line number.
>
>- With AIX 3.2, hostnames longer than 32 would be truncated.  This
>caused hostname verification failures, so that service would be refused
>when paranoid mode was enabled.  Found by:  Adrian van Bloois
>(A.vanBloois@info.nic.surfnet.nl).
>
>- With some IRIX versions, remote username lookups failed because the
>fgets() library function does not handle partial read()s from sockets.
>Found by:  Daniel O'Callaghan (danny@austin.unimelb.edu.au).
>
>- Added a DISCLAIMER document to help you satisfy legal departments.
>
>The extension language module has undergone major revisions and
>extensions.  Thanks, John P. Rouillard (rouilj@ra.cs.umb.edu) for
>discussions, experiments, and for being a good guinea pig. The
>extensions are documented in hosts_options.5, and are enabled by
>editing the Makefile STYLE macro definition.
>
>- (Extension language) The ":" separator may now occur within options
>as long as it is protected with a backslash. A warning is issued when
>a rule ends on ":".
>
>- (Extension language) Better verification mode. When the `try' command
>is run, each option function now explains what it would do.
>
>- (Extension language) New "allow" and "deny" keywords so you can now
>have all rules within a single file. See "nroff -man hosts_options.5"
>for examples.
>
>- (Extension language) "linger" keyword to set the socket linger time
>(SO_LINGER). From:  Marc Boucher <marc@cam.org>.
>
>- (Extension language) "severity" keyword to turn the logging noise up
>or down. Many sites wanted a means to shut up the program; other sites
>wanted to emphasize specific events.  Adapted from code contributed
>by Dave Mitchell <D.Mitchell@dcs.shef.ac.uk>.
>
>Changes per release 5.1 (Mar 1993)
>==================================
>
>- The additional protection against source-routing attacks from hosts
>that pretend to have someone elses network address has become optional
>because it causes kernel panics with SunOS <= 4.1.3.
>
>Changes per release 5.0 (Mar 1993)
>==================================
>
>- Additional protection against source-routing attacks from hosts that
>pretend to have someone elses network address. For example, the address
>of a trusted host within your own network.
>
>- The access control language has been extended with a simple but
>powerful operator that greatly simplifies the design of rule sets (ALL:
>.foo.edu EXCEPT dialup.foo.edu). Blank lines are permitted, and long
>lines can be continued with backslash-newline.
>
>- All configurable stuff, including path names, has been moved into the
>Makefile so that you no longer have to hack source code to just
>configure the programs.
>
>- Ported to Solaris 2. TLI-based applications not yet supported.
>Several workarounds for System V bugs.
>
>- A small loophole in the netgroup lookup code was closed, and the
>remote username lookup code was made more portable.
>
>- Still more documentation. The README file now provides tutorial
>sections with introductions to client, server, inetd and syslogd.
>
>Changes per release 4.3 (Aug 1992) 
>==================================
>
>- Some sites reported that connections would be rejected because
>localhost != localhost.domain. The host name checking code now
>special-cases localhost (problem reported by several sites).
>
>- The programs now report an error if an existing access control file
>cannot be opened (e.g. due to lack of privileges).  Until now, the
>programs would just pretend that the access control file does not exist
>(reported by Darren Reed, avalon@coombs.anu.edu.au).
>
>- The timeout period for remote userid lookups was upped to 30 seconds,
>in order to cope with slow hosts or networks.  If this is too long for
>you, adjust the TIMEOUT definition in file rfc931.c (problem reported
>by several sites).
>
>- On hosts with more than one IP network interface, remote userid
>lookups could use the IP address of the "wrong" local interface.  The
>problem and its solution were discussed on the rfc931-users mailing
>list.  Scott Schwartz (schwartz@cs.psu.edu) folded the fix into the
>rfc931.c module.
>
>- The result of % expansion (in shell commands) is now checked for
>stuff that may confuse the shell; it is replaced by underscores
>(problem reported by Icarus Sparry, I.Sparry@gdr.bath.ac.uk).
>
>- A portability problem was fixed that caused compile-time problems
>on a CRAY (problem reported by Michael Barnett, mikeb@rmit.edu.au).
>
>Changes per release 4.0 (Jun 1992)
>==================================
>
>1 - network daemons no longer have to live within a common directory
>2 - the access control code now uses both the host address and name
>3 - an access control pattern that supports netmasks
>4 - additional protection against forged host names
>5 - a pattern that matches hosts whose name or address lookup fails
>6 - an operator that prevents hosts or services from being matched
>7 - optional remote username lookup with the RFC 931 protocol
>8 - an optional umask to prevent the creation of world-writable files
>9 - hooks for access control language extensions
>10 - last but not least, thoroughly revised documentation.
>
>Changes per release 3.0 (Oct 1991)
>==================================
>
>Enhancements over the previous release are: support for datagram (UDP
>and RPC) services, and execution of shell commands when a (remote host,
>requested service) pair matches a pattern in the access control tables.
>
>Changes per release 2.0 (May 1991)
>==================================
>
>Enhancements over the previous release are: protection against rlogin
>and rsh attacks through compromised domain name servers, optional
>netgroup support for systems with NIS (formerly YP), and an extension
>of the wild card patterns supported by the access control files.
>
>Release 1.0 (Jan 1991)
>/************************************************************************
>* Copyright 1995 by Wietse Venema.  All rights reserved.  Some individual
>* files may be covered by other copyrights.
>*
>* This material was originally written and compiled by Wietse Venema at
>* Eindhoven University of Technology, The Netherlands, in 1990, 1991,
>* 1992, 1993, 1994 and 1995.
>*
>* Redistribution and use in source and binary forms are permitted
>* provided that this entire copyright notice is duplicated in all such
>* copies.
>*
>* This software is provided "as is" and without any expressed or implied
>* warranties, including, without limitation, the implied warranties of
>* merchantibility and fitness for any particular purpose.
>************************************************************************/
>@(#) README 1.30 97/03/21 19:27:21
>
>This is the 7.6 version of the TCP/IP daemon wrapper package.
>
>Thank you for using this program. If you like it, send me a postcard.
>My postal address is at the bottom of this file.
>
>Read the BLURB file for a brief summary of what is new. The CHANGES
>file gives a complete account of differences with respect to previous
>releases.
>
>Announcements of new releases of this software are posted to Usenet
>(comp.security.unix, comp.unix.admin), to the cert-tools mailing list,
>and to a dedicated mailing list.  You can subscribe to the dedicated
>mailing list by sending an email message to majordomo@wzv.win.tue.nl
>with in the body (not subject):  subscribe tcp-wrappers-announce.
>
>Table of contents
>-----------------
>
>    1 - Introduction
>    2 - Disclaimer
>    3 - Tutorials
>                3.1 - How it works
>                3.2 - Where the logging information goes
>    4 - Features
>                4.1 - Access control
>                4.2 - Host name spoofing
>                4.3 - Host address spoofing
>                4.4 - Client username lookups
>                4.5 - Language extensions
>		4.6 - Multiple ftp/gopher/www archives on one host
>		4.7 - Banner messages
>		4.8 - Sequence number guessing
>    5 - Other works
>                5.1 - Related documents
>                5.2 - Related software
>    6 - Limitations
>                6.1 - Known wrapper limitations
>                6.2 - Known system software bugs
>    7 - Configuration and installation
>                7.1 - Easy configuration and installation
>                7.2 - Advanced configuration and installation
>                7.3 - Daemons with arbitrary path names
>                7.4 - Building and testing the access control rules
>                7.5 - Other applications
>    8 - Acknowledgements
>
>1 - Introduction
>----------------
>
>With this package you can monitor and filter incoming requests for the
>SYSTAT, FINGER, FTP, TELNET, RLOGIN, RSH, EXEC, TFTP, TALK, and other
>network services.
>
>It supports both 4.3BSD-style sockets and System V.4-style TLI. Praise
>yourself lucky if you don't know what that means.
>
>The package provides tiny daemon wrapper programs that can be installed
>without any changes to existing software or to existing configuration
>files.  The wrappers report the name of the client host and of the
>requested service; the wrappers do not exchange information with the
>client or server applications, and impose no overhead on the actual
>conversation between the client and server applications.
>
>Optional features are: access control to restrict what systems can
>connect to what network daemons; client user name lookups with the RFC
>931 etc. protocol; additional protection against hosts that pretend to
>have someone elses host name; additional protection against hosts that
>pretend to have someone elses host address.
>
>The programs are very portable. Build procedures are provided for many
>common (and not so common) environments, and guidelines are provided in
>case your environment is not among them.
>
>Requirements are that network daemons are spawned by a super server
>such as the inetd; a 4.3BSD-style socket programming interface and/or
>System V.4-style TLI programming interface; and the availability of a
>syslog(3) library and of a syslogd(8) daemon.  The wrappers should run
>without modification on any system that satisfies these requirements.
>Workarounds have been implemented for several common bugs in systems
>software.
>
>What to do if this is your first encounter with the wrapper programs:
>1) read the tutorial sections for an introduction to the relevant
>concepts and terminology; 2) glance over the security feature sections
>in this document; 3) follow the installation instructions (easy or
>advanced). I recommend that you first use the default security feature
>settings.  Run the wrappers for a few days to become familiar with
>their logs, before doing anything drastic such as cutting off access or
>installing booby traps.
>
>2 - Disclaimer
>--------------
>
>The wrapper programs rely on source address information obtained from
>network packets. This information is provided by the client host. It is
>not 100 percent reliable, although the wrappers do their best to expose
>forgeries.
>
>In the absence of cryptographic protection of message contents, and of
>cryptographic authentication of message originators, all data from the
>network should be treated with sound scepticism.
>
>THIS RESTRICTION IS BY NO MEANS SPECIFIC TO THE TCP/IP PROTOCOLS.
>
>3 - Tutorials
>-------------
>
>The tutorial sections give a gentle introduction to the operation of
>the wrapper programs, and introduce some of the terminology that is
>used in the remainder of the document: client, server, the inetd and
>syslogd daemons, and their configuration files.
>
>3.1 - How it works
>------------------
>
>Almost every application of the TCP/IP protocols is based on a client-
>server model. For example, when a user invokes the telnet command to
>connect to one of your systems, a telnet server process is executed on
>the target host. The telnet server process connects the user to a login
>process. A few examples of client and server programs are shown in the
>table below:
>
>              client   server    application
>              --------------------------------
>              telnet   telnetd   remote login
>              ftp      ftpd      file transfer
>              finger   fingerd   show users
>
>The usual approach is to run one single daemon process that waits for
>all kinds of incoming network connections. Whenever a connection is
>established, this daemon (usually called inetd) runs the appropriate
>server program and goes back to sleep, waiting for other connections.
>
>The wrapper programs rely on a simple, but powerful mechanism.  Instead
>of directly running the desired server program, the inetd is tricked
>into running a small wrapper program. The wrapper logs the client host
>name or address and performs some additional checks.  When all is well,
>the wrapper executes the desired server program and goes away.
>
>The wrapper programs have no interaction with the client user (or with
>the client process).  Nor do the wrappers interact with the server
>application. This has two major advantages: 1) the wrappers are
>application-independent, so that the same program can protect many
>kinds of network services; 2) no interaction also means that the
>wrappers are invisible from outside (at least for authorized users).
>
>Another important property is that the wrapper programs are active only
>when the initial contact between client and server is established. Once
>a wrapper has done its work there is no overhead on the client-server
>conversation.
>
>The simple mechanism has one major drawback: the wrappers go away after
>the initial contact between client and server processes, so the
>wrappers are of little use with network daemons that service more than
>one client.  The wrappers would only see the first client attempt to
>contact such a server. The NFS mount daemon is a typical example of a
>daemon that services requests from multiple clients. See the section on
>related software for ways to deal with such server programs.
>
>There are two ways to use the wrapper programs:
>
>1) The easy way: move network daemons to some other directory and fill
>   the resulting holes with copies of the wrapper programs.  This
>   approach involves no changes to system configuration files, so there
>   is very little risk of breaking things.
>
>2) The advanced way: leave the network daemons alone and modify the
>   inetd configuration file.  For example, an entry such as:
>
>     tftp  dgram  udp  wait  root  /usr/etc/tcpd  in.tftpd -s /tftpboot
>
>   When a tftp request arrives, inetd will run the wrapper program
>   (tcpd) with a process name `in.tftpd'.  This is the name that the
>   wrapper will use when logging the request and when scanning the
>   optional access control tables.  `in.tftpd' is also the name of the
>   server program that the wrapper will attempt to run when all is
>   well.  Any arguments (`-s /tftpboot' in this particular example) are
>   transparently passed on to the server program.
>
>For an account of the history of the wrapper programs, with real-life
>examples, see the section below on related documents.
>
>3.2 - Where the logging information goes
>----------------------------------------
>
>The wrapper programs send their logging information to the syslog
>daemon (syslogd). The disposition of the wrapper logs is determined by
>the syslog configuration file (usually /etc/syslog.conf). Messages are
>written to files, to the console, or are forwarded to a @loghost. Some
>syslogd versions can even forward messages down a |pipeline.
>
>Older syslog implementations (still found on Ultrix systems) only
>support priority levels ranging from 9 (debug-level messages) to 0
>(alerts). All logging information of the specified priority level or
>more urgent is written to the same destination.  In the syslog.conf
>file, priority levels are specified in numerical form.  For example,
>
>    8/usr/spool/mqueue/syslog
>
>causes all messages with priority 8 (informational messages), and
>anything that is more urgent, to be appended to the file
>/usr/spool/mqueue/syslog.
>
>Newer syslog implementations support message classes in addition to
>priority levels.  Examples of message classes are: mail, daemon, auth
>and news. In the syslog.conf file, priority levels are specified with
>symbolic names: debug, info, notice, ..., emerg. For example,
>
>    mail.debug                  /var/log/syslog
>
>causes all messages of class mail with priority debug (or more urgent)
>to be appended to the /var/log/syslog file.
>
>By default, the wrapper logs go to the same place as the transaction
>logs of the sendmail daemon. The disposition can be changed by editing
>the Makefile and/or the syslog.conf file. Send a `kill -HUP' to the
>syslogd after changing its configuration file. Remember that syslogd,
>just like sendmail, insists on one or more TABs between the left-hand
>side and the right-hand side expressions in its configuration file.
>
>Solaris 2.x note: the syslog daemon depends on the m4 macro processor.
>The m4 program is installed as part of the software developer packages.
>
>Trouble shooting note: when the syslogging does not work as expected,
>run the program by hand (`syslogd -d') and see what really happens.
>
>4 - Features
>------------
>
>4.1 - Access control
>--------------------
>
>When compiled with -DHOSTS_ACCESS, the wrapper programs support a
>simple form of access control.  Access can be controlled per host, per
>service, or combinations thereof. The software provides hooks for the
>execution of shell commands when an access control rule fires; this
>feature may be used to install "booby traps".  For details, see the
>hosts_access.5 manual page, which is in `nroff -man' format. A later
>section describes how you can test your access control rules.
>
>Access control can also be used to connect clients to the "right"
>service. What is right may depend on the requested service, the origin
>of the request, and what host address the client connects to. Examples:
>
>(1) A gopher or www database speaks native language when contacted from
>    within the country, otherwise it speaks English.
>
>(2) A service provider offers different ftp, gopher or www services
>    with different internet hostnames from one host (section 4.6).
>
>Access control is enabled by default. It can be turned off by editing
>the Makefile, or by providing no access control tables. The install
>instructions below describe the Makefile editing process.
>
>The hosts_options.5 manual page (`nroff -man' format) documents an
>extended version of the access control language. The extensions are
>disabled by default. See the section below on language extensions.
>
>Later System V implementations provide the Transport Level Interface
>(TLI), a network programming interface that performs functions similar
>to the Berkeley socket programming interface.  Like Berkeley sockets,
>TLI was designed to cover multiple protocols, not just Internet.
>
>When the wrapper discovers that the TLI interface sits on top of a
>TCP/IP or UDP/IP conversation it uses this knowledge to provide the
>same functions as with traditional socket-based applications.  When
>some other protocol is used underneath TLI, the host address will be
>some universal magic cookie that may not even be usable for access
>control purposes.
>
>4.2 - Host name spoofing
>------------------------
>
>With some network applications, such as RSH or RLOGIN, the client host
>name plays an important role in the authentication process. Host name
>information can be reliable when lookups are done from a _local_ hosts
>table, provided that the client IP address can be trusted.
>
>With _distributed_ name services, authentication schemes that rely on
>host names become more problematic. The security of your system now may
>depend on some far-away DNS (domain name server) outside your own
>control. 
>
>The wrapper programs verify the client host name that is returned by
>the address->name DNS server, by asking for a second opinion.  To this
>end, the programs look at the name and addresses that are returned by
>the name->address DNS server, which may be an entirely different host. 
>
>If any name or address discrepancies are found, or if the second DNS
>opinion is not available, the wrappers assume that one of the two name
>servers is lying, and assume that the client host pretends to have
>someone elses host name.
>
>When compiled with -DPARANOID, the wrappers will always attempt to look
>up and double check the client host name, and will always refuse
>service in case of a host name/address discrepancy.  This is a
>reasonable policy for most systems.
>
>When compiled without -DPARANOID, the wrappers by default still perform
>hostname lookup. You can match hosts with a name/address discrepancy
>with the PARANOID wildcard and decide whether or not to grant service.
>
>Automatic hostname verification is enabled by default. Automatic
>hostname lookups and verification can be turned off by editing the
>Makefile. The configuration and installation section below describes
>the Makefile editing process.
>
>4.3 - Host address spoofing
>---------------------------
>
>While host name spoofing can be found out by asking a second opinion,
>it is much harder to find out that a host claims to have someone elses
>network address. And since host names are deduced from network
>addresses, address spoofing is at least as effective as name spoofing.
>
>The wrapper programs can give additional protection against hosts that
>claim to have an address that lies outside their own network.  For
>example, some far-away host that claims to be a trusted host within
>your own network. Such things are possible even while the impersonated
>system is up and running.
>
>This additional protection is not an invention of my own; it has been
>present for at least five years in the BSD rsh and rlogin daemons.
>Unfortunately, that feature was added *after* 4.3 BSD came out, so that
>very few, if any, UNIX vendors have adopted it.  Our site, and many
>other ones, has been running these enhanced daemons for several years,
>and without any ill effects.
>
>When the wrapper programs are compiled with -DKILL_IP_OPTIONS, the
>programs refuse to service TCP connections with IP source routing
>options. -DKILL_IP_OPTIONS is not needed on modern UNIX systems
>that can stop source-routed traffic in the kernel. Examples are
>4.4BSD derivatives, Solaris 2.x, and Linux. See your system manuals
>for details.
>
>If you are going to use this feature on SunOS 4.1.x you should apply
>patch 100804-03+ or 101790-something depending on your SunOS version.
>Otherwise you may experience "BAD TRAP" and "Data fault" panics when
>the getsockopt() system call is executed after a TCP RESET has been
>received. This is a kernel bug, it is not the fault of the wrappers.
>
>The feature is disabled by default. It can be turned on by editing the
>Makefile.  The configuration and installation section below describes
>the Makefile editing process.
>
>UDP services do not benefit from this additional protection. With UDP,
>all you can be certain of is the network packet's destination address.
>
>4.4 - Client username lookups
>-----------------------------
>
>The protocol proposed in RFC 931 provides a means to obtain the client
>user name from the client host.  The requirement is that the client
>host runs an RFC 931-compliant daemon. The information provided by such
>a daemon is not intended to be used for authentication purposes, but it
>can provide additional information about the owner of a TCP connection.
>
>The RFC 931 protocol has diverged into different directions (IDENT,
>TAP, RFC 1413). To add to the confusion, they all use the same network
>port.  The daemon wrappers implement a common subset of the protocols.
>
>There are some limitations: the number of hosts that run an RFC 931 (or
>compatible) daemon is limited (but growing); client user name lookups
>do not work for datagram (UDP) services. More seriously, client user
>name lookups can cause noticeable delays with connections from non-UNIX
>PCs. Recent PC software seem to have fixed this (for example NCSA
>telnet). The wrappers use a 10-second timeout for RFC931 lookups, to
>accommodate slow networks and slow hosts.
>
>By default, the wrappers will do username lookup only when the access
>control rules require them to do so (via user@host client patterns, see
>the hosts_access.5 manual page) or when the username is needed for
>%<letter> expansions.
>
>You can configure the wrappers to always perform client username
>lookups, by editing the Makefile.  The client username lookup timeout
>period (10 seconds default) can be changed by editing the Makefile. The
>installation sections below describe the Makefile editing process.
>
>On System V with TLI-based network services, client username lookups
>will be possible only when the underlying network protocol is TCP/IP.
>
>4.5 - Language extensions
>-------------------------
>
>The wrappers sport only a limited number of features. This is for a
>good reason: programs that run at high privilege levels must be easy to
>verify. And the smaller a program, the easier to verify. There is,
>however, a provision to add features.
>
>The options.c module provides a framework for language extensions.
>Quite a few extensions have already been implemented; they are
>documented in the hosts_options.5 document, which is in `nroff -man'
>format. Examples: changing the severity level at which a request for
>service is logged; "allow" and "deny" keywords; running a customized
>server instead of the standard one; many others.
>
>The language extensions are not enabled by default because they
>introduce an incompatible change to the access control language
>syntax.  Instructions to enable the extensions are given in the
>Makefile.
>
>4.6 - Multiple ftp/gopher/www archives on one host
>--------------------------------------------------
>
>Imagine one host with multiple internet addresses. These addresses do
>not need to have the same internet hostname. Thus, it is possible to
>offer services with different internet hostnames from just one host.
>
>Service providers can use this to offer organizations a presence on the
>"net" with their own internet hostname, even when those organizations
>aren't connected to the Internet at all.  To the end user it makes no
>difference, because applications use internet hostnames.
>
>There are several ways to assign multiple addresses to one machine.
>The nice way is to take an existing network interface and to assign
>additional internet addresses with the `ifconfig' command. Examples:
>
>    Solaris 2:	ifconfig le0:1 <address> netmask <mask> up
>    4.4 BSD:	ifconfig en0 alias <address> netmask <mask>
>
>On other systems one has to increase the number of network interfaces:
>either with hardware interfaces, or with pseudo interfaces like SLIP or
>PPP.  The interfaces do not need to be attached to anything. They just
>need to be up and to be assigned a suitable internet address and mask.
>
>With the wrapper software, `daemon@host' access control patterns can be
>used to distinguish requests by the network address that they are aimed
>at.  Judicious use of the `twist' option (see the hosts_options.5 file,
>`nroff -man' format) can guide the requests to the right server.  These
>can be servers that live in separate chroot areas, or servers modified
>to take additional context from the command line, or a combination.
>
>Another way is to modify gopher or www listeners so that they bind to
>only one specific network address. Multiple gopher or www servers can
>then be run side by side, each taking requests sent to its respective
>network address.
>
>4.7 - Banner messages
>---------------------
>
>Some sites are required to present an informational message to users
>before they attempt to login.  Banner messages can also be useful when
>denying service:  instead of simply dropping the connection a polite
>explanation is given first. Finally, banners can be used to give your
>system a more personal touch.
>
>The wrapper software provides easy-to-use tools to generate pre-login
>banners for ftp, telnet, rlogin etc. from a single prototype banner
>textfile.  Details on banners and on-the-fly %<letter> expansions are
>given in the hosts_options.5 manual page (`nroff -man' format). An
>example is given in the file Banners.Makefile.
>
>In order to support banner messages the wrappers have to be built with
>language extensions enabled. See the section on language extensions.
>
>4.8 - Sequence number guessing
>------------------------------
>
>Recently, systems came under attack from intruders that exploited a
>well-known weakness in TCP/IP sequence number generators.  This
>weakness allows intruders to impersonate trusted hosts. Break-ins have
>been reported via the rsh service. In fact, any network service can be
>exploited that trusts the client host name or address.
>
>A long-term solution is to stop using network services that trust the
>client host name or address, and to use data encryption instead.
>
>A short-term solution, as outlined in in CERT advisory CA-95:01, is to
>configure network routers so that they discard datagrams from "outside"
>with an "inside" source address. This approach is most fruitful when
>you do not trust any hosts outside your local network.
>
>The IDENT (RFC931 etc.) client username lookup protocol can help to
>detect host impersonation attacks.  Before accepting a client request,
>the wrappers can query the client's IDENT server and find out that the
>client never sent that request.
>
>When the client host provides IDENT service, a negative IDENT lookup
>result (the client matches `UNKNOWN@host') is strong evidence of a host
>impersonation attack.
>
>A positive IDENT lookup result (the client matches `KNOWN@host') is
>less trustworthy.  It is possible for an attacker to spoof both the
>client request and the IDENT lookup connection, although doing so
>should be much harder than spoofing just a client request. Another
>possibility is that the client's IDENT server is lying.
>
>Client username lookups are described in more detail in a previous
>section. Pointers to IDENT daemon software are described in the section
>on related software.
>
>5 - Other works
>---------------
>
>5.1 - Related documents
>-----------------------
>
>The war story behind the tcp wrapper tools is described in:
>
>    W.Z. Venema, "TCP WRAPPER, network monitoring, access control and
>    booby traps", UNIX Security Symposium III Proceedings (Baltimore),
>    September 1992. 
>
>    ftp.win.tue.nl:/pub/security/tcp_wrapper.ps.Z (postscript)
>    ftp.win.tue.nl:/pub/security/tcp_wrapper.txt.Z (flat text)
>
>The same cracker is also described in:
>
>    W.R. Cheswick, "An Evening with Berferd, In Which a Cracker is
>    Lured, Endured, and Studied", Proceedings of the Winter USENIX
>    Conference (San Francisco), January 1992.
>
>    research.att.com:/dist/internet_security/berferd.ps
>
>An updated version of the latter paper appeared in:
>
>    W.R. Cheswick, S.M. Bellovin, "Firewalls and Internet Security",
>    Addison-Wesley, 1994.
>
>Discussions on internet firewalls are archived on ftp.greatcircle.com.
>Subscribe to the mailing list by sending a message to 
>
>    majordomo@greatcircle.com
>
>With in the body (not subject): subscribe firewalls.
>
>5.2 - Related software
>----------------------
>
>Network daemons etc. with enhanced logging capabilities can generate
>massive amounts of information: our 150+ workstations generate several
>hundred kbytes each day. egrep-based filters can help to suppress some
>of the noise.  A more powerful tool is the Swatch monitoring system by
>Stephen E. Hansen and E. Todd Atkins. Swatch can process log files in
>real time and can associate arbitrary actions with patterns; its
>applications are by no means restricted to security.  Swatch is
>available ftp.stanford.edu, directory /general/security-tools/swatch.
>
>Socks, described in the UNIX Security III proceedings, can be used to
>control network traffic from hosts on an internal network, through a
>firewall host, to the outer world. Socks consists of a daemon that is
>run on the firewall host, and of a library with routines that redirect
>application socket calls through the firewall daemon.  Socks is
>available from s1.gov in /pub/firewalls/socks.tar.Z.
>
>For a modified Socks version by Ying-Da Lee (ylee@syl.dl.nec.com) try
>ftp.nec.com, directory /pub/security/socks.cstc.
>
>Tcpr is a set of perl scripts by Paul Ziemba that enable you to run ftp
>and telnet commands across a firewall. Unlike socks it can be used with
>unmodified client software. Available from ftp.alantec.com, /pub/tcpr.
>
>The TIS firewall toolkit provides a multitude of tools to build your
>own internet firewall system. ftp.tis.com, directory /pub/firewalls.
>
>Versions of rshd and rlogind, modified to report the client user name
>in addition to the client host name, are available for anonymous ftp
>(ftp.win.tue.nl:/pub/security/logdaemon-XX.tar.Z).  These programs are
>drop-in replacements for SunOS 4.x, Ultrix 4.x, SunOS 5.x and HP-UX
>9.x. This archive also contains ftpd/rexecd/login versions that support
>S/Key or SecureNet one-time passwords in addition to traditional UNIX
>reusable passwords.
>
>The securelib shared library by William LeFebvre can be used to control
>access to network daemons that are not run under control of the inetd
>or that serve more than one client, such as the NFS mount daemon that
>runs until the machine goes down.  Available from eecs.nwu.edu, file
>/pub/securelib.tar.
>
>xinetd (posted to comp.sources.unix) is an inetd replacement that
>provides, among others, logging, username lookup and access control.
>However, it does not support the System V TLI services, and involves
>much more source code than the daemon wrapper programs. Available
>from ftp.uu.net, directory /usenet/comp.sources.unix.
>
>netlog from Texas A&M relies on the SunOS 4.x /dev/nit interface to
>passively watch all TCP and UDP network traffic on a network.  The
>current version is on net.tamu.edu in /pub/security/TAMU.
>
>Where shared libraries or router-based packet filtering are not an
>option, an alternative portmap daemon can help to prevent hackers
>from mounting your NFS file systems using the proxy RPC facility.
>ftp.win.tue.nl:/pub/security/portmap-X.shar.Z was tested with SunOS
>4.1.X Ultrix 3.0 and Ultrix 4.x, HP-UX 8.x and some version of AIX. The
>protection is less effective than that of the securelib library because
>portmap is mostly a dictionary service.
>
>An rpcbind replacement (the Solaris 2.x moral equivalent of portmap)
>can be found on ftp.win.tue.nl in /pub/security. It prevents hackers
>from mounting your NFS file systems by using the proxy RPC facility.
>
>Source for a portable RFC 931 (TAP, IDENT, RFC 1413) daemon by Peter
>Eriksson is available from ftp.lysator.liu.se:/pub/ident/servers.
>
>Some TCP/IP implementations come without syslog library. Some come with
>the library but have no syslog daemon. A replacement can be found in
>ftp.win.tue.nl:/pub/security/surrogate-syslog.tar.Z.  The fakesyslog
>library that comes with the nntp sources reportedly works well, too.
>
>6 - Limitations
>---------------
>
>6.1 - Known wrapper limitations
>-------------------------------
>
>Many UDP (and rpc/udp) daemons linger around for a while after they
>have serviced a request, just in case another request comes in.  In the
>inetd configuration file these daemons are registered with the `wait'
>option. Only the request that started such a daemon will be seen by the
>wrappers.  Such daemons are better protected with the securelib shared
>library (see: Related software).
>
>The wrappers do not work with RPC services over TCP. These services are
>registered as rpc/tcp in the inetd configuration file. The only non-
>trivial service that is affected by this limitation is rexd, which is
>used by the on(1) command. This is no great loss.  On most systems,
>rexd is less secure than a wildcard in /etc/hosts.equiv.
>
>Some RPC requests (for example: rwall, rup, rusers) appear to come from
>the server host. What happens is that the client broadcasts its request
>to all portmap daemons on its network; each portmap daemon forwards the
>request to a daemon on its own system. As far as the rwall etc.  daemons
>know, the request comes from the local host.
>
>Portmap and RPC (e.g. NIS and NFS) (in)security is a topic in itself.
>See the section in this document on related software.
>
>6.2 - Known system software bugs
>--------------------------------
>
>Workarounds have been implemented for several bugs in system software.
>They are described in the Makefile. Unfortunately, some system software
>bugs cannot be worked around. The result is loss of functionality.
>
>IRIX has so many bugs that it has its own README.IRIX file.
>
>Older ConvexOS versions come with a broken recvfrom(2) implementation.
>This makes it impossible for the daemon wrappers to look up the
>client host address (and hence, the name) in case of UDP requests.
>A patch is available for ConvexOS 10.1; later releases should be OK.
>
>With early Solaris (SunOS 5) versions, the syslog daemon will leave
>behind zombie processes when writing to logged-in users.  Workaround:
>increase the syslogd threshold for logging to users, or reduce the
>wrapper's logging severity.
>
>On some systems, the optional RFC 931 etc. client username lookups may
>trigger a kernel bug.  When a client host connects to your system, and
>the RFC 931 connection from your system to that client is rejected by a
>router, your kernel may drop all connections with that client.  This is
>not a bug in the wrapper programs: complain to your vendor, and don't
>enable client user name lookups until the bug has been fixed.
>
>Reportedly, SunOS 4.1.1, Next 2.0a, ISC 3.0 with TCP 1.3, and AIX 3.2.2
>and later are OK.
>
>Sony News/OS 4.51, HP-UX 8-something and Ultrix 4.3 still have the bug.
>Reportedly, a fix for Ultrix is available (CXO-8919).
>
>The following procedure can be used (from outside the tue.nl domain) to
>find out if your kernel has the bug. From the system under test, do:
>
>        % ftp 131.155.70.19
>
>This command attempts to make an ftp connection to our anonymous ftp
>server (ftp.win.tue.nl).  When the connection has been established, run
>the following command from the same system under test, while keeping
>the ftp connection open:
>
>        % telnet 131.155.70.19 111
>
>Do not forget the `111' at the end of the command. This telnet command
>attempts to connect to our portmap process.  The telnet command should
>fail with:  "host not reachable", or with a timeout error. If your ftp
>connection gets messed up, you have the bug. If the telnet command does
>not fail, please let me know a.s.a.p.!
>
>For those who care, the bug is that the BSD kernel code was not careful
>enough with incoming ICMP UNREACHABLE control messages (it ignored the
>local and remote port numbers, and therefore zapped *all* connections
>with the remote system). The bug is still present in the BSD NET/1
>source release (1989) but apparently has been fixed in BSD NET/2 (1991). 
>
>7 - Configuration and installation
>----------------------------------
>
>7.1 - Easy configuration and installation
>-----------------------------------------
>
>The "easy" recipe requires no changes to existing software or
>configuration files.  Basically, you move the daemons that you want to
>protect to a different directory and plug the resulting holes with
>copies of the wrapper programs.
>
>If you don't run Ultrix, you won't need the miscd wrapper program.  The
>miscd daemon implements among others the SYSTAT service, which produces
>the same output as the WHO command.
>
>Type `make' and follow the instructions.  The Makefile comes with
>ready-to-use templates for many common UNIX implementations (sun,
>ultrix, hp-ux, aix, irix,...). 
>
>IRIX has so many bugs that it has its own README.IRIX file.
>
>When the `make' succeeds the result is five executables (six in case of
>Ultrix).
>
>You can use the `tcpdchk' program to identify the most common problems
>in your wrapper and inetd configuration files.  
>
>With the `tcpdmatch' program you can examine how the wrapper would
>react to specific requests for service.  
>
>The `safe_finger' command should be used when you implement booby
>traps:  it gives better protection against nasty stuff that remote
>hosts may do in response to your finger probes.
>
>The `try-from' program tests the host and username lookup code.  Run it
>from a remote shell command (`rsh host /some/where/try-from') and it
>should be able to figure out from what system it is being called.
>
>The tcpd program can be used to monitor the telnet, finger, ftp, exec,
>rsh, rlogin, tftp, talk, comsat and other tcp or udp services that have
>a one-to-one mapping onto executable files.
>
>The tcpd program can also be used for services that are marked as
>rpc/udp in the inetd configuration file, but not for rpc/tcp services
>such as rexd.  You probably do not want to run rexd anyway. On most
>systems it is even less secure than a wildcard in /etc/hosts.equiv.
>
>With System V.4-style systems, the tcpd program can also handle TLI
>services. When TCP/IP or UDP/IP is used underneath TLI, tcpd provides
>the same functions as with socket-based applications. When some other
>protocol is used underneath TLI, functionality will be limited (no
>client username lookups, weird network address formats).
>
>Decide which services you want to monitor. Move the corresponding
>vendor-provided daemon programs to the location specified by the
>REAL_DAEMON_DIR constant in the Makefile, and fill the holes with
>copies of the tcpd program. That is, one copy of (or link to) the tcpd
>program for each service that you want to monitor. For example, to
>monitor the use of your finger service:
>
>    # mkdir REAL_DAEMON_DIR
>    # mv /usr/etc/in.fingerd REAL_DAEMON_DIR
>    # cp tcpd /usr/etc/in.fingerd
>
>The example applies to SunOS 4. With other UNIX implementations the
>network daemons live in /usr/libexec, /usr/sbin or in /etc, or have no
>"in." prefix to their names, but you get the idea.
>
>File protections: the wrapper, all files used by the wrapper, and all
>directories in the path leading to those files, should be accessible
>but not writable for unprivileged users (mode 755 or mode 555). Do not
>install the wrapper set-uid.
>
>Ultrix only:  If you want to monitor the SYSTAT service, move the
>vendor-provided miscd daemon to the location specified by the
>REAL_DAEMON_DIR macro in the Makefile, and install the miscd wrapper
>at the original miscd location.
>
>In the absence of any access-control tables, the daemon wrappers
>will just maintain a record of network connections made to your system.
>
>7.2 - Advanced configuration and installation
>---------------------------------------------
>
>The advanced recipe leaves your daemon executables alone, but involves
>simple modifications to the inetd configuration file.
>
>Type `make' and follow the instructions.  The Makefile comes with
>ready-to-use templates for many common UNIX implementations (sun,
>ultrix, hp-ux, aix, irix, ...). 
>
>IRIX users should read the warnings in the README.IRIX file first.
>
>When the `make' succeeds the result is five executables (six in case of
>Ultrix).
>
>You can use the `tcpdchk' program to identify the most common problems
>in your wrapper and inetd configuration files.  
>
>With the `tcpdmatch' program you can examine how the wrapper would
>react to specific requests for service.  
>
>The `try-from' program tests the host and username lookup code.  Run it
>from a remote shell command (`rsh host /some/where/try-from') and it
>should be able to figure out from what system it is being called.
>
>The `safe_finger' command should be used when you implement a booby
>trap:  it gives better protection against nasty stuff that remote hosts
>may do in response to your finger probes.
>
>The tcpd program can be used to monitor the telnet, finger, ftp, exec,
>rsh, rlogin, tftp, talk, comsat and other tcp or udp services that have
>a one-to-one mapping onto executable files.
>
>With System V.4-style systems, the tcpd program can also handle TLI
>services. When TCP/IP or UDP/IP is used underneath TLI, tcpd provides
>the same functions as with socket-based applications. When some other
>protocol is used underneath TLI, functionality will be limited (no
>client username lookups, weird network address formats).
>
>The tcpd program can also be used for services that are marked as
>rpc/udp in the inetd configuration file, but not for rpc/tcp services
>such as rexd.  You probably do not want to run rexd anyway. On most
>systems it is even less secure than a wildcard in /etc/hosts.equiv.
>
>Install the tcpd command in a suitable place. Apollo UNIX users will
>want to install it under a different name because the name "tcpd" is
>already taken; a suitable name would be "frontd".  
>
>File protections: the wrapper, all files used by the wrapper, and all
>directories in the path leading to those files, should be accessible
>but not writable for unprivileged users (mode 755 or mode 555). Do not
>install the wrapper set-uid.
>
>Then perform the following edits on the inetd configuration file
>(usually /etc/inetd.conf or /etc/inet/inetd.conf):
>
>    finger  stream  tcp     nowait  nobody  /usr/etc/in.fingerd     in.fingerd
>                                            ^^^^^^^^^^^^^^^^^^^
>becomes:
>
>    finger  stream  tcp     nowait  nobody  /usr/etc/tcpd           in.fingerd
>                                            ^^^^^^^^^^^^^
>Send a `kill -HUP' to the inetd process to make the change effective.
>Some IRIX inetd implementations require that you first disable the
>finger service (comment out the finger service and `kill -HUP' the
>inetd) before you can turn on the modified version. Sending a HUP
>twice seems to work just as well for IRIX 5.3, 6.0, 6.0.1 and 6.1.
>
>AIX note: you may have to execute the `inetimp' command after changing
>the inetd configuration file.
>
>The example applies to SunOS 4. With other UNIX implementations the
>network daemons live in /usr/libexec, /usr/sbin, or /etc, the network
>daemons have no "in." prefix to their names, or the username field in
>the inetd configuration file may be missing.
>
>When the finger service works as expected you can perform similar
>changes for other network services. Do not forget the `kill -HUP'.
>
>The miscd daemon that comes with Ultrix implements several network
>services. It decides what to do by looking at its process name. One of
>the services is systat, which is a kind of limited finger service.  If
>you want to monitor the systat service, install the miscd wrapper in a
>suitable place and update the inetd configuration file:
>
>    systat  stream  tcp     nowait  /suitable/place/miscd      systatd
>
>Ultrix 4.3 allows you to specify a user id under which the daemon will
>be executed. This feature is not documented in the manual pages.  Thus,
>the example would become:
>
>    systat  stream  tcp     nowait  nobody /suitable/place/miscd    systatd
>
>Older Ultrix systems still run all their network daemons as root.
>
>In the absence of any access-control tables, the daemon wrappers
>will just maintain a record of network connections made to your system.
>
>7.3 - Daemons with arbitrary path names
>---------------------------------------
>
>The above tcpd examples work fine with network daemons that live in a
>common directory, but sometimes that is not practical. Having soft
>links all over your file system is not a clean solution, either.
>
>Instead you can specify, in the inetd configuration file, an absolute
>path name for the daemon process name.  For example,
>
>    ntalk   dgram   udp     wait    root    /usr/etc/tcpd /usr/local/lib/ntalkd
>
>When the daemon process name is an absolute path name, tcpd ignores the
>value of the REAL_DAEMON_DIR constant, and uses the last path component
>of the daemon process name for logging and for access control.
>
>7.4 - Building and testing the access control rules
>---------------------------------------------------
>
>In order to support access control the wrappers must be compiled with
>the -DHOSTS_ACCESS option. The access control policy is given in the
>form of two tables (default: /etc/hosts.allow and /etc/hosts.deny).
>Access control is disabled when there are no access control tables, or
>when the tables are empty.
>
>If you haven't used the wrappers before I recommend that you first run
>them a couple of days without any access control restrictions. The
>logfile records should give you an idea of the process names and of the
>host names that you will have to build into your access control rules.
>
>The syntax of the access control rules is documented in the file
>hosts_access.5, which is in `nroff -man' format. This is a lengthy
>document, and no-one expects you to read it right away from beginning
>to end.  Instead, after reading the introductory section, skip to the
>examples at the end so that you get a general idea of the language.
>Then you can appreciate the detailed reference sections near the
>beginning of the document.
>
>The examples in the hosts_access.5 document (`nroff -man' format) show
>two specific types of access control policy:  1) mostly closed (only
>permitting access from a limited number of systems) and 2) mostly open
>(permitting access from everyone except a limited number of trouble
>makers). You will have to choose what model suits your situation best.
>Implementing a mixed policy should not be overly difficult either.
>
>Optional extensions to the access control language are described in the
>hosts_options.5 document (`nroff -man' format).
>
>The `tcpdchk' program examines all rules in your access control files
>and reports any problems it can find. `tcpdchk -v' writes to standard
>output a pretty-printed list of all rules. `tcpdchk -d' examines the
>hosts.access and hosts.allow files in the current directory. This
>program is described in the tcpdchk.8 document (`nroff -man' format).
>
>The `tcpdmatch' command can be used to try out your local access
>control files.  The command syntax is:
>
>    tcpdmatch process_name hostname (e.g.: tcpdmatch in.tftpd localhost)
>
>    tcpdmatch process_name address  (e.g.: tcpdmatch in.tftpd 127.0.0.1)
>
>This way you can simulate what decisions will be made, and what actions
>will be taken, when hosts connect to your own system. The program is
>described in the tcpdmatch.8 document (`nroff -man' format).
>
>Note 1: `tcpdmatch -d' will look for hosts.{allow,deny} tables in the
>current working directory. This is useful for testing new rules without
>bothering your users.
>
>Note 2: you cannot use the `tcpdmatch' command to simulate what happens
>when the local system connects to other hosts.
>
>In order to find out what process name to use, just use the service and
>watch the process name that shows up in the logfile.  Alternatively,
>you can look up the name from the inetd configuration file. Coming back
>to the tftp example in the tutorial section above:
>
>    tftp  dgram  udp  wait  root  /usr/etc/tcpd  in.tftpd -s /tftpboot
>
>This entry causes the inetd to run the wrapper program (tcpd) with a
>process name `in.tftpd'.  This is the name that the wrapper will use
>when scanning the access control tables. Therefore, `in.tftpd' is the
>process name that should be given to the `tcpdmatch' command. On your
>system the actual inetd.conf entry may differ (tftpd instead of
>in.tftpd, and no `root' field), but you get the idea.
>
>When you specify a host name, the `tcpdmatch' program will use both the
>host name and address. This way you can simulate the most common case
>where the wrappers know both the host address and the host name.  The
>`tcpdmatch' program will iterate over all addresses that it can find
>for the given host name.
>
>When you specify a host address instead of a host name, the `tcpdmatch'
>program will pretend that the host name is unknown, so that you can
>simulate what happens when the wrapper is unable to look up the client
>host name.
>
>7.5 - Other applications
>------------------------
>
>The access control routines can easily be integrated with other
>programs.  The hosts_access.3 manual page (`nroff -man' format)
>describes the external interface of the libwrap.a library.
>
>The tcpd program can even be used to control access to the mail
>service.  This can be useful when you suspect that someone is trying
>out some obscure sendmail bug, or when a remote site is misconfigured
>and keeps hammering your mail daemon.
>
>In that case, sendmail should not be run as a stand-alone network
>listener, but it should be registered in the inetd configuration file.
>For example:
>
>    smtp    stream  tcp     nowait  root    /usr/etc/tcpd /usr/lib/sendmail -bs
>
>You will still need to run one sendmail background process to handle
>queued-up outgoing mail. A command like:
>
>    /usr/lib/sendmail -q15m
>
>(no `-bd' flag) should take care of that. You cannot really prevent
>people from posting forged mail this way, because there are many
>unprotected smtp daemons on the network.
>
>8 - Acknowledgements
>--------------------
>
>Many people contributed to the evolution of the programs, by asking
>inspiring questions, by suggesting features or bugfixes, or by
>submitting source code.  Nevertheless, all mistakes and bugs in the
>wrappers are my own.
>
>Thanks to Brendan Kehoe (cs.widener.edu), Heimir Sverrisson (hafro.is)
>and Dan Bernstein (kramden.acf.nyu.edu) for feedback on an early
>release of this product.  The host name/address check was suggested by
>John Kimball (src.honeywell.com).  Apollo's UNIX environment has some
>peculiar quirks: Willem-Jan Withagen (eb.ele.tue.nl), Pieter
>Schoenmakers (es.ele.tue.nl) and Charles S. Fuller (wccs.psc.edu)
>provided assistance.  Hal R.  Brand (addvax.llnl.gov) told me how to
>get the client IP address in case of datagram-oriented services, and
>suggested the optional shell command feature.  Shabbir Safdar
>(mentor.cc.purdue.edu) provided a first version of a much-needed manual
>page.  Granville Boman Goza, IV (sei.cmu.edu) suggested to use the
>client IP address even when the host name is available.  Casper H.S.
>Dik (fwi.uva.nl) provided additional insight into DNS spoofing
>techniques.  The bogus daemon feature was inspired by code from Andrew
>Macpherson (BNR Europe Ltd).  Steve Bellovin (research.att.com)
>confirmed some of my suspicions about the darker sides of TCP/IP
>insecurity. Risks of automated fingers were pointed out by Borja Marcos
>(we.lc.ehu.es). Brad Plecs (jhuspo.ca.jhu.edu) was kind enough to try
>my early TLI code and to work out how DG/UX differs from Solaris.
>
>John P.  Rouillard (cs.umb.edu) deserves special mention for his
>persistent, but constructive, nagging about wrong or missing things,
>and for trying out and discussing embryonic code or ideas.
>
>Last but not least, Howard Chu (hanauma.jpl.nasa.gov), Darren Reed
>(coombs.anu.edu.au), Icarus Sparry (gdr.bath.ac.uk), Scott Schwartz
>(cs.psu.edu), John A. Kunze (violet.berkeley.edu), Daniel Len Schales
>(engr.latech.edu), Chris Turbeville (cse.uta.edu), Paul Kranenburg
>(cs.few.eur.nl), Marc Boucher (cam.org), Dave Mitchell
>(dcs.shef.ac.uk), Andrew Maffei, Adrian van Bloois, Rop Gonggrijp, John
>C. Wingenbach, Everett F. Batey  and many, many others provided fixes,
>code fragments, or ideas for improvements.
>
>        Wietse Venema (wietse@wzv.win.tue.nl)
>        Department of Mathematics and Computing Science
>        Eindhoven University of Technology
>        P.O. Box 513
>        5600 MB Eindhoven
>        The Netherlands
>
>	Currently visiting IBM T.J. Watson Research, Hawthorne NY, USA.
>@(#) README.IRIX 1.2 94/12/28 18:45:58
>
>In the past few months I received several messages with questions from
>people that tried to use my tcp wrapper on IRIX 5.x. Some mysteries
>could be solved via email, and then some remained.
>
>Today I finally had a chance to do some tests on someones IRIX 5.2
>system.  Here is my first-hand experience with wrapper release 6.3.
>
>(1) Inetd is broken. Normally one edits inetd.conf, sends a HUP signal
>    to inetd and that's it. With IRIX evil things happen:  inetd is too
>    stupid to remember that it is already listening on a port.
>
>    In order to modify an entry in inetd.conf, first comment it out
>    with a # at the beginning of the line, kill -HUP the inetd, then
>    uncomment the inetd.conf entry and kill -HUP again.
>
>    Even with this amount of care I have seen inetd messing up, like
>    calling rusersd when I make a talk connection.  Even killing and
>    restarting inetd does not solve all problems.
>
>    I find it hard to believe, it but the best thing to do with IRIX is
>    to reboot after changing inetd.conf.
>
>(2) When tcpd is built according to the irix4 Makefile rules, it
>    appears to work as expected with TCP-based services such as
>    fingerd, and with UDP-based services such as ntalk and tftp.
>
>(3) It does NOT work with RPC over UDP services such as rusersd and
>    rstatd:  the wrapper hangs in the recvfrom() system call, and I
>    have spent several hours looking for ways to work around it. No
>    way.  After finding that none of the applicable socket primitives
>    can be made to work (recvfrom recvmsg) I give up. So, the IRIX RPC
>    services cannot be wrapped until SGI fixes their system so that it
>    works like everyone elses code (HP Sun Dec AIX and so on).
>
>(4) I didn't even bother to try the RPC over TCP services.
>
>(5) When an IRIX 5.2 system is a NIS client, it can have problems with
>    hosts that have more than one address: the wrapper will see only
>    one address, and may complain when PARANOID mode is on. The fix is
>    to change the name service lookup order in /etc/resolv.conf so that
>    your system tries DNS before NIS (hostresorder bind nis local).
>
>(6) IRIX 5.2 is not System V.4, and it shows. Do not link with the
>    -lsocket and -lnsl libraries. They are completely broken, and the
>    wrapper will be unable to figure out the client internet address.
>    So, TLI services cannot be wrapped until SGI fixes their system so
>    that it works the way it is supposed to.
>
>I am not impressed by the quality of the IRIX system software.  There
>are many things that work on almost every other system except with IRIX.
>
>	Wietse
>@(#) README.NIS 1.2 96/02/11 17:24:52
>
>> Problem: I have several [machines] with multiple IP addresses, and
>> when they try to connect to a daemon with tcp wrapper, they are often
>> rejected.  I assume this is due to the -DPARANOID option, and depends
>> on which IP address is returned first from the nameserver for a given
>> name.   This behavior seems to be random, may depend on ordering in
>> the YP host map?
>
>[Note: the situation described below no longer exists. Presently, my
>internet gateway uses the same IP address on all interfaces.  To avoid
>confusion I have removed the old name wzv-gw.win.tue.nl from the DNS. I
>have kept the discussion below for educational reasons].
>
>NIS was not designed to handle multi-homed hosts.  With NIS, each
>address should have its own hostname. For example, wzv-gw is my
>gateway. It has two interfaces: one connected to the local ethernet,
>the other to a serial link. In the NIS it is registered as:
>
>        131.155.210.23  wzv-gw-ether
>        131.155.12.78   wzv-gw-slip
>
>In principle, wzv-gw could be the official name of one of these
>interfaces, or it could be an alias for both.
>
>The DNS was designed to handle multi-homed hosts. In the DNS my gateway
>is registered in zone win.tue.nl, with one name that has two A records:
>
>        wzv-gw  IN      A       131.155.210.23
>                IN      A       131.155.12.78
>
>And of course there are PTR records in zones 210.155.131.in-addr.arpa
>and 12.155.131.in-addr.arpa that point to wzv-gw.win.tue.nl.
>
>This setup does not cause any problems. You can test your name service
>with the two programs below. This is what they say on a local NIS client
>(both client and server running SunOS 4.1.3_U1):
>
>        % gethostbyname wzv-gw
>        Hostname:       wzv-gw.win.tue.nl
>        Aliases:        
>        Addresses:      131.155.210.23 131.155.12.78 
>
>        % gethostbyaddr 131.155.210.23
>        Hostname:       wzv-gw-ether
>        Aliases:        
>        Addresses:      131.155.210.23 
>
>        % gethostbyaddr 131.155.12.78
>        Hostname:       wzv-gw-slip
>        Aliases:        
>        Addresses:      131.155.12.78 
>
>Things seem less confusing when seen by a NIS client in a different
>domain (both client and server running SunOS 4.1.3_U1):
>
>        % gethostbyname wzv-gw.win.tue.nl
>        Hostname:       wzv-gw.win.tue.nl
>        Aliases:        
>        Addresses:      131.155.210.23 131.155.12.78 
>
>        % gethostbyaddr 131.155.210.23
>        Hostname:       wzv-gw.win.tue.nl
>        Aliases:        
>        Addresses:      131.155.12.78 131.155.210.23
>
>        % gethostbyaddr 131.155.12.78
>        Hostname:       wzv-gw.win.tue.nl
>        Aliases:        
>        Addresses:      131.155.210.23 131.155.12.78
>
>Alas, Solaris 2.4 still has problems. This is what I get on a Solaris
>2.4 NIS client, with a SunOS 4.1.3_U1 NIS server:
>
>	% gethostbyname wzv-gw.win.tue.nl
>	Hostname:       wzv-gw.win.tue.nl
>	Aliases:        131.155.210.23 wzv-gw.win.tue.nl 
>	Addresses:      131.155.12.78 
>
>The tcpd source comes with a workaround for this problem. The
>workaround is ugly and is not part of the programs attached below.
>
>
>#! /bin/sh
># This is a shell archive.  Remove anything before this line, then unpack
># it by saving it into a file and typing "sh file".  To overwrite existing
># files, type "sh file -c".  You can also feed this as standard input via
># unshar, or by typing "sh <file", e.g..  If this archive is complete, you
># will see the following message at the end:
>#		"End of shell archive."
># Contents:  gethostbyaddr.c gethostbyname.c
># Wrapped by wietse@wzv on Sun Jan  8 17:08:48 1995
>PATH=/bin:/usr/bin:/usr/ucb ; export PATH
>if test -f gethostbyaddr.c -a "${1}" != "-c" ; then 
>  echo shar: Will not over-write existing file \"gethostbyaddr.c\"
>else
>echo shar: Extracting \"gethostbyaddr.c\" $1073 characters$
>sed "s/^X//" >gethostbyaddr.c <<'END_OF_gethostbyaddr.c'
>X /*
>X  * gethostbyaddr tester. compile with:
>X  * 
>X  * cc -o gethostbyaddr gethostbyaddr.c (SunOS 4.x)
>X  * 
>X  * cc -o gethostbyaddr gethostbyaddr.c -lnsl (SunOS 5.x)
>X  * 
>X  * run as: gethostbyaddr address
>X  * 
>X  * Author: Wietse Venema, Eindhoven University of Technology, The Netherlands.
>X  */
>X
>X#include <sys/types.h>
>X#include <sys/socket.h>
>X#include <netinet/in.h>
>X#include <arpa/inet.h>
>X#include <netdb.h>
>X#include <stdio.h>
>X
>Xmain(argc, argv)
>Xint     argc;
>Xchar  **argv;
>X{
>X    struct hostent *hp;
>X    long    addr;
>X
>X    if (argc != 2) {
>X	fprintf(stderr, "usage: %s i.p.addres\n", argv[0]);
>X	exit(1);
>X    }
>X    addr = inet_addr(argv[1]);
>X    if (hp = gethostbyaddr((char *) &addr, sizeof(addr), AF_INET)) {
>X	printf("Hostname:\t%s\n", hp->h_name);
>X	printf("Aliases:\t");
>X	while (hp->h_aliases[0])
>X	    printf("%s ", *hp->h_aliases++);
>X	printf("\n");
>X	printf("Addresses:\t");
>X	while (hp->h_addr_list[0])
>X	    printf("%s ", inet_ntoa(*(struct in_addr *) * hp->h_addr_list++));
>X	printf("\n");
>X	exit(0);
>X    }
>X    fprintf(stderr, "host %s not found\n", argv[1]);
>X    exit(1);
>X}
>END_OF_gethostbyaddr.c
>if test 1073 -ne `wc -c <gethostbyaddr.c`; then
>    echo shar: \"gethostbyaddr.c\" unpacked with wrong size!
>fi
># end of overwriting check
>fi
>if test -f gethostbyname.c -a "${1}" != "-c" ; then 
>  echo shar: Will not over-write existing file \"gethostbyname.c\"
>else
>echo shar: Extracting \"gethostbyname.c\" $999 characters$
>sed "s/^X//" >gethostbyname.c <<'END_OF_gethostbyname.c'
>X /*
>X  * gethostbyname tester. compile with:
>X  * 
>X  * cc -o gethostbyname gethostbyname.c (SunOS 4.x)
>X  * 
>X  * cc -o gethostbyname gethostbyname.c -lnsl (SunOS 5.x)
>X  * 
>X  * run as: gethostbyname hostname
>X  * 
>X  * Author: Wietse Venema, Eindhoven University of Technology, The Netherlands.
>X  */
>X#include <sys/types.h>
>X#include <sys/socket.h>
>X#include <netinet/in.h>
>X#include <arpa/inet.h>
>X#include <netdb.h>
>X#include <stdio.h>
>X
>Xmain(argc, argv)
>Xint     argc;
>Xchar  **argv;
>X{
>X    struct hostent *hp;
>X
>X    if (argc != 2) {
>X	fprintf(stderr, "usage: %s hostname\n", argv[0]);
>X	exit(1);
>X    }
>X    if (hp = gethostbyname(argv[1])) {
>X	printf("Hostname:\t%s\n", hp->h_name);
>X	printf("Aliases:\t");
>X	while (hp->h_aliases[0])
>X	    printf("%s ", *hp->h_aliases++);
>X	printf("\n");
>X	printf("Addresses:\t");
>X	while (hp->h_addr_list[0])
>X	    printf("%s ", inet_ntoa(*(struct in_addr *) * hp->h_addr_list++));
>X	printf("\n");
>X	exit(0);
>X    } else {
>X	fprintf(stderr, "host %s not found\n", argv[1]);
>X	exit(1);
>X    }
>X}
>END_OF_gethostbyname.c
>if test 999 -ne `wc -c <gethostbyname.c`; then
>    echo shar: \"gethostbyname.c\" unpacked with wrong size!
>fi
># end of overwriting check
>fi
>echo shar: End of shell archive.
>exit 0
>Á.`../Éfontutil.m4004eÁÐpkg.m4/ÉÀfontutil.m4;4803004eÁ.
>`..3Élibnfsidmap.pc03004e.Éfontutil.pcÉ gtk-engines-2.pc4803004e4Élibrpcsecgss.pcËÎnotify-python.pc4e80±Î@	netapi.pcà,#gnome-python-extras-2.0.pc;4803004e$gnome-python-extras-2.0.pc# pkg.m4 - Macros to locate and utilise pkg-config.            -*- Autoconf -*-
># 
># Copyright Â© 2004 Scott James Remnant <scott@netsplit.com>.
>#
># This program is free software; you can redistribute it and/or modify
># it under the terms of the GNU General Public License as published by
># the Free Software Foundation; either version 2 of the License, or
># (at your option) any later version.
>#
># This program is distributed in the hope that it will be useful, but
># WITHOUT ANY WARRANTY; without even the implied warranty of
># MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
># General Public License for more details.
>#
># You should have received a copy of the GNU General Public License
># along with this program; if not, write to the Free Software
># Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
>#
># As a special exception to the GNU General Public License, if you
># distribute this file as part of a program that contains a
># configuration script generated by Autoconf, you may include it under
># the same distribution terms that you use for the rest of that program.
>
># PKG_PROG_PKG_CONFIG([MIN-VERSION])
># ----------------------------------
>AC_DEFUN([PKG_PROG_PKG_CONFIG],
>[m4_pattern_forbid([^_?PKG_[A-Z_]+$])
>m4_pattern_allow([^PKG_CONFIG(_PATH)?$])
>AC_ARG_VAR([PKG_CONFIG], [path to pkg-config utility])dnl
>if test "x$ac_cv_env_PKG_CONFIG_set" != "xset"; then
>	AC_PATH_TOOL([PKG_CONFIG], [pkg-config])
>fi
>if test -n "$PKG_CONFIG"; then
>	_pkg_min_version=m4_default([$1], [0.9.0])
>	AC_MSG_CHECKING([pkg-config is at least version $_pkg_min_version])
>	if $PKG_CONFIG --atleast-pkgconfig-version $_pkg_min_version; then
>		AC_MSG_RESULT([yes])
>	else
>		AC_MSG_RESULT([no])
>		PKG_CONFIG=""
>	fi
>		
>fi[]dnl
>])# PKG_PROG_PKG_CONFIG
>
># PKG_CHECK_EXISTS(MODULES, [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND])
>#
># Check to see whether a particular set of modules exists.  Similar
># to PKG_CHECK_MODULES(), but does not set variables or print errors.
>#
>#
># Similar to PKG_CHECK_MODULES, make sure that the first instance of
># this or PKG_CHECK_MODULES is called, or make sure to call
># PKG_CHECK_EXISTS manually
># --------------------------------------------------------------
>AC_DEFUN([PKG_CHECK_EXISTS],
>[AC_REQUIRE([PKG_PROG_PKG_CONFIG])dnl
>if test -n "$PKG_CONFIG" && \
>    AC_RUN_LOG([$PKG_CONFIG --exists --print-errors "$1"]); then
>  m4_ifval([$2], [$2], [:])
>m4_ifvaln([$3], [else
>  $3])dnl
>fi])
>
>
># _PKG_CONFIG([VARIABLE], [COMMAND], [MODULES])
># ---------------------------------------------
>m4_define([_PKG_CONFIG],
>[if test -n "$$1"; then
>    pkg_cv_[]$1="$$1"
> elif test -n "$PKG_CONFIG"; then
>    PKG_CHECK_EXISTS([$3],
>                     [pkg_cv_[]$1=`$PKG_CONFIG --[]$2 "$3" 2>/dev/null`],
>		     [pkg_failed=yes])
> else
>    pkg_failed=untried
>fi[]dnl
>])# _PKG_CONFIG
>
># _PKG_SHORT_ERRORS_SUPPORTED
># -----------------------------
>AC_DEFUN([_PKG_SHORT_ERRORS_SUPPORTED],
>[AC_REQUIRE([PKG_PROG_PKG_CONFIG])
>if $PKG_CONFIG --atleast-pkgconfig-version 0.20; then
>        _pkg_short_errors_supported=yes
>else
>        _pkg_short_errors_supported=no
>fi[]dnl
>])# _PKG_SHORT_ERRORS_SUPPORTED
>
>
># PKG_CHECK_MODULES(VARIABLE-PREFIX, MODULES, [ACTION-IF-FOUND],
># [ACTION-IF-NOT-FOUND])
>#
>#
># Note that if there is a possibility the first call to
># PKG_CHECK_MODULES might not happen, you should be sure to include an
># explicit call to PKG_PROG_PKG_CONFIG in your configure.ac
>#
>#
># --------------------------------------------------------------
>AC_DEFUN([PKG_CHECK_MODULES],
>[AC_REQUIRE([PKG_PROG_PKG_CONFIG])dnl
>AC_ARG_VAR([$1][_CFLAGS], [C compiler flags for $1, overriding pkg-config])dnl
>AC_ARG_VAR([$1][_LIBS], [linker flags for $1, overriding pkg-config])dnl
>
>pkg_failed=no
>AC_MSG_CHECKING([for $1])
>
>_PKG_CONFIG([$1][_CFLAGS], [cflags], [$2])
>_PKG_CONFIG([$1][_LIBS], [libs], [$2])
>
>m4_define([_PKG_TEXT], [Alternatively, you may set the environment variables $1[]_CFLAGS
>and $1[]_LIBS to avoid the need to call pkg-config.
>See the pkg-config man page for more details.])
>
>if test $pkg_failed = yes; then
>        _PKG_SHORT_ERRORS_SUPPORTED
>        if test $_pkg_short_errors_supported = yes; then
>	        $1[]_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors "$2" 2>&1`
>        else 
>	        $1[]_PKG_ERRORS=`$PKG_CONFIG --print-errors "$2" 2>&1`
>        fi
>	# Put the nasty error message in config.log where it belongs
>	echo "$$1[]_PKG_ERRORS" >&AS_MESSAGE_LOG_FD
>
>	ifelse([$4], , [AC_MSG_ERROR(dnl
>[Package requirements ($2) were not met:
>
>$$1_PKG_ERRORS
>
>Consider adjusting the PKG_CONFIG_PATH environment variable if you
>installed software in a non-standard prefix.
>
>_PKG_TEXT
>])],
>		[AC_MSG_RESULT([no])
>                $4])
>elif test $pkg_failed = untried; then
>	ifelse([$4], , [AC_MSG_FAILURE(dnl
>[The pkg-config script could not be found or is too old.  Make sure it
>is in your PATH or set the PKG_CONFIG environment variable to the full
>path to pkg-config.
>
>_PKG_TEXT
>
>To get pkg-config, see <http://pkg-config.freedesktop.org/>.])],
>		[$4])
>else
>	$1[]_CFLAGS=$pkg_cv_[]$1[]_CFLAGS
>	$1[]_LIBS=$pkg_cv_[]$1[]_LIBS
>        AC_MSG_RESULT([yes])
>	ifelse([$3], , :, [$3])
>fi[]dnl
>])# PKG_CHECK_MODULES
>Á.`$..ÁREADME;4803004eeÁAUTHORSÁCOPYINGÁNEWSÁ¤READMEOriginal authors
>----------------
>James Henstridge  <james@daa.com.au>     original pkg-config
>Tim Janik  <timj@gtk.org>                the PKG_CHECK_VERSION macro
>Havoc Pennington <hp@redhat.com>         rewrite in C
>Scott James Remnant <scott@netsplit.com> m4 cleanups and maintainer
>					 for a while
>
>Maintainer
>----------
>Tollef Fog Heen <tfheen@err.no>
>		    GNU GENERAL PUBLIC LICENSE
>		       Version 2, June 1991
>
> Copyright (C) 1989, 1991 Free Software Foundation, Inc.
>     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
> Everyone is permitted to copy and distribute verbatim copies
> of this license document, but changing it is not allowed.
>
>			    Preamble
>
>  The licenses for most software are designed to take away your
>freedom to share and change it.  By contrast, the GNU General Public
>License is intended to guarantee your freedom to share and change free
>software--to make sure the software is free for all its users.  This
>General Public License applies to most of the Free Software
>Foundation's software and to any other program whose authors commit to
>using it.  (Some other Free Software Foundation software is covered by
>the GNU Library General Public License instead.)  You can apply it to
>your programs, too.
>
>  When we speak of free software, we are referring to freedom, not
>price.  Our General Public Licenses are designed to make sure that you
>have the freedom to distribute copies of free software (and charge for
>this service if you wish), that you receive source code or can get it
>if you want it, that you can change the software or use pieces of it
>in new free programs; and that you know you can do these things.
>
>  To protect your rights, we need to make restrictions that forbid
>anyone to deny you these rights or to ask you to surrender the rights.
>These restrictions translate to certain responsibilities for you if you
>distribute copies of the software, or if you modify it.
>
>  For example, if you distribute copies of such a program, whether
>gratis or for a fee, you must give the recipients all the rights that
>you have.  You must make sure that they, too, receive or can get the
>source code.  And you must show them these terms so they know their
>rights.
>
>  We protect your rights with two steps: (1) copyright the software, and
>(2) offer you this license which gives you legal permission to copy,
>distribute and/or modify the software.
>
>  Also, for each author's protection and ours, we want to make certain
>that everyone understands that there is no warranty for this free
>software.  If the software is modified by someone else and passed on, we
>want its recipients to know that what they have is not the original, so
>that any problems introduced by others will not reflect on the original
>authors' reputations.
>
>  Finally, any free program is threatened constantly by software
>patents.  We wish to avoid the danger that redistributors of a free
>program will individually obtain patent licenses, in effect making the
>program proprietary.  To prevent this, we have made it clear that any
>patent must be licensed for everyone's free use or not licensed at all.
>
>  The precise terms and conditions for copying, distribution and
>modification follow.
>
>		    GNU GENERAL PUBLIC LICENSE
>   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
>
>  0. This License applies to any program or other work which contains
>a notice placed by the copyright holder saying it may be distributed
>under the terms of this General Public License.  The "Program", below,
>refers to any such program or work, and a "work based on the Program"
>means either the Program or any derivative work under copyright law:
>that is to say, a work containing the Program or a portion of it,
>either verbatim or with modifications and/or translated into another
>language.  (Hereinafter, translation is included without limitation in
>the term "modification".)  Each licensee is addressed as "you".
>
>Activities other than copying, distribution and modification are not
>covered by this License; they are outside its scope.  The act of
>running the Program is not restricted, and the output from the Program
>is covered only if its contents constitute a work based on the
>Program (independent of having been made by running the Program).
>Whether that is true depends on what the Program does.
>
>  1. You may copy and distribute verbatim copies of the Program's
>source code as you receive it, in any medium, provided that you
>conspicuously and appropriately publish on each copy an appropriate
>copyright notice and disclaimer of warranty; keep intact all the
>notices that refer to this License and to the absence of any warranty;
>and give any other recipients of the Program a copy of this License
>along with the Program.
>
>You may charge a fee for the physical act of transferring a copy, and
>you may at your option offer warranty protection in exchange for a fee.
>
>  2. You may modify your copy or copies of the Program or any portion
>of it, thus forming a work based on the Program, and copy and
>distribute such modifications or work under the terms of Section 1
>above, provided that you also meet all of these conditions:
>
>    a) You must cause the modified files to carry prominent notices
>    stating that you changed the files and the date of any change.
>
>    b) You must cause any work that you distribute or publish, that in
>    whole or in part contains or is derived from the Program or any
>    part thereof, to be licensed as a whole at no charge to all third
>    parties under the terms of this License.
>
>    c) If the modified program normally reads commands interactively
>    when run, you must cause it, when started running for such
>    interactive use in the most ordinary way, to print or display an
>    announcement including an appropriate copyright notice and a
>    notice that there is no warranty (or else, saying that you provide
>    a warranty) and that users may redistribute the program under
>    these conditions, and telling the user how to view a copy of this
>    License.  (Exception: if the Program itself is interactive but
>    does not normally print such an announcement, your work based on
>    the Program is not required to print an announcement.)
>
>These requirements apply to the modified work as a whole.  If
>identifiable sections of that work are not derived from the Program,
>and can be reasonably considered independent and separate works in
>themselves, then this License, and its terms, do not apply to those
>sections when you distribute them as separate works.  But when you
>distribute the same sections as part of a whole which is a work based
>on the Program, the distribution of the whole must be on the terms of
>this License, whose permissions for other licensees extend to the
>entire whole, and thus to each and every part regardless of who wrote it.
>
>Thus, it is not the intent of this section to claim rights or contest
>your rights to work written entirely by you; rather, the intent is to
>exercise the right to control the distribution of derivative or
>collective works based on the Program.
>
>In addition, mere aggregation of another work not based on the Program
>with the Program (or with a work based on the Program) on a volume of
>a storage or distribution medium does not bring the other work under
>the scope of this License.
>
>  3. You may copy and distribute the Program (or a work based on it,
>under Section 2) in object code or executable form under the terms of
>Sections 1 and 2 above provided that you also do one of the following:
>
>    a) Accompany it with the complete corresponding machine-readable
>    source code, which must be distributed under the terms of Sections
>    1 and 2 above on a medium customarily used for software interchange; or,
>
>    b) Accompany it with a written offer, valid for at least three
>    years, to give any third party, for a charge no more than your
>    cost of physically performing source distribution, a complete
>    machine-readable copy of the corresponding source code, to be
>    distributed under the terms of Sections 1 and 2 above on a medium
>    customarily used for software interchange; or,
>
>    c) Accompany it with the information you received as to the offer
>    to distribute corresponding source code.  (This alternative is
>    allowed only for noncommercial distribution and only if you
>    received the program in object code or executable form with such
>    an offer, in accord with Subsection b above.)
>
>The source code for a work means the preferred form of the work for
>making modifications to it.  For an executable work, complete source
>code means all the source code for all modules it contains, plus any
>associated interface definition files, plus the scripts used to
>control compilation and installation of the executable.  However, as a
>special exception, the source code distributed need not include
>anything that is normally distributed (in either source or binary
>form) with the major components (compiler, kernel, and so on) of the
>operating system on which the executable runs, unless that component
>itself accompanies the executable.
>
>If distribution of executable or object code is made by offering
>access to copy from a designated place, then offering equivalent
>access to copy the source code from the same place counts as
>distribution of the source code, even though third parties are not
>compelled to copy the source along with the object code.
>
>  4. You may not copy, modify, sublicense, or distribute the Program
>except as expressly provided under this License.  Any attempt
>otherwise to copy, modify, sublicense or distribute the Program is
>void, and will automatically terminate your rights under this License.
>However, parties who have received copies, or rights, from you under
>this License will not have their licenses terminated so long as such
>parties remain in full compliance.
>
>  5. You are not required to accept this License, since you have not
>signed it.  However, nothing else grants you permission to modify or
>distribute the Program or its derivative works.  These actions are
>prohibited by law if you do not accept this License.  Therefore, by
>modifying or distributing the Program (or any work based on the
>Program), you indicate your acceptance of this License to do so, and
>all its terms and conditions for copying, distributing or modifying
>the Program or works based on it.
>
>  6. Each time you redistribute the Program (or any work based on the
>Program), the recipient automatically receives a license from the
>original licensor to copy, distribute or modify the Program subject to
>these terms and conditions.  You may not impose any further
>restrictions on the recipients' exercise of the rights granted herein.
>You are not responsible for enforcing compliance by third parties to
>this License.
>
>  7. If, as a consequence of a court judgment or allegation of patent
>infringement or for any other reason (not limited to patent issues),
>conditions are imposed on you (whether by court order, agreement or
>otherwise) that contradict the conditions of this License, they do not
>excuse you from the conditions of this License.  If you cannot
>distribute so as to satisfy simultaneously your obligations under this
>License and any other pertinent obligations, then as a consequence you
>may not distribute the Program at all.  For example, if a patent
>license would not permit royalty-free redistribution of the Program by
>all those who receive copies directly or indirectly through you, then
>the only way you could satisfy both it and this License would be to
>refrain entirely from distribution of the Program.
>
>If any portion of this section is held invalid or unenforceable under
>any particular circumstance, the balance of the section is intended to
>apply and the section as a whole is intended to apply in other
>circumstances.
>
>It is not the purpose of this section to induce you to infringe any
>patents or other property right claims or to contest validity of any
>such claims; this section has the sole purpose of protecting the
>integrity of the free software distribution system, which is
>implemented by public license practices.  Many people have made
>generous contributions to the wide range of software distributed
>through that system in reliance on consistent application of that
>system; it is up to the author/donor to decide if he or she is willing
>to distribute software through any other system and a licensee cannot
>impose that choice.
>
>This section is intended to make thoroughly clear what is believed to
>be a consequence of the rest of this License.
>
>  8. If the distribution and/or use of the Program is restricted in
>certain countries either by patents or by copyrighted interfaces, the
>original copyright holder who places the Program under this License
>may add an explicit geographical distribution limitation excluding
>those countries, so that distribution is permitted only in or among
>countries not thus excluded.  In such case, this License incorporates
>the limitation as if written in the body of this License.
>
>  9. The Free Software Foundation may publish revised and/or new versions
>of the General Public License from time to time.  Such new versions will
>be similar in spirit to the present version, but may differ in detail to
>address new problems or concerns.
>
>Each version is given a distinguishing version number.  If the Program
>specifies a version number of this License which applies to it and "any
>later version", you have the option of following the terms and conditions
>either of that version or of any later version published by the Free
>Software Foundation.  If the Program does not specify a version number of
>this License, you may choose any version ever published by the Free Software
>Foundation.
>
>  10. If you wish to incorporate parts of the Program into other free
>programs whose distribution conditions are different, write to the author
>to ask for permission.  For software which is copyrighted by the Free
>Software Foundation, write to the Free Software Foundation; we sometimes
>make exceptions for this.  Our decision will be guided by the two goals
>of preserving the free status of all derivatives of our free software and
>of promoting the sharing and reuse of software generally.
>
>			    NO WARRANTY
>
>  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
>FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
>OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
>PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
>OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
>MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
>TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
>PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
>REPAIR OR CORRECTION.
>
>  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
>WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
>REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
>INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
>OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
>TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
>YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
>PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
>POSSIBILITY OF SUCH DAMAGES.
>
>		     END OF TERMS AND CONDITIONS
>
>	    How to Apply These Terms to Your New Programs
>
>  If you develop a new program, and you want it to be of the greatest
>possible use to the public, the best way to achieve this is to make it
>free software which everyone can redistribute and change under these terms.
>
>  To do so, attach the following notices to the program.  It is safest
>to attach them to the start of each source file to most effectively
>convey the exclusion of warranty; and each file should have at least
>the "copyright" line and a pointer to where the full notice is found.
>
>    <one line to give the program's name and a brief idea of what it does.>
>    Copyright (C) <year>  <name of author>
>
>    This program is free software; you can redistribute it and/or modify
>    it under the terms of the GNU General Public License as published by
>    the Free Software Foundation; either version 2 of the License, or
>    (at your option) any later version.
>
>    This program is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>    GNU General Public License for more details.
>
>    You should have received a copy of the GNU General Public License
>    along with this program; if not, write to the Free Software
>    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
>
>
>Also add information on how to contact you by electronic and paper mail.
>
>If the program is interactive, make it output a short notice like this
>when it starts in an interactive mode:
>
>    Gnomovision version 69, Copyright (C) year  name of author
>    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
>    This is free software, and you are welcome to redistribute it
>    under certain conditions; type `show c' for details.
>
>The hypothetical commands `show w' and `show c' should show the appropriate
>parts of the General Public License.  Of course, the commands you use may
>be called something other than `show w' and `show c'; they could even be
>mouse-clicks or menu items--whatever suits your program.
>
>You should also get your employer (if you work as a programmer) or your
>school, if any, to sign a "copyright disclaimer" for the program, if
>necessary.  Here is a sample; alter the names:
>
>  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
>  `Gnomovision' (which makes passes at compilers) written by James Hacker.
>
>  <signature of Ty Coon>, 1 April 1989
>  Ty Coon, President of Vice
>
>This General Public License does not permit incorporating your program into
>proprietary programs.  If your program is a subroutine library, you may
>consider it more useful to permit linking proprietary applications with the
>library.  If this is what you want to do, use the GNU Library General
>Public License instead of this License.
>pkg-config 0.23
>===
> - Add support for setting sysroot through PKG_CONFIG_SYSROOT_DIR in
>   the environment.
> - Update included glib to 1.2.10.
> - Other minor fixes, including a segfault.
>
>pkg-config 0.22
>===
> - Make Requires.private a whole lot more useful by traversing the
>   whole tree, not just the top-level, for Cflags.
> - Add support for using the system glib.
> - Update URL to pkg-config website
> - Fix some win32 problems.
> - Other minor fixes.
>
>pkg-config 0.21
>===
> - Fix some cosmetic output from pkg.m4
> - Fix build problems with !gcc due to always passing -Wall
> - Documentation fixes
> - We now always add the Cflags from packages we depend on, whether
>   they are public or private dependencies.  The discussion surrouding
>   this change can be found in http://bugs.debian.org/340904 .
> - Add internal pkg-config package which can be queried for version
>   number and other information.
>
>pkg-config 0.20
>===
> - Fix test suite to work on Solaris.  Yay non-POSIX /bin/sh :-(
> - Fix segfault on --help with gcc4.  Fix segfault on bigendian arches
>   in some cases.
> - Win32 fixes
> - Add --short-errors, now used by pkg.m4 if available.  This gives a
>   better error message if some libraries can't be found.
>
>pkg-config 0.19
>===
> - Fix a segfault
> - Fix default search path
> - Fix cosmetic bug in pkg.m4 where AC_MSG_RESULT wasn't called in
>   some cases.
>
>pkg-config 0.18.1
>===
> - Fix up pkg.m4 to not end up with pkg_failed=untried always.
>
>pkg-config 0.18
>===
> - The inter-library dependencies check was too tight and caused
> problems if one used the --no-undefined flag to libtool on Solaris
> (since it there expands to -Wl,-z,defs which disallows undefined
> symbols).  Add a new name to .pc files: Libs.private which will not
> be listed in the output of --libs unless --static is also given.
>
> Private libraries are libraries which are needed in the case of
> static linking or on platforms not supporting inter-library
> dependencies.  They are not supposed to be used for libraries which
> are exposed through the library in question.  An example of an
> exposed library is GTK+ exposing Glib.  A common example of a private
> library is libm.
>
> Generally, if include another library's headers in your own, it's a
> public dependency and not a private one.
>
> Thanks a lot to James Henstridge for both the bug and the following
> discussion.
>
>pkg-config 0.17.2
>===
> - Don't go into an infinite loop allocating more and more memory when
>   the same name is specified twice on the command line and we're in
>   "direct dependencies only"-mode.
>
>pkg-config 0.17.1
>===
> - Now actually sets CFLAGS and LIBS instead of trying to set those in
>   a subshell.  (Only affects if you've autoreconfiscated with 0.17)
> - Fix detection of inter-library dependencies.
>
>pkg-config 0.17
>===
>
> - Evaluate second argument to PKG_CHECK_MODULES again
> - Portability fixes (MacOS, BeOS, Cygwin)
> - Handle inter-library dependencies and assume those are in place if
>   the platform supports them.  Disable with --enable-indirect-deps.
> - Add initial test framework
> - Build fixes (make distcheck now works)
>
>pkg-config 0.16
>===
>
> - Use a search path, rather than a single default directory.
> - Fix a bunch of bugs in glib by backporting
> - More man page fixes
> - Lots of small fixes and cleanups over the place.
> - pkg-config now grabs _PKG_* and PKG_*, so don't use variables
>   starting with that in any configure scripts.
>
>pkg-config 0.15
>===
>
> - add PKG_CONFIG_LIBDIR for cross-compiling (David Schleef)
> - add --libs-only-other/--cflags-only-other (Zack Rusin)
> - apply man page fixes (Pter Breitenlohner)
> - C portability fix (David Robins)
> - fix to win32 build (Tor Lillqvist)
>pkg-config is a script to make putting together all the build
>flags when compiling/linking a lot easier.
>
>Report bugs at http://bugzilla.freedesktop.org/
>
>
>To use pkg-config, do something like the following in your configure.ac
>
>    PKG_CHECK_MODULES([GNOME], [gtk > 1.2.8 gnomeui >= 1.2.0])
>
>This puts the neccesary include flags to compile/link something against
>libgnomeui and all its dependencies in $(GNOME_CFLAGS), and the -L/-l flags
>for linking in $(GNOME_LIBS).
>
>Users can define the PKG_CONFIG environment variable to point at the
>right one, or if they cross-compile and have a correctly named pkg-config
>(eg. arm-linux-pkg-config) in their PATH that will be used in preference.
>
>Users can also define the GNOME_CFLAGS and GNOME_LIBS environment variables
>if they think they know better, pkg-config will not be called if they do
>that.
>
>The "gtk > 1.2.8" part is only neccesary if you want to specifically check
>if libgtk is version 1.2.8 or higher. Otherwise, the flags for gtk
>will be included automatically, since libgnomeui depends on gtk.
>So you could just say:
>
>     PKG_CHECK_MODULES([GNOME], [gnomeui])
>
>for any version of gnomeui.
>
>For more info, there's even a man page, try 'man pkg-config'
>
>
>Á.`4..É(gnome-icon-theme.pc;4803004e04e-É gnome-mime-data-2.0.pc2Éshared-mime-info.pcÉgnome-icon-theme.pc Á.`..£Á	ChangeLog803004e¡ÁAUTHORS¢Á(COPYING¦ÁREADME;4803004ee¤ÁINSTALL¥ÁNEWS¦Á|READMEMaxim Krasnyansky <maxk@qualcomm.com>
>Marcel Holtmann <marcel@holtmann.org>
>Stephen Crane <steve.crane@rococosoft.com>
>		    GNU GENERAL PUBLIC LICENSE
>		       Version 2, June 1991
>
> Copyright (C) 1989, 1991 Free Software Foundation, Inc.
>                       51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
> Everyone is permitted to copy and distribute verbatim copies
> of this license document, but changing it is not allowed.
>
>			    Preamble
>
>  The licenses for most software are designed to take away your
>freedom to share and change it.  By contrast, the GNU General Public
>License is intended to guarantee your freedom to share and change free
>software--to make sure the software is free for all its users.  This
>General Public License applies to most of the Free Software
>Foundation's software and to any other program whose authors commit to
>using it.  (Some other Free Software Foundation software is covered by
>the GNU Library General Public License instead.)  You can apply it to
>your programs, too.
>
>  When we speak of free software, we are referring to freedom, not
>price.  Our General Public Licenses are designed to make sure that you
>have the freedom to distribute copies of free software (and charge for
>this service if you wish), that you receive source code or can get it
>if you want it, that you can change the software or use pieces of it
>in new free programs; and that you know you can do these things.
>
>  To protect your rights, we need to make restrictions that forbid
>anyone to deny you these rights or to ask you to surrender the rights.
>These restrictions translate to certain responsibilities for you if you
>distribute copies of the software, or if you modify it.
>
>  For example, if you distribute copies of such a program, whether
>gratis or for a fee, you must give the recipients all the rights that
>you have.  You must make sure that they, too, receive or can get the
>source code.  And you must show them these terms so they know their
>rights.
>
>  We protect your rights with two steps: (1) copyright the software, and
>(2) offer you this license which gives you legal permission to copy,
>distribute and/or modify the software.
>
>  Also, for each author's protection and ours, we want to make certain
>that everyone understands that there is no warranty for this free
>software.  If the software is modified by someone else and passed on, we
>want its recipients to know that what they have is not the original, so
>that any problems introduced by others will not reflect on the original
>authors' reputations.
>
>  Finally, any free program is threatened constantly by software
>patents.  We wish to avoid the danger that redistributors of a free
>program will individually obtain patent licenses, in effect making the
>program proprietary.  To prevent this, we have made it clear that any
>patent must be licensed for everyone's free use or not licensed at all.
>
>  The precise terms and conditions for copying, distribution and
>modification follow.
>
>		    GNU GENERAL PUBLIC LICENSE
>   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
>
>  0. This License applies to any program or other work which contains
>a notice placed by the copyright holder saying it may be distributed
>under the terms of this General Public License.  The "Program", below,
>refers to any such program or work, and a "work based on the Program"
>means either the Program or any derivative work under copyright law:
>that is to say, a work containing the Program or a portion of it,
>either verbatim or with modifications and/or translated into another
>language.  (Hereinafter, translation is included without limitation in
>the term "modification".)  Each licensee is addressed as "you".
>
>Activities other than copying, distribution and modification are not
>covered by this License; they are outside its scope.  The act of
>running the Program is not restricted, and the output from the Program
>is covered only if its contents constitute a work based on the
>Program (independent of having been made by running the Program).
>Whether that is true depends on what the Program does.
>
>  1. You may copy and distribute verbatim copies of the Program's
>source code as you receive it, in any medium, provided that you
>conspicuously and appropriately publish on each copy an appropriate
>copyright notice and disclaimer of warranty; keep intact all the
>notices that refer to this License and to the absence of any warranty;
>and give any other recipients of the Program a copy of this License
>along with the Program.
>
>You may charge a fee for the physical act of transferring a copy, and
>you may at your option offer warranty protection in exchange for a fee.
>
>  2. You may modify your copy or copies of the Program or any portion
>of it, thus forming a work based on the Program, and copy and
>distribute such modifications or work under the terms of Section 1
>above, provided that you also meet all of these conditions:
>
>    a) You must cause the modified files to carry prominent notices
>    stating that you changed the files and the date of any change.
>
>    b) You must cause any work that you distribute or publish, that in
>    whole or in part contains or is derived from the Program or any
>    part thereof, to be licensed as a whole at no charge to all third
>    parties under the terms of this License.
>
>    c) If the modified program normally reads commands interactively
>    when run, you must cause it, when started running for such
>    interactive use in the most ordinary way, to print or display an
>    announcement including an appropriate copyright notice and a
>    notice that there is no warranty (or else, saying that you provide
>    a warranty) and that users may redistribute the program under
>    these conditions, and telling the user how to view a copy of this
>    License.  (Exception: if the Program itself is interactive but
>    does not normally print such an announcement, your work based on
>    the Program is not required to print an announcement.)
>
>These requirements apply to the modified work as a whole.  If
>identifiable sections of that work are not derived from the Program,
>and can be reasonably considered independent and separate works in
>themselves, then this License, and its terms, do not apply to those
>sections when you distribute them as separate works.  But when you
>distribute the same sections as part of a whole which is a work based
>on the Program, the distribution of the whole must be on the terms of
>this License, whose permissions for other licensees extend to the
>entire whole, and thus to each and every part regardless of who wrote it.
>
>Thus, it is not the intent of this section to claim rights or contest
>your rights to work written entirely by you; rather, the intent is to
>exercise the right to control the distribution of derivative or
>collective works based on the Program.
>
>In addition, mere aggregation of another work not based on the Program
>with the Program (or with a work based on the Program) on a volume of
>a storage or distribution medium does not bring the other work under
>the scope of this License.
>
>  3. You may copy and distribute the Program (or a work based on it,
>under Section 2) in object code or executable form under the terms of
>Sections 1 and 2 above provided that you also do one of the following:
>
>    a) Accompany it with the complete corresponding machine-readable
>    source code, which must be distributed under the terms of Sections
>    1 and 2 above on a medium customarily used for software interchange; or,
>
>    b) Accompany it with a written offer, valid for at least three
>    years, to give any third party, for a charge no more than your
>    cost of physically performing source distribution, a complete
>    machine-readable copy of the corresponding source code, to be
>    distributed under the terms of Sections 1 and 2 above on a medium
>    customarily used for software interchange; or,
>
>    c) Accompany it with the information you received as to the offer
>    to distribute corresponding source code.  (This alternative is
>    allowed only for noncommercial distribution and only if you
>    received the program in object code or executable form with such
>    an offer, in accord with Subsection b above.)
>
>The source code for a work means the preferred form of the work for
>making modifications to it.  For an executable work, complete source
>code means all the source code for all modules it contains, plus any
>associated interface definition files, plus the scripts used to
>control compilation and installation of the executable.  However, as a
>special exception, the source code distributed need not include
>anything that is normally distributed (in either source or binary
>form) with the major components (compiler, kernel, and so on) of the
>operating system on which the executable runs, unless that component
>itself accompanies the executable.
>
>If distribution of executable or object code is made by offering
>access to copy from a designated place, then offering equivalent
>access to copy the source code from the same place counts as
>distribution of the source code, even though third parties are not
>compelled to copy the source along with the object code.
>
>  4. You may not copy, modify, sublicense, or distribute the Program
>except as expressly provided under this License.  Any attempt
>otherwise to copy, modify, sublicense or distribute the Program is
>void, and will automatically terminate your rights under this License.
>However, parties who have received copies, or rights, from you under
>this License will not have their licenses terminated so long as such
>parties remain in full compliance.
>
>  5. You are not required to accept this License, since you have not
>signed it.  However, nothing else grants you permission to modify or
>distribute the Program or its derivative works.  These actions are
>prohibited by law if you do not accept this License.  Therefore, by
>modifying or distributing the Program (or any work based on the
>Program), you indicate your acceptance of this License to do so, and
>all its terms and conditions for copying, distributing or modifying
>the Program or works based on it.
>
>  6. Each time you redistribute the Program (or any work based on the
>Program), the recipient automatically receives a license from the
>original licensor to copy, distribute or modify the Program subject to
>these terms and conditions.  You may not impose any further
>restrictions on the recipients' exercise of the rights granted herein.
>You are not responsible for enforcing compliance by third parties to
>this License.
>
>  7. If, as a consequence of a court judgment or allegation of patent
>infringement or for any other reason (not limited to patent issues),
>conditions are imposed on you (whether by court order, agreement or
>otherwise) that contradict the conditions of this License, they do not
>excuse you from the conditions of this License.  If you cannot
>distribute so as to satisfy simultaneously your obligations under this
>License and any other pertinent obligations, then as a consequence you
>may not distribute the Program at all.  For example, if a patent
>license would not permit royalty-free redistribution of the Program by
>all those who receive copies directly or indirectly through you, then
>the only way you could satisfy both it and this License would be to
>refrain entirely from distribution of the Program.
>
>If any portion of this section is held invalid or unenforceable under
>any particular circumstance, the balance of the section is intended to
>apply and the section as a whole is intended to apply in other
>circumstances.
>
>It is not the purpose of this section to induce you to infringe any
>patents or other property right claims or to contest validity of any
>such claims; this section has the sole purpose of protecting the
>integrity of the free software distribution system, which is
>implemented by public license practices.  Many people have made
>generous contributions to the wide range of software distributed
>through that system in reliance on consistent application of that
>system; it is up to the author/donor to decide if he or she is willing
>to distribute software through any other system and a licensee cannot
>impose that choice.
>
>This section is intended to make thoroughly clear what is believed to
>be a consequence of the rest of this License.
>
>  8. If the distribution and/or use of the Program is restricted in
>certain countries either by patents or by copyrighted interfaces, the
>original copyright holder who places the Program under this License
>may add an explicit geographical distribution limitation excluding
>those countries, so that distribution is permitted only in or among
>countries not thus excluded.  In such case, this License incorporates
>the limitation as if written in the body of this License.
>
>  9. The Free Software Foundation may publish revised and/or new versions
>of the General Public License from time to time.  Such new versions will
>be similar in spirit to the present version, but may differ in detail to
>address new problems or concerns.
>
>Each version is given a distinguishing version number.  If the Program
>specifies a version number of this License which applies to it and "any
>later version", you have the option of following the terms and conditions
>either of that version or of any later version published by the Free
>Software Foundation.  If the Program does not specify a version number of
>this License, you may choose any version ever published by the Free Software
>Foundation.
>
>  10. If you wish to incorporate parts of the Program into other free
>programs whose distribution conditions are different, write to the author
>to ask for permission.  For software which is copyrighted by the Free
>Software Foundation, write to the Free Software Foundation; we sometimes
>make exceptions for this.  Our decision will be guided by the two goals
>of preserving the free status of all derivatives of our free software and
>of promoting the sharing and reuse of software generally.
>
>			    NO WARRANTY
>
>  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
>FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
>OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
>PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
>OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
>MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
>TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
>PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
>REPAIR OR CORRECTION.
>
>  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
>WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
>REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
>INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
>OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
>TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
>YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
>PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
>POSSIBILITY OF SUCH DAMAGES.
>
>		     END OF TERMS AND CONDITIONS
>
>	    How to Apply These Terms to Your New Programs
>
>  If you develop a new program, and you want it to be of the greatest
>possible use to the public, the best way to achieve this is to make it
>free software which everyone can redistribute and change under these terms.
>
>  To do so, attach the following notices to the program.  It is safest
>to attach them to the start of each source file to most effectively
>convey the exclusion of warranty; and each file should have at least
>the "copyright" line and a pointer to where the full notice is found.
>
>    <one line to give the program's name and a brief idea of what it does.>
>    Copyright (C) <year>  <name of author>
>
>    This program is free software; you can redistribute it and/or modify
>    it under the terms of the GNU General Public License as published by
>    the Free Software Foundation; either version 2 of the License, or
>    (at your option) any later version.
>
>    This program is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>    GNU General Public License for more details.
>
>    You should have received a copy of the GNU General Public License
>    along with this program; if not, write to the Free Software
>    Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
>
>
>Also add information on how to contact you by electronic and paper mail.
>
>If the program is interactive, make it output a short notice like this
>when it starts in an interactive mode:
>
>    Gnomovision version 69, Copyright (C) year name of author
>    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
>    This is free software, and you are welcome to redistribute it
>    under certain conditions; type `show c' for details.
>
>The hypothetical commands `show w' and `show c' should show the appropriate
>parts of the General Public License.  Of course, the commands you use may
>be called something other than `show w' and `show c'; they could even be
>mouse-clicks or menu items--whatever suits your program.
>
>You should also get your employer (if you work as a programmer) or your
>school, if any, to sign a "copyright disclaimer" for the program, if
>necessary.  Here is a sample; alter the names:
>
>  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
>  `Gnomovision' (which makes passes at compilers) written by James Hacker.
>
>  <signature of Ty Coon>, 1 April 1989
>  Ty Coon, President of Vice
>
>This General Public License does not permit incorporating your program into
>proprietary programs.  If your program is a subroutine library, you may
>consider it more useful to permit linking proprietary applications with the
>library.  If this is what you want to do, use the GNU Library General
>Public License instead of this License.
>ver 3.30:
>	Add another company identifier.
>
>ver 3.29:
>	Fix memory leak in sdp_get_uuidseq_attr function.
>
>ver 3.28:
>	Add support for MCAP UUIDs.
>
>ver 3.27:
>	Add another company identifier.
>
>ver 3.26:
>	Fix compilation problem with USHRT_MAX and UCHAR_MAX.
>
>ver 3.25:
>	Update copyright information.
>
>ver 3.24:
>	Add definitions for MDP.
>
>ver 3.23:
>	Fix remote name request handling bug.
>
>ver 3.22:
>	Fix remote name request event handling.
>
>ver 3.21:
>	Add constant for Bluetooth socket options level.
>
>ver 3.20:
>	Add support for inquiry transmit power level.
>
>ver 3.19:
>	Add L2CAP mode constants.
>
>ver 3.18:
>	Don't allocate memory for the Bluetooth base UUID.
>
>ver 3.17:
>	Fix supported commands bit calculation.
>
>ver 3.16:
>	Update company identifier list.
>
>ver 3.15:
>	Extract main service class for later use.
>
>ver 3.14:
>	Add definitions and functions for Simple Pairing.
>
>ver 3.13:
>	Update HCI command table.
>
>ver 3.12:
>	Add missing HCI command text descriptions
>	Add missing HCI commands structures.
>	Add missing HCI event structures.
>	Add common bachk() function.
>
>ver 3.11:
>	Fix URL data size handling.
>
>ver 3.10:
>	Add version code for Bluetooth 2.1 specification.
>	Add ESCO_LINK connection type constant.
>	Export sdp_uuid32_to_uuid128() function.
>
>ver 3.9:
>	Update copyright information.
>
>ver 3.8:
>	Add functions for registering binary records.
>
>ver 3.7:
>	Add additional PDU length checks.
>	Fix CSRC value for partial responses.
>
>ver 3.6:
>	Fix issues with the asynchronous API for SDP.
>
>ver 3.5:
>	Add asynchronous API for SDP.
>
>ver 3.4:
>	Fix UUID128 string lookup handling.
>	Fix malloc() versus bt_malloc() usage.
>
>ver 3.3:
>	Remove kernel specific timeouts.
>	Add additional private data field for SDP sessions.
>	Add host controller to host flow control defines.
>	Add host number of completed packets defines.
>	Initialize various memory to zero before usage.
>
>ver 3.2:
>	Fix handling of SDP strings.
>	Add adapter type for SDIO cards.
>	Add features bit for link supervision timeout.
>
>ver 3.1:
>	Add missing placeholders for feature bits.
>
>ver 3.0:
>	Fix broken behavior with EVT_CMD_STATUS.
>	Add features bit for pause encryption.
>	Add additional EIR error code.
>	Add more company identifiers.
>	Add another Phonebook Access identifier.
>	Update sniff subrating data structures.
>
>ver 2.25:
>	Add definitions for Apple Agent.
>	Add support for record handle on service registration.
>
>ver 2.24:
>	Add support for additional access protocols.
>
>ver 2.23:
>	Add constants and definitions for sniff subrating.
>	Add support for allocation of binary text elements.
>	Fix service discovery deadlocks with Samsung D600 phones.
>
>ver 2.22:
>	Decode reserved LMP feature bits.
>	Fix errno overwrite problems.
>	Fix profile descriptor problem with Samsung phones.
>	Add compile time buffer checks (FORTIFY SOURCE).
>
>ver 2.21:
>	Add support for identification of supported commands.
>	Add missing OCF declarations for the security filter.
>	Add two new company identifiers.
>
>ver 2.20:
>	Add UUIDs for video distribution profile.
>	Add UUIDs for phonebook access profile.
>	Add attribute identifier for supported repositories.
>	Add definitions for extended inquiry response.
>	Add functions for extended inquiry response.
>
>ver 2.19:
>	Fix the GCC 4.0 warnings.
>	Fix the routing for dealing with raw devices.
>	Add per device service record functions.
>
>ver 2.18:
>	Add support for reading and writing the inquiry scan type.
>	Add definitions for connection accept timeout and scan enable.
>	Remove hci_vhci.h header file.
>	Remove hci_uart.h header file.
>
>ver 2.17:
>	Include stdio.h in bluetooth.h header file.
>	Include sys/socket.h in the header files.
>	Add functions for stored link keys.
>	Add definitions for PIN type and unit key.
>	Add SDP_WAIT_ON_CLOSE flag for sdp_connect().
>
>ver 2.16:
>	Fix buffer allocation for features to string conversion.
>	Add function for reading local supported commands.
>	Add function for reading local extended features.
>	Add function for reading remote extended features.
>	Add function for getting the remote name with a clock offset.
>	Add function for extracting the OUI from a BD_ADDR.
>	Add inquiry info structure with RSSI and page scan mode.
>	Support inquiry with unlimited number of responses.
>
>ver 2.15:
>	Use better way for unaligned access.
>	Remove sdp_internal.h and its usage.
>	Add deprecated functions for reading the name.
>	Add function for reading the clock.
>	Add function for reading the local Bluetooth address.
>	Add function for reading the local supported features.
>
>ver 2.14:
>	Add function for reading the RSSI.
>	Add function for reading the link quality.
>	Add function for reading the transmit power level.
>	Add functions for the link supervision timeout.
>	Remove deprecated functions.
>	Update AM_PATH_BLUEZ macro.
>
>ver 2.13:
>	Add Device ID and HID attribute definitions.
>	Update the UUID constants and its translations.
>	Update L2CAP socket option definitions.
>	Update connection information definitions.
>
>ver 2.12:
>	Correct kernel interface for CMTP and HIDP support.
>	Add service classes and profile ids for WAP.
>	Add simple AM_PATH_BLUEZ macro.
>
>ver 2.11:
>	Initial support for the kernel security manager.
>	Use bit zero for vendor packets in the filter type bitmask.
>	Add SIM Access types for service discovery.
>	Add more audio/video profile translations.
>	Add another company identifier.
>	Add the missing HCI error codes.
>	Add RFCOMM socket options.
>	Add definition for the SECURE link mode.
>	Add functions for reading and writing the inquiry mode.
>	Add functions for AFH related settings and information.
>	Add version identifier for the Bluetooth 2.0 specification.
>
>ver 2.10:
>	Fix and extend the unaligned access macros.
>	Make compiling with debug information optional.
>	Don't override CFLAGS from configure.
>
>ver 2.9:
>	Add L2CAP info type and info result definitions.
>	Add value for L2CAP_CONF_RFC_MODE.
>	Change RSSI value to signed instead of unsigned.
>	Allow UUID32 values as protocol identifiers.
>
>ver 2.8:
>	Fix the event code of inquiry with RSSI.
>	Add defines and UUID's for audio/video profiles.
>	Add AVDTP protocol identifier.
>	Add HIDP subclass field.
>	Add PKGConfig support.
>	Remove dummy SDP library.
>
>ver 2.7:
>	Fix display of decoded LMP features.
>	Update company identifiers.
>	Add AFH related types.
>	Add first bits from EDR prototyping specification.
>	Add support for inquiry with RSSI.
>	Add HCRP related SDP functions.
>	Add HIDP header file.
>
>ver 2.6:
>	Use R2 for default value of pscan_rep_mode.
>	Add new company identifiers.
>	Add BNEP and CMTP header files.
>	Add the SDP library.
>
>ver 2.5:
>	Add decoding of Bluetooth 1.2 features.
>	Add link manager version parameter for Bluetooth 1.2.
>	Add new company identifiers.
>	Support for transmit power level.
>	Support for park, sniff and hold mode.
>	Support for role switch.
>	Support for reading the clock offset.
>	Use R1 for default value of pscan_rep_mode.
>
>ver 2.4:
>	Added const qualifiers to appropriate function arguments.
>	Minor fixes.
>
>ver 2.3:
>	Fix hci_for_each_dev() for big endian machines.
>	Support for voice settings.
>	RPM package.
>
>ver 2.2:
>	Updated RFCOMM header file.
>	Additional HCI command and event defines.
>
>ver 2.1.1:
>	Resurrect hci_remote_name.
>
>ver 2.1:
>	New HCI functions:
>		hci_{read, write}_class_of_dev(),
>		hci_{read, write}_current_iac_lap(),
>		hci_write_local_name()
>	Added RFCOMM header file.
>	Minor fixes.
>
>ver 2.0:
>	Additional company IDs.
>	Minor fixes.
>
>ver 2.0-pre10:
>	Fix hci_inquiry function to return errors and accept user buffers.
>	New functions hci_devba, hci_devid, hci_for_each_dev and hci_get_route.
>	Additional company IDs.
>	Makefile and other minor fixes.
>
>ver 2.0-pre9:
>	LMP features to string translation support.
>	Additional HCI command and event defines.
>	Extended hci_filter API.
>
>ver 2.0-pre8:
>	Additional HCI ioctls and defines.
>	All strings and buffers are allocated dynamically.
>	ba2str, str2ba automatically swap bdaddress.
>	Minor fixes and cleanup.
>
>ver 2.0-pre7:
>	Bluetooth libraries and header files is now a separate package.
>	New build environment uses automake and libtool.
>	Massive header files cleanup.
>
>ver 2.0-pre6:
>	API cleanup and additions.
>
>ver 2.0-pre4:
>	HCI filter enhancements.
>
>ver 2.0-pre3:
>	Cleanup.
>
>ver 2.0-pre2:
>	Additional HCI library functions.
>	Documentation update.
>	
>ver 2.0-pre1:
>	Minor fixes and improvements.
>Installation Instructions
>*************************
>
>Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
>Software Foundation, Inc.
>
>This file is free documentation; the Free Software Foundation gives
>unlimited permission to copy, distribute and modify it.
>
>Basic Installation
>==================
>
>These are generic installation instructions.
>
>   The `configure' shell script attempts to guess correct values for
>various system-dependent variables used during compilation.  It uses
>those values to create a `Makefile' in each directory of the package.
>It may also create one or more `.h' files containing system-dependent
>definitions.  Finally, it creates a shell script `config.status' that
>you can run in the future to recreate the current configuration, and a
>file `config.log' containing compiler output (useful mainly for
>debugging `configure').
>
>   It can also use an optional file (typically called `config.cache'
>and enabled with `--cache-file=config.cache' or simply `-C') that saves
>the results of its tests to speed up reconfiguring.  (Caching is
>disabled by default to prevent problems with accidental use of stale
>cache files.)
>
>   If you need to do unusual things to compile the package, please try
>to figure out how `configure' could check whether to do them, and mail
>diffs or instructions to the address given in the `README' so they can
>be considered for the next release.  If you are using the cache, and at
>some point `config.cache' contains results you don't want to keep, you
>may remove or edit it.
>
>   The file `configure.ac' (or `configure.in') is used to create
>`configure' by a program called `autoconf'.  You only need
>`configure.ac' if you want to change it or regenerate `configure' using
>a newer version of `autoconf'.
>
>The simplest way to compile this package is:
>
>  1. `cd' to the directory containing the package's source code and type
>     `./configure' to configure the package for your system.  If you're
>     using `csh' on an old version of System V, you might need to type
>     `sh ./configure' instead to prevent `csh' from trying to execute
>     `configure' itself.
>
>     Running `configure' takes awhile.  While running, it prints some
>     messages telling which features it is checking for.
>
>  2. Type `make' to compile the package.
>
>  3. Optionally, type `make check' to run any self-tests that come with
>     the package.
>
>  4. Type `make install' to install the programs and any data files and
>     documentation.
>
>  5. You can remove the program binaries and object files from the
>     source code directory by typing `make clean'.  To also remove the
>     files that `configure' created (so you can compile the package for
>     a different kind of computer), type `make distclean'.  There is
>     also a `make maintainer-clean' target, but that is intended mainly
>     for the package's developers.  If you use it, you may have to get
>     all sorts of other programs in order to regenerate files that came
>     with the distribution.
>
>Compilers and Options
>=====================
>
>Some systems require unusual options for compilation or linking that the
>`configure' script does not know about.  Run `./configure --help' for
>details on some of the pertinent environment variables.
>
>   You can give `configure' initial values for configuration parameters
>by setting variables in the command line or in the environment.  Here
>is an example:
>
>     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
>
>   *Note Defining Variables::, for more details.
>
>Compiling For Multiple Architectures
>====================================
>
>You can compile the package for more than one kind of computer at the
>same time, by placing the object files for each architecture in their
>own directory.  To do this, you must use a version of `make' that
>supports the `VPATH' variable, such as GNU `make'.  `cd' to the
>directory where you want the object files and executables to go and run
>the `configure' script.  `configure' automatically checks for the
>source code in the directory that `configure' is in and in `..'.
>
>   If you have to use a `make' that does not support the `VPATH'
>variable, you have to compile the package for one architecture at a
>time in the source code directory.  After you have installed the
>package for one architecture, use `make distclean' before reconfiguring
>for another architecture.
>
>Installation Names
>==================
>
>By default, `make install' will install the package's files in
>`/usr/local/bin', `/usr/local/man', etc.  You can specify an
>installation prefix other than `/usr/local' by giving `configure' the
>option `--prefix=PREFIX'.
>
>   You can specify separate installation prefixes for
>architecture-specific files and architecture-independent files.  If you
>give `configure' the option `--exec-prefix=PREFIX', the package will
>use PREFIX as the prefix for installing programs and libraries.
>Documentation and other data files will still use the regular prefix.
>
>   In addition, if you use an unusual directory layout you can give
>options like `--bindir=DIR' to specify different values for particular
>kinds of files.  Run `configure --help' for a list of the directories
>you can set and what kinds of files go in them.
>
>   If the package supports it, you can cause programs to be installed
>with an extra prefix or suffix on their names by giving `configure' the
>option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
>
>Optional Features
>=================
>
>Some packages pay attention to `--enable-FEATURE' options to
>`configure', where FEATURE indicates an optional part of the package.
>They may also pay attention to `--with-PACKAGE' options, where PACKAGE
>is something like `gnu-as' or `x' (for the X Window System).  The
>`README' should mention any `--enable-' and `--with-' options that the
>package recognizes.
>
>   For packages that use the X Window System, `configure' can usually
>find the X include and library files automatically, but if it doesn't,
>you can use the `configure' options `--x-includes=DIR' and
>`--x-libraries=DIR' to specify their locations.
>
>Specifying the System Type
>==========================
>
>There may be some features `configure' cannot figure out automatically,
>but needs to determine by the type of machine the package will run on.
>Usually, assuming the package is built to be run on the _same_
>architectures, `configure' can figure that out, but if it prints a
>message saying it cannot guess the machine type, give it the
>`--build=TYPE' option.  TYPE can either be a short name for the system
>type, such as `sun4', or a canonical name which has the form:
>
>     CPU-COMPANY-SYSTEM
>
>where SYSTEM can have one of these forms:
>
>     OS KERNEL-OS
>
>   See the file `config.sub' for the possible values of each field.  If
>`config.sub' isn't included in this package, then this package doesn't
>need to know the machine type.
>
>   If you are _building_ compiler tools for cross-compiling, you should
>use the `--target=TYPE' option to select the type of system they will
>produce code for.
>
>   If you want to _use_ a cross compiler, that generates code for a
>platform different from the build platform, you should specify the
>"host" platform (i.e., that on which the generated programs will
>eventually be run) with `--host=TYPE'.
>
>Sharing Defaults
>================
>
>If you want to set default values for `configure' scripts to share, you
>can create a site shell script called `config.site' that gives default
>values for variables like `CC', `cache_file', and `prefix'.
>`configure' looks for `PREFIX/share/config.site' if it exists, then
>`PREFIX/etc/config.site' if it exists.  Or, you can set the
>`CONFIG_SITE' environment variable to the location of the site script.
>A warning: not all `configure' scripts look for a site script.
>
>Defining Variables
>==================
>
>Variables not defined in a site shell script can be set in the
>environment passed to `configure'.  However, some packages may run
>configure again during the build, and the customized values of these
>variables may be lost.  In order to avoid this problem, you should set
>them in the `configure' command line, using `VAR=value'.  For example:
>
>     ./configure CC=/usr/local2/bin/gcc
>
>causes the specified `gcc' to be used as the C compiler (unless it is
>overridden in the site shell script).  Here is a another example:
>
>     /bin/bash ./configure CONFIG_SHELL=/bin/bash
>
>Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
>configuration-related scripts to be executed by `/bin/bash'.
>
>`configure' Invocation
>======================
>
>`configure' recognizes the following options to control how it operates.
>
>`--help'
>`-h'
>     Print a summary of the options to `configure', and exit.
>
>`--version'
>`-V'
>     Print the version of Autoconf used to generate the `configure'
>     script, and exit.
>
>`--cache-file=FILE'
>     Enable the cache: use and save the results of the tests in FILE,
>     traditionally `config.cache'.  FILE defaults to `/dev/null' to
>     disable caching.
>
>`--config-cache'
>`-C'
>     Alias for `--cache-file=config.cache'.
>
>`--quiet'
>`--silent'
>`-q'
>     Do not print messages saying which checks are being made.  To
>     suppress all normal output, redirect it to `/dev/null' (any error
>     messages will still be shown).
>
>`--srcdir=DIR'
>     Look for the package's source code in directory DIR.  Usually
>     `configure' can determine that directory automatically.
>
>`configure' also accepts some other, not widely useful, options.  Run
>`configure --help' for more details.
>
>BlueZ - Bluetooth protocol stack for Linux
>******************************************
>
>Copyright (C) 2000-2001  Qualcomm Incorporated
>Copyright (C) 2002-2003  Maxim Krasnyansky <maxk@qualcomm.com>
>Copyright (C) 2002-2008  Marcel Holtmann <marcel@holtmann.org>
>
>Bluetooth libraries
>
>
>Compilation and installation
>============================
>
>In order to compile Bluetooth libraries you need following software packages:
>	- Linux Bluetooth protocol stack (BlueZ)
>	- GCC compiler
>
>To configure run:
>	./configure --prefix=/usr
> 
>Configure automatically searches for all required components and packages. 
>
>To compile and install run:
>	make && make install
>
>
>Information
>===========
>
>Mailing lists:
>	bluez-users@lists.sf.net - BlueZ general questions and discussions
>	bluez-devel@lists.sf.net - BlueZ development 
>
>For additional information about the project visit BlueZ web site:
>	http://www.bluez.org
>§Á.`(..«ÁREADME;4803004ee4e¨Á	COPYRIGHT©ÁLICENSEªÁNEWS«ÁREADMEThe copyright information for the JasPer software accompanies the software
>license, and can be found in the file named "LICENSE".
>JasPer License Version 2.0
>
>Copyright (c) 2001-2006 Michael David Adams
>Copyright (c) 1999-2000 Image Power, Inc.
>Copyright (c) 1999-2000 The University of British Columbia
>
>All rights reserved.
>
>Permission is hereby granted, free of charge, to any person (the
>"User") obtaining a copy of this software and associated documentation
>files (the "Software"), to deal in the Software without restriction,
>including without limitation the rights to use, copy, modify, merge,
>publish, distribute, and/or sell copies of the Software, and to permit
>persons to whom the Software is furnished to do so, subject to the
>following conditions:
>
>1.  The above copyright notices and this permission notice (which
>includes the disclaimer below) shall be included in all copies or
>substantial portions of the Software.
>
>2.  The name of a copyright holder shall not be used to endorse or
>promote products derived from the Software without specific prior
>written permission.
>
>THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS
>LICENSE.  NO USE OF THE SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER
>THIS DISCLAIMER.  THE SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS
>"AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING
>BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
>PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS.  IN NO
>EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL
>INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING
>FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
>NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
>WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.  NO ASSURANCES ARE
>PROVIDED BY THE COPYRIGHT HOLDERS THAT THE SOFTWARE DOES NOT INFRINGE
>THE PATENT OR OTHER INTELLECTUAL PROPERTY RIGHTS OF ANY OTHER ENTITY.
>EACH COPYRIGHT HOLDER DISCLAIMS ANY LIABILITY TO THE USER FOR CLAIMS
>BROUGHT BY ANY OTHER ENTITY BASED ON INFRINGEMENT OF INTELLECTUAL
>PROPERTY RIGHTS OR OTHERWISE.  AS A CONDITION TO EXERCISING THE RIGHTS
>GRANTED HEREUNDER, EACH USER HEREBY ASSUMES SOLE RESPONSIBILITY TO SECURE
>ANY OTHER INTELLECTUAL PROPERTY RIGHTS NEEDED, IF ANY.  THE SOFTWARE
>IS NOT FAULT-TOLERANT AND IS NOT INTENDED FOR USE IN MISSION-CRITICAL
>SYSTEMS, SUCH AS THOSE USED IN THE OPERATION OF NUCLEAR FACILITIES,
>AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL
>SYSTEMS, DIRECT LIFE SUPPORT MACHINES, OR WEAPONS SYSTEMS, IN WHICH
>THE FAILURE OF THE SOFTWARE OR SYSTEM COULD LEAD DIRECTLY TO DEATH,
>PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE ("HIGH
>RISK ACTIVITIES").  THE COPYRIGHT HOLDERS SPECIFICALLY DISCLAIM ANY
>EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR HIGH RISK ACTIVITIES.
>
>Dear JasPer Users:
>
>I am pleased to announce the availability of JasPer version 1.900.1.
>
>This release fixes some build problems as well as
>a multiply-defined symbol problem in jpc_qmfb.h.
>
>The new JasPer release is available from the JasPer Project Home Page
>(i.e., http://www.ece.uvic.ca/~mdadams/jasper) and the JPEG web site
>(i.e., http://www.jpeg.org/software).
>
>Regards,
>Michael
>
>---
>Michael Adams, Assistant Professor
>Dept. of Elec. and Comp. Engineering, University of Victoria
>P.O. Box 3055 STN CSC, Victoria, BC, V8W 3P6, CANADA
>E-mail: mdadams@ece.uvic.ca, Web: www.ece.uvic.ca/~mdadams
>JasPer Readme
>*************
>
>This is the source code distribution for JasPer.  JasPer is a collection
>of software (i.e., a library and application programs) for the coding
>and manipulation of images.  This software can handle image data in a
>variety of formats.  One such format supported by JasPer is the JPEG-2000
>format defined in ISO/IEC 15444-1.
>
>The complete licensing terms for the JasPer software can be found in
>the file named "LICENSE" in the top level directory of this software
>distribution.  Any use of this software contrary to the terms of the
>license is strictly prohibited.  The changes made to the software
>since the last release are described in the file "NEWS".  Detailed
>documentation on the JasPer software can be found in the JasPer Software
>Reference Manual.  This manual is located in the "doc" directory, and
>includes useful information such as: 1) how to build, install, and use
>the software, 2) how to submit report bugs, and 3) where to find
>additional information about the software.
>
>Enjoy! :)
>
>¬Á.`..®ÁCOPYING.LIB3004eÁ(COPYING°ÁREADME;4803004e3¯ÁNEWS°ÁREADME                    GNU GENERAL PUBLIC LICENSE
>                       Version 3, 29 June 2007
>
> Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
> Everyone is permitted to copy and distribute verbatim copies
> of this license document, but changing it is not allowed.
>
>                            Preamble
>
>  The GNU General Public License is a free, copyleft license for
>software and other kinds of works.
>
>  The licenses for most software and other practical works are designed
>to take away your freedom to share and change the works.  By contrast,
>the GNU General Public License is intended to guarantee your freedom to
>share and change all versions of a program--to make sure it remains free
>software for all its users.  We, the Free Software Foundation, use the
>GNU General Public License for most of our software; it applies also to
>any other work released this way by its authors.  You can apply it to
>your programs, too.
>
>  When we speak of free software, we are referring to freedom, not
>price.  Our General Public Licenses are designed to make sure that you
>have the freedom to distribute copies of free software (and charge for
>them if you wish), that you receive source code or can get it if you
>want it, that you can change the software or use pieces of it in new
>free programs, and that you know you can do these things.
>
>  To protect your rights, we need to prevent others from denying you
>these rights or asking you to surrender the rights.  Therefore, you have
>certain responsibilities if you distribute copies of the software, or if
>you modify it: responsibilities to respect the freedom of others.
>
>  For example, if you distribute copies of such a program, whether
>gratis or for a fee, you must pass on to the recipients the same
>freedoms that you received.  You must make sure that they, too, receive
>or can get the source code.  And you must show them these terms so they
>know their rights.
>
>  Developers that use the GNU GPL protect your rights with two steps:
>(1) assert copyright on the software, and (2) offer you this License
>giving you legal permission to copy, distribute and/or modify it.
>
>  For the developers' and authors' protection, the GPL clearly explains
>that there is no warranty for this free software.  For both users' and
>authors' sake, the GPL requires that modified versions be marked as
>changed, so that their problems will not be attributed erroneously to
>authors of previous versions.
>
>  Some devices are designed to deny users access to install or run
>modified versions of the software inside them, although the manufacturer
>can do so.  This is fundamentally incompatible with the aim of
>protecting users' freedom to change the software.  The systematic
>pattern of such abuse occurs in the area of products for individuals to
>use, which is precisely where it is most unacceptable.  Therefore, we
>have designed this version of the GPL to prohibit the practice for those
>products.  If such problems arise substantially in other domains, we
>stand ready to extend this provision to those domains in future versions
>of the GPL, as needed to protect the freedom of users.
>
>  Finally, every program is threatened constantly by software patents.
>States should not allow patents to restrict development and use of
>software on general-purpose computers, but in those that do, we wish to
>avoid the special danger that patents applied to a free program could
>make it effectively proprietary.  To prevent this, the GPL assures that
>patents cannot be used to render the program non-free.
>
>  The precise terms and conditions for copying, distribution and
>modification follow.
>
>                       TERMS AND CONDITIONS
>
>  0. Definitions.
>
>  "This License" refers to version 3 of the GNU General Public License.
>
>  "Copyright" also means copyright-like laws that apply to other kinds of
>works, such as semiconductor masks.
>
>  "The Program" refers to any copyrightable work licensed under this
>License.  Each licensee is addressed as "you".  "Licensees" and
>"recipients" may be individuals or organizations.
>
>  To "modify" a work means to copy from or adapt all or part of the work
>in a fashion requiring copyright permission, other than the making of an
>exact copy.  The resulting work is called a "modified version" of the
>earlier work or a work "based on" the earlier work.
>
>  A "covered work" means either the unmodified Program or a work based
>on the Program.
>
>  To "propagate" a work means to do anything with it that, without
>permission, would make you directly or secondarily liable for
>infringement under applicable copyright law, except executing it on a
>computer or modifying a private copy.  Propagation includes copying,
>distribution (with or without modification), making available to the
>public, and in some countries other activities as well.
>
>  To "convey" a work means any kind of propagation that enables other
>parties to make or receive copies.  Mere interaction with a user through
>a computer network, with no transfer of a copy, is not conveying.
>
>  An interactive user interface displays "Appropriate Legal Notices"
>to the extent that it includes a convenient and prominently visible
>feature that (1) displays an appropriate copyright notice, and (2)
>tells the user that there is no warranty for the work (except to the
>extent that warranties are provided), that licensees may convey the
>work under this License, and how to view a copy of this License.  If
>the interface presents a list of user commands or options, such as a
>menu, a prominent item in the list meets this criterion.
>
>  1. Source Code.
>
>  The "source code" for a work means the preferred form of the work
>for making modifications to it.  "Object code" means any non-source
>form of a work.
>
>  A "Standard Interface" means an interface that either is an official
>standard defined by a recognized standards body, or, in the case of
>interfaces specified for a particular programming language, one that
>is widely used among developers working in that language.
>
>  The "System Libraries" of an executable work include anything, other
>than the work as a whole, that (a) is included in the normal form of
>packaging a Major Component, but which is not part of that Major
>Component, and (b) serves only to enable use of the work with that
>Major Component, or to implement a Standard Interface for which an
>implementation is available to the public in source code form.  A
>"Major Component", in this context, means a major essential component
>(kernel, window system, and so on) of the specific operating system
>(if any) on which the executable work runs, or a compiler used to
>produce the work, or an object code interpreter used to run it.
>
>  The "Corresponding Source" for a work in object code form means all
>the source code needed to generate, install, and (for an executable
>work) run the object code and to modify the work, including scripts to
>control those activities.  However, it does not include the work's
>System Libraries, or general-purpose tools or generally available free
>programs which are used unmodified in performing those activities but
>which are not part of the work.  For example, Corresponding Source
>includes interface definition files associated with source files for
>the work, and the source code for shared libraries and dynamically
>linked subprograms that the work is specifically designed to require,
>such as by intimate data communication or control flow between those
>subprograms and other parts of the work.
>
>  The Corresponding Source need not include anything that users
>can regenerate automatically from other parts of the Corresponding
>Source.
>
>  The Corresponding Source for a work in source code form is that
>same work.
>
>  2. Basic Permissions.
>
>  All rights granted under this License are granted for the term of
>copyright on the Program, and are irrevocable provided the stated
>conditions are met.  This License explicitly affirms your unlimited
>permission to run the unmodified Program.  The output from running a
>covered work is covered by this License only if the output, given its
>content, constitutes a covered work.  This License acknowledges your
>rights of fair use or other equivalent, as provided by copyright law.
>
>  You may make, run and propagate covered works that you do not
>convey, without conditions so long as your license otherwise remains
>in force.  You may convey covered works to others for the sole purpose
>of having them make modifications exclusively for you, or provide you
>with facilities for running those works, provided that you comply with
>the terms of this License in conveying all material for which you do
>not control copyright.  Those thus making or running the covered works
>for you must do so exclusively on your behalf, under your direction
>and control, on terms that prohibit them from making any copies of
>your copyrighted material outside their relationship with you.
>
>  Conveying under any other circumstances is permitted solely under
>the conditions stated below.  Sublicensing is not allowed; section 10
>makes it unnecessary.
>
>  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
>
>  No covered work shall be deemed part of an effective technological
>measure under any applicable law fulfilling obligations under article
>11 of the WIPO copyright treaty adopted on 20 December 1996, or
>similar laws prohibiting or restricting circumvention of such
>measures.
>
>  When you convey a covered work, you waive any legal power to forbid
>circumvention of technological measures to the extent such circumvention
>is effected by exercising rights under this License with respect to
>the covered work, and you disclaim any intention to limit operation or
>modification of the work as a means of enforcing, against the work's
>users, your or third parties' legal rights to forbid circumvention of
>technological measures.
>
>  4. Conveying Verbatim Copies.
>
>  You may convey verbatim copies of the Program's source code as you
>receive it, in any medium, provided that you conspicuously and
>appropriately publish on each copy an appropriate copyright notice;
>keep intact all notices stating that this License and any
>non-permissive terms added in accord with section 7 apply to the code;
>keep intact all notices of the absence of any warranty; and give all
>recipients a copy of this License along with the Program.
>
>  You may charge any price or no price for each copy that you convey,
>and you may offer support or warranty protection for a fee.
>
>  5. Conveying Modified Source Versions.
>
>  You may convey a work based on the Program, or the modifications to
>produce it from the Program, in the form of source code under the
>terms of section 4, provided that you also meet all of these conditions:
>
>    a) The work must carry prominent notices stating that you modified
>    it, and giving a relevant date.
>
>    b) The work must carry prominent notices stating that it is
>    released under this License and any conditions added under section
>    7.  This requirement modifies the requirement in section 4 to
>    "keep intact all notices".
>
>    c) You must license the entire work, as a whole, under this
>    License to anyone who comes into possession of a copy.  This
>    License will therefore apply, along with any applicable section 7
>    additional terms, to the whole of the work, and all its parts,
>    regardless of how they are packaged.  This License gives no
>    permission to license the work in any other way, but it does not
>    invalidate such permission if you have separately received it.
>
>    d) If the work has interactive user interfaces, each must display
>    Appropriate Legal Notices; however, if the Program has interactive
>    interfaces that do not display Appropriate Legal Notices, your
>    work need not make them do so.
>
>  A compilation of a covered work with other separate and independent
>works, which are not by their nature extensions of the covered work,
>and which are not combined with it such as to form a larger program,
>in or on a volume of a storage or distribution medium, is called an
>"aggregate" if the compilation and its resulting copyright are not
>used to limit the access or legal rights of the compilation's users
>beyond what the individual works permit.  Inclusion of a covered work
>in an aggregate does not cause this License to apply to the other
>parts of the aggregate.
>
>  6. Conveying Non-Source Forms.
>
>  You may convey a covered work in object code form under the terms
>of sections 4 and 5, provided that you also convey the
>machine-readable Corresponding Source under the terms of this License,
>in one of these ways:
>
>    a) Convey the object code in, or embodied in, a physical product
>    (including a physical distribution medium), accompanied by the
>    Corresponding Source fixed on a durable physical medium
>    customarily used for software interchange.
>
>    b) Convey the object code in, or embodied in, a physical product
>    (including a physical distribution medium), accompanied by a
>    written offer, valid for at least three years and valid for as
>    long as you offer spare parts or customer support for that product
>    model, to give anyone who possesses the object code either (1) a
>    copy of the Corresponding Source for all the software in the
>    product that is covered by this License, on a durable physical
>    medium customarily used for software interchange, for a price no
>    more than your reasonable cost of physically performing this
>    conveying of source, or (2) access to copy the
>    Corresponding Source from a network server at no charge.
>
>    c) Convey individual copies of the object code with a copy of the
>    written offer to provide the Corresponding Source.  This
>    alternative is allowed only occasionally and noncommercially, and
>    only if you received the object code with such an offer, in accord
>    with subsection 6b.
>
>    d) Convey the object code by offering access from a designated
>    place (gratis or for a charge), and offer equivalent access to the
>    Corresponding Source in the same way through the same place at no
>    further charge.  You need not require recipients to copy the
>    Corresponding Source along with the object code.  If the place to
>    copy the object code is a network server, the Corresponding Source
>    may be on a different server (operated by you or a third party)
>    that supports equivalent copying facilities, provided you maintain
>    clear directions next to the object code saying where to find the
>    Corresponding Source.  Regardless of what server hosts the
>    Corresponding Source, you remain obligated to ensure that it is
>    available for as long as needed to satisfy these requirements.
>
>    e) Convey the object code using peer-to-peer transmission, provided
>    you inform other peers where the object code and Corresponding
>    Source of the work are being offered to the general public at no
>    charge under subsection 6d.
>
>  A separable portion of the object code, whose source code is excluded
>from the Corresponding Source as a System Library, need not be
>included in conveying the object code work.
>
>  A "User Product" is either (1) a "consumer product", which means any
>tangible personal property which is normally used for personal, family,
>or household purposes, or (2) anything designed or sold for incorporation
>into a dwelling.  In determining whether a product is a consumer product,
>doubtful cases shall be resolved in favor of coverage.  For a particular
>product received by a particular user, "normally used" refers to a
>typical or common use of that class of product, regardless of the status
>of the particular user or of the way in which the particular user
>actually uses, or expects or is expected to use, the product.  A product
>is a consumer product regardless of whether the product has substantial
>commercial, industrial or non-consumer uses, unless such uses represent
>the only significant mode of use of the product.
>
>  "Installation Information" for a User Product means any methods,
>procedures, authorization keys, or other information required to install
>and execute modified versions of a covered work in that User Product from
>a modified version of its Corresponding Source.  The information must
>suffice to ensure that the continued functioning of the modified object
>code is in no case prevented or interfered with solely because
>modification has been made.
>
>  If you convey an object code work under this section in, or with, or
>specifically for use in, a User Product, and the conveying occurs as
>part of a transaction in which the right of possession and use of the
>User Product is transferred to the recipient in perpetuity or for a
>fixed term (regardless of how the transaction is characterized), the
>Corresponding Source conveyed under this section must be accompanied
>by the Installation Information.  But this requirement does not apply
>if neither you nor any third party retains the ability to install
>modified object code on the User Product (for example, the work has
>been installed in ROM).
>
>  The requirement to provide Installation Information does not include a
>requirement to continue to provide support service, warranty, or updates
>for a work that has been modified or installed by the recipient, or for
>the User Product in which it has been modified or installed.  Access to a
>network may be denied when the modification itself materially and
>adversely affects the operation of the network or violates the rules and
>protocols for communication across the network.
>
>  Corresponding Source conveyed, and Installation Information provided,
>in accord with this section must be in a format that is publicly
>documented (and with an implementation available to the public in
>source code form), and must require no special password or key for
>unpacking, reading or copying.
>
>  7. Additional Terms.
>
>  "Additional permissions" are terms that supplement the terms of this
>License by making exceptions from one or more of its conditions.
>Additional permissions that are applicable to the entire Program shall
>be treated as though they were included in this License, to the extent
>that they are valid under applicable law.  If additional permissions
>apply only to part of the Program, that part may be used separately
>under those permissions, but the entire Program remains governed by
>this License without regard to the additional permissions.
>
>  When you convey a copy of a covered work, you may at your option
>remove any additional permissions from that copy, or from any part of
>it.  (Additional permissions may be written to require their own
>removal in certain cases when you modify the work.)  You may place
>additional permissions on material, added by you to a covered work,
>for which you have or can give appropriate copyright permission.
>
>  Notwithstanding any other provision of this License, for material you
>add to a covered work, you may (if authorized by the copyright holders of
>that material) supplement the terms of this License with terms:
>
>    a) Disclaiming warranty or limiting liability differently from the
>    terms of sections 15 and 16 of this License; or
>
>    b) Requiring preservation of specified reasonable legal notices or
>    author attributions in that material or in the Appropriate Legal
>    Notices displayed by works containing it; or
>
>    c) Prohibiting misrepresentation of the origin of that material, or
>    requiring that modified versions of such material be marked in
>    reasonable ways as different from the original version; or
>
>    d) Limiting the use for publicity purposes of names of licensors or
>    authors of the material; or
>
>    e) Declining to grant rights under trademark law for use of some
>    trade names, trademarks, or service marks; or
>
>    f) Requiring indemnification of licensors and authors of that
>    material by anyone who conveys the material (or modified versions of
>    it) with contractual assumptions of liability to the recipient, for
>    any liability that these contractual assumptions directly impose on
>    those licensors and authors.
>
>  All other non-permissive additional terms are considered "further
>restrictions" within the meaning of section 10.  If the Program as you
>received it, or any part of it, contains a notice stating that it is
>governed by this License along with a term that is a further
>restriction, you may remove that term.  If a license document contains
>a further restriction but permits relicensing or conveying under this
>License, you may add to a covered work material governed by the terms
>of that license document, provided that the further restriction does
>not survive such relicensing or conveying.
>
>  If you add terms to a covered work in accord with this section, you
>must place, in the relevant source files, a statement of the
>additional terms that apply to those files, or a notice indicating
>where to find the applicable terms.
>
>  Additional terms, permissive or non-permissive, may be stated in the
>form of a separately written license, or stated as exceptions;
>the above requirements apply either way.
>
>  8. Termination.
>
>  You may not propagate or modify a covered work except as expressly
>provided under this License.  Any attempt otherwise to propagate or
>modify it is void, and will automatically terminate your rights under
>this License (including any patent licenses granted under the third
>paragraph of section 11).
>
>  However, if you cease all violation of this License, then your
>license from a particular copyright holder is reinstated (a)
>provisionally, unless and until the copyright holder explicitly and
>finally terminates your license, and (b) permanently, if the copyright
>holder fails to notify you of the violation by some reasonable means
>prior to 60 days after the cessation.
>
>  Moreover, your license from a particular copyright holder is
>reinstated permanently if the copyright holder notifies you of the
>violation by some reasonable means, this is the first time you have
>received notice of violation of this License (for any work) from that
>copyright holder, and you cure the violation prior to 30 days after
>your receipt of the notice.
>
>  Termination of your rights under this section does not terminate the
>licenses of parties who have received copies or rights from you under
>this License.  If your rights have been terminated and not permanently
>reinstated, you do not qualify to receive new licenses for the same
>material under section 10.
>
>  9. Acceptance Not Required for Having Copies.
>
>  You are not required to accept this License in order to receive or
>run a copy of the Program.  Ancillary propagation of a covered work
>occurring solely as a consequence of using peer-to-peer transmission
>to receive a copy likewise does not require acceptance.  However,
>nothing other than this License grants you permission to propagate or
>modify any covered work.  These actions infringe copyright if you do
>not accept this License.  Therefore, by modifying or propagating a
>covered work, you indicate your acceptance of this License to do so.
>
>  10. Automatic Licensing of Downstream Recipients.
>
>  Each time you convey a covered work, the recipient automatically
>receives a license from the original licensors, to run, modify and
>propagate that work, subject to this License.  You are not responsible
>for enforcing compliance by third parties with this License.
>
>  An "entity transaction" is a transaction transferring control of an
>organization, or substantially all assets of one, or subdividing an
>organization, or merging organizations.  If propagation of a covered
>work results from an entity transaction, each party to that
>transaction who receives a copy of the work also receives whatever
>licenses to the work the party's predecessor in interest had or could
>give under the previous paragraph, plus a right to possession of the
>Corresponding Source of the work from the predecessor in interest, if
>the predecessor has it or can get it with reasonable efforts.
>
>  You may not impose any further restrictions on the exercise of the
>rights granted or affirmed under this License.  For example, you may
>not impose a license fee, royalty, or other charge for exercise of
>rights granted under this License, and you may not initiate litigation
>(including a cross-claim or counterclaim in a lawsuit) alleging that
>any patent claim is infringed by making, using, selling, offering for
>sale, or importing the Program or any portion of it.
>
>  11. Patents.
>
>  A "contributor" is a copyright holder who authorizes use under this
>License of the Program or a work on which the Program is based.  The
>work thus licensed is called the contributor's "contributor version".
>
>  A contributor's "essential patent claims" are all patent claims
>owned or controlled by the contributor, whether already acquired or
>hereafter acquired, that would be infringed by some manner, permitted
>by this License, of making, using, or selling its contributor version,
>but do not include claims that would be infringed only as a
>consequence of further modification of the contributor version.  For
>purposes of this definition, "control" includes the right to grant
>patent sublicenses in a manner consistent with the requirements of
>this License.
>
>  Each contributor grants you a non-exclusive, worldwide, royalty-free
>patent license under the contributor's essential patent claims, to
>make, use, sell, offer for sale, import and otherwise run, modify and
>propagate the contents of its contributor version.
>
>  In the following three paragraphs, a "patent license" is any express
>agreement or commitment, however denominated, not to enforce a patent
>(such as an express permission to practice a patent or covenant not to
>sue for patent infringement).  To "grant" such a patent license to a
>party means to make such an agreement or commitment not to enforce a
>patent against the party.
>
>  If you convey a covered work, knowingly relying on a patent license,
>and the Corresponding Source of the work is not available for anyone
>to copy, free of charge and under the terms of this License, through a
>publicly available network server or other readily accessible means,
>then you must either (1) cause the Corresponding Source to be so
>available, or (2) arrange to deprive yourself of the benefit of the
>patent license for this particular work, or (3) arrange, in a manner
>consistent with the requirements of this License, to extend the patent
>license to downstream recipients.  "Knowingly relying" means you have
>actual knowledge that, but for the patent license, your conveying the
>covered work in a country, or your recipient's use of the covered work
>in a country, would infringe one or more identifiable patents in that
>country that you have reason to believe are valid.
>
>  If, pursuant to or in connection with a single transaction or
>arrangement, you convey, or propagate by procuring conveyance of, a
>covered work, and grant a patent license to some of the parties
>receiving the covered work authorizing them to use, propagate, modify
>or convey a specific copy of the covered work, then the patent license
>you grant is automatically extended to all recipients of the covered
>work and works based on it.
>
>  A patent license is "discriminatory" if it does not include within
>the scope of its coverage, prohibits the exercise of, or is
>conditioned on the non-exercise of one or more of the rights that are
>specifically granted under this License.  You may not convey a covered
>work if you are a party to an arrangement with a third party that is
>in the business of distributing software, under which you make payment
>to the third party based on the extent of your activity of conveying
>the work, and under which the third party grants, to any of the
>parties who would receive the covered work from you, a discriminatory
>patent license (a) in connection with copies of the covered work
>conveyed by you (or copies made from those copies), or (b) primarily
>for and in connection with specific products or compilations that
>contain the covered work, unless you entered into that arrangement,
>or that patent license was granted, prior to 28 March 2007.
>
>  Nothing in this License shall be construed as excluding or limiting
>any implied license or other defenses to infringement that may
>otherwise be available to you under applicable patent law.
>
>  12. No Surrender of Others' Freedom.
>
>  If conditions are imposed on you (whether by court order, agreement or
>otherwise) that contradict the conditions of this License, they do not
>excuse you from the conditions of this License.  If you cannot convey a
>covered work so as to satisfy simultaneously your obligations under this
>License and any other pertinent obligations, then as a consequence you may
>not convey it at all.  For example, if you agree to terms that obligate you
>to collect a royalty for further conveying from those to whom you convey
>the Program, the only way you could satisfy both those terms and this
>License would be to refrain entirely from conveying the Program.
>
>  13. Use with the GNU Affero General Public License.
>
>  Notwithstanding any other provision of this License, you have
>permission to link or combine any covered work with a work licensed
>under version 3 of the GNU Affero General Public License into a single
>combined work, and to convey the resulting work.  The terms of this
>License will continue to apply to the part which is the covered work,
>but the special requirements of the GNU Affero General Public License,
>section 13, concerning interaction through a network will apply to the
>combination as such.
>
>  14. Revised Versions of this License.
>
>  The Free Software Foundation may publish revised and/or new versions of
>the GNU General Public License from time to time.  Such new versions will
>be similar in spirit to the present version, but may differ in detail to
>address new problems or concerns.
>
>  Each version is given a distinguishing version number.  If the
>Program specifies that a certain numbered version of the GNU General
>Public License "or any later version" applies to it, you have the
>option of following the terms and conditions either of that numbered
>version or of any later version published by the Free Software
>Foundation.  If the Program does not specify a version number of the
>GNU General Public License, you may choose any version ever published
>by the Free Software Foundation.
>
>  If the Program specifies that a proxy can decide which future
>versions of the GNU General Public License can be used, that proxy's
>public statement of acceptance of a version permanently authorizes you
>to choose that version for the Program.
>
>  Later license versions may give you additional or different
>permissions.  However, no additional obligations are imposed on any
>author or copyright holder as a result of your choosing to follow a
>later version.
>
>  15. Disclaimer of Warranty.
>
>  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
>APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
>HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
>OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
>THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
>PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
>IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
>ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
>
>  16. Limitation of Liability.
>
>  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
>WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
>THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
>GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
>USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
>DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
>PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
>EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
>SUCH DAMAGES.
>
>  17. Interpretation of Sections 15 and 16.
>
>  If the disclaimer of warranty and limitation of liability provided
>above cannot be given local legal effect according to their terms,
>reviewing courts shall apply local law that most closely approximates
>an absolute waiver of all civil liability in connection with the
>Program, unless a warranty or assumption of liability accompanies a
>copy of the Program in return for a fee.
>
>                     END OF TERMS AND CONDITIONS
>
>            How to Apply These Terms to Your New Programs
>
>  If you develop a new program, and you want it to be of the greatest
>possible use to the public, the best way to achieve this is to make it
>free software which everyone can redistribute and change under these terms.
>
>  To do so, attach the following notices to the program.  It is safest
>to attach them to the start of each source file to most effectively
>state the exclusion of warranty; and each file should have at least
>the "copyright" line and a pointer to where the full notice is found.
>
>    <one line to give the program's name and a brief idea of what it does.>
>    Copyright (C) <year>  <name of author>
>
>    This program is free software: you can redistribute it and/or modify
>    it under the terms of the GNU General Public License as published by
>    the Free Software Foundation, either version 3 of the License, or
>    (at your option) any later version.
>
>    This program is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>    GNU General Public License for more details.
>
>    You should have received a copy of the GNU General Public License
>    along with this program.  If not, see <http://www.gnu.org/licenses/>.
>
>Also add information on how to contact you by electronic and paper mail.
>
>  If the program does terminal interaction, make it output a short
>notice like this when it starts in an interactive mode:
>
>    <program>  Copyright (C) <year>  <name of author>
>    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
>    This is free software, and you are welcome to redistribute it
>    under certain conditions; type `show c' for details.
>
>The hypothetical commands `show w' and `show c' should show the appropriate
>parts of the General Public License.  Of course, your program's commands
>might be different; for a GUI interface, you would use an "about box".
>
>  You should also get your employer (if you work as a programmer) or school,
>if any, to sign a "copyright disclaimer" for the program, if necessary.
>For more information on this, and how to apply and follow the GNU GPL, see
><http://www.gnu.org/licenses/>.
>
>  The GNU General Public License does not permit incorporating your program
>into proprietary programs.  If your program is a subroutine library, you
>may consider it more useful to permit linking proprietary applications with
>the library.  If this is what you want to do, use the GNU Lesser General
>Public License instead of this License.  But first, please read
><http://www.gnu.org/philosophy/why-not-lgpl.html>.
>		   GNU LESSER GENERAL PUBLIC LICENSE
>                       Version 3, 29 June 2007
>
> Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
> Everyone is permitted to copy and distribute verbatim copies
> of this license document, but changing it is not allowed.
>
>
>  This version of the GNU Lesser General Public License incorporates
>the terms and conditions of version 3 of the GNU General Public
>License, supplemented by the additional permissions listed below.
>
>  0. Additional Definitions. 
>
>  As used herein, "this License" refers to version 3 of the GNU Lesser
>General Public License, and the "GNU GPL" refers to version 3 of the GNU
>General Public License.
>
>  "The Library" refers to a covered work governed by this License,
>other than an Application or a Combined Work as defined below.
>
>  An "Application" is any work that makes use of an interface provided
>by the Library, but which is not otherwise based on the Library.
>Defining a subclass of a class defined by the Library is deemed a mode
>of using an interface provided by the Library.
>
>  A "Combined Work" is a work produced by combining or linking an
>Application with the Library.  The particular version of the Library
>with which the Combined Work was made is also called the "Linked
>Version".
>
>  The "Minimal Corresponding Source" for a Combined Work means the
>Corresponding Source for the Combined Work, excluding any source code
>for portions of the Combined Work that, considered in isolation, are
>based on the Application, and not on the Linked Version.
>
>  The "Corresponding Application Code" for a Combined Work means the
>object code and/or source code for the Application, including any data
>and utility programs needed for reproducing the Combined Work from the
>Application, but excluding the System Libraries of the Combined Work.
>
>  1. Exception to Section 3 of the GNU GPL.
>
>  You may convey a covered work under sections 3 and 4 of this License
>without being bound by section 3 of the GNU GPL.
>
>  2. Conveying Modified Versions.
>
>  If you modify a copy of the Library, and, in your modifications, a
>facility refers to a function or data to be supplied by an Application
>that uses the facility (other than as an argument passed when the
>facility is invoked), then you may convey a copy of the modified
>version:
>
>   a) under this License, provided that you make a good faith effort to
>   ensure that, in the event an Application does not supply the
>   function or data, the facility still operates, and performs
>   whatever part of its purpose remains meaningful, or
>
>   b) under the GNU GPL, with none of the additional permissions of
>   this License applicable to that copy.
>
>  3. Object Code Incorporating Material from Library Header Files.
>
>  The object code form of an Application may incorporate material from
>a header file that is part of the Library.  You may convey such object
>code under terms of your choice, provided that, if the incorporated
>material is not limited to numerical parameters, data structure
>layouts and accessors, or small macros, inline functions and templates
>(ten or fewer lines in length), you do both of the following:
>
>   a) Give prominent notice with each copy of the object code that the
>   Library is used in it and that the Library and its use are
>   covered by this License.
>
>   b) Accompany the object code with a copy of the GNU GPL and this license
>   document.
>
>  4. Combined Works.
>
>  You may convey a Combined Work under terms of your choice that,
>taken together, effectively do not restrict modification of the
>portions of the Library contained in the Combined Work and reverse
>engineering for debugging such modifications, if you also do each of
>the following:
>
>   a) Give prominent notice with each copy of the Combined Work that
>   the Library is used in it and that the Library and its use are
>   covered by this License.
>
>   b) Accompany the Combined Work with a copy of the GNU GPL and this license
>   document.
>
>   c) For a Combined Work that displays copyright notices during
>   execution, include the copyright notice for the Library among
>   these notices, as well as a reference directing the user to the
>   copies of the GNU GPL and this license document.
>
>   d) Do one of the following:
>
>       0) Convey the Minimal Corresponding Source under the terms of this
>       License, and the Corresponding Application Code in a form
>       suitable for, and under terms that permit, the user to
>       recombine or relink the Application with a modified version of
>       the Linked Version to produce a modified Combined Work, in the
>       manner specified by section 6 of the GNU GPL for conveying
>       Corresponding Source.
>
>       1) Use a suitable shared library mechanism for linking with the
>       Library.  A suitable mechanism is one that (a) uses at run time
>       a copy of the Library already present on the user's computer
>       system, and (b) will operate properly with a modified version
>       of the Library that is interface-compatible with the Linked
>       Version. 
>
>   e) Provide Installation Information, but only if you would otherwise
>   be required to provide such information under section 6 of the
>   GNU GPL, and only to the extent that such information is
>   necessary to install and execute a modified version of the
>   Combined Work produced by recombining or relinking the
>   Application with a modified version of the Linked Version. (If
>   you use option 4d0, the Installation Information must accompany
>   the Minimal Corresponding Source and Corresponding Application
>   Code. If you use option 4d1, you must provide the Installation
>   Information in the manner specified by section 6 of the GNU GPL
>   for conveying Corresponding Source.)
>
>  5. Combined Libraries.
>
>  You may place library facilities that are a work based on the
>Library side by side in a single library together with other library
>facilities that are not Applications and are not covered by this
>License, and convey such a combined library under terms of your
>choice, if you do both of the following:
>
>   a) Accompany the combined library with a copy of the same work based
>   on the Library, uncombined with any other library facilities,
>   conveyed under the terms of this License.
>
>   b) Give prominent notice with the combined library that part of it
>   is a work based on the Library, and explaining where to find the
>   accompanying uncombined form of the same work.
>
>  6. Revised Versions of the GNU Lesser General Public License.
>
>  The Free Software Foundation may publish revised and/or new versions
>of the GNU Lesser General Public License from time to time. Such new
>versions will be similar in spirit to the present version, but may
>differ in detail to address new problems or concerns.
>
>  Each version is given a distinguishing version number. If the
>Library as you received it specifies that a certain numbered version
>of the GNU Lesser General Public License "or any later version"
>applies to it, you have the option of following the terms and
>conditions either of that published version or of any later version
>published by the Free Software Foundation. If the Library as you
>received it does not specify a version number of the GNU Lesser
>General Public License, you may choose any version of the GNU Lesser
>General Public License ever published by the Free Software Foundation.
>
>  If the Library as you received it specifies that a proxy can decide
>whether future versions of the GNU Lesser General Public License shall
>apply, that proxy's public statement of acceptance of any version is
>permanent authorization for you to choose that version for the
>Library.
>Copyright 1996, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007
>Free Software Foundation, Inc.
>
>This file is part of the GNU MP Library.
>
>The GNU MP Library is free software; you can redistribute it and/or modify
>it under the terms of the GNU Lesser General Public License as published by
>the Free Software Foundation; either version 3 of the License, or (at your
>option) any later version.
>
>The GNU MP Library is distributed in the hope that it will be useful, but
>WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
>or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Lesser General Public
>License for more details.
>
>You should have received a copy of the GNU Lesser General Public License
>along with the GNU MP Library.  If not, see http://www.gnu.org/licenses/.
>
>
>Changes between GMP version 4.2.1 and 4.2.2
>
>  * License is now LGPL version 3.
>
>  Bugs:
>  * Shared library numbers corrected for libcxx.
>  * Fixed serious bug in gmpxx.h where a=a+b*c would generate garbage.
>    Note that this only affects C++ programs.
>  * Fix crash in mpz_set_d for arguments with large negative exponent.
>  * Fix 32-bit ABI bug with Itanium assembly for popcount and hamdist.
>  * Fix assembly syntax problem for powerpc-ibm-aix with AIX native assembler.
>  * Fix problems with x86 --enable-fat, where the compiler where told to
>    generate code for the build machine, not plain i386 code as it should.
>  * Improved recognition of powerpc systems wrt Altivec/VMX capability.
>  * Misc minor fixes, mainly workarounds for compiler/assembler bugs.
>
>  Speedups:
>  * "Core 2" and Pentium 4 processors, running in 64-bit mode will get a
>     slight boost as they are now specifically recognized.
>
>  Features:
>  * New support for x86_64-solaris
>  * New, rudimentary support for x86-apple-darwin and x86_64-apple-darwin.
>    (Please see http://gmplib.org/macos.html for more information.)
>
>
>Changes between GMP version 4.2 and 4.2.1
>
>  Bugs:
>  * Shared library numbers corrected.
>  * Broken support for 32-bit AIX fixed.
>  * Misc minor fixes.
>
>  Speedups:
>  * Exact division (mpz_divexact) now falls back to plain division for large
>    operands.
>
>  Features:
>  * Support for some new systems.
>
>
>Changes between GMP version 4.1.4 and 4.2
>
>  Bugs:
>  * Minor bug fixes and code generalizations.
>  * Expanded and improved test suite.
>
>  Speedups:
>  * Many minor optimizations, too many to mention here.
>  * Division now always subquadratic.
>  * Computation of n-factorial much faster.
>  * Added basic x86-64 assembly code.
>  * Floating-point output is now subquadratic for all bases.
>  * FFT multiply code now about 25% faster.
>  * Toom3 multiply code faster.
>
>  Features:
>  * Much improved configure.
>  * Workarounds for many more compiler bugs.
>  * Temporary allocations are now made on the stack only if small.
>  * New systems supported: HPPA-2.0 gcc, IA-64 HP-UX, PowerPC-64 Darwin,
>    Sparc64 GNU/Linux.
>  * New i386 fat binaries, selecting optimised code at runtime (--enable-fat).
>  * New build option: --enable-profiling=instrument.
>  * New memory function: mp_get_memory_functions.
>  * New Mersenne Twister random numbers: gmp_randinit_mt, also now used for
>    gmp_randinit_default.
>  * New random functions: gmp_randinit_set, gmp_urandomb_ui, gmp_urandomm_ui.
>  * New integer functions: mpz_combit, mpz_rootrem.
>  * gmp_printf etc new type "M" for mp_limb_t.
>  * gmp_scanf and friends now accept C99 hex floats.
>  * Numeric input and output can now be in bases up to 62.
>  * Comparisons mpz_cmp_d, mpz_cmpabs_d, mpf_cmp_d recognise infinities.
>  * Conversions mpz_get_d, mpq_get_d, mpf_get_d truncate towards zero,
>    previously their behaviour was unspecified.
>  * Fixes for overflow issues with operands >= 2^31 bits.
>
>  Caveats:
>  * mpfr is gone, and will from now on be released only separately.  Please see
>    www.mpfr.org.
>
>
>Changes between GMP version 4.1.3 and 4.1.4
>
>* Bug fix to FFT multiplication code (crash for huge operands).
>* Bug fix to mpf_sub (miscomputation).
>* Support for powerpc64-gnu-linux.
>* Better support for AMD64 in 32-bit mode.
>* Upwardly binary compatible with 4.1.3, 4.1.2, 4.1.1, 4.1, 4.0.1, 4.0,
>  and 3.x versions.
>
>
>Changes between GMP version 4.1.2 and 4.1.3
>
>* Bug fix for FFT multiplication code (miscomputation).
>* Bug fix to K6 assembly code for gcd.
>* Bug fix to IA-64 assembly code for population count.
>* Portability improvements, most notably functional AMD64 support.
>* mpz_export allows NULL for countp parameter.
>* Many minor bug fixes.
>* mpz_export allows NULL for countp parameter.
>* Upwardly binary compatible with 4.1.2, 4.1.1, 4.1, 4.0.1, 4.0, and 3.x
>  versions.
>
>
>Changes between GMP version 4.1.1 and 4.1.2
>
>* Bug fixes.
>
>
>Changes between GMP version 4.1 and 4.1.1
>
>* Bug fixes.
>* New systems supported: NetBSD and OpenBSD sparc64.
>
>
>Changes between GMP version 4.0.1 and 4.1
>
>* Bug fixes.
>* Speed improvements.
>* Upwardly binary compatible with 4.0, 4.0.1, and 3.x versions.
>* Asymptotically fast conversion to/from strings (mpz, mpq, mpn levels), but
>  also major speed improvements for tiny operands.
>* mpn_get_str parameter restrictions relaxed.
>* Major speed improvments for HPPA 2.0 systems.
>* Major speed improvments for UltraSPARC systems.
>* Major speed improvments for IA-64 systems (but still sub-optimal code).
>* Extended test suite.
>* mpfr is back, with many bug fixes and portability improvements.
>* New function: mpz_ui_sub.
>* New functions: mpz_export, mpz_import.
>* Optimization for nth root functions (mpz_root, mpz_perfect_power_p).
>* Optimization for extended gcd (mpz_gcdext, mpz_invert, mpn_gcdext).
>* Generalized low-level number format, reserving a `nails' part of each
>  limb.  (Please note that this is really experimental; some functions
>  are likely to compute garbage when nails are enabled.)
>* Nails-enabled Alpha 21264 assembly code, allowing up to 75% better
>  performance.  (Use --enable-nails=4 to enable it.)
>
>
>Changes between GMP version 4.0 and 4.0.1
>
>* Bug fixes.
>
>
>Changes between GMP version 3.1.1 and 4.0
>
>* Bug fixes.
>* Speed improvements.
>* Upwardly binary compatible with 3.x versions.
>* New CPU support: IA-64, Pentium 4.
>* Improved CPU support: 21264, Cray vector systems.
>* Support for all MIPS ABIs: o32, n32, 64.
>* New systems supported: Darwin, SCO, Windows DLLs.
>* New divide-and-conquer square root algorithm.
>* New algorithms chapter in the manual.
>* New malloc reentrant temporary memory method.
>* New C++ class interface by Gerardo Ballabio (beta).
>* Revamped configure, featuring ABI selection.
>* Speed improvements for mpz_powm and mpz_powm_ui (mainly affecting small
>  operands).
>* mpz_perfect_power_p now properly recognizes 0, 1, and negative perfect
>  powers.
>* mpz_hamdist now supports negative operands.
>* mpz_jacobi now accepts non-positive denominators.
>* mpz_powm now supports negative exponents.
>* mpn_mul_1 operand overlap requirements relaxed.
>* Float input and output uses locale specific decimal point where available.
>* New gmp_printf, gmp_scanf and related functions.
>* New division functions: mpz_cdiv_q_2exp, mpz_cdiv_r_2exp, mpz_divexact_ui.
>* New divisibility tests: mpz_divisible_p, mpz_divisible_ui_p,
>  mpz_divisible_2exp_p, mpz_congruent_p, mpz_congruent_ui_p,
>  mpz_congruent_2exp_p.
>* New Fibonacci function: mpz_fib2_ui.
>* New Lucas number functions: mpz_lucnum_ui, mpz_lucnum2_ui.
>* Other new integer functions: mpz_cmp_d, mpz_cmpabs_d, mpz_get_d_2exp,
>  mpz_init2, mpz_kronecker, mpz_lcm_ui, mpz_realloc2.
>* New rational I/O: mpq_get_str, mpq_inp_str, mpq_out_str, mpq_set_str.
>* Other new rational functions: mpq_abs, mpq_cmp_si, mpq_div_2exp,
>  mpq_mul_2exp, mpq_set_f.
>* New float tests: mpf_integer_p, mpf_fits_sint_p, mpf_fits_slong_p,
>  mpf_fits_sshort_p, mpf_fits_uint_p, mpf_fits_ulong_p, mpf_fits_ushort_p.
>* Other new float functions: mpf_cmp_d, mpf_get_default_prec, mpf_get_si,
>  mpf_get_ui, mpf_get_d_2exp.
>* New random functions: gmp_randinit_default, gmp_randinit_lc_2exp_size.
>* New demo expression string parser (see demos/expr).
>* New preliminary perl interface (see demos/perl).
>* Tuned algorithm thresholds for many more CPUs.
>
>
>Changes between GMP version 3.1 and 3.1.1
>
>* Bug fixes for division (rare), mpf_get_str, FFT, and miscellaneous minor
>  things.
>
>
>Changes between GMP version 3.0 and 3.1
>
>* Bug fixes.
>* Improved `make check' running more tests.
>* Tuned algorithm cutoff points for many machines.  This will improve speed for
>  a lot of operations, in some cases by a large amount.
>* Major speed improvments: Alpha 21264.
>* Some speed improvments: Cray vector computers, AMD K6 and Athlon, Intel P5
>  and Pentium Pro/II/III.
>* The mpf_get_prec function now works as it did in GMP 2.
>* New utilities for auto-tuning and speed measuring.
>* Multiplication now optionally uses FFT for very large operands.  (To enable
>  it, pass --enable-fft to configure.)
>* Support for new systems: Solaris running on x86, FreeBSD 5, HP-UX 11, Cray
>  vector computers, Rhapsody, Nextstep/Openstep, MacOS.
>* Support for shared libraries on 32-bit HPPA.
>* New integer functions: mpz_mul_si, mpz_odd_p, mpz_even_p.
>* New Kronecker symbol functions: mpz_kronecker_si, mpz_kronecker_ui,
>  mpz_si_kronecker, mpz_ui_kronecker.
>* New rational functions: mpq_out_str, mpq_swap.
>* New float functions: mpf_swap.
>* New mpn functions: mpn_divexact_by3c, mpn_tdiv_qr.
>* New EXPERIMENTAL function layer for accurate floating-point arithmetic, mpfr.
>  To try it, pass --enable-mpfr to configure.  See the mpfr subdirectory for
>  more information; it is not documented in the main GMP manual.
>
>
>Changes between GMP version 3.0 and 3.0.1
>
>* Memory leaks in gmp_randinit and mpz_probab_prime_p fixed.
>* Documentation for gmp_randinit fixed.  Misc documentation errors fixed.
>
>
>Changes between GMP version 2.0 and 3.0
>
>* Source level compatibility with past releases (except mpn_gcd).
>* Bug fixes.
>* Much improved speed thanks to both host independent and host dependent
>  optimizations.
>* Switch to autoconf/automake/libtool.
>* Support for building libgmp as a shared library.
>* Multiplication and squaring using 3-way Toom-Cook.
>* Division using the Burnikel-Ziegler method.
>* New functions computing binomial coefficients: mpz_bin_ui, mpz_bin_uiui.
>* New function computing Fibonacci numbers: mpz_fib_ui.
>* New random number generators: mpf_urandomb, mpz_rrandomb, mpz_urandomb,
>  mpz_urandomm, gmp_randclear, gmp_randinit, gmp_randinit_lc_2exp,
>  gmp_randseed, gmp_randseed_ui.
>* New function for quickly extracting limbs: mpz_getlimbn.
>* New functions performing integer size tests: mpz_fits_sint_p,
>  mpz_fits_slong_p, mpz_fits_sshort_p, mpz_fits_uint_p, mpz_fits_ulong_p,
>  mpz_fits_ushort_p.
>* New mpf functions: mpf_ceil, mpf_floor, mpf_pow_ui, mpf_trunc.
>* New mpq function: mpq_set_d.
>* New mpz functions: mpz_addmul_ui, mpz_cmpabs, mpz_cmpabs_ui, mpz_lcm,
>  mpz_nextprime, mpz_perfect_power_p, mpz_remove, mpz_root, mpz_swap,
>  mpz_tdiv_ui, mpz_tstbit, mpz_xor.
>* New mpn function: mpn_divexact_by3.
>* New CPU support: DEC Alpha 21264, AMD K6 and Athlon, HPPA 2.0 and 64,
>  Intel Pentium Pro and Pentium-II/III, Sparc 64, PowerPC 64.
>* Almost 10 times faster mpz_invert and mpn_gcdext.
>* The interface of mpn_gcd has changed.
>* Better support for MIPS R4x000 and R5000 under Irix 6.
>* Improved support for SPARCv8 and SPARCv9 processors.
>
>
>Changes between GMP version 2.0 and 2.0.2
>
>* Many bug fixes.
>
>
>Changes between GMP version 1.3.2 and 2.0
>
>* Division routines in the mpz class have changed.  There are three classes of
>  functions, that rounds the quotient to -infinity, 0, and +infinity,
>  respectively.  The first class of functions have names that begin with
>  mpz_fdiv (f is short for floor), the second class' names begin with mpz_tdiv
>  (t is short for trunc), and the third class' names begin with mpz_cdiv (c is
>  short for ceil).
>
>  The old division routines beginning with mpz_m are similar to the new
>  mpz_fdiv, with the exception that some of the new functions return useful
>  values.
>
>  The old function names can still be used.  All the old functions names will
>  now do floor division, not trunc division as some of them used to.  This was
>  changed to make the functions more compatible with common mathematical
>  practice.
>
>  The mpz_mod and mpz_mod_ui functions now compute the mathematical mod
>  function.  I.e., the sign of the 2nd argument is ignored.
>
>* The mpq assignment functions do not canonicalize their results.  A new
>  function, mpq_canonicalize must be called by the user if the result is not
>  known to be canonical.
>* The mpn functions are now documented.  These functions are intended for
>  very time critical applications, or applications that need full control over
>  memory allocation.  Note that the mpn interface is irregular and hard to
>  use.
>* New functions for arbitrary precision floating point arithmetic.  Names
>  begin with `mpf_'.  Associated type mpf_t.
>* New and improved mpz functions, including much faster GCD, fast exact
>  division (mpz_divexact), bit scan (mpz_scan0 and mpz_scan1), and number
>  theoretical functions like Jacobi (mpz_jacobi) and multiplicative inverse
>  (mpz_invert).
>* New variable types (mpz_t and mpq_t) are available that makes syntax of
>  mpz and mpq calls nicer (no need for & before variables).  The MP_INT and
>  MP_RAT types are still available for compatibility.
>* Uses GNU configure.  This makes it possible to choose target architecture
>  and CPU variant, and to compile into a separate object directory.
>* Carefully optimized assembly for important inner loops.  Support for DEC
>  Alpha, Amd 29000, HPPA 1.0 and 1.1, Intel Pentium and generic x86, Intel
>  i960, Motorola MC68000, MC68020, MC88100, and MC88110, Motorola/IBM
>  PowerPC, National NS32000, IBM POWER, MIPS R3000, R4000, SPARCv7,
>  SuperSPARC, generic SPARCv8, and DEC VAX.  Some support also for ARM,
>  Clipper, IBM ROMP (RT), and Pyramid AP/XP.
>* Faster.  Thanks to the assembler code, new algorithms, and general tuning.
>  In particular, the speed on machines without GCC is improved.
>* Support for machines without alloca.
>* Now under the LGPL.
>
>INCOMPATIBILITIES BETWEEN GMP 1 AND GMP 2
>
>* mpq assignment functions do not canonicalize their results.
>* mpz division functions round differently.
>* mpz mod functions now really compute mod.
>* mpz_powm and mpz_powm_ui now really use mod for reduction.
>
>
>
>----------------
>Local variables:
>mode: text
>fill-column: 76
>End:
>Copyright 1991, 1996, 1999, 2000, 2007 Free Software Foundation, Inc.
>
>This file is part of the GNU MP Library.
>
>The GNU MP Library is free software; you can redistribute it and/or modify
>it under the terms of the GNU Lesser General Public License as published by
>the Free Software Foundation; either version 3 of the License, or (at your
>option) any later version.
>
>The GNU MP Library is distributed in the hope that it will be useful, but
>WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
>or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Lesser General Public
>License for more details.
>
>You should have received a copy of the GNU Lesser General Public License
>along with the GNU MP Library.  If not, see http://www.gnu.org/licenses/.
>
>
>
>
>
>
>			THE GNU MP LIBRARY
>
>
>GNU MP is a library for arbitrary precision arithmetic, operating on signed
>integers, rational numbers, and floating point numbers.  It has a rich set of
>functions, and the functions have a regular interface.
>
>GNU MP is designed to be as fast as possible, both for small operands and huge
>operands.  The speed is achieved by using fullwords as the basic arithmetic
>type, by using fast algorithms, with carefully optimized assembly code for the
>most common inner loops for lots of CPUs, and by a general emphasis on speed
>(instead of simplicity or elegance).
>
>GNU MP is believed to be faster than any other similar library.  Its advantage
>increases with operand sizes for certain operations, since GNU MP in many
>cases has asymptotically faster algorithms.
>
>GNU MP is free software and may be freely copied on the terms contained in the
>files COPYING.LIB and COPYING (most of GNU MP is under the former, some under
>the latter).
>
>
>
>			OVERVIEW OF GNU MP
>
>There are five classes of functions in GNU MP.
>
> 1. Signed integer arithmetic functions (mpz).  These functions are intended
>    to be easy to use, with their regular interface.  The associated type is
>    `mpz_t'.
>
> 2. Rational arithmetic functions (mpq).  For now, just a small set of
>    functions necessary for basic rational arithmetics.  The associated type
>    is `mpq_t'.
>
> 3. Floating-point arithmetic functions (mpf).  If the C type `double'
>    doesn't give enough precision for your application, declare your
>    variables as `mpf_t' instead, set the precision to any number desired,
>    and call the functions in the mpf class for the arithmetic operations.
>
> 4. Positive-integer, hard-to-use, very low overhead functions are in the
>    mpn class.  No memory management is performed.  The caller must ensure
>    enough space is available for the results.  The set of functions is not
>    regular, nor is the calling interface.  These functions accept input
>    arguments in the form of pairs consisting of a pointer to the least
>    significant word, and an integral size telling how many limbs (= words)
>    the pointer points to.
>
>    Almost all calculations, in the entire package, are made by calling these
>    low-level functions.
>
> 5. Berkeley MP compatible functions.
>
>    To use these functions, include the file "mp.h".  You can test if you are
>    using the GNU version by testing if the symbol __GNU_MP__ is defined.
>
>For more information on how to use GNU MP, please refer to the documentation.
>It is composed from the file doc/gmp.texi, and can be displayed on the screen
>or printed.  How to do that, as well how to build the library, is described in
>the INSTALL file in this directory.
>
>
>
>			REPORTING BUGS
>
>If you find a bug in the library, please make sure to tell us about it!
>
>You should first check the GNU MP web pages at http://gmplib.org/, under
>"Status of the current release".  There will be patches for all known serious
>bugs there.
>
>Report bugs to gmp-bugs@swox.com.  What information is needed in a useful bug
>report is described in the manual.  The same address can be used for suggesting
>modifications and enhancements.
>
>
>
>
>----------------
>Local variables:
>mode: text
>fill-column: 78
>End:
>±Á.`$..²ÁCOPYING;4803004e²ÁÐCOPYING
>                  GNU LESSER GENERAL PUBLIC LICENSE
>                       Version 2.1, February 1999
>
> Copyright (C) 1991, 1999 Free Software Foundation, Inc.
>     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
> Everyone is permitted to copy and distribute verbatim copies
> of this license document, but changing it is not allowed.
>
>[This is the first released version of the Lesser GPL.  It also counts
> as the successor of the GNU Library Public License, version 2, hence
> the version number 2.1.]
>
>                            Preamble
>
>  The licenses for most software are designed to take away your
>freedom to share and change it.  By contrast, the GNU General Public
>Licenses are intended to guarantee your freedom to share and change
>free software--to make sure the software is free for all its users.
>
>  This license, the Lesser General Public License, applies to some
>specially designated software packages--typically libraries--of the
>Free Software Foundation and other authors who decide to use it.  You
>can use it too, but we suggest you first think carefully about whether
>this license or the ordinary General Public License is the better
>strategy to use in any particular case, based on the explanations
>below.
>
>  When we speak of free software, we are referring to freedom of use,
>not price.  Our General Public Licenses are designed to make sure that
>you have the freedom to distribute copies of free software (and charge
>for this service if you wish); that you receive source code or can get
>it if you want it; that you can change the software and use pieces of
>it in new free programs; and that you are informed that you can do
>these things.
>
>  To protect your rights, we need to make restrictions that forbid
>distributors to deny you these rights or to ask you to surrender these
>rights.  These restrictions translate to certain responsibilities for
>you if you distribute copies of the library or if you modify it.
>
>  For example, if you distribute copies of the library, whether gratis
>or for a fee, you must give the recipients all the rights that we gave
>you.  You must make sure that they, too, receive or can get the source
>code.  If you link other code with the library, you must provide
>complete object files to the recipients, so that they can relink them
>with the library after making changes to the library and recompiling
>it.  And you must show them these terms so they know their rights.
>
>  We protect your rights with a two-step method: (1) we copyright the
>library, and (2) we offer you this license, which gives you legal
>permission to copy, distribute and/or modify the library.
>
>  To protect each distributor, we want to make it very clear that
>there is no warranty for the free library.  Also, if the library is
>modified by someone else and passed on, the recipients should know
>that what they have is not the original version, so that the original
>author's reputation will not be affected by problems that might be
>introduced by others.
>
>  Finally, software patents pose a constant threat to the existence of
>any free program.  We wish to make sure that a company cannot
>effectively restrict the users of a free program by obtaining a
>restrictive license from a patent holder.  Therefore, we insist that
>any patent license obtained for a version of the library must be
>consistent with the full freedom of use specified in this license.
>
>  Most GNU software, including some libraries, is covered by the
>ordinary GNU General Public License.  This license, the GNU Lesser
>General Public License, applies to certain designated libraries, and
>is quite different from the ordinary General Public License.  We use
>this license for certain libraries in order to permit linking those
>libraries into non-free programs.
>
>  When a program is linked with a library, whether statically or using
>a shared library, the combination of the two is legally speaking a
>combined work, a derivative of the original library.  The ordinary
>General Public License therefore permits such linking only if the
>entire combination fits its criteria of freedom.  The Lesser General
>Public License permits more lax criteria for linking other code with
>the library.
>
>  We call this license the "Lesser" General Public License because it
>does Less to protect the user's freedom than the ordinary General
>Public License.  It also provides other free software developers Less
>of an advantage over competing non-free programs.  These disadvantages
>are the reason we use the ordinary General Public License for many
>libraries.  However, the Lesser license provides advantages in certain
>special circumstances.
>
>  For example, on rare occasions, there may be a special need to
>encourage the widest possible use of a certain library, so that it
>becomes a de-facto standard.  To achieve this, non-free programs must
>be allowed to use the library.  A more frequent case is that a free
>library does the same job as widely used non-free libraries.  In this
>case, there is little to gain by limiting the free library to free
>software only, so we use the Lesser General Public License.
>
>  In other cases, permission to use a particular library in non-free
>programs enables a greater number of people to use a large body of
>free software.  For example, permission to use the GNU C Library in
>non-free programs enables many more people to use the whole GNU
>operating system, as well as its variant, the GNU/Linux operating
>system.
>
>  Although the Lesser General Public License is Less protective of the
>users' freedom, it does ensure that the user of a program that is
>linked with the Library has the freedom and the wherewithal to run
>that program using a modified version of the Library.
>
>  The precise terms and conditions for copying, distribution and
>modification follow.  Pay close attention to the difference between a
>"work based on the library" and a "work that uses the library".  The
>former contains code derived from the library, whereas the latter must
>be combined with the library in order to run.
>
>                  GNU LESSER GENERAL PUBLIC LICENSE
>   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
>
>  0. This License Agreement applies to any software library or other
>program which contains a notice placed by the copyright holder or
>other authorized party saying it may be distributed under the terms of
>this Lesser General Public License (also called "this License").
>Each licensee is addressed as "you".
>
>  A "library" means a collection of software functions and/or data
>prepared so as to be conveniently linked with application programs
>(which use some of those functions and data) to form executables.
>
>  The "Library", below, refers to any such software library or work
>which has been distributed under these terms.  A "work based on the
>Library" means either the Library or any derivative work under
>copyright law: that is to say, a work containing the Library or a
>portion of it, either verbatim or with modifications and/or translated
>straightforwardly into another language.  (Hereinafter, translation is
>included without limitation in the term "modification".)
>
>  "Source code" for a work means the preferred form of the work for
>making modifications to it.  For a library, complete source code means
>all the source code for all modules it contains, plus any associated
>interface definition files, plus the scripts used to control
>compilation and installation of the library.
>
>  Activities other than copying, distribution and modification are not
>covered by this License; they are outside its scope.  The act of
>running a program using the Library is not restricted, and output from
>such a program is covered only if its contents constitute a work based
>on the Library (independent of the use of the Library in a tool for
>writing it).  Whether that is true depends on what the Library does
>and what the program that uses the Library does.
>
>  1. You may copy and distribute verbatim copies of the Library's
>complete source code as you receive it, in any medium, provided that
>you conspicuously and appropriately publish on each copy an
>appropriate copyright notice and disclaimer of warranty; keep intact
>all the notices that refer to this License and to the absence of any
>warranty; and distribute a copy of this License along with the
>Library.
>
>  You may charge a fee for the physical act of transferring a copy,
>and you may at your option offer warranty protection in exchange for a
>fee.
>
>  2. You may modify your copy or copies of the Library or any portion
>of it, thus forming a work based on the Library, and copy and
>distribute such modifications or work under the terms of Section 1
>above, provided that you also meet all of these conditions:
>
>    a) The modified work must itself be a software library.
>
>    b) You must cause the files modified to carry prominent notices
>    stating that you changed the files and the date of any change.
>
>    c) You must cause the whole of the work to be licensed at no
>    charge to all third parties under the terms of this License.
>
>    d) If a facility in the modified Library refers to a function or a
>    table of data to be supplied by an application program that uses
>    the facility, other than as an argument passed when the facility
>    is invoked, then you must make a good faith effort to ensure that,
>    in the event an application does not supply such function or
>    table, the facility still operates, and performs whatever part of
>    its purpose remains meaningful.
>
>    (For example, a function in a library to compute square roots has
>    a purpose that is entirely well-defined independent of the
>    application.  Therefore, Subsection 2d requires that any
>    application-supplied function or table used by this function must
>    be optional: if the application does not supply it, the square
>    root function must still compute square roots.)
>
>These requirements apply to the modified work as a whole.  If
>identifiable sections of that work are not derived from the Library,
>and can be reasonably considered independent and separate works in
>themselves, then this License, and its terms, do not apply to those
>sections when you distribute them as separate works.  But when you
>distribute the same sections as part of a whole which is a work based
>on the Library, the distribution of the whole must be on the terms of
>this License, whose permissions for other licensees extend to the
>entire whole, and thus to each and every part regardless of who wrote
>it.
>
>Thus, it is not the intent of this section to claim rights or contest
>your rights to work written entirely by you; rather, the intent is to
>exercise the right to control the distribution of derivative or
>collective works based on the Library.
>
>In addition, mere aggregation of another work not based on the Library
>with the Library (or with a work based on the Library) on a volume of
>a storage or distribution medium does not bring the other work under
>the scope of this License.
>
>  3. You may opt to apply the terms of the ordinary GNU General Public
>License instead of this License to a given copy of the Library.  To do
>this, you must alter all the notices that refer to this License, so
>that they refer to the ordinary GNU General Public License, version 2,
>instead of to this License.  (If a newer version than version 2 of the
>ordinary GNU General Public License has appeared, then you can specify
>that version instead if you wish.)  Do not make any other change in
>these notices.
>
>  Once this change is made in a given copy, it is irreversible for
>that copy, so the ordinary GNU General Public License applies to all
>subsequent copies and derivative works made from that copy.
>
>  This option is useful when you wish to copy part of the code of
>the Library into a program that is not a library.
>
>  4. You may copy and distribute the Library (or a portion or
>derivative of it, under Section 2) in object code or executable form
>under the terms of Sections 1 and 2 above provided that you accompany
>it with the complete corresponding machine-readable source code, which
>must be distributed under the terms of Sections 1 and 2 above on a
>medium customarily used for software interchange.
>
>  If distribution of object code is made by offering access to copy
>from a designated place, then offering equivalent access to copy the
>source code from the same place satisfies the requirement to
>distribute the source code, even though third parties are not
>compelled to copy the source along with the object code.
>
>  5. A program that contains no derivative of any portion of the
>Library, but is designed to work with the Library by being compiled or
>linked with it, is called a "work that uses the Library".  Such a
>work, in isolation, is not a derivative work of the Library, and
>therefore falls outside the scope of this License.
>
>  However, linking a "work that uses the Library" with the Library
>creates an executable that is a derivative of the Library (because it
>contains portions of the Library), rather than a "work that uses the
>library".  The executable is therefore covered by this License.
>Section 6 states terms for distribution of such executables.
>
>  When a "work that uses the Library" uses material from a header file
>that is part of the Library, the object code for the work may be a
>derivative work of the Library even though the source code is not.
>Whether this is true is especially significant if the work can be
>linked without the Library, or if the work is itself a library.  The
>threshold for this to be true is not precisely defined by law.
>
>  If such an object file uses only numerical parameters, data
>structure layouts and accessors, and small macros and small inline
>functions (ten lines or less in length), then the use of the object
>file is unrestricted, regardless of whether it is legally a derivative
>work.  (Executables containing this object code plus portions of the
>Library will still fall under Section 6.)
>
>  Otherwise, if the work is a derivative of the Library, you may
>distribute the object code for the work under the terms of Section 6.
>Any executables containing that work also fall under Section 6,
>whether or not they are linked directly with the Library itself.
>
>  6. As an exception to the Sections above, you may also combine or
>link a "work that uses the Library" with the Library to produce a
>work containing portions of the Library, and distribute that work
>under terms of your choice, provided that the terms permit
>modification of the work for the customer's own use and reverse
>engineering for debugging such modifications.
>
>  You must give prominent notice with each copy of the work that the
>Library is used in it and that the Library and its use are covered by
>this License.  You must supply a copy of this License.  If the work
>during execution displays copyright notices, you must include the
>copyright notice for the Library among them, as well as a reference
>directing the user to the copy of this License.  Also, you must do one
>of these things:
>
>    a) Accompany the work with the complete corresponding
>    machine-readable source code for the Library including whatever
>    changes were used in the work (which must be distributed under
>    Sections 1 and 2 above); and, if the work is an executable linked
>    with the Library, with the complete machine-readable "work that
>    uses the Library", as object code and/or source code, so that the
>    user can modify the Library and then relink to produce a modified
>    executable containing the modified Library.  (It is understood
>    that the user who changes the contents of definitions files in the
>    Library will not necessarily be able to recompile the application
>    to use the modified definitions.)
>
>    b) Use a suitable shared library mechanism for linking with the
>    Library.  A suitable mechanism is one that (1) uses at run time a
>    copy of the library already present on the user's computer system,
>    rather than copying library functions into the executable, and (2)
>    will operate properly with a modified version of the library, if
>    the user installs one, as long as the modified version is
>    interface-compatible with the version that the work was made with.
>
>    c) Accompany the work with a written offer, valid for at least
>    three years, to give the same user the materials specified in
>    Subsection 6a, above, for a charge no more than the cost of
>    performing this distribution.
>
>    d) If distribution of the work is made by offering access to copy
>    from a designated place, offer equivalent access to copy the above
>    specified materials from the same place.
>
>    e) Verify that the user has already received a copy of these
>    materials or that you have already sent this user a copy.
>
>  For an executable, the required form of the "work that uses the
>Library" must include any data and utility programs needed for
>reproducing the executable from it.  However, as a special exception,
>the materials to be distributed need not include anything that is
>normally distributed (in either source or binary form) with the major
>components (compiler, kernel, and so on) of the operating system on
>which the executable runs, unless that component itself accompanies
>the executable.
>
>  It may happen that this requirement contradicts the license
>restrictions of other proprietary libraries that do not normally
>accompany the operating system.  Such a contradiction means you cannot
>use both them and the Library together in an executable that you
>distribute.
>
>  7. You may place library facilities that are a work based on the
>Library side-by-side in a single library together with other library
>facilities not covered by this License, and distribute such a combined
>library, provided that the separate distribution of the work based on
>the Library and of the other library facilities is otherwise
>permitted, and provided that you do these two things:
>
>    a) Accompany the combined library with a copy of the same work
>    based on the Library, uncombined with any other library
>    facilities.  This must be distributed under the terms of the
>    Sections above.
>
>    b) Give prominent notice with the combined library of the fact
>    that part of it is a work based on the Library, and explaining
>    where to find the accompanying uncombined form of the same work.
>
>  8. You may not copy, modify, sublicense, link with, or distribute
>the Library except as expressly provided under this License.  Any
>attempt otherwise to copy, modify, sublicense, link with, or
>distribute the Library is void, and will automatically terminate your
>rights under this License.  However, parties who have received copies,
>or rights, from you under this License will not have their licenses
>terminated so long as such parties remain in full compliance.
>
>  9. You are not required to accept this License, since you have not
>signed it.  However, nothing else grants you permission to modify or
>distribute the Library or its derivative works.  These actions are
>prohibited by law if you do not accept this License.  Therefore, by
>modifying or distributing the Library (or any work based on the
>Library), you indicate your acceptance of this License to do so, and
>all its terms and conditions for copying, distributing or modifying
>the Library or works based on it.
>
>  10. Each time you redistribute the Library (or any work based on the
>Library), the recipient automatically receives a license from the
>original licensor to copy, distribute, link with or modify the Library
>subject to these terms and conditions.  You may not impose any further
>restrictions on the recipients' exercise of the rights granted herein.
>You are not responsible for enforcing compliance by third parties with
>this License.
>
>  11. If, as a consequence of a court judgment or allegation of patent
>infringement or for any other reason (not limited to patent issues),
>conditions are imposed on you (whether by court order, agreement or
>otherwise) that contradict the conditions of this License, they do not
>excuse you from the conditions of this License.  If you cannot
>distribute so as to satisfy simultaneously your obligations under this
>License and any other pertinent obligations, then as a consequence you
>may not distribute the Library at all.  For example, if a patent
>license would not permit royalty-free redistribution of the Library by
>all those who receive copies directly or indirectly through you, then
>the only way you could satisfy both it and this License would be to
>refrain entirely from distribution of the Library.
>
>If any portion of this section is held invalid or unenforceable under
>any particular circumstance, the balance of the section is intended to
>apply, and the section as a whole is intended to apply in other
>circumstances.
>
>It is not the purpose of this section to induce you to infringe any
>patents or other property right claims or to contest validity of any
>such claims; this section has the sole purpose of protecting the
>integrity of the free software distribution system which is
>implemented by public license practices.  Many people have made
>generous contributions to the wide range of software distributed
>through that system in reliance on consistent application of that
>system; it is up to the author/donor to decide if he or she is willing
>to distribute software through any other system and a licensee cannot
>impose that choice.
>
>This section is intended to make thoroughly clear what is believed to
>be a consequence of the rest of this License.
>
>  12. If the distribution and/or use of the Library is restricted in
>certain countries either by patents or by copyrighted interfaces, the
>original copyright holder who places the Library under this License
>may add an explicit geographical distribution limitation excluding those
>countries, so that distribution is permitted only in or among
>countries not thus excluded.  In such case, this License incorporates
>the limitation as if written in the body of this License.
>
>  13. The Free Software Foundation may publish revised and/or new
>versions of the Lesser General Public License from time to time.
>Such new versions will be similar in spirit to the present version,
>but may differ in detail to address new problems or concerns.
>
>Each version is given a distinguishing version number.  If the Library
>specifies a version number of this License which applies to it and
>"any later version", you have the option of following the terms and
>conditions either of that version or of any later version published by
>the Free Software Foundation.  If the Library does not specify a
>license version number, you may choose any version ever published by
>the Free Software Foundation.
>
>  14. If you wish to incorporate parts of the Library into other free
>programs whose distribution conditions are incompatible with these,
>write to the author to ask for permission.  For software which is
>copyrighted by the Free Software Foundation, write to the Free
>Software Foundation; we sometimes make exceptions for this.  Our
>decision will be guided by the two goals of preserving the free status
>of all derivatives of our free software and of promoting the sharing
>and reuse of software generally.
>
>                            NO WARRANTY
>
>  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
>WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
>EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
>OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
>KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
>IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
>PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
>LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
>THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
>
>  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
>WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
>AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
>FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
>CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
>LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
>RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
>FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
>SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
>DAMAGES.
>
>                     END OF TERMS AND CONDITIONS
>³Á.`..µÁCOPYING.FDL3004e´ÁAUTHORS·ÁCOPYING.LGPL4803004e¶Á4COPYING.GPL¹Á README;4803004e03004e¸ÁCOPYING.Xiph¹Á\README/* FLAC - Free Lossless Audio Codec
> * Copyright (C) 2001,2002,2003,2004,2005,2006,2007  Josh Coalson
> *
> * This file is part the FLAC project.  FLAC is comprised of several
> * components distributed under difference licenses.  The codec libraries
> * are distributed under Xiph.Org's BSD-like license (see the file
> * COPYING.Xiph in this distribution).  All other programs, libraries, and
> * plugins are distributed under the GPL (see COPYING.GPL).  The documentation
> * is distributed under the Gnu FDL (see COPYING.FDL).  Each file in the
> * FLAC distribution contains at the top the terms under which it may be
> * distributed.
> *
> * Since this particular file is relevant to all components of FLAC,
> * it may be distributed under the Xiph.Org license, which is the least
> * restrictive of those mentioned above.  See the file COPYING.Xiph in this
> * distribution.
> */
>
>
>FLAC (http://flac.sourceforge.net/) is an Open Source lossless audio
>codec developed by Josh Coalson <jcoalson@users.sourceforge.net>.
>
>Other major contributors and their contributions:
>"Andrey Astafiev" <andrei@tvcell.ru>
>* Russian translation of the HTML documentation
>
>"Miroslav Lichvar" <lichvarm@phoenix.inf.upol.cz>
>* IA-32 assembly versions of several libFLAC routines
>
>"Brady Patterson" <bpat@users.sourceforge.net>
>* AIFF file support, PPC assembly versions of libFLAC routines
>
>"Daisuke Shimamura" <Daisuke_Shimamura@nifty.com>
>* i18n support in the XMMS plugin
>
>"X-Fixer" <x-fixer@narod.ru>
>* Configuration system, tag editing, and file info in the Winamp2 plugin
>
>"Matt Zimmerman" <mdz@debian.org>
>* Libtool/autoconf/automake make system, flac man page
>
>		GNU Free Documentation License
>		  Version 1.2, November 2002
>
>
> Copyright (C) 2000,2001,2002  Free Software Foundation, Inc.
>     51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
> Everyone is permitted to copy and distribute verbatim copies
> of this license document, but changing it is not allowed.
>
>
>0. PREAMBLE
>
>The purpose of this License is to make a manual, textbook, or other
>functional and useful document "free" in the sense of freedom: to
>assure everyone the effective freedom to copy and redistribute it,
>with or without modifying it, either commercially or noncommercially.
>Secondarily, this License preserves for the author and publisher a way
>to get credit for their work, while not being considered responsible
>for modifications made by others.
>
>This License is a kind of "copyleft", which means that derivative
>works of the document must themselves be free in the same sense.  It
>complements the GNU General Public License, which is a copyleft
>license designed for free software.
>
>We have designed this License in order to use it for manuals for free
>software, because free software needs free documentation: a free
>program should come with manuals providing the same freedoms that the
>software does.  But this License is not limited to software manuals;
>it can be used for any textual work, regardless of subject matter or
>whether it is published as a printed book.  We recommend this License
>principally for works whose purpose is instruction or reference.
>
>
>1. APPLICABILITY AND DEFINITIONS
>
>This License applies to any manual or other work, in any medium, that
>contains a notice placed by the copyright holder saying it can be
>distributed under the terms of this License.  Such a notice grants a
>world-wide, royalty-free license, unlimited in duration, to use that
>work under the conditions stated herein.  The "Document", below,
>refers to any such manual or work.  Any member of the public is a
>licensee, and is addressed as "you".  You accept the license if you
>copy, modify or distribute the work in a way requiring permission
>under copyright law.
>
>A "Modified Version" of the Document means any work containing the
>Document or a portion of it, either copied verbatim, or with
>modifications and/or translated into another language.
>
>A "Secondary Section" is a named appendix or a front-matter section of
>the Document that deals exclusively with the relationship of the
>publishers or authors of the Document to the Document's overall subject
>(or to related matters) and contains nothing that could fall directly
>within that overall subject.  (Thus, if the Document is in part a
>textbook of mathematics, a Secondary Section may not explain any
>mathematics.)  The relationship could be a matter of historical
>connection with the subject or with related matters, or of legal,
>commercial, philosophical, ethical or political position regarding
>them.
>
>The "Invariant Sections" are certain Secondary Sections whose titles
>are designated, as being those of Invariant Sections, in the notice
>that says that the Document is released under this License.  If a
>section does not fit the above definition of Secondary then it is not
>allowed to be designated as Invariant.  The Document may contain zero
>Invariant Sections.  If the Document does not identify any Invariant
>Sections then there are none.
>
>The "Cover Texts" are certain short passages of text that are listed,
>as Front-Cover Texts or Back-Cover Texts, in the notice that says that
>the Document is released under this License.  A Front-Cover Text may
>be at most 5 words, and a Back-Cover Text may be at most 25 words.
>
>A "Transparent" copy of the Document means a machine-readable copy,
>represented in a format whose specification is available to the
>general public, that is suitable for revising the document
>straightforwardly with generic text editors or (for images composed of
>pixels) generic paint programs or (for drawings) some widely available
>drawing editor, and that is suitable for input to text formatters or
>for automatic translation to a variety of formats suitable for input
>to text formatters.  A copy made in an otherwise Transparent file
>format whose markup, or absence of markup, has been arranged to thwart
>or discourage subsequent modification by readers is not Transparent.
>An image format is not Transparent if used for any substantial amount
>of text.  A copy that is not "Transparent" is called "Opaque".
>
>Examples of suitable formats for Transparent copies include plain
>ASCII without markup, Texinfo input format, LaTeX input format, SGML
>or XML using a publicly available DTD, and standard-conforming simple
>HTML, PostScript or PDF designed for human modification.  Examples of
>transparent image formats include PNG, XCF and JPG.  Opaque formats
>include proprietary formats that can be read and edited only by
>proprietary word processors, SGML or XML for which the DTD and/or
>processing tools are not generally available, and the
>machine-generated HTML, PostScript or PDF produced by some word
>processors for output purposes only.
>
>The "Title Page" means, for a printed book, the title page itself,
>plus such following pages as are needed to hold, legibly, the material
>this License requires to appear in the title page.  For works in
>formats which do not have any title page as such, "Title Page" means
>the text near the most prominent appearance of the work's title,
>preceding the beginning of the body of the text.
>
>A section "Entitled XYZ" means a named subunit of the Document whose
>title either is precisely XYZ or contains XYZ in parentheses following
>text that translates XYZ in another language.  (Here XYZ stands for a
>specific section name mentioned below, such as "Acknowledgements",
>"Dedications", "Endorsements", or "History".)  To "Preserve the Title"
>of such a section when you modify the Document means that it remains a
>section "Entitled XYZ" according to this definition.
>
>The Document may include Warranty Disclaimers next to the notice which
>states that this License applies to the Document.  These Warranty
>Disclaimers are considered to be included by reference in this
>License, but only as regards disclaiming warranties: any other
>implication that these Warranty Disclaimers may have is void and has
>no effect on the meaning of this License.
>
>
>2. VERBATIM COPYING
>
>You may copy and distribute the Document in any medium, either
>commercially or noncommercially, provided that this License, the
>copyright notices, and the license notice saying this License applies
>to the Document are reproduced in all copies, and that you add no other
>conditions whatsoever to those of this License.  You may not use
>technical measures to obstruct or control the reading or further
>copying of the copies you make or distribute.  However, you may accept
>compensation in exchange for copies.  If you distribute a large enough
>number of copies you must also follow the conditions in section 3.
>
>You may also lend copies, under the same conditions stated above, and
>you may publicly display copies.
>
>
>3. COPYING IN QUANTITY
>
>If you publish printed copies (or copies in media that commonly have
>printed covers) of the Document, numbering more than 100, and the
>Document's license notice requires Cover Texts, you must enclose the
>copies in covers that carry, clearly and legibly, all these Cover
>Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
>the back cover.  Both covers must also clearly and legibly identify
>you as the publisher of these copies.  The front cover must present
>the full title with all words of the title equally prominent and
>visible.  You may add other material on the covers in addition.
>Copying with changes limited to the covers, as long as they preserve
>the title of the Document and satisfy these conditions, can be treated
>as verbatim copying in other respects.
>
>If the required texts for either cover are too voluminous to fit
>legibly, you should put the first ones listed (as many as fit
>reasonably) on the actual cover, and continue the rest onto adjacent
>pages.
>
>If you publish or distribute Opaque copies of the Document numbering
>more than 100, you must either include a machine-readable Transparent
>copy along with each Opaque copy, or state in or with each Opaque copy
>a computer-network location from which the general network-using
>public has access to download using public-standard network protocols
>a complete Transparent copy of the Document, free of added material.
>If you use the latter option, you must take reasonably prudent steps,
>when you begin distribution of Opaque copies in quantity, to ensure
>that this Transparent copy will remain thus accessible at the stated
>location until at least one year after the last time you distribute an
>Opaque copy (directly or through your agents or retailers) of that
>edition to the public.
>
>It is requested, but not required, that you contact the authors of the
>Document well before redistributing any large number of copies, to give
>them a chance to provide you with an updated version of the Document.
>
>
>4. MODIFICATIONS
>
>You may copy and distribute a Modified Version of the Document under
>the conditions of sections 2 and 3 above, provided that you release
>the Modified Version under precisely this License, with the Modified
>Version filling the role of the Document, thus licensing distribution
>and modification of the Modified Version to whoever possesses a copy
>of it.  In addition, you must do these things in the Modified Version:
>
>A. Use in the Title Page (and on the covers, if any) a title distinct
>   from that of the Document, and from those of previous versions
>   (which should, if there were any, be listed in the History section
>   of the Document).  You may use the same title as a previous version
>   if the original publisher of that version gives permission.
>B. List on the Title Page, as authors, one or more persons or entities
>   responsible for authorship of the modifications in the Modified
>   Version, together with at least five of the principal authors of the
>   Document (all of its principal authors, if it has fewer than five),
>   unless they release you from this requirement.
>C. State on the Title page the name of the publisher of the
>   Modified Version, as the publisher.
>D. Preserve all the copyright notices of the Document.
>E. Add an appropriate copyright notice for your modifications
>   adjacent to the other copyright notices.
>F. Include, immediately after the copyright notices, a license notice
>   giving the public permission to use the Modified Version under the
>   terms of this License, in the form shown in the Addendum below.
>G. Preserve in that license notice the full lists of Invariant Sections
>   and required Cover Texts given in the Document's license notice.
>H. Include an unaltered copy of this License.
>I. Preserve the section Entitled "History", Preserve its Title, and add
>   to it an item stating at least the title, year, new authors, and
>   publisher of the Modified Version as given on the Title Page.  If
>   there is no section Entitled "History" in the Document, create one
>   stating the title, year, authors, and publisher of the Document as
>   given on its Title Page, then add an item describing the Modified
>   Version as stated in the previous sentence.
>J. Preserve the network location, if any, given in the Document for
>   public access to a Transparent copy of the Document, and likewise
>   the network locations given in the Document for previous versions
>   it was based on.  These may be placed in the "History" section.
>   You may omit a network location for a work that was published at
>   least four years before the Document itself, or if the original
>   publisher of the version it refers to gives permission.
>K. For any section Entitled "Acknowledgements" or "Dedications",
>   Preserve the Title of the section, and preserve in the section all
>   the substance and tone of each of the contributor acknowledgements
>   and/or dedications given therein.
>L. Preserve all the Invariant Sections of the Document,
>   unaltered in their text and in their titles.  Section numbers
>   or the equivalent are not considered part of the section titles.
>M. Delete any section Entitled "Endorsements".  Such a section
>   may not be included in the Modified Version.
>N. Do not retitle any existing section to be Entitled "Endorsements"
>   or to conflict in title with any Invariant Section.
>O. Preserve any Warranty Disclaimers.
>
>If the Modified Version includes new front-matter sections or
>appendices that qualify as Secondary Sections and contain no material
>copied from the Document, you may at your option designate some or all
>of these sections as invariant.  To do this, add their titles to the
>list of Invariant Sections in the Modified Version's license notice.
>These titles must be distinct from any other section titles.
>
>You may add a section Entitled "Endorsements", provided it contains
>nothing but endorsements of your Modified Version by various
>parties--for example, statements of peer review or that the text has
>been approved by an organization as the authoritative definition of a
>standard.
>
>You may add a passage of up to five words as a Front-Cover Text, and a
>passage of up to 25 words as a Back-Cover Text, to the end of the list
>of Cover Texts in the Modified Version.  Only one passage of
>Front-Cover Text and one of Back-Cover Text may be added by (or
>through arrangements made by) any one entity.  If the Document already
>includes a cover text for the same cover, previously added by you or
>by arrangement made by the same entity you are acting on behalf of,
>you may not add another; but you may replace the old one, on explicit
>permission from the previous publisher that added the old one.
>
>The author(s) and publisher(s) of the Document do not by this License
>give permission to use their names for publicity for or to assert or
>imply endorsement of any Modified Version.
>
>
>5. COMBINING DOCUMENTS
>
>You may combine the Document with other documents released under this
>License, under the terms defined in section 4 above for modified
>versions, provided that you include in the combination all of the
>Invariant Sections of all of the original documents, unmodified, and
>list them all as Invariant Sections of your combined work in its
>license notice, and that you preserve all their Warranty Disclaimers.
>
>The combined work need only contain one copy of this License, and
>multiple identical Invariant Sections may be replaced with a single
>copy.  If there are multiple Invariant Sections with the same name but
>different contents, make the title of each such section unique by
>adding at the end of it, in parentheses, the name of the original
>author or publisher of that section if known, or else a unique number.
>Make the same adjustment to the section titles in the list of
>Invariant Sections in the license notice of the combined work.
>
>In the combination, you must combine any sections Entitled "History"
>in the various original documents, forming one section Entitled
>"History"; likewise combine any sections Entitled "Acknowledgements",
>and any sections Entitled "Dedications".  You must delete all sections
>Entitled "Endorsements".
>
>
>6. COLLECTIONS OF DOCUMENTS
>
>You may make a collection consisting of the Document and other documents
>released under this License, and replace the individual copies of this
>License in the various documents with a single copy that is included in
>the collection, provided that you follow the rules of this License for
>verbatim copying of each of the documents in all other respects.
>
>You may extract a single document from such a collection, and distribute
>it individually under this License, provided you insert a copy of this
>License into the extracted document, and follow this License in all
>other respects regarding verbatim copying of that document.
>
>
>7. AGGREGATION WITH INDEPENDENT WORKS
>
>A compilation of the Document or its derivatives with other separate
>and independent documents or works, in or on a volume of a storage or
>distribution medium, is called an "aggregate" if the copyright
>resulting from the compilation is not used to limit the legal rights
>of the compilation's users beyond what the individual works permit.
>When the Document is included in an aggregate, this License does not
>apply to the other works in the aggregate which are not themselves
>derivative works of the Document.
>
>If the Cover Text requirement of section 3 is applicable to these
>copies of the Document, then if the Document is less than one half of
>the entire aggregate, the Document's Cover Texts may be placed on
>covers that bracket the Document within the aggregate, or the
>electronic equivalent of covers if the Document is in electronic form.
>Otherwise they must appear on printed covers that bracket the whole
>aggregate.
>
>
>8. TRANSLATION
>
>Translation is considered a kind of modification, so you may
>distribute translations of the Document under the terms of section 4.
>Replacing Invariant Sections with translations requires special
>permission from their copyright holders, but you may include
>translations of some or all Invariant Sections in addition to the
>original versions of these Invariant Sections.  You may include a
>translation of this License, and all the license notices in the
>Document, and any Warranty Disclaimers, provided that you also include
>the original English version of this License and the original versions
>of those notices and disclaimers.  In case of a disagreement between
>the translation and the original version of this License or a notice
>or disclaimer, the original version will prevail.
>
>If a section in the Document is Entitled "Acknowledgements",
>"Dedications", or "History", the requirement (section 4) to Preserve
>its Title (section 1) will typically require changing the actual
>title.
>
>
>9. TERMINATION
>
>You may not copy, modify, sublicense, or distribute the Document except
>as expressly provided for under this License.  Any other attempt to
>copy, modify, sublicense or distribute the Document is void, and will
>automatically terminate your rights under this License.  However,
>parties who have received copies, or rights, from you under this
>License will not have their licenses terminated so long as such
>parties remain in full compliance.
>
>
>10. FUTURE REVISIONS OF THIS LICENSE
>
>The Free Software Foundation may publish new, revised versions
>of the GNU Free Documentation License from time to time.  Such new
>versions will be similar in spirit to the present version, but may
>differ in detail to address new problems or concerns.  See
>http://www.gnu.org/copyleft/.
>
>Each version of the License is given a distinguishing version number.
>If the Document specifies that a particular numbered version of this
>License "or any later version" applies to it, you have the option of
>following the terms and conditions either of that specified version or
>of any later version that has been published (not as a draft) by the
>Free Software Foundation.  If the Document does not specify a version
>number of this License, you may choose any version ever published (not
>as a draft) by the Free Software Foundation.
>
>
>ADDENDUM: How to use this License for your documents
>
>To use this License in a document you have written, include a copy of
>the License in the document and put the following copyright and
>license notices just after the title page:
>
>    Copyright (c)  YEAR  YOUR NAME.
>    Permission is granted to copy, distribute and/or modify this document
>    under the terms of the GNU Free Documentation License, Version 1.2
>    or any later version published by the Free Software Foundation;
>    with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
>    A copy of the license is included in the section entitled "GNU
>    Free Documentation License".
>
>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
>replace the "with...Texts." line with this:
>
>    with the Invariant Sections being LIST THEIR TITLES, with the
>    Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
>
>If you have Invariant Sections without Cover Texts, or some other
>combination of the three, merge those two alternatives to suit the
>situation.
>
>If your document contains nontrivial examples of program code, we
>recommend releasing these examples in parallel under your choice of
>free software license, such as the GNU General Public License,
>to permit their use in free software.
>		    GNU GENERAL PUBLIC LICENSE
>		       Version 2, June 1991
>
> Copyright (C) 1989, 1991 Free Software Foundation, Inc.
> 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
> Everyone is permitted to copy and distribute verbatim copies
> of this license document, but changing it is not allowed.
>
>			    Preamble
>
>  The licenses for most software are designed to take away your
>freedom to share and change it.  By contrast, the GNU General Public
>License is intended to guarantee your freedom to share and change free
>software--to make sure the software is free for all its users.  This
>General Public License applies to most of the Free Software
>Foundation's software and to any other program whose authors commit to
>using it.  (Some other Free Software Foundation software is covered by
>the GNU Library General Public License instead.)  You can apply it to
>your programs, too.
>
>  When we speak of free software, we are referring to freedom, not
>price.  Our General Public Licenses are designed to make sure that you
>have the freedom to distribute copies of free software (and charge for
>this service if you wish), that you receive source code or can get it
>if you want it, that you can change the software or use pieces of it
>in new free programs; and that you know you can do these things.
>
>  To protect your rights, we need to make restrictions that forbid
>anyone to deny you these rights or to ask you to surrender the rights.
>These restrictions translate to certain responsibilities for you if you
>distribute copies of the software, or if you modify it.
>
>  For example, if you distribute copies of such a program, whether
>gratis or for a fee, you must give the recipients all the rights that
>you have.  You must make sure that they, too, receive or can get the
>source code.  And you must show them these terms so they know their
>rights.
>
>  We protect your rights with two steps: (1) copyright the software, and
>(2) offer you this license which gives you legal permission to copy,
>distribute and/or modify the software.
>
>  Also, for each author's protection and ours, we want to make certain
>that everyone understands that there is no warranty for this free
>software.  If the software is modified by someone else and passed on, we
>want its recipients to know that what they have is not the original, so
>that any problems introduced by others will not reflect on the original
>authors' reputations.
>
>  Finally, any free program is threatened constantly by software
>patents.  We wish to avoid the danger that redistributors of a free
>program will individually obtain patent licenses, in effect making the
>program proprietary.  To prevent this, we have made it clear that any
>patent must be licensed for everyone's free use or not licensed at all.
>
>  The precise terms and conditions for copying, distribution and
>modification follow.
>
>		    GNU GENERAL PUBLIC LICENSE
>   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
>
>  0. This License applies to any program or other work which contains
>a notice placed by the copyright holder saying it may be distributed
>under the terms of this General Public License.  The "Program", below,
>refers to any such program or work, and a "work based on the Program"
>means either the Program or any derivative work under copyright law:
>that is to say, a work containing the Program or a portion of it,
>either verbatim or with modifications and/or translated into another
>language.  (Hereinafter, translation is included without limitation in
>the term "modification".)  Each licensee is addressed as "you".
>
>Activities other than copying, distribution and modification are not
>covered by this License; they are outside its scope.  The act of
>running the Program is not restricted, and the output from the Program
>is covered only if its contents constitute a work based on the
>Program (independent of having been made by running the Program).
>Whether that is true depends on what the Program does.
>
>  1. You may copy and distribute verbatim copies of the Program's
>source code as you receive it, in any medium, provided that you
>conspicuously and appropriately publish on each copy an appropriate
>copyright notice and disclaimer of warranty; keep intact all the
>notices that refer to this License and to the absence of any warranty;
>and give any other recipients of the Program a copy of this License
>along with the Program.
>
>You may charge a fee for the physical act of transferring a copy, and
>you may at your option offer warranty protection in exchange for a fee.
>
>  2. You may modify your copy or copies of the Program or any portion
>of it, thus forming a work based on the Program, and copy and
>distribute such modifications or work under the terms of Section 1
>above, provided that you also meet all of these conditions:
>
>    a) You must cause the modified files to carry prominent notices
>    stating that you changed the files and the date of any change.
>
>    b) You must cause any work that you distribute or publish, that in
>    whole or in part contains or is derived from the Program or any
>    part thereof, to be licensed as a whole at no charge to all third
>    parties under the terms of this License.
>
>    c) If the modified program normally reads commands interactively
>    when run, you must cause it, when started running for such
>    interactive use in the most ordinary way, to print or display an
>    announcement including an appropriate copyright notice and a
>    notice that there is no warranty (or else, saying that you provide
>    a warranty) and that users may redistribute the program under
>    these conditions, and telling the user how to view a copy of this
>    License.  (Exception: if the Program itself is interactive but
>    does not normally print such an announcement, your work based on
>    the Program is not required to print an announcement.)
>
>These requirements apply to the modified work as a whole.  If
>identifiable sections of that work are not derived from the Program,
>and can be reasonably considered independent and separate works in
>themselves, then this License, and its terms, do not apply to those
>sections when you distribute them as separate works.  But when you
>distribute the same sections as part of a whole which is a work based
>on the Program, the distribution of the whole must be on the terms of
>this License, whose permissions for other licensees extend to the
>entire whole, and thus to each and every part regardless of who wrote it.
>
>Thus, it is not the intent of this section to claim rights or contest
>your rights to work written entirely by you; rather, the intent is to
>exercise the right to control the distribution of derivative or
>collective works based on the Program.
>
>In addition, mere aggregation of another work not based on the Program
>with the Program (or with a work based on the Program) on a volume of
>a storage or distribution medium does not bring the other work under
>the scope of this License.
>
>  3. You may copy and distribute the Program (or a work based on it,
>under Section 2) in object code or executable form under the terms of
>Sections 1 and 2 above provided that you also do one of the following:
>
>    a) Accompany it with the complete corresponding machine-readable
>    source code, which must be distributed under the terms of Sections
>    1 and 2 above on a medium customarily used for software interchange; or,
>
>    b) Accompany it with a written offer, valid for at least three
>    years, to give any third party, for a charge no more than your
>    cost of physically performing source distribution, a complete
>    machine-readable copy of the corresponding source code, to be
>    distributed under the terms of Sections 1 and 2 above on a medium
>    customarily used for software interchange; or,
>
>    c) Accompany it with the information you received as to the offer
>    to distribute corresponding source code.  (This alternative is
>    allowed only for noncommercial distribution and only if you
>    received the program in object code or executable form with such
>    an offer, in accord with Subsection b above.)
>
>The source code for a work means the preferred form of the work for
>making modifications to it.  For an executable work, complete source
>code means all the source code for all modules it contains, plus any
>associated interface definition files, plus the scripts used to
>control compilation and installation of the executable.  However, as a
>special exception, the source code distributed need not include
>anything that is normally distributed (in either source or binary
>form) with the major components (compiler, kernel, and so on) of the
>operating system on which the executable runs, unless that component
>itself accompanies the executable.
>
>If distribution of executable or object code is made by offering
>access to copy from a designated place, then offering equivalent
>access to copy the source code from the same place counts as
>distribution of the source code, even though third parties are not
>compelled to copy the source along with the object code.
>
>  4. You may not copy, modify, sublicense, or distribute the Program
>except as expressly provided under this License.  Any attempt
>otherwise to copy, modify, sublicense or distribute the Program is
>void, and will automatically terminate your rights under this License.
>However, parties who have received copies, or rights, from you under
>this License will not have their licenses terminated so long as such
>parties remain in full compliance.
>
>  5. You are not required to accept this License, since you have not
>signed it.  However, nothing else grants you permission to modify or
>distribute the Program or its derivative works.  These actions are
>prohibited by law if you do not accept this License.  Therefore, by
>modifying or distributing the Program (or any work based on the
>Program), you indicate your acceptance of this License to do so, and
>all its terms and conditions for copying, distributing or modifying
>the Program or works based on it.
>
>  6. Each time you redistribute the Program (or any work based on the
>Program), the recipient automatically receives a license from the
>original licensor to copy, distribute or modify the Program subject to
>these terms and conditions.  You may not impose any further
>restrictions on the recipients' exercise of the rights granted herein.
>You are not responsible for enforcing compliance by third parties to
>this License.
>
>  7. If, as a consequence of a court judgment or allegation of patent
>infringement or for any other reason (not limited to patent issues),
>conditions are imposed on you (whether by court order, agreement or
>otherwise) that contradict the conditions of this License, they do not
>excuse you from the conditions of this License.  If you cannot
>distribute so as to satisfy simultaneously your obligations under this
>License and any other pertinent obligations, then as a consequence you
>may not distribute the Program at all.  For example, if a patent
>license would not permit royalty-free redistribution of the Program by
>all those who receive copies directly or indirectly through you, then
>the only way you could satisfy both it and this License would be to
>refrain entirely from distribution of the Program.
>
>If any portion of this section is held invalid or unenforceable under
>any particular circumstance, the balance of the section is intended to
>apply and the section as a whole is intended to apply in other
>circumstances.
>
>It is not the purpose of this section to induce you to infringe any
>patents or other property right claims or to contest validity of any
>such claims; this section has the sole purpose of protecting the
>integrity of the free software distribution system, which is
>implemented by public license practices.  Many people have made
>generous contributions to the wide range of software distributed
>through that system in reliance on consistent application of that
>system; it is up to the author/donor to decide if he or she is willing
>to distribute software through any other system and a licensee cannot
>impose that choice.
>
>This section is intended to make thoroughly clear what is believed to
>be a consequence of the rest of this License.
>
>  8. If the distribution and/or use of the Program is restricted in
>certain countries either by patents or by copyrighted interfaces, the
>original copyright holder who places the Program under this License
>may add an explicit geographical distribution limitation excluding
>those countries, so that distribution is permitted only in or among
>countries not thus excluded.  In such case, this License incorporates
>the limitation as if written in the body of this License.
>
>  9. The Free Software Foundation may publish revised and/or new versions
>of the General Public License from time to time.  Such new versions will
>be similar in spirit to the present version, but may differ in detail to
>address new problems or concerns.
>
>Each version is given a distinguishing version number.  If the Program
>specifies a version number of this License which applies to it and "any
>later version", you have the option of following the terms and conditions
>either of that version or of any later version published by the Free
>Software Foundation.  If the Program does not specify a version number of
>this License, you may choose any version ever published by the Free Software
>Foundation.
>
>  10. If you wish to incorporate parts of the Program into other free
>programs whose distribution conditions are different, write to the author
>to ask for permission.  For software which is copyrighted by the Free
>Software Foundation, write to the Free Software Foundation; we sometimes
>make exceptions for this.  Our decision will be guided by the two goals
>of preserving the free status of all derivatives of our free software and
>of promoting the sharing and reuse of software generally.
>
>			    NO WARRANTY
>
>  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
>FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
>OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
>PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
>OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
>MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
>TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
>PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
>REPAIR OR CORRECTION.
>
>  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
>WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
>REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
>INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
>OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
>TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
>YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
>PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
>POSSIBILITY OF SUCH DAMAGES.
>
>		     END OF TERMS AND CONDITIONS
>
>	    How to Apply These Terms to Your New Programs
>
>  If you develop a new program, and you want it to be of the greatest
>possible use to the public, the best way to achieve this is to make it
>free software which everyone can redistribute and change under these terms.
>
>  To do so, attach the following notices to the program.  It is safest
>to attach them to the start of each source file to most effectively
>convey the exclusion of warranty; and each file should have at least
>the "copyright" line and a pointer to where the full notice is found.
>
>    <one line to give the program's name and a brief idea of what it does.>
>    Copyright (C) 19yy  <name of author>
>
>    This program is free software; you can redistribute it and/or modify
>    it under the terms of the GNU General Public License as published by
>    the Free Software Foundation; either version 2 of the License, or
>    (at your option) any later version.
>
>    This program is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>    GNU General Public License for more details.
>
>    You should have received a copy of the GNU General Public License
>    along with this program; if not, write to the Free Software
>    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
>
>
>Also add information on how to contact you by electronic and paper mail.
>
>If the program is interactive, make it output a short notice like this
>when it starts in an interactive mode:
>
>    Gnomovision version 69, Copyright (C) 19yy name of author
>    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
>    This is free software, and you are welcome to redistribute it
>    under certain conditions; type `show c' for details.
>
>The hypothetical commands `show w' and `show c' should show the appropriate
>parts of the General Public License.  Of course, the commands you use may
>be called something other than `show w' and `show c'; they could even be
>mouse-clicks or menu items--whatever suits your program.
>
>You should also get your employer (if you work as a programmer) or your
>school, if any, to sign a "copyright disclaimer" for the program, if
>necessary.  Here is a sample; alter the names:
>
>  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
>  `Gnomovision' (which makes passes at compilers) written by James Hacker.
>
>  <signature of Ty Coon>, 1 April 1989
>  Ty Coon, President of Vice
>
>This General Public License does not permit incorporating your program into
>proprietary programs.  If your program is a subroutine library, you may
>consider it more useful to permit linking proprietary applications with the
>library.  If this is what you want to do, use the GNU Library General
>Public License instead of this License.
>		  GNU LESSER GENERAL PUBLIC LICENSE
>		       Version 2.1, February 1999
>
> Copyright (C) 1991, 1999 Free Software Foundation, Inc.
> 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
> Everyone is permitted to copy and distribute verbatim copies
> of this license document, but changing it is not allowed.
>
>[This is the first released version of the Lesser GPL.  It also counts
> as the successor of the GNU Library Public License, version 2, hence
> the version number 2.1.]
>
>			    Preamble
>
>  The licenses for most software are designed to take away your
>freedom to share and change it.  By contrast, the GNU General Public
>Licenses are intended to guarantee your freedom to share and change
>free software--to make sure the software is free for all its users.
>
>  This license, the Lesser General Public License, applies to some
>specially designated software packages--typically libraries--of the
>Free Software Foundation and other authors who decide to use it.  You
>can use it too, but we suggest you first think carefully about whether
>this license or the ordinary General Public License is the better
>strategy to use in any particular case, based on the explanations below.
>
>  When we speak of free software, we are referring to freedom of use,
>not price.  Our General Public Licenses are designed to make sure that
>you have the freedom to distribute copies of free software (and charge
>for this service if you wish); that you receive source code or can get
>it if you want it; that you can change the software and use pieces of
>it in new free programs; and that you are informed that you can do
>these things.
>
>  To protect your rights, we need to make restrictions that forbid
>distributors to deny you these rights or to ask you to surrender these
>rights.  These restrictions translate to certain responsibilities for
>you if you distribute copies of the library or if you modify it.
>
>  For example, if you distribute copies of the library, whether gratis
>or for a fee, you must give the recipients all the rights that we gave
>you.  You must make sure that they, too, receive or can get the source
>code.  If you link other code with the library, you must provide
>complete object files to the recipients, so that they can relink them
>with the library after making changes to the library and recompiling
>it.  And you must show them these terms so they know their rights.
>
>  We protect your rights with a two-step method: (1) we copyright the
>library, and (2) we offer you this license, which gives you legal
>permission to copy, distribute and/or modify the library.
>
>  To protect each distributor, we want to make it very clear that
>there is no warranty for the free library.  Also, if the library is
>modified by someone else and passed on, the recipients should know
>that what they have is not the original version, so that the original
>author's reputation will not be affected by problems that might be
>introduced by others.
>
>  Finally, software patents pose a constant threat to the existence of
>any free program.  We wish to make sure that a company cannot
>effectively restrict the users of a free program by obtaining a
>restrictive license from a patent holder.  Therefore, we insist that
>any patent license obtained for a version of the library must be
>consistent with the full freedom of use specified in this license.
>
>  Most GNU software, including some libraries, is covered by the
>ordinary GNU General Public License.  This license, the GNU Lesser
>General Public License, applies to certain designated libraries, and
>is quite different from the ordinary General Public License.  We use
>this license for certain libraries in order to permit linking those
>libraries into non-free programs.
>
>  When a program is linked with a library, whether statically or using
>a shared library, the combination of the two is legally speaking a
>combined work, a derivative of the original library.  The ordinary
>General Public License therefore permits such linking only if the
>entire combination fits its criteria of freedom.  The Lesser General
>Public License permits more lax criteria for linking other code with
>the library.
>
>  We call this license the "Lesser" General Public License because it
>does Less to protect the user's freedom than the ordinary General
>Public License.  It also provides other free software developers Less
>of an advantage over competing non-free programs.  These disadvantages
>are the reason we use the ordinary General Public License for many
>libraries.  However, the Lesser license provides advantages in certain
>special circumstances.
>
>  For example, on rare occasions, there may be a special need to
>encourage the widest possible use of a certain library, so that it becomes
>a de-facto standard.  To achieve this, non-free programs must be
>allowed to use the library.  A more frequent case is that a free
>library does the same job as widely used non-free libraries.  In this
>case, there is little to gain by limiting the free library to free
>software only, so we use the Lesser General Public License.
>
>  In other cases, permission to use a particular library in non-free
>programs enables a greater number of people to use a large body of
>free software.  For example, permission to use the GNU C Library in
>non-free programs enables many more people to use the whole GNU
>operating system, as well as its variant, the GNU/Linux operating
>system.
>
>  Although the Lesser General Public License is Less protective of the
>users' freedom, it does ensure that the user of a program that is
>linked with the Library has the freedom and the wherewithal to run
>that program using a modified version of the Library.
>
>  The precise terms and conditions for copying, distribution and
>modification follow.  Pay close attention to the difference between a
>"work based on the library" and a "work that uses the library".  The
>former contains code derived from the library, whereas the latter must
>be combined with the library in order to run.
>
>		  GNU LESSER GENERAL PUBLIC LICENSE
>   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
>
>  0. This License Agreement applies to any software library or other
>program which contains a notice placed by the copyright holder or
>other authorized party saying it may be distributed under the terms of
>this Lesser General Public License (also called "this License").
>Each licensee is addressed as "you".
>
>  A "library" means a collection of software functions and/or data
>prepared so as to be conveniently linked with application programs
>(which use some of those functions and data) to form executables.
>
>  The "Library", below, refers to any such software library or work
>which has been distributed under these terms.  A "work based on the
>Library" means either the Library or any derivative work under
>copyright law: that is to say, a work containing the Library or a
>portion of it, either verbatim or with modifications and/or translated
>straightforwardly into another language.  (Hereinafter, translation is
>included without limitation in the term "modification".)
>
>  "Source code" for a work means the preferred form of the work for
>making modifications to it.  For a library, complete source code means
>all the source code for all modules it contains, plus any associated
>interface definition files, plus the scripts used to control compilation
>and installation of the library.
>
>  Activities other than copying, distribution and modification are not
>covered by this License; they are outside its scope.  The act of
>running a program using the Library is not restricted, and output from
>such a program is covered only if its contents constitute a work based
>on the Library (independent of the use of the Library in a tool for
>writing it).  Whether that is true depends on what the Library does
>and what the program that uses the Library does.
>  
>  1. You may copy and distribute verbatim copies of the Library's
>complete source code as you receive it, in any medium, provided that
>you conspicuously and appropriately publish on each copy an
>appropriate copyright notice and disclaimer of warranty; keep intact
>all the notices that refer to this License and to the absence of any
>warranty; and distribute a copy of this License along with the
>Library.
>
>  You may charge a fee for the physical act of transferring a copy,
>and you may at your option offer warranty protection in exchange for a
>fee.
>
>  2. You may modify your copy or copies of the Library or any portion
>of it, thus forming a work based on the Library, and copy and
>distribute such modifications or work under the terms of Section 1
>above, provided that you also meet all of these conditions:
>
>    a) The modified work must itself be a software library.
>
>    b) You must cause the files modified to carry prominent notices
>    stating that you changed the files and the date of any change.
>
>    c) You must cause the whole of the work to be licensed at no
>    charge to all third parties under the terms of this License.
>
>    d) If a facility in the modified Library refers to a function or a
>    table of data to be supplied by an application program that uses
>    the facility, other than as an argument passed when the facility
>    is invoked, then you must make a good faith effort to ensure that,
>    in the event an application does not supply such function or
>    table, the facility still operates, and performs whatever part of
>    its purpose remains meaningful.
>
>    (For example, a function in a library to compute square roots has
>    a purpose that is entirely well-defined independent of the
>    application.  Therefore, Subsection 2d requires that any
>    application-supplied function or table used by this function must
>    be optional: if the application does not supply it, the square
>    root function must still compute square roots.)
>
>These requirements apply to the modified work as a whole.  If
>identifiable sections of that work are not derived from the Library,
>and can be reasonably considered independent and separate works in
>themselves, then this License, and its terms, do not apply to those
>sections when you distribute them as separate works.  But when you
>distribute the same sections as part of a whole which is a work based
>on the Library, the distribution of the whole must be on the terms of
>this License, whose permissions for other licensees extend to the
>entire whole, and thus to each and every part regardless of who wrote
>it.
>
>Thus, it is not the intent of this section to claim rights or contest
>your rights to work written entirely by you; rather, the intent is to
>exercise the right to control the distribution of derivative or
>collective works based on the Library.
>
>In addition, mere aggregation of another work not based on the Library
>with the Library (or with a work based on the Library) on a volume of
>a storage or distribution medium does not bring the other work under
>the scope of this License.
>
>  3. You may opt to apply the terms of the ordinary GNU General Public
>License instead of this License to a given copy of the Library.  To do
>this, you must alter all the notices that refer to this License, so
>that they refer to the ordinary GNU General Public License, version 2,
>instead of to this License.  (If a newer version than version 2 of the
>ordinary GNU General Public License has appeared, then you can specify
>that version instead if you wish.)  Do not make any other change in
>these notices.
>
>  Once this change is made in a given copy, it is irreversible for
>that copy, so the ordinary GNU General Public License applies to all
>subsequent copies and derivative works made from that copy.
>
>  This option is useful when you wish to copy part of the code of
>the Library into a program that is not a library.
>
>  4. You may copy and distribute the Library (or a portion or
>derivative of it, under Section 2) in object code or executable form
>under the terms of Sections 1 and 2 above provided that you accompany
>it with the complete corresponding machine-readable source code, which
>must be distributed under the terms of Sections 1 and 2 above on a
>medium customarily used for software interchange.
>
>  If distribution of object code is made by offering access to copy
>from a designated place, then offering equivalent access to copy the
>source code from the same place satisfies the requirement to
>distribute the source code, even though third parties are not
>compelled to copy the source along with the object code.
>
>  5. A program that contains no derivative of any portion of the
>Library, but is designed to work with the Library by being compiled or
>linked with it, is called a "work that uses the Library".  Such a
>work, in isolation, is not a derivative work of the Library, and
>therefore falls outside the scope of this License.
>
>  However, linking a "work that uses the Library" with the Library
>creates an executable that is a derivative of the Library (because it
>contains portions of the Library), rather than a "work that uses the
>library".  The executable is therefore covered by this License.
>Section 6 states terms for distribution of such executables.
>
>  When a "work that uses the Library" uses material from a header file
>that is part of the Library, the object code for the work may be a
>derivative work of the Library even though the source code is not.
>Whether this is true is especially significant if the work can be
>linked without the Library, or if the work is itself a library.  The
>threshold for this to be true is not precisely defined by law.
>
>  If such an object file uses only numerical parameters, data
>structure layouts and accessors, and small macros and small inline
>functions (ten lines or less in length), then the use of the object
>file is unrestricted, regardless of whether it is legally a derivative
>work.  (Executables containing this object code plus portions of the
>Library will still fall under Section 6.)
>
>  Otherwise, if the work is a derivative of the Library, you may
>distribute the object code for the work under the terms of Section 6.
>Any executables containing that work also fall under Section 6,
>whether or not they are linked directly with the Library itself.
>
>  6. As an exception to the Sections above, you may also combine or
>link a "work that uses the Library" with the Library to produce a
>work containing portions of the Library, and distribute that work
>under terms of your choice, provided that the terms permit
>modification of the work for the customer's own use and reverse
>engineering for debugging such modifications.
>
>  You must give prominent notice with each copy of the work that the
>Library is used in it and that the Library and its use are covered by
>this License.  You must supply a copy of this License.  If the work
>during execution displays copyright notices, you must include the
>copyright notice for the Library among them, as well as a reference
>directing the user to the copy of this License.  Also, you must do one
>of these things:
>
>    a) Accompany the work with the complete corresponding
>    machine-readable source code for the Library including whatever
>    changes were used in the work (which must be distributed under
>    Sections 1 and 2 above); and, if the work is an executable linked
>    with the Library, with the complete machine-readable "work that
>    uses the Library", as object code and/or source code, so that the
>    user can modify the Library and then relink to produce a modified
>    executable containing the modified Library.  (It is understood
>    that the user who changes the contents of definitions files in the
>    Library will not necessarily be able to recompile the application
>    to use the modified definitions.)
>
>    b) Use a suitable shared library mechanism for linking with the
>    Library.  A suitable mechanism is one that (1) uses at run time a
>    copy of the library already present on the user's computer system,
>    rather than copying library functions into the executable, and (2)
>    will operate properly with a modified version of the library, if
>    the user installs one, as long as the modified version is
>    interface-compatible with the version that the work was made with.
>
>    c) Accompany the work with a written offer, valid for at
>    least three years, to give the same user the materials
>    specified in Subsection 6a, above, for a charge no more
>    than the cost of performing this distribution.
>
>    d) If distribution of the work is made by offering access to copy
>    from a designated place, offer equivalent access to copy the above
>    specified materials from the same place.
>
>    e) Verify that the user has already received a copy of these
>    materials or that you have already sent this user a copy.
>
>  For an executable, the required form of the "work that uses the
>Library" must include any data and utility programs needed for
>reproducing the executable from it.  However, as a special exception,
>the materials to be distributed need not include anything that is
>normally distributed (in either source or binary form) with the major
>components (compiler, kernel, and so on) of the operating system on
>which the executable runs, unless that component itself accompanies
>the executable.
>
>  It may happen that this requirement contradicts the license
>restrictions of other proprietary libraries that do not normally
>accompany the operating system.  Such a contradiction means you cannot
>use both them and the Library together in an executable that you
>distribute.
>
>  7. You may place library facilities that are a work based on the
>Library side-by-side in a single library together with other library
>facilities not covered by this License, and distribute such a combined
>library, provided that the separate distribution of the work based on
>the Library and of the other library facilities is otherwise
>permitted, and provided that you do these two things:
>
>    a) Accompany the combined library with a copy of the same work
>    based on the Library, uncombined with any other library
>    facilities.  This must be distributed under the terms of the
>    Sections above.
>
>    b) Give prominent notice with the combined library of the fact
>    that part of it is a work based on the Library, and explaining
>    where to find the accompanying uncombined form of the same work.
>
>  8. You may not copy, modify, sublicense, link with, or distribute
>the Library except as expressly provided under this License.  Any
>attempt otherwise to copy, modify, sublicense, link with, or
>distribute the Library is void, and will automatically terminate your
>rights under this License.  However, parties who have received copies,
>or rights, from you under this License will not have their licenses
>terminated so long as such parties remain in full compliance.
>
>  9. You are not required to accept this License, since you have not
>signed it.  However, nothing else grants you permission to modify or
>distribute the Library or its derivative works.  These actions are
>prohibited by law if you do not accept this License.  Therefore, by
>modifying or distributing the Library (or any work based on the
>Library), you indicate your acceptance of this License to do so, and
>all its terms and conditions for copying, distributing or modifying
>the Library or works based on it.
>
>  10. Each time you redistribute the Library (or any work based on the
>Library), the recipient automatically receives a license from the
>original licensor to copy, distribute, link with or modify the Library
>subject to these terms and conditions.  You may not impose any further
>restrictions on the recipients' exercise of the rights granted herein.
>You are not responsible for enforcing compliance by third parties with
>this License.
>
>  11. If, as a consequence of a court judgment or allegation of patent
>infringement or for any other reason (not limited to patent issues),
>conditions are imposed on you (whether by court order, agreement or
>otherwise) that contradict the conditions of this License, they do not
>excuse you from the conditions of this License.  If you cannot
>distribute so as to satisfy simultaneously your obligations under this
>License and any other pertinent obligations, then as a consequence you
>may not distribute the Library at all.  For example, if a patent
>license would not permit royalty-free redistribution of the Library by
>all those who receive copies directly or indirectly through you, then
>the only way you could satisfy both it and this License would be to
>refrain entirely from distribution of the Library.
>
>If any portion of this section is held invalid or unenforceable under any
>particular circumstance, the balance of the section is intended to apply,
>and the section as a whole is intended to apply in other circumstances.
>
>It is not the purpose of this section to induce you to infringe any
>patents or other property right claims or to contest validity of any
>such claims; this section has the sole purpose of protecting the
>integrity of the free software distribution system which is
>implemented by public license practices.  Many people have made
>generous contributions to the wide range of software distributed
>through that system in reliance on consistent application of that
>system; it is up to the author/donor to decide if he or she is willing
>to distribute software through any other system and a licensee cannot
>impose that choice.
>
>This section is intended to make thoroughly clear what is believed to
>be a consequence of the rest of this License.
>
>  12. If the distribution and/or use of the Library is restricted in
>certain countries either by patents or by copyrighted interfaces, the
>original copyright holder who places the Library under this License may add
>an explicit geographical distribution limitation excluding those countries,
>so that distribution is permitted only in or among countries not thus
>excluded.  In such case, this License incorporates the limitation as if
>written in the body of this License.
>
>  13. The Free Software Foundation may publish revised and/or new
>versions of the Lesser General Public License from time to time.
>Such new versions will be similar in spirit to the present version,
>but may differ in detail to address new problems or concerns.
>
>Each version is given a distinguishing version number.  If the Library
>specifies a version number of this License which applies to it and
>"any later version", you have the option of following the terms and
>conditions either of that version or of any later version published by
>the Free Software Foundation.  If the Library does not specify a
>license version number, you may choose any version ever published by
>the Free Software Foundation.
>
>  14. If you wish to incorporate parts of the Library into other free
>programs whose distribution conditions are incompatible with these,
>write to the author to ask for permission.  For software which is
>copyrighted by the Free Software Foundation, write to the Free
>Software Foundation; we sometimes make exceptions for this.  Our
>decision will be guided by the two goals of preserving the free status
>of all derivatives of our free software and of promoting the sharing
>and reuse of software generally.
>
>			    NO WARRANTY
>
>  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
>WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
>EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
>OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
>KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
>IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
>PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
>LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
>THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
>
>  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
>WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
>AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
>FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
>CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
>LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
>RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
>FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
>SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
>DAMAGES.
>
>		     END OF TERMS AND CONDITIONS
>
>           How to Apply These Terms to Your New Libraries
>
>  If you develop a new library, and you want it to be of the greatest
>possible use to the public, we recommend making it free software that
>everyone can redistribute and change.  You can do so by permitting
>redistribution under these terms (or, alternatively, under the terms of the
>ordinary General Public License).
>
>  To apply these terms, attach the following notices to the library.  It is
>safest to attach them to the start of each source file to most effectively
>convey the exclusion of warranty; and each file should have at least the
>"copyright" line and a pointer to where the full notice is found.
>
>    <one line to give the library's name and a brief idea of what it does.>
>    Copyright (C) <year>  <name of author>
>
>    This library is free software; you can redistribute it and/or
>    modify it under the terms of the GNU Lesser General Public
>    License as published by the Free Software Foundation; either
>    version 2.1 of the License, or (at your option) any later version.
>
>    This library is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
>    Lesser General Public License for more details.
>
>    You should have received a copy of the GNU Lesser General Public
>    License along with this library; if not, write to the Free Software
>    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
>
>Also add information on how to contact you by electronic and paper mail.
>
>You should also get your employer (if you work as a programmer) or your
>school, if any, to sign a "copyright disclaimer" for the library, if
>necessary.  Here is a sample; alter the names:
>
>  Yoyodyne, Inc., hereby disclaims all copyright interest in the
>  library `Frob' (a library for tweaking knobs) written by James Random Hacker.
>
>  <signature of Ty Coon>, 1 April 1990
>  Ty Coon, President of Vice
>
>That's all there is to it!
>
>
>Copyright (C) 2000,2001,2002,2003,2004,2005,2006,2007  Josh Coalson
>
>Redistribution and use in source and binary forms, with or without
>modification, are permitted provided that the following conditions
>are met:
>
>- Redistributions of source code must retain the above copyright
>notice, this list of conditions and the following disclaimer.
>
>- Redistributions in binary form must reproduce the above copyright
>notice, this list of conditions and the following disclaimer in the
>documentation and/or other materials provided with the distribution.
>
>- Neither the name of the Xiph.org Foundation nor the names of its
>contributors may be used to endorse or promote products derived from
>this software without specific prior written permission.
>
>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
>A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE FOUNDATION OR
>CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
>EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
>PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
>PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
>LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
>NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
>SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>/* FLAC - Free Lossless Audio Codec
> * Copyright (C) 2001,2002,2003,2004,2005,2006,2007  Josh Coalson
> *
> * This file is part the FLAC project.  FLAC is comprised of several
> * components distributed under difference licenses.  The codec libraries
> * are distributed under Xiph.Org's BSD-like license (see the file
> * COPYING.Xiph in this distribution).  All other programs, libraries, and
> * plugins are distributed under the LGPL or GPL (see COPYING.LGPL and
> * COPYING.GPL).  The documentation is distributed under the Gnu FDL (see
> * COPYING.FDL).  Each file in the FLAC distribution contains at the top the
> * terms under which it may be distributed.
> *
> * Since this particular file is relevant to all components of FLAC,
> * it may be distributed under the Xiph.Org license, which is the least
> * restrictive of those mentioned above.  See the file COPYING.Xiph in this
> * distribution.
> */
>
>
>FLAC (http://flac.sourceforge.net/) is an Open Source lossless audio
>codec developed by Josh Coalson.
>
>FLAC is comprised of
>  * `libFLAC', a library which implements reference encoders and
>    decoders for native FLAC and Ogg FLAC, and a metadata interface
>  * `libFLAC++', a C++ object wrapper library around libFLAC
>  * `flac', a command-line program for encoding and decoding files
>  * `metaflac', a command-line program for viewing and editing FLAC
>    metadata
>  * player plugins for XMMS and Winamp
>  * user and API documentation
>
>The libraries (libFLAC, libFLAC++) are
>licensed under Xiph.org's BSD-like license (see COPYING.Xiph).  All other
>programs and plugins are licensed under the GNU General Public License
>(see COPYING.GPL).  The documentation is licensed under the GNU Free
>Documentation License (see COPYING.FDL).
>
>
>===============================================================================
>FLAC - 1.2.1 - Contents
>===============================================================================
>
>- Introduction
>- Prerequisites
>- Note to embedded developers
>- Building in a GNU environment
>- Building with Makefile.lite
>- Building with MSVC
>- Building on Mac OS X
>
>
>===============================================================================
>Introduction
>===============================================================================
>
>This is the source release for the FLAC project.  See
>
>	doc/html/index.html
>
>for full documentation.
>
>A brief description of the directory tree:
>
>	doc/          the HTML documentation
>	include/      public include files for libFLAC and libFLAC++
>	man/          the man page for `flac'
>	src/          the source code and private headers
>	test/         the test scripts
>
>
>===============================================================================
>Prerequisites
>===============================================================================
>
>To build FLAC with support for Ogg FLAC you must have built and installed
>libogg according to the specific instructions below.  You must have
>libogg 1.1.2 or greater, or there will be seeking problems with Ogg FLAC.
>
>If you are building on x86 and want the assembly optimizations, you will
>need to have NASM >= 0.98.30 installed according to the specific instructions
>below.
>
>
>===============================================================================
>Note to embedded developers
>===============================================================================
>
>libFLAC has grown larger over time as more functionality has been
>included, but much of it may be unnecessary for a particular embedded
>implementation.  Unused parts may be pruned by some simple editing of
>configure.in and src/libFLAC/Makefile.am; the following dependency
>graph shows which modules may be pruned without breaking things
>further down:
>
>metadata.h
>	stream_decoder.h
>	format.h
>
>stream_encoder.h
>	stream_decoder.h
>	format.h
>
>stream_decoder.h
>	format.h
>
>In other words, for pure decoding applications, both the stream encoder
>and metadata editing interfaces can be safely removed.
>
>There is a section dedicated to embedded use in the libFLAC API
>HTML documentation (see doc/html/api/index.html).
>
>Also, there are several places in the libFLAC code with comments marked
>with "OPT:" where a #define can be changed to enable code that might be
>faster on a specific platform.  Experimenting with these can yield faster
>binaries.
>
>
>===============================================================================
>Building in a GNU environment
>===============================================================================
>
>FLAC uses autoconf and libtool for configuring and building.
>Better documentation for these will be forthcoming, but in
>general, this should work:
>
>./configure && make && make check && make install
>
>The 'make check' step is optional; omit it to skip all the tests,
>which can take several hours and use around 70-80 megs of disk space.
>Even though it will stop with an explicit message on any failure, it
>does print out a lot of stuff so you might want to capture the output
>to a file if you're having a problem.  Also, don't run 'make check'
>as root because it confuses some of the tests.
>
>NOTE: Despite our best efforts it's entirely possible to have
>problems when using older versions of autoconf, automake, or
>libtool.  If you have the latest versions and still can't get it
>to work, see the next section on Makefile.lite.
>
>There are a few FLAC-specific arguments you can give to
>`configure':
>
>--enable-debug : Builds everything with debug symbols and some
>extra (and more verbose) error checking.
>
>--disable-asm-optimizations : Disables the compilation of the
>assembly routines.  Many routines have assembly versions for
>speed and `configure' is pretty good about knowing what is
>supported, but you can use this option to build only from the
>C sources.  May be necessary for building on OS X (Intel)
>
>--enable-sse : If you are building for an x86 CPU that supports
>SSE instructions, you can enable some of the faster routines
>if your operating system also supports SSE instructions.  flac
>can tell if the CPU supports the instructions but currently has
>no way to test if the OS does, so if it does, you must pass
>this argument to configure to use the SSE routines.  If flac
>crashes when built with this option you will have to go back and
>configure without --enable-sse.  Note that
>--disable-asm-optimizations implies --disable-sse.
>
>--enable-local-xmms-plugin : Installs the FLAC XMMS plugin in
>$HOME/.xmms/Plugins, instead of the global XMMS plugin area
>(usually /usr/lib/xmms/Input).
>
>--with-ogg=
>--with-xmms-prefix=
>--with-libiconv-prefix=
>Use these if you have these packages but configure can't find them.
>
>If you want to build completely from scratch (i.e. starting with just
>configure.in and Makefile.am) you should be able to just run 'autogen.sh'
>but make sure and read the comments in that file first.
>
>
>===============================================================================
>Building with Makefile.lite
>===============================================================================
>
>There is a more lightweight build system for do-it-yourself-ers.
>It is also useful if configure isn't working, which may be the
>case since lately we've had some problems with different versions
>of automake and libtool.  The Makefile.lite system should work
>on GNU systems with few or no adjustments.
>
>From the top level just 'make -f Makefile.lite'.  You can
>specify zero or one optional target from 'release', 'debug',
>'test', or 'clean'.  The default is 'release'.  There is no
>'install' target but everything you need will end up in the
>obj/ directory.
>
>If you are not on an x86 system or you don't have nasm, you
>may have to change the DEFINES in src/libFLAC/Makefile.lite.  If
>you don't have nasm, remove -DFLAC__HAS_NASM.  If your target is
>not an x86, change -DFLAC__CPU_IA32 to -DFLAC__CPU_UNKNOWN.
>
>
>===============================================================================
>Building with MSVC
>===============================================================================
>
>There are .dsp projects and a master FLAC.dsw workspace to build all
>the libraries and executables with MSVC6.  There are also .vcproj
>projects and a master FLAC.sln solution to build all the libraries and
>executables with VC++ 2005.
>
>Prerequisite: you must have the Ogg libraries installed as described
>later.
>
>Prerequisite: you must have nasm installed, and nasmw.exe must be in
>your PATH, or the path to nasmw.exe must be added to the list of
>directories for executable files in the MSVC global options.
>
>MSVC6:
>To build everything, run Developer Studio, do File|Open Workspace,
>and open FLAC.dsw.  Select "Build | Set active configuration..."
>from the menu, then in the dialog, select "All - Win32 Release" (or
>Debug if you prefer).  Click "Ok" then hit F7 to build.
>
>VC++ 2005:
>To build everything, run Visual Studio, do File|Open and open FLAC.sln.
>From the dropdown in the toolbar, select "Release" instead of "Debug",
>then hit F7 to build.
>
>Either way, this will build all libraries both statically (e.g.
>obj\release\lib\libFLAC_static.lib) and as DLLs (e.g.
>obj\release\lib\libFLAC.dll), and it will build all binaries, statically
>linked (e.g. obj\release\bin\flac.exe).
>
>Everything will end up in the "obj" directory.  DLLs and .exe files
>are all that are needed and can be copied to an installation area and
>added to the PATH.  The plugins have to be copied to their appropriate
>place in the player area.  For Winamp2 this is <winamp2-dir>\Plugins.
>
>By default the code is configured with Ogg support.  Before building FLAC
>you will need to get the Ogg source distribution
>(see http://xiph.org/ogg/vorbis/download/), build ogg_static.lib (load and
>build win32\ogg_static.dsp), copy ogg_static.lib into FLAC's
>'obj\release\lib' directory, and copy the entire include\ogg tree into
>FLAC's 'include' directory (so that there is an 'ogg' directory in FLAC's
>'include' directory with the files ogg.h, os_types.h and config_types.h).
>
>If you want to build without Ogg support, instead edit all .dsp or
>.vcproj files and remove any occurrences of "/D FLAC__HAS_OGG".
>
>
>===============================================================================
>Building on Mac OS X
>===============================================================================
>
>If you have Fink or a recent version of OS X with the proper autotooles,
>the GNU flow above should work.  The Project Builder project has been
>deprecated but we are working on replacing it with an Xcode equivalent.
>ºÁ.`..½Á	ChangeLog803004e»ÁAUTHORS¼Á(COPYING¿Á
TODO;4803004e4e0¾ÁREADME¿ÁTODOCredits
>=======
>
>The following people have contributed to this program:
>
>  Adam Wozniak <adam@mudlist.eorbit.net>
>  - original CD-ROM TOC code
>
>  Ben Wong <cdindex@wongs.net>
>  - support for SGI Irix
>
>  Bert Vermeulen <bert@biot.com>
>  - improved endian support
>
>  Johnny Tevessen <j.tevessen@gmx.net>
>  - brought in autoconf support
>
>  Jukka Poikolainen <jukka.poikolainen@poikosoft.com>
>  - brought in Win32 TOC code
>
>  Marc E E van Woerkom <van.woerkom@netcologne.de>
>  - support for FreeBSD, NetBSD, OpenBSD, Solaris and Win32/Cygwin
>  - current maintainer
>
>  Mark A Mankins <raider@dnaco.net>
>  - improved Netscape support 
>
>  Rick Bradey <roundeye@bellsouth.net>
>  - support Linux 2.2 kernel and -l command line option
>
>  Robert Kaye <rob@emusic.com>
>  - hacked it together in the first place
>  - support for Win32/MS VC++
>  - coordination of the CD Index/MusicBrainz project
>  - move the CD Index over to MusicBrainz
>  - All the RDF/XML work in the client library
>
>  Stephen van Egmond <svanegmond@home.com>
>  - support for BeOS
>
>  Winston Chang <winston@stdout.org>
>  - support for Solaris
>
>  David W. Gray <david@thegray.com>
>  - cmd.dsp and added support for exporting the C++ interface in Win32
>
>  Alexey Zakhlestine <indy@mgupp.ru> 
>  - Supplied a patch compile this lib under BeOS
>
>  Brian Reichert <reichert@numachi.com>
>  - Supplied a patch compile this lib under FreeBSD-4.3
>
>  Erik Gavert <erik@jsdata.se>
>  - A small browser launch patch
>
>  Patrick Mauritz <oxygene@studentenbude.ath.cx>
>  - A patch to allow building mb_client from a different directory.
>
>  Chris Gray <cgray4@cs.mcgill.ca>
>  - A patch to keep the trm stuff from crashing.
>
>  Myers Carpenter <myers@maski.org> 
>  - Added track duration queries to queries.h
>  - Added all the python and debian support
>
>  Matthias Friedrich <mfriedrich@users.sourceforge.net>
>  - Provided a patch for fixing NetBSD cdrom TOC code
>
>  Sander van Zoest <sander@vanZoest.com>
>  - Wrote the perl bindings
>
>  Philippe Normand <sweafty@free.fr>
>  - Supplied a couple of minor patches to the new build system
>
>  Andreas Rottmann <a.rottmann@gmx.at>
>  - Improve build system and debian support
>
>  Tim Van Holder <tim.van.holder@pandora.be>
>  - Supplied a patch to fix some compile issues under cygwin
>
>  Clayton O'Neill <coneill@oneill.net>
>  - Improved the mp3 sanity checking code in the lib/bitzi/mp3.c
>
>  Juergen Kreileder <jk@blackdown.de>
>  - Supplied minimal patch for making sure that mb_client still works
>    when CDO_CHECK_TYPE is defined.
>
>  Martin Michlmayr <tbm@cyrius.com>
>  - Supplied a number of patches that fixed minor issues with the reintegrated python bindings
>
>  Ryan McCabe <ryan@numb.org>
>  - Supplied a patch to fix pointer issues in comhttpsocket.cpp and
>    comsocket.cpp on 64-bit architectures.
>  
>(please send change requests to rob@musicbrainz.org or maintainer)
>		  GNU LESSER GENERAL PUBLIC LICENSE
>		       Version 2.1, February 1999
>
> Copyright (C) 1991, 1999 Free Software Foundation, Inc.
>     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
> Everyone is permitted to copy and distribute verbatim copies
> of this license document, but changing it is not allowed.
>
>[This is the first released version of the Lesser GPL.  It also counts
> as the successor of the GNU Library Public License, version 2, hence
> the version number 2.1.]
>
>			    Preamble
>
>  The licenses for most software are designed to take away your
>freedom to share and change it.  By contrast, the GNU General Public
>Licenses are intended to guarantee your freedom to share and change
>free software--to make sure the software is free for all its users.
>
>  This license, the Lesser General Public License, applies to some
>specially designated software packages--typically libraries--of the
>Free Software Foundation and other authors who decide to use it.  You
>can use it too, but we suggest you first think carefully about whether
>this license or the ordinary General Public License is the better
>strategy to use in any particular case, based on the explanations below.
>
>  When we speak of free software, we are referring to freedom of use,
>not price.  Our General Public Licenses are designed to make sure that
>you have the freedom to distribute copies of free software (and charge
>for this service if you wish); that you receive source code or can get
>it if you want it; that you can change the software and use pieces of
>it in new free programs; and that you are informed that you can do
>these things.
>
>  To protect your rights, we need to make restrictions that forbid
>distributors to deny you these rights or to ask you to surrender these
>rights.  These restrictions translate to certain responsibilities for
>you if you distribute copies of the library or if you modify it.
>
>  For example, if you distribute copies of the library, whether gratis
>or for a fee, you must give the recipients all the rights that we gave
>you.  You must make sure that they, too, receive or can get the source
>code.  If you link other code with the library, you must provide
>complete object files to the recipients, so that they can relink them
>with the library after making changes to the library and recompiling
>it.  And you must show them these terms so they know their rights.
>
>  We protect your rights with a two-step method: (1) we copyright the
>library, and (2) we offer you this license, which gives you legal
>permission to copy, distribute and/or modify the library.
>
>  To protect each distributor, we want to make it very clear that
>there is no warranty for the free library.  Also, if the library is
>modified by someone else and passed on, the recipients should know
>that what they have is not the original version, so that the original
>author's reputation will not be affected by problems that might be
>introduced by others.
>
>  Finally, software patents pose a constant threat to the existence of
>any free program.  We wish to make sure that a company cannot
>effectively restrict the users of a free program by obtaining a
>restrictive license from a patent holder.  Therefore, we insist that
>any patent license obtained for a version of the library must be
>consistent with the full freedom of use specified in this license.
>
>  Most GNU software, including some libraries, is covered by the
>ordinary GNU General Public License.  This license, the GNU Lesser
>General Public License, applies to certain designated libraries, and
>is quite different from the ordinary General Public License.  We use
>this license for certain libraries in order to permit linking those
>libraries into non-free programs.
>
>  When a program is linked with a library, whether statically or using
>a shared library, the combination of the two is legally speaking a
>combined work, a derivative of the original library.  The ordinary
>General Public License therefore permits such linking only if the
>entire combination fits its criteria of freedom.  The Lesser General
>Public License permits more lax criteria for linking other code with
>the library.
>
>  We call this license the "Lesser" General Public License because it
>does Less to protect the user's freedom than the ordinary General
>Public License.  It also provides other free software developers Less
>of an advantage over competing non-free programs.  These disadvantages
>are the reason we use the ordinary General Public License for many
>libraries.  However, the Lesser license provides advantages in certain
>special circumstances.
>
>  For example, on rare occasions, there may be a special need to
>encourage the widest possible use of a certain library, so that it becomes
>a de-facto standard.  To achieve this, non-free programs must be
>allowed to use the library.  A more frequent case is that a free
>library does the same job as widely used non-free libraries.  In this
>case, there is little to gain by limiting the free library to free
>software only, so we use the Lesser General Public License.
>
>  In other cases, permission to use a particular library in non-free
>programs enables a greater number of people to use a large body of
>free software.  For example, permission to use the GNU C Library in
>non-free programs enables many more people to use the whole GNU
>operating system, as well as its variant, the GNU/Linux operating
>system.
>
>  Although the Lesser General Public License is Less protective of the
>users' freedom, it does ensure that the user of a program that is
>linked with the Library has the freedom and the wherewithal to run
>that program using a modified version of the Library.
>
>  The precise terms and conditions for copying, distribution and
>modification follow.  Pay close attention to the difference between a
>"work based on the library" and a "work that uses the library".  The
>former contains code derived from the library, whereas the latter must
>be combined with the library in order to run.
>
>		  GNU LESSER GENERAL PUBLIC LICENSE
>   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
>
>  0. This License Agreement applies to any software library or other
>program which contains a notice placed by the copyright holder or
>other authorized party saying it may be distributed under the terms of
>this Lesser General Public License (also called "this License").
>Each licensee is addressed as "you".
>
>  A "library" means a collection of software functions and/or data
>prepared so as to be conveniently linked with application programs
>(which use some of those functions and data) to form executables.
>
>  The "Library", below, refers to any such software library or work
>which has been distributed under these terms.  A "work based on the
>Library" means either the Library or any derivative work under
>copyright law: that is to say, a work containing the Library or a
>portion of it, either verbatim or with modifications and/or translated
>straightforwardly into another language.  (Hereinafter, translation is
>included without limitation in the term "modification".)
>
>  "Source code" for a work means the preferred form of the work for
>making modifications to it.  For a library, complete source code means
>all the source code for all modules it contains, plus any associated
>interface definition files, plus the scripts used to control compilation
>and installation of the library.
>
>  Activities other than copying, distribution and modification are not
>covered by this License; they are outside its scope.  The act of
>running a program using the Library is not restricted, and output from
>such a program is covered only if its contents constitute a work based
>on the Library (independent of the use of the Library in a tool for
>writing it).  Whether that is true depends on what the Library does
>and what the program that uses the Library does.
>  
>  1. You may copy and distribute verbatim copies of the Library's
>complete source code as you receive it, in any medium, provided that
>you conspicuously and appropriately publish on each copy an
>appropriate copyright notice and disclaimer of warranty; keep intact
>all the notices that refer to this License and to the absence of any
>warranty; and distribute a copy of this License along with the
>Library.
>
>  You may charge a fee for the physical act of transferring a copy,
>and you may at your option offer warranty protection in exchange for a
>fee.
>
>  2. You may modify your copy or copies of the Library or any portion
>of it, thus forming a work based on the Library, and copy and
>distribute such modifications or work under the terms of Section 1
>above, provided that you also meet all of these conditions:
>
>    a) The modified work must itself be a software library.
>
>    b) You must cause the files modified to carry prominent notices
>    stating that you changed the files and the date of any change.
>
>    c) You must cause the whole of the work to be licensed at no
>    charge to all third parties under the terms of this License.
>
>    d) If a facility in the modified Library refers to a function or a
>    table of data to be supplied by an application program that uses
>    the facility, other than as an argument passed when the facility
>    is invoked, then you must make a good faith effort to ensure that,
>    in the event an application does not supply such function or
>    table, the facility still operates, and performs whatever part of
>    its purpose remains meaningful.
>
>    (For example, a function in a library to compute square roots has
>    a purpose that is entirely well-defined independent of the
>    application.  Therefore, Subsection 2d requires that any
>    application-supplied function or table used by this function must
>    be optional: if the application does not supply it, the square
>    root function must still compute square roots.)
>
>These requirements apply to the modified work as a whole.  If
>identifiable sections of that work are not derived from the Library,
>and can be reasonably considered independent and separate works in
>themselves, then this License, and its terms, do not apply to those
>sections when you distribute them as separate works.  But when you
>distribute the same sections as part of a whole which is a work based
>on the Library, the distribution of the whole must be on the terms of
>this License, whose permissions for other licensees extend to the
>entire whole, and thus to each and every part regardless of who wrote
>it.
>
>Thus, it is not the intent of this section to claim rights or contest
>your rights to work written entirely by you; rather, the intent is to
>exercise the right to control the distribution of derivative or
>collective works based on the Library.
>
>In addition, mere aggregation of another work not based on the Library
>with the Library (or with a work based on the Library) on a volume of
>a storage or distribution medium does not bring the other work under
>the scope of this License.
>
>  3. You may opt to apply the terms of the ordinary GNU General Public
>License instead of this License to a given copy of the Library.  To do
>this, you must alter all the notices that refer to this License, so
>that they refer to the ordinary GNU General Public License, version 2,
>instead of to this License.  (If a newer version than version 2 of the
>ordinary GNU General Public License has appeared, then you can specify
>that version instead if you wish.)  Do not make any other change in
>these notices.
>
>  Once this change is made in a given copy, it is irreversible for
>that copy, so the ordinary GNU General Public License applies to all
>subsequent copies and derivative works made from that copy.
>
>  This option is useful when you wish to copy part of the code of
>the Library into a program that is not a library.
>
>  4. You may copy and distribute the Library (or a portion or
>derivative of it, under Section 2) in object code or executable form
>under the terms of Sections 1 and 2 above provided that you accompany
>it with the complete corresponding machine-readable source code, which
>must be distributed under the terms of Sections 1 and 2 above on a
>medium customarily used for software interchange.
>
>  If distribution of object code is made by offering access to copy
>from a designated place, then offering equivalent access to copy the
>source code from the same place satisfies the requirement to
>distribute the source code, even though third parties are not
>compelled to copy the source along with the object code.
>
>  5. A program that contains no derivative of any portion of the
>Library, but is designed to work with the Library by being compiled or
>linked with it, is called a "work that uses the Library".  Such a
>work, in isolation, is not a derivative work of the Library, and
>therefore falls outside the scope of this License.
>
>  However, linking a "work that uses the Library" with the Library
>creates an executable that is a derivative of the Library (because it
>contains portions of the Library), rather than a "work that uses the
>library".  The executable is therefore covered by this License.
>Section 6 states terms for distribution of such executables.
>
>  When a "work that uses the Library" uses material from a header file
>that is part of the Library, the object code for the work may be a
>derivative work of the Library even though the source code is not.
>Whether this is true is especially significant if the work can be
>linked without the Library, or if the work is itself a library.  The
>threshold for this to be true is not precisely defined by law.
>
>  If such an object file uses only numerical parameters, data
>structure layouts and accessors, and small macros and small inline
>functions (ten lines or less in length), then the use of the object
>file is unrestricted, regardless of whether it is legally a derivative
>work.  (Executables containing this object code plus portions of the
>Library will still fall under Section 6.)
>
>  Otherwise, if the work is a derivative of the Library, you may
>distribute the object code for the work under the terms of Section 6.
>Any executables containing that work also fall under Section 6,
>whether or not they are linked directly with the Library itself.
>
>  6. As an exception to the Sections above, you may also combine or
>link a "work that uses the Library" with the Library to produce a
>work containing portions of the Library, and distribute that work
>under terms of your choice, provided that the terms permit
>modification of the work for the customer's own use and reverse
>engineering for debugging such modifications.
>
>  You must give prominent notice with each copy of the work that the
>Library is used in it and that the Library and its use are covered by
>this License.  You must supply a copy of this License.  If the work
>during execution displays copyright notices, you must include the
>copyright notice for the Library among them, as well as a reference
>directing the user to the copy of this License.  Also, you must do one
>of these things:
>
>    a) Accompany the work with the complete corresponding
>    machine-readable source code for the Library including whatever
>    changes were used in the work (which must be distributed under
>    Sections 1 and 2 above); and, if the work is an executable linked
>    with the Library, with the complete machine-readable "work that
>    uses the Library", as object code and/or source code, so that the
>    user can modify the Library and then relink to produce a modified
>    executable containing the modified Library.  (It is understood
>    that the user who changes the contents of definitions files in the
>    Library will not necessarily be able to recompile the application
>    to use the modified definitions.)
>
>    b) Use a suitable shared library mechanism for linking with the
>    Library.  A suitable mechanism is one that (1) uses at run time a
>    copy of the library already present on the user's computer system,
>    rather than copying library functions into the executable, and (2)
>    will operate properly with a modified version of the library, if
>    the user installs one, as long as the modified version is
>    interface-compatible with the version that the work was made with.
>
>    c) Accompany the work with a written offer, valid for at
>    least three years, to give the same user the materials
>    specified in Subsection 6a, above, for a charge no more
>    than the cost of performing this distribution.
>
>    d) If distribution of the work is made by offering access to copy
>    from a designated place, offer equivalent access to copy the above
>    specified materials from the same place.
>
>    e) Verify that the user has already received a copy of these
>    materials or that you have already sent this user a copy.
>
>  For an executable, the required form of the "work that uses the
>Library" must include any data and utility programs needed for
>reproducing the executable from it.  However, as a special exception,
>the materials to be distributed need not include anything that is
>normally distributed (in either source or binary form) with the major
>components (compiler, kernel, and so on) of the operating system on
>which the executable runs, unless that component itself accompanies
>the executable.
>
>  It may happen that this requirement contradicts the license
>restrictions of other proprietary libraries that do not normally
>accompany the operating system.  Such a contradiction means you cannot
>use both them and the Library together in an executable that you
>distribute.
>
>  7. You may place library facilities that are a work based on the
>Library side-by-side in a single library together with other library
>facilities not covered by this License, and distribute such a combined
>library, provided that the separate distribution of the work based on
>the Library and of the other library facilities is otherwise
>permitted, and provided that you do these two things:
>
>    a) Accompany the combined library with a copy of the same work
>    based on the Library, uncombined with any other library
>    facilities.  This must be distributed under the terms of the
>    Sections above.
>
>    b) Give prominent notice with the combined library of the fact
>    that part of it is a work based on the Library, and explaining
>    where to find the accompanying uncombined form of the same work.
>
>  8. You may not copy, modify, sublicense, link with, or distribute
>the Library except as expressly provided under this License.  Any
>attempt otherwise to copy, modify, sublicense, link with, or
>distribute the Library is void, and will automatically terminate your
>rights under this License.  However, parties who have received copies,
>or rights, from you under this License will not have their licenses
>terminated so long as such parties remain in full compliance.
>
>  9. You are not required to accept this License, since you have not
>signed it.  However, nothing else grants you permission to modify or
>distribute the Library or its derivative works.  These actions are
>prohibited by law if you do not accept this License.  Therefore, by
>modifying or distributing the Library (or any work based on the
>Library), you indicate your acceptance of this License to do so, and
>all its terms and conditions for copying, distributing or modifying
>the Library or works based on it.
>
>  10. Each time you redistribute the Library (or any work based on the
>Library), the recipient automatically receives a license from the
>original licensor to copy, distribute, link with or modify the Library
>subject to these terms and conditions.  You may not impose any further
>restrictions on the recipients' exercise of the rights granted herein.
>You are not responsible for enforcing compliance by third parties with
>this License.
>
>  11. If, as a consequence of a court judgment or allegation of patent
>infringement or for any other reason (not limited to patent issues),
>conditions are imposed on you (whether by court order, agreement or
>otherwise) that contradict the conditions of this License, they do not
>excuse you from the conditions of this License.  If you cannot
>distribute so as to satisfy simultaneously your obligations under this
>License and any other pertinent obligations, then as a consequence you
>may not distribute the Library at all.  For example, if a patent
>license would not permit royalty-free redistribution of the Library by
>all those who receive copies directly or indirectly through you, then
>the only way you could satisfy both it and this License would be to
>refrain entirely from distribution of the Library.
>
>If any portion of this section is held invalid or unenforceable under any
>particular circumstance, the balance of the section is intended to apply,
>and the section as a whole is intended to apply in other circumstances.
>
>It is not the purpose of this section to induce you to infringe any
>patents or other property right claims or to contest validity of any
>such claims; this section has the sole purpose of protecting the
>integrity of the free software distribution system which is
>implemented by public license practices.  Many people have made
>generous contributions to the wide range of software distributed
>through that system in reliance on consistent application of that
>system; it is up to the author/donor to decide if he or she is willing
>to distribute software through any other system and a licensee cannot
>impose that choice.
>
>This section is intended to make thoroughly clear what is believed to
>be a consequence of the rest of this License.
>
>  12. If the distribution and/or use of the Library is restricted in
>certain countries either by patents or by copyrighted interfaces, the
>original copyright holder who places the Library under this License may add
>an explicit geographical distribution limitation excluding those countries,
>so that distribution is permitted only in or among countries not thus
>excluded.  In such case, this License incorporates the limitation as if
>written in the body of this License.
>
>  13. The Free Software Foundation may publish revised and/or new
>versions of the Lesser General Public License from time to time.
>Such new versions will be similar in spirit to the present version,
>but may differ in detail to address new problems or concerns.
>
>Each version is given a distinguishing version number.  If the Library
>specifies a version number of this License which applies to it and
>"any later version", you have the option of following the terms and
>conditions either of that version or of any later version published by
>the Free Software Foundation.  If the Library does not specify a
>license version number, you may choose any version ever published by
>the Free Software Foundation.
>
>  14. If you wish to incorporate parts of the Library into other free
>programs whose distribution conditions are incompatible with these,
>write to the author to ask for permission.  For software which is
>copyrighted by the Free Software Foundation, write to the Free
>Software Foundation; we sometimes make exceptions for this.  Our
>decision will be guided by the two goals of preserving the free status
>of all derivatives of our free software and of promoting the sharing
>and reuse of software generally.
>
>			    NO WARRANTY
>
>  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
>WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
>EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
>OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
>KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
>IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
>PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
>LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
>THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
>
>  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
>WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
>AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
>FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
>CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
>LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
>RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
>FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
>SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
>DAMAGES.
>
>		     END OF TERMS AND CONDITIONS
>
>           How to Apply These Terms to Your New Libraries
>
>  If you develop a new library, and you want it to be of the greatest
>possible use to the public, we recommend making it free software that
>everyone can redistribute and change.  You can do so by permitting
>redistribution under these terms (or, alternatively, under the terms of the
>ordinary General Public License).
>
>  To apply these terms, attach the following notices to the library.  It is
>safest to attach them to the start of each source file to most effectively
>convey the exclusion of warranty; and each file should have at least the
>"copyright" line and a pointer to where the full notice is found.
>
>    <one line to give the library's name and a brief idea of what it does.>
>    Copyright (C) <year>  <name of author>
>
>    This library is free software; you can redistribute it and/or
>    modify it under the terms of the GNU Lesser General Public
>    License as published by the Free Software Foundation; either
>    version 2.1 of the License, or (at your option) any later version.
>
>    This library is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
>    Lesser General Public License for more details.
>
>    You should have received a copy of the GNU Lesser General Public
>    License along with this library; if not, write to the Free Software
>    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
>
>Also add information on how to contact you by electronic and paper mail.
>
>You should also get your employer (if you work as a programmer) or your
>school, if any, to sign a "copyright disclaimer" for the library, if
>necessary.  Here is a sample; alter the names:
>
>  Yoyodyne, Inc., hereby disclaims all copyright interest in the
>  library `Frob' (a library for tweaking knobs) written by James Random Hacker.
>
>  <signature of Ty Coon>, 1 April 1990
>  Ty Coon, President of Vice
>
>That's all there is to it!
>
>
>Changes for libmusicbrainz 2.1.5
>-------------------------------------
>
>   - Fix for CD TOC reading on Solaris, thanks to Brian Cameron. (#2009)
>   - Fixed compilation on GCC 4.3. (http://bugs.debian.org/417352)
>   - Fix the patch for buffer overflows in rdfparse.c (2066)
>   - Support for Debian GNU/kFreeBSD in configure.in (patch from the
>     libmb package in Debian) 
>   - Patch to allow manually entering the CD TOC information, thanks
>     to sbooth. (#2193) 
>   - Fixed configure.in to work with newer versions of autoconf. (#1829)
>   - Buffer overflow in MBHttp::WriteToBuffer. (#2273) 
>   - Python bindings:
>      - No shebang in non-executable scripts.
>
>Changes for libmusicbrainz 2.1.4
>-------------------------------------
>
>   - Fixed buffer overflows in the RDF parsing and HTTP code. Patch by
>     Martin Schulze. (#2066)
>   - Fixed memory leaks in RDFExtract. (#2061)
>   - Fixed invalid memory access in the HTTP code. (#2033)
>
>Changes for libmusicbrainz 2.1.3
>-------------------------------------
>
>   - New queries for selecting album artists: 
>      - MBS_SelectAlbumArtist
>      - MBE_AlbumGetAlbumArtistName
>      - MBE_AlbumGetAlbumArtistSortName
>   - New query MBE_AlbumGetCdindexId
>   - Using size_t instead of int in networking code
>   - Little fixes in the API documentation 
>   - Python bindings:
>      - Using the new ctypes 0.9.9.x API, with support to fallback to
>        the old API if only an old ctypes version is installed
>      - Removed dependency on ctypes in setup.py
>
>Changes for libmusicbrainz 2.1.2
>-------------------------------------
>
>   - Since expat is now installed on most systems we removed our internal copy
>     and now rely on the system installed version.
>   - Juergen Kreileder Supplied minimal patch for making sure that mb_client still works
>     when CDO_CHECK_TYPE is defined
>   - Fixed a C++ style variable declaration inside the album.c C module
>   - On linux the cdrom drive is now opened in non-blocking mode
>   - Fixed bug #834541: Tagger setting track no. is 0 - possibly due to trm mixup?
>   - Added support for parsing AdvancedRelationship date. Also added new
>     getrels.c example program.
>   - Re-added the python bindings and changed the binding's version number to
>     match the version of this lib.
>   - Fixed bug # 1224562: libmusicbrainz fails to post large RDF. This fixes
>     problems looking up CDs with large numbers of tracks. (This was also  
>     bug # 725701 ignores blank tracks)
>
>   The included perl bindings had the following changes:
>      - Updated bindings to match up to 2.1.1
>      - Fixed int size cast warning
>      - Fixed #6431: unmatched bootstrap parameter
>      - Updated req for MusicBrainz::Queries to 0.07
>
>   The included python bindings had the following changes:
>      - Fixed #957393: Python Bindings type bug
>      - Fixed #1206514: Python bindings to select release not up-to-date
>
>Changes for libmusicbrainz 2.1.1
>-------------------------------------
>
>   - Return special TRMs for special conditions for TRM generation:
>     c457a4a8-b342-4ec9-8f13-b6bd26c0e400  -- Sigserver busy and overloaded
>     f9809ab1-2b0f-4d78-8862-fb425ade8ab9  -- Source file is too short to calculate TRM
>     7d154f52-b536-4fae-b58b-0666826c2bac  -- File is slience
>
>   - If the TRM signature server becomes overloaded, it will now start
>     returning HTTP 503 error codes and the TRM generator will catch that
>     and return the Sigserver busy TRM shown above.
>
>
>Changes for libmusicbrainz 2.1.0
>-------------------------------------
>
>   - moved the python bindings into a new seperate project
>   - rewrote the mp3 duration detection code to be more robust
>     by making it vastly easier. In the process the bitzi 
>     related code has been tossed. This should make the libary
>     smaller and the mp3 duration checking faster.
>   - Due to the bitzi code being removed, the SHA1 and Bitprint
>     related functions have been removed.
>   - Added query items for Release Dates/Countries, Amazon Asins and Amazon cover art URLs
>   - Move include files into include/musicbrainz so that the example
>     files will compile outside of the libmusicbrainz client 
>     source tree.
>
>Changes for libmusicbrainz 2.0.2
>-------------------------------------
>
>   - Added support for Mac OS X
>   - Improved build system
>   - Added build files for Visual Studio .NET (VC7)
>
>Changes for libmusicbrainz 2.0.1
>-------------------------------------
>   - Added patch for pkgconfig
>   - Threading handled correctly in python wrapper
>   - New perl bindings
>   - Had client use HTTP 1.0 rather than HTTP 1.1
>   
>
>Changes for libmusicbrainz 2.0.0
>-------------------------------------
>
>   - Removed some spurious C++ comments from mb_c.h
>   - Fixes and improvements to the python language bindings and tools
>   - Updated NetBSD cdrom reading code
>
>Changes for libmusicbrainz 2.0.0-pre4
>-------------------------------------
>
>   - Two new functions have been added:
>       mb_GetFragmentFromURL - Retrieve a fragment from a URI
>       mb_GetOrdinalFromList - Retrieve a list ordinal from a given list -- 
>                               this is sometimes needed to determine the 
>                               location of an item in a list. (e.g. a track in 
>                               an album in order to find the track number)
>   - The TRM code has been updated for TRM B#er.
>   - New queries have been added to queries.h in order to support the improved
>     FileLookupInterface.
>   - The client library now uses the mm-2.1 and mq-1.1 namespaces.
>   - The client library will now be referred to as libmusicbrainz
>
>Changes from version 1.1.0 to version 2.0.0-pre1
>------------------------------------------------
>
>   - Added authentication support
>   - Added new queries
>   - Added support for submitting client version to the server 
>     during TRM submits
>   - Updated client code for TRM B#er
>
>Changes from version 1.0.1 to version 1.1.0
>-------------------------------------------
>
>   - Fixed an OpenBSD 3.0 compile problem
>   - Updated libtool version to 1.4.2 in hopes to get it to build on OSX.
>   - Added MBQ_Quick queries to support the MB Tagger
>   - Fixed a bug in the TRM generation that caused different TRMs to be
>     generated for subsequent runs on the same file.
>
>Changes from version 1.0.0 to version 1.0.1
>-------------------------------------------
>
>   - Fixed the multi drive support under windows.
>   - Added support for setting the depth of a query via GET methods.
>   - Added SetDebug() function that allows the caller to set the
>     debug mode. In debug mode the library will print the server
>     URL, query and responses to stdout.
>   - Fixed a few crash bugs in the bitzi id3/mp3 metadata code
>   - Changed the bitzi plugin manager to not load plugins, in order
>     to avoid the unecessary dependency on dlopen/dlsym/dlclose.
>   - Removed a bunch of generates files from the CVS archive.
>                         MusicBrainz Client Library
>                         --------------------------
>
>Giving credit where credit is due
>---------------------------------
>
>If you write an application that uses the TRM interface (any functions that
>start with trm_ ) you need to include the following legal quip somewhere in
>your application -- preferrably the about box if your app has one:
>
>   Acoustic fingerprint technology provided by Relatable(TM),
>   Copyright (c) 2000-2, Relatable LLC, All rights reserved.
>
>Relatable has graciously given MusicBrainz a FREE license to use the TRM 
>technology with MusicBrainz. Please give credit to Relatable by including the
>above message into your applications.
>
>Documentation
>-------------
>
>Please refer to the online documentation for information on how to
>use this client library:
>
>        Online HOWTO: http://musicbrainz.org/client_howto.html
>         Online Docs: http://musicbrainz.org/docs/mb_client/index.html
>     Query Reference: http://users.musicbrainz.org/~luks/docs/mb_client-2.1.3/queries_8h.html
>  Function Reference: http://users.musicbrainz.org/~luks/docs/mb_client-2.1.3/mb__c_8h.html
>
>
>Configure notes:
>----------------
>
>If you want to use the client library with C++, give the following arguments to
>configure:
>
>    configure --enable-cpp-headers
>
>
>Link notes:
>-----------
>
>If you're compiling a C program and you're linking in the musicbrainz client
>library you will need to also link in the C++ standard library:
>
>   cc -o test_app test_app.c -lmusicbrainz -lm -lstdc++
>
>MusicBrainz Client Library TODO List:
>-------------------------------------
>
>1) This library has been compiled and tested under Linux, Windows, FreeBSD,
>   and Mac OS X.
>   It still needs to be compiled and tested under:
>     
>       Win32/cygwin, IRIX, NetBSD, OpenBSD
>
>ÀÁ.S ..ÁÁman1ÂÁman4ÅÐman8ÁÁ.ÀÁ,..9É dcraw.1.gz;4803004eeeeÎÁ
hunspell.1.gzíÅgpasswd.1.gzîÅnewgrp.1.gzïÅsg.1.gz9Éx
>dcraw.1.gzÂÁ.ÀÁ,..ÏÁ hunspell.4.gz;4803004eÏÁÈ
hunspell.4.gzÃÁ.`..ÅÁAUTHORS.myspelleÄÁAUTHORSÇÁCOPYING.LGPL004eÆÁCOPYINGÊÁREADME.myspelle3004eÈÁCOPYING.MPLÉÁREADMEÌÁlicense.hunspellËÁ0THANKSÍÁ license.myspell;4803004eÍÁlicense.myspellAuthor of Hunspell:
>NÃ©meth LÃ¡szlÃ³ nemeth (at) OpenOffice.org
>
>Hunspell based on OpenOffice.org's Myspell. MySpell's author:
>Kevin Hendricks kevin.hendricks (at) sympatico.ca
>Developer Credits:
>
>Special credit and thanks go to ispell's creator Geoff Kuenning.  
>Ispell affix compression code was used as the basis for the 
>affix code used in MySpell. Specifically Geoff's use of a 
>conds[] array that makes it easy to check if the conditions 
>required for a particular affix are present was very 
>ingenious! Kudos to Geoff.  Very nicely done.  
>BTW: ispell is available under a BSD style license 
>from Geoff Kuennings ispell website:
>http://www.cs.ucla.edu/ficus-members/geoff/ispell.html 
>
>
>Kevin Hendricks <kevin.hendricks@sympatico.ca> is the original 
>author and now maintainer of the MySpell codebase.  Recent 
>additions include ngram support, and related character maps 
>to help improve and create suggestions for very poorly 
>spelled words. 
>
>Please send any and all contributions or improvements
>to him or to dev@lingucomponent.openoffice.org.
>
>
>David Einstein (Deinst@world.std.com) developed an almost
>complete rewrite of MySpell for use by the Mozilla project.
>David and I are now working on parallel development tracks 
>to help our respective projects (Mozilla and OpenOffice.org) 
>and we will maintain full affix file and dictionary file 
>compatibility and work on merging our versions of MySpell 
>back into a single tree. David has been a significant help 
>in improving MySpell.
>
>
>Németh László <nemethl@gyorsposta.hu> is the author of 
>the Hungarian dictionary and he developed and contributed
>extensive changes to MySpell including ... 
>  * code to support compound words in MySpell
>  * fixed numerous problems with encoding case conversion tables. 
>  * designed/developed replacement tables to improve suggestions
>  * changed affix file parsing to trees to greatly speed loading
>  * removed the need for malloc/free pairs in suffix_check which
>      speeds up spell checking in suffix rich languages by 20%
>
>Davide Prina <davideprina@uahoo.com>, Giuseppe Modugno 
><gppe.modugno@libero.it>, Gianluca Turconi <luctur@comeg.it> 
>all from the it_IT OpenOffice.org team performed an 
>extremely  detailed code review of MySpell and generated
>fixes for bugs, leaks, and speedup improvements. 
>
>Simon Brouwer <simon.oo.o@xs4all.nl> for fixes and enhancements
>that have greatly improved MySpell auggestions
>  * n-gram suggestions for an initcap word have an init. cap. 
>  * fix for too many n-gram suggestions from specialized dictionary,
>  * fix for long suggestions rather than close ones in case of 
>      dictionaries with many compound words (kompuuter)
>  * optionally disabling split-word suggestions (controlled 
>      by NOSPLITSUGS line in affix file)
>
>
>Special Thanks to all others who have either contributed ideas or
>testing for MySpell
>
>
>Thanks,
>
>Kevin Hendricks
>kevin.hendricks@sympatico.ca
>GPL 2.0/LGPL 2.1/MPL 1.1 tri-license
>
>The contents of this software may be used under the terms of
>the GNU General Public License Version 2 or later (the "GPL"), or
>the GNU Lesser General Public License Version 2.1 or later (the "LGPL",
>see COPYING.LGPL) or (excepting the LGPLed GNU gettext library in the
>intl/ directory) the Mozilla Public License Version 1.1 or later
>(the "MPL", see COPYING.MPL).
>
>Software distributed under these licenses is distributed on an "AS IS" basis,
>WITHOUT WARRANTY OF ANY KIND, either express or implied. See the licences
>for the specific language governing rights and limitations under the licenses.
>
>                  GNU LESSER GENERAL PUBLIC LICENSE
>                       Version 2.1, February 1999
>
> Copyright (C) 1991, 1999 Free Software Foundation, Inc.
>     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
> Everyone is permitted to copy and distribute verbatim copies
> of this license document, but changing it is not allowed.
>
>[This is the first released version of the Lesser GPL.  It also counts
> as the successor of the GNU Library Public License, version 2, hence
> the version number 2.1.]
>
>                            Preamble
>
>  The licenses for most software are designed to take away your
>freedom to share and change it.  By contrast, the GNU General Public
>Licenses are intended to guarantee your freedom to share and change
>free software--to make sure the software is free for all its users.
>
>  This license, the Lesser General Public License, applies to some
>specially designated software packages--typically libraries--of the
>Free Software Foundation and other authors who decide to use it.  You
>can use it too, but we suggest you first think carefully about whether
>this license or the ordinary General Public License is the better
>strategy to use in any particular case, based on the explanations
>below.
>
>  When we speak of free software, we are referring to freedom of use,
>not price.  Our General Public Licenses are designed to make sure that
>you have the freedom to distribute copies of free software (and charge
>for this service if you wish); that you receive source code or can get
>it if you want it; that you can change the software and use pieces of
>it in new free programs; and that you are informed that you can do
>these things.
>
>  To protect your rights, we need to make restrictions that forbid
>distributors to deny you these rights or to ask you to surrender these
>rights.  These restrictions translate to certain responsibilities for
>you if you distribute copies of the library or if you modify it.
>
>  For example, if you distribute copies of the library, whether gratis
>or for a fee, you must give the recipients all the rights that we gave
>you.  You must make sure that they, too, receive or can get the source
>code.  If you link other code with the library, you must provide
>complete object files to the recipients, so that they can relink them
>with the library after making changes to the library and recompiling
>it.  And you must show them these terms so they know their rights.
>
>  We protect your rights with a two-step method: (1) we copyright the
>library, and (2) we offer you this license, which gives you legal
>permission to copy, distribute and/or modify the library.
>
>  To protect each distributor, we want to make it very clear that
>there is no warranty for the free library.  Also, if the library is
>modified by someone else and passed on, the recipients should know
>that what they have is not the original version, so that the original
>author's reputation will not be affected by problems that might be
>introduced by others.
>^L
>  Finally, software patents pose a constant threat to the existence of
>any free program.  We wish to make sure that a company cannot
>effectively restrict the users of a free program by obtaining a
>restrictive license from a patent holder.  Therefore, we insist that
>any patent license obtained for a version of the library must be
>consistent with the full freedom of use specified in this license.
>
>  Most GNU software, including some libraries, is covered by the
>ordinary GNU General Public License.  This license, the GNU Lesser
>General Public License, applies to certain designated libraries, and
>is quite different from the ordinary General Public License.  We use
>this license for certain libraries in order to permit linking those
>libraries into non-free programs.
>
>  When a program is linked with a library, whether statically or using
>a shared library, the combination of the two is legally speaking a
>combined work, a derivative of the original library.  The ordinary
>General Public License therefore permits such linking only if the
>entire combination fits its criteria of freedom.  The Lesser General
>Public License permits more lax criteria for linking other code with
>the library.
>
>  We call this license the "Lesser" General Public License because it
>does Less to protect the user's freedom than the ordinary General
>Public License.  It also provides other free software developers Less
>of an advantage over competing non-free programs.  These disadvantages
>are the reason we use the ordinary General Public License for many
>libraries.  However, the Lesser license provides advantages in certain
>special circumstances.
>
>  For example, on rare occasions, there may be a special need to
>encourage the widest possible use of a certain library, so that it
>becomes
>a de-facto standard.  To achieve this, non-free programs must be
>allowed to use the library.  A more frequent case is that a free
>library does the same job as widely used non-free libraries.  In this
>case, there is little to gain by limiting the free library to free
>software only, so we use the Lesser General Public License.
>
>  In other cases, permission to use a particular library in non-free
>programs enables a greater number of people to use a large body of
>free software.  For example, permission to use the GNU C Library in
>non-free programs enables many more people to use the whole GNU
>operating system, as well as its variant, the GNU/Linux operating
>system.
>
>  Although the Lesser General Public License is Less protective of the
>users' freedom, it does ensure that the user of a program that is
>linked with the Library has the freedom and the wherewithal to run
>that program using a modified version of the Library.
>
>  The precise terms and conditions for copying, distribution and
>modification follow.  Pay close attention to the difference between a
>"work based on the library" and a "work that uses the library".  The
>former contains code derived from the library, whereas the latter must
>be combined with the library in order to run.
>^L
>                  GNU LESSER GENERAL PUBLIC LICENSE
>   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
>
>  0. This License Agreement applies to any software library or other
>program which contains a notice placed by the copyright holder or
>other authorized party saying it may be distributed under the terms of
>this Lesser General Public License (also called "this License").
>Each licensee is addressed as "you".
>
>  A "library" means a collection of software functions and/or data
>prepared so as to be conveniently linked with application programs
>(which use some of those functions and data) to form executables.
>
>  The "Library", below, refers to any such software library or work
>which has been distributed under these terms.  A "work based on the
>Library" means either the Library or any derivative work under
>copyright law: that is to say, a work containing the Library or a
>portion of it, either verbatim or with modifications and/or translated
>straightforwardly into another language.  (Hereinafter, translation is
>included without limitation in the term "modification".)
>
>  "Source code" for a work means the preferred form of the work for
>making modifications to it.  For a library, complete source code means
>all the source code for all modules it contains, plus any associated
>interface definition files, plus the scripts used to control
>compilation
>and installation of the library.
>
>  Activities other than copying, distribution and modification are not
>covered by this License; they are outside its scope.  The act of
>running a program using the Library is not restricted, and output from
>such a program is covered only if its contents constitute a work based
>on the Library (independent of the use of the Library in a tool for
>writing it).  Whether that is true depends on what the Library does
>and what the program that uses the Library does.
>
>  1. You may copy and distribute verbatim copies of the Library's
>complete source code as you receive it, in any medium, provided that
>you conspicuously and appropriately publish on each copy an
>appropriate copyright notice and disclaimer of warranty; keep intact
>all the notices that refer to this License and to the absence of any
>warranty; and distribute a copy of this License along with the
>Library.
>
>  You may charge a fee for the physical act of transferring a copy,
>and you may at your option offer warranty protection in exchange for a
>fee.
>
>  2. You may modify your copy or copies of the Library or any portion
>of it, thus forming a work based on the Library, and copy and
>distribute such modifications or work under the terms of Section 1
>above, provided that you also meet all of these conditions:
>
>    a) The modified work must itself be a software library.
>
>    b) You must cause the files modified to carry prominent notices
>    stating that you changed the files and the date of any change.
>
>    c) You must cause the whole of the work to be licensed at no
>    charge to all third parties under the terms of this License.
>
>    d) If a facility in the modified Library refers to a function or a
>    table of data to be supplied by an application program that uses
>    the facility, other than as an argument passed when the facility
>    is invoked, then you must make a good faith effort to ensure that,
>    in the event an application does not supply such function or
>    table, the facility still operates, and performs whatever part of
>    its purpose remains meaningful.
>
>    (For example, a function in a library to compute square roots has
>    a purpose that is entirely well-defined independent of the
>    application.  Therefore, Subsection 2d requires that any
>    application-supplied function or table used by this function must
>    be optional: if the application does not supply it, the square
>    root function must still compute square roots.)
>
>These requirements apply to the modified work as a whole.  If
>identifiable sections of that work are not derived from the Library,
>and can be reasonably considered independent and separate works in
>themselves, then this License, and its terms, do not apply to those
>sections when you distribute them as separate works.  But when you
>distribute the same sections as part of a whole which is a work based
>on the Library, the distribution of the whole must be on the terms of
>this License, whose permissions for other licensees extend to the
>entire whole, and thus to each and every part regardless of who wrote
>it.
>
>Thus, it is not the intent of this section to claim rights or contest
>your rights to work written entirely by you; rather, the intent is to
>exercise the right to control the distribution of derivative or
>collective works based on the Library.
>
>In addition, mere aggregation of another work not based on the Library
>with the Library (or with a work based on the Library) on a volume of
>a storage or distribution medium does not bring the other work under
>the scope of this License.
>
>  3. You may opt to apply the terms of the ordinary GNU General Public
>License instead of this License to a given copy of the Library.  To do
>this, you must alter all the notices that refer to this License, so
>that they refer to the ordinary GNU General Public License, version 2,
>instead of to this License.  (If a newer version than version 2 of the
>ordinary GNU General Public License has appeared, then you can specify
>that version instead if you wish.)  Do not make any other change in
>these notices.
>^L
>  Once this change is made in a given copy, it is irreversible for
>that copy, so the ordinary GNU General Public License applies to all
>subsequent copies and derivative works made from that copy.
>
>  This option is useful when you wish to copy part of the code of
>the Library into a program that is not a library.
>
>  4. You may copy and distribute the Library (or a portion or
>derivative of it, under Section 2) in object code or executable form
>under the terms of Sections 1 and 2 above provided that you accompany
>it with the complete corresponding machine-readable source code, which
>must be distributed under the terms of Sections 1 and 2 above on a
>medium customarily used for software interchange.
>
>  If distribution of object code is made by offering access to copy
>from a designated place, then offering equivalent access to copy the
>source code from the same place satisfies the requirement to
>distribute the source code, even though third parties are not
>compelled to copy the source along with the object code.
>
>  5. A program that contains no derivative of any portion of the
>Library, but is designed to work with the Library by being compiled or
>linked with it, is called a "work that uses the Library".  Such a
>work, in isolation, is not a derivative work of the Library, and
>therefore falls outside the scope of this License.
>
>  However, linking a "work that uses the Library" with the Library
>creates an executable that is a derivative of the Library (because it
>contains portions of the Library), rather than a "work that uses the
>library".  The executable is therefore covered by this License.
>Section 6 states terms for distribution of such executables.
>
>  When a "work that uses the Library" uses material from a header file
>that is part of the Library, the object code for the work may be a
>derivative work of the Library even though the source code is not.
>Whether this is true is especially significant if the work can be
>linked without the Library, or if the work is itself a library.  The
>threshold for this to be true is not precisely defined by law.
>
>  If such an object file uses only numerical parameters, data
>structure layouts and accessors, and small macros and small inline
>functions (ten lines or less in length), then the use of the object
>file is unrestricted, regardless of whether it is legally a derivative
>work.  (Executables containing this object code plus portions of the
>Library will still fall under Section 6.)
>
>  Otherwise, if the work is a derivative of the Library, you may
>distribute the object code for the work under the terms of Section 6.
>Any executables containing that work also fall under Section 6,
>whether or not they are linked directly with the Library itself.
>^L
>  6. As an exception to the Sections above, you may also combine or
>link a "work that uses the Library" with the Library to produce a
>work containing portions of the Library, and distribute that work
>under terms of your choice, provided that the terms permit
>modification of the work for the customer's own use and reverse
>engineering for debugging such modifications.
>
>  You must give prominent notice with each copy of the work that the
>Library is used in it and that the Library and its use are covered by
>this License.  You must supply a copy of this License.  If the work
>during execution displays copyright notices, you must include the
>copyright notice for the Library among them, as well as a reference
>directing the user to the copy of this License.  Also, you must do one
>of these things:
>
>    a) Accompany the work with the complete corresponding
>    machine-readable source code for the Library including whatever
>    changes were used in the work (which must be distributed under
>    Sections 1 and 2 above); and, if the work is an executable linked
>    with the Library, with the complete machine-readable "work that
>    uses the Library", as object code and/or source code, so that the
>    user can modify the Library and then relink to produce a modified
>    executable containing the modified Library.  (It is understood
>    that the user who changes the contents of definitions files in the
>    Library will not necessarily be able to recompile the application
>    to use the modified definitions.)
>
>    b) Use a suitable shared library mechanism for linking with the
>    Library.  A suitable mechanism is one that (1) uses at run time a
>    copy of the library already present on the user's computer system,
>    rather than copying library functions into the executable, and (2)
>    will operate properly with a modified version of the library, if
>    the user installs one, as long as the modified version is
>    interface-compatible with the version that the work was made with.
>
>    c) Accompany the work with a written offer, valid for at
>    least three years, to give the same user the materials
>    specified in Subsection 6a, above, for a charge no more
>    than the cost of performing this distribution.
>
>    d) If distribution of the work is made by offering access to copy
>    from a designated place, offer equivalent access to copy the above
>    specified materials from the same place.
>
>    e) Verify that the user has already received a copy of these
>    materials or that you have already sent this user a copy.
>
>  For an executable, the required form of the "work that uses the
>Library" must include any data and utility programs needed for
>reproducing the executable from it.  However, as a special exception,
>the materials to be distributed need not include anything that is
>normally distributed (in either source or binary form) with the major
>components (compiler, kernel, and so on) of the operating system on
>which the executable runs, unless that component itself accompanies
>the executable.
>
>  It may happen that this requirement contradicts the license
>restrictions of other proprietary libraries that do not normally
>accompany the operating system.  Such a contradiction means you cannot
>use both them and the Library together in an executable that you
>distribute.
>^L
>  7. You may place library facilities that are a work based on the
>Library side-by-side in a single library together with other library
>facilities not covered by this License, and distribute such a combined
>library, provided that the separate distribution of the work based on
>the Library and of the other library facilities is otherwise
>permitted, and provided that you do these two things:
>
>    a) Accompany the combined library with a copy of the same work
>    based on the Library, uncombined with any other library
>    facilities.  This must be distributed under the terms of the
>    Sections above.
>
>    b) Give prominent notice with the combined library of the fact
>    that part of it is a work based on the Library, and explaining
>    where to find the accompanying uncombined form of the same work.
>
>  8. You may not copy, modify, sublicense, link with, or distribute
>the Library except as expressly provided under this License.  Any
>attempt otherwise to copy, modify, sublicense, link with, or
>distribute the Library is void, and will automatically terminate your
>rights under this License.  However, parties who have received copies,
>or rights, from you under this License will not have their licenses
>terminated so long as such parties remain in full compliance.
>
>  9. You are not required to accept this License, since you have not
>signed it.  However, nothing else grants you permission to modify or
>distribute the Library or its derivative works.  These actions are
>prohibited by law if you do not accept this License.  Therefore, by
>modifying or distributing the Library (or any work based on the
>Library), you indicate your acceptance of this License to do so, and
>all its terms and conditions for copying, distributing or modifying
>the Library or works based on it.
>
>  10. Each time you redistribute the Library (or any work based on the
>Library), the recipient automatically receives a license from the
>original licensor to copy, distribute, link with or modify the Library
>subject to these terms and conditions.  You may not impose any further
>restrictions on the recipients' exercise of the rights granted herein.
>You are not responsible for enforcing compliance by third parties with
>this License.
>^L
>  11. If, as a consequence of a court judgment or allegation of patent
>infringement or for any other reason (not limited to patent issues),
>conditions are imposed on you (whether by court order, agreement or
>otherwise) that contradict the conditions of this License, they do not
>excuse you from the conditions of this License.  If you cannot
>distribute so as to satisfy simultaneously your obligations under this
>License and any other pertinent obligations, then as a consequence you
>may not distribute the Library at all.  For example, if a patent
>license would not permit royalty-free redistribution of the Library by
>all those who receive copies directly or indirectly through you, then
>the only way you could satisfy both it and this License would be to
>refrain entirely from distribution of the Library.
>
>If any portion of this section is held invalid or unenforceable under
>any particular circumstance, the balance of the section is intended to
>apply, and the section as a whole is intended to apply in other
>circumstances.
>
>It is not the purpose of this section to induce you to infringe any
>patents or other property right claims or to contest validity of any
>such claims; this section has the sole purpose of protecting the
>integrity of the free software distribution system which is
>implemented by public license practices.  Many people have made
>generous contributions to the wide range of software distributed
>through that system in reliance on consistent application of that
>system; it is up to the author/donor to decide if he or she is willing
>to distribute software through any other system and a licensee cannot
>impose that choice.
>
>This section is intended to make thoroughly clear what is believed to
>be a consequence of the rest of this License.
>
>  12. If the distribution and/or use of the Library is restricted in
>certain countries either by patents or by copyrighted interfaces, the
>original copyright holder who places the Library under this License
>may add an explicit geographical distribution limitation excluding those
>countries, so that distribution is permitted only in or among
>countries not thus excluded.  In such case, this License incorporates
>the limitation as if written in the body of this License.
>
>  13. The Free Software Foundation may publish revised and/or new
>versions of the Lesser General Public License from time to time.
>Such new versions will be similar in spirit to the present version,
>but may differ in detail to address new problems or concerns.
>
>Each version is given a distinguishing version number.  If the Library
>specifies a version number of this License which applies to it and
>"any later version", you have the option of following the terms and
>conditions either of that version or of any later version published by
>the Free Software Foundation.  If the Library does not specify a
>license version number, you may choose any version ever published by
>the Free Software Foundation.
>^L
>  14. If you wish to incorporate parts of the Library into other free
>programs whose distribution conditions are incompatible with these,
>write to the author to ask for permission.  For software which is
>copyrighted by the Free Software Foundation, write to the Free
>Software Foundation; we sometimes make exceptions for this.  Our
>decision will be guided by the two goals of preserving the free status
>of all derivatives of our free software and of promoting the sharing
>and reuse of software generally.
>
>                            NO WARRANTY
>
>  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
>WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
>EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
>OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
>KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
>IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
>PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
>LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
>THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
>
>  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
>WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
>AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
>FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
>CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
>LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
>RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
>FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
>SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
>DAMAGES.
>
>                     END OF TERMS AND CONDITIONS
>^L
>           How to Apply These Terms to Your New Libraries
>
>  If you develop a new library, and you want it to be of the greatest
>possible use to the public, we recommend making it free software that
>everyone can redistribute and change.  You can do so by permitting
>redistribution under these terms (or, alternatively, under the terms
>of the ordinary General Public License).
>
>  To apply these terms, attach the following notices to the library.
>It is safest to attach them to the start of each source file to most
>effectively convey the exclusion of warranty; and each file should
>have at least the "copyright" line and a pointer to where the full
>notice is found.
>
>
>    <one line to give the library's name and a brief idea of what it
>does.>
>    Copyright (C) <year>  <name of author>
>
>    This library is free software; you can redistribute it and/or
>    modify it under the terms of the GNU Lesser General Public
>    License as published by the Free Software Foundation; either
>    version 2 of the License, or (at your option) any later version.
>
>    This library is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
>    Lesser General Public License for more details.
>
>    You should have received a copy of the GNU Lesser General Public
>    License along with this library; if not, write to the Free Software
>    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307  USA
>
>Also add information on how to contact you by electronic and paper
>mail.
>
>You should also get your employer (if you work as a programmer) or
>your
>school, if any, to sign a "copyright disclaimer" for the library, if
>necessary.  Here is a sample; alter the names:
>
>  Yoyodyne, Inc., hereby disclaims all copyright interest in the
>  library `Frob' (a library for tweaking knobs) written by James
>Random Hacker.
>
>  <signature of Ty Coon>, 1 April 1990
>  Ty Coon, President of Vice
>
>That's all there is to it!
>
>
>                          MOZILLA PUBLIC LICENSE
>                                Version 1.1
>
>                              ---------------
>
>1. Definitions.
>
>     1.0.1. "Commercial Use" means distribution or otherwise making the
>     Covered Code available to a third party.
>
>     1.1. "Contributor" means each entity that creates or contributes to
>     the creation of Modifications.
>
>     1.2. "Contributor Version" means the combination of the Original
>     Code, prior Modifications used by a Contributor, and the Modifications
>     made by that particular Contributor.
>
>     1.3. "Covered Code" means the Original Code or Modifications or the
>     combination of the Original Code and Modifications, in each case
>     including portions thereof.
>
>     1.4. "Electronic Distribution Mechanism" means a mechanism generally
>     accepted in the software development community for the electronic
>     transfer of data.
>
>     1.5. "Executable" means Covered Code in any form other than Source
>     Code.
>
>     1.6. "Initial Developer" means the individual or entity identified
>     as the Initial Developer in the Source Code notice required by Exhibit
>     A.
>
>     1.7. "Larger Work" means a work which combines Covered Code or
>     portions thereof with code not governed by the terms of this License.
>
>     1.8. "License" means this document.
>
>     1.8.1. "Licensable" means having the right to grant, to the maximum
>     extent possible, whether at the time of the initial grant or
>     subsequently acquired, any and all of the rights conveyed herein.
>
>     1.9. "Modifications" means any addition to or deletion from the
>     substance or structure of either the Original Code or any previous
>     Modifications. When Covered Code is released as a series of files, a
>     Modification is:
>          A. Any addition to or deletion from the contents of a file
>          containing Original Code or previous Modifications.
>
>          B. Any new file that contains any part of the Original Code or
>          previous Modifications.
>
>     1.10. "Original Code" means Source Code of computer software code
>     which is described in the Source Code notice required by Exhibit A as
>     Original Code, and which, at the time of its release under this
>     License is not already Covered Code governed by this License.
>
>     1.10.1. "Patent Claims" means any patent claim(s), now owned or
>     hereafter acquired, including without limitation,  method, process,
>     and apparatus claims, in any patent Licensable by grantor.
>
>     1.11. "Source Code" means the preferred form of the Covered Code for
>     making modifications to it, including all modules it contains, plus
>     any associated interface definition files, scripts used to control
>     compilation and installation of an Executable, or source code
>     differential comparisons against either the Original Code or another
>     well known, available Covered Code of the Contributor's choice. The
>     Source Code can be in a compressed or archival form, provided the
>     appropriate decompression or de-archiving software is widely available
>     for no charge.
>
>     1.12. "You" (or "Your")  means an individual or a legal entity
>     exercising rights under, and complying with all of the terms of, this
>     License or a future version of this License issued under Section 6.1.
>     For legal entities, "You" includes any entity which controls, is
>     controlled by, or is under common control with You. For purposes of
>     this definition, "control" means (a) the power, direct or indirect,
>     to cause the direction or management of such entity, whether by
>     contract or otherwise, or (b) ownership of more than fifty percent
>     (50%) of the outstanding shares or beneficial ownership of such
>     entity.
>
>2. Source Code License.
>
>     2.1. The Initial Developer Grant.
>     The Initial Developer hereby grants You a world-wide, royalty-free,
>     non-exclusive license, subject to third party intellectual property
>     claims:
>          (a)  under intellectual property rights (other than patent or
>          trademark) Licensable by Initial Developer to use, reproduce,
>          modify, display, perform, sublicense and distribute the Original
>          Code (or portions thereof) with or without Modifications, and/or
>          as part of a Larger Work; and
>
>          (b) under Patents Claims infringed by the making, using or
>          selling of Original Code, to make, have made, use, practice,
>          sell, and offer for sale, and/or otherwise dispose of the
>          Original Code (or portions thereof).
>
>          (c) the licenses granted in this Section 2.1(a) and (b) are
>          effective on the date Initial Developer first distributes
>          Original Code under the terms of this License.
>
>          (d) Notwithstanding Section 2.1(b) above, no patent license is
>          granted: 1) for code that You delete from the Original Code; 2)
>          separate from the Original Code;  or 3) for infringements caused
>          by: i) the modification of the Original Code or ii) the
>          combination of the Original Code with other software or devices.
>
>     2.2. Contributor Grant.
>     Subject to third party intellectual property claims, each Contributor
>     hereby grants You a world-wide, royalty-free, non-exclusive license
>
>          (a)  under intellectual property rights (other than patent or
>          trademark) Licensable by Contributor, to use, reproduce, modify,
>          display, perform, sublicense and distribute the Modifications
>          created by such Contributor (or portions thereof) either on an
>          unmodified basis, with other Modifications, as Covered Code
>          and/or as part of a Larger Work; and
>
>          (b) under Patent Claims infringed by the making, using, or
>          selling of  Modifications made by that Contributor either alone
>          and/or in combination with its Contributor Version (or portions
>          of such combination), to make, use, sell, offer for sale, have
>          made, and/or otherwise dispose of: 1) Modifications made by that
>          Contributor (or portions thereof); and 2) the combination of
>          Modifications made by that Contributor with its Contributor
>          Version (or portions of such combination).
>
>          (c) the licenses granted in Sections 2.2(a) and 2.2(b) are
>          effective on the date Contributor first makes Commercial Use of
>          the Covered Code.
>
>          (d)    Notwithstanding Section 2.2(b) above, no patent license is
>          granted: 1) for any code that Contributor has deleted from the
>          Contributor Version; 2)  separate from the Contributor Version;
>          3)  for infringements caused by: i) third party modifications of
>          Contributor Version or ii)  the combination of Modifications made
>          by that Contributor with other software  (except as part of the
>          Contributor Version) or other devices; or 4) under Patent Claims
>          infringed by Covered Code in the absence of Modifications made by
>          that Contributor.
>
>3. Distribution Obligations.
>
>     3.1. Application of License.
>     The Modifications which You create or to which You contribute are
>     governed by the terms of this License, including without limitation
>     Section 2.2. The Source Code version of Covered Code may be
>     distributed only under the terms of this License or a future version
>     of this License released under Section 6.1, and You must include a
>     copy of this License with every copy of the Source Code You
>     distribute. You may not offer or impose any terms on any Source Code
>     version that alters or restricts the applicable version of this
>     License or the recipients' rights hereunder. However, You may include
>     an additional document offering the additional rights described in
>     Section 3.5.
>
>     3.2. Availability of Source Code.
>     Any Modification which You create or to which You contribute must be
>     made available in Source Code form under the terms of this License
>     either on the same media as an Executable version or via an accepted
>     Electronic Distribution Mechanism to anyone to whom you made an
>     Executable version available; and if made available via Electronic
>     Distribution Mechanism, must remain available for at least twelve (12)
>     months after the date it initially became available, or at least six
>     (6) months after a subsequent version of that particular Modification
>     has been made available to such recipients. You are responsible for
>     ensuring that the Source Code version remains available even if the
>     Electronic Distribution Mechanism is maintained by a third party.
>
>     3.3. Description of Modifications.
>     You must cause all Covered Code to which You contribute to contain a
>     file documenting the changes You made to create that Covered Code and
>     the date of any change. You must include a prominent statement that
>     the Modification is derived, directly or indirectly, from Original
>     Code provided by the Initial Developer and including the name of the
>     Initial Developer in (a) the Source Code, and (b) in any notice in an
>     Executable version or related documentation in which You describe the
>     origin or ownership of the Covered Code.
>
>     3.4. Intellectual Property Matters
>          (a) Third Party Claims.
>          If Contributor has knowledge that a license under a third party's
>          intellectual property rights is required to exercise the rights
>          granted by such Contributor under Sections 2.1 or 2.2,
>          Contributor must include a text file with the Source Code
>          distribution titled "LEGAL" which describes the claim and the
>          party making the claim in sufficient detail that a recipient will
>          know whom to contact. If Contributor obtains such knowledge after
>          the Modification is made available as described in Section 3.2,
>          Contributor shall promptly modify the LEGAL file in all copies
>          Contributor makes available thereafter and shall take other steps
>          (such as notifying appropriate mailing lists or newsgroups)
>          reasonably calculated to inform those who received the Covered
>          Code that new knowledge has been obtained.
>
>          (b) Contributor APIs.
>          If Contributor's Modifications include an application programming
>          interface and Contributor has knowledge of patent licenses which
>          are reasonably necessary to implement that API, Contributor must
>          also include this information in the LEGAL file.
>
>               (c)    Representations.
>          Contributor represents that, except as disclosed pursuant to
>          Section 3.4(a) above, Contributor believes that Contributor's
>          Modifications are Contributor's original creation(s) and/or
>          Contributor has sufficient rights to grant the rights conveyed by
>          this License.
>
>     3.5. Required Notices.
>     You must duplicate the notice in Exhibit A in each file of the Source
>     Code.  If it is not possible to put such notice in a particular Source
>     Code file due to its structure, then You must include such notice in a
>     location (such as a relevant directory) where a user would be likely
>     to look for such a notice.  If You created one or more Modification(s)
>     You may add your name as a Contributor to the notice described in
>     Exhibit A.  You must also duplicate this License in any documentation
>     for the Source Code where You describe recipients' rights or ownership
>     rights relating to Covered Code.  You may choose to offer, and to
>     charge a fee for, warranty, support, indemnity or liability
>     obligations to one or more recipients of Covered Code. However, You
>     may do so only on Your own behalf, and not on behalf of the Initial
>     Developer or any Contributor. You must make it absolutely clear than
>     any such warranty, support, indemnity or liability obligation is
>     offered by You alone, and You hereby agree to indemnify the Initial
>     Developer and every Contributor for any liability incurred by the
>     Initial Developer or such Contributor as a result of warranty,
>     support, indemnity or liability terms You offer.
>
>     3.6. Distribution of Executable Versions.
>     You may distribute Covered Code in Executable form only if the
>     requirements of Section 3.1-3.5 have been met for that Covered Code,
>     and if You include a notice stating that the Source Code version of
>     the Covered Code is available under the terms of this License,
>     including a description of how and where You have fulfilled the
>     obligations of Section 3.2. The notice must be conspicuously included
>     in any notice in an Executable version, related documentation or
>     collateral in which You describe recipients' rights relating to the
>     Covered Code. You may distribute the Executable version of Covered
>     Code or ownership rights under a license of Your choice, which may
>     contain terms different from this License, provided that You are in
>     compliance with the terms of this License and that the license for the
>     Executable version does not attempt to limit or alter the recipient's
>     rights in the Source Code version from the rights set forth in this
>     License. If You distribute the Executable version under a different
>     license You must make it absolutely clear that any terms which differ
>     from this License are offered by You alone, not by the Initial
>     Developer or any Contributor. You hereby agree to indemnify the
>     Initial Developer and every Contributor for any liability incurred by
>     the Initial Developer or such Contributor as a result of any such
>     terms You offer.
>
>     3.7. Larger Works.
>     You may create a Larger Work by combining Covered Code with other code
>     not governed by the terms of this License and distribute the Larger
>     Work as a single product. In such a case, You must make sure the
>     requirements of this License are fulfilled for the Covered Code.
>
>4. Inability to Comply Due to Statute or Regulation.
>
>     If it is impossible for You to comply with any of the terms of this
>     License with respect to some or all of the Covered Code due to
>     statute, judicial order, or regulation then You must: (a) comply with
>     the terms of this License to the maximum extent possible; and (b)
>     describe the limitations and the code they affect. Such description
>     must be included in the LEGAL file described in Section 3.4 and must
>     be included with all distributions of the Source Code. Except to the
>     extent prohibited by statute or regulation, such description must be
>     sufficiently detailed for a recipient of ordinary skill to be able to
>     understand it.
>
>5. Application of this License.
>
>     This License applies to code to which the Initial Developer has
>     attached the notice in Exhibit A and to related Covered Code.
>
>6. Versions of the License.
>
>     6.1. New Versions.
>     Netscape Communications Corporation ("Netscape") may publish revised
>     and/or new versions of the License from time to time. Each version
>     will be given a distinguishing version number.
>
>     6.2. Effect of New Versions.
>     Once Covered Code has been published under a particular version of the
>     License, You may always continue to use it under the terms of that
>     version. You may also choose to use such Covered Code under the terms
>     of any subsequent version of the License published by Netscape. No one
>     other than Netscape has the right to modify the terms applicable to
>     Covered Code created under this License.
>
>     6.3. Derivative Works.
>     If You create or use a modified version of this License (which you may
>     only do in order to apply it to code which is not already Covered Code
>     governed by this License), You must (a) rename Your license so that
>     the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape",
>     "MPL", "NPL" or any confusingly similar phrase do not appear in your
>     license (except to note that your license differs from this License)
>     and (b) otherwise make it clear that Your version of the license
>     contains terms which differ from the Mozilla Public License and
>     Netscape Public License. (Filling in the name of the Initial
>     Developer, Original Code or Contributor in the notice described in
>     Exhibit A shall not of themselves be deemed to be modifications of
>     this License.)
>
>7. DISCLAIMER OF WARRANTY.
>
>     COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
>     WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
>     WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF
>     DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING.
>     THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE
>     IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT,
>     YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE
>     COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER
>     OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF
>     ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
>
>8. TERMINATION.
>
>     8.1.  This License and the rights granted hereunder will terminate
>     automatically if You fail to comply with terms herein and fail to cure
>     such breach within 30 days of becoming aware of the breach. All
>     sublicenses to the Covered Code which are properly granted shall
>     survive any termination of this License. Provisions which, by their
>     nature, must remain in effect beyond the termination of this License
>     shall survive.
>
>     8.2.  If You initiate litigation by asserting a patent infringement
>     claim (excluding declatory judgment actions) against Initial Developer
>     or a Contributor (the Initial Developer or Contributor against whom
>     You file such action is referred to as "Participant")  alleging that:
>
>     (a)  such Participant's Contributor Version directly or indirectly
>     infringes any patent, then any and all rights granted by such
>     Participant to You under Sections 2.1 and/or 2.2 of this License
>     shall, upon 60 days notice from Participant terminate prospectively,
>     unless if within 60 days after receipt of notice You either: (i)
>     agree in writing to pay Participant a mutually agreeable reasonable
>     royalty for Your past and future use of Modifications made by such
>     Participant, or (ii) withdraw Your litigation claim with respect to
>     the Contributor Version against such Participant.  If within 60 days
>     of notice, a reasonable royalty and payment arrangement are not
>     mutually agreed upon in writing by the parties or the litigation claim
>     is not withdrawn, the rights granted by Participant to You under
>     Sections 2.1 and/or 2.2 automatically terminate at the expiration of
>     the 60 day notice period specified above.
>
>     (b)  any software, hardware, or device, other than such Participant's
>     Contributor Version, directly or indirectly infringes any patent, then
>     any rights granted to You by such Participant under Sections 2.1(b)
>     and 2.2(b) are revoked effective as of the date You first made, used,
>     sold, distributed, or had made, Modifications made by that
>     Participant.
>
>     8.3.  If You assert a patent infringement claim against Participant
>     alleging that such Participant's Contributor Version directly or
>     indirectly infringes any patent where such claim is resolved (such as
>     by license or settlement) prior to the initiation of patent
>     infringement litigation, then the reasonable value of the licenses
>     granted by such Participant under Sections 2.1 or 2.2 shall be taken
>     into account in determining the amount or value of any payment or
>     license.
>
>     8.4.  In the event of termination under Sections 8.1 or 8.2 above,
>     all end user license agreements (excluding distributors and resellers)
>     which have been validly granted by You or any distributor hereunder
>     prior to termination shall survive termination.
>
>9. LIMITATION OF LIABILITY.
>
>     UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
>     (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL
>     DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE,
>     OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR
>     ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
>     CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL,
>     WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER
>     COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN
>     INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
>     LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY
>     RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
>     PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
>     EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO
>     THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
>
>10. U.S. GOVERNMENT END USERS.
>
>     The Covered Code is a "commercial item," as that term is defined in
>     48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer
>     software" and "commercial computer software documentation," as such
>     terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48
>     C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995),
>     all U.S. Government End Users acquire Covered Code with only those
>     rights set forth herein.
>
>11. MISCELLANEOUS.
>
>     This License represents the complete agreement concerning subject
>     matter hereof. If any provision of this License is held to be
>     unenforceable, such provision shall be reformed only to the extent
>     necessary to make it enforceable. This License shall be governed by
>     California law provisions (except to the extent applicable law, if
>     any, provides otherwise), excluding its conflict-of-law provisions.
>     With respect to disputes in which at least one party is a citizen of,
>     or an entity chartered or registered to do business in the United
>     States of America, any litigation relating to this License shall be
>     subject to the jurisdiction of the Federal Courts of the Northern
>     District of California, with venue lying in Santa Clara County,
>     California, with the losing party responsible for costs, including
>     without limitation, court costs and reasonable attorneys' fees and
>     expenses. The application of the United Nations Convention on
>     Contracts for the International Sale of Goods is expressly excluded.
>     Any law or regulation which provides that the language of a contract
>     shall be construed against the drafter shall not apply to this
>     License.
>
>12. RESPONSIBILITY FOR CLAIMS.
>
>     As between Initial Developer and the Contributors, each party is
>     responsible for claims and damages arising, directly or indirectly,
>     out of its utilization of rights under this License and You agree to
>     work with Initial Developer and Contributors to distribute such
>     responsibility on an equitable basis. Nothing herein is intended or
>     shall be deemed to constitute any admission of liability.
>
>13. MULTIPLE-LICENSED CODE.
>
>     Initial Developer may designate portions of the Covered Code as
>     "Multiple-Licensed".  "Multiple-Licensed" means that the Initial
>     Developer permits you to utilize portions of the Covered Code under
>     Your choice of the NPL or the alternative licenses, if any, specified
>     by the Initial Developer in the file described in Exhibit A.
>
>EXHIBIT A -Mozilla Public License.
>
>     ``The contents of this file are subject to the Mozilla Public License
>     Version 1.1 (the "License"); you may not use this file except in
>     compliance with the License. You may obtain a copy of the License at
>     http://www.mozilla.org/MPL/
>
>     Software distributed under the License is distributed on an "AS IS"
>     basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
>     License for the specific language governing rights and limitations
>     under the License.
>
>     The Original Code is ______________________________________.
>
>     The Initial Developer of the Original Code is ________________________.
>     Portions created by ______________________ are Copyright (C) ______
>     _______________________. All Rights Reserved.
>
>     Contributor(s): ______________________________________.
>
>     Alternatively, the contents of this file may be used under the terms
>     of the _____ license (the  "[___] License"), in which case the
>     provisions of [______] License are applicable instead of those
>     above.  If you wish to allow use of your version of this file only
>     under the terms of the [____] License and not to allow others to use
>     your version of this file under the MPL, indicate your decision by
>     deleting  the provisions above and replace  them with the notice and
>     other provisions required by the [___] License.  If you do not delete
>     the provisions above, a recipient may use your version of this file
>     under either the MPL or the [___] License."
>
>     [NOTE: The text of this Exhibit A may differ slightly from the text of
>     the notices in the Source Code files of the Original Code. You should
>     use the text of this Exhibit A rather than the text found in the
>     Original Code Source Code for Your Modifications.]
>
>About Hunspell
>--------------
>
>Hunspell is a spell checker and morphological analyzer library and program
>designed for languages with rich morphology and complex word compounding or
>character encoding. Hunspell interfaces: Ispell-like terminal interface
>using Curses library, Ispell pipe interface, OpenOffice.org UNO module.
>
>Hunspell's code base comes from the OpenOffice.org MySpell
>(http://lingucomponent.openoffice.org/MySpell-3.zip). See README.MYSPELL,
>AUTHORS.MYSPELL and license.myspell files.
>Hunspell is designed to eventually replace Myspell in OpenOffice.org.
>
>Main features of Hunspell spell checker and morphological analyzer:
>
>- Unicode support (affix rules work only with the first 65535 Unicode characters)
>
>- Morphological analysis (in custom item and arrangement style)
>
>- Max. 65535 affix classes and twofold affix stripping (for agglutinative
>  languages, like Azeri, Basque, Estonian, Finnish, Hungarian, Turkish, etc.)
>
>- Support complex compoundings (for example, Hungarian and German)
>
>- Support language specific features (for example, special casing of
>  Azeri and Turkish dotted i, or German sharp s)
>
>- Handle conditional affixes, circumfixes, fogemorphemes,
>  forbidden words, pseudoroots and homonyms.
>
>- Free software (LGPL, GPL, MPL tri-license)
>
>Compiling
>---------
>
>./configure
>make
>make install
>
>For dictionary development, use the --with-warnings option of configure.
>
>For compiling morphological analyser and stemmer code and tools, use the
>--with-experimental option of configure.
>
>For interactive user interface of Hunspell executable, use the --with-ui option.
>
>The developer packages you need to compile Hunspell's interface:
>
>glibc-devel
>
>optional developer packages:
>
>ncurses (need for --with-ui)
>readline (for fancy input line editing,
>  configure parameter: --with-readline)
>locale and gettext (but you can also use the
>  --with-included-gettext configure parameter)
>
>Hunspell distribution uses new Autoconf (2.59) and Automake (1.9).
>
>Testing
>-------
>
>Testing Hunspell (see tests in tests/ subdirectory):
>
>make check
>
>or with Valgrind debugger:
>
>make check
>VALGRIND=[Valgrind_tool] make check
>
>For example:
>
>make check
>VALGRIND=memcheck make check
>
>Documentation
>-------------
>
>features and dictionary format:
>man 4 hunspell
>
>man hunspell
>hunspell -h
>http://hunspell.sourceforge.net
>
>Usage
>-----
>
>The src/tools dictionary contains three executables.
>A spell checker with Ispell-like curses interface and Ispell
>compatible pipe interface (hunspell) and two small example
>program (hunmorph and hunstem).
>
>After compiling and installing (see INSTALL) you can
>run the Hunspell spell checker (compiled with user interface)
>with a Hunspell or Myspell dictionary:
>
>hunspell -d en_UK text.txt
>
>or without interface:
>
>hunspell -d en_UK -l <text.txt
>
>(Dictionaries consists of an affix and dictionary file.)
>
>Usage of Hunmorph morphological analyzer:
>
>hunmorph en_UK.aff en_UK.dic input_file
>
>Using Hunspell library with GCC
>-------------------------------
>
>Including in your program:
>#include <hunspell.hxx>
>
>Linking with Hunspell static library:
>g++ -lhunspell example.cxx 
>
>Dictionaries
>------------
>
>Myspell dictionaries:
>http://lingucomponent.openoffice.org/spell_dic.html
>
>Aspell dictionaries (need some conversion):
>ftp://ftp.gnu.org/gnu/aspell/dict
>Conversion steps: see relevant feature request at http://hunspell.sf.net.
>
>NÃ©meth LÃ¡szlÃ³
>nemeth at OOo
>MySpell is a simple spell checker that uses affix 
>compression and is modelled after the spell checker
>ispell.  
>
>MySpell was written to explore how affix compression 
>can be implemented. 
>
>The Main features of MySpell are:
>
>1. written in C++ to make it easier to interface with 
>   Pspell, OpenOffice, AbiWord, etc
>
>2. it is stateless, uses no static variables and
>   should be completely reentrant with almost no 
>   ifdefs  
>
>3. it tries to be as compatible with ispell to
>   the extent it can.  It can read slightly modified 
>   versions of munched ispell dictionaries (and it 
>   comes with a munched english wordlist borrowed from 
>   Kevin Atkinson's excellent Aspell.
>
>4. it uses a heavily modified aff file format that
>   can be derived from ispell aff files but uses
>   the iso-8859-X character sets only
> 
>5. it is simple with *lots* of comments that 
>   describes how the affixes are stored
>   and tested for (based on the approach used by 
>   ispell).
>
>6. it supports improved suggestions with replacement
>   tables and ngram-scoring based mechanisms in addition
>   to the main suggestion mechanisms
>
>7. like ispell it has a BSD license (and  no 
>   advertising clause)
>
>But ... it has *no* support for adding words
>to a personal dictionary, *no* support for converting
>between various text encodings, and *no* command line
>interface (it is purely meant to be a library).
>
>It can not (in any way) replace all of the functionality
>of ispell or aspell/pspell.  It is meant as a learning
>tool for understanding affix compression and for 
>being used by front ends like OpenOffice, Abiword, etc.
>
>MySpell has been tested under Linux and Solaris
>and has the world's simplest Makefile and no 
>configure support.
>
>It does come with a simple example program that 
>spell checks some words and returns suggestions.
>
>To build a static library and an example
>program under Linux simply type:
>
>tar -zxvf myspell.tar.gz
>cd myspell2
>make
>
>To run the example program:
>./example ./en_US.aff ./en_US.dic checkme.lst
>
>Please play around with it and let me know
>what you think.
>
>Please see the file CONTRIBUTORS for more info.
>Many thanks to the following contributors and supporters:
>
>Lars Aronsson
>BencsÃ¡th BoldizsÃ¡r
>BÃrÃ³ ÃrpÃ¡d
>Ingo H. de Boer
>Simon Brouwer
>Jeppe Bundsgaard
>Ginn Chen
>Dmitri Gabinski
>Dvornik LÃ¡szlÃ³
>David Einstein
>Rene Engelhard
>Frederik Fouvry
>Gavins at OOo
>Gefferth AndrÃ¡s
>GodÃ³ Ferenc
>Goldman EleonÃ³ra
>HalÃ¡csy PÃ©ter
>Chris Halls
>Khaled Hosny
>IzsÃ³k AndrÃ¡s
>BjÃ¶rn Jacke
>Mike Tian-Jian Jiang
>Dafydd Jones
>Ryan Jones
>Jean-Christophe Helary
>Kevin Hendricks
>Martin Hollmichel
>Pavel JanÃk
>KÃ©mÃ©nczy KÃ¡lmÃ¡n
>Dan Kenigsberg
>Khiraly LÃ¡szlÃ³
>Koblinger Egmont
>Kornai AndrÃ¡s
>Tor Lillqvist
>Robert Longson
>Marot at SF dot net
>Caolan McNamara
>Michael Meeks
>Moheb Mekhaiel
>Ellis Miller
>Giuseppe Modugno
>JÃ¡nos MohÃ¡csi
>Bram Moolenaar
>Daniel Naber
>Nagy Viktor
>John Nisly
>Noll JÃ¡nos
>Bryan Petty
>Harri PitkÃ¤nen
>Davide Prina
>Kevin F. Quinn
>Erdal Ronahi
>Bernhard Rosenkraenzer
>SarlÃ³s TamÃ¡s
>Thobias Schlemmer
>Jose da Silva
>Munzir Taha
>TÃmÃ¡r AndrÃ¡s
>Tonal at OOo
>TrÃ³n Viktor 
>Gianluca Turconi
>Ryan VanderMeulen
>Varga DÃ¡niel
>Miha Vrhovnik
>Martijn Wargers
>Friedel Wolff
>GÃ¡bor Zahemszky
>Taha Zerrouki 
>and others (see also AUTHORS.myspell)
>
>FSF.hu Foundation
>http://www.fsf.hu
>
>MOKK Research Centre
>Budapest University of Technology and Economics
>Sociology and Communications Department
>http://www.mokk.bme.hu
>
>Hungarian Ministry of Informatics and Telecommunications
>
>IMEDIA Ltd.
>http://www.imedia.hu
>
>OpenOffice.org community
>http://www.openoffice.org
>
>UHU-Linux Ltd.
>
>Thanks,
>
>NÃ©meth LÃ¡szlÃ³
>nemeth at OOo
>/* ***** BEGIN LICENSE BLOCK *****
> * Version: MPL 1.1/GPL 2.0/LGPL 2.1
> *
> * The contents of this file are subject to the Mozilla Public License Version
> * 1.1 (the "License"); you may not use this file except in compliance with
> * the License. You may obtain a copy of the License at
> * http://www.mozilla.org/MPL/
> *
> * Software distributed under the License is distributed on an "AS IS" basis,
> * WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License
> * for the specific language governing rights and limitations under the
> * License.
> *
> * The Original Code is Hunspell, based on MySpell.
> *
> * The Initial Developers of the Original Code are
> * Kevin Hendricks (MySpell) and NÃ©meth LÃ¡szlÃ³ (Hunspell).
> * Portions created by the Initial Developers are Copyright (C) 2002-2005
> * the Initial Developers. All Rights Reserved.
> *
> * Contributor(s):
> * David Einstein 
> * Davide Prina
> * Giuseppe Modugno 
> * Gianluca Turconi
> * Simon Brouwer
> * Noll JÃ¡nos
> * BÃrÃ³ ÃrpÃ¡d
> * Goldman EleonÃ³ra
> * SarlÃ³s TamÃ¡s
> * BencsÃ¡th BoldizsÃ¡r
> * HalÃ¡csy PÃ©ter
> * Dvornik LÃ¡szlÃ³
> * Gefferth AndrÃ¡s
> * Nagy Viktor
> * Varga DÃ¡niel
> * Chris Halls
> * Rene Engelhard
> * Bram Moolenaar
> * Dafydd Jones
> * Harri PitkÃ¤nen
> *
> * Alternatively, the contents of this file may be used under the terms of
> * either the GNU General Public License Version 2 or later (the "GPL"), or
> * the GNU Lesser General Public License Version 2.1 or later (the "LGPL"),
> * in which case the provisions of the GPL or the LGPL are applicable instead
> * of those above. If you wish to allow use of your version of this file only
> * under the terms of either the GPL or the LGPL, and not to allow others to
> * use your version of this file under the terms of the MPL, indicate your
> * decision by deleting the provisions above and replace them with the notice
> * and other provisions required by the GPL or the LGPL. If you do not delete
> * the provisions above, a recipient may use your version of this file under
> * the terms of any one of the MPL, the GPL or the LGPL.
> *
> * ***** END LICENSE BLOCK ***** */
>/*
> * Copyright 2002 Kevin B. Hendricks, Stratford, Ontario, Canada
> * And Contributors.  All rights reserved.
> *
> * Redistribution and use in source and binary forms, with or without
> * modification, are permitted provided that the following conditions
> * are met:
> *
> * 1. Redistributions of source code must retain the above copyright
> *    notice, this list of conditions and the following disclaimer.
> *
> * 2. Redistributions in binary form must reproduce the above copyright
> *    notice, this list of conditions and the following disclaimer in the
> *    documentation and/or other materials provided with the distribution.
> *
> * 3. All modifications to the source code must be clearly marked as
> *    such.  Binary redistributions based on modified source code
> *    must be clearly marked as modified versions in the documentation
> *    and/or other materials provided with the distribution.
> *
> * THIS SOFTWARE IS PROVIDED BY KEVIN B. HENDRICKS AND CONTRIBUTORS 
> * ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 
> * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS 
> * FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL 
> * KEVIN B. HENDRICKS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 
> * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 
> * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 
> * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
> * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
> * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
> * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
> * SUCH DAMAGE.
> *
> *
> * NOTE: A special thanks and credit goes to Geoff Kuenning
> * the creator of ispell.  MySpell's affix algorithms were
> * based on those of ispell which should be noted is
> * copyright Geoff Kuenning et.al. and now available
> * under a BSD style license. For more information on ispell
> * and affix compression in general, please see:
> * http://www.cs.ucla.edu/ficus-members/geoff/ispell.html
> * (the home page for ispell)
> *
> * An almost complete rewrite  of MySpell for use by  
> * the Mozilla project has been developed by David Einstein 
> * (Deinst@world.std.com).  David and I are now 
> * working on parallel development tracks to help 
> * our respective projects (Mozilla and OpenOffice.org 
> * and we will maintain full affix file and dictionary 
> * file compatibility and work on merging our versions 
> * of MySpell back into a single tree. David has been 
> * a significant help in improving MySpell.
> * 
> * Special thanks also go to La'szlo' Ne'meth 
> * <nemethl@gyorsposta.hu> who is the author of the 
> * Hungarian dictionary and who developed and contributed 
> * the code to support compound words in MySpell 
> * and fixed numerous problems with the encoding 
> * case conversion tables.
> *
> */
>Ì[ÏoG¾×_QIv*&);3³8ì8±i%[¤ñ&YÍE±H»ÙMt¨o>æ0Àä´:ØÀOÓÐÿµß{UÕ]MÑ,²lñGw¿zõ~~ï½âp*9[áÙ>^²r©ÓT>ï|ÿþor¬/ôb¤ùà÷Ã÷ÅðèX>ÃÓ}ù´þá¹hn?ÈN/uY¿,êëò|0Wëú¥_õeYÕ¯lýz«Û+Yßr<_M2R§zAE>-ÔI×/ÎÎöÕ?¶KüÛùàÖQøÿ%þÏðÿií#ü_àÿöÏtçØ/{]ðÇ¥,Õ¼¾¶ßFßÖ×i/êëì²';æöê¿Ô/NÅ#1ü¬8àóAYéâö'i2«Øúå7tQÞ^MtZ¿MµJö¨é¥*väKÇù¤~;®ëì2©_gkb`WCñNM¹Ða2Nds%U%Å:IºÅ«rfFõu¢¬(ÍBÑ!Ö©.û²w¤vÎôW}¹öä¨ÏOL|2½¤¾©[WæéX¥;²ÝyT6ÃgÏÄ¾^H5^e\èitWVß¬åRA=õ
vnûØä~Puâ±ê®äLyM«L.nc<ÄÃ#½Ð6Væ2x©ÔZ%¾Ï3ì¿/ýúò^_®!J9sÐ×©Lt5¾½Â?¦`D¡Rº¡2},(5 -Ë9)}à¨|è©ð]E^ÕP>êêö]ÄÓÚ¸Áö¼ö7ö»©ÄðLR$jyQMäÔP_¯ÁV}SX.teëï©Ô%	-âM6^¥¼F´]ivì/ðîè?
>~!'d6a·ÓéíUvY¿&kÂë9YKñ¢¾IsØ$§ShßO¼ÝONàf?Ì {]?Ã¶Åa}³õ¦b'ù8#kÖVeï¬~=ÙV^ã£kF¥NñV[«EªgÚÞ^ÁSÀÕeÙA&F«lYù;¹0ij°[
ÌüR%ya@fj§'«Þ	lîç<3zBÄ$µìe
%rÍ=O/¡Zâ/o8\«>%@³kGzgØv»'©²x
>óÆEÂÆ×Äv^5&0T{k&YÒyt¡Do¾^Âs_ÎwÍ|Þæ»Yvé"f}3õtíêBÙìÒàãÍDÄ×Á©JV_<>ª::t&p`[æ`=BP>qB¦×Ü13dðIwß\÷%ä¯íZÓÃºL)þgi,¹1d5:o¤c¹µú5<WýMî#Ù+1«Ø¥÷}ä ®¼HdÒ¢ K6(kRh¾Døïk5çÄó2³·?á]ý&½´d3vÔÚÅ¿´ZÁúßûS	a»¸¢³1Ì]ºÝ¥PXìu5qìÖ/û2ß%FW»õX3xl6^ÿm¢^#/ùçß"(PNáÿi¢ÒªÜ¶ºùBYv{UÀÿúr
>GLòÒ¼XárlèíÊOòjJ{ÜJ;1kgC:Î¦zs%ï¯Î0¢Cô\p®µêtMSß.ÉRÓlGRjwÝÖõfÊ¦°H_ÖT:cKm¿£3µ6î,s¤>8vÁG°{ÏÛúíìHxÐEMÌ÷«E°¼Í é«oÆYÙkÂG=µ¨i^oòæÛ+²TxÄw=Oô.íKd)r)D]
>z.øÐ ¬M£R0*ýÈÁðÙ³äÄo!Âo(6dEõ
$%åqO[ÌDXªt¦²)î*ÌÞGJÂÕ$`3E_\ßPvA¢W%x« ád'òPô\Èñò%¿á@Bü#[msBæQMÇ«xí<±y6<mxiD´Ú]:õ
©ÆE2(!ôì
>Ùb²BÔËóÁ§¶~K;ÔoÉZõÖ¯¡Vòý2øjd*«,®2à%3Xà OYè×ÚÄàa0Ûðßü~Æ6
¿ýw_þÆ!¸¿ýø
TMÈÍÆä)ìÍéÜ%wW&ñ|÷Ô/òrü¶E¿}Ál¦Wá¹Q~9W@LKÄ¿ËµN·={0¸Ì)à{5n'ø(Ë³ËÅ
>FCdcÊÈ]'ÛhÁQý*>ÜOê×é¸PóÊH2P=EÖþ )/È~Í6Zû¯ËÝÛtñKæ¸£2Cè6Mrx5 +vPVÝ¬qæ	Âl.@úi@nísÏÆ(â5è®
+ËYè·nJ>à¹â¹Ä[ºV ÊCDáªkz¹²@Exã®lØ	å¸2Î¢ürh±²<Bi~Ç½?ì®en¯vbà`V1ñ°©LÀ×ý$#,á»¼X8Ë .\Å1×¥%CðL@»ñÊfìØAÁ"¬¥RÂK»ÃGÏ>?=>ªÿãî3ÚêIqºÔ@8(Ãh
<cW¨B1Qëäy%@«*¬Ëe¯\%ÃFê
>JèE÷Æ,DºÂSþs*7|CV-**?âZµïõéï½¾+DÜËùå¾ 4Goÿ]Ü©he«ÛË¾<äÐÚVOQ9É±H ¨ÈÖQã ¢½©Ä#7TIÕ¯ÙXïTù ªeø¦j:
Õhmv(÷*a79!ë|±TÖLjØ `,ÍlkNV¶îJ¢<È$%ðTvQ]~Eõ=ÜK#ØOªk¹¤Ë¨,VÝíYªP»®Ø¶®T+/À3`#"®*z¦¥CpUÿ@"&HÎ	F"¥Vd%cù~ãiï`<«â2/BmD&TQ8\6Uj@ßtÛÏNäîª,vË*ônhìõDRxþ#WîRèªßØua#\ÄI5¢J_²;*®VÁ´<ñDóH[û2z]Ðþá +vLYÍÇïfG´MÔfB v©Ú}â½WÅP
Ì³ú£ÇõÃH_
>2^$óÁw.Q_©ÑibR@¦¹Df_"uU1£¸½JäêÊïK=ÎÞJ8'ÙÛ(¾Q6amYÛñæG9:Cn{IABüçp[	ËD!¾¯ÞÙnw§Ï¶¶ÁU	NàÂ)XÑtn<öÍ|BH03î-4ñn_èHØ33^tºØGÀ{ j©vvº)èá}AM®m!º	áDÀ§ÅBIµ7
>v+¦Ã]@éôâ»MÃïì(~´}GYtÃGºé°$b/&¡£xec±D"Ci9¤\2û>¸¬J*Û'ÉYúÑ&ÛFõ[ËÑñQ0&º<Ê¼5À+ØYÐÃ äÈøàRH$Ä8í*ÚðøÜ=²¹Û·æÿW¢Ø*¤s´mQ2ÁwXI4{GÐ%A¬°y8T$¬L<¥¾ì®åîì/·a 
>°CANI%bð|³|ì¸ÛÒC·þ>ü®Z7+E	b8áPÙ£KÄGíØ?~²·;û[@D»kvÑð"¥¹ÔÂY×±¦wV¾öøàó³ã§N¾¦\PÂV$ÓÐys·«_È[¸L
ZÚ¯rÑãÎÓN¹ãUQd¤wQÂd\¸i2ìf(|±&öWÀÜC÷H·?EÇCTFzÖDt¢Øe#ôÙÜ¢ÜàÑ¥1
>|oæ9ÈdÜzO¦f¬[ë&¥:a/¥NÀÿz|òøèàôl»x7{ÞÔçè2¢,!PmõÛ\3ææ-?#2×ÇotÐ^Snj"õX;
-~ôÓ
È0F¾wÅ#¼xßP'!Vñße%ò=+ÔþêW¥+Ù¦+«¿¿"9P¿ÆíKPjËØj#èRÂ(CÿÖr)ÕPúxT;ÃÂ.VÒúÕ!º=«SzÙCíXÍr÷ùGT¨F£äåÑõ	¸ÉÖnxse3¢xî2°ÏD<e#Cll\ÐÎ,rY¤¶p·Ù'Yw\-%¸*UNÒAù¸åCç"=´$a ßFzÿÔ]ÅÑ·çñänÀæ$Îj°É¼9°û@<n~	ó=8 rDê¢³M&æR&5ÂÉæ¤ÙPÏZ$Á8þäCà`ÕrðÁKÏ7ë D®±tÓ¥ A×0Ìô|4»¤âdlú¢5#Îínn"Ö[]kyGï(r¹U½æ-lånë1ëUD²J¡
>h²QÇÿ©~_	,`^òôh<á|HC ¯D/18°ÔNóxqZçº¨7®ñîZ·56t÷ßüî]ïâ»>û!5ù3+ÂÌö]Èr±vrÇÇkÕÞÒ(;øäõwynbPù]ÇÊ+§xzEÊ_¨EPîË§g{'Ïê¿<_ìÕÿy´wækÑ¤\®Ã¡1Þæ¶Mü7Ë%ì*tbÄårå)"v· &¯¡DôÁµ¡Mè
>¶ß¡DÃ\Å4&MUð!|{vptv|vöè}q|òÙÁãÇ{OßÛõÛÏ¶äCÆ¢ñï/ªº\YÂq³|J¼/Lænß	ÙMö],Æ1uÉËÀ³ÜäÙúyçH#^B·ÖndâÎß(p Iß}û³EKAÐ.Jûõe]6ÞÝ}Pä
>k~a¬?ëT?#ê döv/¸WzNÿ<%Ô¯+q#F)Õ×qvnf#ç¢ÝE%Þ©c¸vo4ìÒ)Â"^ÂCä5UÆÈRµÉÔ-ç}p]_ïj©£ýòð" +@ûvÍ¡¢T(Bð·
SsìÁ5Ø«¶=Ä=¶ÐéP¶);	DQ~Ç ÍÝûShYrÔsCç_JÄºq#Ë£'IÈ<DàÄ× fw»Ñ)¦DençÁ9Åón2êV\ë¨»6bß"¤ÜçpBÑÕÃeÑ|nÆ0È+WÒ¸ih5Ï¹¢Ozôñv|öÌ±Û5ÙsEÅáqÐÁOÞGl<l&ÒFö)¨Å^Ê¡Ôû¨ë·ÖÃHWà <üÜSvíb°)é|Oxô9î¸ÒÒ:jÆ>KÞWtÅ%qdc¾ÍTXµð#£v^È-bQ8Â¢i·ÀsÔ«úß-èh
I6kÞÐ÷Îèy(Aîâ¯æÎ)"} iu»²"Å$aÊsBm{WýÆ;¾hG_a¸ÍÄ¥YFµBõKl,yoÔ¡ÙÕô$Çv²cyÆá,3æèÔè!`@üîh
¥*±úa¡½3oØó!6ôªâLñªëk`´~,
BhèN'MÜ´$45bÓ§ÀOÞ@0ûÝFÑÔÕ(_À(]ÁÁCàÉÏ]<ûP"àÁs8#Uj%èPe³
>K=6S®©oÓ,ÑOSÍø^í&H§ÌÈ~ýãaËHUÙS>älÍ·Öí,CÎPk
>½ã»3M4.\!Ï·ÞpA;î±«E?âD_:ñ<àªïÞÓ¡¼ð©þ±(¿¡;ör%WôT3-ý-E¾fLéºðz*¬R"©äuõN«è¨ÄÈöíÛ$fEòWYÿtõ:möÛHÛ§ø0	ähºOT&)¢Ùíû$üÇìQrÊ)¢9ââ@`³ÿ'
>.ÁÄî¹ãú¿&ïV	néÒüÃÒ(íF÷«Û1	ÉW´8jIÎ@©¨Í\DzË"j¿
Ê<NÁ®µw{Ü»|¼M£rm7´:oxÒÿBâTh½¹s1yÓ¨Ò
¬£DNTwn&ªÝszø
>¹*ïR¬»)Ô±æz-úíöý8/~¥6xMm]=ÆwZ¢d®ù¹q0ÁoØügqÚD_ZÃ×ÁÐÑÚß9RBHm
ÌÏ¾sÁWþÄÀç§·j0
>\Íqwr»¦~cÀ)î24©DÜCQ|\º9þê#}DDz9í°ÈÁzg!w2æA¿è5EøRs Ð<6U°!ÃN[ñqáO·Ü¾#[²i¥½Q%Sº'ÝÎß..{Ür{E àº³\oT§Ð¸SKT¶ÌI@t¶~KÝ¸µ&"ú5Ã2Btê%:Õ'Ý{Äu>qu$BR_ÒñîÀd\|éLÛíÕl¾V¹a6îÄøÈ¿©ùª¬ÄÀ}¤)þ=(G,ðW| éEÞ§ëøîCÉ¯òò~8¼CEáþt°Ì½¬ÝËBþNãF&ÙÁ¢_d ÂÌ¾ýÓ)é
>ñ¤6ôax×4Oßq:`£¬CZnçña0ð÷çñÎ¶p¶/íîñRgÇ¹ÐÃ¼>Þ>ð´ÆæÂîæy¾;Öß>Þ5ðÉ
ûyJËæBsÚ àÆöÝî óãZîrþQ+ÃwÌv¢CsÂ§ÕÑì9>¾6}wÁARù£[z0bw0´´¶P,þvÑ¬úª>«6?÷1ñ¸Ô··ëO~½÷
ªg,Ý=jJznò-ÅÃGyê
>&Î^ÓKrl£u=:Ûá)X7ÍÙu3àj4s°;ã«_Ãñrcþ	ÔÑÑ1ûÓ¯áÚÄß¨Édë6ôë¥6GøfÜØAïw;®µôÚp@ñó§*>®C	|Ûzüó¦mKb¹wMÁ<tñ#ÊEçÅ¸hÃöãäÁòQýâô±|RÿðeÇGÀi?|aA÷óçJôxÔ|Ló<>ÿðÆG¢åÏVúæú8OV¸kç89ýfïäÛ¿Â°:?¬¢H¢ò1)ÿxÊîÔ¸wÎæ>¿w÷REØ¤§î÷atCN
>éüÜÏÑ\õ2¢ßó6Oõ;×Ñ/Û:?_U5ÝqA$ÕÕæªóûA^fa)ÐøÊÖvB»ëg¢^ÕVq®¨³ ¿Ôt¤âpEy6íÒlgCãÅ
>xÍõ.ÈTHI>FYÙ6¦Ñ0á²òP¯M&÷QÖæ"¡`éÑd(ó)TÒ¦38wxÙMn¢çCT""Ê¸K;Òù©Ø^D9ß¿ÿà|¿Ü@ÙñÔmÓÇV<å´9cë¯ÅÆðEúGæ-sdA8â§ÿS·µä8
Ñ½Oav %Ø!!ÄH°A«l:NOÒi;;"qÀ¸ÀÝ\zõqÇ!ìÆ§»ÝUÝUõê½á'É¬ÒÜ¦Ä#UEèÐDw]jýð&Zyà~í£(éèj$¹2CàæÛ}Ý 6PJ³xz4O¹¨õ¥-°/<41FÊ{NN><p¶ ß³º¢÷MyëJ÷4»cTõ¢;¡
>mhH6Òó°`ñTÑLåì{T§ôi|Û48á»[Õäu·ÝMºÊ§ßåIþÅd>F²TºMj¼b°É96å[ô¶C¾®ç3HµÒÙñ_µÎ®´á.©A.ß_ÌõQÁëï%6ê.ÓM=¹*2f&IÞ(h ¦hFP(¤ò
>¥¹Ü?.ÏÏe³±£Ì®	mÕQm!Ìì·Ó¿OmE@¡ùú%K±PµF;Ûn^È
>Ä49 ïf|á3K¸FôÜQü8¶T.2]Â>Cú£U·"yúé7#q-Vbðt	,¤ë+Îh¤®8U1HHùx;E]@f¸ûúaüZÓvüýêº/ðpöj
>:ÿÿÔÜé~QîÁêß¤t*)6è-]»v8?£§ûDcB+_Äç/N¢@âq¥½ºïsÒÞTûtÔlhsKfrdTBt$ë>ÏoýàuTLËxÂ&¤;Ã²¬	¿tªõã6¾]Úgæý~6®\(s>½ô½w_>ÑYRß7©¥ }wî<q3«§¬^.½þ7Bâ¬Ó½kÞÚ7Wxb8OIéezu6ëòÁÞý¢'ßänÞ|ÎIiÌìb²EïfßïÑÀ¸:dNu&tÜßê¿$èÕ#ÜMãÌ`?F§ËÝy.þÁûÁcHùwàãö'âîËöómïªyWvªÉZx±ÆA[KG>oþÜC$õ²5 %Jâ¨_ÛÝ²¥q{d3I«XÅa9j.ö £V`½ôiÑ#ÐÁÐi
>ý¿öÈGelUÏ/"£:DÉÉRtÎâOÏuÈ/äÞÝÛ·¿ìÈYy5]æòÎ½ÎèìÉ;¢súT?~#üàó¶Tò©»*¯$Ãké¥RËQ¶ÀU±)~u¿WþtR¾>]ÑéT¯5î4E\^ÁûÆåuz©©ÇR
³¢t¹Ò©,ÊOoÞÈN.u^¾]WùyiÜ]¬Ëë|¢×Ñ]KäWÍÌóåëò}Q^-ªÛ-©fTëp)S+-ù^ëXÆj~gIù>*dCÅ"?Ó£¢)µ(T2SëµêÈ.ñ/ÏQ,.hñgk<0Ãh½ZÎrOQa2"KÏòm¡Bxb9ÕØ/8y´âù¨ï$s>:iIæp
àyä·´$ÿa½Ò9Qù:1S%GÄ{ìYôjE`+p¤ÐHV¦zF¢ëµèäæMR~å Â(æÈ8*ôbªó5zó®Ys#é°6Âä^ãfúrú§ò¯gåk¨ÌþþÑAùúð¥èn¢óõA
>#ð<[o;T*òzEcH¼1¹"5ÝÔl0h&ú¥ØgZúµÞQ:é¾\b½#ÁÚZß¼Á3zoNlHXèº%W
>ûáu*Í¢× X¯'¤
>/
tqó.×±%Ôò
>7'fE°TY2TØkL"£0<)nÞ¡y\^'ÃòjHØçñ±èN:w¼}ëußêé¢3ð¸ÇÃO+KªX!îÕ¦µ(9ÃÕ¢ÒzØ¢JÔ|JìÂô2â-ÑÔx#Ðî%¸\¬²ó÷÷*~ÅMâcÅRò¸áÎm÷·ÍöI®sÚö.Õà-ÁdLÄ}Ï)²3Ã²¬SâXgD¬0®TMEùW×ùBwÙbDÛG*6®bÚeIfj°L £)Z¾Y°ÖÜw53Ò6Xû_è¿|×Òû¾&V²¸î£?ÁC÷e`s]2´½ÊkUìØóµ^ïã(×PäYy½ 5
>cãåtk9HÒòíEDº<#ràÏTàaLÏ>,Âö;µ½öÎdÿôè«¯¾üÃyû®8;y)Ë·åûòçò§ò¯åß¥ó¥Ùb2£òz8»¼y3_ÁÆ£iùñæÝ«¿üù¬Û;ÝÇFN>yÖ/|tðòæ¿)ÿöõóÿXþïÍ?^|ûçíØï>Çùáésñðèàøèùá£þ¡¼ë¯ïwÈþòÛ£GÝÁ££3yé/O_îïw¿ÞïÉûRWº¼Ê·èÿpófM>á>?q2»ðï~Ý{µWþºwøH¾N¾î?Â-ÿ"O{Ïñ²KÑ}ø°wx×Ì&,cVJGY-KAï=|Ú=9E8ïüóÿþíÿ¸}çî½/¾¼ÿû¯þ ö{ÝOz§4OCÞ1vGÿÊä$r*Äñãò|)ïÙ_RÞÆ?V`ÿ_§þº.?ù°üCµªâO5¸oI	pãjýÝpý}o!Ûü¥!	Ú^¨ø~sÄæ:;FlÏÁCFØÙ]ûËÒpKo_ßMºvZ?²øÄÈFVÞñ2¹ÈmèóBÃaôåYW¬*FÄË÷Ã=¼àý=»GX#»ÊqS4fÁ$ßí©áá":~ =nÕªLúNÞ;	®o·£1pJuã|vÔÿª}bÿ>o!à],²<íù»_Þ¡ùöûíG½oºÝ'Ý~ÇìÜ#XÇ´»)'rzý¥ðSwîT£rò=¹¥½T@¢A</<:pv¡åENN¡>"'·ÒrpóffX2N÷ûg§ÏîC@¦"K×r¥	JÖë5ª16W>çðÉI÷ÀL	ÜjæwÁßªWÉ-ÊâÙì"¾ptHïqbæm'2xyy§K7QnDÈ·ý³§Î@ÐScå+å;ldq(
|#j!|µ<à	×¹ÆÊaÆÁa
>}@×ZÍuz¼Ðl1öºZÁ:,@XWc«}«J·$³¯gäoTÿø/5$îÈbõ|2P9ÐG¤`Ò·d=êð»£òãx|óFÌñb=eíYHav5;²üûÔ¦qv1%ÆérÖ¼z%2¹ÈEt.^½
>ñx*cRSøÐÊ%`'h;À½v=ö{/àÒ÷_ô gðZÄYÕ
jÂ<ÀcWMCdc¨½&ÆÕ{ùzi¨^dR5âb¾¾yFq3 ÃSÕ;±$ÉIGe"Ìb#eAü[¼>ì°²¨i/±ÌA{Þ7çèí¡äèzAE
ò¢ìºäÜÒCÀM<7K_ÃNu:ÖCü%á¯
>±o¬fâw°\7ýdûcmB§Ê¦ÕB`x^~HÜÞþÜûÝÓ³ß´äiC¿mQù,qÞæQÊ|Ü¨Ö[yoUÉþÑ#@¡ßBå«ÁogË¬¿£òèpÿeÿÐÑRù0%»È#4S!Â#[i¨áLÑ!_g	LSUª"Hwf:r#ô{E4âeî-§òðù7$©ç2Ø¬`Í.D'å±6\¸áÎÌÌ:u±9h®M§Ù8N:d°ml·a´¦}Ü;9èmÚ±R½m¥*HÚ¤y`ÉÆ59q¸³áÄÈ%Hp»Ud«ÑSfÅ®mjDIÃè$&Ëuðë"H2ÊÒG/Tp"Õñ¦a¾¹Ï3~{5üUÞ´n¾µëtï*G¨êT]Òö$U³fpÓÚG¢©úòR¢Ìji2K¤¡Îl:N"jÖéì@ÉzåhDJ¶Ä¡
>«W¡r±)ÉË·Tîs9¸7Øôýö½¶Ê«ÝÎnÞ¡eØ@Óî	`²V-(î¦.úXÕYðæÚÄÔ£·ÂÅ\ÊçØ¦u<Ð.R`EtlIoC3ÆË,wYÛ
R#ò("âùEF¦3Õ;ZB¡æÛÌÛØÏIy@&l ç¸1£,·\-yÐÄèÈ@ÁmCdWq
ÖúßÃs»ªÛF(,ènR¼§¸Ïª=<'bh6¸Ò	aTÑfpq¢ 
¼òL+@ÖËlK <³L£p?øÍ%vøçÇ[ª ã½Çiµ2¯víq
tD{¤-,tªàÑBwYLü'ÇU°2*G%Ë1àSRÒ$Úx¢¾'ÊÜ¬d¡¹-f\x3"¦I0ÃtBþ/¯¨)"!¤bÙu<Ç¦XØ¥1r0X4Ðgõü¼íGD¤mõrHÍyÍÇ$w;¦jù:²Ð 
>_®OUDaFf¼2ÒWå9àaÁ,D³ÿnº²ç(ÍÒhf·È©ì&Ý2,Õ â³JÕ±Û®ùUãÚRòqåÛwZ6/âk¢a6·TFáÒÅyò=3,#ãt,2(?¨èWù+q]Ç²êü.[£Ö?Ø?R9Óc?Údp]³|i¦ÙqÝÿ-t"Ø¬\<¼aÍ
>	ª&ç½sX(¡Ì	GÆØÆ¾+ÝQEàU/ôÝÇí<@õ¸²û ¤@Zïë8²1ÞÅDnÿô¨MåöÝ¦¡*rõ\#hPDxÆ0®#ûCçÕYDå'èPÉ Å!jÍË7GùKGº=Zæ¸4*bÿ>Ki	wHg:¬Ý¶òÄ
>¶Q@º-ªªÒ÷á¯Ù^LÛ¹LÂ²h[7ëÕÓqÎvþÁB®ûæ#z`¬N3UÂáØÅÝck¬²FØé¬Q×ZfY	zC× "f:ed¡@ôÏÍ³h¥¹"ÆÐ#0ÖpÂíSÙã'>×
N9FÖ¿°@lÍw	C)åaäÙaùLUh¿üõ,Ô¢¶U>(¸4M^
R¤âS~¬vX$ÓÌæ¯BÑÊ2ÙÂ)v±2
{â]
>ðmo~Xªô¦;2BBp+¢Â XÔÒVEuÑl	&
FdE`óD6ÈE>ÁO^7±a²C#ÆÎ'åöö7Bm±[Årè\¾¯çAÕt²H ÈJu½kÚ
>»9½\6¡à~`L¬ÏÅPpì9®-§ÿ`÷¡|5XÃTecÙno2Ê½®¦GH|Õ6Èe/¥/BI¹ åò
>ØÜ¬üy|)ìk*»#	0gÂ>ÂÁ¡Üæ#Èì2TÃ+¬øÜÏÄEO\ëg0ËÀEçQ`gÕ*S8êßýÎ`mÔØ½µ$©6(¢óö¿o-dãËs@h^¿²+ÐYNp¨md»Øê¯·ÙúUÑ×$¹öK¼ý
>Â{þ+-9¬2y~¥]:§X¡äºJ9¤c¥üA2¤eð?\"¡¤eÂt¥¹ý%ñ`¤§Pì°U¶+ YhÜiÒ²n&òkjM	{ÑÄhjå¤ïm8(ôT54:ògÂB\%/o6É&Â>]ðE	/0E¹PIÌ;a6Xe·!lÉ"°ºÁNÈóÓK4ßûíTÇð1ûG°ÝùÂ0ì^½Åò`!
ôS0ªîÅ
>¤ÇÐ$fzQ2óxDåûux'j2þµ¦Û£92ökðÃÐØ¸E@¥Cv=pvk\RR¹Ìö¶ãC%ÒÊT½C ·[ôGçü;Èñ4Â5!YèÏ±¶]²êbXU(*ÇT¿âÁñNk#j¥_¥È)*@ÍHóu¬ùp©¦Ì0W
©:aèÁËÂLtpaà¨ÌcA
µq}¶X_^l'Õ&Ê10"- HË»
>ÄæÆDvàÁ¬L	óÊF§)öàN¸âU&Èèí!sÛwÄAÀIÞÁ Zgéef%á;ÐÆä>NbÖÔ/ó~ÊÑ,×cD2E
µv¢µüN
.ßdP:ÁZò¢:nPËëm4oÛÕ@XéÍßE!(©@f"³g`KºFy5.,SM
ÂÅFoZÕ:æ3½
>®×n¯iaLX\6þ³égpä.]h¬ÜÏDP¬]h°®Rk$YPì_©)hAÝMüñÛ]WèWr¯ñ{nª/rgÃQGr·1,µµwsí*7ïnÒ5@uªû:äðWló0ä)¼¯ÙÌz8ÁàÅ²iª²¦nÞQÒRPgaÕ'ÕrQ²¼¢lÆEgõ¤ùÏ¢i'fþ/ÞÕ¥¸f~ÓÓèbAh£@8©b¬-cµ s7>a¢Ë0öÏè?å\)5ýXÄ}ÏL(¯g¦àèÝÞÐ¸o~ÝB"åÛàoTõªS Iyqüà¸±gBÙy;§#%¬Os]+op&[ÆPh"RT½gX´#zÆsíÓAµ
LUÌk}caÏ
>õ´¶sçªÔÒzÞ-ShèøAè&gÿÇº¥ÖY~Z.h"(ê¨íä¼Å»Ò*c7fÒ@¸íÐ©µæbJ-D
>P/QÿRÇýVå¸hMË	ÃÉÈÒnÝ«ôË½Ì¿ã
>²µ©Ñ[ÃÖ¼J?¦5tåjg²V1Lye];|r§Âbó_òU_ægÛÑÉ	D]Ý2(l±¨IÇ.þÆ@4Z ÎSþ¨,Ð§YEúaðÖû¡i£õ¼"Z&ubi¯Xé}=¾äâÀEÕV±ëmiªlzÌê+Õ¶[t¬nÒ .Cy®¸¨3¨Ì¯g\Ó±¸c0æ÷Äýó¶ÈØ4¶L±,ýøÀ·¬'ZiÔuÀ:ÌÐÐãÝôwÈ1hÀPáúõ¥§É&%Ç»²üT3@Ù(ùýÓLìÈJ¡HÆb×)°!ßv}H½ãÿS«Ñ"¶)¡:Ý-XMMiÜ:|zùØ\1VÚ?e\¢q¿IÉjýX"°º:A*êÉÇ1Ä²§#¶ZÞØ>-oGJõãp4×ÁÿBJ½úôÝ¹~aÎ©Mg}ØKbfeÔmOþ~5O¢WTD4á;Øe¬	þb3÷Uîj6ýlXbwÂZéòGSÐõ©>k"íë/¶î0ÉløÜ¶t¯`;rEi¦¡"6âÁh!h:æÛîË×gþ:µVSr~±êãæSîøòÂ¿ÁZaÌÝßNØãzÃ»èC²RÙ¤É}Äa-½öý¬}¿!LÃ9Ó8Ô\wÙµ®*Tb[!¯%ä|Å'BæàpóÑeôÕÙXða»þ8/çÈô(Ëe´Q¸Æo2ä±*.³Y¥·n¯tb]~Î´cÃøðIN8%Íq;¢¢«á<W"ÓÈzÚnÈoÚ·±ä®ðg?bY
HÍ·1Âv±ºNÙ±RC`í¸ü~ÓWFAç}%V¾>}$ÊÐw*gibñßÁ#·èñ$øoD»/ix,Y¼¤l«¼"Xi>+ÿvrVþxØ;£óå)t¢¢ÊK[wÙºé§
l Ïô
>2yªÓá"ºsÖµùKKQ0âòN|¯m>C@ÈÈ¤µo¯äø2[ä°÷%Çßh¨§à¸8føØATí5ÜdúG=æðTÚ¶dr³ÕW4¾^¯ÐoT§áKÄèb]åk>û
7È6ìínÑ·!,áÅùÉ¯÷/°*(ÛòíU( É·éÔ4aVÜCVJ"h1mÕøÑ²
µ¿b&åÓÜ¾¼RðÒY.j0¼çløµôrU.coÛWn(
>|+¸ÿ¹ùÙ¤[a3GpdaÎ}9´°>Çw¨ËJØwÂÏÝ@}ª
&°Jü³¡GgéÐJ$l;i¡±ÿ³Y°j!ñ6$ÍeñÄ!;+\<½ySP§?5
>/¿{gp¹\ùIE9Ó-öéÕ!®²-ª<l¦¡ãøÊu§Zìªo£¡×.bRjÃðú)c à`â±Oÿô:h2Çê>u ògoÀ5<éÐGMÆô6úå¢?¸u+3·Fù¨3ùÿ¾Aî9EÖ.9@÷Î!«j !¨TnÓÖïÅjÀÆ8öó¿à¬×]éþ½dv¶b8{Æ¡îgÒ_Ù9xÉe3s´Ý4¾)Þêr°Wzs=wPÏf¼ÈkY*w,÷^EP#°Pù5(´ è-Tjë0ÇM1ØuÛz/ìªË:¢`g~Õá±ær7s<ÊYð¥¶XS
Ñ¡Á[¿ò¦V ªcßÝç:Õ=û9¥ð'$Ï=
>osimg: //dev/live-osimg
>size: 4294967296.0
>
>
>Anaconda instance, containing members:
>rescue_mount: True
>intf: InstallInterface instance, containing members:
>  intf.ppw: InstallProgressWindow instance, containing members:
>    intf.ppw.pixmaps: [progress_first.png]
>    intf.ppw.intf: Already dumped
>    intf.ppw.adbox: <gtk.EventBox object at 0xa9ed2d4 (GtkEventBox at 0xa18bb90)>
>    intf.ppw._updateChange: 0.01
>    intf.ppw.adpix: <gtk.Image object at 0xa9e7f2c (GtkImage at 0xaa71538)>
>    intf.ppw._showPercentage: False
>    intf.ppw.infolabel: <WrappingLabel object at 0xa9ed054 (GtkLabel at 0xa94fca8)>
>    intf.ppw.ics: InstallControlState instance, containing members:
>      intf.ppw.ics.prevEnabled: False
>      intf.ppw.ics.cw: InstallControlWindow instance, containing members:
>        intf.ppw.ics.cw.handle: 1239
>        intf.ppw.ics.cw.currentWindow: Already dumped
>        intf.ppw.ics.cw.mainxml: <glade.XML object at 0xa3fe9dc (PyGladeXML at 0xa237998)>
>        intf.ppw.ics.cw.window: <gtk.Window object at 0xa3feb1c (GtkWindow at 0xa1960f8)>
>        intf.ppw.ics.cw.installFrame: <gtk.Frame object at 0xa3fea2c (GtkFrame at 0xa222970)>
>        intf.ppw.ics.cw.anaconda: Already dumped
>        intf.ppw.ics.cw.reloadRcQueued: 0
>      intf.ppw.ics.nextEnabled: False
>      intf.ppw.ics.grabNext: True
>      intf.ppw.ics.title: Installing Packages
>    intf.ppw.progress: <gtk.ProgressBar object at 0xa9ed07c (GtkProgressBar at 0xaa89238)>
>  intf.icw: Already dumped
>  intf.runres: 800x600
>  intf.anaconda: Already dumped
>rescue: False
>updateSrc: None
>mediaDevice: None
>methodstr: livecd:///dev/live-osimg
>dispatch: <dispatch.Dispatcher object at 0xa3fc9ac>
>rootPath: /mnt/sysimage
>isKickstart: False
>_loaderMethodstr: livecd:///dev/live-osimg
>id: InstallData instance, containing members:
>  id.firewall: Firewall instance, containing members:
>    id.firewall.portlist: [22:tcp]
>    id.firewall.trustdevs: []
>    id.firewall.enabled: 1
>  id.anaconda: Already dumped
>  id.instProgress: Already dumped
>  id.upgradeRoot: None
>  id.xsetup: XSetup instance, containing members:
>    id.xsetup.skipx: 0
>    id.xsetup.xserver: XServer instance, containing members:
>      id.xsetup.xserver.videohw: primary: 0
>vidCards: [<rhpxl.videocard.VideoCard instance at 0xa2605ac>]
>Primary Video Card Info:
>device: None
>driver : nv
>descr : nVidia Corporation NV25 [GeForce4 Ti 4200]
>vidRam: None
>
>      id.xsetup.xserver.serverflags: [vt6, -config, /tmp/XConfig.test, -s, 1440, -dpms, -v, -ac, -nolisten, tcp]
>      id.xsetup.xserver.resolution: 800x600
>      id.xsetup.xserver.root: /
>      id.xsetup.xserver.hwstate: XF86HardwareState instance, containing members:
>        id.xsetup.xserver.hwstate.videocard_PCIFn: None
>        id.xsetup.xserver.hwstate.monitor: monName: None
>monID: Unprobed Monitor
>monHoriz: None
>monVert: None
>physicalWidth: 0
>physicalHeight: 0
>
>        id.xsetup.xserver.hwstate.config_resolutions: []
>        id.xsetup.xserver.hwstate.videocard_name: nVidia Corporation NV25 [GeForce4 Ti 4200]
>        id.xsetup.xserver.hwstate.monitor_name: Unknown monitor
>        id.xsetup.xserver.hwstate.video_ram: 0
>        id.xsetup.xserver.hwstate.videocard: Already dumped
>        id.xsetup.xserver.hwstate.videocard_driver: nv
>        id.xsetup.xserver.hwstate.videocard_options: []
>        id.xsetup.xserver.hwstate.all_resolutions: [640x480, 800x480, 800x512, 800x600, 848x480, 854x480, 1024x600, 1024x768, 1152x768, 1152x864, 1200x900, 1280x720, 1280x800, 1280x854, 1280x960, 1280x1024, 1360x768, 1400x900, 1400x1050, 1440x900, 1600x1024, 1600x1200, 1680x1050, 1920x1080, 1920x1200, 1920x1440, 2048x1536, 2560x1600]
>        id.xsetup.xserver.hwstate.hsync: 31.5-37.9
>        id.xsetup.xserver.hwstate.vsync: 50-70
>        id.xsetup.xserver.hwstate.probed_video_ram: 0
>        id.xsetup.xserver.hwstate.videocard_PCIBus: None
>        id.xsetup.xserver.hwstate.colordepth: 24
>        id.xsetup.xserver.hwstate.videocard_PCIDev: None
>        id.xsetup.xserver.hwstate.resolution: 800x600
>        id.xsetup.xserver.hwstate.dri_enabled: 0
>        id.xsetup.xserver.hwstate.xconfig: None
>      id.xsetup.xserver.monitorhw: Already dumped
>      id.xsetup.xserver.keyboard: None
>      id.xsetup.xserver.mousehw: None
>      id.xsetup.xserver.defaultdepth: 24
>      id.xsetup.xserver.logfile: /dev/null
>      id.xsetup.xserver.config: None
>      id.xsetup.xserver.display: :9
>    id.xsetup.anaconda: Already dumped
>  id.keyboard: Keyboard instance, containing members:
>    id.keyboard.info: {'KEYBOARDTYPE': pc, 'KEYTABLE': de-latin1-nodeadkeys}
>    id.keyboard.type: PC
>    id.keyboard.beenset: 1
>    id.keyboard._mods: KeyboardModels instance, containing members:
>  id.timezone: Timezone instance, containing members:
>    id.timezone.utc: False
>    id.timezone.tz: Europe/Berlin
>  id.zfcp: ZFCP instance, containing members:
>    id.zfcp.hasReadConfig: True
>    id.zfcp.fcpdevs: []
>  id.upgrade: None
>  id.monitor: Already dumped
>  id.iscsi: <iscsi.iscsi object at 0xa3fc94c>
>  id.methodstr: livecd:///dev/live-osimg
>  id.fsset: FileSystemSet instance, containing members:
>    id.fsset.messageWindow: <bound method InstallInterface.messageWindow of <gui.InstallInterface instance at 0xa2608ec>>
>    id.fsset.volumesCreated: 1
>    id.fsset.progressWindow: <bound method InstallInterface.progressWindow of <gui.InstallInterface instance at 0xa2608ec>>
>    id.fsset.migratedfs: 1
>    id.fsset.waitWindow: <bound method InstallInterface.waitWindow of <gui.InstallInterface instance at 0xa2608ec>>
>    id.fsset.entries: [fsentry -- device: sdb1   mountpoint: /
>  fsystem: ext3 format: True
>  ismounted: 0  options: 'defaults'
>  label: / fsprofile: None
>
>, fsentry -- device: shm   mountpoint: /dev/shm
>  fsystem: tmpfs format: 0
>  ismounted: 0  options: 'defaults'
>  label: None fsprofile: None
>
>, fsentry -- device: devpts   mountpoint: /dev/pts
>  fsystem: devpts format: 0
>  ismounted: 0  options: 'gid=5,mode=620'
>  label: None fsprofile: None
>
>, fsentry -- device: sys   mountpoint: /sys
>  fsystem: sysfs format: 0
>  ismounted: 0  options: 'defaults'
>  label: None fsprofile: None
>
>, fsentry -- device: proc   mountpoint: /proc
>  fsystem: proc format: 0
>  ismounted: 0  options: 'defaults'
>  label: None fsprofile: None
>
>, fsentry -- device: sda10   mountpoint: None
>  fsystem: ntfs format: 0
>  ismounted: 0  options: 'defaults'
>  label: None fsprofile: None
>
>, fsentry -- device: sda1   mountpoint: None
>  fsystem: ntfs format: 0
>  ismounted: 0  options: 'defaults'
>  label: None fsprofile: None
>
>, fsentry -- device: sda8   mountpoint: swap
>  fsystem: swap format: 0
>  ismounted: 1  options: 'defaults'
>  label: SWAP fsprofile: None
>
>, fsentry -- device: sdc1   mountpoint: None
>  fsystem: foreign format: 0
>  ismounted: 0  options: 'defaults'
>  label: None fsprofile: None
>
>, fsentry -- device: sdc2   mountpoint: swap
>  fsystem: swap format: 0
>  ismounted: 1  options: 'defaults'
>  label: SWAP-sda21 fsprofile: None
>
>, fsentry -- device: sdb4   mountpoint: None
>  fsystem: foreign format: 0
>  ismounted: 0  options: 'defaults'
>  label: None fsprofile: None
>
>, fsentry -- device: sdb2   mountpoint: swap
>  fsystem: swap format: True
>  ismounted: 1  options: 'defaults'
>  label: SWAP-sdb2 fsprofile: None
>
>]
>    id.fsset.mountcount: 5
>  id.desktop: Desktop instance, containing members:
>    id.desktop.info: {}
>    id.desktop.runlevel: 3
>  id.rootParts: None
>  id.x_already_set: 1
>  id.backend: LiveCDCopyBackend instance, containing members:
>    id.backend.modeText: 
>    id.backend.instPath: /mnt/sysimage
>    id.backend.skipFormatRoot: True
>    id.backend.instLog: None
>    id.backend.supportsUpgrades: False
>    id.backend.osimg: //dev/live-osimg
>    id.backend.supportsPackageSelection: False
>  id.firstboot: 0
>  id.diskset: DiskSet instance, containing members:
>    id.diskset.initializedDisks: {sda: True, sdb: True, sdc: True}
>    id.diskset.disks: {sda: <PedDisk object at 0xa2933f8>, sdb: <PedDisk object at 0x9ee6ce0>, sdc: <PedDisk object at 0xa28e338>}
>    id.diskset.anaconda: Already dumped
>    id.diskset.onlyPrimary: None
>  id.users: None
>  id.displayMode: g
>  id.auth: --enableshadow --passalgo=sha512
>  id.ksdata: None
>  id.bootloader: x86BootloaderInfo instance, containing members:
>    id.bootloader._configdir: /boot/grub
>    id.bootloader.doUpgradeOnly: 0
>    id.bootloader.above1024: 0
>    id.bootloader.defaultDevice: partition
>    id.bootloader.pure: None
>    id.bootloader.serialDevice: None
>    id.bootloader.args: KernelArguments instance, containing members:
>      id.bootloader.args.args: 
>    id.bootloader.kernelLocation: /boot/
>    id.bootloader.timeout: None
>    id.bootloader._configname: grub.conf
>    id.bootloader.device: sdb1
>    id.bootloader.kickstart: 0
>    id.bootloader.serialOptions: None
>    id.bootloader.useGrubVal: 1
>    id.bootloader._drivelist: [sda, sdb, sdc]
>    id.bootloader.images: BootImages instance, containing members:
>      id.bootloader.images.default: sdb1
>      id.bootloader.images.images: {'sdb1': ('linux', 'Fedora', 'ext3')}
>    id.bootloader.drivelist: [sda, sdb, sdc]
>    id.bootloader.serial: 0
>    id.bootloader.password: None
>    id.bootloader.forceLBA32: 0
>  id.extraModules: []
>  id.network: Network instance, containing members:
>    id.network.hostname: localhost.localdomain
>    id.network.overrideDHCPhostname: 1
>    id.network.netdevices: {eth1: DEVICE=eth1
>BOOTPROTO=dhcp
>HWADDR=00:19:db:48:79:4f
>ONBOOT=yes
>
>, eth0: DEVICE=eth0
>BOOTPROTO=dhcp
>HWADDR=00:c0:26:01:10:34
>ONBOOT=no
>
>}
>    id.network.primaryNS: None
>    id.network.firstnetdevice: eth1
>    id.network.isConfigured: 0
>    id.network.domains: []
>    id.network.secondaryNS: None
>    id.network.gateway: None
>  id.instClass: <installclass.DefaultInstall object at 0x9e3412c>
>  id.partitions: Partitions instance, containing members:
>    id.partitions.useFdisk: 0
>    id.partitions.isKickstart: 0
>    id.partitions.globalPassphrase: 
>    id.partitions.autoClearPartType: 0
>    id.partitions.autoEncryptPass: 
>    id.partitions.nextUniqueID: 20
>    id.partitions.reinitializeDisks: 0
>    id.partitions.autoClearPartDrives: []
>    id.partitions.protected: [sdd1]
>    id.partitions.useAutopartitioning: 1
>    id.partitions.anaconda: Already dumped
>    id.partitions.zeroMbr: 0
>    id.partitions.encryptedDevices: {}
>    id.partitions.requests: [PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      fsprofile: None
>      resizable: True
>      format: True
>      migrate: 0
>      origfstype: ext3FileSystem instance, containing members:
>        origfstype.partedPartitionFlags: []
>        origfstype.checked: 1
>        origfstype.name: ext3
>        origfstype.migratetofs: None
>        origfstype.deviceArguments: {}
>        origfstype.linuxnativefs: 1
>        origfstype.resizable: True
>        origfstype.fsprofile: None
>        origfstype.needProgram: None
>        origfstype.maxSizeMB: 8388608
>        origfstype.supported: -1
>        origfstype.defaultOptions: defaults
>        origfstype.fsProfileSpecifier: -T
>        origfstype.packages: [e2fsprogs]
>        origfstype.supportsFsProfiles: True
>        origfstype.extraFormatArgs: [-j]
>        origfstype.formattable: 1
>        origfstype.partedFileSystemType: <PedFileSystemType object at 0x9b5cce0>
>        origfstype.maxLabelChars: 16
>      primary: None
>      fsopts: None
>      preexist: 1
>      fslabel: /1
>      uniqueID: 9
>      device: sdb1
>      mountpoint: /
>      requestSize: 5153.63378906
>      grow: 0
>      size: 5153.63378906
>      targetSize: None
>      end: 10554704
>      encryption: None
>      drive: sdb
>      dev: PartitionDevice instance, containing members:
>        dev.isSetup: 0
>        dev.deviceOptions: 
>        dev.crypto: None
>        dev.label: None
>        dev.device: sdb1
>        dev.doLabel: 1
>      maxSizeMB: None
>      start: 63
>      protected: 0
>      maxResizeSize: 5153.0
>      multidrive: None
>      ignoreBootConstraints: 0
>      type: 1
>      fstype: Already dumped
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: NTFSFileSystem instance, containing members:
>        origfstype.partedPartitionFlags: []
>        origfstype.checked: 0
>        origfstype.name: ntfs
>        origfstype.migratetofs: None
>        origfstype.deviceArguments: {}
>        origfstype.linuxnativefs: 0
>        origfstype.resizable: True
>        origfstype.fsprofile: None
>        origfstype.needProgram: None
>        origfstype.maxSizeMB: 8388608
>        origfstype.supported: -1
>        origfstype.defaultOptions: defaults
>        origfstype.fsProfileSpecifier: None
>        origfstype.packages: []
>        origfstype.supportsFsProfiles: False
>        origfstype.extraFormatArgs: []
>        origfstype.formattable: 0
>        origfstype.partedFileSystemType: <PedFileSystemType object at 0x9c31320>
>        origfstype.maxLabelChars: 16
>      primary: None
>      drive: sda
>      dev: PartitionDevice instance, containing members:
>        dev.isSetup: 0
>        dev.deviceOptions: 
>        dev.crypto: None
>        dev.label: None
>        dev.device: sda10
>        dev.doLabel: 1
>      uniqueID: 8
>      mountpoint: None
>      requestSize: 24999.5566406
>      size: 24999.5566406
>      end: 488392064
>      encryption: None
>      grow: 0
>      start: 437192973
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sda10
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: None
>      protected: 0
>      maxResizeSize: 24999.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: Already dumped
>      primary: None
>      drive: sdc
>      dev: None
>      uniqueID: 17
>      mountpoint: None
>      requestSize: 6000.78076172
>      size: 6000.78076172
>      end: 25623674
>      encryption: None
>      grow: 0
>      start: 13334076
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sdc5
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: none
>      protected: 0
>      maxResizeSize: 6000.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: Already dumped
>      primary: None
>      drive: sdb
>      dev: None
>      uniqueID: 11
>      mountpoint: None
>      requestSize: 101441.689453
>      size: 101441.689453
>      end: 220411799
>      encryption: None
>      grow: 0
>      start: 12659220
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sdb3
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: backup
>      protected: 0
>      maxResizeSize: 101441.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: xfsFileSystem instance, containing members:
>        origfstype.partedPartitionFlags: []
>        origfstype.checked: 1
>        origfstype.name: xfs
>        origfstype.migratetofs: None
>        origfstype.deviceArguments: {}
>        origfstype.linuxnativefs: 1
>        origfstype.resizable: False
>        origfstype.fsprofile: None
>        origfstype.needProgram: mkfs.xfs
>        origfstype.maxSizeMB: 16777216
>        origfstype.supported: 0
>        origfstype.defaultOptions: defaults
>        origfstype.fsProfileSpecifier: None
>        origfstype.packages: [xfsprogs]
>        origfstype.supportsFsProfiles: False
>        origfstype.extraFormatArgs: []
>        origfstype.formattable: 1
>        origfstype.partedFileSystemType: <PedFileSystemType object at 0x9b5caa0>
>        origfstype.maxLabelChars: 12
>      primary: None
>      drive: sdc
>      dev: None
>      uniqueID: 18
>      mountpoint: None
>      requestSize: 38813.2602539
>      size: 38813.2602539
>      end: 105113294
>      encryption: None
>      grow: 0
>      start: 25623738
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sdc6
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: weiteres
>      protected: 0
>      maxResizeSize: 38813.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: Already dumped
>      primary: None
>      drive: sdc
>      dev: None
>      uniqueID: 19
>      mountpoint: None
>      requestSize: 24991.7124023
>      size: 24991.7124023
>      end: 156296384
>      encryption: None
>      grow: 0
>      start: 105113358
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sdc7
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: fedora_backup
>      protected: 0
>      maxResizeSize: 24991.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: Already dumped
>      primary: None
>      drive: sda
>      dev: PartitionDevice instance, containing members:
>        dev.isSetup: 0
>        dev.deviceOptions: 
>        dev.crypto: None
>        dev.label: None
>        dev.device: sda1
>        dev.doLabel: 1
>      uniqueID: 1
>      mountpoint: None
>      requestSize: 7436.30712891
>      size: 7436.30712891
>      end: 15229619
>      encryption: None
>      grow: 0
>      start: 63
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sda1
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: None
>      protected: 0
>      maxResizeSize: 7436.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: None
>      primary: None
>      drive: sda
>      dev: None
>      uniqueID: 2
>      mountpoint: None
>      requestSize: 231036.350098
>      size: 231036.350098
>      end: 488392064
>      encryption: None
>      grow: 0
>      start: 15229620
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: None
>      preexist: 1
>      device: sda2
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: None
>      protected: 0
>      maxResizeSize: 231036.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: Already dumped
>      primary: None
>      drive: sda
>      dev: None
>      uniqueID: 3
>      mountpoint: None
>      requestSize: 9601.28613281
>      size: 9601.28613281
>      end: 34893179
>      encryption: None
>      grow: 0
>      start: 15229746
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sda5
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: fedora
>      protected: 0
>      maxResizeSize: 9601.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: Already dumped
>      primary: None
>      drive: sda
>      dev: None
>      uniqueID: 4
>      mountpoint: None
>      requestSize: 10001.3730469
>      size: 10001.3730469
>      end: 55376054
>      encryption: None
>      grow: 0
>      start: 34893243
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sda6
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: rawhide
>      protected: 0
>      maxResizeSize: 10001.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: Already dumped
>      primary: None
>      drive: sda
>      dev: None
>      uniqueID: 5
>      mountpoint: None
>      requestSize: 4400.58691406
>      size: 4400.58691406
>      end: 64388519
>      encryption: None
>      grow: 0
>      start: 55376118
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sda7
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: fedora_home
>      protected: 0
>      maxResizeSize: 4400.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: swapFileSystem instance, containing members:
>        origfstype.partedPartitionFlags: []
>        origfstype.checked: 0
>        origfstype.name: swap
>        origfstype.migratetofs: None
>        origfstype.deviceArguments: {}
>        origfstype.linuxnativefs: 1
>        origfstype.resizable: False
>        origfstype.fsprofile: None
>        origfstype.needProgram: None
>        origfstype.maxSizeMB: 8388608
>        origfstype.supported: 1
>        origfstype.defaultOptions: defaults
>        origfstype.fsProfileSpecifier: None
>        origfstype.packages: []
>        origfstype.supportsFsProfiles: False
>        origfstype.extraFormatArgs: []
>        origfstype.formattable: 1
>        origfstype.partedFileSystemType: <PedFileSystemType object at 0x9c310e0>
>        origfstype.maxLabelChars: 15
>      primary: None
>      drive: sda
>      dev: PartitionDevice instance, containing members:
>        dev.isSetup: 0
>        dev.deviceOptions: 
>        dev.crypto: None
>        dev.label: None
>        dev.device: sda8
>        dev.doLabel: 1
>      uniqueID: 6
>      mountpoint: None
>      requestSize: 2494.43701172
>      size: 2494.43701172
>      end: 69497189
>      encryption: None
>      grow: 0
>      start: 64388583
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sda8
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: None
>      protected: 0
>      maxResizeSize: 2494.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: Already dumped
>      primary: None
>      drive: sda
>      dev: None
>      uniqueID: 7
>      mountpoint: None
>      requestSize: 179538.89502
>      size: 179538.89502
>      end: 437192909
>      encryption: None
>      grow: 0
>      start: 69497253
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sda9
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: daten
>      protected: 0
>      maxResizeSize: 179538.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: ForeignFileSystem instance, containing members:
>        origfstype.partedPartitionFlags: []
>        origfstype.checked: 0
>        origfstype.name: foreign
>        origfstype.migratetofs: None
>        origfstype.deviceArguments: {}
>        origfstype.linuxnativefs: 0
>        origfstype.resizable: False
>        origfstype.fsprofile: None
>        origfstype.needProgram: None
>        origfstype.maxSizeMB: 8388608
>        origfstype.supported: -1
>        origfstype.defaultOptions: defaults
>        origfstype.fsProfileSpecifier: None
>        origfstype.packages: []
>        origfstype.supportsFsProfiles: False
>        origfstype.extraFormatArgs: []
>        origfstype.formattable: 0
>        origfstype.partedFileSystemType: None
>        origfstype.maxLabelChars: 16
>      primary: None
>      drive: sdc
>      dev: PartitionDevice instance, containing members:
>        dev.isSetup: 0
>        dev.deviceOptions: 
>        dev.crypto: None
>        dev.label: None
>        dev.device: sdc1
>        dev.doLabel: 1
>      uniqueID: 13
>      mountpoint: None
>      requestSize: 6000.71923828
>      size: 6000.71923828
>      end: 12289535
>      encryption: None
>      grow: 0
>      start: 63
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sdc1
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: None
>      protected: 0
>      maxResizeSize: 6000.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: None
>      primary: None
>      drive: sdc
>      dev: None
>      uniqueID: 14
>      mountpoint: None
>      requestSize: 0.09228515625
>      size: 0.09228515625
>      end: 12289724
>      encryption: None
>      grow: 0
>      start: 12289536
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: None
>      preexist: 1
>      device: sdc-1
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: None
>      protected: 0
>      maxResizeSize: 0.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: Already dumped
>      primary: None
>      drive: sdc
>      dev: PartitionDevice instance, containing members:
>        dev.isSetup: 0
>        dev.deviceOptions: 
>        dev.crypto: None
>        dev.label: None
>        dev.device: sdc2
>        dev.doLabel: 1
>      uniqueID: 15
>      mountpoint: None
>      requestSize: 509.875488281
>      size: 509.875488281
>      end: 13333949
>      encryption: None
>      grow: 0
>      start: 12289725
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sdc2
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: None
>      protected: 0
>      maxResizeSize: 509.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: None
>      primary: None
>      drive: sdc
>      dev: None
>      uniqueID: 16
>      mountpoint: None
>      requestSize: 69805.8764648
>      size: 69805.8764648
>      end: 156296384
>      encryption: None
>      grow: 0
>      start: 13333950
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: None
>      preexist: 1
>      device: sdc3
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: None
>      protected: 0
>      maxResizeSize: 69805.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      migrate: None
>      origfstype: Already dumped
>      primary: None
>      drive: sdb
>      dev: PartitionDevice instance, containing members:
>        dev.isSetup: 0
>        dev.deviceOptions: 
>        dev.crypto: None
>        dev.label: None
>        dev.device: sdb4
>        dev.doLabel: 1
>      uniqueID: 12
>      mountpoint: None
>      requestSize: 45002.3950195
>      size: 45002.3950195
>      end: 312576704
>      encryption: None
>      grow: 0
>      start: 220411800
>      ignoreBootConstraints: 0
>      type: 1
>      resizable: True
>      format: None
>      fsopts: None
>      fstype: Already dumped
>      preexist: 1
>      device: sdb4
>      maxSizeMB: None
>      targetSize: None
>      fsprofile: None
>      fslabel: None
>      protected: 0
>      maxResizeSize: 45002.0
>      multidrive: None
>, PreexistingPartitionSpec instance, containing members:
>      currentDrive: None
>      fsprofile: None
>      resizable: True
>      format: True
>      migrate: 0
>      origfstype: Already dumped
>      primary: None
>      fsopts: None
>      preexist: 1
>      fslabel: None
>      uniqueID: 10
>      device: sdb2
>      mountpoint: None
>      requestSize: 1027.59521484
>      grow: 0
>      size: 1027.59521484
>      targetSize: None
>      end: 12659219
>      encryption: None
>      drive: sdb
>      dev: PartitionDevice instance, containing members:
>        dev.isSetup: 0
>        dev.deviceOptions: 
>        dev.crypto: None
>        dev.label: None
>        dev.device: sdb2
>        dev.doLabel: 1
>      maxSizeMB: None
>      start: 10554705
>      protected: 0
>      maxResizeSize: 1027.0
>      multidrive: None
>      ignoreBootConstraints: 0
>      type: 1
>      fstype: Already dumped
>]
>    id.partitions.autoEncrypt: False
>    id.partitions.autoPartitionRequests: [New Part Request -- mountpoint: None uniqueID: None
>  type: physical volume (LVM)  format: 1 
>  device: None drive: None  primary: None
>  size: 0  grow: 1  maxsize: None
>  start: None  end: None  migrate: None    fslabel: None  origfstype: None
>  options: 'None'
>  fsprofile: None  encryption: None
>, VG Request -- name: lvm  uniqueID: None
>  format: 1 pesize: 32768  
>  physvols: []
>, LV Request -- mountpoint: /  uniqueID: None
>  type: ext3  format: 1
>  size: 1024  lvname: LogVol00  volgroup: lvm
>  options: 'None'  fsprofile: None  encryption: 'None'
>, New Part Request -- mountpoint: /boot uniqueID: None
>  type: ext3  format: 1 
>  device: None drive: None  primary: None
>  size: 200  grow: 0  maxsize: None
>  start: None  end: None  migrate: None    fslabel: None  origfstype: None
>  options: 'None'
>  fsprofile: None  encryption: None
>, LV Request -- mountpoint: None  uniqueID: None
>  type: swap  format: 1
>  size: 1000  lvname: LogVol01  volgroup: lvm
>  options: 'None'  fsprofile: None  encryption: 'None'
>]
>    id.partitions.deletes: []
>  id.isHeadless: 0
>  id.videocard: Already dumped
>  id.instLanguage: Language instance, containing members:
>    id.instLanguage.targetLang: None
>    id.instLanguage.default: en_US.UTF-8
>    id.instLanguage.displayMode: g
>    id.instLanguage.current: en_US.UTF-8
>  id.security: Security instance, containing members:
>    id.security.selinux: 1
>  id.upgradeSwapInfo: None
>dir: 1
>backend: Already dumped
>
>
>/tmp/anaconda.log:
>17:21:07 INFO    : using only installclass _Fedora
>17:21:07 INFO    : anaconda called with cmdline = ['/usr/sbin/anaconda', '--method=livecd:///dev/live-osimg', '--lang', 'en_US.UTF-8']
>17:21:07 INFO    : Display mode = g
>17:21:07 INFO    : Method = livecd:///dev/live-osimg
>17:21:13 INFO    : Starting graphical installation...
>17:21:13 INFO    : Detected 2032M of memory
>17:21:13 INFO    : Swap attempt of 1000M to 2000M
>17:21:13 WARNING : step installtype does not exist
>17:21:13 WARNING : step confirminstall does not exist
>17:21:13 WARNING : step complete does not exist
>17:21:13 INFO    : moving (1) to step welcome
>17:23:21 INFO    : moving (1) to step betanag
>17:23:23 INFO    : moving (1) to step keyboard
>17:23:27 INFO    : moving (1) to step networkdevicecheck
>17:23:27 INFO    : moving (1) to step network
>17:23:32 INFO    : moving (1) to step timezone
>17:23:38 INFO    : moving (1) to step accounts
>17:23:44 INFO    : moving (1) to step partitionobjinit
>17:23:44 INFO    : no /tmp/fcpconfig; not configuring zfcp
>17:23:44 DEBUG   : starting mpaths
>17:23:44 INFO    : sdd looks to be the live device; ignoring
>17:23:44 DEBUG   : self.driveList(): [u'sda', u'sdb', u'sdc']
>17:23:44 DEBUG   : DiskSet.skippedDisks: []
>17:23:44 DEBUG   : DiskSet.skippedDisks: []
>17:23:44 DEBUG   : starting all mpaths on drives [u'sda', u'sdb', u'sdc']
>17:23:44 DEBUG   : scanning for multipath on drives [u'sda', u'sdb', u'sdc']
>17:23:44 DEBUG   : loading bdevid modules from: '/tmp/updates/bdevid/:/mnt/source/RHupdates/bdevid/:/lib/bdevid/:/usr/lib/bdevid/'
>17:23:44 DEBUG   : mpaths: []
>17:23:44 DEBUG   : done starting mpaths.  Drivelist: [u'sda', u'sdb', u'sdc']
>17:23:44 DEBUG   : starting dmraids
>17:23:44 DEBUG   : self.driveList(): [u'sda', u'sdb', u'sdc']
>17:23:44 DEBUG   : DiskSet.skippedDisks: []
>17:23:44 DEBUG   : DiskSet.skippedDisks: []
>17:23:44 DEBUG   : starting all dmraids on drives [u'sda', u'sdb', u'sdc']
>17:23:44 DEBUG   : scanning for dmraid on drives [u'sda', u'sdb', u'sdc']
>17:23:44 DEBUG   : done starting dmraids.  Drivelist: [u'sda', u'sdb', u'sdc']
>17:23:44 DEBUG   : adding drive sda to disk list
>17:23:44 DEBUG   : adding drive sdb to disk list
>17:23:45 DEBUG   : adding drive sdc to disk list
>17:23:45 INFO    : going to get passphrase for encrypted device sdb4
>17:23:49 INFO    : skipping passphrase for sdb4
>17:23:52 INFO    : sdd1 is a protected partition
>17:23:52 INFO    : no request, probably a removable drive
>17:23:52 INFO    : moving (1) to step parttype
>17:23:55 INFO    : moving (1) to step partition
>17:23:58 INFO    : used size of /dev/sdb1 is 2281.0
>17:24:03 DEBUG   : adding drive sda to disk list
>17:24:03 DEBUG   : adding drive sdb to disk list
>17:24:04 DEBUG   : adding drive sdc to disk list
>17:24:08 DEBUG   : adding drive sda to disk list
>17:24:08 DEBUG   : adding drive sdb to disk list
>17:24:09 DEBUG   : adding drive sdc to disk list
>17:24:11 INFO    : moving (1) to step partitiondone
>17:24:12 INFO    : moving (1) to step migratefilesystems
>17:24:12 INFO    : moving (1) to step enablefilesystems
>17:24:13 INFO    : disk.commit() for /dev/sda
>17:24:13 INFO    : disk.commit() for /dev/sdb
>17:24:13 INFO    : disk.commit() for /dev/sdc
>17:24:14 DEBUG   : adding drive sda to disk list
>17:24:14 DEBUG   : adding drive sdb to disk list
>17:24:14 DEBUG   : adding drive sdc to disk list
>17:24:16 INFO    : formatting swap as swap
>17:24:16 DEBUG   : adding drive sda to disk list
>17:24:16 DEBUG   : adding drive sdb to disk list
>17:24:17 DEBUG   : adding drive sdc to disk list
>17:24:18 INFO    : trying to mount sys on /sys
>17:24:18 INFO    : set SELinux context for mountpoint /sys to False
>17:24:18 DEBUG   : mounting sys on /mnt/sysimage//sys as sysfs
>17:24:18 DEBUG   : isys.py:mount()- going to mount sys on /mnt/sysimage/sys with options defaults
>17:24:18 INFO    : set SELinux context for newly mounted filesystem root at /sys to False
>17:24:18 INFO    : trying to mount proc on /proc
>17:24:18 INFO    : set SELinux context for mountpoint /proc to False
>17:24:18 DEBUG   : mounting proc on /mnt/sysimage//proc as proc
>17:24:18 DEBUG   : isys.py:mount()- going to mount proc on /mnt/sysimage/proc with options defaults
>17:24:18 INFO    : set SELinux context for newly mounted filesystem root at /proc to False
>17:24:18 INFO    : moving (1) to step bootloadersetup
>17:24:18 INFO    : moving (1) to step bootloader
>17:24:30 INFO    : moving (1) to step reposetup
>17:24:30 INFO    : moving (1) to step basepkgsel
>17:24:30 INFO    : moving (1) to step postselection
>17:24:30 INFO    : moving (1) to step install
>17:24:30 INFO    : moving (1) to step setuptime
>17:24:31 INFO    : moving (1) to step preinstallconfig
>17:24:31 INFO    : moving (1) to step installpackages
>17:24:31 INFO    : Preparing to install packages
>
>
>/tmp/lvmout:
>Running... ['lvm', 'vgchange', '-an', '-v']
>oups found

Actions: View

Attachments on bug 442365: 302353