Bug 200244
Summary: | udev reports 'parse_file: line too long '.../60-libsane.rules : 772' | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tom London <selinux> |
Component: | udev | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | alan, gc1111, gerry, horsley1953, kay.sievers, maxx, michal, nphilipp, olen.e.boydstun |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-08-10 12:14:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 150224 |
Description
Tom London
2006-07-26 14:30:05 UTC
Harald, could udev maybe just ignore too long _comment_ lines like the one it complains about in this case -- it's a large number of scanner models covered by one vendor/product code? While I could just take the rules and cut off lines that are too long (how long may they be anyway), I think in this case allowing such long comments (udev won't be doing anything with them, will it?) would be beneficial. Udev rule lines can be 512 chars long. Sounds like a _very_ long comment. :) It is ;-). Still, it should be easy to read the line into that buffer, check the buffer if it's a comment and only complain if it isn't. can the comment be splitted in multiple lines? *** Bug 200324 has been marked as a duplicate of this bug. *** *** Bug 201845 has been marked as a duplicate of this bug. *** *** Bug 201985 has been marked as a duplicate of this bug. *** Still present in FC6 t2 *** Bug 202148 has been marked as a duplicate of this bug. *** *** Bug 202175 has been marked as a duplicate of this bug. *** *** Bug 202937 has been marked as a duplicate of this bug. *** |