From: Matti Aarnio <matti.aarnio@zmailer.org>
To: 64738 <schwung@rumms.uni-mannheim.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel bits
Date: Wed, 22 Nov 2000 12:09:16 +0200 [thread overview]
Message-ID: <20001122120916.Z28963@mea-ext.zmailer.org> (raw)
In-Reply-To: <974881546.3a1b830ae5202@rumms.uni-mannheim.de> <20001122112952.Y28963@mea-ext.zmailer.org> <974886395.3a1b95fb43c63@rumms.uni-mannheim.de>
In-Reply-To: <974886395.3a1b95fb43c63@rumms.uni-mannheim.de>; from schwung@rumms.uni-mannheim.de on Wed, Nov 22, 2000 at 10:46:35AM +0100
On Wed, Nov 22, 2000 at 10:46:35AM +0100, 64738 wrote:
> uname -m tells me the hardware type of the machine. Is this determined while
> booting or is this the architecture I choose during 'make config'?
Mainly chosen during "make config".
Processor info you see at /proc/cpuinfo
> Can't I run a i386 kernel on a ia64 machine? I know something like this
> from HP-UX. You can choose between a 32 and a 64 bit kernel when
> installing, so knowing that you have a 64 bit capable machine does not
> say that you have a 64 bit kernel.
> And I want to have the kernel bits, not the processor bits.
Solaris runs 32-bit kernels on 64-bit UltraSPARCs
(up to Solaris version 2.6)
So yes, something like that MAY be possible in case
of ia64, but somehow I doubt...
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-22 10:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 8:25 64738
2000-11-22 9:29 ` Matti Aarnio
2000-11-22 9:46 ` 64738
2000-11-22 10:09 ` Matti Aarnio [this message]
2000-11-23 1:15 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2000-11-22 8:25 64738
2000-11-27 13:36 ` Chad Schwartz
2000-11-27 13:31 ` Keith Owens
2000-11-27 14:22 ` Chad Schwartz
2000-11-27 13:53 ` Richard B. Johnson
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=20001122120916.Z28963@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwung@rumms.uni-mannheim.de \
/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
all inboxes | Powered by JetHome®