Arch-projects May 2011

arch-projects@lists.archlinux.org

22 participants
61 discussions

[arch-projects] [initscripts] [GIT] Arch Linux initscripts repository branch master updated. 2011.04.1-27-gb329364
by tomegun＠archlinux.org 07 May '11

07 May '11

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Arch Linux initscripts repository". The branch, master has been updated via b329364663801e609a56f2f6a19d53bf5c754873 (commit) via bf329c43dc671746e23c1760f9a674c58898aebb (commit) via d8796827633d533e53ba7e158ee6354c38d0e88e (commit) from e98a352e9568ec31b33af8671987d026f1f73647 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit b329364663801e609a56f2f6a19d53bf5c754873 Author: Tom Gundersen <teg(a)jklm.no> Date: Fri May 6 21:37:50 2011 +0200 Revert "udev: do not automatically save persistent net/cd udev rules to /etc on boot" This fixes FS#24115. The persistent net/cd rules will go away soon, but no replacement is in place yet, so we reinstate the copying magic. This partially reverts commit e9b658239f45d858ff7b30b46441b8733d20f151. Signed-off-by: Tom Gundersen <teg(a)jklm.no> commit bf329c43dc671746e23c1760f9a674c58898aebb Author: Tom Gundersen <teg(a)jklm.no> Date: Tue May 3 21:09:07 2011 +0200 workaround: symlink /var/run/daemons -> /run/daemons Some initscripts check the folder /var/run/daemons to see if another daemon is running. They should not do this as this folder is supposed to be internal to initscripts, and use ck_daemon instead. However, we add this workaround to minimize the pain. Should be removed one day. Signed-off-by: Tom Gundersen <teg(a)jklm.no> commit d8796827633d533e53ba7e158ee6354c38d0e88e Author: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> Date: Sat Apr 30 16:52:40 2011 -0300 Change stat_busy()/stat_done() -> status() Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> Signed-off-by: Tom Gundersen <teg(a)jklm.no> ----------------------------------------------------------------------- Summary of changes: rc.shutdown | 17 +++++------------ rc.single | 5 +---- rc.sysinit | 14 ++++++++++++-- 3 files changed, 18 insertions(+), 18 deletions(-) hooks/post-receive -- Arch Linux initscripts repository

1 0

[arch-projects] [initscripts] background color in /sbin/rc
by Kwpolska 07 May '11

07 May '11

(a reprint of FS#24074) > The initscripts' /etc/rc.d/functions uses colors with a black > background. It does not look very nice on a transparent black > terminal. A patch is included. tomegun requested a git patch to be sent here. It's in the attachments section. -- Cheers, -- Kwpolska (http://kwpolska.co.cc) O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

4 8

[arch-projects] [initscripts] /sbin/rc conflicts with plan9 package
by Tom Gundersen 04 May '11

04 May '11

Hi all, I missed this conflict when I merged our new rc script: <https://bugs.archlinux.org/task/24082>. The two packages in question are in [community]. I cannot see the conflict with extra/cmus, so I dont know what that is about. Does anyone have any suggestions on how to solve this? We could rename our script, or we could as plan9 packager to rename his I guess... Cheers, Tom

5 7

Re: [arch-projects] [arch-announce] initscripts update
by Gerardo Exequiel Pozzi 03 May '11

03 May '11

On 05/02/2011 04:01 PM, Arch Linux: Recent news updates: Tom Gundersen wrote: > * The adjustment of the hwclock for drift is moved into a daemon that should > not be used in most scenarios as it can lead to subtle bugs (especially if using > dual-boot or ntp). If you know what you are doing and want to adjust the > hardware clock for drift, add `"hwclock"` to your `DAEMONS` array. Question: Why this is already added by default to the daemons? Thanks for the work :) -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

2 1

Re: [arch-projects] [RFC3][PATCH] [mkinitcpio] Cleanly stop udev >= 168 as recommended by upstream.
by Gerardo Exequiel Pozzi 03 May '11

