Re: TO recover passewd, i need ur help!~~
- From: bv@xxxxxxx (Bill Vermillion)
- Date: Wed, 25 Jan 2006 20:55:01 GMT
In article <qY6dnc7NkPAKKErenZ2dnUVZ_sWdnZ2d@xxxxxxxxxxx>,
Tony Lawrence <foo@xxxxxxxxxx> wrote:
>Brian K. White wrote:
>> ----- Original Message -----
>> From: "Stuart" <stnking@xxxxxxxxx>
>> Newsgroups: comp.unix.sco.misc
>> To: <distro@xxxxxxx>
>> Sent: Tuesday, January 24, 2006 8:18 PM
>> Subject: TO recover passewd, i need ur help!~~
>>
>>
>>
>>>to recover password of SCO UNIX OPENSERVER5..0.7.
>>>i tried to boot from boot floppy and edit the passwd file.
>>>but ,after i booting ,i cannot mount harddisk on ...i know that its
>>>bcuz the harddisk is installed on an SCSI card...
>>>so i download lsil.btld.img file from the SCO website, use
>>>/images/floppycp.exe to make the btld floppy in windows.
>>>and then, type defbootstr link=lsil at the "boot::" prompt ...
>>>but :
>>>
>>>-----------------------------------------------------------------
>>> bootlocore: out of low(below 1Mb) memmory
>>> No memmory for string table
>>> No(or cannot load)kernel hd(40)unix symbol table
>>> link failed, press <enter> or
>>>..............................................
>>>
>>>-------------------------------------------------------------------
>>>i dont even know what to do next............HELPPP!
>>>i really need your help.thanks much!
>>>
>>>and,also,when u type link=lsil.....how the machine knows where to find
>>>it whityout a path??
>>
>>
>> Boot from the sco install floppy not one you made with mkdev fd or scoadmin.
>> The installation media kit includes a floppy, and the install cd includes an
>> image of the same floppy, or you could just boot the install cd directly.
>> At the boot prompt type this (everything after "boot:")
>> boot: defbootstr link=lsil Sdsk=lsil(0,0,0,0)
>>
>> Assuming the main disk is on lsil adapter 0, bus 0, id 0, lun 0,
>>
>> And, are you sure your card uses the lsil driver? Various LSI cards use
>> other drivers such as amird and slha.
>>
>> Also, this starts an installation but you break out if the install script to
>> a shell.
>> See: http://wdb1.sco.com/kb/showta?taid=105094
>> Those are 5.0.6 instructions and I don't know if I ever tried it in 507
>> media so it's possible it won't work.
>> However, media that does work is downloadable!
>>
>> See Tony Lawrences nice web site for details and lot's of help with this
>> very common problem.
>> http://aplawrence.com/Unixart/lost_root_password.html
>>
>> Brian K. White -- brian@xxxxxxxxx -- http://www.aljex.com/bkw/
>> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
>> filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!
>>
>>
>>
>>
>
>I had this problem just the other day but happened to notice
>that there were ancient Lonetar diskettes mixed in with all the
>other disorganized junk. There were also Microlite disks, so
>obviously somebody was trying out both at one time. So at the
>hard drive boot I tried "airbag" and, yup, it was installed,
>and from there you just exit to a shell, mount /dev/root under
>/mnt and proceed to edit the password fields out of shadow and
>tcb/files/auth/r/root
A question.
Why did you just not chroot under the mount point and then
just run passwd? I've always found that quicker and you don't have
to edit the shadow files, etc. As it does things in an orderly
fashion.
>That "airbag" on the hard drive is quite handy - of course it's
>also a serious security risk if someone has physical access
>to the machine. But heck, physical access means all bets off
>anyway. Always worth a try - this customer didn't even know he
>was running that software - and may not even be, but somebody
>installed it some time in the past anyway, and it worked.
That's the problem with the Intel based hardware. In the
proprietary Unix environments many had firmware passwords, while
in the Intel environment you can often get to the BIOS and start
from there.
I vaguely recall on an AT&T 3B2-310 when that password was
forgotten you had to open the case, move a jumper, wait a few
seconds for the NVRAM to be cleared, put it bac, and then
re-assemble the case. And some of these had loops for locks
and/or security cables. So if someone goes through those you have
more than just a normal security problem - or there is a bit of
industrial espionage at hand.
>So I was able to fix that rather quickly - and was tempted to say
>S"Hi Ho ilver and away!" as I left :-)
So you ARE that masked man?
Bill
--
Bill Vermillion - bv @ wjv . com
.
- Follow-Ups:
- Re: TO recover passewd, i need ur help!~~
- From: Tony Lawrence
- Re: TO recover passewd, i need ur help!~~
- References:
- TO recover passewd, i need ur help!~~
- From: Stuart
- Re: TO recover passewd, i need ur help!~~
- From: Brian K. White
- Re: TO recover passewd, i need ur help!~~
- From: Tony Lawrence
- TO recover passewd, i need ur help!~~
- Prev by Date: Install OSR 6
- Next by Date: Re: TO recover passewd, i need ur help!~~
- Previous by thread: Re: TO recover passewd, i need ur help!~~
- Next by thread: Re: TO recover passewd, i need ur help!~~
- Index(es):
Relevant Pages
|