All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Albert Cahalan <albert@users.sourceforge.net>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	ak@muc.de, gandalf@wlug.westbo.se
Subject: Re: [PATCH] Warn people that ipchains and ipfwadm are going away.
Date: 23 Sep 2004 15:36:34 -0400	[thread overview]
Message-ID: <1095968193.4969.980.camel@cube> (raw)
In-Reply-To: <41532504.3000005@nortelnetworks.com>

On Thu, 2004-09-23 at 15:33, Chris Friesen wrote:
> Albert Cahalan wrote:
> 
> > Who is doing a 32-bit userland on x86-64, and WTF for?
> > Why do they not also run a 32-bit kernel?
> 
> Backwards compatibility?  Desire to run binary-only 32-bit software as well as 
> 64-bit software on the same kernel?

Nope. For that, you run 99% 64-bit, including iptables.
That's what is typically done. So you'd have a 32-bit
OpenOffice maybe, and everything else is 64-bit.

I'm still not seeing a need to run an x86-64 kernel
with an i386 iptables.



  reply	other threads:[~2004-09-23 19:41 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23 18:07 [PATCH] Warn people that ipchains and ipfwadm are going away Albert Cahalan
2004-09-23 19:33 ` Chris Friesen
2004-09-23 19:36   ` Albert Cahalan [this message]
2004-09-23 19:57     ` Andy Lutomirski
2004-09-23 19:57     ` David S. Miller
2004-09-23 23:08 ` Matthew Garrett
2004-09-23 23:25   ` David S. Miller
     [not found] <2GFBZ-61e-11@gated-at.bofh.it>
     [not found] ` <2GSfS-6eW-5@gated-at.bofh.it>
     [not found]   ` <2H0ZO-49v-13@gated-at.bofh.it>
     [not found]     ` <2HdDL-48z-53@gated-at.bofh.it>
     [not found]       ` <2HdNp-4eJ-27@gated-at.bofh.it>
2004-09-22 12:15         ` Andi Kleen
2004-09-22 14:04           ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2004-09-20 23:09 Rusty Russell (IBM)
2004-09-21 12:36 ` Marc Ballarin
2004-09-21 21:58   ` Rusty Russell
2004-09-21 21:58     ` Rusty Russell
2004-09-21 22:36     ` Marc Ballarin
2004-09-21 22:36       ` David S. Miller
2004-09-21 22:36         ` David S. Miller
2004-09-21 23:35         ` Marc Ballarin
2004-09-22  0:16           ` Patrick McHardy
2004-09-22  0:16             ` Patrick McHardy
2004-09-22 13:37             ` Marc Ballarin
2004-09-22 13:58               ` Jesper Juhl
2004-09-22 14:13                 ` Richard B. Johnson
2004-09-22 11:36     ` Richard B. Johnson
2004-09-22 11:47       ` Martin Josefsson
2004-09-22 11:47         ` Martin Josefsson
2004-09-22 12:05         ` Richard B. Johnson
2004-09-22 12:41           ` Gene Heskett
2004-09-23 14:56             ` Martijn Lievaart
2004-09-22 14:19           ` Fao, Sean
2004-09-22 15:31           ` William Stearns
2004-09-22 15:31             ` William Stearns
2004-09-22 16:03             ` Richard B. Johnson
2004-09-22 16:27               ` William Stearns
2004-09-22 11:52       ` James Courtier-Dutton
2004-09-22 11:55       ` Marc Ballarin
2004-09-21 17:57 ` Bill Davidsen

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=1095968193.4969.980.camel@cube \
    --to=albert@users.sf.net \
    --cc=ak@muc.de \
    --cc=albert@users.sourceforge.net \
    --cc=cfriesen@nortelnetworks.com \
    --cc=gandalf@wlug.westbo.se \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.