1 |
On Tue, 27 Mar 2012 19:55:37 +0200 |
2 |
che@××××××.se wrote: |
3 |
|
4 |
> Neil Bothwick <neil@××××××××××.uk> writes: |
5 |
> |
6 |
> > On Tue, 27 Mar 2012 14:26:46 +0000, Alan Mackenzie wrote: |
7 |
> > |
8 |
> >> > As you move more and more software off of /usr into / you start |
9 |
> >> > to realize that the idea of "tiny partition that contains just |
10 |
> >> > what I need to boot and mount /usr" is becoming "not so tiny" |
11 |
> >> > anymore. The distinction between what is "boot" software versus |
12 |
> >> > "user" software gets less clear. |
13 |
> >> |
14 |
> >> Again, isn't this the same for an initramfs? |
15 |
> > |
16 |
> > No, because an initramfs only needs enough to mount / and /usr, then |
17 |
> > everything else comes from the usual source. If you're not using and |
18 |
> > fancy block devices, the initramfs only needs busybox and an init |
19 |
> > script. Even adding LVM, RAID and encryption only requires three |
20 |
> > more binaries - and those are all disposed of once switch_root is |
21 |
> > run and the tmpfs released. |
22 |
> |
23 |
> The question remains. If it's possible to do that from an initramfs, |
24 |
> then shouldn't it be possible to put the same tools and binarias on /, |
25 |
> and mount /usr early? |
26 |
|
27 |
Of course it's possible, it's merely a gigantic list of cd commands. |
28 |
|
29 |
The question is, is it advisable? |
30 |
|
31 |
I offer you two choices: |
32 |
|
33 |
a. Move a few commands into an initramfs, truly only the ones you |
34 |
really do need, or |
35 |
b. Move 7G of files onto / (i.e. everything) and lose any benefit you |
36 |
(and everyone else with different ideas to you) may want by having a |
37 |
separate /usr. Oh, and you get to deal with finding the hardcoded paths |
38 |
and fixing the code yourself. |
39 |
|
40 |
Those are your choices. Pick one. |
41 |
|
42 |
|
43 |
|
44 |
-- |
45 |
Alan McKinnnon |
46 |
alan.mckinnon@×××××.com |