From: Uriel <uriel99@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF
Date: Thu, 12 Apr 2007 17:14:08 +0200 [thread overview]
Message-ID: <5d375e920704120814x7df5749sd7b8524972878a85@mail.gmail.com> (raw)
In-Reply-To: <5247962e2f1f11c9b374c57d9a9a71db@cat-v.org>
> # uncomment the following for booting other systems
> #ip/dhcpd
> #ip/tftpd
Shouldn't optional stuff like this go in cpurc.local anyway?
> + #if(! netstat -n | grep -v 17008 | grep -s il.*Listen)
> + # aux/listen -q il
[...]
> + # cpu specific startup
> + #if(test -e /cfg/$sysname/cpustart)
> + # . /cfg/$sysname/cpustart
> +
> + #echo `{date} $sysname >>/sys/log/boot
Why is all this commented out?
This changes seem to intend to allow local installations to override
the default cpurc setup without having to edit it (and therefore get
out of sync with sources and need to merge future changes by hand and
so on), so I see little reason to leave 'alternative' sections
commented out when the local and $sysname specific scripts can take
care of that.
And thanks dho for writing the summaries! Just one small complaint,
could you fix the first line of the comments (specially because it is
used by convention as subject for the emails)?
Best wishes
uriel
next parent reply other threads:[~2007-04-12 15:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5247962e2f1f11c9b374c57d9a9a71db@cat-v.org>
2007-04-12 15:14 ` Uriel [this message]
2007-04-12 15:32 ` Devon H. O'Dell
2007-04-12 15:48 ` erik quanstrom
2007-04-12 16:03 ` Devon H. O'Dell
2007-04-12 16:05 ` Russ Cox
2007-04-12 15:56 ` Uriel
2007-04-12 16:08 ` Devon H. O'Dell
2007-04-12 17:42 ` [9fans] Re: [sources] 20070410: % cat geoff
2007-04-12 18:00 ` Anthony Sorace
2007-04-12 18:16 ` Russ Cox
2007-04-12 18:57 ` Anthony Sorace
2007-04-13 4:04 ` Lucio De Re
2007-04-13 4:58 ` geoff
2007-04-12 18:25 ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF ron minnich
2007-04-12 18:38 ` [9fans] Re: [sources] 20070410: % cat geoff
2007-04-12 18:43 ` Devon H. O'Dell
2007-04-12 18:40 ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF erik quanstrom
2007-04-12 18:50 ` Francisco J Ballesteros
2007-04-12 18:41 ` Russ Cox
2007-04-13 4:18 ` [9fans] Re: [sources] 20070410: % cat Lucio De Re
2007-04-13 4:59 ` geoff
2007-04-12 18:48 ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF andrey mirtchovski
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=5d375e920704120814x7df5749sd7b8524972878a85@mail.gmail.com \
--to=uriel99@gmail.com \
--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).