| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-id: <45B1895F.1090206@shaw.ca> Date: Fri, 19 Jan 2007 21:15:43 -0600 From: Robert Hancock <hancockr@...w.ca> To: Sunil Naidu <akula2.shark@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: Missing dmesg parameters in 2.6.19.2 Sunil Naidu wrote: > Hello All, > > Atlast I have succeeded in booting 2.6.19.2 on mutiple x86 machines. I > did observe a strange dmesg parameter behavior in this case:- > > > 1) Compiling with SMP as Generic (CONFIG_X86_PC is not set, CONFIG_M686=y) > > ........ > ........ > Using x86 segment limits to approximate NX protection > ........ > ........ > Using APIC driver default > ........ > ........ > > 2) Compiling with SMP as Processor specific (CONFIG_X86_PC=y, > CONFIG_MPENTIUM4=y) > > I do not find the above mentioned parameters in this case. I don't think the "segment limits" message shows up in stock kernels, are you sure that was from 2.6.19.2? That sounds like a Fedora kernel with Exec Shield. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from hancockr@...pamshaw.ca Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists