On Fri, Sep 07, 2007 at 09:42:11PM -0500, Karl O. Pinc wrote: > > On 09/07/2007 11:41:02 AM, Osamu Aoki wrote: >> On Tue, Sep 04, 2007 at 10:13:40AM -0500, Karl O. Pinc wrote: >> > >> > On 09/04/2007 07:59:47 AM, Osamu Aoki wrote: > >> > I didn't want to expand this section to re-create the >> > definitive list, but I also think it could be useful to >> > list the 'scanner' group and the 'plugdev' group. (Because >> > those are the ones I've struggled with in the past. :) >> >> But gnome and xfce do not use plugdev (pmount). > > I am unclear on what's used when. (I recently switched from > gnome to kde, so am now using kde.) All I can say is that > when I plugged in my usb camera (which requires a special > wire protocol, it does not mount as a filesystem) it came > up with plugdev as the group allowed to read and write it. > (Kde also did some odd things popping up a dialog box. > I was unable to figure out how to get it to launch, for > example, gtkam. I poked it with a stick for a while and > gave up.) I'm not sure what kde is really doing that I want > and don't know I'll stick with it.
I am unclear too :-) I use Gnome. KDE seems to use pmount as underlayer for mounting devices from desktop while gtk and xfce seems to have their own tools. [EMAIL PROTECTED]:~$ man -k mount (and manual cherry picks) drivemount_applet (1) - Drive Mount Applet for the GNOME panel. exo-mount (1) - mount volumes based on their HAL UDIs or their device files exo-unmount (1) - umount volumes based on their HAL UDIs or their device files gnome-eject (1) - Mount drives and volumes using HAL and read settings from the GNOME desktop configuration system gconf. gnome-mount (1) - Mount drives and volumes using HAL and read settings from the GNOME desktop configuration system gconf. gnome-umount (1) - Mount drives and volumes using HAL and read settings from the GNOME desktop configuration system gconf. gnome-volume-manager (1) - GNOME daemon to auto-mount and manage media devices pmount (1) - mount arbitrary hotpluggable devices as normal user pmount-hal (1) - HAL-aware wrapper around pmount pumount (1) - umount arbitrary hotpluggable devices as normal user KDE has dependency to pmount as I see. >> >> But if this is for devices, floppy etc may serve better as example. >> > >> > I'm not sure what you mean, but that's ok. Second thought. CDROM these days. >> > I chose the audio group because you already had text for >> > the adm group, which grants read access, and I wanted >> > something that would grant write access (and have to do with >> > devices rather than files.) >> >> What do you think my rewrite? >> >> http://wiki.debian.org/DRBasics#head-8c8218c777b29b3179dd99503f0a019f55ebca0a > > As written: > When some filesystem access is only available from the super user (root), > this is a good indication that access permission of some file (including > device) is set to deny access by the user account used. This situation may > be removed by adding the pertinent user to the pertinent group and setting > proper group access permission to the file. > > Revised: > When some filesystem access is only available to the super user (root), > this is a good indication that access permission of the file (or device) is > set to deny access to the user account. This situation may be removed by > adding the pertinent user to the pertinent group and setting proper group > access permission to the file. > > (It's still not so good. E.g. The first sentence seems to say > only "if only root can use it then regular user's can't." which > is a tautology.) > > I think this part needs to go in "The root account" section > and taken out of the group section. I say this because that's > where the reader needs to perk up and remember "hey, this is > what the root account's good for. If I want to do any of these > things I'd better be root". It's easier for the reader if the > whole list is in one place. I think this is true, even though it'd > be nice to remind the reader throughout the document where ever > root permissions are required, because generally the new user > won't know which part of the document has the relevant concept > when, for example, he does not have permission. But he should > be able to remember that root _always_ has permission and so should > be able to rely on the part of the document that explains the > root concept to refer him to the concepts in the other parts > of the document. > > Re-revised (for after the bullet points): > Some files (and most devices -- hardware devices are just another > kind of file) can not be used by non-root users without the > root user's permission. As explained below, permission is granted via > membership to the relevant <link to groups section>group</link>. Very good points. But injecting group thing too much in early root section may skew the flow of text. I have made rewrite of the many related sections. I hope this is better. http://wiki.debian.org/DRBasics (If you have some more thought, please edit this wiki. Your help s most appreciated. FYI: We need to wait 1.6 release of moinmoin to do synchronization. Until then, I am manually doing copy-paste between my machine and debian site) I am doing many rewrite etc now. I have script to convert these pages to XML. Once stabilize, I will make XML as the upstream and publish it via DDP if it is accepted by others. By the way, I am aware of interesting page: http://wiki.debian.org/DebianDesktopHowTo Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
