public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Changing CPU and motherboard
Date: Sun, 29 Jun 2025 04:23:28 +0200	[thread overview]
Message-ID: <aGCjoAjOwSryFQ67@tp> (raw)
In-Reply-To: <0c9eeaf9-84c8-7841-464d-f732a150f3f3@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

Am Sat, Jun 28, 2025 at 07:39:03PM -0500 schrieb Dale:
> whiteman808 wrote:
> > How does situation look in binary-based distros like Debian, Arch? Is
> > rsyncing old Debian or Arch installation to PC with new processor or
> > motherboard and configuring hardware-specific stuff sufficient?
> >
> >
> 
> 
> I haven't used those in ages.  Unless something has changed, they are
> always ready for pretty much any hardware.  When you install those, they
> are set to a common setting for pretty much any CPU in that arch. 
> Basically and amd64 install should work with any amd64 CPU.  This is why
> some run Gentoo.  In some cases having settings specific to a CPU can
> result in code running faster. 

I just read about using a binary distro with a more modern baseline. One 
post said that a lot of software already has built-in support for that. So 
even if you use a well-hung distro like debian whose baseline is, say v2, 
then there is still userland software that detects the hardware and 
dynamically loads proper code paths, like blender, ffmpeg etc.

-- 
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.

Rather to have a good position than a good job.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-06-29  2:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-28 16:38 [gentoo-user] Changing CPU and motherboard whiteman808
2025-06-28 17:33 ` Jay Faulkner
2025-06-28 17:49   ` Michael
2025-06-28 19:10   ` whiteman808
2025-06-28 19:57     ` Jay Faulkner
2025-06-28 19:32   ` Dale
2025-06-28 19:44     ` whiteman808
2025-06-28 20:10       ` Dale
2025-06-28 20:15         ` Michael
2025-06-29  0:33           ` Dale
2025-06-28 23:04         ` whiteman808
2025-06-29  0:39           ` Dale
2025-06-29  2:23             ` Frank Steinmetzger [this message]
2025-06-29  1:17           ` Jay Faulkner
2025-06-29 17:51           ` [gentoo-user] " Grant Edwards
2025-06-29  2:19   ` [gentoo-user] " Frank Steinmetzger
2025-06-29  7:44     ` Michael
2025-06-29 17:55       ` [gentoo-user] " Grant Edwards
2025-06-29 17:54     ` Grant Edwards
2025-07-01 16:22   ` [gentoo-user] " Steven Lembark
2025-07-01 22:58     ` Jay Faulkner
2025-06-29 17:48 ` [gentoo-user] " Grant Edwards

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=aGCjoAjOwSryFQ67@tp \
    --to=warp_7@gmx.de \
    --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