-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 While trying to write a small script that would help Tom Rhodes to extract the list of sysctl names and descriptions from a running kernel, I noticed the following (pardon the long lines):
hw.pci.enable_io_modes: Enable I/O and memory bits in the config register. Some BIOSes do not enable these bits correctly. We'd like to do this all the time, but there are some peripherals that this causes problems with. hw.pci.allow_unsupported_io_range: Allows the PCI Bridge to pass through an unsupported memory range assigned by the BIOS. The description of hw.pci.enable_io_modes uses embedded '\n' characters to keep the length of the description below 80 columns. It works fine. But only for the description text, which doesn't appear in the output of: % sysctl -dna | cut -c 80- | grep -v '^[[:space:]]*$' Strangely, this is the only sysctl that I could spot in the entire tree with '\n' characters in the description. The next sysctl in the output of sysctl -ad is hw.pci.allow_unsupported_io_range as shown above, which doesn't make any effort to keep the text below 80 columns. Is there a reason for wrapping with '\n'? If yes, what would that be? I'm only asking because it would make my life simpler if the sysctl descriptions didn't have embedded newlines, and this is a good opportunity to learn something too :-) - - Giorgos -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+cjBf1g+UGjGGA7YRAic3AJ0SgcgupeQiEqoOiBUWHbqzcMq1igCePFvC 9yg+XSZaqtXCpN3cKyyRjzU= =6IkN -----END PGP SIGNATURE----- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
