public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason <gentoo@lakedaemon.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] boot Gentoo from USB key
Date: Wed, 30 Apr 2008 11:40:28 -0400	[thread overview]
Message-ID: <481892EC.6050105@lakedaemon.net> (raw)
In-Reply-To: <48188AC2.70804@avtomatika.com>

Branko Badrljica wrote:
> Jason wrote:
>> initrd is exactly how you do it.  In the case of booting off of USB, 
>> there are too many variables (drive detection order, different 
>> hardware, etc) to handle on the kernel command line. An initrd gives 
>> you the flexibility to solve these problems.
>>
>>> You could use initrd/initramfs, but seems like a lot of complications 
>>> for little gain...
>>
>> I wouldn't call a portable, writable, boot from anywhere Linux OS on a 
>> thumbdrive a trivial gain.  ;-)
> 
> But y<ou have the headache of interface at the old and new root across 
> the pivot root. What happens if you execute something that was 
> dynamically linked from intramfs and it decides to load and link another 
> module with dlopen() from new root ? If you have that module and it 
> belongs to the same version, then probably everything is fine. Otherwise 
> it might not be.

1.) a good initrd will use only statically linked executables.
2.) you shouldn't start any servers or background processes from initrd.
3.) initrd's are tied to kernels.  Every distro's initrd generator is 
re-run upon upgrading the kernel.  The modules versions won't be out of 
sync then.  Gentoo has genkernel for this purpose.

> Also, opened files and extra nodes in /dev during intiramfs phase tend 
> to cause a headache or two...

If your initrd follows the 3 suggestions, above, there won't be any 
processes running to hold a file or device open.  Unless you had 
something else in mind?

Jason.
-- 
gentoo-amd64@lists.gentoo.org mailing list



  reply	other threads:[~2008-04-30 15:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30  6:43 [gentoo-amd64] boot Gentoo from USB key Raffaele BELARDI
2008-04-30  6:49 ` Kyle Liddell
2008-04-30  6:56 ` Branko Badrljica
2008-04-30  7:44   ` Raffaele BELARDI
2008-05-05  8:40     ` Raffaele BELARDI
2008-04-30 10:47 ` [gentoo-amd64] " Duncan
2008-04-30 12:35 ` [gentoo-amd64] " Jason
2008-04-30 14:29   ` Branko Badrljica
2008-04-30 14:47     ` Jason
2008-04-30 15:05       ` Branko Badrljica
2008-04-30 15:40         ` Jason [this message]
2008-04-30 15:55           ` Branko Badrljica
2008-05-05  8:53           ` Raffaele BELARDI
2008-04-30 17:39 ` Hernan Lopez
2008-04-30 17:58   ` Branko Badrljica
2008-05-01  7:26     ` Branko Badrljica
2008-04-30 18:03 ` Drake Donahue
2008-04-30 18:21   ` Drake Donahue
2008-05-02 11:22 ` [gentoo-amd64] " Duncan
2008-05-02 15:33   ` Drake Donahue
2008-05-05  8:38     ` Raffaele BELARDI
2008-05-06 13:18       ` Raffaele BELARDI
2008-05-06 17:08         ` Duncan

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=481892EC.6050105@lakedaemon.net \
    --to=gentoo@lakedaemon.net \
    --cc=gentoo-amd64@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