Messages in this thread | | | From | Carl Karsten <> | Date | Tue, 20 Dec 2011 17:42:54 -0600 | Subject | Re: [PATCH 1/3] firewire: do not expose globally unique IDs in the kernel log |
| |
On Tue, Dec 20, 2011 at 5:10 PM, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote: > On Dec 20 Carl Karsten wrote: >> grumble. >> >> I use those guids like so: >> >> plug in dv cam, dmesg, cut guid to clipboard, run: >> dvgrab -guid (paste) > > How about: > > #!/bin/sh > guid=$(cat /sys/bus/firewire/devices/$1/guid) > shift > dvgrab -guid $guid "$@" > > To be called as "dvgrab-wrapper fw3 [more dvgrab options]", with fw3 being > the device of your choice, e.g. the one that just scrolled by in syslog. > > Or you run "grep . /sys/bus/firewire/devices/*/guid | sed s/\\/guid:/\\t/" > before dvgrab, and you get a list of GUIDs from which you can copy and > paste.
I can't rely on these scripts being available, and I certainly won't to try and create them on the fly when I need them (which is often as a talk is starting and I am already in a panic trying to figure out why something isn't working... every second counts, and my brain is topped out.)
> >> It also kinda helps me keep track of what devices are misbehaving, but >> this alone isn't very important. >> >> Any chance of making this configurable? > > So far the configuration of the "new" firewire drivers were kept at an > essential minimum, and I am hesitant to add more baroque ones. I would > rather drop this patch now that there was negative feedback, unless there > is going to be positive feedback as well.
+1.
As a peace offering to people that want to x them out before posting:
juser@pc8:~$ sed -r 's/(GUID [0-9A-Fa-f]{8})[0-9A-Fa-f]{8}/\1xxxxxxxx/' /var/log/syslog
snip snip Dec 20 08:30:00 pc8 kernel: [ 1.980149] firewire_core: created device fw0: GUID 00241b00xxxxxxxx, S100
-- Carl K -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |