[2011-06-02 19:16:29 +0300] Evangelos Foutras:

The net-tools package in [testing] still ships the man page for hostname(1), which also exists in the coreutils package (also in [testing]):

My bad. I'll upload a new version soon. -- Gaetan

On 2 June 2011 09:52, Gaetan Bisson wrote:

[2011-06-02 18:26:39 +0200] Gaetan Bisson:

...

[2011-06-02 19:16:29 +0300] Evangelos Foutras:

...

The net-tools package in [testing] still ships the man page for hostname(1), which also exists in the coreutils package (also in [testing]):

My bad. I'll upload a new version soon.

Done.

Signoff x86_64.

On 2 June 2011 10:57, Thomas Bächler wrote:

Complete the load-modules.sh removal. Module blacklisting/disabling now only works with the methods Tom described for the initscripts changes. load_modules=off is no longer supported.

Please sign off.

Signoff x86_64.

On 03/06/11 10:15, Tom Gundersen wrote:

On Thu, Jun 2, 2011 at 7:57 PM, Thomas Bächler wrote:

...

Complete the load-modules.sh removal. Module blacklisting/disabling now only works with the methods Tom described for the initscripts changes. load_modules=off is no longer supported.

Please sign off.

Dan McGee (1): Don't print success/failure result on same line

Thomas Bächler (3): mkinitcpio.conf: Fix modprobe.conf location in the FILES= example Remove load-modules.sh. Requires the udev 171-2 package. Release version 0.6.13

Signoff x86_64

Signoff i686, Allan

On Thu, Jun 2, 2011 at 10:53 PM, Eric Bélanger wrote:

On Thu, Jun 2, 2011 at 11:28 AM, Tom Gundersen wrote:

...

Hi guys,

After the discussion regarding initscripts-2011.06.1 we decided that things would be simpler if we move all the above packages in one go (thanks to Gaetan and Thomas for the help!), so please test and sign off.

The error messages I mentionned in an earlier signoff thread are back: http://mailman.archlinux.org/pipermail/arch-dev-public/2011-May/020434.html

I was also getting them with the previous versions of these packages in testing/core.

I'll reboot with udev_log set to debug. Maybe that will give us more info.

That won't help unless there's a way to save it. The text scroll so fast that I can't read it. I booted the LTS kernel and I got the same message. Also, my loopback interface didn't started. When I ran "/usr/sbin/ip link set up dev lo" manually in a terminal, it started fine. I don't know why it didn't work when booting up.

On Fri, Jun 3, 2011 at 7:37 AM, Tom Gundersen wrote:

On Fri, Jun 3, 2011 at 7:17 AM, Eric Bélanger wrote:

...

On Thu, Jun 2, 2011 at 10:53 PM, Eric Bélanger wrote:

...

On Thu, Jun 2, 2011 at 11:28 AM, Tom Gundersen wrote:

...

Hi guys,

After the discussion regarding initscripts-2011.06.1 we decided that things would be simpler if we move all the above packages in one go (thanks to Gaetan and Thomas for the help!), so please test and sign off.

The error messages I mentionned in an earlier signoff thread are back: http://mailman.archlinux.org/pipermail/arch-dev-public/2011-May/020434.html

What happens when you try to execute the commands in question manually after boot?

