From: Sean Elble <elbles@sessys.com>
To: Christian Kujau <lists@nerdbynature.de>,
Matthias Schniedermeyer <ms@citd.de>
Cc: xfs@oss.sgi.com
Subject: Re: Using xfsdump On Linux With IRIX Version 1 FS?
Date: Sat, 25 Jul 2009 20:24:18 -0400 [thread overview]
Message-ID: <C6911A72.B9D6%elbles@sessys.com> (raw)
In-Reply-To: <alpine.DEB.2.01.0907250241170.6426@bogon.housecafe.de>
[-- Attachment #1.1: Type: text/plain, Size: 2065 bytes --]
On 7/25/09 5:46 AM, "Christian Kujau" <lists@nerdbynature.de> wrote:
> On Sat, 25 Jul 2009 at 09:26, Matthias Schniedermeyer wrote:
>>> # losetup -r /dev/loop0 /path/to/IRIXbackup
>>> # hexedit /dev/loop0 ...or whatever tool you'll be using.
>>
>> Which has what advantage over directly changing the image?
>
> Sean mentioned the "thrashing of the old disk" and I figured I'd be
> worried not only by that but that the old disk might die anytime soon. So
> I wanted to present an alternative to do the search - I don't know too
> much about his setup, so it's up to him to follow this advice or not.
>
Well, I ended up dd'ing the old SCSI disk to a file on a spare Linux box I
have laying around for just this sort of purpose. I then opened the
resulting file up with hexedit, switched to ASCII mode, did a search for the
root password hash, and replaced it with a known hash for "blah."
DD'ed the image back to the disk, threw it back in the Indigo2, and booted.
I entered maintenace mode, ran sash, and cat'ed the /etc/shadow file. It
still had the old password. So, back to the image file I went. The
password string was in there multiple times, to the point where I lost
count. I should have thought of that the first time around, but I figured
once was good enough. Searched and replaced the string until the old string
wasn't in there anymore, reimaged the drive, put it back in the SGI, booted,
and voila: I can log in again.
The loopback method was a moot point, as the box I was using didn't have the
loopback driver compiled in or available as a module, so I never even tried
it. I'll definitely keep it in mind (and in my inbox) should another few
years go by and I can't remember the password again. :-)
Thanks so much for all the help guys, I really appreciate it.
-Sean
--
+-------------------------------------------------
| Sean Elble
| Virginia Tech, Class of 2009
| E-Mail: elbles@sessys.com
| Web: http://www.sessys.com/~elbles/
| Cell: 860.946.9477
+-------------------------------------------------
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2139 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-26 0:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 23:57 Using xfsdump On Linux With IRIX Version 1 FS? Sean Elble
2009-07-24 2:23 ` Eric Sandeen
2009-07-24 3:02 ` Sean Elble
2009-07-24 3:32 ` Sean Elble
2009-07-24 7:30 ` Matthias Schniedermeyer
2009-07-24 15:36 ` Sean Elble
2009-07-24 17:11 ` Matthias Schniedermeyer
2009-07-24 19:13 ` Sean Elble
2009-07-25 3:53 ` Christian Kujau
2009-07-25 7:26 ` Matthias Schniedermeyer
2009-07-25 9:46 ` Christian Kujau
2009-07-25 10:22 ` Matthias Schniedermeyer
2009-07-25 10:36 ` Christian Kujau
2009-07-25 16:25 ` Sean Elble
2009-07-26 0:24 ` Sean Elble [this message]
2009-07-24 8:23 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C6911A72.B9D6%elbles@sessys.com \
--to=elbles@sessys.com \
--cc=lists@nerdbynature.de \
--cc=ms@citd.de \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox