[arch-releng] 2010.04.05 snapshots ready for testing

Gerardo Exequiel Pozzi vmlinuz386 at yahoo.com.ar
Wed Apr 7 00:23:35 CEST 2010


On 04/06/2010 05:49 PM, Dieter Plaetinck wrote:
> On Tue, 06 Apr 2010 22:38:24 +0200
> Thomas Bächler<thomas at archlinux.org>  wrote:
>
>    
>> Am 06.04.2010 22:31, schrieb Dieter Plaetinck:
>>      
>>> thanks, but need more info.
>>> which image is this ? netinstall or core?
>>> when does this happen? which step exactly in the init process?
>>> screenshot?
>>> what happens if you pick the normal x86, or the normal x86_64?
>>>
>>> i just tried netinstall-dual, picked x86 and it works fine.
>>> I only have 32bit systems so i cannot try the other options.
>>> (well i can select them, but they refuse to boot, obviously :)
>>>
>>> also, please use http://bugs.archlinux.org/index/proj6
>>>        
>> That problem is known (I saw Gerardo posting about it either here or
>> on the bugtracker). The 64 bit kernel/aufs lacks the 32 bit
>> compatibility system call, so remounting aufs on 32 bit userland with
>> a 64 bit kernel fails. We can't do anything about it, and it is
>> read-write anyway.
>>
>>      
> hm you're right
> http://mailman.archlinux.org/pipermail/arch-releng/2010-February/000883.html
>
> is this a system call which is not enabled in the arch kernels? or just
> does not exist? what exactly do you mean with "it is read-write
> anyway"? what is? and how is that relevant?
> If i understood ionut's mail correctly, this is something that breaks
> the boot process/environment. or not?
> maybe we should just disable the "64bit kernel with 32bit userspace"
> option.
>
> Dieter
>
>    
Not all 32 bit ioctls are implemented as wrapper to ioctls in 64 bits.

This will work if -i parameter is add to mount in rc.sysinit. The mount 
-i does not call in this case to mount.aufs, just use mount. Maybe we 
can keep a overlay copy of rc.sysinit or ...(*)

Anyway: I said that remouting / as ro (aufs) is not necessary. This is 
only necessary when you boot a normal filesystem with rw (normally will 
be mounted as ro), so in the next step can run fsck.

* Maybe can be implemented without any issues in rc.sysinit at initscripts.
-/bin/mount -n -o remount,ro /
+/bin/mount -i -n -o remount,ro /


-- 
Gerardo Exequiel Pozzi ( djgera )
http://www.djgera.com.ar
KeyID: 0x1B8C330D
Key fingerprint = 0CAA D5D4 CD85 4434 A219  76ED 39AB 221B 1B8C 330D




More information about the arch-releng mailing list