On Fri, 29 Nov 2002, sean finney wrote:
> well the trouble is, if you're not running an smp kernel, the kernel
> doesn't know bout multiple cpus to begin with, right?
That's true.
> afaik there'd only be one cpu entry in /proc/cpuinfo if you're not
> running an smp kernel
But it's a good defaul
On Fri, Nov 29, 2002 at 01:25:09PM +0100, Jens Ruehmkorf wrote:
> On Thu, 28 Nov 2002, sean finney wrote:
> > On Wed, Nov 27, 2002 at 06:45:21PM -0500, Michael Stone wrote:
> > > Can you detect smp from non-smp kernel?
> >
> > i would guess not...
>
> Just count the processors in /proc/cpuinfo, he
On Thu, 28 Nov 2002, sean finney wrote:
> On Wed, Nov 27, 2002 at 06:45:21PM -0500, Michael Stone wrote:
> > Can you detect smp from non-smp kernel?
>
> i would guess not...
Just count the processors in /proc/cpuinfo, here is an example:
$ grep "^proc" /proc/cpuinfo
processor : 0
processor
* Stephen Zander <[EMAIL PROTECTED]> [2002-11-28 09:05]:
> > "sean" == sean finney <[EMAIL PROTECTED]> writes:
> /proc/cpuinfo.
it doesn't work with a non-smp kernel.
but
dmesg | grep Processors seems to work (on x86, 2.4 kernel).
> Of course if the user doesn't start out using an smp kern
On Thu, 2002-11-28 at 19:00, Stephen Zander wrote:
> > "sean" == sean finney <[EMAIL PROTECTED]> writes:
> sean> i would guess not...
>
> /proc/cpuinfo.
>
> Of course if the user doesn't start out using an smp kernel, they
> clearly don't need one.
Not necessarily. One obvious applicatio
> "sean" == sean finney <[EMAIL PROTECTED]> writes:
sean> i would guess not...
/proc/cpuinfo.
Of course if the user doesn't start out using an smp kernel, they
clearly don't need one.
--
Stephen
"So if she weighs the same as a duck, she's made of wood."... "And
therefore?"... "A witch!
On Wed, Nov 27, 2002 at 06:45:21PM -0500, Michael Stone wrote:
> On Thu, Nov 28, 2002 at 09:55:52AM +1100, Brian May wrote:
> >Ideally have some way for the user to override the default choice if
> >automatic selection fails...
>
> Can you detect smp from non-smp kernel?
i would guess not...
pg
On Thu, Nov 28, 2002 at 09:55:52AM +1100, Brian May wrote:
Ideally have some way for the user to override the default choice if
automatic selection fails...
Can you detect smp from non-smp kernel?
Mike Stone
On Wed, Nov 27, 2002 at 12:46:20PM -0800, Vonsur Kcin wrote:
> *)
> echo 386
Ideally have some way for the user to override the default choice if
automatic selection fails...
--
Brian May <[EMAIL PROTECTED]>
On Wed, Nov 27, 2002 at 12:46:20PM -0800, Vonsur Kcin wrote:
> cpuid=sed -ne 's/^model name.*: //p' < /proc/cpuinfo
just don't forget the backticks :)
> case "$cpuid" in
> "AMD Athlon"*)
> echo k7
> ;;
yeah, even simpler than i was thinking!
sean
pgpVsp5bfIinX.pgp
D
On Wed, Nov 27, 2002 at 12:46:20PM -0800, Vonsur Kcin wrote:
> case "$cpuid" in
> "AMD Athlon"*)
> echo k7
> ;;
> "AMD K6"*)
> echo k6
> ;;
> "Celeron"*)
> echo 686
> ;;
> "Pentium "*)
> echo 586tsc
> ;;
> *)
> echo 386
> es
On Wed, Nov 27, 2002 at 03:22:12PM -0500, sean finney wrote:
> On Wed, Nov 27, 2002 at 08:25:35PM +0100, Thomas Lange wrote:
> > Is there a script, that can automaticly determine the best or correct
> > name of the kernel-image that should be installed?
> >
> > I think something with grep and sed
On Wed, Nov 27, 2002 at 08:25:35PM +0100, Thomas Lange wrote:
> Is there a script, that can automaticly determine the best or correct
> name of the kernel-image that should be installed?
>
> I think something with grep and sed from /proc/cpuinfo should write
> k7, k6, 586tsc or someing else to std
On Wed, Nov 27, 2002 at 08:25:35PM +0100, Thomas Lange wrote:
> Is there a script, that can automaticly determine the best or correct
> name of the kernel-image that should be installed?
>
> I think something with grep and sed from /proc/cpuinfo should write
> k7, k6, 586tsc or someing else to st
You might want to talk to the debian-installer people. They either might
have some ideas about it or will certainly be interested...
Grep the -devel list for debian-installer and Tollef Fog Heen.
*t
--
---
Tomas Pospisek
So
Is there a script, that can automaticly determine the best or correct
name of the kernel-image that should be installed?
I think something with grep and sed from /proc/cpuinfo should write
k7, k6, 586tsc or someing else to stdout. Has someone created this
script already ?
kernel-image-2.4.18-k7
16 matches
Mail list logo
