Date: Wed, 3 Nov 2004 14:24:55 -0700 From: Gordon Freeman <freebsdjunkie@gmail.com> To: Ceri Davies <ceri@submonkey.net>, Gordon Freeman <freebsdjunkie@gmail.com>, freebsd-current@freebsd.org Subject: Re: FreeBSD 5.3 and Adaptec RaidUtils Message-ID: <32ab229c041103132437dbab9@mail.gmail.com> In-Reply-To: <20041103211728.GB57641@submonkey.net> References: <32ab229c041103131414015bbe@mail.gmail.com> <20041103211728.GB57641@submonkey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
The link is created (and it is just a normal symlink as far as I can tell) but once raidtuil runs the symlink disappears. devfs.conf entry: link asr0 rdptr17 On Wed, 3 Nov 2004 21:17:28 +0000, Ceri Davies <ceri@submonkey.net> wrote: > On Wed, Nov 03, 2004 at 02:14:37PM -0700, Gordon Freeman wrote: > > > > Between 5.2.1 and 5.3-RC2 the rasr device was removed: > > > > http://lists.freebsd.org/pipermail/...May/023064.html > > > > In FreeBSD 5.2.1 it use to be that using the compat4x port and > > creating a symlink of /dev/rasr0 to /dev/rdpti17 would be enough to > > allow Adaptec's RAID management binaries work. However, that trick no > > longer appears to be working. When you run Adaptec's raidutil (either > > from the port or from the Adaptec package itself) the symlink > > disappears and raidutil returns an error stating that it couldn't > > connect to /dev/rdptr17. > > > > Any ideas on why the symlink disappears or another way to get the old > > Adaptec binaries to work under FreeBSD 5.3 short of rewriting asr.c to > > include a device alias? > > Does it work if you create the symlink via devfs.conf? > > Ceri > -- > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32ab229c041103132437dbab9>