From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] diff to get a /dev/config file
Date: Fri, 14 Jun 2002 11:46:10 +0200 [thread overview]
Message-ID: <68ac7861c2bdc06ed75c9de0e5eef755@plan9.escet.urjc.es> (raw)
For those like me who just don't remember what was in the config file
used to build the kernel, this adds /dev/config (#c/config).
/dev/config holds a copy of the config file used to build the kernel.
If you are interested, instructions follow.
At /sys/src/9/port/portmkfile, replace the $CONF.c rule with this one:
$CONF.c: ../port/mkdevc $CONF
rc ../port/mkdevc $CONF > $CONF.c
{echo 'uchar configfile[]={'
xd -1x $CONF |
sed -e 's/^[0-9a-f]+ //' -e 's/ ([0-9a-f][0-9a-f])/0x\1,/g'
echo 0,
echo '};'} >> $CONF.c
Then apply this change:
diff devcons.c /sys/src/9/port/devcons.c
500a501
> Qconfig,
530a532
> "config", {Qconfig}, 0, 0444,
653a656
> extern char configfile[];
758c761,762
<
---
> case Qconfig:
> return readstr((ulong)offset, buf, n, configfile);
If you applied it, you may also like to apply this to /sys/man/3/cons:
diff cons /sys/man/3/cons
28a29
> .B /dev/config
146a148,151
> .PP
> The
> .B config
> file contains a copy of the kernel configuration file used to build the kernel.
enjoy
reply other threads:[~2002-06-14 9:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68ac7861c2bdc06ed75c9de0e5eef755@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).