All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mark Haverkamp <markh@osdl.org>
Cc: Mark Salyzyn <mark_salyzyn@adaptec.com>,
	Christoph Hellwig <hch@infradead.org>,
	Ross Macintyre <raz@macs.hw.ac.uk>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: adaptec 2120S software under RedHat 8.0 and FC2
Date: Sun, 20 Mar 2005 09:09:20 +0000	[thread overview]
Message-ID: <20050320090920.GA12000@infradead.org> (raw)
In-Reply-To: <1111009971.17676.33.camel@markh1.pdx.osdl.net>

On Wed, Mar 16, 2005 at 01:52:51PM -0800, Mark Haverkamp wrote:
> On Wed, 2005-03-16 at 08:02 -0500, Salyzyn, Mark wrote:
> > The applications require the Adaptec Branch of the driver in order to
> > function (mainly because the kernel.org branch drops the
> > /proc/scsi/aacraid entry). I have submitted a patch to Mark Haverkamp
> > for consideration where we add the information back to the /sys
> > filesystem, and the /proc filesystem (with CONFIG_PROC_FS defined) that
> > will help re-enable the applications.
> 
> The proc info code was removed almost two years ago.  I assume that it
> was removed because of the move away from using /proc and towards
> using /sys.  Christoph, is that the reason for its removal?

Yes.  Note that aacraid never had a non-trivial proc_info handler in mainline.

> 
> 
> Mark.
> 
> > 
> > There is also a Public GPL daemon, aeventd, that provides event services
> > that you may consider.
> > 
> > I will provide the sources for both under separate cover.
> > 
> > Sincerely -- Mark Salyzyn
> > 
> > -----Original Message-----
> > From: linux-scsi-owner@vger.kernel.org
> > [mailto:linux-scsi-owner@vger.kernel.org] On Behalf Of Ross Macintyre
> > Sent: Wednesday, March 16, 2005 6:20 AM
> > To: linux-scsi@vger.kernel.org
> > Subject: adaptec 2120S software under RedHat 8.0 and FC2
> > 
> > Could someone possibly help?
> > 
> > I have upgraded a machine from RedHat 8.0 to FC2 and the
> > adaptec-browser1 and adaptec-smbe software that I installed is not
> > working
> > properly. It looks ok at first glance but if I pull a disk out I only
> > get
> > informed of the 'informational' type messages.
> > (Also the browser interface to the RAID doesn't notice that the disk has
> > been pulled)
> > 
> > These are the RPMs that I installed from adaptec:
> >   adaptec-browser-1.2b-2
> >   adaptec-smbe-1.01.005-0
> > 
> > and I am running this kernel: 2.6.8-1.521smp
> > 
> > Note the mail part works ok and I do get informational messages when I
> > use
> > the browser interface and I tell it to rescan, (the array is rebuilt
> > ok),
> > but after the disk is pulled, from the browser interface it still shows
> > the disk as being there, and it is only when I tell it to rescan that it
> > starts sending out the informational messages and rebuilds.
> > The messages are logged to /var/log/messages but it seems that anotifyd
> > is
> > not picking them up.
> > 
> > Maybe I just need to upgrade the firmware and put on the latest RPMs?
> > I think I am at firmware revision 7244.
> > 
> > I have attached the anotify.conf file.
> > 
> > Thanks in advance,
> > Ross
> > 
> -- 
> Mark Haverkamp <markh@osdl.org>
> 
---end quoted text---

  reply	other threads:[~2005-03-20  9:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 13:02 adaptec 2120S software under RedHat 8.0 and FC2 Salyzyn, Mark
2005-03-16 21:52 ` Mark Haverkamp
2005-03-20  9:09   ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-23 15:37 Salyzyn, Mark
2005-03-23 17:43 ` Markus Lidel
2005-03-28 21:57 ` Christoph Hellwig
2005-03-22 17:43 Salyzyn, Mark
2005-03-23 11:05 ` Christoph Hellwig
2005-03-17 13:41 Salyzyn, Mark
2005-03-20  9:12 ` Christoph Hellwig
2005-03-22 16:32   ` Ross Macintyre
2005-03-23 11:04     ` Christoph Hellwig
2005-03-23 17:53       ` Markus Lidel
2005-03-24 17:19       ` Ross Macintyre
2005-03-16 11:20 Ross Macintyre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050320090920.GA12000@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    --cc=markh@osdl.org \
    --cc=raz@macs.hw.ac.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.