For no reason aside from it being nice to at least acquaint one's self with the buzzwords - if not at some level of forced compunction make a half-hearted go of skiming through the terrifying guts of a big and complicated system you have already or have meritous reason to fear a long and soul-sucking betrothal to. In my case it's NetBSD under Xen, if you've been at all tracing the concerning trajectory my recently published articles are steadfastly committed to plough through arse-first with no feigned notion of expertise, as one does when one endeavours to endear from the blessedly beleagured-by-spitballs-and-wise-cracks back of the class from whence I clearly matriculated. Indeed, you have stumbled on another unclever attempt to snooker some SEO whilst also self-abasingly stretching my shameful, verbial pud - as they say in the old country.

acpi0: <Xen> debug0: <Xen debug handler> on xenpv0 evtchn0: <Xen event channel user-space device> on xenpv0 gntdev0: <Xen grant-table user-space device> on xenpv0 granttable0: <Xen Grant-table Device> on xenpv0 privcmd0: <Xen privileged interface user-space device> on xenpv0 xbd0: 20480MB <Virtual Block Device> at device/vbd/768 on xenbusb_front0 xctrl0: <Xen Control Device> on xenstore0 xenballoon0: <Xen Balloon Device> on xenstore0 xenbusb_back0: <Xen Backend Devices> on xenstore0 xenbusb_front0: <Xen Frontend Devices> on xenstore0 xen_et0: registered as a time-of-day clock, resolution 0.000001s xen_et0: <Xen PV Clock> on xenpv0 xenpci0: <Xen Platform Device> port 0xc000-0xc0ff mem 0xf4000000-0xf4ffffff irq 24 at device 2.0 on pci0 xenpv0: <Xen PV bus> xenstore0: <XenStore> on xenpv0 xn0: backend features:xn2: <Virtual Network Interface> at device/vif/2 on xenbusb_front0 xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_front0 xn1: <Virtual Network Interface> at device/vif/1 on xenbusb_front0 xn3: <Virtual Network Interface> at device/vif/3 on xenbusb_front0 xsd_dev0: <Xenstored user-space device> on xenpv0 xs_dev0: <Xenstore user-space device> on xenstore0

For the interested, one produces such a tidy amalgum by piping dmesg through a convoluted chain of cozy standbys we in the industry lean upon from time to time what'fer making one's shell scripts shine:

dmesg | grep xen > temp; dmesg | grep Xen >> temp; uniq temp | sort > temp

Then one naturally calls in nano, champion of the vim-emacs holy war, to put in the spit shine needed to weed out the straggling non-device-noded contestants in this wonderful game we call: how to make a vapid and keyword rich utterance before the kettle whistles. Medium, eat your goddamned heart out.