public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Advice for 64-bit n00b?
Date: Thu, 4 Mar 2010 08:56:34 +0000	[thread overview]
Message-ID: <3BB5376C-2909-484D-8780-F9E492754C19@stellar.eclipse.co.uk> (raw)
In-Reply-To: <hmnmul$1l4$1@dough.gmane.org>


On 4 Mar 2010, at 07:19, Nikos Chantziaras wrote:

> On 03/04/2010 08:44 AM, Graham Murray wrote:
>> Volker Armin Hemmann<volkerarmin@googlemail.com>  writes:
>>
>>> no, it is not safe to have a 64bit only system. Just choose the  
>>> multilib
>>> profile and start installing. If something needs the 32bit emul  
>>> libs, it will
>>> pull the stuff in. There is nothing you need to care about.
>>
>> What is unsafe about a 64bit only system? Surely if it were unsafe  
>> then
>> Gentoo would not offer no-multilib profiles? I have recently built 2
>> systems using a no-multilib profile and have not found any  
>> problems, and
>> expect to start building a third one today.
>
> You didn't understand the question Volker was replying to.  The  
> question was not about "safe" as in "security", but rather "safe" as  
> in "I can rest assured that a no-multilib system can run every  
> software I could install", which is clearly not the case since some  
> applications need 32-bit support.

I could imagine that web-browsers might need 32-bit support in order  
to play Flash, but can you suggest other applications which might?

This is a headless server, and I was kinda reassured by Alan's  
response (Wed, 3 Mar 2010 22:04:17 +0200) [1] that seemed to assure me  
that a statically linked 32-bit binary would work fine if I selected  
the "no-multilib" profile.

I'd be really quite happy if I knew that this decision was revocable -  
if I could choose "no-multilib" now and change my mind using eselect  
later. Presumably  I can choose to keep these 32-bit libs for the  
moment & blow them away if I find I don't need them - this lib32 is,  
after all, in the stage3-amd64-*tar.bz2, so what is the point in  
offering me "no-multilib" if I can't do that?

Stroller.



[1] http://archives.gentoo.org/gentoo-user/msg_64a30b77742cf5846705952e6129367d.xml
http://tinyurl.com/ykvx5co



  parent reply	other threads:[~2010-03-04  8:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 15:29 [gentoo-user] Advice for 64-bit n00b? Stroller
2010-03-03 15:32 ` Alan McKinnon
2010-03-03 17:04 ` Stroller
2010-03-03 20:04   ` Alan McKinnon
2010-03-03 22:50     ` Mick
2010-03-03 22:56       ` Volker Armin Hemmann
2010-03-04  6:44         ` Graham Murray
2010-03-04  7:19           ` [gentoo-user] " Nikos Chantziaras
2010-03-04  8:16             ` Volker Armin Hemmann
2010-03-04  8:56             ` Stroller [this message]
2010-03-04  9:15               ` Volker Armin Hemmann
2010-03-04 12:02                 ` Mick
2010-03-05  1:52               ` Walter Dnes
2010-03-04  7:23           ` [gentoo-user] " Zeerak Mustafa Waseem
2010-03-04  7:30           ` Alan McKinnon

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=3BB5376C-2909-484D-8780-F9E492754C19@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox