June 2011 - Arch-projects - lists.archlinux.org

[arch-projects] [mkinitcpio][PATCH 0/10] Kill off gen_init_cpio
by Dave Reisner 06 Jun '11

06 Jun '11

It's like a disease... I can't stop myself... Here's an overview of what's happening: Patch 1 deprecates our unfortunately named 'install' function, and replaces it with 'build'. Patches 2 through 5 are cleanup and refactoring of the codebase in preparation for patch 6 which introduces a new method of doing the actual initcpio creation. As I explained a few days back, we can directly use a cpio tool to create images. I've opted to use bsdcpio, which imo, has some advantages over GNU cpio: 1) it's part of libarchive. libarchive is awesome. 2) because of #1, it's already in core. 3) it has a useful farking man page instead of saying "see the info page" So what's the downside? 1) We have to dump a whole bunch of stuff in /tmp. This is as little as 3-4Mb, but might be as much as 20mb. I will likely add an option to change the location of the tmpdir. 2) add_device goes away, as we can't use mknod as non-root. This was only ever referenced in the 'base' install hook, and as explained in patch 4, we can get around this. 3) add_symlink2 goes away. No idea why this exists. No one has ever used it. 4) the -a option to mkinitcpio goes away. I don't think anyone will miss this. Patches 7, 8, and 10 aren't very interesting. patch 9 introduces a new feature to allow specifying the kernel version as a path to a kernel image, rather than an absolute version. I think this is a great thing to have as it means we can simplify the way we do kernel PKGBUILDs. The kver file can go away, as the kernel "version" will only ever have to be updated when the filename of the image changes (as we may do fairly soon). As such, this is a good opportunity to implement such a feature. I've tested this on a few of my VMs which cover: encrypt, lvm, and raid/lvm. My GitHub tree also contains some changes to some of the previous patches I've sent, as I discovered a few bugs in the course of my testing. I'm rather excited about this, as it makes mkinitcpio a lot more pleasant to use. The SSD is extremely happy: $ time ./mkinitcpio -k /boot/vmlinuz26 -g foo.img :: Begin build :: Parsing hook [base] :: Parsing hook [udev] :: Parsing hook [autodetect] :: Parsing hook [pata] :: Parsing hook [scsi] :: Parsing hook [sata] :: Parsing hook [filesystems] :: Generating module dependencies :: Generating image 'foo.img' 6463 blocks :: Image generation successful real 0m0.731s user 0m0.440s sys 0m0.159s As always, comments, criticism, and tomatos welcome. d

2 21

Re: [arch-projects] hwclock adjust file
by Tom Gundersen 06 Jun '11

06 Jun '11

