From owner-freebsd-hackers  Sun Aug 20 10:50:30 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id KAA10608
          for hackers-outgoing; Sun, 20 Aug 1995 10:50:30 -0700
Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id KAA10602
          for <hackers@freebsd.org>; Sun, 20 Aug 1995 10:50:27 -0700
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA21651; Sun, 20 Aug 1995 11:52:18 -0600
Date: Sun, 20 Aug 1995 11:52:18 -0600
From: Nate Williams <nate@rocky.sri.MT.net>
Message-Id: <199508201752.LAA21651@rocky.sri.MT.net>
To: Coranth Gryphon <gryphon@healer.com>
Cc: hackers@freebsd.org
Subject: Re: known rogue?
In-Reply-To: <199508201309.JAA00223@healer.com>
References: <199508201309.JAA00223@healer.com>
Sender: hackers-owner@freebsd.org
Precedence: bulk

> Hi. What does the phrase 
> 
> 	st0: Archive Viper 150 is a known rogue
> 
> actually mean?

It means that the tape doesn't work quite like the SPEC says it should.

> It seems to mean that the tape is not really supported.

Nope, the tape is supported.  However, depending on which version of the
tape firmware is on board, you may/may not need to remove the rogue
entry out of the kernel.  My 150 didn't work correctly with the rogue
entry, so I commented it out and all was well.


Nate