I am replying to the list, since we had some personal conversation with klaatu recently and the problem seems solved (well, probably not solved yet, but we discovered what is the reason for it).
So the list should know about it, in order to let other people know that an answer is probably no longer needed. The answer to klaatu's question is: make sure the newly compiled (and patched) kernel is actually the one which you're booting: uname -a or cat /proc/version if you prefer Also, if you are using LILO, rerun it to make sure it picks the new kernel. Tomas M On Thu, Aug 30, 2012 at 4:35 AM, klaatu <kla...@rocketship.com> wrote: > Hello > > I am trying to install aufs in slackware64 13.37, for a livecd project. > Although installation proceeds without apparent difficulty, the > resulting module will not load, for unknown symbols. > > I know aufs2 is an older and now unmaintained version, but this is the > linux dist & kernel I am using so these are the aufs files that appear > to be necessary. > > Any help with resolving this would be deeply appreciated. The files & > procedure used are given below. > > Kind Regards, > Mishma > >.... > dmesg > .... > [ 176.499991] aufs: Unknown symbol __lookup_one_len (err 0) > [ 176.500868] aufs: Unknown symbol file_sb_list_del (err 0) > [ 176.501160] aufs: Unknown symbol do_splice_to (err 0) > [ 176.501241] aufs: Unknown symbol security_inode_permission (err 0) > [ 176.501434] aufs: Unknown symbol security_file_mmap (err 0) > [ 176.501681] aufs: Unknown symbol inode_lock (err 0) > [ 176.501869] aufs: Unknown symbol devcgroup_inode_permission (err 0) ... ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
