INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NAME INSTALL -- Installation procedure for NetBSD/sandpoint. CONTENTS About this Document............................................2 What is NetBSD?................................................2 Dedication.....................................................3 Changes Between the NetBSD 5.1 and 5.1.2 Releases..............3 Security Advisory Fixes.....................................3 Other Security Fixes........................................4 Kernel......................................................4 Networking..................................................4 Miscellaneous...............................................4 Known Problems..............................................4 Features to be removed in a later release......................5 The NetBSD Foundation..........................................5 Sources of NetBSD..............................................5 NetBSD 5.1.2 Release Contents..................................5 NetBSD/sandpoint subdirectory structure.....................6 Binary distribution sets....................................7 NetBSD/sandpoint System Requirements and Supported Devices.....8 Supported processor cards...................................8 Supported devices...........................................8 Unsupported devices.........................................9 Supported boot devices and media............................9 Getting the NetBSD System on to Useful Media...................9 Preparing your System for NetBSD installation.................11 Booting over a serial line.................................11 Installing the NetBSD System..................................11 Booting the installer......................................11 Example of a normal boot...................................11 Common Problems and Error Messages.........................11 Running the sysinst installation program...................11 Introduction............................................11 Possible hardware problems..............................12 General.................................................12 Quick install...........................................12 Booting NetBSD..........................................13 Network configuration...................................13 Installation drive selection and parameters.............13 Selecting which sets to install.........................14 Partitioning the disk...................................14 Preparing your hard disk................................14 Getting the distribution sets...........................15 Installation from CD-ROM................................15 Installation using ftp..................................15 Installation using NFS..................................15 Installation from an unmounted file system..............16 Installation from a local directory.....................16 Extracting the distribution sets........................16 Finalizing your installation............................16 Post installation steps.......................................16 Upgrading a previously-installed NetBSD System................19 Compatibility Issues With Previous NetBSD Releases............19 Issues when running older binaries on NetBSD 5.1.2.........20 Issues affecting an upgrade from NetBSD 3.x releases.......20 Issues affecting an upgrade from NetBSD 4.x releases.......21 Using online NetBSD documentation.............................22 Administrivia.................................................22 Thanks go to..................................................23 We are........................................................24 Legal Mumbo-Jumbo.............................................30 The End.......................................................36 DESCRIPTION About this Document This document describes the installation procedure for NetBSD 5.1.2 on the sandpoint platform. It is available in four different formats titled INSTALL.ext, where .ext is one of .ps, .html, .more, or .txt: .ps PostScript. .html Standard Internet HTML. .more The enhanced text format used on UNIX-like systems by the more(1) and less(1) pager utility programs. This is the format in which the on-line man pages are generally pre- sented. .txt Plain old ASCII. You are reading the ASCII version. What is NetBSD? The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the University of California, Berkeley Net- working Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on 57 different system architectures (ports) across 15 distinct CPU families, and is being ported to more. The NetBSD 5.1.2 release contains complete binary releases for many different system architectures. (A few ports are not fully supported at this time and are thus not part of the binary distribution. Please see the NetBSD web site at http://www.NetBSD.org/ for information on them.) NetBSD is a completely integrated system. In addition to its highly por- table, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code. NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist. Dedication NetBSD 5.1.2 is dedicated to the memory of Yoshihiro Masuda, who passed away in May 2011. He was a spiritual pillar of the BSD community in Japan. Through an impressive number of books and articles on BSD, he gave courage to BSD developers. We remember his passion and deep love for BSD. Changes Between the NetBSD 5.1 and 5.1.2 Releases NetBSD 5.1.2 is the second critical/security update of the NetBSD 5.1 release branch. It represents a selected subset of fixes deemed critical for security or stability reasons. Please note that all fixes in security/critical updates (i.e., NetBSD 5.0.1, 5.0.2, etc.) are cumulative, so the latest update contains all such fixes since the corresponding minor release. These fixes also appear in minor releases (i.e., NetBSD 5.1, 5.2, etc.). The complete list of changes can be found in the CHANGES-5.1.2: http://ftp.NetBSD.org/pub/NetBSD/NetBSD-5.1.2/CHANGES-5.1.2 file in the top level directory of the NetBSD 5.1.2 release tree. Note that since 5.1.1 was not announced, the changes below are relative to 5.1, not 5.1.1. An abbreviated list is as follows: Security Advisory Fixes o NetBSD-SA2010-012: ,: http://ftp.NetBSD.org/pub/NetBSD/security/advisories/NetBSD-SA2010-012.txt.asc OpenSSL TLS extension parsing race condition. o NetBSD-SA2011-001: ,: http://ftp.NetBSD.org/pub/NetBSD/security/advisories/NetBSD-SA2011-001.txt.asc BIND DoS due to improper handling of RRSIG records. o NetBSD-SA2011-002: ,: http://ftp.NetBSD.org/pub/NetBSD/security/advisories/NetBSD-SA2011-002.txt.asc OpenSSL TLS extension parsing race condition. o NetBSD-SA2011-003: ,: http://ftp.NetBSD.org/pub/NetBSD/security/advisories/NetBSD-SA2011-003.txt.asc Exhausting kernel memory from user controlled value. o NetBSD-SA2011-004: ,: http://ftp.NetBSD.org/pub/NetBSD/security/advisories/NetBSD-SA2011-004.txt.asc Kernel stack overflow via nested IPCOMP packet. o NetBSD-SA2011-005: ,: http://ftp.NetBSD.org/pub/NetBSD/security/advisories/NetBSD-SA2011-005.txt.asc ISC dhclient does not strip shell meta-characters in environment variables passed to scripts. o NetBSD-SA2011-006: ,: http://ftp.NetBSD.org/pub/NetBSD/security/advisories/NetBSD-SA2011-006.txt.asc BIND DoS via packet with rrtype zero. o NetBSD-SA2011-007: ,: http://ftp.NetBSD.org/pub/NetBSD/security/advisories/NetBSD-SA2011-007.txt.asc LZW decoding loop on manipulated compressed files. o NetBSD-SA2011-008: ,: http://ftp.NetBSD.org/pub/NetBSD/security/advisories/NetBSD-SA2011-008.txt.asc OpenPAM privilege escalation. o NetBSD-SA2011-009: ,: http://ftp.NetBSD.org/pub/NetBSD/security/advisories/NetBSD-SA2011-009.txt.asc BIND resolver DoS. Advisories prior to NetBSD-SA2010-012 do not affect NetBSD 5.1.2: .: http://www.NetBSD.org/support/security/patches-5.1.2.html Other Security Fixes o Fix a buffer overflow in libtelnet. o OpenSSL: Fix CVE-2010-4180, CVE-2012-0050, CVE-2011-4109, CVE-2011-4109, and CVE-2011-4576. o Postfix: Update to 2.6.9, fixing CVE-2011-0411. o dhcpcd: Fix CVE-2011-0996. o xrdb: Fix CVE-2011-0465. o glob(3): Prevent resource DoS from brace expansion. o OpenSSH: Fix CVE-2012-0814. Kernel o wapbl(4): Fix errors that can lead to file system corruption and pan- ics. o Several stability fixes. Networking o Clean up setting ECN bit in TOS. PR 44742. o Prevent NFS server hang under load. PR 45093. o gem(4): Fix corrupted packet problem on 100Mb/s half duplex links. Miscellaneous o Update and add some TNF ssh keys to /etc/ssh/ssh_known_hosts. o Update tzdata to 2011n. Known Problems Using block device nodes (e.g., wd0a) directly for I/O may cause a kernel crash when the file system containing /dev is FFS and is mounted with -o log. Workaround: use raw disk devices (e.g., rwd0a), or remount the file system without -o log. Occassionally, gdb may cause a process that is being debugged to hang when ``single stepped''. Workaround: kill and restart the affected process. gdb cannot debug running threaded programs correctly. Workaround: gener- ate a core file from the program using gcore(1) and pass the core to gdb, instead of debugging the running program. The sparc port does not have functional SMP support in this release. Features to be removed in a later release The following features are to be removed from NetBSD in the future: o Support for soft dependencies, also knows as soft updates (see ``softdep'' in mount(8)) will be removed in the next major release. NetBSD 5.1.2 includes a preview of WAPBL (Write Ahead Physical Block Logging), which will replace soft dependencies in the next major release. See wapbl(4) and http://mail-index.netbsd.org/netbsd-announce/2008/12/14/msg000051.html for details. o Support for Xen 2.0.x. The Xen-3 and hypervisor interface is diverg- ing from Xen-2 as development is ongoing, increasing the maintenance cost for NetBSD. It should be considered as deprecated. Users are expected to not rely on it any more beyond this major release. Further, at least version 3.1 of Xen will be required to run NetBSD as Dom0 or DomU. The NetBSD Foundation The NetBSD Foundation is a tax exempt, not-for-profit 501(c)(3) corpora- tion that devotes itself to the traditional goals and Spirit of the NetBSD Project and owns the trademark of the word ``NetBSD''. It sup- ports the design, development, and adoption of NetBSD worldwide. More information on the NetBSD Foundation, its composition, aims, and work can be found at: http://www.NetBSD.org/foundation/ Sources of NetBSD Refer to http://www.NetBSD.org/mirrors/ NetBSD 5.1.2 Release Contents The root directory of the NetBSD 5.1.2 release is organized as follows: .../NetBSD-5.1.2/ CHANGES Changes between the 4.0 and 5.0 releases. CHANGES-5.0 Changes between the initial 5.0 branch and final release of 5.0. CHANGES-5.1 Changes between the 5.0 and 5.1 releases. CHANGES-5.1.1 Changes between the 5.1 and 5.1.1 releases. CHANGES-5.1.2 Changes between the 5.1.1 and 5.1.2 releases. CHANGES.prev Changes in previous NetBSD releases. LAST_MINUTE Last minute changes and notes about the release. README.files README describing the distribution's contents. source/ Source distribution sets; see below. In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD 5.1.2 has a binary distribution. The source distribution sets can be found in subdirectories of the source subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows: gnusrc This set contains the ``gnu'' sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. sharesrc This set contains the ``share'' sources, which include the sources for the man pages not associated with any particular program; the sources for the typesettable document set; the dictionaries; and more. src This set contains all of the base NetBSD 5.1.2 sources which are not in gnusrc, sharesrc, or syssrc. syssrc This set contains the sources to the NetBSD 5.1.2 kernel for all architectures as well as the config(1) utility. xsrc This set contains the sources to the X Window System. All the above source sets are located in the source/sets subdirectory of the distribution tree. The source sets are distributed as compressed tar files. Except for the pkgsrc set, which is traditionally unpacked into /usr/pkgsrc, all sets may be unpacked into /usr/src with the command: # cd / ; tar -zxpf set_name.tgz In each of the source distribution set directories, there are files which contain the checksums of the files in the directory: MD5 MD5 digests in the format produced by the command: cksum -a MD5 file. SHA512 SHA512 digests in the format produced by the command: cksum -a SHA512 file. The SHA512 digest is safer, but MD5 checksums are provided so that a wider range of operating systems can check the integrity of the release files. NetBSD/sandpoint subdirectory structure The sandpoint-specific portion of the NetBSD 5.1.2 release is found in the sandpoint subdirectory of the distribution: .../NetBSD-5.1.2/sandpoint/. It contains the following files and direc- tories: INSTALL.html INSTALL.ps INSTALL.txt INSTALL.more Installation notes in various file formats, including this file. The .more file contains underlined text using the more(1) conventions for indicating italic and bold display. binary/ kernel/ netbsd-GENERIC.gz A gzipped NetBSD kernel containing code for everything supported in this release. sets/ sandpoint binary distribution sets; see below. installation/ floppy/ sandpoint boot and installation floppies; see below. misc/ Miscellaneous sandpoint installation utilities; see installation section below. Binary distribution sets The NetBSD sandpoint binary distribution sets contain the binaries which comprise the NetBSD 5.1.2 release for sandpoint. The binary distribution sets can be found in the sandpoint/binary/sets subdirectory of the NetBSD 5.1.2 distribution tree, and are as follows: base The NetBSD 5.1.2 sandpoint base binary distribution. You must install this distribution set. It contains the base NetBSD utilities that are necessary for the system to run and be mini- mally functional. comp Things needed for compiling programs. This set includes the system include files (/usr/include) and the various system libraries (except the shared libraries, which are included as part of the base set). This set also includes the manual pages for all of the utilities it contains, as well as the system call and library manual pages. etc This distribution set contains the system configuration files that reside in /etc and in several other places. This set must be installed if you are installing the system from scratch, but should not be used if you are upgrading. games This set includes the games and their manual pages. kern-GENERIC This set contains a NetBSD/sandpoint 5.1.2 GENERIC kernel, named /netbsd. You must install this distribution set. man This set includes all of the manual pages for the binaries and other software contained in the base set. Note that it does not include any of the manual pages that are included in the other sets. misc This set includes the system dictionaries, the typesettable doc- ument set, and other files from /usr/share. text This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages. NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86 4.5.0. Binary sets for the X Window System are distributed with NetBSD. The sets are: xbase The basic files needed for a complete X client environment. This does not include the X servers. xcomp The extra libraries and include files needed to compile X source code. xfont Fonts needed by the X server and by X clients. xetc Configuration files for X which could be locally modified. xserver The X server. The sandpoint binary distribution sets are distributed as gzipped tar files named with the extension .tgz, e.g. base.tgz. The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the filenames stored in the sets are relative and therefore the files are extracted below the current directory. Therefore, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the tar -xzpf command from the root directory ( / ) of your system. Note: Each directory in the sandpoint binary distribution also has its own checksum files, just as the source distribution does. NetBSD/sandpoint System Requirements and Supported Devices Currently, NetBSD/sandpoint requires the use of Motorola's DINK32 ROM to load over a serial port. This means that there is no way to boot from a local disk or PCI device. Supported processor cards o Unity X4 with MPC8240 o Altimus X3 with either MPC755 or MPC7410 Other PMCs should work, but may need minor adjustments or more substan- tial work to support additional functionality. Supported devices o Ethernet - Asante Mac 10/100 PCI Rev A, part number 09-00169-01 (de) - Farallon Fast EtherTX 10/100, part number PN996L-TX (de) - SMC Etherpower II (9432TX) (epic) - SMC 83c170 (epic) - 3Com 3c905 (ex) - Intel EtherExpress PRO/10+ PCI LAN Adapter (fxp) - Realtek 8029 Ethernet (ne) - VIA Technologies VT86C926 (ne) - D-Link DFE-530TX+ (rtk) - Realtek 8139 (rtk) - Netgear FA-311 (sip) - Lite-On PNIC (tlp) - D-Link DFE-530TX (vr) - Many other PCI Ethernet interfaces, such as Tulip-compati- ble (de and tlp), 3Com (ep), SMC (epic), Intel (fxp), NE2000-compatible (ne), and Realtek (rtk) o SCSI - Adaptec PCI controllers 291x, 2920, 2930C, 294x, 295x, 39xx, 19160, 29160 and AIC-78xx (ahc) - AdvanSys ABP-940UW[68], ABP-970UW[68], ASB3940UW-00 SCSI host adapters (adw) - AdvanSys 1200[A,B], 9xx[U,UA] SCSI controller (adv) - AMD 53c974 (pcscp) - DPT SmartCache/SmartRAID (dpt) - NCR/Symbios 53C8xx (siop or esiop) - Many other PCI SCSI controllers should work, but no one has tried them - Most SCSI disk/tape/CD-ROM devices should work o IDE - Promise Ultra66 (pciide) - Some other PCI IDE controllers should work, although no one has had much success - Most IDE disk/CD-ROM/ATAPI devices should work o Audio - PCI audio cards, although none have been tested. o Serial ports - On-board serial ports (the modem and printer ports) (com0 and com1) - Some PCI serial ports should work, but no one has tried them o PCI cards - Most MI PCI cards should work, although very few have been tested with NetBSD/sandpoint http://www.NetBSD.org/support/hardware/pci.html Unsupported devices o Built-in PS/2 keyboard & mouse o Built-in parallel o Built-in floppy o Built-in IDE Supported boot devices and media Currently, the only way to boot the system is with the DINK32 ROM moni- tor's serial download or a JTAG device. Getting the NetBSD System on to Useful Media Note that if you are installing or upgrading from writable media, it can be write-protected if you wish. These systems mount a root image from inside the kernel, and will not need to write to the media. If you booted from a floppy, the floppy disk may be removed from the drive after the system has booted. Installation is supported from several media types, including: o CD-ROM / DVD o MS-DOS floppy o FTP o Remote NFS partition o Tape o Existing NetBSD partitions, if performing an upgrade The steps necessary to prepare the distribution sets for installation depend upon which installation medium you choose. The steps for the var- ious media are outlined below. CD-ROM / DVD Find out where the distribution set files are on the CD- ROM or DVD. Likely locations are binary/sets and sandpoint/binary/sets. Proceed to the instructions on installation. MS-DOS floppy NetBSD does not include split distribution sets for installation by floppy. However, they can be created on a separate machine using the split(1) command, running e.g. split -b 235k base.tgz base. to split the base.tgz file from sandpoint/binary/sets into files named base.aa, base.ab, and so on. Repeat this for all set_name.tgz files, splitting them into set_name.xx files. Count the number of set_name.xx files that make up the distribution sets you want to install or upgrade. You will need one sixth that number of 1.44 MB floppies. Format all of the floppies with MS-DOS. Do not make any of them bootable MS-DOS floppies, i.e. don't use format /s to format them. (If the floppies are bootable, then the MS-DOS system files that make them bootable will take up some space, and you won't be able to fit the distribution set parts on the disks.) If you're using floppies that are formatted for MS-DOS by their manufacturers, they probably aren't bootable, and you can use them out of the box. Place all of the set_name.xx files on the MS-DOS disks. Once you have the files on MS-DOS disks, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the sec- tion on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. FTP The preparations for this installation/upgrade method are easy; all you need to do is make sure that there's an FTP site from which you can retrieve the NetBSD distribution when you're about to install or upgrade. If you don't have DHCP available on your network, you will need to know the numeric IP address of that site, and, if it's not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself. Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. NFS Place the NetBSD distribution sets you wish to install into a directory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading NetBSD. This will probably require modifying the /etc/exports file on the NFS server and resetting its mount daemon (mountd). (Both of these actions will proba- bly require superuser privileges on the server.) You need to know the numeric IP address of the NFS server, and, if you don't have DHCP available on your network and the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself. Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on pre- paring your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. Tape To install NetBSD from a tape, you need to make a tape that contains the distribution set files, in `tar' format. If you're making the tape on a UNIX-like system, the easi- est way to do so is probably something like: # tar -cf tape_device dist_directories where tape_device is the name of the tape device that describes the tape drive you're using; possibly /dev/rst0, or something similar, but it will vary from system to sys- tem. (If you can't figure it out, ask your system admin- istrator.) In the above example, dist_directories are the distribution sets' directories, for the distribution sets you wish to place on the tape. For instance, to put the kern-GENERIC, base, and etc distributions on tape (in order to do the absolute minimum installation to a new disk), you would do the following: # cd .../NetBSD-5.1.2 # cd sandpoint/binary # tar -cf tape_device kern-GENERIC base etc Note: You still need to fill in tape_device in the example. Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. Preparing your System for NetBSD installation When installing NetBSD for your NetBSD 5.1.2 system, you have to decide where you want your root partition and how you'll be downloading your kernel. Since the IBM ROM rather limits your boot options, you won't be able to have the machine boot independently. Once you load the kernel, however, you may have the root file system on a local disk or you can configure a diskless setup. In either case, you'll need to set up to boot the kernel over the network or over a serial line. Booting over a serial line This is not currently documented or supported. If you would like to attempt this and supply documentation, please do! Installing the NetBSD System Booting the installer Once the kernel is downloaded, type "go 90000" to start the kernel. Example of a normal boot Of course, a lot of the information in this example depends on your model and what your boot method is, but we'll include this anyways just so you get an idea of what to expect (user-typed commands are in bold). DINK32>> go 90000 [ XXX - insert boot w/ installer on ramdisk instead of this example ] Common Problems and Error Messages Insufficient data. Running the sysinst installation program 1. Introduction Using sysinst, installing NetBSD is a relatively easy process. Still, you should read this document and have it in hand when doing the installation process. This document tries to be a good guide to the installation, and as such, covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use. 2. Possible hardware problems Should you encounter hardware problems during installation, try rebooting after unplugging removable devices you don't need for installation. Non-removable devices can be disabled with userconf (use boot -c to enter it). 3. General The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. sysinst is a menu driven installation system that allows for some freedom in doing the installation. Sometimes, questions will be asked and in many cases the default answer will be displayed in brackets (``[ ]'') after the question. If you wish to stop the installation, you may press CONTROL-C at any time, but if you do, you'll have to begin the installation process again from scratch by running the /sysinst pro- gram from the command prompt. It is not necessary to reboot. 4. Quick install First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instruc- tions, skip to the next section. This section describes a basic installation, using a CD-ROM install as an example. o What you need. - The distribution sets (in this example, they are on CD). - One 1.44 MB 3.5" floppy. - A CD-ROM drive (SCSI), a hard disk and a minimum of of mem- ory installed. - The hard disk should have at least + n megabytes of space free, where n is the number of megabytes of main memory in your system. If you wish to install the X Window System as well, you will need at least 215 MB more. o The Quick Installation - Insert the first boot floppy you just created and boot the computer. After language selection, the main menu will be displayed. .***********************************************. * NetBSD-5.1.2 Install System * * * *>a: Install NetBSD to hard disk * * b: Upgrade NetBSD on a hard disk * * c: Re-install sets or install additional sets * * d: Reboot the computer * * e: Utility menu * * x: Exit Install System * .***********************************************. - If you wish, you can configure some network settings immedi- ately by choosing the Utility menu and then Configure network. It isn't actually required at this point, but it may be more convenient. Go back to the main menu. - Choose install. - You will be guided through some steps regarding the setup of your disk, and the selection of distributed components to install. When in doubt, refer to the rest of this document for details. - After your disk has been prepared, choose CD-ROM as the medium. The default values for the path and device should be ok. - After all the files have been unpacked, go back to the main menu and select reboot, after you have removed the boot- floppy from the drive. - NetBSD will now boot. If you haven't already done so in sysinst, you should log in as root and set a password for that account. You are also advised to edit /etc/rc.conf to match your needs. - Your installation is now complete. 5. Booting NetBSD Boot your machine. The boot loader will start, and will print a countdown and begin booting. If the boot loader messages do not appear in a reasonable amount of time, you either have a bad boot floppy or a hardware problem. Try writing the install floppy image to a different disk, and using that. It will take a while to load the kernel from the floppy, probably around a minute or so, then, the kernel boot messages will be dis- played. This may take a little while also, as NetBSD will be prob- ing your system to discover which hardware devices are installed. The most important thing to know is that wd0 is NetBSD's name for your first IDE disk, wd1 the second, etc. sd0 is your first SCSI disk, sd1 the second, etc. Note that once the system has finished booting, you need not leave the floppy in the disk drive. Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus. 6. Network configuration If you do not intend to use networking during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the Utility menu and select the Configure network option. If you only want to temporarily use net- working during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response when asked to provide a server. 7. Installation drive selection and parameters To start the installation, select Install NetBSD to hard disk from the main menu. The first thing is to identify the disk on which you want to install NetBSD. sysinst will report a list of disks it finds and ask you for your selection. You should see disk names like sd0 or sd1. 8. Selecting which sets to install The next step is to choose which distribution sets you wish to install. Options are provided for full, minimal, and custom instal- lations. If you choose sets on your own, base, etc, and a kernel must be selected. 9. Partitioning the disk o Which portion of the disk to use. You will be asked if you want to use the entire disk or only part of the disk. If you decide to use the entire disk for NetBSD, sysinst will check for the presence of other operating systems and you will be asked to confirm that you want to over- write these. 10. Editing the NetBSD disklabel The partition table of the NetBSD part of a disk is called a disklabel. If your disk already has a disklabel written to it, you can choose Use existing partition sizes. Otherwise, select Set sizes of NetBSD partitions. After you have chosen your partitions and their sizes (or if you opted to use the existing partitions), you will be presented with the layout of the NetBSD disklabel and given one more chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 4.2BSD. A swap parti- tion has a special type called swap. Some partitions in the diskla- bel have a fixed purpose. a Root partition (/) b Swap partition. c The NetBSD portion of the disk. d-p Available for other use. Traditionally, e is the par- tition mounted on /usr, but this is historical prac- tice and not a fixed value. You will then be asked to name your disk's disklabel. The default response will be ok for most purposes. If you choose to name it something different, make sure the name is a single word and con- tains no special characters. You don't need to remember this name. 11. Preparing your hard disk You are now at the point of no return. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to pro- ceed, select yes. The install program will now label your disk and make the file sys- tems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installa- tion program after pressing the return key. 12. Getting the distribution sets The NetBSD distribution consists of a number of sets that come in the form of gzipped tarfiles. At this point, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly. For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to the section labeled `Extracting the distribution sets'. 13. Installation from CD-ROM When installing from a CD-ROM, you will be asked to specify the device name for your CD-ROM drive (usually cd0), and the directory name on the CD-ROM where the distribution files are. sysinst will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets. 14. Installation using ftp To be able to install using ftp, you first need to configure your network setup if you haven't already done so. sysinst will do this for you, asking you if you want to use DHCP. If you do not use DHCP, you can enter network configuration details yourself. If you do not have DNS set up for the machine that you are installing on, you can just press RETURN in answer to this question, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS, you will need to specify an IP address instead of a hostname for the ftp server. sysinst will proceed to transfer all the default set files from the remote site to your hard disk. 15. Installation using NFS To be able to install using NFS, you first need to configure your network setup if you haven't already done so. sysinst will do this for you, asking you if you want to use DHCP. If you do not use DHCP, you can enter network configuration details yourself. If you do not have DNS set up for the machine that you are installing on, you can just press RETURN in answer to this question, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e., correctly exported to your machine. If you did not set up DNS, you will need to specify an IP address instead of a hostname for the NFS server. 16. Installation from an unmounted file system In order to install from a local file system, you will need to spec- ify the device that the file system resides on (for example sd1e) the type of the file system, and the directory on the specified file system where the sets are located. sysinst will then check if it can indeed access the sets at that location. 17. Installation from a local directory This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file sys- tem that is already accessible. sysinst will ask you for the name of this directory. 18. Extracting the distribution sets Before extraction begins, you can elect to watch the files being extracted; the name of each file that is extracted will be shown. This can slow down the installation process considerably on machines with slow graphics consoles or serial consoles. Alternatively, you can choose to see a progress bar. This is the preferred option as it shows progress without significantly slowing down the installa- tion process. After all the files have been extracted, the device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files. The next menu will allow you to select the time zone that you're in, to make sure your clock has the right offset from UTC. Finally you will be asked to select a password encryption algorithm and can then set a password for the "root" account, to prevent the machine from coming up without access restrictions. 19. Finalizing your installation Congratulations, you have successfully installed NetBSD 5.1.2. You can now reboot the machine and boot NetBSD from hard disk. Post installation steps Once you've got the operating system running, there are a few things you need to do in order to bring the system into a properly configured state. The most important steps are described below. 1. Configuring /etc/rc.conf If you or the installation software haven't done any configuration of /etc/rc.conf (sysinst usually will), the system will drop you into single user mode on first reboot with the message /etc/rc.conf is not configured. Multiuser boot aborted. and with the root file system (/) mounted read-only. When the sys- tem asks you to choose a shell, simply press RETURN to get to a /bin/sh prompt. If you are asked for a terminal type, respond with vt220 (or whatever is appropriate for your terminal type) and press RETURN. You may need to type one of the following commands to get your delete key to work properly, depending on your keyboard: # stty erase '^h' # stty erase '^?' At this point, you need to configure at least one file in the /etc directory. You will need to mount your root file system read/write with: # /sbin/mount -u -w / Change to the /etc directory and take a look at the /etc/rc.conf file. Modify it to your tastes, making sure that you set rc_configured=YES so that your changes will be enabled and a multi- user boot can proceed. Default values for the various programs can be found in /etc/defaults/rc.conf, where some in-line documentation may be found. More complete documentation can be found in rc.conf(5). When you have finished editing /etc/rc.conf, type exit at the prompt to leave the single-user shell and continue with the multi-user boot. Other values that may need to be set in /etc/rc.conf for a networked environment are hostname and possibly defaultroute. You may also need to add an ifconfig_int for your network interface, along the lines of ifconfig_tlp0="inet 192.0.2.123 netmask 255.255.255.0" or, if you have myname.my.dom in /etc/hosts: ifconfig_tlp0="inet myname.my.dom netmask 255.255.255.0" To enable proper hostname resolution, you will also want to add an /etc/resolv.conf file or (if you are feeling a little more adventur- ous) run named(8). See resolv.conf(5) or named(8) for more informa- tion. Instead of manually configuring network and naming service, DHCP can be used by setting dhclient=YES in /etc/rc.conf. Other files in /etc that may require modification or setting up include /etc/mailer.conf, /etc/nsswitch.conf, and /etc/wscons.conf. 2. Logging in After reboot, you can log in as root at the login prompt. Unless you've set a password in sysinst, there is no initial password. You should create an account for yourself (see below) and protect it and the ``root'' account with good passwords. By default, root login from the network is disabled (even via ssh(1)). One way to become root over the network is to log in as a different user that belongs to group ``wheel'' (see group(5)) and use su(1) to become root. 3. Adding accounts Use the useradd(8) command to add accounts to your system. Do not edit /etc/passwd directly! See vipw(8) and pwd_mkdb(8) if you want to edit the password database. 4. The X Window System If you installed the X Window System, you may want to read the chap- ter about X in the NetBSD Guide: http://netbsd.org/docs/guide/en/chap-x.html 5. Installing third party packages If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system, pkgsrc. pkgsrc automatically handles any changes necessary to make the software run on NetBSD. This includes the retrieval and installation of any other packages on which the soft- ware may depend. o More information on the package system is available at http://www.NetBSD.org/docs/software/packages.html o A list of available packages suitable for browsing is at ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/README.html o Precompiled binaries can be found at ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/ usually in the sandpoint/5.1.2/All subdir. You can install them with the following commands under sh(1): # PKG_PATH=ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/sandpoint/5.1.2/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v bash # pkg_add -v perl # pkg_add -v apache # pkg_add -v kde # pkg_add -v firefox ... If you are using csh(1) then replace the first two lines with the following: # setenv PKG_PATH ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/sandpoint/5.1.2/All Note: Some mirror sites don't mirror the /pub/pkgsrc directory. If you would like to use such mirrors, you could also try the /pub/NetBSD/packages/current-packages/NetBSD/sandpoint/5.1.2/All directory, which may have the same contents. The above commands will install the Tenex-csh and Bourne Again shells, the Perl programming language, Apache web server, KDE desktop environment and the Firefox web browser as well as all the packages they depend on. Note: In some cases the pkg_add(1) command will complain about a version mismatch of packages with a message like the following: Warning: package `foo' was built for a different version of the OS: NetBSD/i386 M.N (pkg) vs. NetBSD/i386 5.1.2 (this host), This warning is harmless if the formal major release num- bers are the same between the pkg and your host. Please refer to the NetBSD release glossary and graphs at http://www.NetBSD.org/releases/release-map.html for more information about NetBSD's release numbering scheme. o The framework for compiling packages can be obtained by retriev- ing the file ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz It is typically extracted into /usr/pkgsrc (though other loca- tions work fine) with the commands: # cd /usr # tar -zxpf pkgsrc.tar.gz After extracting, see the doc/pkgsrc.txt file in the extraction directory (e.g., /usr/pkgsrc/doc/pkgsrc.txt) for more informa- tion. 6. Misc o Edit /etc/mail/aliases to forward root mail to the right place. Don't forget to run newaliases(1) afterwards. o The /etc/postfix/main.cf file will almost definitely need to be adjusted. If you prefer a different MTA, then install it using pkgsrc or by hand and adjust /etc/mailer.conf. o Edit /etc/rc.local to run any local daemons you use. o Many of the /etc files are documented in section 5 of the man- ual; so just invoking # man 5 filename is likely to give you more information on these files. Upgrading a previously-installed NetBSD System The easiest way to upgrade to NetBSD 5.1.2 is with binaries, and that is the method documented here. To do the upgrade, you must have one form of boot media available. You must also have at least the base and kern binary distribution sets avail- able. Finally, you must have sufficient disk space available to install the new binaries. Since files already installed on the system are over- written in place, you only need additional free space for files which weren't previously installed or to account for growth of the sets between releases. If you have a few megabytes free on each of your root (/) and /usr partitions, you should have enough space. Since upgrading involves replacing the kernel, boot blocks, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to back up any important data on the NetBSD partition or on another operating system's partition on your disk before beginning the upgrade process. The upgrade procedure is similar to an installation, but without the hard disk partitioning. sysinst will attempt to merge the settings stored in your /etc directory with the new version of NetBSD. Also, file systems are checked before unpacking the sets. Fetching the binary sets is done in the same manner as the installation procedure; refer to the installa- tion part of the document for help. After a new kernel has been copied to your hard disk, your machine is a complete NetBSD 5.1.2 system. However, that doesn't mean that you're finished with the upgrade process. You will probably want to update the set of device nodes you have in /dev. If you've changed the contents of /dev by hand, you will need to be careful about this, but if not, you can just cd into /dev, and run the command: # sh MAKEDEV all Finally, you will want to delete old binaries that were part of the ver- sion of NetBSD that you upgraded from and have since been removed from the NetBSD distribution. Compatibility Issues With Previous NetBSD Releases Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 5.1.2. Note: None of the items mentioned below are relevant if upgrading from 5.1. They still apply if you are upgrading from a pre-5.1 release, though. If your port uses X.Org and you see messages from the X server indicating that no devices were found, you may need to run X -configure and update your existing xorg.conf to use the BusID line from the newly-generated config file. Dual-head support for PC systems has become broken for many configura- tions with the update to xorg-server 1.6.x, which has removed the user- land PCI configuration mechanism, and needs to rely upon the OS. We hope to correct this for future releases. Workaround: The only workaround is non-trivial and requires programming several PCI BAR registers as they previously were in NetBSD 5.0. If you are updating to NetBSD 5.1.2 without the aid of sysinst or postin- stall and your port uses X.Org, be sure to remove /usr/X11R7/lib/X11/xkb/symbols/pc before extracting the xbase set. In the version of X.Org shipped with 5.0, this was a directory, but in more recent X.Org versions it is a file. pkg_install now depends on the pkgdb cache for automatic conflict detec- tion. It is recommended to rebuild the cache with # pkg_admin rebuild audit-packages.conf(5) has been superseded by pkg_install.conf(5). The default configuration is the same. Support for pkg_view(1) has been retired. The functionality of audit-packages(1) and download-vulnerability-list(1) has moved into pkg_admin(1). However, wrapper scripts that handle the common use cases are provided. Issues when running older binaries on NetBSD 5.1.2 The pthread libraries from previous versions of NetBSD require that the sysctl(3) node kern.no_sa_support be set to 0. This affects the follow- ing environments: o Running a 5.x kernel with an older userland. o Running an older userland inside a chroot'ed environment on a 5.x system. o Running older statically linked pthread applications. The 5.x kernel defaults to 0 for kern.no_sa_support, which covers the first case. However, please note that a full installation of 5.x (either from scratch or through an upgrade) will set kern.no_sa_support to 1 dur- ing the boot process. This means that for the last two cases, you will have to manually set kern.no_sa_support to 0, using either the sysctl(8) command or through sysctl.conf(5). Note that sysinst will automatically invoke postinstall fix and thus all issues that are fixed by postinstall by default (see below) will be handled. Issues affecting an upgrade from NetBSD 3.x releases See the section below on upgrading from NetBSD 4.x as well. The following issues can generally be resolved by running postinstall with the etc set: postinstall -s /path/to/etc.tgz check postinstall -s /path/to/etc.tgz fix Issues fixed by postinstall: o Various files in /etc need upgrading. These include: - /etc/defaults/* - /etc/mtree/* - /etc/daily - /etc/weekly - /etc/monthly - /etc/security - /etc/rc.subr - /etc/rc - /etc/rc.shutdown - /etc/rc.d/* - /etc/envsys.conf The following issues need to be resolved manually: o The users `_proxy', `_rwhod', and `_sdpd' and the groups `_proxy', `_rwhod' and `_sdpd' need to be created and the user `uucp' needs to be updated. o A number of things were removed in the NetBSD 4.0 release, including: the evbsh5 port, the Fortran 77 compiler (g77), NETCCITT, NETNS, Sendmail, Sushi, UUCP, and Vinum. If you were using any of these, please see the "Components removed from NetBSD" at http://www.NetBSD.org/releases/formal-4/NetBSD-4.0.html#removals o The replacement of Sendmail by Postfix can be handled automati- cally by postinstall but it is not done by default. If you want to transition to Postfix, the command postinstall -s /path/to/etc.tgz fix mailerconf will update your /etc/mailer.conf file to use Postfix as the MTA. When using sysinst to upgrade the system, it will ask if you want this to be done. Note that if you have a customized Sendmail setup, you need to set up Postfix in an equivalent way; there is no tool for auto- matic conversion of Sendmail configuration to a Postfix one. Postfix will be started automatically when the system boots. You may see messages like "$sendmail is not set properly" at boot. You can suppress them by removing /etc/rc.d/sendmail and /etc/rc.d/smmsp. Those files and other parts of sendmail con- figuration like files under /usr/share/sendmail are not removed by default while upgrading for those who want to continue using sendmail from outside the base system. If you want to delete them, postinstall can be used: postinstall -s /path/to/etc.tgz fix sendmail Issues affecting an upgrade from NetBSD 4.x releases The following issues can generally be resolved by running postinstall with the etc set: postinstall -s /path/to/etc.tgz check postinstall -s /path/to/etc.tgz fix Issues fixed by postinstall: o Various files in /etc need upgrading. These include: - /etc/defaults/* - /etc/mtree/* - /etc/daily - /etc/weekly - /etc/monthly - /etc/security - /etc/rc.subr - /etc/rc - /etc/rc.shutdown - /etc/rc.d/* - /etc/envsys.conf The following issues need to be resolved manually: o The users `_httpd' and `_timedc' and the groups `_httpd' and `_timedc' need to be created. o Unprivileged use of the mount(8) command now requires the nosuid and nodev options to be explicitly specified. Previ- ously, these options were automatically enforced even if they were not explicitly specified. o A number of things have been removed from the NetBSD 5.1.2 release. See the "Components removed from NetBSD" section near the beginning of this document for a list. Using online NetBSD documentation Documentation is available if you installed the manual distribution set. Traditionally, the ``man pages'' (documentation) are denoted by `name(section)'. Some examples of this are o intro(1), o man(1), o apropos(1), o passwd(1), sc-g>s9V3Kϴ3g|F ^c=|[.n[0xc ||ͽL|&/19/{:?b*2bqMq̝oͶޯȒ9ߗ>ؘgL׶}dސ]Cy+9ߐyyi_;% ߓuwKL 9M9ȯ"옮0d[vaG7o^GHY n2~am?wL[kcy:20ј/jpRQ>e*T O%^f/e'lM| Y0na Ex'X`-[{t ^U@_ճ)A ѵ"l;5-kNq-6.<-dmO٦$Ls)ʽ+-1{ǹG ګr'*^ Y}դo=|G~ƃZ6GMWM x{p5vqyL\l|kgJ{zJK+CyC߯aAw+ ]r'g%_jSB]`l*7/L7:{&eo Næ)l3;M:~;o *=ieSuAo)'nK"gece> nU` !̳w7N=7ZLD;hZ8φ?y$KamzkCu0 uj,s4wh!_B~gQG^o10ֱ]?:?ۯh`[6(T91)/Εh):#v}]-$k/t{GQ((ӌ~({# j=n'CnI6\39 ΍mO$ߝ{lKE7{k`YjCZsa~,CGkOgHno2♗x=_Ylyiپoo3'ܢ|>^%z"k䉊u1K.Ehkn}H?ϑ>% ɾcc[t2mUðxfTOK17lv}@qqc?јQ{TV:눽Z,k~]q6ba{V@y0s7K0 /XwCfq}PE~.9\Fky4yaA{^hGW ǻ'r%H+$Jaۉ@'Pοkib+|c);+N 7{X__?0z +q2K݉x !Dc?DAX|-?l*E:}9ۆ}uac=lr২/6Sg\6zڛUS⚤&.;wq(a|osf8jzJʭ[gV[<)CN>! KFɴbᢽNsGGͱVɧ01;6~o-9~d@؊6,>#>͠'lf-Lq?NmKG|/%PY7 _5ٕtGK/IA>=mcJAgJmn\:rmT\-^|g_WSCRGQѳFx^L}D|fؖv.Ϩ2p|i)*a^QiQ Z-[ <~KF>Ƒ$it;|o+x?(*NcI2V9ĭ~c̬ŗCO@rBe7' gni/3(ԏU~\^O\ᏧxGn8Δ14q{Ch8LzTrX@#Xw9ף@\/Fr3K[laez|_anQn+pu zЏ*6٢g'c|j$źaK(F 8B21R[*%cl}Ry!Y.6 clܜ|sbx {iuK)F2ϳ࡜s;Vybn\RD"|} B<-6r^<=SP&sM9?lF@ۖ0's=vXǛdD݊>38ofz;8SS%,TSQҩ!IJMT֝UFc_lʟ)W( }7OXör_9y.srɼ2*AyZs1O4Q|sFcLv/19~!xQs<[sOiѼ;A6F^wF/[(C~˵y`,JmdS[0bafX<Ȱ((H:ЧsӘXvm͝L?mt+er?&cEɋ?Jˎe8&υhL91 qˌK4O%s:>yŽ% iLW3 _4|%O#kŧG ܉9$?|9E*&W\"8U/pߟ?}_-쏽Y ;8>25=7_+ DORLxa%zW N/+NuuCY.dVךD]˦>S}e&L}h2Wy5vQj\iaHgẋ-q,'~=u?a/oxl,{^{©lqq˗1.C~~ӧ^W+.<drIǕɻx0yW<3A};l'T;mgf3xl4&:;X.拟cYװy|~od6"~e~Vsyif<2IBwkwkw by$oZ[e _K&%Uk aƷmm vQV鬲@o3ggb[/iOV`V=sT6a]n1 rZb>&s~亜\;xvD8=ᡧˇ~hz2#b(-v9w;OW]C3{ҡ~Gnۗ GǪ;cƃ'ZT/Αn"FSُYz3bE Е"#jTl.Zrby :_RKJZt\%%Jz%a^IX$W+ 땄JzIc ӌT;_`vdz#"ܲ Þ scr͹;7]g@cvFl19jXIes M!('[C>kt2\d7e˚@ɡVG pzypU|Uιa=wٹq(`-+sBg^є{Mw2A5X) QLԢo߿jʢ1x~Q3V_<__>0턦̂eMqpnx3b d, OsHπ`Fho|̱Ӱ:߼~1 c⋘$pww _p8~/ޛw5z12Oy/,B^Pt7X@M@mBZjx] !;1b?lC#uE)tx3D{4QYpM3/ kw:c~D {Jaq^,0˾"ب@wJ߼H7Yfxe\pJxzH&Edźjϼר\@pIQ>_J{ힵ;*|Œ(p%>%%m jjӋC{ȱђBk$\Z͕]E({V WOh%U5#A tw& H11Fa>lNa{ !6~ѵ _0F4^NUXI"+&WsJWZP5>t5+iϊ=B^<^ܣ EjK&7py}c7#L[vn۲a\{)1~wg4'߭yP~qoܡ15 a?;(.h% h*4yzR<~Mw.^(\`m''i.z=WzT1Qه@߮|UDG4?=dc`%@wU]NwanUEd35\3".IWSd.' A<p.eҋH <"2m߳Dk먽K_;b,5E՚x3tޥTX~Ւ:BCYqsŇ\}!M8Q{Z4/:L>X_>`x"җf"!=i}ہMqa#&胜o6~gj=^P^b~Hg/?VGK/>OeͲ%ʐK)[N?X\~^@rg]A}̞Xcd1^,.؋& I+B?)D4%dsϑ|d1q׏wƢKfCOYM-Ƃ_fm0S/tYA ?(AO2nxpFvX{DQM{Q~]'i ٙitQ _}n뒮8vk7G@U.fș-R:W|8Ʋr'{=țx[UZƌuX/(eK~N QB!{jHgϳ,,w=Uy\9}jr_G7 ׻iѩx6^âL ;)f;9l["/Dܿg^':?Lz^~$?n ɔ'W: e &lJ27k*l@?7Kox_}}i!+g_[}4N/"/U7ɺ "gy" 9Rc3'_klQ6TjC:sY!}vu^~pB.[P#o/VxFpgI'Klҟryet_C.:]hǗaոV ~dJ3?u蓲: z* Y5ވG"+y0e3mC;>wO{fK_F3eZiT`Tm72("@}Ѭ3ěҗr=q>pҺ.P8RQ?yksαI7'2(9.NAKyA~9[1zڝ%e68|>dvN;/o([QΘf{_=tp\#d4T Nݨ(].WWXKytK%_˥>RqX>w)H{9V н/ʿK}PmȬuyfZ+ :gWơ1̹NS H pf?Ihc-5* y1d1$((<ڽΧEN w&#i&)q 3U&io&b«[1<]_rh曋ݴ^'3-l區".6.Q>']z0|Yn2,7r-X}^{ǎ\=G.xZ<9q3ϴpV ޟ55Rr6@FAG[3z/K_94*/'7e2xwTj$n;G0זY 'm3nm*.v%/zJ%юdƤ\wdnOugҕ-Gj&Ǚ&fD'NAԳ_(`Y'Ϻzg&'lO{fmbnՎ(G"nTx/7; x̟՚C,~3ú7T2٥֑|BP΋5iXn5aX>eurRL}S)`$0_ZdlGse^b鯔aOmD^:2fAp,g|Z7qXFyoL&`OMH-~ pQ?)ސ6tV1 JqNK_5ϛ+rYA ;WQgNI09L~7֏Lk ~C{vV nި)>k}v )QwS'WmLGH&X,^a*SS-inޕo} ߟde,˵0u3.1_t /ҧpzG6AJ^ċ[O%i?i8}RBV?~OM'JYKYEdRV?Iz2 qQRE1ho3F'mv:m} e_?i>D>l.S>tG(ǖ<ҋ73#P&, 8m#" hw*̙__|3L1'{y6'V=d BqKmo [YMPnOw˩alքVU>kؾ7>i#r&x⽚/^Jɮ8DοzF߽}by4&Oịo%eh 6] g9qq0 JE^0pG m//~ݗka/C"E+mG$n"dغ][]SՒ޶{c:#b>3xK_=KP>C8{~0M:"?iTʨ\;kӮq+oQy'ja4s!} Ƌ~@H+ }"xfV;qu3T~?q^ƿ?i?E{y}ph+}ٽ非\ N_44+>(!Mw~6N[p\~2u=q Խh] @u#b3cXDvh>s:jgۢU9x^zVEes=5| ڴv0FdsSoiSwP]is` " SX3Q Gpa'r"- Y;o]4߼MYl`/3m1ɝp>~1[|Q>xr Pw(P dw13>}`wErˍcy:ΖNG6JoBg֒[Oώ {t-ED~1G3t(x=%vy GNwtFy`w+ƻtOk`Lkw@%jYOg [\;g;+< kZmIonˋڳ}/ 1Ox(˘W zN+>oW};oY(YߎUIrY<,EǴ"yb)')h/F)uȱ_6 =y@y`M<&%L=#vq7Iѓ{lv3SuU7[9w0OǟK?kUnyy-1+ γyF }#}w ֚?2>[kQEKѷ7s<'|=cnTד,H_9I_9>LbLŘ'w]~c;^pn,.3΢F3qe7H:Q\M~_;C#|ލ]evCbLe;ّmaXȠ/ғ]6 XJӷ :*ۻGd9B={>|4GWYcОg7niFt3#>{kx$aBINJ{mProֶZ$@мThy ! VZM"mi֪mSWk+>jb_k9?Ǘ<ُ~!V.Ň"xy*qqup/zW>Od||o_{5 J+Ou:)Vmg Bze;R`Lֆ{?-̔9 y<<_ ?~\;uVa/2?/.Rg]u9V$waO_<>mo!2{^fv,CwvŔv_ếu /vxpu>vNf @YEKe !l r.gFBNѷ'Lဿn;;Nb lwbd!Ә+UcfŒpWIKAw9sշ5!^S\*;Aul1\IRh*{ <6yjpכU_taֹb\]W1u96nV󡘹.=TĽ'R9*uݚl2(rz Wr̠k9V˻̫>'G*o|up~+ 9a@sT?[c7\,|x80DR ['Vw֡}θoa̬+̫͹Mza$?[+S]QWca~3!79\S98'g8qkO[#9 yT)gB5Ww(zx8RxpkdC%M3N {̥7/&>(M,ỵZ#w()y D6tm;~X{6W7=-|Xxrʜ?.yJojg→Ӹv޲MCRLy?i8,MB| |QW'4]ϓm貐9n:Mx=yi1%E $o֊eB,4AKaqk-+˨ߪ!6UjlY?j4ʙ& ;p(ݴVh`nʠ$C\ /y>!Ya w:x"d/)LeZI6ÞC6ktX^|I 6>\ +֕ah:m-3DWj_vE5wF:=(Uyeof*11q_1:rR)NS;s0dzv,lǰ6s/Y"$M޴ 0L<ҡTJw>mFKY/kuyϷ9mNzMu S1҇b}}c:\!.%7.s@csmaSi qɤ /,IvW~"\aP~lMZhU?9?̺œh 5䟆5<63zUr:sj\Yx>s+F_P}/CUsDZn:;xvr6))Gk]+YpF>i0+ֈ%NQtr9[)Vf1%kOp'd}sՈ9jF)~qa ` a a OHWunx~.is̃k\~\p~c<+.cR0dŶL3dN?$CYxّ Y>X&g|DYAʨ~*s"' o|cv>{큲mWuWz^07 Cx|XU_;F?rY9䓝 J^fE AYÓ&5[O|jo36tUtv$0E}@{HSo!;ݘS鳟gȖ>Uc[46GP%ShfMHiO}"_JNsQ{Yz=,Gm_x';? NQg~k3#)WqyZ[}R5ދ.Gn2 %V<8K]M|޶">Y/Ɋ<{Uuy}>Yd}vjuj3OY*8XpСzcP"$yϒ)7g86NE{K{cs;,F%?5S=Gg`*6ZGGodmd]RϾb¬*U:r ~P6c8ӿ>^1Jլ/^ ^Wx]y] EMF6GQ_X=Ys=d1٣TJY63yg+xޟO4S9^}h&;J }RB'&qq`ܵD#F73ڸSg8OFS?% ?5d[ (L*CAzeQA/\KSkdf5uzo muElW .7(ߢHו~a*r1=pNMk-dR1ʏy=Q^)r^I1z\_ m]0 l;i43#]ǵ,g[0@=ܣ=yMQ+rr^앷wUaٛQ(.a}ٛoD*$M^v8]b(>}y! ]^;x}_B|')76ؼa/2l^ȰyA l60F\[~yVϼL̓JHw>襁su#K>r`d듩4xhSFy'O;1T,z_?+"[dKōX ~_V:v3y4JRb\Eo"@6X{MC-ټHaBM^O`CX`~? ʏaQ 0]8wI5 2}G_cx~"4zѐRЯsChu`{1z)/X-25LUV*2EW8K VڕŘ%Gbu1dR@vߦ@5b@r6/d|2iiy2ʃLG[p:Vc\aē:Ő_Z%6'ZK;gh y`x'%i|?>\2w0\trKsa^? 3saaD0 s}t'h4Ϛ,'s Jf8ݢK4x]³7{D*~~<;^`O_H(uH cX^4/x}rN7 2v (Vi;Rҷ(﵉ʴc ҅gw#L_`_u운cSizC݁g{ifbV,:(%>6Ű!%_(=Xnq<>j۶(.uIQ~Ǵ.T6:˶\dNV2JU[#(zDgdhۣQ\U% @Yɚ%_]}[)9f?~hzm?3~"ɱXssr]O#|\pAb-B$EgF'ctƓ~y E<3,mOP/6-2Z<ɕTLMOK=uRub>5H0O:b]?669̼y?iiGץyO|5}\81v\ߋ9@ ~,DœrtƼqq!vE#2Su&3W<,YGkhzO^W>㜮=sojx6e>\ogz|0c=Կi{zGVH5Xci)'Is^}M)//szʃlY՚ /=篇F'o6kZ'[oqOxA}_v%){EJY}m$7pc7YL}]f̳\⯶m=L\'Ο陗}Fcy4r|z< %aM8?A߇wBր m"V|u.yw(Rr;[NmR5z!1zw?${'&`唅_9eo>C|:uQp8:>wg"CK_6+}Ti%7S Ø2:~]ƴwKw!{6.K.@eH&Y-󗰭q?N1[ڠ]GڱzaR_49/(W8CʞwXjżnJᐞ=*f/='͞Yg&9*ΐjnTiv״(of"͜ fh-ZKsrSx=)p|O}؉>}I?kgg<#>?}%IX35X9uܼ{اP %=ky߿~;l(OY䃇<9y2s#`KYcKY%Л 30ԥPO\} &[o=׮PPRh8yx YƉ@s>u5{RűO;eҢCBuY9ڸ|FoojZ}c."k ]6Io*Cz M .bj^Ewh1ٖ34juپEށwʱ庵"G0̗Q6pNN+(~~7wrV.'.4ִ:\)z8:k ` 6iGNO5]Ӗ2ΫtF,֊55"c1V\ E"}YX[UL֥t1v;3T޶HTLkvsf+gVqND9~cIP=IBcMf>yCg1 *ZV*V|2)B8! [\R5+Y3/j` uRYNR8OO:aLiV>]D3dEʉvMUi.}5~Fs5jc݋׋qjw}|gyړkW/363636RΘkmP8'ubf3F$+Ƀi-% fV>;X#S'[5ޜq.(.deCWZ4|k')\={o!9NGpE?3Nq 8LA("dЙ-Y0;΢v􇜚C~,y&jnOx18 j>e˵>/X |u̍c#_2ܹ3_9HՏ0⢸d8;TDFvcv T\- 9bҚCͥ"oJ)"#Z$rvŽ0I4_i/k$ G ߤs':U$^oP-c:-B5Il:yŋJ<1+>܈?1yVc-)zwR~PI^Ǵf<OZC Ӛ=Kl=sێr漐Add5$ߩ̮3˕gF{p8_'2pU{{Ao{ݡo.ூ僿ZL*zlv|&oo ̿5 癖G"oc9exk^"m.t{YӇ)?,_#. \<fX+;#q-xnT Ϯ !3IGڊkr)'y0O5+@/Y js_jtYSwu\'HMq&KK~0EEE~7}y<:x8/'Lػ*(*3s;N18~hvG h$˱ަf Y;= VPܧֺR1Cl|wןfO9h͕ӇZ 3D]}͑;Ӝnk胥ESW@4%+Vfjh'r"O5{Vo?_4hr\jk` F_s&KcHxӒp;5dž6ʻy" ]9I<'գg.gsgQzU_9Hc wY$#pJX#W+/gr뗲^_YQzͱoq/v06OχW-Fx'|{#':= }KdIASaf`Z֟=g%JC7kc=ch1qR7u8^ɭ9L[!-s+缊K3yv>9Q;?V0$->-vylprܛ+L1&ypكۿp?\o|e?\!彣1!k8^=d덊*fNy:y$w2ǓVX6j86oz1@K3NBi jR CyQ^՗\hWdz޾^ps?E>1nױ u}1M}k?lcVQ5Np̫5). d{d%9׫^׹coc>?ߛgnL35xO޼4i4y3IM3ol+7ß ^iqv_KWf7/[ef +)=ga/rF]Z6,f=at9 vnn i&yxl?DkxAϭQ^/y_/ǻ7⏨7]0~} \Kmu|ilhgQߤԕ7IrBqqU{\>{,8ZG+?X!ܟy3gzc ;&ڹn7ƭ3ϢPh垌Ftʵhs{Q l.dW yQ K}f_gyX%v 4lJVGz} C0޷CǫzwO}n^UϦ8A1Ӊ76?bj 5'י;O]}~0zv'8fsΩ v١xft\_I׿j-݂ulfmg=x9ЊC[<(1HsDZP}j q)Ol!a1"Q^K|xcWU2){ƃ}G&*~o.Y5J|v\7ջPuZ`c&t:d'gzVzvR/~=Mvެ^07o;?b8q..Y6x]+5U|$Se,7xl_K2"Bz/]+>6W{QN>b\~Z>a!BE2T)r鐱Q|vӴGoA5X]FH nk>"g|O;~15G+'ٗrg_{_{EoBawN׷`' XOĪڇ'Rle'zH>ҳ_;O۽z%f-<;𭬭.O lo>~~~M|gA24"#UsW m=^8Cƹ͌s>l 8wh8G6L-: cܲzeHށ8f /+~d+IOu/N7-_\Kl􍫵48yvVhywL3Bn1TWp>'+bZ&c9wScOn-l3cd2">Cl$;_û}oѸW ф{,yPoJ~IKxU%1&KaH%?yy9zctցLW*G2>ϱy~MgOjwSskv~f-6}l} ƩɌS~ }2A|~֡/'ͧz;`Rm7 C,C/9S:z9{ݕ_{G>Wv9R'UyuzKBxfsy`}[1[Չ5UÖ|%ԯW c]ÏsoP>A;QǠu&|b1͒,ޟ-O=Qkq)p{+uߟMo49}r%Xt5µk\6q_s8PpC}MDM>&rHb EFp3 6i-C ɸ Ct n#.}re3@+|, BE($9\^ټ/z>2gS#Xyb0^%5eϟ伓 /byRƧc:?شn^ cCA91Admd,ZӞNo9ɱϲo\KTwZY4J {Oc.z/Hrf'ӻvMl=VmJ)[HשpFS'-z{:wl#ڢOڒ-w~Hڲ0iRȘ gHcM)i˗\)+Vi'P/(rS=o:lhtOmR9%a3ã#ã[<s|FKYg>뗳t]Pv^bXe6Q腩\p^ګvNp< tM;6h,%yQ: xS2t\W^U'$G˚ZsklSwƔ.gl}3ӟm>a=d=x'Te<Ϟ*Z>]KY{GۏuXgXN9pf\tnȱǾ۝7!kܳF uUGӳ]MSzȅ#*${nkxݖݱ>NrtLM.$~ӳ1ZMMGW5M{Y4 ^ 7 O3OsyhWyKyw{ !`_ JYꡉf!;OwS=m5Z`]~;/O̡౪XBPLjűOx|3>՛vQИbcGpQ{d:fff]\3#Qb5{mV>f>uDz0ֱSn#o$z7}$+[ӏn=ZL>]??_F}E>6hl| I%Wjz̕z-O- %CN/++x>͞wǨ MOsISצ[̧N\'3NLWq>QG>gzVz.JRgP`F쒅/"|7gafi:$1W3oHYOXC؏8O1z>(_K {gc;kCy`x*)+r1YۖrvRs^} !m!:`^gmٿߢ)4f#Z9oξkN}OlӜ6Y6_-'`OGf*!" Q]{щ{?{0O<'Or)WJGr4~4f37|^*sPer~7dKp_yɯ&̞悿Co /R9$/"=Ҿw^׫jgVzhXvs7;@^a]|n;vy Y xXummFr8PEڄc/ְ/o|0u{ sf\S/1MzǾ](^{gc,WccmyGxF?[~~vԯF4lm-w0΍# a/Z.?% ҲQoԉ7*AB>J|rnj` y4}"l)c8ȇ خ/y#'ÊϜ~Qj@埨r8uuL~W(7dOmey+TcQ$sH<犡bxU3;ڞ|Ù7[zYk}8\waF@^ͣ^2Kַ{AA ne-9#s7Xc?:DM?|&VD-a-g@:~q K-Ui©s҄z?$kS=N='Ƹe=m/r|A⇼m2WO3>z~V[cŠvd `GՒPZs'a^iuK*xh0~oDs!Wj >wێ x[xz)}|rQY-N/䘌G Dta_!!/15'q2Y15+gLM$FYͯ41%O 2Lcʵ@(F]"Q>\M< {M̕ע<\0{FG^Yq$?mL';g #ifpE% OGzQVV2{#W?kkϾ[ܕòrXd\)ǚ(qwcdϒXɽ\OsߑYώzQV?Z%i)گNŎ))NwNg ~+ 0x"5ӹ,{:D HGEMYDUMť{vHy\ ڦ{Ȼ?b rʈ(#]?uo*>bT̫va0Bs jv0)l#5cKs:d1"Gwx (B܃.Y&Sm\Gyw__;4(s|'tdj\ͽֺ55 0 /Sbc/W)?v/z}<|璿2o|/8~#sχ9m'\ѣ^mę[.twqJkw{_Sؘ1$̘7MUEC0UhĜKSYP,+jZȤHs\$D)"ΰTD^"|1mk[+Epuzmy[\pSg4]}/YrQ1 /a =TVx1J&<鎑>kGe@j^„ap6|xT!0?(4STs*OIcN<29_1茅J Kh?'aC /8q!$I<.r5ZasǷ}m ]=ezF,OxW ϴ߱J&^Pwƨ垇7=v{'6ZW{ zo*}3d󼶪!؈~`ZB‡S9MKgYyIyyVNU@#H=@Dz+vg7[ra WۋϕngU!#hw7Yp=^+BBYAN G^ Ϥ}5P87dӖ]5&Nj:uϚ~,HPW砯E|t8B֝koƱT,ո_7p/ύT7ڲkIKM`OO<|5o??6h6ϕ^R +W½u8[GCZޛe^/6C\xY/-@gR BQz*汮c u={ZU&@{ ] }^'whp=(|/:ػ:(9(eU=fy9+(Fp\ܳ\6?3AGkϿ<{'cfBNq̋:8v~h~xqmƵu?"d$D, ؝)xj8H$"LO[ jos:ids^ӂU a,,Bq5([t'? \:?K @kMn,ər/U/(uM0t@MX x?'>#T[mcv!.&[- rZY|xi^nXcff} sNHcيכKɖcE Qd`A3j"ME?lHރAثs {ij&(9Eϊx"aθ'AIjl{ ~m[9[DHSZ5JZ wȢģaܫxZ^zj2DcgxiY&π޵{q%go\C鬤¾ŤW j13y\k}^k?5n{rFGU{)Hmxxn_jfhW@ ]=?mbn T^ϩÐ68XYzNI~S,E~:{=9)s~`–87tM-"/XRc"*z5 sglXHo@ \ʸm.bJE)h4u猢2?.ad墲" /.9z+gKrAf.xr6"8Lsn+1S{;ݲd-"$604:i(|琘GV{zӊIB| }" $&^YeWDh+֭ ]n L5Kl紕YxC54v9W{bn|ks!!s6aĉuDGۢ; K߳`׽Bk;q"<١5N#<:Qq90^>[% ? ?gq?GiR)2oikt֚֨+e_gS5-;\8#d"g=r6jFT/[7sJ>ft̹r7aQ9a>)8~ gt/6ЏVEBK&)MH7]ߨD{tx1^~kLiED{/[5aa;7 \lA~O?4%q_$j@{0W g=ڐo5)jV|s6 ! 3xA ȀA=jҹ̍:Fkߧh.aiC6bz'Q0NI4sb _֏I>zMku}4IXޢ~izx}W=y ?aXtV8PWGi[WRXwI[6se|/q6#ڿ2E8i׏J~18?jZ:O𞷕tA>wC-wi2x?A)!*LvZ<ӆ.Q*%:ȳjmި~斃:XVZߧRۺ 8vuQݟ~5 =orOoE._mHi3M,lfiZo -33Oͩ"8sJ7l ZAy<jC S+ĿG^aKvHo/!8: `Ƒ[T2 #g?_ߴggQ?Jzt7;#=w]̭B̟FIX9="W5빯Z=w'|n8pVFM[)(c1G64qr70Gf߰Hgwo@nyW'64ӒO|Ǻ2r+{zˆE-z[0vK LmV m_e]@]2Z9_/9d6:JohW/UpMPFKH9j^mɮ|ѯsVsMb5) {qa3|T߃p#„CC[VʳU| ' SΚ|;.^:+7 <^#.\DzhuE? 0~ }4TU,8Im^ 7oF$)WY{A3x^Q y 㱗|k==|?896X46qil:&hͺ열D˥1m6t)[{|3w^oA}x&0^N3>K_9p/7%ߡ<9rf/<o-~kOCB1C7c*ZcKଌ0u堊 sDCod}ýEg:K$ ,,m΋ )_s;ern[q4G|w큱}w;?M$|%lx4Z)Fx ыw2Y'\| B|- %e2&$]Ȕ6Z²YF~QIx❖i1)5|x.פ 5/:4+tq/]GFf뷮|e#<lXgEM=gDl?[8HBP?nMcVǣ 6І([ *.)2w>Wcź e.p ߴi݌Y; t)%x΍Q {g\2 <cgO/5~쩵p/ l¸ 5]|'lx9Z, رbAXb 2KЃkw@Z 󌌌 s/3xQoՈ3qOezoP_~Ņ#8N1`a.N#**(τ멦~HW~ :H! 3 jּ~jS |gYH=m9=uNI1=lx@Ү2mM.(΢V0ö0KQdJ2{3\%wgFri'X-X ??C04g1āetv?Cs.DsȱbӀ 2&a3box#/c4I_wtǂ\bŝ4"$)NL2Bx%ø'G!A{j,9[$bsNI|n!>^%[u}p))w6/#:`(&8Pў꺿u^yWY7?YYOT??d.9O2F>Wmb0Ct_eZAxЬjYgͪU 4+4kЬ@͊2^ r;rJNo>E]Y[оx8UƩ6R'P}TkT 죝8POڣۦ[ܧv"Bzml@x9dl#Q UK8^XXf|uoi (aJٸWFbͷ\1IģeG %?\Wv$x9uĉX@sCgoggvQܪ_oO=[O1i26~v<#MA?ng3mĹ?쳏k:}czo7:הbD.`OD&Uғum}}[\ɇОQ^!f.ѷK\2fm GD\/\Cs&N۶wvҳ'5h}EuΥܘ\2C^Q]wٸý_ހ3goe2om$G,yW8uͪʯl^$*#ou=/Qo(s5\Dz&ƇٱPZBI-cHJYStbY|vd-A]!8xȶGPֈ sb%/eD7PL$kB':8X1sb叧=oٮѫt6_ϓFYcHMٗ/VsիT9&<'I(gKksvc[$ug|CW6du/?ڄk&>N 8}ݒ=m;CwhBLrdl@~G *C#^u#lQ\QYd$rTf[~O?ZGP u+zɞ ϵ[ cp:P PgwY50@X,.8|v~o|XBԪ("%˩~R07?s^sK2)2Bqq" AEEDf(UR|"Ԍۂh:fcrsW-X1 uuuf=on+^^⻇d=ױ<(;sMi-bR_8"{(6e6,Q{FY}Y.mltO ox08Q9Rf=4⢫xhqoRw0dzZW]Ǿi5'%{qEw9ԗ%#<;-t} V6 XkLI;c Q_ҁdKIFr`2ۅ œg #>veEaY22N~7Z{=n W]" K7 ~-8hx&{˻$688.Afxl+g|d| rsx{Lu|~j]2DqQRMovٟ9.VQ\ cz+">TdNyPZ^2LDq^/+x,?üM I}|0M%%`|OxY^#‹aG(b 6T8/>PL9mgx;- &ah{suʿPL2j$W0j ,B+P]H{Oyû$\0ÆʟO,:QM՛h~[ aNċǁa?EMy4 '"ا h/BxZTa[+n7`NOݗ$ԊqZkBMKp,U" gK̝5oO&&p5~aP̸P5IDE~X܆8|զ 9 1+R"5G|ĵ#[agըzFScW à564"ؼFd77"T\QPm/Ao34/G~M V5? .Bݱjgq"r4St=V8%[&E4Wkj,׷ 4K0OsZ]Co|Qn됵ZI L ΆsZVc)\oObJ; u}b Xy y2Kԃ 8 ql% |`X e@w@yiw|"M(TBh,QyZBN ^ qpFbگT P|xi}?cI9hOk)ACSM](\G` qԹh0 .l}?%af0Կmo3?3d\W|yCA@vV1H] mv5vriU6N;Sߢofpϲ ^/kV%jkcӐ]~hyMmh*xEC()f~]@[VN9% K6Q A,j嶗T4`|1)$+dy{#X m>rW>]ˈSG;`jj!DĥkDKO/Γuze5FJKsWU3I6m:"in'cpcuMKuv5)Z`Z`:i&i)ج,;S((ZjL ]֭Reѭ*UQ+sfLfw}~>Ly<N,Q2nUL rTy+ lIjM v(F-p1jV)8Lj,3eWĻJkx# ^aocjv{UTM%H58#2?+)Leg,m4i1Zاs8g0oMLޖf)6ƳtNfH\Y[{xn5?)RP[hW /Ew0&ݧ=݇˴l?S9,fV51w崯R e n ڠw*[MfP4C4,g~o'ȱNs>^5&}Xc7zHI7yXilk!;ykܩb\Yrj2ڕ0ں>+!xTLQ*3 +}TkAڏB9|#R3Yiدv +HAeQ?B|_vGs9Z8}QO/8GF6ڵjohq^ќ896>[|G,$Sj./_:9ƺ.'Jü6^Έ8ݻ ]4E3 LdYcG-"r0 ̋ pwDܐupωo&ި837_sF};Ye`pGaSmez⬽eKW1-:o9zm`)J^I)eeLjDW[g>2_>}x"◱ecڏﰭZ|؎ ^gJ,Dg_i^{{+o{l? ֮;FnߐPk7W6g>Sg3.2yw{@Mݛ1 ٮ/HG8֋^9lul_`qV  J9xҠ%6❕"ui⥇ܙ~N?:;e9k^=sqOz#"D`D, +u^UjmYW"&'ߕEôf创Úk~V*] t3ٮGOy/zc$MQ~¼Hko43A816-֡}jdžXX{X8m?0  Hs>2Xe}wwO|k JBI[{p^_dI,%)'Ltڥ9|xSQ 3KT} cדq#i6!YY|ӪdzqTϾ)L]uSz61iBkz㸧xGEtxh#פ3EZ)yߣFmMsX{]U*9>Шf;~c.e$xUWlA?$Z@.*-Ce>lb57ҼcQ9ˇd^̉2^t.lۦ .l[(?>=͸9#-4`kd.V[yGØc]w0i]p'goi@Nmo}h4uo+ϓ*!{S4gB|0Cg26m+X<+rXy~Cb5 Wh@zпsHלP~{x褿GՕoGQ(,) :E̙7q|? 3}hC3/v8f4D i /2GܟLeoq'm[C2EшPjS1SXV*z|ՠGb?ѡ&c]fs!m$.x7?'>iv63NYCfv ̸k} .z-oMyZbM7-{.~v]s~וִ/Ū=b~.2:oe[ O/#k CXXX7L<1sskwj-0iNy1?NӸ܌N$B').=r? ޡx@e>_'so|ﮪƠb,kgO\קmWHgc z#*3=z?ԚE?'s;J w [ɸޯ1roH;U5!:V[1_{h4d&(VSKnW|'Tcϴתv[%|"b@ p晧wT]jMW=KV:sZ|晿O3 DτcgT;i;{߉x*Xqw ;i,7B1q#IϷHe6~=[6|먽o؏6|>v/wTd+ Ä;gJŗ͢7Qe~(gUDNH:u],Gyat)w\x-:=-'gBa(毜m˵D/6g2I{UWW9t~mc7S&~7y{{Xq`y7Y5aG-Ӓs9c|ޅD$j^k;n 'g}`o$Ƈ4=--Ftr1X }kQ46MoQ\'?Y;xidkDe_]: /4|Gq)D5N| ?r/Uy[Cu}:'\g0-,6tj]/O{zyǼ;=Nn'FÅpyYY^w^LoNuN-oY'5z :ij:ro0&uʙ_Lm4M{3h7vm6L-=;haeq>],zɺ2wsy"[E<9믠}}~L*xYH32jX]}FxRod3`!^FKٔǜz/y| 8~!_"~~k jyu/o@A{B4%/~0?y'$amWmŐ}l(vob9u“x(K,TfeVܩo;>*m=׉'f\..G|F?Y#Ee?Q #.kQzz-A?*q]*co8slemreEW%-a9l@aZ\]zIPw&%1^%$NSu_Ƹimn w]O2Qu(ZB{hN5{=K=׈{{$>ߟۿ'Y?l#X3D঩P eij7 7woH_ d`ΜѺ'.v8<3є:ӚjZ=C~uG^~CBE.n~fwqYX bē¬#Y=eVwlGӆqyn"% bg-[f!?XBרȱy<3$eֆM-M'T,Q/\C1y1$V\u2@?i#$pyt7s< 1| 57Ԡ.0< s&⪙sHŬ+q˻ib<ïh^3 4-NKfo8zbIzK^YܘAeycB{!h!K)f,ŌȈq}=ƜaD'|l:c[qaHϑ#֑/[}X{/S:'ջslIzK^<VBsy<6Y;*g܈C}n+<1Ior1i|#v<9r:W;']l!ca}#k+3+/-CD0ltNW?YOql  8c8~'=C,%:G8ހMܢ%:U5⏿Jkq0G 8$]aa0:-skƳ&ё;JCܩ1Ol_qss1VscNn;Xn{?m[Cr gc!Np ~sSj ܚӺ5ڸ1ڦc;b䏒bzͨ磲C2\6m[=Zq}Z7i6vUKT',y7c*Uf罹v$O}<۬Ll#Rψ'o\ᵜ1'zUŁj߷u|cS3k*Tʅ\09ބ{-{\ijc^iFG4I1'w 欆^G< urڔ6!wv'N%_r{`&c8d:u}{w<98Uv5?\y22lÎe`&d 绡f"y& J^H|(y]gfxL̈́ /%R?!Z*ɿ^l'-i_0Ix9w֮ɹKt&%Iy'u2MS/\HNMko},w|] |3yMbkU`֕eSx.7ϡΦss`:RuPSckmjzwj8l:Gv8TWd)ZJ,k]Qp7U1/gđsZ_{69gnuX:L]g99T{u֟C}P7_Pg99|9ԉC#oΆsl9:ϼ:.?:0OCogss3]PЛsg7CΡ9sCP'5mm 7C5OU՚a=u2)u),od7~&NSKo7;1V'7nn#u_8'\{r_(e!zqM{w38UW>Uo=Fc-I2[7wDDc)+Oi16vk8D0jcsA{|]E՜1n-jx@6E!^^őٗ=O*_Y43}l?p9j+|k8Md8礫pQE6E WkR~ؒs9c2/ /fz {KYw׷ẍ`^gho`J*:H!J,],OU{ةbCt0}}> !=L{,3}S_X/ig=*`:);H^wjxOB#t'vSNv/n!~q3񋛈&l$~qb aу@T 2e"27uK>^sC0#¼@_잸n-sFݳ.:uk}C4DUcnc_qg-[ Һa 3/1o_+!ᮊX/6۩ʞHA}\+5 sxL98#!Y"ƕf#N{J{b-'±k>(9YQom^ ֈ0zٶ$?XbDUE'ѧ2==nm]k1#V#Q ީ s(A/ qkZqհ'`}M!zoxxDWFņń#AS^! CP1o2}_5ǺMY>1Cߏ*j?D5QK$vˇ9FrΏDVi`v];2rr\[C?'s,eN4VS;Bep'p+"bAZM7>`m1y'%ɭ$^*i?i.̿m ; nA':x|ת8-1e1|H}^}Cvj ̥껓-ڑp6P9#ўZ5"^?~<|{D3U"?6UA{(5IcAk2gmp26|s}v䝚/b l48w5r(L·l/xLwy1of<=W/-T9fujhki8;`\)\~|j`߳L~ۚ!*FKl qq*ăsi. Q8X*n"R!c oP}oj%%/O۶5&}0L.Kz1UgW|:9?Q>yA,;'o}1i XGrކ?>1i>k0RO .9蘴;~ZόƔ^Q%zkr# [|?w^1ڳvVf(?4ehPuov*Yy+q`g$HbW̰OQWKyC}xX X QNؿB9i>ٯN9]2GOkDc!aSwXw - fW4kDLtJz6s3\'dIyTv !w_g҃xQg98u^DdܳΎc]U}O6ώԕ>\;ſ#;8q-,+?º;NMu7?3ui鿇ro/*:p4M?$W-"`ߐ[T5ElJ>*‡t8 =U :$O(YAo.U,9YfβZ w*Wt9ee=W>Xs_{/!ĵQzz5WwG٨0˻g۩~QyC$ń%Zes}"߲oT½oLx}OJߗO ؿ :L k_3}/X!K9O9roIQM\&u${ye}#w}zyygR[<=hmsxDp>%} kGs -vGtw. u+:?;}K6 m8+Zߔ(}+/Ë/k b: [罝V :[#Bߡpiܝk[>ɥ}M{M<)jZ[nG{67%N2xgu: W?[o#M޳ipp5W=\ʃ*D?%P".8 S.KP+L[<<_G|GYF#˅I̋|  ь*陋_xN:;'"gd2γCky|lD;}aN>o \G8њ' ]t" JO-]Ӝ6Ew{ֹ9f xaDZ.U /p srZ$'s V̯+@2_zB#aj6x]#LJyk { qw.ib f+Ti ,C<_!Yaw/CtV-GʍrMcoÿl]>R"6[y7JXeY5ahlbv⧔s0¥c}j};i 54M]Kxw=FnKScIG">0T¢}`G7xhQx[̄vٔiNX}ٺ`k=!S2MNˬK9$-v1aKhoca`ϸVbъ\ 5 "1bLmaSfnDj)Yz$ɯM[jFju`/ 8,nů=בʣNzOvNQp\$\15TFYR,TF }YT\k酹|?oL"V4c0ȃ?gg/T^Zm '*?qnV\FҎ Xe-ìVFo$1wdQjBl?.#7ɷىQ$ПPC