Date: Thu, 26 Aug 2004 13:14:05 -0400 From: Tim Kellers <kellers@njit.edu> To: Michael Nottebrock <michaelnottebrock@gmx.net> Cc: freebsd-ports@freebsd.org Subject: Re: K3B issues under Beta1 Message-ID: <200408261314.05823.kellers@njit.edu> In-Reply-To: <200408261844.34830.michaelnottebrock@gmx.net> References: <412D3943.8020002@makeworld.com> <200408252252.54325.kellers@njit.edu> <200408261844.34830.michaelnottebrock@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 26 August 2004 12:44 pm, Michael Nottebrock wrote: > On Thursday 26 August 2004 04:52, Tim Kellers wrote: > > I'm the only console user on my multi-user system and to keep k3b working > > after every buildworld/buildkernel/installkernel triple flip (and there > > has been one almost every day since August 17th), I've been including a > > dev.sh script in /usr/local/etc/rc.d: > > > > chmod 777 /dev/xpt* && chmod 777 /dev/pass* && chmod 777 /dev/cd0 && echo > > "Burn Away!" > > > > in order to keep k3b working cross-build. I know this has been discussed > > before in slightly other iterations, but could someone refresh my memory > > and point me to the docs that allow k3b to run on FreeBSD 5.x without > > changing the permissions of the affected /dev/* entries globally? > > You can add your user to the operator group, that way you will only need to > set mode 660 on a few devices like cd*. To keep permissions across reboots > on 5.x, you should use /etc/devfs.conf. Thank you Michael, that was very helpful.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408261314.05823.kellers>