Fix up pkg-message for sysutils/k3b

The message was no longer entirely correct for currently-supported
FreeBSD systems.

PR:		240273
Submitted by:	Marko Cupac
This commit is contained in:
Adriaan de Groot 2020-01-05 16:57:58 +00:00
parent 8ff2e45e42
commit fabc051d49
Notes: svn2git 2021-03-31 03:12:20 +00:00
svn path=/head/; revision=522163

View file

@ -6,21 +6,14 @@
(http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html)
2. k3b has to be started from a root console, which is not recommended.
Alternatively, do ALL of the following:
a. Set the suid flag on cdrecord and cdrdao. The 'Notes' chapter of
'man cdrecord' discusses this.
b. Set the vfs.usermount sysctl variable to 1.
# sysctl vfs.usermount=1
Add this line to /etc/sysctl.conf to make it permanent:
vfs.usermount=1
Note that this has negative security implications
c. Every user must have read and write access to /dev/cdX:
a. Every user must have read and write access to /dev/cdX:
- add to your /etc/devfs.rules under '[system=10]':
add path 'cd*' mode 666
- or if you prefer allow access for a group XXX only add instead:
add path 'cd*' mode 660 group XXX
- to enable it, add to your /etc/rc.conf
# sysrc devfs_system_ruleset="system"
d. Every user who should be able to use k3b must have read and write access
b. Every user who should be able to use k3b must have read and write access
to all pass through devices connected with CD and DVD drives and to the
/dev/xpt0 device. Run 'camcontrol devlist' to identify those devices (seek
string 'passX' at the end of each line). Note, that this is a security
@ -42,6 +35,9 @@
a. Either use the (default) HAL backend, and enable HAL in /etc/rc.conf via
# sysrc hald_enable="YES"
b. *or* use the (experimental) BSDISKS backend.
5. Last but not the least, you need to set cdrecord parameters in K3b's
"Settings --> Configure k3b... --> Programs --> User Parameters" to
match your device as seen by `cdrecord -scanbus' (e.g. dev=3,0,0)
EOM
}
]