public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Elble <elbles@sessys.com>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: Using xfsdump On Linux With IRIX Version 1 FS?
Date: Fri, 24 Jul 2009 11:36:31 -0400	[thread overview]
Message-ID: <C68F4D3F.B931%elbles@sessys.com> (raw)
In-Reply-To: <20090724073030.GA15785@citd.de>


[-- Attachment #1.1: Type: text/plain, Size: 2160 bytes --]

On 7/24/09 3:30 AM, "Matthias Schniedermeyer" <ms@citd.de> wrote:

>> 
>> Looks like the version 1 directory code was removed as of June 15th, 2006,
>> per this:
>> 
>> http://oss.sgi.com/archives/xfs/2006-06/msg00067.html
>> 
>> But another post <http://oss.sgi.com/archives/xfs/2003-07/msg00495.html> has
>> a 2.4.21 kernel being used with a patch, so I'm not sure if I want to try a
>> 2.6 kernel, or see if I can patch together a 2.4.x kernel on an old FC4 box
>> I have laying around.  Truth be told, it's a lot of work just to blank the
>> entries in /etc/shadow so I can login to a 150 MHz box again, so who knows
>> if I'll even try at this point, hah.
>> 
>> In any event, thanks a lot for the pointers in the right direction.
> 
> I'd guess the disc isn't very big.
> 
> You just dd it completly (for backup).
> 
> Then search for the content of the shadow-file and blank out the entry
> with a hex-editor. Make sure that you don't change the filesize, pad
> the previous/following entry with any character you have to remove.

Right, the disk is only 2 GB.  Presumably, to back the disk up, all I'd have
to do would be something like:

    dd if=/dev/sda of=IRIXbackup

Correct?  No need to specify bs or count, I presume...

Then, I could use hexedit in the following manner to edit the disk:

    hexedit -d -f /dev/sda

I suppose I could search for the encrypted password string itself, but as
Chris Wedgwood suggested, I might be better off finding the offset of the
/etc/shadow file by doing something like the following:
    
    xfs_ncheck /dev/sda | grep /etc/shadow

I'm not sure if I can use the inode number directly as an offset or not, but
I *think* I could use it in conjunction with a xfs_db convert command to get
something usable as an offset.  Something like the following, perhaps?

    xfs_db -c convert inode <inode from xfs_ncheck command> daddr /dev/sda

My apologies for all the questions, but I've never tried this before, and I
don't particularly feel like messing it up, even with a backup of the FS
available.  Many thanks to Andi Kleen and Chris Wedgwood, in addition to
Eric Sandeen and Matthias Schniedermeyer.

-Sean

[-- 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

  reply	other threads:[~2009-07-24 15:35 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 [this message]
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
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=C68F4D3F.B931%elbles@sessys.com \
    --to=elbles@sessys.com \
    --cc=ms@citd.de \
    --cc=sandeen@sandeen.net \
    --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