Closed GoogleCodeExporter closed 9 years ago
You need to be a little more cautious for the first time you converting livecd
into a proper install. As the warning says, read the errors during update and
act accordingly.
I smell that you missed one of important steps. For example, forgot to run
"deepclean" or revdep-rebuild.
Please reboot from livecd again, mount disk partitions to /mnt/gentoo in the
right order (root, boot), swap and chroot to your pentoo setup on a harddisk
(http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=6) and run
the update steps again.
Post "rc-udate show" output here after that.
You can also review /var/log/portage/elog/summary.log for errors or
recommendations you might missed.
FYI, I don't have that file either, but it boots just fine.
Original comment by blshkv
on 30 Mar 2013 at 7:04
ok, the /etc/inittab file (with faulty mingetty) is getting generated by
"fixinittab" livecd script.
Once you have your chroot env ready, try the following:
disable fixinittab from rc-update:
rc-update delete fixinittab
re-emerge inittab:
emerge -1 sys-apps/sysvinit && etc-update
I'm checking if "emerge --depclean" suppose to clean up the livecd start up
services..
Original comment by blshkv
on 30 Mar 2013 at 7:45
To answer your question on the IRC:
no, you don't need to reinstall even the new env is no longer bootable.
You can boot from liveusb and chroot to your pentoo on the harddisk.
I have started a new wiki page with suggestions above. Feel free to expand it
with your experience: https://code.google.com/p/pentoo/wiki/PentooInstaller
Original comment by blshkv
on 30 Mar 2013 at 8:30
FYI, I tried upgrading rc1.1 by following the upgrading steps and I didn't have
to rebuild anything manually.
I'll keep in the wiki just in case anyways. Hope it works for you too.
Original comment by blshkv
on 31 Mar 2013 at 1:59
Issue 131 has been merged into this issue.
Original comment by blshkv
on 15 Apr 2013 at 11:53
Re-opening, since the issue hasn't been resolved for the user
Original comment by blshkv
on 15 Apr 2013 at 11:54
seems false positive. Closing again
Original comment by blshkv
on 16 Apr 2013 at 2:39
Original issue reported on code.google.com by
runner...@gmail.com
on 30 Mar 2013 at 3:56