03 May '11

On 05/02/2011 01:09 PM, Dave Reisner wrote: > On Mon, May 02, 2011 at 12:28:41PM -0300, Gerardo Exequiel Pozzi wrote: >> On 05/02/2011 11:23 AM, Thomas Bächler wrote: >>> Am 02.05.2011 16:00, schrieb Gerardo Exequiel Pozzi: >>>> N0: device-mapper/LVM udev rules must be parsed for initramfs creation >>>> to add OPTIONS+="db_persist" >>> Patch looks good now. >> Great! >>> I am unsure and confused why we would need this db_persist option. In >>> the past, we killed udev and the db completely and everything worked out >>> fine. What kind of state would need to be persistent? Is upstream adding >>> this option? > We've never killed the DB on leaving early userspace because the DB > previously lived in /dev/.udev. Yes, see above. > We did a mount --move of /dev to > /new_root/dev and continued on our merry way. Nothing different with the > DB in /run/udev. We transfer that tmpfs over to the root and everything > is preserved. > Yes. >> Yes, that is what I not understand, If I am not wrong this was >> before devtmpfs times. > Not sure where devtmpfs comes into play. This is all created by udevd in > userland regardless of the filesystem /dev is mounted on. > In old times (about one year ago), "/proc" "/sys" was discarded from initramfs [#1]. Also no separate "/dev" exist at initramfs [#2] stage, so all "udev DB" was discarded at all. [#1] http://projects.archlinux.org/mkinitcpio.git/commit/init?id=64c0a72e9fc0a83… [#2] http://projects.archlinux.org/mkinitcpio.git/commit/init?id=3bb6c683094490e… >> Maybe this is needed in case if rules on initramfs differs from real >> root. Dave can you ask to Kay on IRC about this? (I am going to my >> work now) Thanks. >> > Seems to me like lvm2 is just a pain in the ass for udev all around. In > systemd, it's the only reason that a call to udevadm settle is required > during late bootup. Everything else can be handled as hotplug events as > they come up. > > Snippets from Kay... > > 11:52 kay » falconindy: only if you use --db-cleanup, and yes lvm > plays dirty tricks with udev and needs the db preserved > 11:54 kay » falconindy: they need to catch up with 2011 a bit though > and stop scanning /dev, or have crazy regexes in their > config files > 11:58 kay » falconindy: in the past we used to rm -rf /dev/.udev > in the real root > 11:59 falconindy » which i assume is a more of a sledgehammer approach > to what the cleanup does > 12:00 kay » falconindy: not that different, the db_persist just > adds a sticky bit to the db file > > So LVM is just a pain in the butt all around. State can be wiped for all > other devices and the rebuilt DB in later userspace doesn't contain > failed/unhandled events from the initramfs. > > dave > > Thanks. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

2 1

[arch-projects] [RFC] [PATCH] [mkinitcpio] Cleanly stop udev >= 168 as recommended by upstream.
by Gerardo Exequiel Pozzi 03 May '11

03 May '11

N0: udev >= 168 is needed. N1: I guess the order is correct (first cleanup then exit). N2: device-mapper/LVM udev rules must be parsed for initramfs creation to add OPTIONS+="db_persist" >From udev NEWS: The running udev daemon can now cleanly shut down with: udevadm control --exit Udev in initramfs should clean the state of the udev database with: udevadm info --cleanup-db which will remove all state left behind from events/rules in initramfs. If initramfs uses --cleanup-db and device-mapper/LVM, the rules in initramfs need to add OPTIONS+="db_persist" for all dm devices. This will prevent removal of the udev database for these devices. Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- init | 12 ++++-------- 1 files changed, 4 insertions(+), 8 deletions(-) diff --git a/init b/init index 7b81a1a..f586220 100644 --- a/init +++ b/init @@ -118,15 +118,11 @@ elif [ ! -x "/new_root${init}" ]; then launch_interactive_shell --exec fi -#Special handling if udev is running -udevpid=$(/bin/pidof udevd) -if [ -n "${udevpid}" ]; then - # Settle pending uevents, then kill udev +# Stop udevd if is running +if [ "${udevd_running}" -eq 1 ]; then /sbin/udevadm settle - /bin/kill ${udevpid} > /dev/null 2>&1 - while /bin/pidof udevd >/dev/null; do - sleep 0.1 - done + /sbin/udevadm info --cleanup-db + /sbin/udevadm control --exit fi for d in proc sys dev run; do -- 1.7.5

