1 |
On Wed, 7 Sep 2011 19:04:17 -0400, Canek Peláez Valdés wrote: |
2 |
|
3 |
> > Putting it on a logical volume is one advantage, allowing /usr to be |
4 |
> > resized should the need arise. |
5 |
> |
6 |
> Why not allow / to be resized entirely? You probably will take the |
7 |
> machine off-line anyway. |
8 |
|
9 |
Because you can't boot from an LV, so you'd than need a separate /boot |
10 |
and an initramfs. Without LVM, you are unlikely to be able to resize / |
11 |
or /usr as it is not usually the last partition on the drive. |
12 |
|
13 |
> >> Mounting it read-only |
14 |
> >> seems the only sensible one, and then I think is better to go all the |
15 |
> >> way and mount / read-only. |
16 |
> > |
17 |
> > Putting /etc on a read-only filesystem seems a really bad idea. |
18 |
> |
19 |
> mount -o remount,rw / |
20 |
> emerge --sync && emerge -uDNv world |
21 |
> dispatch-conf |
22 |
> mount -o remount,ro / |
23 |
> |
24 |
> Or, if you only want to modify some configuration file (which in a |
25 |
> sane environment doesn't happen that often): |
26 |
> |
27 |
> mount -o remount,rw / |
28 |
> adduser fulano ... |
29 |
> mount -o remount,ro / |
30 |
|
31 |
This is longer than the init script needed in an initramfs. I wonder what |
32 |
problems you'd have when booting as the kernel tries to update the likes |
33 |
of /etc/mtab on a read-only fs. |
34 |
|
35 |
> Again, I don't see the reason for a separated /usr. |
36 |
|
37 |
That doesn't mean there aren't several valid reasons to do so. |
38 |
|
39 |
> But *again*, if |
40 |
> that's what you want, you will be able to do it. You will just need an |
41 |
> initramfs. |
42 |
|
43 |
I neither have nor need one at the moment, which means this update will |
44 |
break my system. |
45 |
|
46 |
|
47 |
-- |
48 |
Neil Bothwick |
49 |
|
50 |
Last words of a Windows user: = Where do I have to click now? - There? |