2012/7/22 Uli Armbruster <uli.armbruster@xxxxxxxxxxxxxx>: [...] > > In the first moment when seeing those changes I had the same feeling. But after taking some time thinking > about it, I changed my mind. Here's why: So :) > > - The rc.conf used to be the center of all config files. But this has been changing for quite some time. For >example, preventing modules from being loaded could be done in the rc.conf's MODULES line by putting a ! in I remember this time. >front. Before this, there was an extra line for modules which should not be loaded. This functionality was >removed quite some time ago and nobody really complained. Of course it was much simpler back then, but >it's still doable today. Using /etc/modprobe.d/ to manage modules is less simple than using a ! in front of a blacklisted module. And blacklisting modules is done once or twice a year. > - Many variables in the rc.conf are only touched once in the livetime of an installation. E.g. HOSTNAME, who >ever changes that? So you only have to deal with it once, so it's not a big loss, if this isn't configured in the >rc.conf anymore. It won't hurt to let it in /etc/rc.conf either. > - _THE_ killer argument for Archlinux is and stays the AUR combined with pacman's capabilities. And >pacman improved a LOT over the last months, not just because of signed packages, also e.g. that -U can >resolve dependencies etc. Well, since my first installation of arch back in end of 2008, pacman is far better :) > - Arch's own init system is still supported and right now I don't see any signs that this will change. So just >adjust your rc.conf or keep it (it still works), but nothing really changes for you. It won't be the same for new users or if you change your hardware. I change my hardware fully every 3 years or so. And to be honest, I reinstall my arch every 18 to 24 months because it is kinda dirty. > > Those are my $0.02 If it work, don't try to fix it :D -- Frederic Bezies fredbezies@xxxxxxxxx
