On Saturday 08 June 2019 04:55:45 am [email protected] wrote: > On Fri, Jun 07, 2019 at 09:44:23PM -0400, Gene Heskett wrote: > > [...] > > > But first you need to know the name of the man page. You can't read > > it if you don't know its true name... > > Not a user of systemd here, but... have you ever tried "man -k > systemd"? > No, didn't know it existed Tomas, but howinhell is all that supposed to help? Must be 3 or 4 screens full. What we'd need to do is to feed all that to grep to see if the problem child device is mentioned.
I think we could, but the resultant cli would be too long. Maybe if we could nuke the comments and only use the filename? But even then it would be over a kilobyte. Even that fails: gene@coyote:/CoCo/pyDriveWire/config$ grep usbS0 `man -k systemd` grep: deb-systemd-helper: No such file or directory (no path to it from the instant `pwd`) grep: (1p): No such file or directory And 2 minutes later its still stuck there. But does quit with a ctl-c. Perhaps the list could be a source for locate? But that would blow up on the comments too. Somewhat past ridiculous, into sublime, but you get my point. I hope. Thank for educating me about the -k. However, the -K option seems as if it may be what is needed. Lets see. No, it doesn't find usbS0. No help there IOW. But it does find ttyS. In at least 10% of the pages. Thats less than usefull. Nice try, it did look promising. It also would take several hours to grep the whole man tree. > Cheers > -- t You too. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
