• General Linux Chat and Small Questions
    3,153 replies, posted
[img]http://imgkk.com/i/zbzt.png[/img] :v:
[img]http://i.imgur.com/pus8J.png[/img] [editline]19th February 2011[/editline] Just spend an hour on writing a bash script that does magic. echo $mood satisfied
Can someone tell me how i can reset me password? I have tried all the ones i know.
passwd will allow you to reset the password of the user currently logged in, it will ask you for your current password. If you want to change the password but don't know it, you need to run [code]passwd username[/code]
I mean i cant get passed the login screen.
[QUOTE=Xonax;28167967]I mean i cant get passed the login screen.[/QUOTE] What's your display(login) manager? gdm, kdm, lxdm, SLiM?
At the bottom bar it says (Just typing everything) English (US) Keyboard (USA) Weird picture (Gnome) and the date and time..
[QUOTE=Xonax;28169208]At the bottom bar it says (Just typing everything) English (US) Keyboard (USA) Weird picture (Gnome) and the date and time..[/QUOTE] Press Ctrl+alt+F2, login from there and do the commands in the previous post.
-snip-
Yeah the thing is, i forgot my password and i want to change it, so i can't login. Every tip you gave me is about logging in to fix it.
I know that Ubuntu used to have a boot option that allowed you to boot into a root shell and fix shit. If you're running ubuntu and that option is there, it should do the job. [editline]20th February 2011[/editline] You could also boot from a live cd, chmod into the installed system then chnage the password there.
[QUOTE=Boris-B;28170239]I know that Ubuntu used to have a boot option that allowed you to boot into a root shell and fix shit. If you're running ubuntu and that option is there, it should do the job. [editline]20th February 2011[/editline] You could also boot from a live cd, chmod into the installed system then chnage the password there.[/QUOTE] [url]http://ubuntuforums.org/showthread.php?t=1275192[/url] What I snipped before: [quote] I just found out from a USENET reply that the following works: * Reboot and press ESC at the GRUB prompt, to go into GRUB menu * Press 'e' to edit the kernel selection that you want * Select a second line in the kernel selection and press 'e' again * Remove stuff such as "ro quiet splash" and append "rw init=/bin/bash" * Press ESC to go back press 'b' to boot, you should drop into root shell. I tested this on a Ubuntu Hardy server edition. I will try it later on Ubuntu Jaunty desktop edition to see if it works, which is what I expect. Then I will mark this thread as solved. Thanks [/quote] Follow these steps and run the command mentioned before. Then just run "reboot"
"ESC at the GRUB prompt" should be replaced with "Shift at the GRUB prompt". At least if you are using GRUB 2, which is standard for Ubuntu 10.04 and forward.
[QUOTE=Lego399_;28170467]"ESC at the GRUB prompt" should be replaced with "Shift at the GRUB prompt". At least if you are using GRUB 2, which is standard for Ubuntu 10.04 and forward.[/QUOTE] ??? I'm using Arch with GRUB2 and all that still works.
[QUOTE=jjsullivan;28170668]??? I'm using Arch with GRUB2 and all that still works.[/QUOTE] Both apparently works then :smile:
[QUOTE=jjsullivan;28170336][url]http://ubuntuforums.org/showthread.php?t=1275192[/url] What I snipped before: Follow these steps and run the command mentioned before. Then just run "reboot"[/QUOTE] Everything on there is right, but instead of removing stuff from the kernel line and adding the stuff you added. All you need to do is add a 1 to the end of the kernel line. That boots you up in runlevel 1 which drops you in a root shell. I'm pretty sure you don't need the root password for that.
When i press ESC at the grub, it does nothing, same with shift. If this helps its Linux Mint 10.
[QUOTE=Xonax;28171436]When i press ESC at the grub, it does nothing, same with shift. If this helps its Linux Mint 10.[/QUOTE] You should probably extend the time then that grub displays itself: [code] sudo *text editor here* /boot/grub/menu.lst [/code] Then change timeout to something longer(I recommend five seconds): [code] timeout 5 [/code] Save, close, reboot, then do whats been said about five times now :P
That would help, if he was able to log in.
[QUOTE=nikomo;28171795]That would help, if he was able to log in.[/QUOTE] Goddamnit, why do I always seem to forget things like this :saddowns: Guess the final option is the only one then, guess he'll have to load a livecd to edit the grub file.
I think that my Arch Linux install on my laptop finally went full retard. I was doing a full system upgrade and a few commands failed out of the blue. pacman gave me "Error: Command failed" or something in the very non descriptives lines of that. I was using yaourt for the update and it suddenly started spewing a bunch of errors saying that grep and other commands were no where to be found. In the list of missing commands there was: pacman, grep, bash, ls, etc. I couldn't even read then damn log because cat went missing. I finally boot from a live cd and see that all the files are where they should be. I also backup all of my important crap. When reading the log, pacman gave me no other useful information. I then decide to boot my install and it kernel panics telling me that init is no where to be found. When I check with a live cd it's right there. I then try to boot the arch install disk and use pacman to install some packages remotely. They all give me the "error: command failed" error. Even if that happens, pacman assumes the installation went fine and thinks the package is up to date. I really don't feel like reinstalling and I don't know what to do. I'm currently running badblocks on the disk to see if there are any errors on the disk itself. When I'm done I'll go check to see if the permissions are right and if that's the reason for those problems. Also, when I booted once from CD I tried to see if the commands worked. I rand the ls program from my mounted drive and it ran just fine. I'll read through the logs when badblocks is done and see what happened. Maybe I installed something that fucked with the GNU utilities and what not.
Something similar happened to my Arch install a week ago.
How did you fix it? Badblocks just finished and there's nothing wrong with the disk. I really wonder what happened...
[QUOTE=Boris-B;28192795]How did you fix it? Badblocks just finished and there's nothing wrong with the disk. I really wonder what happened...[/QUOTE] Same thing happened because I set the permissions of / to everyone, not knowing how touchy it was.
[QUOTE=Boris-B;28191664]I think that my Arch Linux install on my laptop finally went full retard. I was doing a full system upgrade and a few commands failed out of the blue. pacman gave me "Error: Command failed" or something in the very non descriptives lines of that. I was using yaourt for the update and it suddenly started spewing a bunch of errors saying that grep and other commands were no where to be found. In the list of missing commands there was: pacman, grep, bash, ls, etc. I couldn't even read then damn log because cat went missing. I finally boot from a live cd and see that all the files are where they should be. I also backup all of my important crap. When reading the log, pacman gave me no other useful information. I then decide to boot my install and it kernel panics telling me that init is no where to be found. When I check with a live cd it's right there. I then try to boot the arch install disk and use pacman to install some packages remotely. They all give me the "error: command failed" error. Even if that happens, pacman assumes the installation went fine and thinks the package is up to date. I really don't feel like reinstalling and I don't know what to do. I'm currently running badblocks on the disk to see if there are any errors on the disk itself. When I'm done I'll go check to see if the permissions are right and if that's the reason for those problems. Also, when I booted once from CD I tried to see if the commands worked. I rand the ls program from my mounted drive and it ran just fine. I'll read through the logs when badblocks is done and see what happened. Maybe I installed something that fucked with the GNU utilities and what not.[/QUOTE] I got these kinds of errors a while back when I first tried arch on my netbook, the inkscape install went amok when it asked to remove conflicting packages with xz-utils. So pacman went, then some other dependency issues arised so I just re-installed and was very careful the next time. I didn't have anything to lose anyway since all my documents are on dropbox.
I couldn't fix it on mine, reinstalled.
The more I think about the more it looks like a permission issue. I can't be that all these binaries are gone bad, because they work. Also, my upgrade didn't touch all those files. I can't be the new kernel because the problem appeared before I rebooted. Everything that might be a possible cause for it doesn't make sense because it either doesn't affect all the files that break, or I need to reboot or do something special for it to work. I think that some package might have accidentally changed a permission on something like / or even just something in the $PATH so that executables become invisible. Is there some sort of a list of what files should have what permissions and what directories should have what permissions.
Found old HDD and put into a machine I have. Installed Debian. Not booting, probably installed GRUB onto the old HDD I just put in, booted from it. Welcome to GRUB! Debian... SUSE Linux 10? How old is SUSE Linux 10, exactly?
[QUOTE=nikomo;28197682]Found old HDD and put into a machine I have. Installed Debian. Not booting, probably installed GRUB onto the old HDD I just put in, booted from it. Welcome to GRUB! Debian... SUSE Linux 10? How old is SUSE Linux 10, exactly?[/QUOTE] 06-10-2005 Anyway buying a Asus K52F-EX699V , can't wait.
[QUOTE=nikomo;28197682]Found old HDD and put into a machine I have. Installed Debian. Not booting, probably installed GRUB onto the old HDD I just put in, booted from it. Welcome to GRUB! Debian... SUSE Linux 10? How old is SUSE Linux 10, exactly?[/QUOTE] SUSE 10 is about 6 years old
Sorry, you need to Log In to post a reply to this thread.