By editing init, how to change some locations of files?

HuskyDG / initrd-magisk

Integrate Magisk into Android-x86 project

GNU General Public License v3.0

174 stars 124 forks source link

By editing init, how to change some locations of files? #25

Open 1457384613gh opened 1 year ago

1457384613gh commented 1 year ago

What I want is to achieve this picture,

mmap_1675497971976

The advantage of this is

to avoid editing android.cfg over and over again, if Android x86 updates;
to avoid copying initrd.img (initrd-magisk.img renamed first) to cover initrd.img (the real not having been made a backup, yet), by mistake;
to avoid .img files into $SRC are too many to be recognized immediately rightly, only to be deleted or covered by mistake;
to avoid hesitating for a long time to tangle which .img file should be renamed at first.

And then I create a fork to edit,

After building, I download to try. It can boot, but seems not to mount boot-magisk.img. It must be something I haven't edited yet.

Could you tell me what else I should edit?

I will appreciate it if you would help me about that.

HuskyDG commented 1 year ago

make PR if you want :)

1457384613gh commented 1 year ago

PR? What? I even don't know how I haven't done enough.

HuskyDG commented 1 year ago

Pull request...

1457384613gh commented 1 year ago

https://github.com/HuskyDG/initrd-magisk/pull/26

HuskyDG commented 1 year ago

You mean we should leave stock initrd and boot-magisk in /boot ?

1457384613gh commented 1 year ago

You mean we should leave stock initrd and boot-magisk in /boot ?

Yes.

1457384613gh commented 1 year ago

By the way, another question. I have checked that [boot-magisk.img] is R/W and into a f2fs partition. 截图 2023-02-05 15-21-06 I have tried over and over again. It always shows that. 😭😭😭 Screenshot_20230205-153502_Magisk

HuskyDG commented 1 year ago

Work fine for me ¯_(ツ)_/¯ If you can't, it is because of f2fs

1457384613gh commented 1 year ago

Work fine for me ¯_(ツ)_/¯ If you can't, it is because of f2fs

I tried ext4. It could work.

The kernel+initrd.img can actually mount f2fs.

What's the problem?

1457384613gh commented 1 year ago

I have another idea. I have adapted a Bootloader. mmap_1675588169436 I am asking Huy Minh Bùi and K for how to mount ESP:/EFI into /mnt/efi by using kernel+initrd.img with init edited first. And then similarly, conclude how to mount ESP:/EFI/Bootloader/Linux_boot_partition into /mnt/boot with init edited first. ESP is FAT16/32; It won't show "/dev/block/loop2 is read only", I think. I will try slowly.

vinphan commented 11 months ago

I have another idea. I have adapted a Bootloader. I am asking Huy Minh Bùi and K for how to mount ESP:/EFI into /mnt/efi by using kernel+initrd.img with init edited first. And then similarly, conclude how to mount ESP:/EFI/Bootloader/Linux_boot_partition into /mnt/boot with init edited first. ESP is FAT16/32; It won't show "/dev/block/loop2 is read only", I think. I will try slowly.

Hvae you sucessfully installed Magisk on Bliss OS?