1 |
Henry W. Peters posted on Fri, 20 Sep 2013 23:55:01 -0400 as excerpted: |
2 |
|
3 |
> You mentioned in a previous msg, that it was possible to install Gentoo |
4 |
> from another "live" DVD/C OS... wondering if you know of any how to do |
5 |
> links... ? |
6 |
|
7 |
FWIW, I've only installed from gentoo's live* when working on someone |
8 |
else's systems, doing it all as simple as possible "by the handbook", so |
9 |
they could see how it all worked. |
10 |
|
11 |
Back when I first installed gentoo in 2004, I did so from an existing |
12 |
Mandrake system, installing gentoo to a different (set of) partition(s). |
13 |
|
14 |
Since that first time I've not actually done a whole lot of gentoo |
15 |
installs, only the (32-bit) netbook. For it, I created a 32-bit chroot |
16 |
on my main system based on the gentoo/amd64 32-bit chroot guide, except |
17 |
building the bits (like the kernel and openrc) that would ordinarily not |
18 |
need built in a chroot too. Then I cp-ed the chroot install to an |
19 |
external drive and booted it on the target system. Once booted to the |
20 |
external on the target system, I was able to run the usual partitioning |
21 |
natively, mount the new internal drive partitions as necessary, and cp |
22 |
external -> internal. |
23 |
|
24 |
Since my main system is vastly more powerful than the netbook, I continue |
25 |
to use the chroot build scheme for netbook updates today, doing an rsync |
26 |
dry-run first to catch anything that's different between the netbook and |
27 |
the chroot-image, resolving any config differences so they're the same on |
28 |
both, then doing the update to the chroot and ssh/rsyncing it over to the |
29 |
netbook. |
30 |
|
31 |
Unfortunately I don't keep up with netbook updates like I do the main |
32 |
system, so it gets quite behind, often a year or more, so when I *DO* do |
33 |
the update, it's a BIG job, often involving intermediate updates and |
34 |
reconfiguration in the middle of things so the final update will actually |
35 |
complete properly. |
36 |
|
37 |
But of course not all that's apropos to the current situation. Anyway, |
38 |
yes, installing gentoo from an existing installation or some non-gentoo |
39 |
live* isn't particularly hard. As might be expected on gentoo, there's |
40 |
actually instructions! =:^) |
41 |
|
42 |
The Gentoo Linux alternative installation method HOWTO |
43 |
|
44 |
http://www.gentoo.org/doc/en/altinstall.xml |
45 |
|
46 |
Section 3 is Installation from non-Gentoo LiveCDs. |
47 |
Section 4 is Diskless install using PXE boot. |
48 |
Section 5 is Installing Gentoo from an existing Linux distribution. |
49 |
|
50 |
Take your pick! =:^) |
51 |
|
52 |
Note that in all three cases the instructions substitute a few steps as |
53 |
appropriate for those found in the handbook, so you'll need the handbook |
54 |
available as well, since after the substituted steps you resume |
55 |
installation from the handbook at the appropriate location as instructed. |
56 |
That shouldn't be a problem from either an existing install or from most |
57 |
non-gentoo live*s as you can simply use the existing browser and net |
58 |
connection to read the docs on the gentoo site. =:^) |
59 |
|
60 |
The other alternative, as mentioned, would be doing a chroot |
61 |
installation, much like I did with my netbook, basically following the 32- |
62 |
bit chroot guide except that it doesn't have to be 32-bit, a 64-bit chroot |
63 |
on an existing 64-bit system would work similarly except that you'd run |
64 |
linux64 instead of linux32. And (as I did) you'd install the bits the |
65 |
chroot guide skips as well, kernel and openrc, etc, since it won't just |
66 |
be a chroot, you'll ultimately be booting it. |
67 |
|
68 |
(One nice thing about a fully bootable chroot is that if you setup your |
69 |
bootloader for it, you can even boot to it instead of the main system on |
70 |
the chroot system too. And if it's a 32-bit chroot that means you can |
71 |
run the main system no-multilib as well, since you don't need the 32-bit |
72 |
multilib stuff because you have a full 32-bit system in the chroot! =:^) |
73 |
|
74 |
How to set up a 32bit chroot |
75 |
|
76 |
http://www.gentoo.org/proj/en/base/amd64/howtos/chroot.xml |
77 |
|
78 |
|
79 |
You can of course do a chroot without following the guide above, but |
80 |
following the guide is nice, as they've already given some thought to |
81 |
making the chroot work well with the host system too, with as little |
82 |
waste as possible. For instance, the chroot guide uses a lot of bind- |
83 |
mounts to mount bits of the main system inside the chroot as well, so |
84 |
they don't have to be duplicated, and cps other things. That's a nice |
85 |
touch, and it gives you a bit of flexibility too, since you can simply |
86 |
choose not to bind-mount or copy bits that differ enough between the host |
87 |
system and the ultimate target to screw things up. =:^) (Things like |
88 |
/sys and /proc shouldn't matter, however, since in chroot mode you don't |
89 |
actually run the kernel you build in the chroot, and you'll want to |
90 |
configure and build the kernel for the target system without referring to |
91 |
the hosts /proc and /sys files. So those can be mounted from the host |
92 |
without interfering with the target system, as long as you don't use them |
93 |
to setup your kernel config.) |
94 |
|
95 |
-- |
96 |
Duncan - List replies preferred. No HTML msgs. |
97 |
"Every nonfree program has a lord, a master -- |
98 |
and if you use the program, he is your master." Richard Stallman |