There are two main ways LIRC supports remotes.
One is just via a generic IR receiver. It's possible to "train" these to get a config file, or download one. These just list the pulse timings for each button.
The other means is via an event device - which is the likely mechanism of the remote you've got, since it already has an effect on your machine. This is where the kernel has a driver for this remote, and translates it's pulses into events.
The device is effectively plumbed in as an extra keyboard with some odd keys, some of which have bindings in X. You can use LIRC to add extra bindings to such a device via it's evdev (event device) module.
lsmod | grep evdev
And see if the evdev module is loaded - this is often in response to one of these remote receivers. The kernel drivers for these modules usually map the events to the standard set of key codes. Some of the keys might even be in the usual keymap - the remotes I have produce the correct keycodes for numerics, enter, etc - and you can see them inputting keys into applications like any other HID keyboard.
try working out which /dev/input/eventN device your remote is - try looking through your
dmesg output ; e/g/
dmesg | grep event
Then run one of the LIRC debug tools, irw
irw /dev/input/eventN # should produce a list of button identifiers when you point and shoot. Once you have this working ...
From here you can configure LIRC to receive certain button presses and send other keys to applications. I have a mixed setup for MythTV - some of the buttons are the values I'd want anyway (OK == ENTER, 0-9, etc) some of them I remap in LIRC (STOP == d for delete).