Are you new to LinuxQuestions. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here!
Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use. Click here for more info. I haven't a clue. What is the output of the commands locate init-bottom locate local-bottom. Interesting study! Also, mll is on my 'to-do' list Let us know what you 'find' which distro? Last edited by Jjanel; at AM. There is some information on these directories in man initramfs-tools On my system, Linux Mint No surprise here, as noted by other posters: Code:.
Sorry, I actually run debian which does have scripts in the those directories. I guess mint does not. Thanks for that 'man' reference hydrurga. I'm afraid it's above my pay grade however. If your script does not depend on other scripts inside the same directory, you can just copy the boilerplate code.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Ask Question. Asked 5 years, 8 months ago. Active 3 years, 9 months ago. Viewed times. I assume if you're not asked to do the upgrade that Code:. April 28th, 4. Join Date Apr Beans 8. I also solved the problem with a USB keyboard and typing Code:. May 25th, 5. Fixed my Acer Aspire One netbook which got frozen login screen after a botched attempt to run a routine update on an unreliable hotel WiFi.
August 4th, 6. Join Date Aug Beans 1. I can recover mouse and keyboard functionality by using USB mouse and keyboard as suggested. Latest initscripts package installed. Rebooted successfully. Looks like this bug is fixed. Thanks Ubuntu team! Now the system boots fine I still see those udev warnings from bug but that's certainly another issue.
So the package upstart? I still have this problem How can I boot again and preform fix?? I wasn't able to fix the issue directly from updates. However if you want to boot into something you can edit the boot parameters in grub:.
As said before, despite all the updates applied in the last 15 hours, I had to reinstall to get the issue fixed. Can sombody tell me what is wrong in the upstart package and how i can fix? I cannot reinstall again the machine and would like to continue to use the karmic. Hi, For those that can't boot to your system no matter what, here is my solution chroot from live cd :.
I already upgrade a lot of times my system without success and the problem still remain. I will try to upgrade tomorrow hoping to solve the problem. I booted from a live cd and ran apt-get update; apt-get upgrade, but the system reboots after doing this:.
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct this problem. I created a fresh debootstrap install for my system and encountered the same problem, so it's not an issue of timing the updates wrong, as others have suggested. The original problem in this bug report, hangs at boot time, has been reported fixed by most of the users following up here. Since there have been extensive fixes to the boot scripts in the two days since this was reported, I believe this bug is fixed and as such am marking it as closed.
If you are the original submitter of this bug and are still seeing problems after applying all updates to your system, please feel free to reopen. Someone has a better suggestion? I used zsh instead, try dash as well 4. Set network connection ifconfig eth0 Errors were encounted while processing linux-image- 2.
I fixed it somehow Many steps and I don't know if I remember them all. Then type dhclient eth0 connect an ethernet cable first if you havent already. If it manages to connect which it should type aptitude update and then aptitude upgrade. It will update mine failed a few packages because something was not mounted I dont know exactly what happened.
After this I tried to boot using the latest kernel but it froze sayin somethin about kernel panic.. I dont remember exactly. Anyway I chose the previous kernel in recovery mode run fsck, rebooted again with the previous kernel in recovery and the options were there.
I chose make free space then fsck and then resume normal boot and I got in kde. I ran aptitude again aptitude autoremove apt-get autoclean apt-get autoremove aptitude update aptitude upgrade and all that stuff Hope it helps.
0コメント