They work as expected. The error is not fatal. My raid array gets assembled without user intervention. Either it is eventually done by the initscripts (I can't find where, I think that code parthas been removed) or by something else.

...

...

I'll reboot with udev_log set to debug. Maybe that will give us more info.

That won't help unless there's a way to save it. The text scroll so fast that I can't read it. I booted the LTS kernel and I got the same message.

debug is probably too much information, try warning first. The messages should be in "dmesg", /var/log/boot or /var/log/everythnig.

FWIW, the instructive comments in udev.conf doesn't mention "warning" as a valid value. I tried it and the error message doesn't get printed. Dmesg doesn't have the error message and the logs are useless since the error happens when the kernel is booting, i.e. rc.sysinit isn't running yet. I suppose it's mkinitcpio/udev related.

...

Also, my loopback interface  didn't started.  When I ran "/usr/sbin/ip link set up dev lo" manually in a terminal, it started fine. I don't know why it didn't work when booting up.

Do you see anything in the above logs?

I found the source of this error. My /usr is on it's own partition. So when rc.sysinit attemps to setup the loopback interface with /usr/sbin/ip, my /usr partition is not mounted yet. So it fails. I don't know what would be the best way to fix. Maybe moving ip to /sbin or to postpone the lo interface setup after the partitions are mounted. OT: I noticed that the /var/log/boot is somewhat hard to read because of the presence of the ansi escape sequences for the colored output. Would it be a good idea (or even possible) to removed these perhaps with a sed line after bootlogd has finished its stuff?

Thanks for reporting,

Tom

On Sat, Jun 4, 2011 at 9:23 AM, Thomas Bächler wrote:

Am 04.06.2011 05:41, schrieb Eric Bélanger:

...

OT: I noticed that the /var/log/boot is somewhat hard to read because of the presence of the ansi escape sequences for the colored output. Would it be a good idea (or even possible) to removed these perhaps with a sed line after bootlogd has finished its stuff?

You can 'sed' them out (you need to replace the '^[' with a proper escape character). But there are other problems, some lines are truncated.

A patch implementing a sensible heuristic for what to do with this would be very welcome. -t

On Sat, Jun 4, 2011 at 10:56 AM, Thomas Bächler wrote:

However, the truncation problem is already present in the source file.

Ah, I read your message too quickly. I don't think we can do much about this (except sending patches upstream), as there is no way to configure the output from bootlog. -t

On Sat, Jun 4, 2011 at 6:02 PM, Eric Bélanger wrote:

I don't see any truncated lines in /var/log/boot.  Either it's system dependent or I don't look at the right place. Anyway I'll look into a patch for the ansi code. Even if we can't make the output format as we would wish, cleaning it up wouldn't hurt.

It would be nice to be able to use "less -r" to view the file... -t

On Sat, Jun 4, 2011 at 4:58 AM, Tom Gundersen wrote:

On Sat, Jun 4, 2011 at 5:41 AM, Eric Bélanger wrote:

...

FWIW, the instructive comments in udev.conf doesn't mention "warning" as a valid value.

Oops, I meant to say "info".

I also tried info when I tried with debug. I didn't noticed any difference with debug as far as the excessive output go. I could try it again and check dmesg more carefully.

...

I tried it and the error message doesn't get printed.  Dmesg doesn't have the error message and the logs are useless since the error happens when the kernel is booting, i.e. rc.sysinit isn't running yet. I suppose it's mkinitcpio/udev related.

If rc.sysinit is not running, then this is an mkinitcpio problem. I guess the reason you are seeing it again might be a race? We have sped things up quite a bit with this release, so things might race differently than before.

That's what I believe. I didn't mentionned it but dmesg contains output saying that the raid was assemble and all mirrors are active. So despite the error message from udevd, the kernel still manage to assemble the raid array. Also, I can't find the hook or config file that contains the mdadm command line displayed in the error message. I looked in /etc and /lib/initcpio but it's not there.

...

They work as expected. The error is not fatal.  My raid array gets assembled without user intervention. Either it is eventually done by the initscripts (I can't find where, I think that code parthas been removed) or by something else.

My guess is that the error you are seeing is from udev in mkinitcpio, and the udev in rc.sysinit works correctly. To change the error reporting you would need to run mkinitcpio -p kernel26 after updating udev.conf.

I was updating my initcpio file when changing the udev.conf.

...

...

...

Also, my loopback interface  didn't started.  When I ran "/usr/sbin/ip link set up dev lo" manually in a terminal, it started fine. I don't know why it didn't work when booting up.

Do you see anything in the above logs?

I found the source of this error. My /usr is on it's own partition. So when rc.sysinit attemps to setup the loopback interface with /usr/sbin/ip, my /usr partition is not mounted yet. So it fails.  I don't know what would be the best way to fix. Maybe moving ip to /sbin or to postpone the lo interface  setup after the partitions are mounted.

Ahhhh. I think this might cause many more problems than just the loopback. In particular, anything called in udev rules may reside on /usr. This means the rule will fail and it will not be rerun.

Have a look at "grep /usr /lib/udev/rules.d/*" to see examples of what might be broken.

Most other distros, and upstream projects have given up on supporting a separate /usr, so it will be buggy. I suggest moving your /usr to your rootfs, regardless of this particular problem.

I recall you mentionning that on another ML thread. I wanted to ask you for details at the time but did get to. I'll move my /usr to my rootfs. I use lvm2 so the resizing/repartionning should be easy.

As to the loopback device. I don't think it is a good idea to delay this to after /usr is mounted. If anything we might want to move it earlier in boot. That leaves moving ip out of /usr.

Does anyone know the consequences of this? Do we want to keep supporting a separate /usr?

If I'm the only one with the problem, you can also keep things as they are now, i.e. not support /usr on a separate partition. As I'll be moving my /usr, that problem will become moot. Eric

Cheers,

Tom

On Sat, Jun 4, 2011 at 12:45 PM, Tom Gundersen wrote:

On Sat, Jun 4, 2011 at 6:30 PM, Eric Bélanger wrote:

...

That's what I believe.  I didn't mentionned it but dmesg contains output saying that the raid was assemble and all mirrors are active. So despite the error message from udevd, the kernel still manage to assemble the raid array. Also, I can't find the hook or config file that contains the mdadm command line displayed in the error message. I looked in /etc and /lib/initcpio but it's not there.

It is called from udev (both in the initramfs, which fails, and in the real fs, which succeeds). The rule is /lib/udev/rules.d/64-md-raid.rules. Could it be that your initramfs lacks some modules? I guess Thomas would know this better than me...

I could try my fallback initcpio. I don't remember if I tried that. My /etc/mkinitcpio.conf has: MODULES="pata_amd ata_generic sata_nv sata_sil24 floppy dm-mod raid1 raid456" HOOKS="base udev autodetect pata scsi sata usbinput keymap mdadm lvm2 filesystems" md=0,/dev/sda1,/dev/sdb1 md=1,/dev/sda2,/dev/sdb2

...

If I'm the only one with the problem, you can also keep things as they are now, i.e. not support /usr on a separate partition. As I'll be moving my /usr, that problem will become moot.

There probably will be more affected people once it reaches [core], so we should either decide not to support separate /usr, or fix it.

-t

On Tue, Jun 7, 2011 at 11:28 PM, Eric Bélanger wrote:

Same problem with fallback image.  Using the info log level doesn't help at all. It scrolls too fast to read and it's not recorded anywhere. dmesg only contains a message that udevd has started, I guess it's because the output is produced by udevd and not the kernel. The logs are useless because the loggers are not running yet. I think I'll just ignore the message for now.

cc'ing arch-projects: Maybe we should add bootlogd (orsomething similar) to mkinitcpio and keep those logs in /run so that these kind of issues can be debugged more easily? -t

On Tue, Jun 7, 2011 at 11:45 PM, Dan McGee wrote:

Isn't this what minilogd [1] was intended for?

Hmmm... it would be neat if we can make that work. However, I'm not sure it would. If I understand correctly, minilogd will buffer all messages to /dev/log until syslog-ng is started, and then minilogd will push it's log into the normal syslog. However, if we have a minilogd instance in initramfs I guess we would have to kill it before starting init, so it will not be able to pass on its messages. Or am I wrong? I really don't know the details of how this is supposed to work. Cheers, Tom

On Tue, Jun 7, 2011 at 11:50 PM, Eric Bélanger wrote:

Isn't the filesystems ro at that point in time?

That's the beauty of /run, it is rw from initramfs until shutdown ;-) -t

On Fri, Jun 3, 2011 at 7:17 AM, Eric Bélanger wrote:

Also, my loopback interface  didn't started.  When I ran "/usr/sbin/ip link set up dev lo" manually in a terminal, it started fine. I don't know why it didn't work when booting up.

I'm not able to reproduce this... Anyone else? -t