[arch-dev-public] [signoff] kernel26-

Eric Belanger belanger at ASTRO.UMontreal.CA
Wed Mar 26 14:00:08 EDT 2008

On Wed, 26 Mar 2008, Eric Belanger wrote:

> On Mon, 24 Mar 2008, Tobias Powalowski wrote:
>> Am Montag, 24. März 2008 schrieb Simo Leone:
>>> On Mon, Mar 24, 2008 at 07:28:13PM +0100, Tobias Powalowski wrote:
>>>> Users are happy with the new ISOs, just read the Forum thread about it.
>>> You know what. I don't care if the users are happy with the new ISOs.
>>> That's right, I finally said it.
>>> _I DON'T CARE_
>>> I don't care because _I_ am not happy with them. As someone who can see
>>> that from a technological standpoint, it's a marvel that they even work,
>>> that is, as a software developer, I'm ashamed to be associated with such
>>> a shoddy product.
>>> I've offered alternatives, hell I've spent a lot of time offering
>>> alternatives, built on more solid software enginerring principles
>>> than "Users are Happy", but no one around here, save Dan and Aaron, who
>>> just happen to be code contributors, seems to give a damn. What's up
>>> with that?
>> You never started to create ISOs nor you wanted to create them.
>> This topic here is about kernel26 signoff and i would be fine if people 
>> would
>> stay on topic.
>> greetings
>> tpowa
> It works fine on i686 here so signing off for i686.
> For x86_64, it booted fine but I received these error messages in my terminal 
> while building a package:
> Message from syslogd at ovide at Tue Mar 25 23:06:08 2008 ...
> ovide kernel: Oops: 0000 [1] PREEMPT SMP
> Message from syslogd at ovide at Tue Mar 25 23:06:08 2008 ...
> ovide kernel: CR2: 0000000000001128
> Message from syslogd at ovide at Tue Mar 25 23:13:25 2008 ...
> ovide kernel: Oops: 0000 [2] PREEMPT SMP
> In the dmesg trace, there was mention of unionfs. I don't have the trace 
> anymore because the system froze (black screen, had to reset manually) when I 
> tried to build the same package which I had previously interrupted as it 
> seemed to have stalled.
> Snippet from dmesg (which seems that it's currently syncing itself so I think 
> I just need to wait and it'll fix itself on his own. I definitely need to 
> RTFM about raid ;) :

The raid problem is fixed. As I realised when writing my initial email, I 
just had to give it time to resync. I'll updated the kernel and see how it 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

More information about the arch-dev-public mailing list