|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
k3b on OpenBSD
That worked perfectly. I can now mount both; my flashdrive and cd/dvd drive with a standard user account. Very intuitive write-up.
A couple of things however: I had to set up permissions for sd1 and sd2 since OpenBSD assigns either of these two disklabels to the flashdrive. I am not sure how it chooses one or the other Although the cd/dvd drive mounts perfectly fine now under the standard user account, k3b which is an authoring tool that I like, delivers the following message. Quote:
Thanks again. |
|
||||
To my knowledge you won't be able to use K3b with HAL, since HAL is a Linuxism which is not available.
See http://www.openbsd.org/faq/faq13.html#burnCD for guidance on optical drive writing. Last edited by jggimi; 25th March 2016 at 02:55 PM. Reason: clarity |
|
|||
Quote:
Hmm, I wonder why it's asking for it since it is an OpenBSD port? I'll see if I can find the solution in that link. I'll report back. thanks... |
|
|||
This thread has been split from its parent:
http://daemonforums.org/showthread.php?p=58451 ...as that thread questioned access due to permission issues. Discussion here has shifted to multimedia/k3b. We ask that members stay on the subject set up by the initial message in a thread. We welcome changes in subject, but please do so in a new thread. Many of our members do not have English as their native language. Technical discussion can be difficult enough to follow without discussion simply meandering. Please be cognizant of others at different technical comprehensions by staying on the original subject. Last edited by ocicat; 26th March 2016 at 03:57 AM. Reason: grammar |
|
|||
If k3b doesn't work, maybe try ./multimedia/k3b-kde4.
|
|
|||
Quote:
|
|
|||
Wrong version installed.
I initially installed 'k3b-kde4' (kde windows manager version), which is version 2.0.3a. I needed to install the 'k3b' package, which is version 1.0.4. I did not realize this until I looked at both packages in openports.se
k3b now sees the cd/dvd drive. Message being displayed is; 'no write access to /dev/rcd0c/. I think I can resolve this by simply adding the _user created when k3b was installed to the 'operator' group, since I already authorized the group to have rw access to /dev/rcd0c/. However, I can't find the _user account in /etc/groups/. Last edited by jjstorm; 26th March 2016 at 07:12 PM. |
|
|||
My device permissions in 5.8 for rcd0* devices
Code:
PooBear$ ls -al rcd0* crw-r----- 1 root operator 15, 0 Nov 12 06:08 rcd0a crw-r----- 1 root operator 15, 2 Nov 12 06:08 rcd0c PooBear$ ls -al cd0* brw-r----- 1 root operator 6, 0 Nov 12 06:08 cd0a brw-r----- 1 root operator 6, 2 Nov 12 06:08 cd0c There is a nice howto on mounting usb drives as a non-root user here. In the thread it describes how to add your user to the operator group and expand group permission on a specific usb port from read only to read/write. You can expand permissions on rcd0c the same way. |
|
|||
Quote:
Is there a command that will list the _user created when a program gets installed? Last edited by jjstorm; 26th March 2016 at 07:14 PM. |
|
|||
Quote:
|
|
||||
Let me try to help clarify.
First, there is no userid created when k3b or k3b-kde4 are installed. New users are created for applications which have daemons, this application does not have one. To add a user, the packing-list in the port would indicate this with a @newuser instruction but one is not included with either /usr/ports/multimedia/k3b/pkg/PLIST or /usr/ports/multimedia/k3b-kde4/pkg/PLIST. Second, burning of media is performed against the raw, character device, not against the block device: /dev/rcd0c rather than /dev/cd0c. This may be your permissions problem. Please note: there is no /dev/cd0 special file (device node) configured on OpenBSD. |
|
|||
To add more information, the backend for dvd burning is growisofs. Since you are using growisofs (part of sysutils/dvd+rw-tools you will need read/write permissions to rcd0c
Quote:
|
|
|||
That was it. I just did the following:
To give the permission: Code:
# chmod g=rw /dev/rcd0c Code:
$ ls -l /dev/rcd0c crw-rw---- 1 root operator 15, 2 Mar 22 15:32 /dev/rcd0c Last edited by jjstorm; 26th March 2016 at 07:18 PM. |
Thread Tools | |
Display Modes | |
|
|