From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and irda-usb trouble
Date: Wed, 22 Dec 2004 01:23:59 +0000 [thread overview]
Message-ID: <1103678639.5845.52.camel@localhost.localdomain> (raw)
In-Reply-To: <AC07842E-5395-11D9-8CA9-000D932A03A8@beefstew.net>
On Tue, 2004-12-21 at 20:12 -0500, Chris Horn wrote:
> On Tuesday 21 December 2004 20:01, Greg KH wrote:
> > On Tue, Dec 21, 2004 at 07:54:35PM -0500, Chris Horn wrote:
> > >
> > > Is there anything I can do to get udev (or whatever is responsible) from
> > > deleting the nodes I put in by hand? Is there a "don't delete list
> > > somewhere?"
> >
> > I don't understand, why do you want to keep device nodes that are never
> > used?
> >
> > Anyway, that's a distro specific issue, I suggest asking the proper
> > distro mailing list for how to do that.
> >
> > Hope this helps,
> >
> > greg k-h
>
> I'm sorry: one more message. I mis-typed what I want - and I see from your
> message that I need to clarify my problem. I meant:
>
> "Is there anything I can do to get udev (or whatever is responsible) to NOT
> delete nodes I've added by hand?"
>
> The problem is that when I go to sync my Palm Pilot with jpilot, udev (or some
> other software) has often deleted the /dev/irda0 node I created for jpilot to
> talk through. This means that almost every time I want to sync my Palm I
> have to create /dev/irda0 by hand because something has deleted it. I want
> to stop whatever is automatically deleting the nodes I've added by hand (in
> this case /dev/irda0). It's really annoying!
Does it really get deleted without a reboot? If your system use udev,
than there is a high chance that the /dev directory is on tmpfs which
will not survive a reboot.
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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
next prev parent reply other threads:[~2004-12-22 1:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 21:17 udev and irda-usb trouble Chris Horn
2004-12-21 23:50 ` Kay Sievers
2004-12-22 0:05 ` Chris Horn
2004-12-22 0:26 ` Greg KH
2004-12-22 0:43 ` Chris Horn
2004-12-22 0:52 ` Greg KH
2004-12-22 0:54 ` Chris Horn
2004-12-22 1:01 ` Greg KH
2004-12-22 1:12 ` Chris Horn
2004-12-22 1:23 ` Greg KH
2004-12-22 1:23 ` Kay Sievers [this message]
2004-12-22 1:35 ` Chris Horn
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=1103678639.5845.52.camel@localhost.localdomain \
--to=kay.sievers@vrfy.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).