| 1 |
Jason wrote: |
| 2 |
> |
| 3 |
> initrd is exactly how you do it. In the case of booting off of USB, |
| 4 |
> there are too many variables (drive detection order, different |
| 5 |
> hardware, etc) to handle on the kernel command line. An initrd gives |
| 6 |
> you the flexibility to solve these problems. |
| 7 |
> |
| 8 |
>> You could use initrd/initramfs, but seems like a lot of complications |
| 9 |
>> for little gain... |
| 10 |
> |
| 11 |
> I wouldn't call a portable, writable, boot from anywhere Linux OS on a |
| 12 |
> thumbdrive a trivial gain. ;-) |
| 13 |
> |
| 14 |
> Jason. |
| 15 |
> |
| 16 |
|
| 17 |
|
| 18 |
But y<ou have the headache of interface at the old and new root across |
| 19 |
the pivot root. What happens if you execute something that was |
| 20 |
dynamically linked from intramfs and it decides to load and link another |
| 21 |
module with dlopen() from new root ? If you have that module and it |
| 22 |
belongs to the same version, then probably everything is fine. Otherwise |
| 23 |
it might not be. |
| 24 |
|
| 25 |
Also, opened files and extra nodes in /dev during intiramfs phase tend |
| 26 |
to cause a headache or two... |
| 27 |
|
| 28 |
|
| 29 |
Branko |
| 30 |
-- |
| 31 |
gentoo-amd64@l.g.o mailing list |
Archives