@congeec my init.d seems intact, it contains a bunch of files, but i wonder how u manage to get over it ? thanks. (im replying on livecd which lacks a chinese input method, sorry about it
congeec
2016-07-28 23:06:00 +08:00
@asxaqz I'm fine with English. What I did was to download a net-bootable image, chroot into the original broken system, rebuiding and installing missing packages, and most importantly, ran Gentoo's depency-checking tool: rev-rebuild.
congeec
2016-07-28 23:08:25 +08:00
@asxaqz If I am right, you can use dpkg on Debian derivied systems to determine which package does /sbin/init belong to.
You can pull a full-iso, make a directory comparison and copy the missing files.
asxaqz
2016-07-28 23:20:54 +08:00
@congeec thanks, i will try it, but there are really tons of them contributing to /sbin/init
asxaqz
2016-07-28 23:25:13 +08:00
@xss i suppose u mean initramfs? just check my dpkg.log, and find i did upgrade some package about initramfs, i will try to reinstall them, thanks
congeec
2016-07-28 23:29:18 +08:00
@asxaqz My suggestion is that you'd better figure out what does your missing /sbin/init belong to. sysvinit or systemd? If you can figure it out, repairing your inti system (sysvinit or systemd) is the best way.
asxaqz
2016-07-28 23:45:34 +08:00
@congeec oh i see, i just used dpkg -S to check the the /sbin/init of the original livecd, it turns out to belong to upstart, and i happened to do an upgrade to it last night. i try to reinstall it but it seems that i have to uninstall some core-package to resolve the dependency. now im not sure if i should do it
congeec
2016-07-28 23:51:54 +08:00
@asxaqz Backup your data. Try to reinstall these core-package, remember to make a record of the packages you will uninstall. BACKUP YOUR DATA