From: sl@9front.org
To: 9front@googlegroups.com
Subject: Re: rep
Date: Tue, 1 May 2012 13:34:37 +0000 [thread overview]
Message-ID: <cf684b3b775f735290ff55f611203e8d@sp.nv> (raw)
In-Reply-To: <fae04ed534038c33292a407bcf496bad@rei2.9hal>
After cinap's mail and discussing possibilities on IRC,
a revised version, renamed to sysinfo (see below).
> instead of dumping plan9.ini, wich should be the same after
> install anyway. dump the effective kernel parameters as this
> will also catch manual entered bootargs:
>
> cd '#ec'; for(i in *){echo $i '=' `{cat $i}}
This does make more sense, and would capture any changes to
plan9.ini just as effectively.
> if we dump ioalloc, also dump archctl, irqalloc:
>
> cat '#P/archctl'
> cat '#P/irqalloc'
> cat '#P/ioalloc'
Added cat '#P/apm', just in case.
> enumerated devices (optional, because alarm sucks):
>
> alarm 1 cat /dev/usbevent
Leaving this out, for now.
> we should dump the effective vga configuration instead of just
> assuming vesa.
>
> cat '#v/vgactl'
Keeping both, since the valid VESA modes of various video cards
is an open question.
-sl
---
#!/bin/rc
fn logprog{
echo '% '^$"*
$*
echo
}
echo '% cd ''#ec''; for(i in *){echo $i ''='' `{cat $i}}'
cd '#ec'; for(i in *){echo $i '=' `{cat $i}}
echo
logprog cat '#P/archctl'
logprog cat '#P/irqalloc'
logprog cat '#P/ioalloc'
logprog cat '#P/apm'
logprog cat '#c/config'
logprog cat '#c/swap'
logprog cat '#c/sysstat'
logprog cat '#c/kmesg'
logprog pci -v
logprog aux/icanhasmsi
logprog aux/pcmcia
logprog cat '#u/usb/ctl'
logprog cat '#S/sdctl'
for(i in `{ls /dev | grep -e 'sd[A-Z][0-9].*'})
logprog cat $i/ctl
for(i in /net/ether*){
logprog cat $i/addr
logprog cat $i/stats
logprog cat $i/ifstats
}
logprog cat '#v/vgactl'
echo '@{rfork n; aux/realemu; aux/vga -p}'
@{rfork n; aux/realemu; aux/vga -p}
logprog xd -x1 '#r/nvram'
logprog cat /dev/audiostat
logprog cat /dev/volume
next prev parent reply other threads:[~2012-05-01 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 18:14 rep sl
2012-04-30 23:19 ` rep cinap_lenrek
2012-05-01 13:34 ` sl [this message]
2012-05-01 14:07 ` rep cinap_lenrek
2012-05-01 14:19 ` rep sl
2012-05-01 15:33 ` rep cinap_lenrek
2012-05-01 15:49 ` rep Steve Simon
2012-05-01 15:52 ` rep sl
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=cf684b3b775f735290ff55f611203e8d@sp.nv \
--to=sl@9front.org \
--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).