From: Alex deVries <adevries@thepuffingroup.com>
To: Rich Rauenzahn <rrauenza@cup.hp.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] H60
Date: Wed, 30 Jun 1999 02:34:57 -0400 [thread overview]
Message-ID: <3779BA91.96869AC9@thepuffingroup.com> (raw)
In-Reply-To: 008f01bec2bc$a91023c0$e38f4b0f@cup.hp.com
Rich Rauenzahn wrote:
>
> Take a look at /usr/lib/sched.models on HP-UX -- it documents quite a few
> models and PA-RISC versions.
>
Oh, that's pretty interesting. I found sched.modules in
/usr/sam/lib/mo.
What's the second column?
- Alex
--
Alex deVries
Vice President of Engineering
The Puffin Group
next prev parent reply other threads:[~1999-06-30 6:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-29 23:51 [parisc-linux] H60 Davin Petersen
1999-06-30 0:13 ` Stan Sieler
1999-06-30 0:43 ` Alex deVries
1999-06-30 0:53 ` Stan Sieler
1999-06-30 5:51 ` Rich Rauenzahn
1999-06-30 6:34 ` Alex deVries [this message]
1999-06-30 6:55 ` Richard J. Rauenzahn
-- strict thread matches above, loose matches on Subject: below --
1999-06-30 5:20 Mike Hibler
1999-06-30 15:54 Davin Petersen
1999-06-30 17:27 ` Stan Sieler
1999-06-30 17:26 Davin Petersen
1999-06-30 21:38 ` Kirk Bresniker
1999-07-01 1:20 Kevin Carson
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=3779BA91.96869AC9@thepuffingroup.com \
--to=adevries@thepuffingroup.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=rrauenza@cup.hp.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