1 |
On 2013-11-12 4:55 PM, Tanstaafl <tanstaafl@×××××××××××.org> wrote: |
2 |
>> Depending on your system, you might want to add one or more of the |
3 |
>> following options: |
4 |
>> Option Description |
5 |
>> --disklabel Add support for LABEL= settings in your /etc/fstab |
6 |
>> --dmraid Add support for fake hardware RAID |
7 |
>> --firmware Add in firmware code found on the system |
8 |
>> --gpg Add in GnuPG support |
9 |
>> --iscsi Add support for iSCSI |
10 |
>> --luks Add support for luks encryption containers |
11 |
>> --lvm Add support for LVM |
12 |
>> --mdadm Add support for software RAID |
13 |
>> --multipath Add support for multiple I/O access towards a SAN |
14 |
>> --zfs Add support for ZFS |
15 |
> |
16 |
> So, are these *all* of the potential options? If so, then I can probably |
17 |
> safely say that all I need is lvm... |
18 |
|
19 |
Never got a response to this... |
20 |
|
21 |
Maybe I can ask another way... |
22 |
|
23 |
Is this a complete list of the items that may break BOOTING? I |
24 |
understand now that you can add pretty much any drivers that you want, |
25 |
but on my server (that has the separate /usr), modules are disabled and |
26 |
so I have every driver and filesystem built into the kernel. |
27 |
|
28 |
Going just by the above list of items, the only thing I use is lvm, so |
29 |
I'm guessing (I *hate* guessing) that this is the only thing I need in |
30 |
my initramfs. |
31 |
|
32 |
Another question - is there any reason I couldn't just enable everything |
33 |
just in case? Or could that cause other problems? |
34 |
|
35 |
On 2013-11-12 5:54 PM, Neil Bothwick <neil@××××××××××.uk> wrote: |
36 |
> There is a very capable tool for examining your system and deciding |
37 |
> what is needed... you. |
38 |
|
39 |
Yes, but again, I have never had to worry about this - EVER - in the |
40 |
past. The question simply never came up. |
41 |
|
42 |
Now, I am being FORCED to worry about it... and I want to understand it |
43 |
as much as possible. |