1. 14 2月, 2008 1 次提交
  2. 09 2月, 2008 4 次提交
  3. 08 2月, 2008 4 次提交
  4. 03 2月, 2008 2 次提交
  5. 30 11月, 2007 1 次提交
    • P
      The namespaces compatibility list doc · 2868f89f
      Pavel Emelyanov 提交于
      People discuss how the namespaces are working/going-to-work together.
      
      Ted Ts'o proposed to create some document that describes what problems user
      may have when he/she creates some new namespace, but keeps others shared.
      I liked this idea, so here's the initial version of such a document with
      the problems I currently have in mind and can describe somewhat audibly -
      the "namespaces compatibility list".
      
      The Documentation/namespaces/ directory is about to contain more docs about
      the namespaces stuff.
      
      Thanks to Cedirc for notes and spell checks on the doc, to Daniel for
      additional info about IPC and User namespaces interaction and to Randy, who
      alluded me to using a spell checker before sending the documentation :)
      Signed-off-by: NPavel Emelyanov <xemul@openvz.org>
      Cc: Randy Dunlap <randy.dunlap@oracle.com>
      Cc: Daniel Lezcano <dlezcano@fr.ibm.com>
      Cc: Theodore Tso <tytso@mit.edu>
      Cc: Cedric Le Goater <clg@fr.ibm.com>
      Cc: "Eric W. Biederman" <ebiederm@xmission.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      2868f89f
  6. 20 11月, 2007 1 次提交
  7. 17 10月, 2007 2 次提交
  8. 10 10月, 2007 2 次提交
  9. 12 9月, 2007 1 次提交
  10. 17 7月, 2007 1 次提交
  11. 04 12月, 2006 1 次提交
  12. 23 9月, 2006 1 次提交
    • P
      [NetLabel]: documentation · 8802f616
      Paul Moore 提交于
      Documentation for the NetLabel system, this includes a basic overview
      of how NetLabel works, how LSM developers can integrate it into their
      favorite LSM, as well as documentation on the CIPSO related sysctl
      variables.  Also, due to the difficulty of finding expired IETF
      drafts, I am including the IETF CIPSO draft that is the basis of the
      NetLabel CIPSO implementation.
      Signed-off-by: NPaul Moore <paul.moore@hp.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8802f616
  13. 19 11月, 2005 2 次提交
  14. 11 9月, 2005 1 次提交
  15. 10 9月, 2005 1 次提交
  16. 26 6月, 2005 1 次提交
    • V
      [PATCH] kdump: Documentation for Kdump · b089f4a6
      Vivek Goyal 提交于
      This patch contains the documentation for the kexec based crash dump tool.
      
      Quick kdump-howto
      ================================================================
      
      1) Download and build kexec-tools.
      
      2) Download and build the latest kexec/kdump (-mm) kernel patchset.
         Two kernels need to be built in order to get this feature working.
      
        A) First kernel:
         a) Enable "kexec system call" feature:
      	CONFIG_KEXEC=y
         b) Physical load address (use default):
      	CONFIG_PHYSICAL_START=0x100000
         c) Enable "sysfs file system support":
      	CONFIG_SYSFS=y
         d) Boot into first kernel with the command line parameter "crashkernel=Y@X":
            For example: "crashkernel=64M@16M".
      
        B) Second kernel:
         a) Enable "kernel crash dumps" feature:
      	CONFIG_CRASH_DUMP=y
         b) Physical load addreess, use same load address as X in "crashkernel"
            kernel parameter in d) above, e.g., 16 MB or 0x1000000.
      	CONFIG_PHYSICAL_START=0x1000000
         c) Enable "/proc/vmcore support" (Optional, in Pseudo filesystems).
      	CONFIG_PROC_VMCORE=y
      
      3) Boot into the first kernel.
      
      4) Load the second kernel to be booted using:
      
         kexec -p <second-kernel> --crash-dump --args-linux --append="root=<root-dev>
         maxcpus=1 init 1"
      
      5) System reboots into the second kernel when a panic occurs. A module can be
         written to force the panic, for testing purposes.
      
      6) See Documentation/kdump.txt for how to read the first kernel's
         memory image and how to analyze it.
      Signed-off-by: NHariprasad Nellitheertha <hari@in.ibm.com>
      Signed-off-by: NEric Biederman <ebiederm@xmission.com>
      Signed-off-by: NVivek Goyal <vgoyal@in.ibm.com>
      Signed-off-by: Nrandy_dunlap <rdunlap@xenotime.net>
      Signed-off-by: NManeesh Soni <maneesh@in.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      b089f4a6
  17. 06 5月, 2005 1 次提交
  18. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4