I'm sorry, I didn't catch the "front-end" part of this whole thing.

"Of course, you're right!"  Ignore me if I do that again [TM].

On Fri, 9 Mar 2001, Frederick Bruckman wrote:

# Date: Fri, 9 Mar 2001 18:49:01 -0600 (CST)
# From: Frederick Bruckman <fb@enteract.com>
# To: Greywolf <greywolf@starwolf.com>
# Cc: Jared D. McNeill <jmcneill@invisible.yi.org>,
#      Matthias Drochner <M.Drochner@fz-juelich.de>, tech-pkg@netbsd.org
# Subject: Re: glib/gtk update?
#
# On Fri, 9 Mar 2001, Greywolf wrote:
#
# > On Fri, 9 Mar 2001, Jared D. McNeill wrote:
# >
# > # > f) Tell the user to change the permissions on the raw cdrom device
# > # > nodes. (Assuming that that works, it's no more than you have to do to
# > # > get a ripper to run as non-root.)
# > #
# > # This is definitely the best idea yet -- I seem to remember CD player
# > # applications telling me to change the mode on the CDROM device as well.
# > # What about the other burning packages (sysutils/gcombust for example)?
# > # We'll definitely have to show a message for them as well.
# >
# > The thing about running rippers non-root is that root can mlock() entire
# > memory regions (at least cdrecord complains that mlock() fails).
# > Also, if you run set-uid root, you can renice(-20) the process.
#
# The way I read it, that limitation only applies to powerpc's and
# sparc's (and sun3 and vax).
#
# Besides, isn't gcombust a front-end for cdrecord? If so, wouldn't it
# make more sense to make cdrecord suid root?
#
#
# Frederick
#
#


				--*greywolf;
--
*BSD: The choice of hundreds worldwide.