Skip to content
Snippets Groups Projects
Select Git revision
  • cb6b69e73d2a054a8c8ec06b928707e8e6963fae
  • master default
  • trunk
  • RELEASE_6_5_DRIVEDB
  • RELEASE_6_6_DRIVEDB
  • RELEASE_7_0_DRIVEDB
  • RELEASE_7_2_DRIVEDB
  • RELEASE_7_3_DRIVEDB
  • RELEASE_6_0_DRIVEDB
  • RELEASE_6_1_DRIVEDB
  • RELEASE_6_2_DRIVEDB
  • RELEASE_6_3_DRIVEDB
  • RELEASE_6_4_DRIVEDB
  • tags/RELEASE_7_4
  • tags/RELEASE_7_3
  • RELEASE_5_41_DRIVEDB
  • RELEASE_5_42_DRIVEDB
  • RELEASE_5_43_DRIVEDB
  • tags/RELEASE_7_2
  • tags/RELEASE_7_1
  • tags/RELEASE_7_0
  • RELEASE_5_40_DRIVEDB
22 results

NEWS

Blame
  • user avatar
    ballen4705 authored
    git-svn-id: https://smartmontools.svn.sourceforge.net/svnroot/smartmontools/trunk@1263 4ea69e1a-61f1-4043-bf83-b5c94c648137
    cb6b69e7
    History
    NEWS 3.05 KiB
    smartmontools NEWS
    ------------------
    CVS ID: $Id: NEWS,v 1.11 2003/11/19 21:34:07 ballen4705 Exp $
    
    The most up-to-date version of this file is:
    http://cvs.sourceforge.net/viewcvs.py/smartmontools/sm5/NEWS?sortby=date&view=markup
    
    
    Date: 2003-11-18
    Summary: smartmontools release 5.25
    -----------------------------------
    From this point on, even numbered releases will be 'stable' ones and
    odd numbered releases (like this one) will be
    unstable/testing/development ones.  This release should not hang when
    accessing USB devices. It provides SCSI self-test log monitoring, and
    a larger table of known ATA drives.  DEVICESCAN should work correctly
    even on file systems containing XFS or JFS partitions, and on machines
    that use devfs, even without traditional links.
    
    Date: 2003-10-28
    Summary: smartmontools release 5.22
    -----------------------------------
    Replaces flawed 5.21 release: the -T verypermissive option had to be
    entered as -T verpermissive. First experimental solaris support (SCSI
    only).
    
    
    Date: 2003-10-14
    Summary: smartmontools release 5.21
    -----------------------------------
    Preliminary support for FreeBSD added to smartmontools.  For FreeBSD,
    ATA support requires a 5.1-CURRENT kernel while SCSI support should
    work across multiple versions (any that support CAM).
    
    
    Date: 2003-10-04
    Summary: smartmontools release 5.20
    -----------------------------------
    Replaces flawed 5.19 release (which had a zero-length man page
    smartd.conf.5).
    
    
    Date: 2003-10-03
    Summary: smartmontools release 5.19
    -----------------------------------
    This is the first release of smartmontools based on autoconf/automake.
    For this reason, it is a very experimental release.  Please let us
    know in particular about documenation errors/omissions, missing or
    unneccesary files, and similar oversights.  The major changes are:
     [1]  installation scripts based on autoconfig/automake
     [2] ./configure [options] lets you set arbitrary paths
     [3] supports FHS with ./configure --prefix=/usr/local
     [4] correct paths are inserted into all man pages, binaries, etc.
     [5] tarballs and RPMs are now GPG-signed
    
    
    Date: 2003-10-02 11:35
    Summary: smartd SEGV
    --------------------
    Some versions of smartd, including smartmontools release 5.1-18, will
    SEGV if the combination of Directives in /etc/smartd.conf contains
    -l error
    AND/OR
    -l selftest
    without any Attribute monitoring Directives.  This is fixed in 5.19
    and above.
    
    A good workaround is to add:
    -o on
    OR
    -o off
    to enable or disable automatic offline data collection.
    
    
    Date: 2002-11-17 07:41
    Summary: testunitready bug in smartd
    ------------------------------------
    A bug in smartd prevented functioning on scsi devices.
    The bug in question only affects smartd users with scsi devices.
    To see if your version of smartd has the testunitready() bug, do
    smartd -V
    If the version of the module smartd.c in a line like:
    Module: smartd.c revision: 1.66 date: 2002/11/17
    has a revision greater than or equal to 1.30, and less than or
    equal to 1.64, then your version of the code has this problem.
    
    This problem affected releases starting with RELEASE_5_0_16 up to and
    including RELEASE_5_0_43.