public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Burton Samograd <kruhft@kruhft.dyndns.org>
To: "gentoo-dev@gentoo.org" <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Problems with links browswer and permissions
Date: Wed, 21 Aug 2002 10:39:03 -0700	[thread overview]
Message-ID: <20020821173902.GC25293@kruhft.dyndns.org> (raw)
In-Reply-To: <20020820000458.GA15131@kruhft.dyndns.org>

I seem to have solved my own problem.  It turns out that the devices
/dev/gpmctl and /dev/gpmdata don't have the correct permissions for
non-privelidged users to access them.  After doing a

chown root.input /dev/gpm*
chmod g+rw /dev/gpmctl
chmod g+r /dev/gpmdata

it all seemed to work.  I also changed devfsd.conf to register those
devices with those permissions as well.  Any security people care to
comment on if that is the correct way i should be doing access control
(using the group and permissions given)?

burton


On Mon, Aug 19, 2002 at 05:04:58PM -0700, Burton Samograd wrote:
> Hi all,
> 
> I'm having some problems with the links web browser.  I'm thinking
> it's a problem with permissions on the frame buffer or mouse since I
> get the following when i try and run it when it's not +s:
> 
> Could not initialize graphics driver fb:
> Cannot open GPM mouse.
> 
> I notice that links likes to grab onto the mouse and not let it go
> while it's running (very annoying since gpm becomes totally useless,
> even when links is running in text mode).  Any ideas on how to fix one
> or both of these problems?  
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev


      reply	other threads:[~2002-08-21 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20  0:04 [gentoo-dev] Problems with links browswer and permissions Burton Samograd
2002-08-21 17:39 ` Burton Samograd [this message]

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=20020821173902.GC25293@kruhft.dyndns.org \
    --to=kruhft@kruhft.dyndns.org \
    --cc=gentoo-dev@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