1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh
4 <imp@village.org>. Please send new entries directly to him. See end
5 of file for further details. For commonly done items, please see the
6 COMMON ITEMS: section later in the file.
9 The PAM libraries have had an API upgrade that is beyond
10 the ability of the shared library major number to handle.
11 It is manifested by PAM-using ports dumping core. The
12 solution is to rebuild those ports.
15 The kernel compile module has moved from src/sys/compile/FOO
16 to src/sys/${MACHINE}/compile/FOO.
19 The pccard modem issue has been corrected. OLDCARD support is
20 still a little weak in -current. slot 1 is known not to work
21 on some TI based cardbus bridges. Some cardbus bridges do not
22 properly detect insert/removal events. IRQ configuration needs
26 Softupdates problems have been corrected.
29 Peter ripped out the linkerset support. You must, as always,
30 rerun config after you cvsup if you are using the traditional
31 kernel building methods.
34 pccard modems may not work with current after 20010604 date. Some
35 do, others result in panics. *MAKE*SURE* that you update your
36 config and /etc/rc.conf ala the 20010604 entry, or you will have
37 problems (this issue will be fixed, it just hasn't been yet).
40 SOFTUPDATES seem to be broken since the middle of May or so. Do not
41 use them in current. You can disable softupdates on all mounted
42 partitions, or remove SOFTUPDATES the kernel config file.
45 After Peter's commits to the hints code, people have been noticing
46 that certain devices are attached (or try to) twice. This is due
47 to having both static hints as well as a /boot/device.hints. To
48 work around this issue, please use only one or the other mechanism
49 until this bug is fixed.
51 Please note that a feature of config is that if you have config
52 file FOO and FOO.hints, it automatically adds FOO.hints to the
53 hints.c file, wheather you want it to or not.
56 Locale names have changed to match other systems better.
59 pccard support for pci cards has been committed. You must change
60 your /etc/pccard.conf irq lines. It must match the irq used by
61 pcic device. Interrupt storms may result if you fail to do this.
62 Interrupt storms look a lot like a hang.
64 You must also install a new pccardd, otherwise you will get an
65 interrupt storm at card reset time (just after it tells you what
68 pccardd_flags="-I" is necessary for the time being. It tells pccardd
69 not to ask the kernel if the interrupt is really free or not before
70 using it. You can either change the /etc/pccard.conf irq lines to
71 match pcic, or add "-i X" to the pccardd_flags.
74 INSTALL=install -C is being deprecated. If you want to do this,
75 use COPY=-C instead. The former method will be supported for only
76 a limited time. If you see
78 install: warning: the -d and -C options may not be specified together
80 in your makeworld, then you need to migrate towards using
84 It appears that vm is now stable enough to use again. However,
85 there may be other problems, so caution is still urged. alpha
86 definitely is in bad shape.
89 Minor repo damanged has happened. This may cause problems
90 with cvsup of ports. If you get errors, please see
91 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
92 at the bottom for details on a workaround. The error message
94 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
97 Vm and/or swapping are busted on -current. Please be patient.
100 pccard has had much reorganizational work done to it over
101 the past few days. Everything should still work, but if
102 not, please contact imp@freebsd.org.
105 ata ioctl changed. Make sure to recompile both kernel and
106 userland at the same time.
109 New ncurses imported.
112 DEVFS is now opt out, not opt in. Barring major problems, this
113 will be the only way to go starting July 1.
116 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
119 Building perl was broken at 02:25:25 PDT.
122 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
123 go back in the water.
126 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
127 this date, but before the correction date.
130 old fsck and new kernel interactions appear to have been fixed.
133 fsck and the kernel were changed to handle some optimizations
134 to directory layout. This breaks backward compatibility.
135 Update only if you understand that you must not use the old
136 fsck with the new kernel ever.
139 fsck has changed the meaning of the pass column in /etc/fstab.
140 Please see the cvs commit to fsck.8 or the fsck.8 man page for
141 details. It is unclear if changes to /etc/fstab are necessary.
144 portmap had changed name to rpcbind for maximum POLA in your
145 current world. /etc/hosts.{allow,deny} needs changes. nfs and
146 other rpc based programs that rely on portmapper will not work
147 without updates to /etc/hosts.{allow,deny} and /etc/netcofnig.
150 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
151 and ATA_ENABEL_TAGS are no longer kernel options. They have
152 been replaced by tunables. See ata.4 for details.
155 The fxp driver was converted to use miibus. If you compile
156 fxp into your kernel statically, you will need to add miibus.
159 The wi device now defaults to BSS (infrastructure) mode
163 /dev/urandom should be a symbolic link to /dev/random now.
164 Users of current not using DEVFS need to run MAKEDEV std.
165 ssh might not work if you don't.
168 The problems with libc have been corrected. It is now mostly
169 safe to go back into the water.
172 The size of FILE was changed. This breaks upgrading. If
173 you must upgrade, be prepared for pain. It also breaks almost
174 all binaries that you've compiled on -current. You are warned
175 that before upgrading would be a good time to do a level 0
176 dump of your system. No, really, I mean it this time.
178 To get to the new system, you'll need to use the following
179 workaround. Hopefully this can be sorted out so that we
180 don't have to move this to the updating section.
182 To get around the installworld problem, do:
183 # cd /usr/src/usr.bin/sed
187 If that doesn't work, then try:
188 # make -k installworld
192 DEVFS is now the default. If you use vinum, make sure that you
193 do not include devfs in your kernel as problems result.
196 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
197 Remove them from your config.
200 ****************************** WARNING ******************************
201 buildkernel has been changed slightly
202 ****************************** WARNING ******************************
203 KERNCONF replaces the variable KERNEL for buildkernel. You
204 should update your scripts and make.conf accordingly.
207 config has changed to allow DEV_FOO as a replacement for NFOO.
208 This requires a new config to build correctly.
211 The kerrnel option I386_CPU is now mutually exclusive with the
212 other cpu types. If you have an i386 system, be sure that it
213 only had this line. Remove it for all other configurations.
216 Changes to the kernel require it and burncd be in sync.
219 Everyone who has hw.sndunit set to something in
220 /etc/sysctl.conf, it is now hw.snd.unit.
223 ex and vi were broken by some changes to sys/queue.h. If you
224 have a bad vi, you will see make buildworld fail with a core
225 dump while building termcap. You can work around this problem
226 by adding -k to your make buildworld. This will cause the
227 build to complete and install a new vi. Once that's done, you
228 can rebuild again without the -k to pick up anything that
229 might have been ignored by the -k option.
231 Others have suggested that you can just rebuild libc if your
232 vi/ex is dynamically linked, but I've not received any reports
236 There have been some changes to libcrypt in -current. The
237 libscrypt/libdescrypt symlink sillyness is gone and the installed
238 libcrypt is fully functional. Be aware of this.
241 Linksys Fast Ethernet PCCARD cards supported by the ed driver
242 now require the addition of flag 0x80000 to their config line
243 in pccard.conf(5). This flag is not optional. These Linksys
244 cards will not be recognized without it.
247 Important new FreeBSD-version stuff: PAM support has been worked
248 in, partially from the "Unix" OpenSSH version. This requires
249 adding the following in pam.conf:
251 sshd auth sufficient pam_skey.so
252 sshd auth required pam_unix.so try_first_pass
253 sshd session required pam_permit.so
259 The random device needs more entropy, so you need to make sure
260 that you've run mergemaster to get a /etc/rc which will seed
261 /dev/random. If you don't and the system hangs after ldconfig,
262 then banging on the keyboard randomly until it unhangs is one
266 ****************************** WARNING ******************************
267 Sendmail has been updated.
268 ****************************** WARNING ******************************
269 o mail.local(8) is no longer installed as a set-user-id binary.
270 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
272 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
274 o Now using sendmail's version of vacation(1).
275 o The sendmail cf building tools (contrib/sendmail/cf) are installed
276 in /usr/share/sendmail/cf.
277 o sendmail.cw changed to local-host-names
279 More details can be found at
280 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
283 The ports tree's new layout is in place. Be sure to update
284 your entire ports tree, or you will have problems.
287 The perl build procedure no longer installs miniperl, nor uses
288 the installed miniperl. It is recommended that you delete
292 This weekend the ports tree will be updated to a new layout.
293 It will be in an inconsistent state until noted in the UPDATING
294 file, or with asami-san's message to the relevant mailing
295 lists. With this new layout, you'll need to update the whole
296 tree for anything to work.
299 There was a change in the passwd format. Need more information.
302 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
303 place. Please update boot loader (not the boot blocks) at the
304 same time as your kernel.
307 The new pmtimer device is necessary for laptops. Failure to
308 include the device will cause suspended laptops losing time
309 when they resume. Include
311 in your config file and
312 hint.pmtimer.0.at="isa"
313 to your /boot/device.hints file.
316 The random device has been turned into a (pseudo-)device,
317 rather than an option. The supplied kernel config files have
318 been updated. You will need to do something similar in your
319 own kernel config file.
324 If you prefer to load the loadable module, you need to do
328 The random device module has been renamed from randomdev.ko to
329 random.ko. You will need to edit your /boot/loader.conf to
330 reflect this if you load this module at boot time.
331 The line should read:
335 The SMPNG commit has happened. It should work, but if it
336 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
337 to be a variety of minor issues. Please see 20000905 to make
338 sure you don't have model loading problems which might at
339 first blush appear related to SMP.
342 nsswitch has been imported from NetBSD. Among other things,
343 this means that /etc/host.conf is no longer used. See
344 nsswitch.conf(5) instead. Note that at boot time rc.network
345 will attempt to produce a new nsswitch.conf file for you if you
346 don't have one, and you have host.conf.
349 The ucred structure changed size. This breaks the interface
350 that mountd uses. Trying to use an older mountd with a newer
351 kernel guarantees a panic. This means that you need to use
352 kernels newer than today only with matching mountd, but you
353 needed to do that anyway with the boot loader changes.
356 The boot loader has been updated. The new default kernel is
357 now /boot/kernel/kernel.ko. The new default module location
360 You *MUST* upgrade your boot loader and kernel at the same time.
361 The easiest way to do this is to do the buildworld/buildkernel/
362 installkernel/installworld dance.
364 Furthermore, you are urged to delete your old /modules directory
365 before booting the new kernel, since kldload will find stale
366 modules in that directory instead of finding them in the correct
367 path, /boot/kernel. The most common complaint that this cures
368 is that the linux module crashes your machine after the update.
370 if [ ! -d /boot/kernel.old ]; then
371 mv /modules.old /boot/kernel.old
372 chflags noschg /kernel.old
373 mv /kernel.old /boot/kernel.old/kernel.ko
374 chflags schg /boot/kernel.old/kernel.ko
378 A new issue with the sendmail upgrade has come to light.
379 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
380 incorrectly install the default aliases in /etc/mail rather than
381 move the old one from /etc. So you'll need to manually move the
382 file, create a symbolic link, remove the old /etc/aliases.db and
383 run newaliases. For safety sake, you should stop sendmail
384 while doing this and run the upgrade when locally sourced email
385 is not likely to be generated.
388 /boot/device.hints is now required for installkernel to
389 succeed. You should copy GENERIC.hints for your architecture
390 into /boot/device.hints. If and only if you compile hints
391 into your kernel, then this file may be empty. Please note,
392 if you have an empty or missing /boot/device.hints file and
393 you neglected to compile hints into your kernel, no boot
394 messages will appear after the boot loader tries to start the
398 If you do NOT have ``options RANDOMDEV'' in your kernel and
399 you DO want the random device then add randomdev_load="YES" to
403 suidperl is now always built and installed on the system, but
404 with permissions of 511. If you have applications that use
405 this program, you are now required to add ENABLE_SUIDPERL=true
406 to /etc/make.conf. If you forget to do this,
407 chmod 4511 /usr/bin/suidperl
408 will fix this until the next build.
411 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
412 visible changes that may immediately affect your configuration
414 - New default file locations from src/contrib/sendmail/cf/README
415 - newaliases limited to root and trusted users
416 - MSA port (587) turned on by default
417 - New queue file naming system so can't go from 8.11 -> 8.9
418 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
419 - FEATURE(`nullclient') is more full featured
420 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
421 - mail.local FreeBSD-only -b option changed to -B
422 - See src/contrib/sendmail/RELEASE_NOTES for more info
425 suidperl (aka sperl) is no longer build by default. You must
426 specifically define BUILD_SUIDPERL to "true" for it to be build.
427 Furthermore, we recommend that you remove /usr/bin/sperl* and
428 /usr/bin/suidperl files from your system unless you have a
432 Networking defaults have been tightened. Anybody upgrading
433 /etc/defaults/rc.conf needs to add the following lines to
434 /etc/rc.conf if they want to have the same setup
435 afterwards (unless the variables already are set, of course):
436 # Enable network daemons for user convenience.
439 sendmail_enable="YES"
442 If you have null_load="YES" in your /boot/loader.conf, you
443 will need to change that to nullfs_load="YES".
446 The "installkernel" target has changed slightly. Now even if
447 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
448 it will install the MYKERNEL file (built with the buildkernel
449 target) as /kernel rather than /MYKERNEL. Those who have
450 updated their /boot/loader.conf files to point to /MYKERNEL
451 should remove that entry or perform manual rename of /kernel
455 If you use CVSUP or CTM to get CVS trees, AND you used to get
456 the old crypto files from internat.freebsd.org AND you check
457 out files from the CVS tree with the cvs command, please read
458 http://people.freebsd.org/~imp/internat.txt
459 for details on potential problems that you might have and how
462 If you are merely a mirror, or don't answer yes to each of the
463 clauses above, you needn't worry.
466 /etc/security has been updated to print the inode number of
467 setuid programs that have changed. You will see a large spike
468 in the number of changed programs the first time when you run
469 mergemaster to get a new /etc/security.
472 /dev/random now has good entropy collection (from the keyboard
473 and sysmouse drivers). Please ensure that either `options
474 RANDOMDEV' is present in your kernel config file or that
475 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
476 not have the /dev/random driver, OpenSSL (and consequently
477 lots of crypto tools (like SSH)) will fail with strange
478 errors. (see below, 20000624).
480 FreeBSD-current is safe again to run Crypto.
483 phk made the malloc default options AJ. This may slow things
484 down and uncover other latent bugs in the code. If you need to
485 run at full speed, you can disable this by doing the following:
486 ln -s aj /etc/malloc.conf
489 libftpio's version was accidentally bumped a few days ago. This
490 has been corrected. You may need to remove /usr/lib/libftpio.so.6
491 before doing your next buildworld/installworld pair. It certainly
492 won't hurt to remove it before the update procedure. It will
493 break fetch until a new one is built, but ftp can be used in the
497 The crypto packages have changed for the cvsup. This has been done
498 in a backward compatible way, but the old packages will go away at
499 some point in the future. Look at /usr/share/examples/cvsup for
503 With the new sys/modules/sound/drivers/*, you will need to
504 set SYSDIR until you do an installworld after July 7th.
507 rc.shutdown and rc will now call the rc.d scripts with start
508 or stop. This may cause some harmless warnings from older
509 rc.d scripts that haven't been updated.
512 The libfetch based version of fetch has gone into the tree.
513 Minor problems may result on some of the less popular sites,
514 which should be reported to des@freebsd.org.
517 From approximately this date forward, one must have the crypto
518 system installed in order to build the system and kernel.
519 While not technically strictly true, one should treat it as
520 required and grab the crypto bits. If you are grabbing CVS
521 trees, src-all and cvs-crypto should be treated as if they
522 were required. You should check with the latest collections
523 to make sure that these haven't changed.
526 Mark Murray just committed the first parts of a cleanup of
527 /dev/zero, et al. This is also cleaning up /dev/random.
528 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
529 -CURRENT FROM THIS POINT FORWARD for cryptographic services
530 until Mark can merge in the fixes to this work in progress.
531 openssh and openssl should not be used to generate keys from this
532 date to the completion of the work.
534 If you must operate at this reduced level of security, add '
535 options RANDOMDEV' to your kernel or modload the randomdev
536 module. You may also need to copy a new MAKEDEV to /dev and
537 recreate the random and urandom devices.
540 The license on the softupdates is now a standard 2 clause
541 BSD license. You may need to remove your symbolic links
542 that used to be required when updating.
545 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
546 the config file update procedure.
547 http://people.freebsd.org/~imp/config-upd.html
548 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
549 isn't buildable. However, you can generate a LINT file.
552 Binutils 2.10 have hit the tree, or will shortly. As soon
553 as they do, the problem noted in 20000522 will be resolved and
554 that workaround will no longer be required.
557 phk removed the compatibility creation of wd devices in the
558 ad driver. If you haven't done so already, you must update
559 your fstab, etc to use the ad devices instead of the wd
562 In addition, you'll need to update your boot blocks to a
563 more modern version, if you haven't already done so. Modern
564 here means 4.0 release or newer (although older releases
568 Peter took an axe to config(8). Be sure that you read his mail
569 on the topic before even thinking about updating. You will
570 need to create a /boot/device.hints or add a hints directive
571 to your config file to compile them in statically. The format
572 of the config file has changed as well. Please see GENERIC or
573 NEWCARD for examples of the new format.
576 A new set of binutils went into the tree today. Anybody
577 building a kernel after this point is advised that they need
578 to rebuild their binutils (or better yet do a
579 buildworld/installworld) before building a new kernel.
581 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
582 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
583 is recommended that you don't set this option until the problem
587 The ethernet drivers were all updated to clean up the BPF handling.
590 The problems with boot blocks on the alphas have been corrected.
591 This will require some care in updating alphas. A new libstand
592 is requires for the boot blocks to build properly.
595 Recompile all kld modules. Proper version dependency info
599 Modules have been disconnected from the buildworld tree and
600 connected to the kernel building instead.
603 You may need to build gperf
604 cd /usr/src/gnu/usr.bin/gperf && make depend all install
605 when upgrading from 4.0 -> current. The build system now uses
606 an option only in -current.
609 The method that we brand ELF binaries has changed to be more
610 acceptable to the binutils maintainers. You will need to
611 rebrand your ELF binaries that aren't native. One problem
612 binary is the Linux ldconfig. After your make world, but
613 before you reboot, you'll need to issue:
614 brandelf -t Linux /compat/linux/sbin/ldconfig
615 if you have Linux compatibility enabled on your machine.
618 If you have really bad/marginal IDE drives, you may find they
619 don't work well. Use pio mode instead. The easiest way to
620 cope if you have a problem combination is to add:
621 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
622 to the start of /etc/rc.conf.
625 The ISA and PCI compatibility shims have been connected to the
626 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
627 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
628 include the appropriate option in your kernel config. Drivers
629 using the shims should be updated or they won't ship with
630 5.0-RELEASE, targeted for 2001.
633 We've entered the traditional post release dumping party.
634 Large kernel changes are being committed and are in the
635 works. It is important to keep the systems' klds and kernel
636 in sync as kernel interfaces and structures are changing.
637 Before reporting kernel panics, make sure that all modules
638 that you are loading are up to date.
641 If you are upgrading from an older version of FreeBSD, you
642 need to update your boot blocks as well. 'disklabel -B ad0'
643 will do the trick. This isn't critical until you remove your
644 wd device entries in /dev, at which point your system will not
648 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
649 to upgrade to 4.0 from 3.x.
655 Avoid using make -j when upgrading. From time to time in the
656 past there have been problems using -j with buildworld and/or
657 installworld. This is especially true when upgrading between
658 "distant" versions (eg one that cross a major release boundary
659 or several minor releases, or when several months have passed
660 on the -current branch).
664 If you are updating from a prior version of FreeBSD (even one just
665 a few days old), you should follow this procedure. With a
666 /usr/obj tree with a fresh buildworld,
667 make buildkernel KERNCONF=YOUR_KERNEL_HERE
668 make installkernel KERNCONF=YOUR_KERNEL_HERE
670 To just build a kernel when you know that it won't mess you up
671 --------------------------------------------------------------
672 cd src/sys/{i386,alpha}/conf
673 config KERNEL_NAME_HERE [1]
674 cd ../../compile/KERNEL_NAME_HERE
679 [1] If in doubt, -r might help here.
681 If this fails, go to the "To build a kernel" section.
683 To rebuild everything and install it on the current system.
684 -----------------------------------------------------------
686 Build a new kernel, see above.
688 To upgrade from 4.x-stable to current
689 -------------------------------------
691 make buildkernel KERNCONF=YOUR_KERNEL_HERE
692 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
693 make installkernel KERNCONF=YOUR_KERNEL_HERE
694 reboot in single user [3]
700 Make sure that you've read the UPDATING file to understand the
701 tweaks to various things you need. At this point in the life
702 cycle of current, things change often and you are on your own
703 to cope. The defaults can also change, so please read ALL of
704 the UPDATING entries.
706 Also, if you are tracking -current, you must be subscribed to
707 freebsd-current@freebsd.org. Make sure that before you update
708 your sources that you have read and understood all the recent
709 messages there. If in doubt, please track -stable which has
712 [1] If you have third party modules, such as vmware, you
713 should disable them at this point so they don't crash your
716 [2] If you have legacy ISA devices, you may need to create
717 your own device.hints to reflect your unique hardware
720 [3] From the bootblocks, boot -s, and then do
725 adjkerntz -i # if COMS is wall time
729 This file contains a list, in reverse chronological order, of major
730 breakages in tracking -current. Not all things will be listed here,
731 and it only starts on March 15, 2000. Updating files can found in
732 previous releases if your system is older than this.
734 Please filter your entries through Warner Losh (imp@village.org) so
735 that the style, formatting, etc of this file can be maintained.
737 Copyright information:
739 Copyright 1998, 2001 M. Warner Losh. All Rights Reserved.
741 Redistribution, translation and use, with or without modification, in
742 full or in part, are permitted provided that the above copyright
745 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
746 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
747 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
748 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
749 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
750 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
751 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
752 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
753 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
754 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
755 POSSIBILITY OF SUCH DAMAGE.
757 If you find this document useful, and you want to, you may buy the