|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| ARCHIVES - HowTos Discussions Have any questions about any HowTo found at the wiki? Post in here! |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Thanks Bozo. I have copied that just in case.
It almost came up when I had to work on my Fathers computer last week. He had forgot what it was. And I had lost where I had written it down when I had set up his computer. Luckily it came to mind, but for us aging folks on a computer we don't use daily it would be all too easy to forget the password. |
|
|||
|
Quote:
Cannot open /dev/urandom for reading: no such file or dir Cannot create salt for blowfish crypt Error: password NOT changed passwd: Authentication token manipulation error I've also tried editing passwd and shadow, as mentioned in the original post, and when I log back in as a regular user and type su in a terminal window, I'm prompted for a password. I've tried just hitting enter, and I'm told that it's the incorrect password. Any ideas? |
|
|||
|
Quote:
I'm not sure from your post what went wrong, but I suspect in Step 5 you didn't understand what you were to enter. Forgive me if I'm explaining basics you're familiar with, but I don't know your background/experience with Linux, and I'm just guessing what went wrong. In Linux, hard drives are referred to by a letter, i.e. hda would mean the first hard drive, hdb the second, and so forth. Partitions on that hard drive are referred to by a number, so hda1 is the first partition on the first hard drive, hdb1 is the first partition on the second hard drive. What should have been entered in the mount command was /dev/hd followed by a letter and a number. Step four was to find out which partition was the root partition. Here is my result from fdisk -l: Quote:
Note also in Step 7 the command is passwd root not password root, and in Step 8 it's umount /mnt, not unmount /mnt. I don't know how many times it took me to learn that one. I don't know if I picked up on any mistakes you may have made, but even if I'm way off base, this may help someone else. Good luck, and have fun! Edit: The quote screwed up the columns, and I don't know why; tried correcting once, ti didn't work, and now the cat wants out. I think you can figure out where the column breaks go. |
|
|||
|
bozo
I tried your method a couple of times, following it to the letter, and each time I got the same error as KnightWolfJK. I had previously attempted to reset root password as suggested by anomie and broch which was unsuccessful, and I don't know if that had anything to do with this method not working. Do you have any further suggestions? Thanks |
|
|||
|
Quote:
those steps are correct as with most distros i normally mount the partitions manually under /mnt then issue chroot. In the case of suse u have to mount /, /var/ and /usr; u also have to start the service random with the command /etc/init.d/random start. This is one the first services suse starts after loading the kernel. Hope that work elisa |
|
|||
|
Thanks elisa!
I attempted to do what you suggested, however when I executed "/etc/init.d/random start" the following line was shown: Initialzing random number generator/etc/init.d/random: line 40: /var/lib/misc/random-seed: No such file or directory chmod: cannot access '/var/lib/misc/random-seed': No such file of directory failed Now I'm not sure if I was doing what you suggested correctly. Would you post the complete syntax so that I can be sure? |
|
|||
|
Quote:
|
|
|||
|
Thanks!
Had to play around a bit, but I finally got it!
|
|
|||
|
Quote:
falcon would you mind posting exactly what you did to get things to work? I am stuck at same place you were in your previous post. Thanks! |
|
|||
|
I followed the steps posted by bozo, up to and including step 6.
I then entered the following:
|
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|