ArchThis Forum is for the discussion of Arch Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Here's my menu.lst from Debian which I actually use to boot Arch (I didn't install GRUB from Arch. Used the Debian one which is already present)
Code:
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/hdb3.
title Arch Linux 0.7
root (hd1,2)
kernel /boot/vmlinuz26 root=/dev/hdb3
savedefault
boot
hi there,
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.
regards,
slackie1000
You can use hwd if hotplug still gives you troubles. When upgrading, conf files can be created, so make sure everytime you do it, check if new conf files were made.
Originally posted by Harishankar
I just had to copy the newer rc.conf file and put it in place of the old one and make the older changes manually and *poof* it worked.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.