Searched full:like (Results 1 – 25 of 3196) sorted by relevance
12345678910>>...128
| /openbmc/openbmc/meta-security/dynamic-layers/meta-perl/recipes-security/bastille/files/ |
| H A D | config | 1 # Q: Would you like to enforce password aging? [Y]
7 # Q: What umask would you like to set for users on the system? [077]
11 # Q: Would you like to deactivate the Apache web server? [Y]
13 # Q: Would you like to password protect single-user mode? [Y]
19 # Q: Would you like to put limits on system resource usage? [N]
21 # Q: Would you like to set more restrictive permissions on the administration utilities? [N]
23 # Q: Would you like to disable SUID status for mount/umount?
25 # Q: Would you like to disable SUID status for ping? [Y]
27 # Q: Would you like to disable SUID status for traceroute? [Y]
33 # Q: Would you like to run the packet filtering script? [N]
[all …]
|
| /openbmc/linux/block/partitions/ |
| D | Kconfig | |
| /openbmc/u-boot/drivers/usb/eth/ |
| H A D | Kconfig | 4 Say Y here if you would like to enable support for USB Ethernet
13 Say Y here if you would like to support ASIX AX8817X based USB 2.0
20 Say Y here if you would like to support ASIX AX88179 based USB 3.0
28 Say Y here if you would like to support Microchip LAN75XX Hi-Speed
38 Say Y here if you would like to support Microchip LAN78XX USB 3.1
47 Say Y here if you would like to support MOSCHIP MCS7830 based
54 Say Y here if you would like to support Realtek RTL8152B/RTL8153 base
62 Say Y here if you would like to support SMSC LAN95xx based USB 2.0
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-ref-variables-context.rst | 10 should only be used in global files like ``.conf``, while others are intended only
11 for local files like ``.bb``. This chapter aims to describe some important variable
22 - System resources, like disk space to be used (:term:`BB_DISKMON_DIRS`),
36 - Like :term:`B` or :term:`T`, that are used to specify directories used by
38 specified in ``bitbake.conf``. Some, like :term:`B`, are quite often
46 data reuse between build runs like :term:`CACHE`, :term:`DL_DIR` or
85 a recipe like :term:`SRC_URI` or :term:`SRCDATE`. Those are also usually set
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| D | README | |
| /openbmc/openbmc/poky/meta/recipes-devtools/dnf/dnf/ |
| H A D | 0001-lock.py-fix-Exception-handling.patch | 7 like "Permission denied: '/var/log/log_lock.pid'", and in this case,
9 handled, it maybe cause log_lock.pid not be deleted in case like [1].
12 rootfs, seems like some threads don't do chroot like work, some threads
13 do chroot like work. so for the threads don't do chroot, "Permission denied"
18 So fixed like this, if _try_lock raise Exception, _unlock_thread first,
|
| /openbmc/linux/Documentation/trace/coresight/ |
| D | coresight-perf.rst | |
| /openbmc/u-boot/doc/ |
| H A D | README.console | 53 fputc (like putc but redirected to a file)
54 fputs (like puts but redirected to a file)
55 fprintf (like printf but redirected to a file)
56 ftstc (like tstc but redirected to a file)
57 fgetc (like getc but redirected to a file)
74 some parameters like the framebuffer descriptors are passed to the
|
| H A D | README.hwconfig | 10 interface for Award BIOS-like interface, and frame-buffer
11 interface for AMI GUI[1] BIOS-like interface with mouse
37 experience by adding more mature interfaces, like a hwconfig
47 into reduced mode (like RMII-only interface for ethernet,
|
| /openbmc/linux/Documentation/kbuild/ |
| D | kconfig-macro-language.rst | |
| /openbmc/linux/include/uapi/linux/ |
| D | sound.h | |
| D | if_vlan.h | |
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| D | libv4l-introduction.rst | |
| /openbmc/qemu/util/ |
| H A D | qemu-print.c | 18 * Print like vprintf().
31 * Print like printf().
46 * Print like vfprintf()
58 * Print like fprintf().
|
| H A D | error-report.c | 182 * Format arguments like vsprintf(). The resulting message should be
221 * Format arguments like vsprintf(). The resulting message should be
233 * Format arguments like vsprintf(). The resulting message should be
245 * Format arguments like vsprintf(). The resulting message should be
256 * Format arguments like sprintf(). The resulting message should be
272 * Format arguments like sprintf(). The resulting message should be a
288 * Format arguments like sprintf(). The resulting message should be a
302 * Like error_report(), except print just once.
322 * Like warn_report(), except print just once.
|
| /openbmc/linux/Documentation/sound/designs/ |
| D | oss-emulation.rst | |
| /openbmc/linux/Documentation/core-api/ |
| D | asm-annotations.rst | |
| D | packing.rst | |
| /openbmc/linux/Documentation/ABI/stable/ |
| D | sysfs-devices-system-cpu | |
| /openbmc/u-boot/drivers/reset/aspeed/ |
| H A D | Kconfig | 9 is that some reset signals, like I2C or MISC reset multiple devices.
19 is that some reset signals, like I2C or MISC reset multiple devices.
29 is that some reset signals, like I2C or MISC reset multiple devices.
|
| /openbmc/linux/scripts/ |
| D | rustdoc_test_builder.rs | |
| /openbmc/linux/drivers/staging/media/atomisp/pci/runtime/isp_param/interface/ |
| D | ia_css_isp_param_types.h | |
| /openbmc/linux/arch/loongarch/include/asm/ |
| D | uaccess.h | |
| /openbmc/linux/samples/trace_events/ |
| D | trace_custom_sched.h | |
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libtext/ |
| H A D | libtext-wrapi18n-perl_0.06.bb | 8 on terminal, like diacritical marks in UTF-8) and fullwidth characters \
9 (which occupy two columns on terminal, like most of east Asian \
11 whitespaces between words (like Chinese and Japanese) is supported."
|
12345678910>>...128