Home | History | Annotate | Line # | Download | only in mac68k
upgrade revision 1.6
      1 <<<<<<< upgrade
      2 The upgrade to NetBSD _VER is a binary upgrade; it would be prohibitive
      3 to make users upgrade by compiling and installing the _VER sources, and
      4 it would be very difficult to even compile a set of instructions that
      5 allowed them to do so.  Because of the many changes to the system, it
      6 is difficult and impractical to upgrade by recompiling from the sources
      7 and installing.
      8 
      9 There is no upgrade program for upgrading to release _VER for the
     10 NetBSD/mac68k architecture.  The current procedure is basically to perform
     11 a new install from scratch.  It is hoped that there will be a good upgrade
     12 procedure for future releases.  Please feel free to volunteer to help
     13 replace these installation tools.
     14 
     15 The following steps outline the current upgrade procedure.  These steps
     16 should help ease the upgrade process.  Please read these instructions
     17 carefully and completely before proceeding:
     18 
     19 1) Since upgrading involves replacing the kernel and most of the system
     20    binaries, it has the potential to cause data loss.  You are strongly
     21    advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the
     22    NetBSD partition or on another operating system's partition, before
     23    beginning the upgrade process.  Although the upgrade should not
     24    damage your filesystem(s) in any way, you never know what may happen.
     25 
     26 2) Download the distribution sets you want from the "mac68k/binary/sets"
     27    subdirectory of the NetBSD _VER distribution.  You will need the base
     28    set and the kernel at a minimum.  Be sure to download the files in
     29    _binary_ mode.  If you will be upgrading from within NetBSD, make sure
     30    that you place the distribution sets on a filesystem you will be able to
     31    reach from single-user mode.
     32 
     33 3) Install the _VER kernel.  You may either use the Installer utility
     34    (included in the "installation/misc" subdirectory) or install from
     35    within NetBSD (the latter is recommended for speed reasons).  If you
     36    choose the former, proceed as you normally would.  If you choose to
     37    install from within NetBSD, then boot (or shutdown) into single-user
     38    mode and do the following:
     39 
     40      cd /
     41      tar -zxvpf /path/to/kern.tgz
     42 
     43    There is no need to explicitly backup your old kernel since it will be
     44    incapable of running many of the newer binaries you are about to
     45    install (unless, of course, you have a backup copy of your older
     46    binaries and want to revert to them for some reason).
     47 
     48 4) If you are installing using the Installer, skip to step 5.  Otherwise,
     49    reboot into NetBSD in single-user mode.  Run 'fsck -f' and then mount all
     50    local partitions read/write.  Usually 'mount -a -t nonfs' should do the
     51    trick, but if you have several partitions on the same disk, take note of
     52    the fact that a change in partition numbering may have moved a few of
     53    your partitions around.  You can do a 'disklabel sdX' (where X is a
     54    drive on which you have NetBSD partitions) to see how the partitions are
     55    currently layed out.  It is likely that a partition has shifted into
     56    'sdXe', a slot that was often not available under previous releases of
     57    NetBSD.  If this is the case, you will need to manually mount your root
     58    partition  (via 'mount -w /') and edit your /etc/fstab file to reflect
     59    the new partition layout.  Unless you are familiar with 'ex' or 'ed',
     60    the easiest way to fix your /etc/fstab file is probably to simply do a
     61    'cat > /etc/fstab' and type in the corrected file in its entirety. 
     62 
     63 5) Install the distribution sets.  Keep in mind that the NetBSD _VER
     64    distribution takes up a considerably larger amount of disk space than
     65    did the 1.2 or 1.2.1 distributions.  If you are using the Installer,
     66    proceed normally (remember that you will need to mount non-root
     67    partitions by hand using the MiniShell before installing).  If you are
     68    installing from within NetBSD, do the following:
     69 
     70      cd /
     71      tar --unlink -zxvpf /path/to/base.tgz
     72 
     73    It is crucial that you use the '--unlink' flag when invoking tar or you
     74    will fail to correctly overwrite some files.  Keep in mind that there is
     75    no going back once you have installed the base set short of a complete
     76    re-install of an earlier distribution.  Continue with the appropriate
     77    command line for each of the other sets you wish to install except for
     78    the etc set.  If you are in the Installer, open up the Minishell and do
     79    the following:
     80 
     81      cd /tmp
     82      exit
     83 
     84    Now, use the Installer to install the etc set (it will install into
     85    /tmp instead of the /etc/ directory).
     86 
     87    If you are in NetBSD, do the following instead:
     88 
     89      cd /tmp
     90      tar --unlink -zxvpf /path/to/etc.tgz
     91 
     92 6) If you are in the Installer, quit it and boot into NetBSD in single-user
     93    mode.  From there, 'cd' to the /tmp/etc directory and compare each file
     94    there with your old files in /etc.  You will probably want to replace
     95    some of your system configuration files, or incorporate some of the
     96    changes in the new versions into yours.  You should take note of the
     97    following when upgrading to the NetBSD _VER etc.tgz set:
     98 
     99    * The first file to pay attention to is /etc/rc.conf.  This file did not
    100    exist under NetBSD 1.2, but it is used to configure the rc scripts
    101    under NetBSD _VER.  Edit the file to your preferences, making sure
    102    that you change the line that says:
    103 
    104      rc_configured=NO
    105 
    106    to read:
    107 
    108      rc_configured=YES
    109 
    110    This will enable all of the options you have configured in /etc/rc.conf.
    111 
    112    * The next important item to take note of is the new networking
    113    configuration files.  If you currently have an /etc/hostname.xxN file
    114    (fill in the xx with either ae or sn and the X with a number), you will
    115    need to convert it into an ifconfig.xxN file before networking
    116    automatically works.  The format for the new file is simply the
    117    arguments which you would give to ifconfig on the command line.  The
    118    following is an example of the minimal ifconfig.xxN file:
    119 
    120      inet hostname.domain.dom netmask 0xffffff00
    121 
    122    Read the ifconfig(8) man page for more details on arguments to ifconfig.
    123    Be sure to set
    124 
    125      auto_ifconfig=YES
    126 
    127    in /etc/rc.conf to ensure that your network interfaces will be brought
    128    up automatically on boot.
    129 
    130    * Many of the options given to many of the file systems have changed,
    131    and some of the file systems have changed names.  IT IS IMPERATIVE THAT
    132    YOU CHANGE ANY INSTANCES OF "ufs" IN /etc/fstab TO "ffs".  To find out
    133    more about different filesystem options, read the man page for the
    134    associated mount command (e.g. mount_mfs(8) for MFS filesystems, note:
    135    FFS type filesystems are documented in the mount(8) man page).  If you
    136    have not already done so, you may also need to correct /etc/fstab for
    137    a shift in the partition numbering scheme.  See step (4) above for more
    138    details.
    139 
    140    * You will also probably want to upgrade your device nodes at this time
    141    as well.  Make sure you have installed the latest MAKEDEV script (it
    142    should be included in the etc set) and perform the following commands:
    143 
    144      cd /dev
    145      sh MAKEDEV all
    146 
    147 
    148 7) A number of binaries have changed their locations from NetBSD 1.2.1 to
    149    NetBSD _VER (most of these have moved from /sbin to /usr/sbin).  A few
    150    binaries have been removed.  It is probably best if you scan the
    151    modification dates of the files in the /sbin directory.  If there are
    152    files in the directory which have newer counterparts in the /usr/sbin
    153    directory, it is a very good idea to remove the older files (you will
    154    probably run into difficulties later if you choose not to do this). 
    155    You should also check the /sbin, /bin, /usr/bin/, and /usr/sbin
    156    directories for old binaries that are no longer part of the NetBSD
    157    distribution and delete them as well.  In general, all the files in a
    158    particular distribution should have similar modification dates, so
    159    looking at these is a good way of determining a file's age.
    160 
    161 8) Run 'fsck -f' to make sure that your filesystem is still consistent.  If
    162    fsck reports any errors, fix them by answering 'y' to its suggested
    163    solutions (note: if there are a large number of errors, you may wish
    164    to stop and run 'fsck -fy' to automatically answer "yes" instead).
    165 
    166 9) Exit from single-user mode and it should continue to boot into
    167    multi-user mode.
    168 
    169 At this point you have successfully upgraded to NetBSD _VER.
    170 ||||||| 1.4
    171 There is no upgrade to release _VER for the NetBSD/mac68k architecture.
    172 It is hoped that there will be a good upgrade procedure for future
    173 releases.  Please feel free to volunteer to help replace these
    174 installation tools.
    175 =======
    176 The upgrade to NetBSD _VER is a binary upgrade; it would be prohibitive
    177 to make users upgrade by compiling and installing the _VER sources, and
    178 it would be very difficult to even compile a set of instructions that
    179 allowed them to do so.  Because of the many changes to the system, it
    180 is difficult and impractical to upgrade by recompiling from the sources
    181 and installing.
    182 
    183 There is no upgrade program for upgrading to release _VER for the
    184 NetBSD/mac68k architecture.  The current procedure is basically to perform
    185 a new install from scratch.  It is hoped that there will be a good upgrade
    186 procedure for future releases.  Please feel free to volunteer to help
    187 replace these installation tools.
    188 
    189 The following steps outline the current upgrade procedure.  These steps
    190 should help ease the upgrade process.  Please read these instructions
    191 carefully and completely before proceeding:
    192 
    193 1) Since upgrading involves replacing the kernel and most of the system
    194    binaries, it has the potential to cause data loss.  You are strongly
    195    advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the
    196    NetBSD partition or on another operating system's partition, before
    197    beginning the upgrade process.  Although the upgrade should not
    198    damage your filesystem(s) in any way, you never know what may happen.
    199 
    200 2) Download the distribution sets you want from the "mac68k/binaries"
    201    subdirectory of the NetBSD _VER distribution.  You will need the base
    202    set and the kernel at a minimum.  Be sure to download the files in
    203    _binary_ mode.  If you will be upgrading from within NetBSD, make sure
    204    that you place the distribution sets on a filesystem you will be able to
    205    reach from single-user mode.
    206 
    207 3) Install the _VER kernel.  You may either use the Installer utility
    208    (included in the utils subdirectory) or install from within
    209    NetBSD (the latter is recommended for speed reasons).  If you choose
    210    the former, proceed as you normally would.  If you choose to install from
    211    within NetBSD, then boot (or shutdown) into single-user mode and do the
    212    following:
    213 
    214      cd /
    215      tar -zxvpf netbsd13  (substitute the full path to archive here)
    216 
    217    There is no need to explicitly backup your old kernel since it will be
    218    incapable of running many the newer binaries you are about to install.
    219 
    220 4) If you are installing using the Installer, skip to step 5.  Otherwise,
    221    reboot into NetBSD in single-user mode.  Run 'fsck -f' and then mount all
    222    local partitions read/write.  Usually 'mount -a -t nonfs' should do the
    223    trick, but if you have several partitions on the same disk, take note of
    224    the fact that a change in partition numbering may have moved a few of
    225    your partitions around.  You can do a 'disklabel sdX' (where X is a
    226    drive on which you have NetBSD partitions) to see how the partitions are
    227    currently layed out.  It is likely that a partition has shifted into
    228    'sdXd', a slot that was not available under previous releases of NetBSD.
    229    If this is the case, you will need to manually mount your root partition
    230    (via 'mount -w /') and edit your /etc/fstab file to reflect the new
    231    partition layout.  Unless you are familiar with 'ex', the easiest way to
    232    fix your /etc/fstab file is probably to simply do a 'cat > /etc/fstab'
    233    and type in the corrected file in its entirety. 
    234 
    235 5) Install the distribution sets.  Keep in mind that the NetBSD _VER
    236    distribution takes up a considerable amount more of disk space than did
    237    the 1.2 or 1.2.1 distributions.  If you are using the Installer, proceed
    238    normally (remember that you will need to mount non-root partitions by
    239    hand using the MiniShell before installing).  If you are installing from
    240    with NetBSD, do the following:
    241 
    242      cd /
    243      tar --unlink -zxvpf base13 (substitute the full path to the archive here)
    244 
    245    It is crucial that you use the '--unlink' flag when invoking tar or you
    246    will fail to correctly overwrite some files.  Keep in mind that there is
    247    no going back once you have installed the base set short of a complete
    248    reinstall of an earlier distribution.  Continue with the appropriate
    249    command line for each of the other packages you have installed except for
    250    the etc package.  If you are in the Installer, open up the Minishell and
    251    do the following:
    252 
    253      cd /tmp
    254      exit
    255 
    256    Now, use the Installer to install the etc package (it will install into
    257    /tmp instead of the /etc/ directory).
    258 
    259    If you are in NetBSD, do the following instead:
    260 
    261      cd /tmp
    262      tar --unlink -zxvpf etc13 (substitute the full path to the archive here)
    263 
    264 6) If you are in the Installer, quit it and boot into NetBSD in single-user
    265    mode.  From there, 'cd' to the /tmp/etc directory and compare each file
    266    there with your old files in /etc.  You will probably want to replace
    267    some of your system configuration files, or incorporate some of the
    268    changes in the new versions into yours.  You should take note of the
    269    following when upgrading to the etc13 set:
    270 
    271    * The first file to pay attention to is /etc/rc.conf.  This file did not
    272    exist under NetBSD 1.2, but it is used to configure the rc scripts
    273    under NetBSD _VER.  Edit the file to your preferences, making sure that
    274    you change the line that says:
    275 
    276      rc_configured=NO
    277 
    278    to read:
    279 
    280      rc_configured=YES
    281 
    282    This will enable all of the options you have configured in /etc/rc.conf.
    283 
    284    * The next important item to take note of is the new networking
    285    configuration files.  If you currently have an /etc/hostname.xxN file
    286    (fill in the xxN with either ae0 or sn0), you will need to convert it
    287    into an ifconfig.xxN file before networking automatically works.  The
    288    format for the new file is simply the arguments which you would give
    289    to ifconfig on the command line.  The following is an example of the
    290    minimal ifconfig.xxN file:
    291 
    292      inet hostname.domain.dom netmask 0xffffff00
    293 
    294    Read the ifconfig(8) man page for more details on arguments to ifconfig.
    295    Be sure to set
    296 
    297      auto_ifconfig=YES
    298 
    299    in /etc/rc.conf to ensure that your network interfaces will be brought
    300    up automatically on boot.
    301 
    302    * Many of the options given to many of the file systems have changed,
    303    and some of the file systems have changed names.  IT IS IMPERATIVE THAT
    304    YOU CHANGE ANY INSTANCES OF "ufs" IN /etc/fstab TO "ffs".  To find out
    305    more about different filesystem options, read the man page for the
    306    associated mount command (e.g. mount_mfs(8) for MFS filesystems, note:
    307    FFS type filesystems are documented in the mount(8) man page).  If you
    308    have not already done so, you may also need to correct /etc/fstab for
    309    a shift in the partition numbering scheme.  See step (4) above for more
    310    details.
    311 
    312    * You will also probably want to upgrade your device nodes at this time
    313    as well.  Make sure you have installed the latest MAKEDEV script (it
    314    should be included in the etc set) and perform the following commands:
    315 
    316      cd /dev
    317      sh MAKEDEV all
    318 
    319 
    320 7) A number of binaries have changed their locations from NetBSD 1.2.1 to
    321    NetBSD _VER (most of these have moved from /sbin to /usr/sbin).  A few
    322    binaries have been removed.  It is probably best if you scan the
    323    modification dates of the files in the /sbin directory.  If there are
    324    files in the directory which have newer counterparts in the /usr/sbin
    325    directory, it is a very good idea to remove the older files (you will
    326    probably run into difficulties later if you choose not to do this). 
    327    You should also check the /sbin, /bin, /usr/bin/, and /usr/sbin
    328    directories for old binaries that are no longer part of the NetBSD
    329    distribution and delete them as well.  In general, all the files in a
    330    particular distribution should have similar modification dates, so
    331    looking at these is a good way of determining a file's age.
    332 
    333 8) Run 'fsck -f' to make sure that your filesystem is still consistent.  If
    334    fsck reports any errors, fix them by answering 'y' to its suggested
    335    solutions (note: if there are a large number of errors, you may wish
    336    to stop and run 'fsck -fy' to automatically answer "yes" instead).
    337 
    338 9) Exit from single-user mode and it should continue to boot into
    339    multi-user mode.
    340 
    341 At this point you have successfully upgraded to NetBSD _VER.
    342 >>>>>>> 1.5
    343