X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail-vc0-f179.google.com (mail-vc0-f179.google.com [209.85.220.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id B54F2DC011F for ; Tue, 26 Feb 2013 08:51:30 +0000 (UTC) Received: by mail-vc0-f179.google.com with SMTP id k1so1358793vck.24 for ; Tue, 26 Feb 2013 00:51:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=wXfVtzTVmGKQrXf7UmvVm1ItjGvsuZxjwrMr9sMHbQM=; b=ksrPDiXEQjFeILGGsCJgZD6v+Vrk89MBahBJARx00A5ftegmJFi42nx738o1XZA29i A8tf2/cDpDUU0getwf1YfGcFvA408bW2iP1NXRtHyGQvAUCIdT0g8M8Sc2ckx+/wGwpy lEsz6GM07MepUzRlusB4zdhu2leOtO6vWzcLka7/dBewWqgSiQL6+NzuDjDsUwaou8Cn 6kfR+oYsP53Csv//2ZiwX+Ikcx5iYyecQauZhQ569908xVP+K7HkmHcne7JsTHrHB+tX GRo6sUoSPdCmnKQaypnTKlLesTVndiwbyS5OUrY8ZmMGzLhxxOrGbPz6PqSLL0SaDmT6 j34g== X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 X-Received: by 10.220.226.70 with SMTP id iv6mr11307232vcb.9.1361868689656; Tue, 26 Feb 2013 00:51:29 -0800 (PST) Received: by 10.58.106.114 with HTTP; Tue, 26 Feb 2013 00:51:29 -0800 (PST) Date: Tue, 26 Feb 2013 12:51:29 +0400 Message-ID: Subject: [alpine-devel] mkinitfs initramfs-init questions From: =?UTF-8?B?0JXQstCz0LXQvdC40LkgJ1J1c2gnINCd0LXQv9C+0LzQvdGP0YnQuNC5?= To: alpine-devel@lists.alpinelinux.org Content-Type: text/plain; charset=UTF-8 There are some magic when parsing kernel command line (at the end of message): 1. Which reason for doing sed 's: :_:g' ? What command line will be affected this for example? 2. Syslinux (5.x) pass kernel path as the first arg (twice in my case). This code run with errors "/init: eval: line 1: KOPT_/boot/datacom=yes: not found". This a bug or feature? 3. I've passed console=tty0 console=ttyS1,115200 for my Ubuntu kernels on Dell servers with IPMI SOL to see kernel output both on IP KVM and IPMI SOL (because not everywhere I have both). I think tty0 must not be placed in inittab, because it is "current console". Seems like a bug? 4. Code looks overcomplicated because there are a) not many options to be parsed by initramfs-init b) not all kernel options must be parsed by initramfs-init, unknown options must be skipped (and errors as in #2 will not be raised in the future) 8<------------------------------------------------------------------------------------------->8 # read the kernel options. We use eval set so we can handle things like # acpi_osi="!Windows 2006" eval set -- `cat /proc/cmdline` while [ $# -gt 0 ]; do case "$1" in s|single|1) SINGLEMODE=yes ;; console=*) CONSOLE="$CONSOLE ${1#console=}";; *=*) eval "KOPT_${1%%=*}='${1#*=}'" ;; no*) eval "KOPT_$(echo ${1#no} | sed 's: :_:g')=no" ;; *) eval "KOPT_$(echo $1 | sed 's: :_:g')=yes" ;; esac shift done 8<------------------------------------------------------------------------------------------->8 / # cat /proc/cmdline /boot/datacom /boot/datacom initrd=/boot/datacom.gz alpine_dev=usbdisk:vfat modules=loop,squashfs,sd-mod,usb-storage nomodeset console=tty0 console=ttyS1,115200 -- Cogito ergo sum --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---