1 |
Michael Mol wrote: |
2 |
> On Mon, Sep 17, 2012 at 3:08 PM, Dale <rdalek1967@×××××.com> wrote: |
3 |
>> Michael Mol wrote: |
4 |
>>> On Mon, Sep 17, 2012 at 2:26 PM, Dale <rdalek1967@×××××.com> wrote: |
5 |
>>>> Michael Mol wrote: |
6 |
>>>>> On Mon, Sep 17, 2012 at 2:00 PM, Volker Armin Hemmann |
7 |
>>>>> <volkerarmin@××××××××××.com> wrote: |
8 |
>>>>>> Am Montag, 17. September 2012, 12:34:12 schrieb covici@××××××××××.com: |
9 |
>>>>>>> OK, sorry if this is a dumb question, but I did search for it using make |
10 |
>>>>>>> menuconfig, but could not actually find it! I have all my usb host |
11 |
>>>>>>> controller drivers as modules, if that makes any difference. I am using |
12 |
>>>>>>> 3.4.0-gentoo. |
13 |
>>>>>> hit / in menuconfig. It is there. |
14 |
>>>>> Although I do believe you need to remove the CONFIG_ prefix before you search. |
15 |
>>>>> |
16 |
>>>> Also, there are also other options that must be turned on for it to show |
17 |
>>>> up. I had to enable other things before I could find it in the menu. |
18 |
>>>> This is another reason I asked the question on whether it is really |
19 |
>>>> needed or not. It wasn't just one thing I had to enable but a couple |
20 |
>>>> other things too. I'm still not sure I need either of those but . . . |
21 |
>>> You do, for the same reason you need electricity; you may not use |
22 |
>>> electricity directly, but something you use does. |
23 |
>>> |
24 |
>>> Similarly, you may not need this config option, but something you use |
25 |
>>> does (or something you use uses something you use which does). |
26 |
>>> |
27 |
>>> Further, the config option won't be available unless all of the things |
28 |
>>> _it_ uses are enabled. So, if this config option X isn't available |
29 |
>>> because it needs config option Y, you need config option Y, because |
30 |
>>> you need config option X, because you need udisks, because you need |
31 |
>>> something which needs udisks. |
32 |
>>> |
33 |
>>> So if some option X says "don't enable this unless you need it", and |
34 |
>>> you need some option Z, which says it needs option X, then, yes, you |
35 |
>>> need option X, because you need option Z. |
36 |
>>> |
37 |
>>> This is what Volker meant when he said that there was no 'unsure' at |
38 |
>>> play. Since you're sure you want udisk (because you installed it), |
39 |
>>> then, logically following, you're sure you want whatever udisk depends |
40 |
>>> on. (Either that, or you're not being logical. ^^ ) |
41 |
>>> |
42 |
>> |
43 |
>> But, I was still unsure. If it wants me to enable the option for |
44 |
>> battery monitoring, do I do that too? I don't have any batteries but it |
45 |
>> wants the option enabled so to use your logic, I must need it because it |
46 |
>> asks for it even tho I don't use it and can't use it. |
47 |
> When it comes to software, even if you don't actively use a thing, you |
48 |
> may depend on it being there. The reasons involved could come from any |
49 |
> of dozens of programming issues you may be unaware of or uncaring of; |
50 |
> it could come from the need of a programmer to simplify his reasoning |
51 |
> about a system in order to simplify his code (or the problem his code |
52 |
> is trying to solve). It could come from some automatic linking process |
53 |
> that looks for a symbol even if the function that symbol represents is |
54 |
> never called in practice. It could come from some indirect artifact of |
55 |
> the thing being there. |
56 |
> |
57 |
> You're trying to apply a holistic reasoning basis to a deterministic |
58 |
> dependency problem. That kind of logic is the same kind of logic that |
59 |
> leads to stories such as "but why won't you plug in your computer?" |
60 |
> "because it makes a lot of noise. Why won't my computer work?" |
61 |
> "Because it needs power, so you need to plug it in." "But it makes a |
62 |
> lot of noise." |
63 |
> |
64 |
> Apologies for the crass analogy, but it really is the same thing, just |
65 |
> at a different technical depth. |
66 |
> |
67 |
|
68 |
But as I said, the package did compile without it. Since it did compile |
69 |
without it, it was not a hard, must have, requirement. If the package |
70 |
would have failed to compile, then I would either have to get rid of the |
71 |
package or enable the option. The message said it should have the |
72 |
option just like one should give the computer power. Thing is, my |
73 |
system was working just fine without the option before. Heck, I still |
74 |
may not really need the option. The software would just like to have |
75 |
it. I may even be able to get rid of the software which would be the |
76 |
next thing if I didn't choose to enable the kernel option. I'm pretty |
77 |
sure it is KDE that is pulling all this extra stuff in. |
78 |
|
79 |
Now that I know more about the option, I added it. Maybe when I reboot |
80 |
it will be happy. ;-) |
81 |
|
82 |
Dale |
83 |
|
84 |
:-) :-) |
85 |
|
86 |
-- |
87 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |