public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luigi Pinna <mailing-gentoo@sailorferris.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] No working "burning" cdrom
Date: Thu, 9 Nov 2006 23:30:59 +0100	[thread overview]
Message-ID: <200611092331.07959.mailing-gentoo@sailorferris.com> (raw)
In-Reply-To: <20061109101645.4caedda9@krikkit.digimed.co.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alle 11:16, giovedì 9 novembre 2006, Neil Bothwick ha scritto:
> On Thu, 9 Nov 2006 15:31:25 +0530, Mrugesh Karnik wrote:
> > > This limit only applies to the root user, so the question becomes
> > > "why is K3b running growisofs as root?".  Is growisofs suid?
> >
> > ls -l $(which growisofs)
> > -rws--x--- 1 root burning 71888 2006-10-19 11:33 /usr/bin/growisofs
> >
> >
> > Apparently, it is. I suppose it is to do with avoiding issues with
> > users being in the proper group for burning the disks.
>
> Does the problem go away if you chmod 750 /usr/bin/growisofs?

It works again!
Question is why emerge/k3b installed/changed permission with suid bit.
It is a bug?
In everycase: thanks a lot at all of you!
Luigi

- -- 
Public key GPG(0x633F86B7) on hkp://keyserver.linux.it/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFU6wrHmkkjmM/hrcRAk8tAKCQ5QnaTzc+NRjMAsh26kHtre4dfgCbBuKw
XTayac918bKdDrSm0bGI++I=
=kJqr
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-11-09 22:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 23:14 [gentoo-user] No working "burning" cdrom Luigi Pinna
2006-11-09  1:04 ` Neil Bothwick
2006-11-09  5:49 ` Mrugesh Karnik
2006-11-09  7:27   ` Luigi Pinna
2006-11-09  8:00     ` Mrugesh Karnik
2006-11-09  9:40       ` Neil Bothwick
2006-11-09 10:01         ` Mrugesh Karnik
2006-11-09 10:16           ` Neil Bothwick
2006-11-09 22:30             ` Luigi Pinna [this message]
2006-11-10  0:39               ` b.n.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200611092331.07959.mailing-gentoo@sailorferris.com \
    --to=mailing-gentoo@sailorferris.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox