Re: Sarge to Etch upgrade report
"A. F. Cano" <afc@shibaya.lonestar.org> wrote:
> For the longest time, I had been annoyed that shells in a konsole did
> not execute startup files. The last time this worked was in woody.
Don't know about konsole, but other xterm's I tried have an option
called 'login shell'.
[snip]
> [...] I
> noticed though that the .bashrc user files were not touched or even
> apparently known to the upgrade scripts. From another from-scratch
> installation, I realized that the .bashrc that gets installed in a
> new user's directory is much more involved than what came with
> sarge. Should this be reported as a bug?
This is a feature (policy to be more accurate), not a bug. Imagine a
system with lots of users and many customized .*rc files... Of course,
a new install will put the default version of the file.
One way to handle this is to move /home to /home.old, let the packages
install whatever they want and compare the files. In the case of bash
the relevant files are copies of /etc/skel/.bash*
[snip]
> Where in Etch should I add the blacklisted modules so that only the
> snd-cs4231 (which I've added to /etc/modules) is loaded?
>
> Since this is a built-in device, not removable, I presume udev doesn't
> apply, but in /etc/modprobe.d there are 2 files alsa-base-blacklist
> and blacklist.
There are more ways to do it, but I prefer creating a
file /etc/modprobe.d/00local with all my customizations. This has the
benefit of preserving your settings across upgrades.
> Well, overall, no major problems. I'm happy with the way the upgrade
> turned out. Kudos to the developers!!!
:)
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
Reply to: