On Mon, Mar 23, 1998 at 09:23:00AM -0500, Gerard Hickey wrote:
No, it just needs someone dedicated to maintaining it. It took me four times to try to get the contact information corrected! When I submitted my third request, I received back a message stating that it would be updated shortly. After about two months, it was still not updated!
My big issue with NetApp support is that they have TONS of bugs that are in their internal database, but yet arent on NOW. I call up NetApp, they're like "Oh, yeah that's bug xxyy". I ask "Is that on NOW?" and the engineer will say "Oh no, its not been sanitized for the web site yet."
When I've got a bug that's affecting my customers and the quality of service I'm offering, I could care less if its been "sanitized" and internal engineering comments / cuss words / etc has been removed - I want the *info available*, or at least indication that the problem *is* an acknowledged bug and NetApp is working on it, as *soon as possible*.
NetApp, if you're going to keep a list of bugs on your web page, make sure they're up-to-date, otherwise such info is useless.
I've made this request at least twice, and never heard anything of it.
The other "minor annoying" problem I've seen with the Toasters:
nfs> exit Use control-D to exit nfs> ^D Connection closed by foreign host.
Why not just use the code that is in the OS to print "Use control-D to exit" to make the filer go ahead and exit?
Bill
-- Bill Bradford Systems Engineer, Texas.Net http://www.texas.net mrbill@texas.net BeOS Developer #9630 ICQ: 1864511 --------------------------------------------------------------------- Called up the Bureau of Alcohol, Tobacco, and Firearms regional office and asked, "What wine goes best with an M-16?" The guy who answered did his best to be helpful: "That depends. What are you smoking?"