Bug 29534
| Summary: | syscons(4), sc(4) reference non-existant file for color values. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Documentation | Reporter: | Gary W. Swearingen <swear> | ||||
| Component: | Books & Articles | Assignee: | ru <ru> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
On Tue, Aug 07, 2001 at 10:57:22PM -0700, Gary W. Swearingen wrote: > > syscons(4) and sc(4) references non-existant "/usr/include/machine/pc/display.h" > file for users to get color values from (for setting driver options > in kernel configuration). > The actual problem is the missing /usr/include/machine/pc/ in SHARED=copies case. I will try to fix this later. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age Responsible Changed From-To: freebsd-doc->ru Ruslan wanted to fix the lack of /usr/include/machine/pc State Changed From-To: open->closed There's now /usr/include/machine/pc in 4.6-STABLE and 5.0-CURRENT. |
syscons(4) and sc(4) references non-existant "/usr/include/machine/pc/display.h" file for users to get color values from (for setting driver options in kernel configuration). Tag-along: The man pages are identical and probably waste storage. ================ Fix: Apply this PR/patch to the source file. I notice that the two man pages are hard links of each other. I don't know how handle the patching, but this should be close. patch -d "some uncompressed man/man4 dir" < this-PR As for the tag-along (see above), I don't know how to "link" man pages together in the compressed form. ("gnudoit" unsuccessfully attempts to do it with ".so man1/gnuserv.1" and I failed with ".so man4/sc.4.gz".) *** /tmp/old-sc.4 Tue Aug 7 21:52:59 2001 How-To-Repeat: <code/input/activities to reproduce the problem (multiple lines)> ================