On 2015-09-10 at 04:57 -0700, Jose R R wrote: > On Wed, Sep 9, 2015 at 6:16 AM, Ivan Shapovalov <intelfx100@xxxxxxxxx > > wrote: > > On 2015-09-09 at 00:54 -0700, Jose R R wrote: > > > Scratch my previous issue, Ed. It is *not* related to your new > > > Reiser4 > > > software release 4.0.1 module nor reiser4progs. > > > > > > My usual development environment is a modified non-systemd Debian > > > Sid > > > (unstable) on a Reiser4 root partition. The kernels built won't > > > boot > > > in *that* particular instance due to a least one other additional > > > issue: > > > target filesystem does not have requested /sbin/init > > > > Could you please elaborate? > > I can only describe what's going on; still searching for a solution > myself. > > < http://without-systemd.org/wiki/index.php/Main_Page > > > initrd.imgs created within a debian Sid environment -- with systemd > replaced by init -- will fail to mount new reiser4 root file system > during boot; whereas, > initrd.imgs created within a debian Sid environment -- with systemd - > - > will mount *any* (systemd and non-systemd) new reiser4 root fs and > boots system -- as it should. > > Issue closely resembles recent ZFS issue < > https://github.com/zfsonlinux/zfs/issues/3605 > except that, in this > non-systemd particular case, neither mkinitramfs-tools nor > dracut-created initrd.imgs are successful. > > As I am running a couple of more or less similar AMD64 Debian Sid on > Reiser4 root fs, I built the initrd.img for a non-systemd Debian Sid > inside the environment of a systemd Debian Sid. > > I already disassembled an older 3.xy.z initrd and compared its > contents with a initrd.img 4.1.6 built into this non-systemd Debian > Sid but file trees appears similar. > > < http://linux.koolsolutions.com/2009/11/12/initramfs-ramfs-tmpfs-com > pressed-image/ > > > > Thus, a kernel I built in this non-systemd environment (Sept. 07, > 2015) can be installed in a systemd environment and it will boot; > moreover, I can take the initrd.img produced in the systemd > enviroment > (during kernel installation) and use it to boot this non-systemd > system -- and will proceed smoothly into its new Reiser4 4.0.1 root > fs. > > < https://pbs.twimg.com/media/COiiyUtUkAAw95X.png:large > > Very interesting, thanks for the observations. I'm surprised with the fact that systemd makes a difference here... -- Ivan Shapovalov / intelfx /
Attachment:
signature.asc
Description: This is a digitally signed message part
