n run X as root just fine. But when I try to run it as a user, I
get the following errors in /var/log/XFree86.0.log:
(WW) xf86ReadBIOS: Failed to open /dev/mem (Operation not permitted)
Fatal server error:
xf86OpenConsole: Server must be suid root
Here is some info:
XFree86 Version 4.2.1.1
ha
error:
xf86OpenConsole: Server must be suid root
Here is some info:
XFree86 Version 4.2.1.1
hardin:/usr/X11R6/bin# ls -l X*
-rwsr-sr-x1 root root 7476 Aug 29 11:30 X
-rwsr-sr-x1 root root 1584152 Aug 29 11:30 XFree86
-rwxr-xr-x1 root root27494 Aug 29 11:26
When cdrecord is run suid root it will work. However, it won't have
access to the function setpriority() listed below. If you want to do
away with those errors, you will have to run cdrecord as root (ex: sudo
cdrecord)
- Ryan
On Tue, Jun 03, 2003 at 01:39:40PM -0400, Chris Metzler
ion denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
>From searching the web/newsgroups, I can see that this is fairly
common -- cdrecord needs to be run as root, or as suid root. However,
there are a few important differ
On 19 Sep 2001, John Hasler wrote:
> Anthony writes:
> > I have no idea how all this happened, nor do I understand why /dev/ttyS0
> > had originally got incorrect permissions while /dev/ttyS1, etc, were
> > correct.
>
> Pppd once had a bug that caused it to fail to restore the permissions on
> the
Anthony writes:
> I have no idea how all this happened, nor do I understand why /dev/ttyS0
> had originally got incorrect permissions while /dev/ttyS1, etc, were
> correct.
Pppd once had a bug that caused it to fail to restore the permissions on
the serial port. I thought it was fixed long ago, t
On 19 Sep 2001, Michael Heldebrant wrote:
> On Wed, 2001-09-19 at 08:35, Anthony Campbell wrote:
> > On 19 Sep 2001, Carel Fellinger wrote:
> > > On Wed, Sep 19, 2001 at 07:51:11AM +0100, Anthony Campbell wrote:
> > > > On 18 Sep 2001, Michael Heldebrant wrote:
> > > > > On Tue, 2001-09-18 at 10:59
On Wed, Sep 19, 2001 at 01:57:06PM +0100, Anthony Campbell wrote:
> On 19 Sep 2001, Carel Fellinger wrote:
...
> > group ownership:
> >
> > $ ls -l /dev/ttyS0
> > crw-rw1 root dialout4, 64 Jul 5 2000 /dev/ttyS0
...
> A good suggestion and in fact I found that the permiss
On Wed, 2001-09-19 at 08:35, Anthony Campbell wrote:
> On 19 Sep 2001, Carel Fellinger wrote:
> > On Wed, Sep 19, 2001 at 07:51:11AM +0100, Anthony Campbell wrote:
> > > On 18 Sep 2001, Michael Heldebrant wrote:
> > > > On Tue, 2001-09-18 at 10:59, Anthony Campbell wrote:
> > > > > I have to have m
On 19 Sep 2001, Carel Fellinger wrote:
> On Wed, Sep 19, 2001 at 07:51:11AM +0100, Anthony Campbell wrote:
> > On 18 Sep 2001, Michael Heldebrant wrote:
> > > On Tue, 2001-09-18 at 10:59, Anthony Campbell wrote:
> > > > I have to have minicom setuid root, even though I have added myself to
> > > >
On 19 Sep 2001, Carel Fellinger wrote:
> On Wed, Sep 19, 2001 at 07:51:11AM +0100, Anthony Campbell wrote:
> > On 18 Sep 2001, Michael Heldebrant wrote:
> > > On Tue, 2001-09-18 at 10:59, Anthony Campbell wrote:
> > > > I have to have minicom setuid root, even though I have added myself to
> > > >
On Wed, Sep 19, 2001 at 07:51:11AM +0100, Anthony Campbell wrote:
> On 18 Sep 2001, Michael Heldebrant wrote:
> > On Tue, 2001-09-18 at 10:59, Anthony Campbell wrote:
> > > I have to have minicom setuid root, even though I have added myself to
> > > the dialout group, which according to the man pag
On 18 Sep 2001, Michael Heldebrant wrote:
> On Tue, 2001-09-18 at 10:59, Anthony Campbell wrote:
> > I have to have minicom setuid root, even though I have added myself to
> > the dialout group, which according to the man page should allow access
> > to serial port devices. Any suggestions for what
On Tue, 2001-09-18 at 10:59, Anthony Campbell wrote:
> I have to have minicom setuid root, even though I have added myself to
> the dialout group, which according to the man page should allow access
> to serial port devices. Any suggestions for what's wrong?
You need to add yourself to the dialout
I have to have minicom setuid root, even though I have added myself to
the dialout group, which according to the man page should allow access
to serial port devices. Any suggestions for what's wrong?
Anthony
--
Anthony Campbell - running Debian GNU/Linux (Windows-free zone).
For electronic books
On 04 Aug 2001, Matthias Fonfara wrote:
> Since I installed Dosemu 1.0.2 it reports suid root is not allowed
> because of insecure experimental code. I should recompile it without
> this code.
>
> But I have no idea what to change.
>
> Bye
> Matthias
> -
I had the s
On Thu, Sep 14, 2000 at 10:18:37PM -0400, Jonathan D. Proulx wrote:
> If this machine is in your home *and* your internet connection is via
> intermittent dial-up with dynamic IP adressing, I say no big deal.
> If you have persistant internet connection (via LAN, xDSL, Cable) your
> risk goes way
your self to the "floppy" group in /etc/group,
then relogin. This will give you, and only you, permission to write to the
floppy device.
As for suid root, for "convenience", well, that's something we never do by
default. We setup perms on devices like this (and programs th
On Thu, 14 Sep 2000, Ethan Benson wrote:
> a better way to go is adding yourself to group floppy, then you can
> read and write /dev/fd0. this is less of a risk then making random
> binaries suid.
>
> sudo as someone else mentioned is also probably safer.
>
> just don't add yourself to grou
On Thu, Sep 14, 2000 at 10:00:55PM -0400, Michael Soulier wrote:
>
> How do you guys feel about SUID root? For example, I'm here using
> supermount, finding it mildly annoying that I have to login as root to
> format a floppy. Is it against the "Debian way" to SU
On Thu, Sep 14, 2000 at 10:00:55PM -0400, Michael Soulier wrote:
:
: How do you guys feel about SUID root? For example, I'm here using
:supermount, finding it mildly annoying that I have to login as root to
:format a floppy. Is it against the "Debian way" to SUID root on
How do you guys feel about SUID root? For example, I'm here using
supermount, finding it mildly annoying that I have to login as root to
format a floppy. Is it against the "Debian way" to SUID root on supermount
and mformat for convenience? Does that cause a majo
On Wed, 22 Mar 2000, Pollywog wrote:
> Is it just me or does traceroute need to be suid root?
Traceroute needs to be setuid so it can write IP packets directly rather
than using the socket interface. Without that ability, it could not set
the time-to-live on the packet and thus wouldn't work.
Is it just me or does traceroute need to be suid root?
I was unable to use it as an ordinary user until I set the suid bit.
thanks
--
Andrew
>
> Sorry to bug the list with yet another programming problem but ...
>
> What permissions on the file do I need to change to allow an ordinary user
> to run a setuid-root programme ? The programme below compiles and runs if
> I compile & run as root but does not work if run by a user regardles
Sorry to bug the list with yet another programming problem but ...
What permissions on the file do I need to change to allow an ordinary user
to run a setuid-root programme ? The programme below compiles and runs if
I compile & run as root but does not work if run by a user regardless of
who comp
26 matches
Mail list logo
