Frank Batschulat wrote: > So lets repeat what I said to this proposal on the ufs-discuss list: > > >> A lot of what you want to do can already be done via >> fstyp -v and fsdb_ufs(1M). If you want to extend mdb, >> > > actually not. > > 1) What are the things fsdb lacks in? > > It is very buggy, and has very difficult user interface. Adding > support for any new UFS features has usually resulted in breaking one > or more of its other aspects. The fsdb logging support is a shining > example of that and is broken in a couple of places actually. > I completely agree with you about the user interface. Every time I want to use it, I need to look at the examples on the man page. As for fstyp, it is also sub-optimal as it is not interactive and basically gives you all or none. I still think adding the ability in mdb of using ctf information with the raw disk is much more generally applicable, and would give you (actually, me) most of what I need. Then a few dcmds and walkers to give me summary info and I''ve got everything I need to examine not only ufs, but zfs as well on the disk. My view is that there is a perfectly good tool, mdb, that with a little work could be made to examine structures on raw disk very similar to what it does right now with memory.
max
