Recent changes to feature-requests

Add support for High Sierra CD-ROMs

2010-06-03T16:48:37Z

Hi,

Is anyone interested in adding support for CD-ROMs which use the High Sierra filesystem? High Sierra is the predecessor to ISO 9660, and is (as I understand it) mostly similar.

Currently disktype does not recognise High Sierra discs; example output for the one High Sierra disc that I have:
--- /dev/sr0
Block device, size 286.7 MiB (300609536 bytes)
CD-ROM, 1 track, CDDB disk ID 0207A501
Track 1: Data track, 286.7 MiB (300609536 bytes)

I could provide an image file of the High Sierra disc if anyone wants to implement this.

Support for big-endian data?

2010-05-16T10:47:37Z

I just tried to run disktype on a disk from a NetBSD system (I think). There should be a disklabel and a FFS file system, byt disktype could not recognize them.

After a while it dawned on me that the magic number of the disklabel was in big-endian format instead of litte-endian as expected. I suspecxt the disklabel is created in a struct in-core and then just written -- so byte-reordering of these fields should probably be expected.

ext4 and maybe btrfs support

2009-04-02T14:08:15Z

Hi Christoph,

Any chance we can expect ext4 support in the nearest future?

Thanks,
Aldas

Print offset positions

2007-02-13T06:57:52Z

(Awesome tool - thank you!)

One thing that would seriously improve the utility of the utility would be if it printed out (where applicable) the offset in the file where each entity begins.

I believe that would allow one to do something like this:

losetup -o <offset> -t <type> /dev/loop0 <filename>

The program's current output does not make <offset> particularly clear, so while it is the case that one can see the various structures in the file, one must do something like scan the file again to find the offset.

Sector numbers

2006-10-31T20:32:27Z

First of all, disktype is a great tool already. =)

I would like to see one new feature though: sector
numbers of partitions, and especially file systems
within an LVM volume could be displayed more clearly.

For example, I'm able to see the starting sector of an
LVM partition directly ("xxx sectors from xxxx+63), but
the starting point of an ext3 file system within this
LVM volume is expressed as "starts at 64 KiB". It's not
a huge task to take a calculator and find out the
starting sector, but it would be a lot easier if
disktype would show it directly.

Another nice addition would be a simple "this partition
/ volume / whatever is spread among sectors xxx-xxxxxx".

Cheers!

- Jyri <jyri@q-olio.net>

read from stdin

2005-08-14T10:15:10Z

disktype does not appear to be able to read from stdin:

dd if=/dev/mapper/vg01-tmp bs=512 count=1 | disktype
Usage: disktype <device/file>...

dd if=/dev/mapper/vg01-tmp bs=512 count=1 | disktype -
disktype: Can't stat -: No such file or directory

"End of disc" calculation

2005-05-24T10:23:03Z

I suggest that disktype should display where the "end"
of the disc is. This would be calculated as where the
last partition ends.

If you use the "isosize" command on a hybrid
ISO9660/HFS disc, the length reported by isosize is
much shorter than the "real" length of the disc,
because this doesn't take into account the HFS
partition (which is located after the ISO9660 partition).

As disktype scans through each partition, it could keep
track of where each partition ends, so that it could
display the "real" end of the disc. (This wouldn't be
too difficult as you already work out the start and
length of each partition.)

This would be useful (e.g.) when ISO images are copied
to a hard drive - running disktype would show the real
extent of the data, and this value could be compared to
the length of the image file to ensure all the data has
been copied.

Or, to put it another way - it would make disktype into
a more accurate (and verbose) version of isosize!

reiser4

2004-12-18T05:46:10Z

Any plans to add reiser4 detection?

pharon@gmail.com