From: cinap_lenrek@gmx.de
To: 9front@googlegroups.com
Subject: Re: Fwd: cpu0: 1995MHz GenuineIntel Xeon5000-series (cpuid: AX 0x06FB DX 0xBFEBFBFF)
Date: Wed, 2 May 2012 06:22:50 +0200 [thread overview]
Message-ID: <301749fa5f0bb550c32c5c6b79d8d8e7@rei2.9hal> (raw)
In-Reply-To: <b8bf7a03465be8e40761f1a185f96715@sp.nv>
instead of using kmesg, wich can roll over and not contain
a "cpu0" line maybe use /dev/cputype wich will always work.
maybe we should be more carefull with kmesg in general as
it might contain stuff entered on the console wich is
sensitive.
maybe try to extract everything between:
^Plan 9 and ^init: starting /bin/rc
using some awk magic?
--
cinap
next prev parent reply other threads:[~2012-05-02 4:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 0:31 sl
2012-05-02 4:22 ` cinap_lenrek [this message]
2012-05-02 4:31 ` cinap_lenrek
2012-05-02 4:45 ` cinap_lenrek
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=301749fa5f0bb550c32c5c6b79d8d8e7@rei2.9hal \
--to=cinap_lenrek@gmx.de \
--cc=9front@googlegroups.com \
/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).