Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

LPI Exam 101-500 Topic 1 Question 101 Discussion

Actual exam question for LPI's 101-500 exam
Question #: 101
Topic #: 1
[All 101-500 Questions]

A faulty kernel module is causing issues with a network interface card. Which of the following actions ensures that this module is not loaded automatically when the system boots?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Nina at Sep 15, 2024, 09:16 AM

Limited Time Offer

25%

Off

Get Premium 101-500 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Lorrine
3 months ago
Option A, huh? 'lsmod --remove --autoclean' without naming the module? Sounds like a great way to clean up your system... or accidentally nuke it. I'll pass on that one!
upvoted 0 times
Lasandra
2 months ago
Yeah, using modprobe to remove the module is a good approach too. Just be careful with the syntax.
upvoted 0 times
...
Virgina
2 months ago
I've used option C before and it worked fine for me. Just make sure you specify the name of the offending module.
upvoted 0 times
...
Keneth
2 months ago
I agree, it's a more controlled way to prevent the faulty module from loading automatically.
upvoted 0 times
...
Ashlee
2 months ago
I think option D is the safest bet. Adding the module to the blacklist seems like a good solution.
upvoted 0 times
...
...
Nelida
3 months ago
Hmm, Option B with modinfo seems a bit roundabout. I'd probably go for the simple blacklist route in Option D.
upvoted 0 times
Glenn
2 months ago
I think I'll go with Option D as well, thanks for the suggestion!
upvoted 0 times
...
Berry
3 months ago
Yeah, blacklisting the module is the easiest way to prevent it from loading.
upvoted 0 times
...
Heidy
3 months ago
I agree, Option D is the most straightforward solution.
upvoted 0 times
...
...
Samira
3 months ago
I'm not sure, but I think option C) Using modprobe --r followed by the name of the offending module could also work
upvoted 0 times
...
Roselle
4 months ago
Ooh, Option E sounds like an adventure! Recompiling the kernel, huh? That's a bold move, but I'm not sure I'm feeling that adventurous today.
upvoted 0 times
Cruz
3 months ago
A: Good idea, that seems like a safer option.
upvoted 0 times
...
Elvera
3 months ago
B: Yeah, I think I'll stick to adding a blacklist line in blacklist.conf.
upvoted 0 times
...
Delsie
3 months ago
A: I know, recompiling the kernel sounds intense.
upvoted 0 times
...
...
Reed
4 months ago
I agree with Cherilyn, adding the module to the blacklist is the best way to prevent it from loading automatically
upvoted 0 times
...
Paris
4 months ago
I'm leaning towards Option C. Using modprobe to remove the offending module seems like a more direct approach.
upvoted 0 times
Yuonne
3 months ago
That could work too, but modprobe seems quicker.
upvoted 0 times
...
Phil
3 months ago
But what about adding a blacklist line to blacklist.conf?
upvoted 0 times
...
Rasheeda
3 months ago
I agree, using modprobe is a direct way to remove the module.
upvoted 0 times
...
Natalie
3 months ago
I think Option C is the best choice.
upvoted 0 times
...
...
Cherilyn
4 months ago
I think the correct answer is D) Adding a blacklist line including the name of the offending module to the file /etc/modprobe.d/blacklist.conf
upvoted 0 times
...
Dahlia
4 months ago
Option D looks like the way to go. Blacklisting the pesky module in the modprobe.d config file sounds like a straightforward solution.
upvoted 0 times
Josue
3 months ago
Yeah, blacklisting the module in the config file should prevent it from loading automatically.
upvoted 0 times
...
Edmond
4 months ago
I agree, option D seems like the best choice.
upvoted 0 times
...
...

Save Cancel