3 11

[arch-projects] [RFC] [PATCH] [initscripts] chmod dmesg.log based on value from dmesg_restrict
by Gerardo Exequiel Pozzi 03 May '11

03 May '11

Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- rc.sysinit | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/rc.sysinit b/rc.sysinit index e07afe6..55b3d53 100755 --- a/rc.sysinit +++ b/rc.sysinit @@ -371,6 +371,13 @@ fi # Set console font if required set_consolefont +if [[ -e /proc/sys/kernel/dmesg_restrict && $(< /proc/sys/kernel/dmesg_restrict) -eq 1 ]]; then + : >| /var/log/dmesg.log + chmod 600 /var/log/dmesg.log +else + : >| /var/log/dmesg.log + chmod 644 /var/log/dmesg.log +fi /bin/dmesg >| /var/log/dmesg.log run_hook sysinit_end -- 1.7.5

1 0

[arch-projects] Fwd: Re: [RFC3][PATCH] [mkinitcpio] Cleanly stop udev >= 168 as recommended by upstream.
by Dave Reisner 02 May '11

02 May '11

----- Forwarded message from Dave Reisner <d(a)falconindy.com> ----- > Date: Mon, 2 May 2011 12:09:54 -0400 > From: Dave Reisner <d(a)falconindy.com> > To: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> > Subject: Re: [arch-projects] [RFC3][PATCH] [mkinitcpio] Cleanly stop udev >= 168 as > recommended by upstream. > > On Mon, May 02, 2011 at 12:28:41PM -0300, Gerardo Exequiel Pozzi wrote: > > On 05/02/2011 11:23 AM, Thomas Bächler wrote: > > >Am 02.05.2011 16:00, schrieb Gerardo Exequiel Pozzi: > > >>N0: device-mapper/LVM udev rules must be parsed for initramfs creation > > >> to add OPTIONS+="db_persist" > > >Patch looks good now. > > Great! > > >I am unsure and confused why we would need this db_persist option. In > > >the past, we killed udev and the db completely and everything worked out > > >fine. What kind of state would need to be persistent? Is upstream adding > > >this option? > > We've never killed the DB on leaving early userspace because the DB > previously lived in /dev/.udev. We did a mount --move of /dev to > /new_root/dev and continued on our merry way. Nothing different with the > DB in /run/udev. We transfer that tmpfs over to the root and everything > is preserved. > > > Yes, that is what I not understand, If I am not wrong this was > > before devtmpfs times. > > Not sure where devtmpfs comes into play. This is all created by udevd in > userland regardless of the filesystem /dev is mounted on. > > > Maybe this is needed in case if rules on initramfs differs from real > > root. Dave can you ask to Kay on IRC about this? (I am going to my > > work now) Thanks. > > > > Seems to me like lvm2 is just a pain in the ass for udev all around. In > systemd, it's the only reason that a call to udevadm settle is required > during late bootup. Everything else can be handled as hotplug events as > they come up. > > Snippets from Kay... > > 11:52 kay » falconindy: only if you use --db-cleanup, and yes lvm > plays dirty tricks with udev and needs the db preserved > 11:54 kay » falconindy: they need to catch up with 2011 a bit though > and stop scanning /dev, or have crazy regexes in their > config files > 11:58 kay » falconindy: in the past we used to rm -rf /dev/.udev > in the real root > 11:59 falconindy » which i assume is a more of a sledgehammer approach > to what the cleanup does > 12:00 kay » falconindy: not that different, the db_persist just > adds a sticky bit to the db file > > So LVM is just a pain in the butt all around. State can be wiped for all > other devices and the rebuilt DB in later userspace doesn't contain > failed/unhandled events from the initramfs. > > dave > ----- End forwarded message ----- And i replied to Gerardo by mistake instead of the list... d

