Slackbuilds.org: dosbox not available for Slackware 13?
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
No, I cannot find it Slackware 13, only Slackware 12.2
Maybe it has something to do with this. Dosbox is likely to want CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR=0.
Tue Aug 18 18:50:46 CDT 2009
Patched kernels and kernel packages for Linux 220.127.116.11 to address
a bug in proto_ops structures which could allow a user to use the
kernel sendpage operation to execute arbitrary code in page zero.
This could allow local users to gain escalated privileges.
This flaw was discovered by Tavis Ormandy and Julien Tinnes of the
Google Security Team.
For more information, see: http://cve.mitre.org/cgi-bin/cvename...=CVE-2009-2692
In addition, these kernels change the CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR
kernel config option value to 4096, which should prevent the execution
of arbitrary code by future NULL dereference bugs that might be found
in the kernel. If you are compiling your own kernel, please check this
option in your .config. If it is set to =0, you may wish to edit it
to 4096 (or some other value > 0) and then reconfigure, or the kernel
will not have default protection against zero page attacks from
(* Security fix *)
Then again, maybe not. There is a recent build for Slackware64 on AlienBob's wiki.