Mailinglist Archive: opensuse (4054 mails)
| < Previous | Next > |
Re: [SLE] What is so special on /dev/hda? was how to make device permissions stick?
- From: Peter Sutter <sutterp@xxxxxxxxxxxx>
- Date: Mon, 23 Jan 2006 09:14:39 +0800
- Message-id: <200601230914.39475.sutterp@xxxxxxxxxxxx>
On Sunday 22 January 2006 18:43, Roger Oberholtzer wrote:
> On Wed, 2006-01-18 at 21:09 +0100, Carlos E. R. wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > The Wednesday 2006-01-18 at 10:04 +0800, Peter Sutter wrote:
> > > To burn the dvd, growisofs needs physical access to the dvd
> > > burner, which is /dev/hda, and the permissions of /dev/hda
> > > change from 666 root:disks to 600 root:disks after a crash.
> >
> > Did you read my email (Monday)?
> >
> > In file /etc/logindevperm:
> > :0 0600 /dev/cdrom:/dev/cdrom1:/dev/cdrom2:/dev/cdrom3
>
> How does logindevperms relate to udev and HAL? I would guess that
> if a device is already present when you log in, logindevperms
> will replace any udev/HAL settings. If the device gets inserted
> while logged in, the udev/HAL settings are used and not
> logindevperms.
>
> Joy. Another piece of the puzzle.
>
After reading all the man pages of resmgr, logindevperm etc. and
setting the permissions at various places
(/etc/permissions, /etc/logindevperm, /etc/resmgr.conf) I am still
not getting the desired result. It works if the login is
interactive on a console or to the graphical user interface (I have
installed this in the meantime), but it seems not to work for
apache web server or processes initiated via cronjobs. I still need
to run SuSEconfig manually after a reboot/crash to gain write
access to /dev/hda (via /etc/permissions) for these to work.
snip...
Peter
> On Wed, 2006-01-18 at 21:09 +0100, Carlos E. R. wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > The Wednesday 2006-01-18 at 10:04 +0800, Peter Sutter wrote:
> > > To burn the dvd, growisofs needs physical access to the dvd
> > > burner, which is /dev/hda, and the permissions of /dev/hda
> > > change from 666 root:disks to 600 root:disks after a crash.
> >
> > Did you read my email (Monday)?
> >
> > In file /etc/logindevperm:
> > :0 0600 /dev/cdrom:/dev/cdrom1:/dev/cdrom2:/dev/cdrom3
>
> How does logindevperms relate to udev and HAL? I would guess that
> if a device is already present when you log in, logindevperms
> will replace any udev/HAL settings. If the device gets inserted
> while logged in, the udev/HAL settings are used and not
> logindevperms.
>
> Joy. Another piece of the puzzle.
>
After reading all the man pages of resmgr, logindevperm etc. and
setting the permissions at various places
(/etc/permissions, /etc/logindevperm, /etc/resmgr.conf) I am still
not getting the desired result. It works if the login is
interactive on a console or to the graphical user interface (I have
installed this in the meantime), but it seems not to work for
apache web server or processes initiated via cronjobs. I still need
to run SuSEconfig manually after a reboot/crash to gain write
access to /dev/hda (via /etc/permissions) for these to work.
snip...
Peter
| < Previous | Next > |