linux - Export Command -- Intended Effect? - Super User

in faq article on amsn, states if have amsn "hang up" , have configured of sound options correctly try running amsn command: export ld_assume_kernel=2.2.5 && amsn

now, question effect have on system? linux newbie, not sure how system react , if command idea.

if export affect amsn, giving shot. seeing nature of linux commands (rm -rf anyone?) , how disastrous , unforgiving can if don't know you're doing, reluctant try it, if 'official' source. not want lose performance or similar make amsn work -- i'd rather take occasional hang amsn.

export ld_assume_kernel=2.2.5 setting shell environment variable $ld_assume_kernel 2.2.5. programs use environment variables configure various aspects of (like $term variable shell indicates type of terminal should emulate) , can relatively harmless. (i can because variables important, $path variable , $ps1)

if want see if $ld_assume_kernel set before running amsn, open terminal (like konsole or terminal) , type echo $ld_assume_kernel @ prompt. if blank line produced $ld_assume_kernel unset , amsn defaults settings , setting let amsn whatever variable. if set, you'll replacing whatever there 2.2.5 when run amsn.

off top of head don't recognize ld_assume_kernel variable believe should safe running it. if happen can reboot since export command doesn't persist across reboots. (the system , personal profile scripts set on every boot , login)