You'll get those mail messages added every time you update the aaa_base package. it's nothing to worry about. just clean them out after an update.
|
Quote:
|
Quote:
In my humble opinion it would be less confusing to remove the parameter from the "mkinitrd" command. |
For the curious...
Just did a clean install on a Dell Latitude E6400 (you can find full specs online).
Code:
# lspci I gotta say, so far I am tickled pink. I might even switch back to KDE (for the 1st time since 3.5.10). The BCM4322 chip is working too (but still no 802.11n): I fixed up the SBo scripts (filenames and locations) for the newer firmware and fw-cutter from from here: http://www.lwfinger.com/b43-firmware...163.46.tar.bz2 http://bues.ch/b43/fwcutter/b43-fwcutter-018.tar.bz2 and am posting this via my home wifi. When KDE fires up it reports a "bad battery" with only 38% capacity. Given that I never got more than 2-3 hrs on this heap I find that curious as WinXP (is a corporate laptop I am forced to use) doesn't see this. Maybe related to this syslog entry? Code:
Oct 19 14:19:36 sauron kernel: [ 6.446244] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared |
Quote:
|
Quote:
In 14.1 rc the restrictive build is broken for me I reply For me it does compile and it does limited functions then will Segmentation fault on some codecs. the same one compiled in the 14.0 environment used in the 14.1 rc does fine . So I will start a new thread in the future on the kdenlive because the newest one coming out the kdenlive 1.0 is going to be very different from what we been seeing. This is the ffmpeg 1.2 that I been compiling with my builds and also with Alien Bob build 14.0. The Alien Bob 14.0 build works fine in 14.1 rc but that is built in the 14.0 environment. thanks for all the feed back you slackers are the best. Tested with this NVIDIA-Linux-x86_64-331.13-beta in 14.1 rc with 14.0 restrictive build, built in 14.0 ffmpeg 1.2. |
Quote:
|
On reflection (and a bit of searching of LQ to find my previous posts on this subject) what I was almost but not entirely remembering above is that you end up having problems if you use an encrypted rootfs and pass the luks mapping name with the old style "mkinitrd -r cryptroot", or even root=/dev/mapper/cryptroot from lilo.conf
In lilo.conf you can't put root=cryptroot (it will throw out an error), but if you specify root=/dev/mapper/cryptroot in lilo.conf (as suggested in README_CRYPT.TXT) then that would override the -r cryptroot passed to the initrd and when you get to the following section of code in the initrd's init file you end up with an incorrect assignment. Code:
if /sbin/cryptsetup isLuks ${LUKSDEV} 1>/dev/null 2>/dev/null ; then I'm not certain but I've gotten the idea in my head that before the version bump of lilo it didn't used to pass root= to the kernel if an initrd was used, and this is why this latent problem hasn't hit us until now. In short, If you're using an encrypted rootfs and if your bootloader passes the root= to the initrd via the kernel args then you better be using the luksnnnn names (e.g. root=/dev/mapper/lukssda1) or you're going to hit a problem. If you're using the old style 'cryptroot' name, then don't pass the root= argument from your bootloader. Anyway, that's what I was trying to remember when I posted above. P.S. On first thought, there's a temptation to do a quick and dirty fix like this: Code:
diff -Nurp mkinitrd.orig/init mkinitrd/init Probably better just to get everyone to use the luksnnnn names and leave the old cryptroot stuff to rot. Those who insist on doing it the old way will just have to learn not to put root= in their bootloaders. ;) Quote:
|
follow-up:
I think this would safely fix the case of "mkinitrd -r cryptroot" and root=/dev/mapper/cryptroot Code:
diff -Nurp mkinitrd.orig/init mkinitrd/init |
Quote:
I haven't used KDE since version 3.2. I am impressed. I am now updating a system from KDE-4.5.5/GNOME-2.32 to current. clean-system was lengthy install-new was giant I am still waiting on upgrade-all |
a new gcc! :cool:
Code:
Mon Oct 21 07:30:10 UTC 2013 |
Quote:
|
All times are GMT -5. The time now is 11:06 PM. |