ArchThis Forum is for the discussion of Arch Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
which CD are you using? 0.7? did you make the update? do you have the new initscripts installed?
it is not a solution but i would recommend hwdetect. hotplug is getting deprecated in Arch and the new hardware detection tool looks quite nice - i don't use it.
if you have the possibility, through other distro in your setup, make the download of the necessary things: hwdetect, initscripts and the latest kernel and take hotplug out of your daemons list in rc.conf.
My point being you did a sysupgrade and didn't even know that some config file(s) potentially were updated - or not because you had them set to NoUpgrade.
You apparently didn't even know you had them excluded.
And yes, it *is* covered in the manpage.
This is a significant exposure - obviously some people are going to get caught.
I know that config files get updated during upgrades, syg00. I have known it for a long time now since I installed Debian. Only difference is that with Debian I hardly had to do any work myself because it handled the upgrades seamlessly.
You assume too much and you have such a superior attitude.
What I wasn't aware was that the kernel got updated.
Most OSes don't update the kernel by default. I got caught I admit, but the reason was the kernel update. Not the config file. Arch did update the kernel and I should have known better.
Leave it well alone. My problem has been solved... I know that you guys have better knowledge than me but I really don't want to prove any points here.