[64studio-devel] [SOLVED] HDD: Write permissions for ordinary user [SOLVED]

Jason Schaefer schaefer.jason at gmail.com
Wed Feb 28 03:37:53 UTC 2007


use the user/group id option

> /dev/hda5       /home/Diverses  vfat    defaults,gid=100,uid=1000        0       0

defaults - Use default settings. Equivalent to rw, suid, dev, exec,
auto, nouser, async.
gid= group id, look in /etc/group
uid= user id, look in /etc/passwd

Yes, hacking these files directly is similar to the registry but a lot
nicer and effective:-)

Jason



On 2/27/07, R.Wolff <musicwolf at web.de> wrote:
> Sure Jason, here it is:
>
> # /etc/fstab: static file system information.
> #
> # <file system> <mount point>   <type>  <options>       <dump>  <pass>
> proc            /proc           proc    defaults        0       0
> /dev/hda6       /               ext3    defaults,errors=remount-ro 0       1
> /dev/hda7       /home           ext3    defaults        0       2
> /dev/hda5       /home/Diverses  vfat    defaults        0       0
> /dev/hde5       /home/MIDI      vfat    defaults        0       0
> /dev/hdc5       /home/Projects  vfat    defaults        0       0
> /dev/hdg5       /home/Samples   vfat    defaults        0       0
> /dev/hdc6       none            swap    sw              0       0
> /dev/hdb        /media/cdrom0   udf,iso9660 user,noauto,     0       0
> /dev/hdd        /media/cdrom1   udf,iso9660 user,noauto,     0       0
>
> All this stuff is making me really dizzy. The man pages are not always
> of great help here neither. It all sounds partly contradictory.
>
>
> Jason Schaefer schrieb:
> > I am curious what your fstab says. You want to send it? I haven't
> > followed this thread very carefully but it seems the way to resolve
> > permissions issues would be with /etc/fstab.
>
> You're sure right. And it's a hell to make your way through the registry
> for fixing up stuff manually.
> It's a good thing in my mind that in Linux-land things are kept "simple".
> Only if you've never done any scripting and such things, well, it sure
> looks not less impressive then the Windows registry.
>
> Cheers
> Raphael ;)
>
>
> > The Windows registry is perhaps the most difficult, annoying and
> > error-prone part of Windows. I think most people are very grateful gnu
> > software keeps it [fairly] simple with separate (modular) files
> > throughout /etc. The closest thing I know of to the Windows registry
> > is gnome's gconf. But that is for your gui interface.
> >
> >
> >
> > On 2/27/07, R.Wolff <musicwolf at web.de> wrote:
> >> Thanks to all who tried to help me here. Special thanks go out
> >> to Michael Pacey, as it was his hints which brought me the final results.
> >>
> >> I've added the following lines to /etc/udev/permissions.rules (although
> >> I guess that this is really, really not OK to do so):
> >>
> >> # hd devices
> >> KERNEL=="hda5"          MODE="0777"     GROUP="funkster"
> >> KERNEL=="hdc5"          MODE="0777"     GROUP="funkster"
> >> KERNEL=="hde5"          MODE="0777"     GROUP="funkster"
> >> KERNEL=="hdg5"          MODE="0777"     GROUP="funkster
> >>
> >> Now that has changed the owner of my drives to my username (funkster),
> >> root has become the group of them without apparent write permissions
> >> when logged in as user. Still, I'm able to create dirs/files no problem.
> >>
> >>
> >> Haven't changed the entries in 'fstab', since the drives were already
> >> mounted.
> >>
> >> This whole permission thing and setup routines etc is just so terribly
> >> different from Windows.
> >> It seems that EVERYTHING is handled through scripts and such.
> >> Does something like the Windows registry exist for GNU/Linux? Or is all
> >> handled through those little snippets of code here and there?
> >> I've just so much to learn, so back to the books I guess.
> >> The other problems are getting solved petit a petit.
> >>
> >> Cheers
> >> Raphael ;)
> >>
> >> _______________________________________________
> >> 64studio-devel mailing list
> >> 64studio-devel at 64studio.com
> >> http://lists.64studio.com/mailman/listinfo/64studio-devel
> >>
> >
>
>



More information about the 64studio-devel mailing list