From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: Moving Ubuntu to upstream udev rules (Part 2)
Date: Mon, 22 Dec 2008 16:15:01 +0000 [thread overview]
Message-ID: <20081222161501.GA31319@bongo.bofh.it> (raw)
In-Reply-To: <1229955629.6944.63.camel@quest>
On Dec 22, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > - KERNEL="tun", NAME="net/%k", MODE="0666", OPTIONS+="ignore_remove"
> > + KERNEL="tun", NAME="net/%k"
> > The mode seems rather permissive? Do you really allow any user to
> > make tunnels by default? (Ours is 0600!)
> Hmm, I don't know. I see Ubuntu users complaining on the net, who use
> virtualization not running as root. But if it's unsafe we should
> change that.
It's safe with modern kernels, it should be 666 to not anger users.
> > We have the nvram group, no idea why, we just do ;)
> Hmm, if there is a good reason. Maybe just drop "nvram", and wait if
> anybody complains?
As I explained, it's a Debianism.
> Putting gigabyte-big USB hard disks in the "floppy" group? Also some
Yes, because "floopy" actually means "removable storage devices".
> ATA/SCSI storage controller are marked as removable. I don't think we
I like to call these "buggy".
> If we can not agree on a default, we can do an option, but we do
> nobody a favor who works on an upstream project and who needs to find
> the differences again. So, I'm all for finding a common solution, For
> me it would not be a problem to use "dialout" if that is what we want.
> Harald?
In Debian uucp and dialout are totally unrelated groups: the first one
is used by the Taylor UUCP package for its own stuff, the second one
means "member users can initiate a dialout connection using SLIP,
PPP or a terminal program". I think some distributions overloaded the
uucp group with both meanings. Debian cannot merge them.
--
ciao,
Marco
next prev parent reply other threads:[~2008-12-22 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 14:20 Moving Ubuntu to upstream udev rules (Part 2) Scott James Remnant
2008-12-22 15:30 ` Kay Sievers
2008-12-22 15:42 ` Bernhard Walle
2008-12-22 15:55 ` Kay Sievers
2008-12-22 16:02 ` Scott James Remnant
2008-12-22 16:12 ` Kay Sievers
2008-12-22 16:15 ` Marco d'Itri [this message]
2008-12-22 16:30 ` Kay Sievers
2008-12-22 16:40 ` Marco d'Itri
2008-12-22 16:52 ` Kay Sievers
2008-12-22 19:57 ` Piter PUNK
2008-12-22 20:25 ` Marco d'Itri
2008-12-24 15:28 ` Kay Sievers
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=20081222161501.GA31319@bongo.bofh.it \
--to=md@linux.it \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).