[cc'ing arch-projects and Kurt Bosch as they might have opinions] Context: I suggested to Dave that we should move /var/lib/hwclock/adjfile to /etc (which is what upstream does). Sorry for the verbosity, hwclock does this to me... On Sun, Jun 5, 2011 at 5:21 PM, Dave Reisner <d(a)falconindy.com> wrote: > Poked around at this, and apparently it's FHS that recommends putting > the adjtime file in /var/lib/hwclock, instead of /etc: > > http://www.pathname.com/fhs/2.2/fhs-5.8.html Hm, didn't know this. That said, I think we should (always) ignore FHS. > In poking around, I noticed various bugs related to a readonly root > which made writing to this file problematic. Fedora has gone back to > using /etc as well. > > Seems to me like /var/lib/hwclock is the appropriate place for it. I don't really have a "real" solution to this problem. It seems hwclock is really, really messed up. That said, maybe I'm missing the point. I'll explain the way I see it, and you tell me if i got it all wrong. Assumption: - We must never ever make system time go backwards. - We want to find the correct solution and push it upstream rather than work around it in Arch. UTC/LOCALTIME: When the rtc device is instantiated by the kernel the system time is set, assuming rtc is in UTC. If it is not, then we must reset the time to the correct timezone using "hwclock --systz" (we probably want to call this even if we are in UTC as it tells the kernel what timezone we are in for the benefit of fat filesystems (I know, wtf!?)). I believe already here we have a problem, as there is a gap between "system time not set" and "system time set correctly", where the time might be several hours in the future. We should at least make this gap as small as possible, and make sure that things like udev does not get started in this gap. This means that we must know very early whether we are in UTC or in LOCALTIME, storing this information in /var makes it impossible (so we work around it at the moment by having a redundant entry in rc.conf and essentially ignoring the timezone info of adjtime, and upstream work around it by having adjtime in /etc). Another option, that I have considered in the past is to add a module option to rtc-cmos, so you can simply do rtc-cmos.timezone=120 (for CEST) or rtc-cmos.timezone=0 for UTC. However, that's ugly, as I don't think it would be possible to pass it the real timezone, as that would require the kernel to keep a copy of /usr/share/zoneinfo, rather we'd have to pass the offset in minutes, and we would have to adjust this when DST kicks in. That said, maybe there is a nice way to do this that I'm not aware of, as I'm no kernel time/timezone expert. DRIFT This is the original purpose of adjtime, and I believe it belongs in /var (maybe this was the situation when FHS was written ;-) ). My understanding: The rtc runs at a relatively constant frequency, however this frequency is not very accurate. The system time on the other hand has frequency which is both constant and accurate. By measuring how the rtc and the system time drift, we are able to calculate the real frequency of the rtc, and adjusting for this we are able to get a very accurate time reading even when the system time has not been running (computer off or sleeping). This is useful if you want to keep a good time, but don't have a network connection, so cannot use ntp. To do this, we must be able to store somewhere the time when we last adjusted the rtc (so we know how long it has been drifting). If we want our system time to be adjust ed for drift at boot, we need to do "hwclock --adjust; hwclock --hctosys". The call to --adjust needs to save to a file what time it was done at (maybe this could be done with some /run magic, but I don't think it would be pretty, and it would at any rate require adjtime to be in /etc), and the call to --hctosys may only be done very early in boot (otherwise time might go backwards). I think the correct solution is to keep the drift information in /var, and only call "hwclock --adjust" (without the --hctosys) after the system is up and running (possibly just before shutdown/sleep), and never call "hwclock --systohc" automatically (this is only to be done when the system time is known to be correct, e.g. after setting the time). This means that the system time will be a bit wrong, but the errors will not accumulate (you are only off by the amount you drifted after the last clean shutdown, which in a non-networked scenario should be negligible, and a reboot will get you "perfect" time). Note: if ntpd/dual-boot is happening, the adjustment should never be done by hwclock, as we will not know the time since last --adjust, and we will over-shoot the adjustment. TL;DR: I propose splitting adjtime in two (upstream), one for /var (drift) and one for /etc (TZ), if this can be done in a clever way to not lose any backwards compatibility. Cheers, Tom PS If no one points out any mistakes in what I wrote, I might continue the work by Kurt Bosch, and simplify our hwclock handling further.

2 5

[arch-projects] [initscripts][PATCH] Clean up ANSI codes from /var/log/boot
by Eric Bélanger 06 Jun '11

06 Jun '11

Signed-off-by: Eric Bélanger <snowmaniscool(a)gmail.com> --- rc.multi | 2 ++ rc.single | 2 ++ 2 files changed, 4 insertions(+), 0 deletions(-) diff --git a/rc.multi b/rc.multi index 7af9279..9ebf483 100755 --- a/rc.multi +++ b/rc.multi @@ -30,6 +30,8 @@ if [[ -f /run/bootlogd.pid ]]; then /bin/touch /var/log/boot kill $(< /run/bootlogd.pid) /bin/rm -f /run/bootlogd.pid + sed -i -r -e 's/\^\[\[[0-9]?;?[0-9]?[0-9]?;?[0-9]?[0-9]?[ms]//g' \ + -e 's/\^\[(\[151|%)G//g' /var/log/boot fi # vim: set ts=2 sw=2 noet: diff --git a/rc.single b/rc.single index 91d346b..bb27ddf 100755 --- a/rc.single +++ b/rc.single @@ -54,6 +54,8 @@ if [[ -f /run/bootlogd.pid ]]; then touch /var/log/boot kill $(< /run/bootlogd.pid) rm -f /run/bootlogd.pid + sed -i -r -e 's/\^\[\[[0-9]?;?[0-9]?[0-9]?;?[0-9]?[0-9]?[ms]//g' \ + -e 's/\^\[(\[151|%)G//g' /var/log/boot fi # End of file -- 1.7.5.4

1 0

[arch-projects] [initscripts] [GIT] Arch Linux initscripts repository branch master updated. 2011.06.3-15-g3ac781f
by tomegun＠archlinux.org 06 Jun '11

06 Jun '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 3ac781f2f188b4e9c698aba7ede6154a64ffc679 (commit) via 36f31f686374ae3f2311f8674e0a91022d502576 (commit) via 2de44ef544862f3ce9144a16c5158ed771fec6de (commit) via 3b1d78bc524724ed49ac000d85f477876ccfc794 (commit) via 7a6fc752cf8dc09b9358810d947e6e01f9a8fc25 (commit) via 6e3ce6f9776d954091deba38ef3b45c4cf4a03db (commit) via 3e874cfd73e0cb70abd568c5b070ff85609af3a4 (commit) via 71ef9c40189ff87d84c7bf354fb43038997913d1 (commit) via c6adbe7a36a7330debfaa07d4351bcd80d479214 (commit) via 17f7e7483e46a68e2b4cea6cc76216b92370c5e3 (commit) from 0dfd69b9e8617ef15413e5022442017603be5344 (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 3ac781f2f188b4e9c698aba7ede6154a64ffc679 Merge: 36f31f6 7a6fc75 Author: Tom Gundersen <teg(a)jklm.no> Date: Mon Jun 6 02:27:39 2011 +0200 Merge remote-tracking branch 'djgera/djgera' Conflicts: rc.single rc.sysinit Mostly trivial conflicts with Dave's path purging Signed-off-by: Tom Gundersen <teg(a)jklm.no> commit 36f31f686374ae3f2311f8674e0a91022d502576 Author: Tom Gundersen <teg(a)jklm.no> Date: Mon Jun 6 02:06:34 2011 +0200 udev: remove rule generation This has been removed from the udev package, so this code would never be executed. Can finally be removed. Signed-off-by: Tom Gundersen <teg(a)jklm.no> commit 2de44ef544862f3ce9144a16c5158ed771fec6de Author: Tom Gundersen <teg(a)jklm.no> Date: Sun Jun 5 19:39:49 2011 +0200 hwclock: refactor daemon Before: adjust and set time on boot, adjust rtc every hour, and on shutdown. Now: do not set time on boot, adjust rtc on shutdown. Rationale: 1) We can never ever set the systemtime after system is up and running, as this might make time go backwards (unless we are careful à la ntpd, but we don't want to get into that business). 2) We are under the assumption that exact time is not needed, we are just trying to avoid large, accumulating drifts over time. With the new (significantly simpler) implementation systemtime will be off by the drift since the last clean shutdown. With the old implementation systemtime would be off by the drift since last shutdown (even if it was unclean). Either way the drifts would not accumulate, and a clean reboot would get you a "perfect" time. Signed-off-by: Tom Gundersen <teg(a)jklm.no> commit 3b1d78bc524724ed49ac000d85f477876ccfc794 Author: Tom Gundersen <teg(a)jklm.no> Date: Sun Jun 5 19:15:20 2011 +0200 hwclock: allow TZ to be set in adjtime, only adjust for TZ during boot This allows HARDWARECLOCK to be removed from rc.conf, if you want to rely on /var/lib/hwclock/adjtime (or wherever the file ends up in the future). It assumes the relevant path is on the rootfs. Furthermore, we can assume (since kernel2.6.??) that the rtc modules set the time from rtc themselves, so our job is just to adjust the tz. (FWIW, this coincides with what systemd does). To get the old behavior of not touching the rtc, set it to anything anything else. We should probably have chosen a syntax for this, like IGNORE. Maybe another time... Signed-off-by: Tom Gundersen <teg(a)jklm.no> commit 7a6fc752cf8dc09b9358810d947e6e01f9a8fc25 Author: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> Date: Mon May 9 12:39:32 2011 -0300 Be consistent (with mkinitcpio) source naming of /run Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> commit 6e3ce6f9776d954091deba38ef3b45c4cf4a03db Author: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> Date: Tue May 3 03:04:44 2011 -0300 [initscripts] chmod dmesg.log based on value from dmesg_restrict Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> commit 3e874cfd73e0cb70abd568c5b070ff85609af3a4 Author: Tom Gundersen <teg(a)jklm.no> Date: Sun Jun 5 02:29:40 2011 +0200 udev: don't silence settle + trivial If settle finishes too early, we want to know as some needed devices might not yet have been enumerated. Do not pass --quiet. Do not check for running udev before doing trigger/settle. Worst case, if someone does not have udev (which is not supported), they will see some extra status lines, but boot will still continue. Lastly, remove obvious comments (they were repeating the status message in the line below). Signed-off-by: Tom Gundersen <teg(a)jklm.no> commit 71ef9c40189ff87d84c7bf354fb43038997913d1 Author: Dave Reisner <d(a)falconindy.com> Date: Sat Jun 4 19:58:14 2011 -0400 remove absolute paths from daemons and rc.d These are run from a context where PATH will be set, so defining absolute paths is unnecessary. commit c6adbe7a36a7330debfaa07d4351bcd80d479214 Author: Dave Reisner <d(a)falconindy.com> Date: Sat Jun 4 19:55:36 2011 -0400 add PATH, strip absolute path from binaries Since we're declaring a PATH anyways, we may as well use it. This gives us immunity against binaries moving around, as in the recent case of iproute2. A few other minor, associated, tweaks to go along with this: * any -x tests are modified to use 'type -P' to resolve the path before checking for execute permission * any pidof checks are stripped of paths as well. commit 17f7e7483e46a68e2b4cea6cc76216b92370c5e3 Author: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> Date: Sat Jun 4 21:18:29 2011 -0300 [initscripts] Avoid error message when switch runlevels. Going from multi to single and going back to multi, bootlogd is not running. Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> ----------------------------------------------------------------------- Summary of changes: Makefile | 3 +- adjtime | 15 ----- hwclock | 23 ++----- network | 60 ++++++++++---------- rc.d | 2 +- rc.multi | 8 ++- rc.shutdown | 42 +++++++------ rc.single | 24 +++++--- rc.sysinit | 185 ++++++++++++++++++++++++++++------------------------------ 9 files changed, 169 insertions(+), 193 deletions(-) delete mode 100755 adjtime hooks/post-receive -- Arch Linux initscripts repository

1 0

[arch-projects] [mkinitcpio][PATCH 0/4] more low hanging froot
by Dave Reisner 05 Jun '11

05 Jun '11

There's a couple new minor features proposed in here, but most of it is in the name of simplification: 1/4: set fewer vars, which means we remove a bunch of eval usage. Just mark the hook as unreadable to disable it from running. 2/4: support identifying root by tag name. There's a bit of a conflict here, though. The kernel will support mounting root when provided as PARTUUID=, but util-linux's blkid won't support this. We can, however, support LABEL= and UUID= syntax by resolving via blkid, and trimming the 'PART' from PARTUUID is trivial. 3/4: just a shortcut when we need to create the root device in the non-udev use case when its specified as something like /dev/sdxy. 4/4: cleanse the environment before leaving early userspace. self explanatory. d init | 23 +++++++++-------------- init_functions | 23 ++++++++++++++--------- 2 files changed, 23 insertions(+), 23 deletions(-)

2 9

[arch-projects] [PATCH] [initscripts] Avoid error message when switch runlevels.
by Gerardo Exequiel Pozzi 05 Jun '11

05 Jun '11

Going from multi to single and going back to multi, bootlogd is not running. Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- rc.multi | 8 +++++--- rc.single | 8 +++++--- 2 files changed, 10 insertions(+), 6 deletions(-) diff --git a/rc.multi b/rc.multi index 60bb835..7af9279 100755 --- a/rc.multi +++ b/rc.multi @@ -26,8 +26,10 @@ fi run_hook multi_end -/bin/touch /var/log/boot -kill $(/bin/cat /run/bootlogd.pid) -/bin/rm /run/bootlogd.pid +if [[ -f /run/bootlogd.pid ]]; then + /bin/touch /var/log/boot + kill $(< /run/bootlogd.pid) + /bin/rm -f /run/bootlogd.pid +fi # vim: set ts=2 sw=2 noet: diff --git a/rc.single b/rc.single index 92b8f53..6a8cc29 100755 --- a/rc.single +++ b/rc.single @@ -48,9 +48,11 @@ if [[ $RUNLEVEL = 1 ]]; then exec /sbin/init -t1 S fi -/bin/touch /var/log/boot -kill $(/bin/cat /run/bootlogd.pid) -/bin/rm /run/bootlogd.pid +if [[ -f /run/bootlogd.pid ]]; then + /bin/touch /var/log/boot + kill $(< /run/bootlogd.pid) + /bin/rm -f /run/bootlogd.pid +fi # End of file # vim: set ts=2 sw=2 noet: -- 1.7.5.2

2 2

[arch-projects] [initscripts] [GIT] Arch Linux initscripts repository branch master updated. 2011.06.3-5-g0dfd69b
by tomegun＠archlinux.org 04 Jun '11

04 Jun '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 0dfd69b9e8617ef15413e5022442017603be5344 (commit) via d847a204aa5ab21a6c02998846ec3216cc7f887d (commit) via 023d6584d487d1c72788429584d4f2480075c963 (commit) via a79921851bfd93b3ac27955fa0bf191b96c22822 (commit) via af0b5c55dbd94a04ebc54cf3d119261bee383951 (commit) from 66f7acdc789099114945f08c92c9957f7e536f2d (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 0dfd69b9e8617ef15413e5022442017603be5344 Merge: 66f7acd d847a20 Author: Tom Gundersen <teg(a)jklm.no> Date: Sun Jun 5 01:57:31 2011 +0200 Merge remote-tracking branch 'falconindy/working' Conflicts: rc.sysinit Conflict with ip move away from /usr commit d847a204aa5ab21a6c02998846ec3216cc7f887d Author: Dave Reisner <d(a)falconindy.com> Date: Thu Jun 2 10:30:21 2011 -0400 use $() instead of `` for command substitutions Signed-off-by: Dave Reisner <d(a)falconindy.com> commit 023d6584d487d1c72788429584d4f2480075c963 Author: Dave Reisner <d(a)falconindy.com> Date: Thu Jun 2 10:28:47 2011 -0400 rc.d/rc.sysinit: whitespace cleanup Signed-off-by: Dave Reisner <d(a)falconindy.com> commit a79921851bfd93b3ac27955fa0bf191b96c22822 Author: Dave Reisner <d(a)falconindy.com> Date: Thu Jun 2 10:24:42 2011 -0400 rc.sysinit: allow exec in /run We already have /tmp and /dev/shm as world writeable directories with exec permissions, so it doesn't necessarily make sense to inhibit exec here. There also might be use cases where running one-off programs from /run might make sense. Signed-off-by: Dave Reisner <d(a)falconindy.com> commit af0b5c55dbd94a04ebc54cf3d119261bee383951 Author: Dave Reisner <d(a)falconindy.com> Date: Sat Jun 4 13:40:24 2011 -0400 rc.sysinit: kill off VERBOSE= parameter Upstream already supports this via the loglevel= parameter on the kernel cmdline, so we should support using this instead of our own homegrown solution. Signed-off-by: Dave Reisner <d(a)falconindy.com> ----------------------------------------------------------------------- Summary of changes: rc.conf | 2 -- rc.d | 4 ++-- rc.multi | 2 +- rc.single | 2 +- rc.sysinit | 30 ++++++++++++------------------ 5 files changed, 16 insertions(+), 24 deletions(-) hooks/post-receive -- Arch Linux initscripts repository

1 0

[arch-projects] [initscripts] new release soon
by Tom Gundersen 04 Jun '11

04 Jun '11

Hi guys, I'm thinking of making a release in the next few days. The reason I want it soon is to add deprecation comments to MODULES/MOD_AUTOLOAD. Aside from that we have some bug fixes, a new network system and lots of improvements to rc.d. If anyone have any outstanding patches, please remind me. And it would be great if people could try out the current git to make sure there are no problems I have missed ;-) [I am aware of the stuff being discussed by Eric and Sebastien, so if you guys agree soon, I'll include it, otherwise we can just wait for the next release (at the current rate, in a month's time)]. Cheers, Tom

3 6

[arch-projects] [initscripts] [GIT] Arch Linux initscripts repository annotated tag 2011.06.3 created. 2011.06.3
by tomegun＠archlinux.org 04 Jun '11

04 Jun '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 annotated tag, 2011.06.3 has been created at 43988f2ed2368640a0db41d673b9a846d99d43f9 (tag) tagging 66f7acdc789099114945f08c92c9957f7e536f2d (commit) replaces 2011.06.2 tagged by Tom Gundersen on Sun Jun 5 00:21:16 2011 +0200 - Log ----------------------------------------------------------------- fix for separate /usr Tom Gundersen (1): loopback: support separate /usr ----------------------------------------------------------------------- hooks/post-receive -- Arch Linux initscripts repository

1 0

[arch-projects] [initscripts] [GIT] Arch Linux initscripts repository branch master updated. 2011.06.3
by tomegun＠archlinux.org 04 Jun '11

04 Jun '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 66f7acdc789099114945f08c92c9957f7e536f2d (commit) via 6119386d3664ebbedc89cf43f1e1d4e62f71da0c (commit) from e404acd5fdeb0a7511e47b539c717e66a62777a9 (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 66f7acdc789099114945f08c92c9957f7e536f2d Author: Tom Gundersen <teg(a)jklm.no> Date: Sun Jun 5 00:18:10 2011 +0200 loopback: support separate /usr The move to iproute2 broke the setup of loopback for users having a separate /usr, as it was not monuted before /usr/bin/ip was called. Together with iprouet2-2.6.38-3, this fixes the problem by using /sbin/ip instead. Signed-off-by: Tom Gundersen <teg(a)jklm.no> commit 6119386d3664ebbedc89cf43f1e1d4e62f71da0c Author: Tom Gundersen <teg(a)jklm.no> Date: Thu Jun 2 16:22:42 2011 +0200 MOD_AUTOLOAD: remove from rc.conf This will no longer have any effect with the new udev package. Signed-off-by: Tom Gundersen <teg(a)jklm.no> ----------------------------------------------------------------------- Summary of changes: rc.conf | 2 -- rc.sysinit | 2 +- 2 files changed, 1 insertions(+), 3 deletions(-) hooks/post-receive -- Arch Linux initscripts repository

1 0