Date: Wed, 17 Aug 2016 11:41:02 +0200 From: Tijl Coosemans <tijl@FreeBSD.org> To: Manish Jain <bourne.identity@hotmail.com> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Unable to run k3b Message-ID: <20160817114102.74681d4e@kalimero.tijl.coosemans.org> In-Reply-To: <VI1PR02MB0974F43342E006C862D4D98EC2140@VI1PR02MB0974.eurprd02.prod.outlook.com> References: <alpine.BSF.2.20.1608170942540.1388@bourne.1dent1ty> <VI1PR02MB0974F43342E006C862D4D98EC2140@VI1PR02MB0974.eurprd02.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 Aug 2016 04:38:37 +0000 Manish Jain <bourne.identity@hotmail.com> wrote: > I managed to get k3b working by restarting devfs after adding the > following to devfs.conf : > > own /dev/pass0 root:operator > perm /dev/pass0 0660 This is probably your hard disk so you shouldn't need this. You can check by running 'camcontrol devlist'. > own /dev/pass1 root:operator > perm /dev/pass1 0660 > > own /dev/xpt0 root:operator > perm /dev/xpt0 0660 These are probably fine, but you may want to use a different group than operator. When you add users to group operator you make them rather powerful. They have full read access to every disk (via /dev/ada*) for instance. It is better to create a separate group. > own /dev/pci root:operator > perm /dev/pci 0664 This one is probably not needed either. To burn a cd you may need write access to /dev/cd0: own /dev/cd0 root:operator perm /dev/cd0 0660
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160817114102.74681d4e>