linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert McMeekin <rrm3@rrm3.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: bad /dev/tty permission in udev.permissions.debian
Date: Mon, 01 Mar 2004 09:34:41 +0000	[thread overview]
Message-ID: <20040301093440.GB26809@rrm3.org> (raw)
In-Reply-To: <87wu65vpd2.fsf@thorr.asgardr.info>

 * Marco d'Itri <md@Linux.IT> [2004/02/29 17:52]:

> On Feb 29, Marco d'Itri <md@Linux.IT> wrote:
> 
>  > >> The copy in the debian package is correct, I suggest again that
>  > >> this file should be removed from the udev tree.
>  > >And the reason the Debian package maintainer does not want to
>  > >share with the rest of the world is?
>  >That the file is not really debian-specific.
> s/not //

That file has been a great help to me getting udev working on my CRUX
box (just got it managing /dev properly today).  I, for one, would
surely appreciate your improvements being sent upstream.  :-)

-- 
Robert McMeekin <rrm3@rrm3.org>


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2004-03-01  9:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29 16:10 bad /dev/tty permission in udev.permissions.debian Daniel 'NebuchadnezzaR' Dehennin
2004-02-29 16:13 ` Marco d'Itri
2004-02-29 16:19 ` Greg KH
2004-02-29 16:45 ` Marco d'Itri
2004-02-29 16:52 ` Marco d'Itri
2004-03-01  9:34 ` Robert McMeekin [this message]
2004-03-01 16:53 ` MALET JL

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=20040301093440.GB26809@rrm3.org \
    --to=rrm3@rrm3.org \
    --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).