Kconfig.char 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124
  1. menu "UML Character Devices"
  2. config STDERR_CONSOLE
  3. bool "stderr console"
  4. default y
  5. help
  6. console driver which dumps all printk messages to stderr.
  7. config SSL
  8. bool "Virtual serial line"
  9. help
  10. The User-Mode Linux environment allows you to create virtual serial
  11. lines on the UML that are usually made to show up on the host as
  12. ttys or ptys.
  13. See <http://user-mode-linux.sourceforge.net/old/input.html> for more
  14. information and command line examples of how to use this facility.
  15. Unless you have a specific reason for disabling this, say Y.
  16. config NULL_CHAN
  17. bool "null channel support"
  18. help
  19. This option enables support for attaching UML consoles and serial
  20. lines to a device similar to /dev/null. Data written to it disappears
  21. and there is never any data to be read.
  22. config PORT_CHAN
  23. bool "port channel support"
  24. help
  25. This option enables support for attaching UML consoles and serial
  26. lines to host portals. They may be accessed with 'telnet <host>
  27. <port number>'. Any number of consoles and serial lines may be
  28. attached to a single portal, although what UML device you get when
  29. you telnet to that portal will be unpredictable.
  30. It is safe to say 'Y' here.
  31. config PTY_CHAN
  32. bool "pty channel support"
  33. help
  34. This option enables support for attaching UML consoles and serial
  35. lines to host pseudo-terminals. Access to both traditional
  36. pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled
  37. with this option. The assignment of UML devices to host devices
  38. will be announced in the kernel message log.
  39. It is safe to say 'Y' here.
  40. config TTY_CHAN
  41. bool "tty channel support"
  42. help
  43. This option enables support for attaching UML consoles and serial
  44. lines to host terminals. Access to both virtual consoles
  45. (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and
  46. /dev/pts/*) are controlled by this option.
  47. It is safe to say 'Y' here.
  48. config XTERM_CHAN
  49. bool "xterm channel support"
  50. help
  51. This option enables support for attaching UML consoles and serial
  52. lines to xterms. Each UML device so assigned will be brought up in
  53. its own xterm.
  54. It is safe to say 'Y' here.
  55. config NOCONFIG_CHAN
  56. bool
  57. default !(XTERM_CHAN && TTY_CHAN && PTY_CHAN && PORT_CHAN && NULL_CHAN)
  58. config CON_ZERO_CHAN
  59. string "Default main console channel initialization"
  60. default "fd:0,fd:1"
  61. help
  62. This is the string describing the channel to which the main console
  63. will be attached by default. This value can be overridden from the
  64. command line. The default value is "fd:0,fd:1", which attaches the
  65. main console to stdin and stdout.
  66. It is safe to leave this unchanged.
  67. config CON_CHAN
  68. string "Default console channel initialization"
  69. default "xterm"
  70. help
  71. This is the string describing the channel to which all consoles
  72. except the main console will be attached by default. This value can
  73. be overridden from the command line. The default value is "xterm",
  74. which brings them up in xterms.
  75. It is safe to leave this unchanged, although you may wish to change
  76. this if you expect the UML that you build to be run in environments
  77. which don't have X or xterm available.
  78. config SSL_CHAN
  79. string "Default serial line channel initialization"
  80. default "pty"
  81. help
  82. This is the string describing the channel to which the serial lines
  83. will be attached by default. This value can be overridden from the
  84. command line. The default value is "pty", which attaches them to
  85. traditional pseudo-terminals.
  86. It is safe to leave this unchanged, although you may wish to change
  87. this if you expect the UML that you build to be run in environments
  88. which don't have a set of /dev/pty* devices.
  89. config UML_SOUND
  90. tristate "Sound support"
  91. help
  92. This option enables UML sound support. If enabled, it will pull in
  93. soundcore and the UML hostaudio relay, which acts as a intermediary
  94. between the host's dsp and mixer devices and the UML sound system.
  95. It is safe to say 'Y' here.
  96. config SOUND
  97. tristate
  98. default UML_SOUND
  99. config SOUND_OSS_CORE
  100. bool
  101. default UML_SOUND
  102. config HOSTAUDIO
  103. tristate
  104. default UML_SOUND
  105. endmenu