Subject: Re: MySQL Running as Ingres
To: Ty Sarna <email@example.com>
From: Curt Sampson <firstname.lastname@example.org>
Date: 08/07/1998 16:14:46
> Hubert Feyrer wrote:
> > Um, abusing ingres for mysql seems a bit bad. Either use a general
> > "database" user (db, whatever), or use a "mysql" login.
Ok; I'd like to set up a general database user. I was using ingres for
this purpose until now.
On Thu, 23 Jul 1998, Ty Sarna wrote:
> I'd have to agree. You can look at AMANDA (misc/amanda, I think) for an
> example of a package that creates a user for itself if it doesn't exist.
The problem with this is that someone may use that userid for
something else before the package goes in; we should have stuff
like this in the passwd file from the beginning to make installations
that use lots of NFS happy.
> Also, MySQL should really be split into client and server packages,
> rather than having one package that may or may not include the server,
Yes. Also, I'm not sure that the databases themselves should go in
/var; it's the sort of thing that can get quite large (which on
many systems /var isn't sized to handle), and they certainly don't
fall into the category of `log, temporary, transient and spool
files.' What about under /usr/pkg/mysql?
Curt Sampson email@example.com Info at http://www.portal.ca/
Internet Portal Services, Inc. Through infinite mist, software reverberates
Vancouver, BC (604) 257-9400 In code possess'd of invisible folly.