Arch-releng January 2010

arch-releng@lists.archlinux.org

1 participants
2 discussions

[arch-releng] [PATCH] Fix grub lines for various encryption setups
by Thomas Bächler 06 Mar '10

06 Mar '10

The first one used a deprecated syntax and failed whenever / was not called /dev/mapper/root The second one got a cosmetical cleanup to be more consistent with what was set during the installer The third one also failed whenever / was not called /dev/mapper/root --- src/core/libs/lib-ui-interactive.sh | 9 +++++---- 1 files changed, 5 insertions(+), 4 deletions(-) diff --git a/src/core/libs/lib-ui-interactive.sh b/src/core/libs/lib-ui-interactive.sh index 586abc9..d9f8795 100644 --- a/src/core/libs/lib-ui-interactive.sh +++ b/src/core/libs/lib-ui-interactive.sh @@ -1089,20 +1089,21 @@ generate_grub_menulst() { then debug 'FS' 'Grub kernel line? Found / on dm_crypt on raw' raw_device=`echo "$ANSWER_DEVICES" | sed -n '2p' | cut -d ' ' -f1` - kernel="kernel $subdir/vmlinuz26 root=$raw_device ro" + crypt_device=`echo "$ANSWER_DEVICES" | sed -n '1p' | cut -d ' ' -f1` + kernel="kernel $subdir/vmlinuz26 root=$crypt_device cryptdevice=$raw_device:`basename $crypt_device` ro" elif echo "$ANSWER_DEVICES" | sed -n '1p' | grep -q 'lvm-lv$' && echo "$ANSWER_DEVICES" | sed -n '4p' | grep -q 'dm_crypt$' && echo "$ANSWER_DEVICES" | sed -n '5p' | grep -q 'raw$' then debug 'FS' 'Grub kernel line? Found / on lvm on dm_crypt on raw' lv_device=`echo "$ANSWER_DEVICES" | sed -n '1p' | cut -d ' ' -f1` - vg_device=`echo "$ANSWER_DEVICES" | sed -n '2p' | cut -d ' ' -f1` + crypt_device=`echo "$ANSWER_DEVICES" | sed -n '4p' | cut -d ' ' -f1` raw_device=`echo "$ANSWER_DEVICES" | sed -n '5p' | cut -d ' ' -f1` - kernel="kernel $subdir/vmlinuz26 root=$lv_device cryptdevice=$raw_device:`basename $vg_device` ro" + kernel="kernel $subdir/vmlinuz26 root=$lv_device cryptdevice=$raw_device:`basename $crypt_device` ro" elif echo "$ANSWER_DEVICES" | sed -n '1p' | grep -q 'dm_crypt$' && echo "$ANSWER_DEVICES" | sed -n '2p' | grep -q 'lvm-lv$' && echo "$ANSWER_DEVICES" | sed -n '5p' | grep -q 'raw$' then debug 'FS' 'Grub kernel line? Found / on dm_crypt on lvm on raw' crypt_device=`echo "$ANSWER_DEVICES" | sed -n '1p' | cut -d ' ' -f1` lv_device=`echo "$ANSWER_DEVICES" | sed -n '2p' | cut -d ' ' -f1` - kernel=" kernel $subdir/vmlinuz26 root=$crypt_device cryptdevice=$lv_device:root ro" + kernel=" kernel $subdir/vmlinuz26 root=$crypt_device cryptdevice=$lv_device:`basename $crypt_device` ro" elif echo "$ANSWER_DEVICES" | sed -n '1p' | grep -q 'raw$' then debug 'FS' 'Grub kernel line? Found / on raw' -- 1.6.4.1

2 1

Re: [arch-releng] [arch-dev-public] LTS install ISOs (was: makechrootpkg without aufs2)
by Dieter Plaetinck 24 Jan '10

24 Jan '10

On Sun, 24 Jan 2010 13:07:28 +0200 Ionut Biru <biru.ionut(a)gmail.com> wrote: > On 01/24/2010 09:55 AM, Aaron Griffin wrote: > > Hmmm. LTS install ISOs is an interesting idea, but not sure how > > people feel about that. I mean, the kernel for the install ISO is > > just the running kernel. You can still install the LTS kernel from > > a non-LTS ISO. > > > > Does anyone have a strong opinion on this? > > i don't see any reason to have that. > what's the purpose of the LTS kernel again? it's basically to make kernel update cycles of your system longer, right? so instead of getting a new major version every 3 months, you jump from LTS to LTS. I can see why some people want that on their installed box [and hence the possibility to install it using any installation medium]. our goal with the installation media (we're failing at that goal right now), is to have a set of media for each new kernel release. why? optimal hardware support. so the question is simple: do LTS kernels get driver updates like the normal kernels do? but even if they do, they probably run behind on filesystems support and such. so i do not see any advantages for installation media running an LTS kernel. Dieter

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Arch-releng January 2010