public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What are common SSDs does and don'ts.
Date: Tue, 1 Apr 2025 05:12:44 -0500	[thread overview]
Message-ID: <6e010192-cc37-46be-bd89-c6d67deac4b3@gmail.com> (raw)
In-Reply-To: <12658467.O9o76ZdvQC@cube>

Peter Humphrey wrote:
> On Tuesday, 1 April 2025 01:44:18 British Summer Time Dale wrote:
>
>> ... I have /usr on the same partition as / this time around. 
>> Do I need a init thingy still or can I ditch that thing?  I do have /var
>> on a separate partition, if that matters. 
> I have /var on a separate partition on some machines, and I only need an 
> initrd for microcode loading. I suppose I could include that in the kernel, 
> but I haven't tried that.
>


I thought about the fact I have a merged /usr now which means everything
is in /usr.  I hadn't thought of microcode being needed tho.  How do I
find out if there is any microcode being loaded on my system?  I do have
the package installed, read somewhere that it only loads something if it
is needed so no real harm in having it installed even if nothing is
being used today.  It could prove helpful if something is being used
later on tho. 

Is there somewhere I can look or some command I can run to see if I load
any microcode that it needs to access while booting but before /var is
mounted?  Why isn't the microcode put in /usr or something anyway? 

Dale

:-)  :-) 


  reply	other threads:[~2025-04-01 10:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-22 18:50 [gentoo-user] What are common SSDs does and don'ts Dale
2025-03-22 19:29 ` Mark Knecht
2025-03-22 21:37 ` Michael
2025-03-23  1:48   ` Dale
2025-03-23  9:00     ` Michael
2025-03-23 21:41       ` Dale
2025-03-23 22:15         ` Nate Eldredge
2025-03-23 22:32         ` Frank Steinmetzger
2025-03-23 23:24           ` Dale
2025-03-31 21:27             ` Frank Steinmetzger
2025-04-01  0:44               ` Dale
2025-04-01 10:01                 ` Peter Humphrey
2025-04-01 10:12                   ` Dale [this message]
2025-04-01 10:24                     ` Peter Humphrey
2025-04-01 12:56                       ` Dale
2025-04-01 13:13                         ` Peter Humphrey
2025-04-02  3:33                           ` Dale
2025-04-02 11:13                             ` Peter Humphrey
2025-04-01 11:04                     ` Michael
2025-04-01 13:03                       ` Dale
2025-04-01 15:44                         ` Michael
2025-04-02  4:04                           ` Dale
2025-04-02  8:29                             ` Michael
2025-04-07 18:28                               ` Dale
2025-04-01 22:46                         ` Frank Steinmetzger
2025-04-01 23:08                 ` Frank Steinmetzger
2025-04-02  4:03                   ` Dale
2025-03-23  4:34   ` Matt Jolly
2025-03-23  6:56   ` netfab
2025-03-23  7:01     ` Dale
2025-03-23  7:03       ` netfab
2025-03-23 22:46   ` Frank Steinmetzger

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=6e010192-cc37-46be-bd89-c6d67deac4b3@gmail.com \
    --to=rdalek1967@gmail.com \
    --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