summaryrefslogtreecommitdiff
path: root/drivers/usb
diff options
context:
space:
mode:
authorThomas Stewart <thomas@stewarts.org.uk>2010-05-27 01:42:33 +0400
committerLinus Torvalds <torvalds@linux-foundation.org>2010-05-27 20:12:43 +0400
commitd27d7a9a7838587fcdcc6f2b042f5610eb4984a1 (patch)
tree1f54d3904a7a80cb483074478aaa36e72f60cd6b /drivers/usb
parentb8d6b0d6b6882a53e4586a07e1292223d55299d1 (diff)
downloadlinux-d27d7a9a7838587fcdcc6f2b042f5610eb4984a1.tar.xz
ufs: permit mounting of BorderWare filesystems
I recently had to recover some files from an old broken machine that was running BorderWare Document Gateway. It's basically a drop in web server for sharing files. From the look of the init process and using strings on of a few files it seems to be based on FreeBSD 3.3. The process turned out to be more difficult than I imagined, but to cut a long story short BorderWare in their wisdom use a nonstandard magic number in their UFS (ufstype=44bsd) file systems. Thus Linux refuses to mount the file systems in order to recover the data. After a bit of hunting I was able to make a quick fix to fs/ufs/super.c in order to detect the new magic number. I assume that this number is the same for all installations. It's quite easy to find out from ufs_fs.h. The superblock sits 8k into the block device and the magic number its 1372 bytes into the superblock struct. # dd if=/dev/sda5 skip=$(( 8192 + 1372 )) bs=1 count=4 2> /dev/null | hd 00000000 97 26 24 0f |.&$.| # Signed-off-by: Thomas Stewart <thomas@stewarts.org.uk> Cc: Evgeniy Dushistov <dushistov@mail.ru> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/usb')
0 files changed, 0 insertions, 0 deletions