Since raw1394 access can't really be given to users, we have to find some sort of workaround that makes itself obvious.
How about the possibility of policykit integration (I know that can't be done for hardy)?
We could have a better error message with instructions when /dev/raw1394 exists, but isn't accessible.
Maybe using a separate group for the device, and presenting the user with instructions on which group they need to be added to during package installation (since it's not in by default).
Note that adding the user to the "disk" group didn't work on hardy (as of 4/21/08).