linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Possible udev bug and some questions
Date: Thu, 25 Dec 2003 10:06:41 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-107234693527644@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107230596809166@msgid-missing>

On Thu, Dec 25, 2003 at 12:25:22AM +0200, Martin Schlemmer wrote:
> 3) After looking at ide-devfs.sh, I converted it to create the 'compat'
> symlinks (/dev/{cdroms,discs}/* stuff) if anybody is interested (as
> ide-devfs-compat.sh).
[...]
> 4) Is there any reason why only one 'method' (meaning only one of the
> callouts I may have for ide devices - I may want to use both the
> ide-devfs.sh and ide-devfs-compat.sh to have multiple symlinks for on
> device ...) is done for each device and/or hotplug event (beside lack
> of time to implement) ?  Same for why only 'type' of 'method' is done
> for each (if a CALLOUT is done, the rest is skipped) ?

Why not merge the two callout scripts in one, so that it
returns the two symlinks at once?
We support multiple symlinks separated by spaces.

...,NAME="%k", SYMLINK="%2c %3c"


> 5) I use a devfs-less setup with udev, 2.6.0 kernel with most of the
> sysfs patches from Greg, if not all, and a pre 2.3.3 glibc.  Also
> have devpts compiled in, and mounted to /dev/pts.  I now have the
> following 'w' output:
> 
> --
>  $ w
>  00:22:22 up  1:15, 13 users,  load average: 0.98, 0.28, 0.14
> USER     TTY        LOGIN@   IDLE   JCPU   PCPU WHAT
> azarah   tty4      23:07    1:14m  1.19s  0.00s /bin/sh
> /usr/X11R6/bin/startx
> azarah   ttyp0     23:08     ?     0.00s  0.00s -bash
> azarah   ttyp1     23:08     ?     0.00s  0.00s -bash

No problem here, my glibc package is 2.3.2.

kay@pim:~/src/udev.kay$ w
10:55:19 up 4 days, 22:53,  4 users,  load average: 0.00, 0.02, 0.05
USER     TTY      FROM              LOGIN@   IDLE   JCPU   PCPU WHAT
kay      tty1     -                Sat12    4days 38.78s  0.00s /bin/sh /usr/bin/X11/startx
kay      pts/0    :0.0             10:12    0.00s  0.07s  0.00s w
kay      pts/1    :0.0             10:43   24.00s  0.23s  0.22s ssh puk
kay      pts/2    :0.0             10:20   28:38   0.04s  0.04s bash


thanks,
Kay


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&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:[~2003-12-25 10:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24 22:25 Possible udev bug and some questions Martin Schlemmer
2003-12-25  0:19 ` Greg KH
2003-12-25  0:30 ` Greg KH
2003-12-25 10:06 ` Kay Sievers [this message]
2003-12-25 18:59 ` Martin Schlemmer
2003-12-25 19:32 ` Kay Sievers
2003-12-25 20:00 ` Kay Sievers
2003-12-25 21:04 ` Kay Sievers
2003-12-25 21:26 ` Kay Sievers
2003-12-25 22:58 ` 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=marc-linux-hotplug-107234693527644@msgid-missing \
    --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).