Date: Sun, 23 Jul 2000 11:13:58 -0400 (EDT) From: "James E. Housley" <housley@thehousleys.net> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/20127: Update src/sys/i386/conf/LINT INCLUDE_CONFIG_FILE description Message-ID: <200007231513.LAA07742@baby.int.thehousleys.net>
next in thread | raw e-mail | index | archive | help
>Number: 20127 >Category: kern >Synopsis: Update src/sys/i386/conf/LINT INCLUDE_CONFIG_FILE description >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun Jul 23 08:20:00 PDT 2000 >Closed-Date: >Last-Modified: >Originator: James E. Housley >Release: FreeBSD 4.1-RC i386 >Organization: The Housleys dot Net >Environment: All elf based kernels >Description: The description in the LINT kernel for the INCLUDE_CONFIG_FILE options says to you -aout with strings. The more proper is -elf. BTW neither are documented in strings(1). >How-To-Repeat: >Fix: --- LINT Thu Jul 20 08:05:30 2000 +++ LINT.new Sun Jul 23 11:10:21 2000 @@ -80,7 +80,7 @@ # This allows you to actually store this configuration file into # the kernel binary itself, where it may be later read by saying: -# strings -aout -n 3 /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL +# strings -elf -n 3 /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL # options INCLUDE_CONFIG_FILE # Include this file in kernel >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007231513.LAA07742>