1 0

[arch-projects] [RFC3][PATCH] [mkinitcpio] Cleanly stop udev >= 168 as recommended by upstream.
by Gerardo Exequiel Pozzi 02 May '11

02 May '11

N0: device-mapper/LVM udev rules must be parsed for initramfs creation to add OPTIONS+="db_persist" >From udev NEWS: The running udev daemon can now cleanly shut down with: udevadm control --exit Udev in initramfs should clean the state of the udev database with: udevadm info --cleanup-db which will remove all state left behind from events/rules in initramfs. If initramfs uses --cleanup-db and device-mapper/LVM, the rules in initramfs need to add OPTIONS+="db_persist" for all dm devices. This will prevent removal of the udev database for these devices. Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- init | 13 ++++--------- 1 files changed, 4 insertions(+), 9 deletions(-) diff --git a/init b/init index 7b81a1a..1173998 100644 --- a/init +++ b/init @@ -118,15 +118,10 @@ elif [ ! -x "/new_root${init}" ]; then launch_interactive_shell --exec fi -#Special handling if udev is running -udevpid=$(/bin/pidof udevd) -if [ -n "${udevpid}" ]; then - # Settle pending uevents, then kill udev - /sbin/udevadm settle - /bin/kill ${udevpid} > /dev/null 2>&1 - while /bin/pidof udevd >/dev/null; do - sleep 0.1 - done +# Stop udevd if is running +if [ "${udevd_running}" -eq 1 ]; then + /sbin/udevadm control --exit + /sbin/udevadm info --cleanup-db fi for d in proc sys dev run; do -- 1.7.5

2 2

[arch-projects] [PATCH] [RFC][mkinitcpio] Cleanly stop udev >= 168 as recommended by upstream.
by Gerardo Exequiel Pozzi 02 May '11

02 May '11

N0: udev >= 168 is needed. N1: I guess the order is correct (first cleanup then exit). N2: device-mapper/LVM udev rules must be parsed for initramfs creation to add OPTIONS+="db_persist" >From udev NEWS: The running udev daemon can now cleanly shut down with: udevadm control --exit Udev in initramfs should clean the state of the udev database with: udevadm info --cleanup-db which will remove all state left behind from events/rules in initramfs. If initramfs uses --cleanup-db and device-mapper/LVM, the rules in initramfs need to add OPTIONS+="db_persist" for all dm devices. This will prevent removal of the udev database for these devices. Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- init | 13 ++++--------- 1 files changed, 4 insertions(+), 9 deletions(-) diff --git a/init b/init index 7b81a1a..a2c6c8a 100644 --- a/init +++ b/init @@ -118,15 +118,10 @@ elif [ ! -x "/new_root${init}" ]; then launch_interactive_shell --exec fi -#Special handling if udev is running -udevpid=$(/bin/pidof udevd) -if [ -n "${udevpid}" ]; then - # Settle pending uevents, then kill udev - /sbin/udevadm settle - /bin/kill ${udevpid} > /dev/null 2>&1 - while /bin/pidof udevd >/dev/null; do - sleep 0.1 - done +# Stop udevd if is running +if [ "${udevd_running}" -eq 1 ]; then + /sbin/udevadm info --cleanup-db + /sbin/udevadm control --exit fi for d in proc sys dev run; do -- 1.7.5

4 6

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Arch-projects May 2011