summaryrefslogtreecommitdiff
path: root/udevstart.c
diff options
context:
space:
mode:
authorandrew.patterson@hp.com <andrew.patterson@hp.com>2004-10-14 00:47:38 -0700
committerGreg KH <gregkh@suse.de>2005-04-26 21:58:15 -0700
commit1fa26490e0d3b0df595fc7d327be46e4d9586bf7 (patch)
tree6d04b5fc3b3ddecd5553555174deead87d0c743c /udevstart.c
parentc008fe93f5252d47f82d7f00e423983bda9ce1e3 (diff)
[PATCH] Problem parsing %s in udev rules
> > > > That explains the spaces. What about stuff trailing %s, if %s does not > > > > contain spaces. I.e, in the above example, model is ST336753LC and the > > > > resulting device file is /dev/scsi_disks/some-proceding-stuff- > > > > ST336753LC. > > > > > > I expect the model value has trailing spaces. > > > > > > You may look with: > > > udevinfo -a -p /block/sdX > > > > Yes it does, and it seems for most SCSI devices, vendor and model will > > have trailing spaces. > > It all depends on the vendor and model :) > > > I have included a patch to udev-036 to deal with > > this issue. It trims off trailing whitespace for all sysfs attributes. > > It might be better to trim off leading whitespace as well. > > We already trim it off when matching, but we also allow matching if you > do put the spaces in there. This patch breaks that, right? Correct, I have a new patch that trims after the comparison, so it should work in both cases.
Diffstat (limited to 'udevstart.c')
0 files changed, 0 insertions, 0 deletions