search for: device_t

2011/6/27 Frederic BOHE <fbohe-guest at alioth.debian.org> > Author: fbohe-guest > Date: Mon Jun 27 13:56:51 2011 > New Revision: 3060 > URL: http://trac.networkupstools.org/projects/nut/changeset/3060 > > Log: > Add NUT server scan. > > (...) > device_t * scan_snmp(char * start_ip, char * stop_ip,long usec_timeout, > snmp_security_t * sec); > > device_t * scan_usb(); > > device_t * scan_xml_http(long usec_timeout); > > +device_t * scan_nut(char * startIP, char * stopIP, char * port); > for the sake of coherence and compl...

...y /bin/mknod: `/dev/net/tun': Operation not permitted /bin/mknod: `/dev/ppp': Operation not permitted /bin/mknod: `/dev/fuse': Operation not permitted /sbin/start_udev: line 269: /proc/sys/kernel/hotplug: Read-only file system udevd[71]: file_contexts:  invalid context system_u:object_r:device_t:s0 udevd[71]: file_contexts:  invalid context system_u:object_r:device_t:s0 udevd[71]: matchpathcon(/dev/.udev/rules.d) failed udevd[71]: matchpathcon(/dev/.udev/rules.d) failed                                                            [  OK  ] Setting hostname vm1292ussac1-goagent1.cust.aops-ed...

Hello! I have an old Dell Latitude C800 laptop (with Pentium3 CPU in it). FreeBSD 6.3-STABLE was running fine on it, but I decided to update the machine to 9.1-STABLE. Well, neither my own custom kernel, nor even the official 9.1-RELEASE CD1 would boot... In both cases the boot process runs up to detecting uhub0, then either hangs forever or shuts off after a short while. Again, I thought I

Daniel P. Berrangé <berrange@redhat.com> writes: > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >> Hi, >> > >> I've met two situations with NVDIMM support in libvirt where I'm not >> sure all the parties (libvirt & I) do the things correctly. >> >> The first problem is with memory alignment and size changes. In

...to client 192.168.0.56. Error Connection reset by peer syslog(kern.debug): May 22 16:57:37 server kernel: audit(1179827857.498:149): avc: denied { write } for pid=10734 comm="smbd" name="log" dev=tmpfs ino=24665 scontext=system_u:system_r:smbd_t:s0 tcontext=root:object_r:device_t:s0 tclass=sock_file Please, help. Philipp.

...net/tun': Operation not permitted > /bin/mknod: `/dev/ppp': Operation not permitted > /bin/mknod: `/dev/fuse': Operation not permitted > /sbin/start_udev: line 269: /proc/sys/kernel/hotplug: Read-only file system > udevd[71]: file_contexts:  invalid context system_u:object_r:device_t:s0 > udevd[71]: file_contexts:  invalid context system_u:object_r:device_t:s0 > > udevd[71]: matchpathcon(/dev/.udev/rules.d) failed > udevd[71]: matchpathcon(/dev/.udev/rules.d) failed You don't want to have udevd running in any container. The /dev filesystem for a container is...

...what and where is the problem exactly. The problem apparently is that /dev/dax* is a character device rather than a block device (such as /dev/pmem*), which is not expected by SELinux policy rules. This is an NVDIMM in fsdax mode: # ls -lZ /dev/pmem0 brw-rw----. 1 root disk system_u:object_r:device_t:s0 259, 0 Jul 9 11:39 /dev/pmem0 This is the same NVDIMM reconfigured as devdax: # ls -lZ /dev/dax0.0 crw-------. 1 root root system_u:object_r:device_t:s0 252, 5 Jul 9 11:43 /dev/dax0.0 (Unix permissions are different, but when I change them to `disk' group and 660, the same problem...

...:00.0 into 1x mode agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode audit(1172747921.184:6): avc: denied { getattr } for pid=2323 comm="pam_console_app" name="card0" dev=tmpfs ino=7969 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255tcontext=system_u:object_r:device_t:s0 tclass=chr_file Zapata Telephony Interface Registered on major 196 Zaptel Version: 1.2.14 Zaptel Echo Canceller: KB1 and finally this is my configuration fxsks=1-4 loadzone=us defaultzone=us -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/...

..._t:tcp_socket name_connect; allow chroot_user_t user_home_t:chr_file open; #============= syslogd_t ============== #!!!! The source type 'syslogd_t' can write to a 'dir' of the following types: # var_log_t, var_run_t, syslogd_tmp_t, syslogd_var_lib_t, syslogd_var_run_t, innd_log_t, device_t, tmp_t, logfile, cluster_var_lib_t, cluster_var_run_t, root_t, krb5_host_rcache_t, cluster_conf_t, tmp_t allow syslogd_t user_home_t:dir write; My questions are: Do SE booleans settings exist that permit chrooted ssh access to forward https and log the activity? If so then what are they? If n...

...* Bluetooth stack for FreeBSD (Netgraph implementation) * ACPI Status Report * AMD64 Porting * ATAPI/CAM Status Report * Binary security updates for FreeBSD * bsd.java.mk version 2.0 * Compile FreeBSD with Intels C compiler (icc) * Cryptographic Support * Device_t locking * Disk I/O * Dynamically Linked Root Support * FreeBSD Java Project * FreeBSD ports monitoring system * FreeBSD/ia64 * jpman project * KDE FreeBSD Project * kgi4BSD Status Report * KSE * Network Subsystem Locking and Performance * Porti...

...console.c @@ -69,11 +69,14 @@ struct mtx cn_mtx; static char wbuf[WBUF_SIZE]; static char rbuf[RBUF_SIZE]; static int rc, rp; -static unsigned int cnsl_evt_reg; +unsigned int cnsl_evt_reg; static unsigned int wc, wp; /* write_cons, write_prod */ xen_intr_handle_t xen_intr_handle; device_t xencons_dev; +/* Virt address of the shared console page */ +char *console_page; + #ifdef KDB static int xc_altbrk; #endif @@ -113,6 +116,9 @@ static struct ttydevsw xc_ttydevsw = { static void xc_cnprobe(struct consdev *cp) { + if (!xen_pv_domain()) + return; + cp->cn_pri = CN_REMOTE...

...(83.8 confidence) suggests ******************* If you want to allow systemd-readahe to have add_name access on the .readahead.new directory Then you need to change the label on .readahead.new Do # semanage fcontext -a -t FILE_TYPE '.readahead.new' where FILE_TYPE is one of the following: device_t, init_var_run_t, readahead_var_lib_t, readahead_var_run_t, root_t, var_run_t. Then execute: restorecon -v '.readahead.new' ***** Plugin catchall (17.1 confidence) suggests ************************** If you believe that systemd-readahe should be allowed add_name access on the .readahea...

Starting udev: /sbin/restorecon set context /dev/.initramfs/live->system_u:object_r:device_t:s0 failed:'Read-only file system' Resolves: rhbz#675868 Signed-off-by: Mike Burns <mburns at redhat.com> --- recipe/common-post.ks | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/recipe/common-post.ks b/recipe/common-post.ks index a17e899..cf5bc72 100644 -...

...ly manually. So I traced the problem to SE Linux. Specifically the context for /dev/mapper/VolGroup01-lv_ staff is wrong. s -lsahZ /dev/mapper/VolGroup01-* lrwxrwxrwx. root root system_u:object_r:quota_db_t:s0 /dev/mapper/VolGroup01-lv_staff -> ../dm-25 lrwxrwxrwx. root root system_u:object_r:device_t:s0 /dev/mapper/VolGroup01-lv_student -> ../dm-24 I have tried to correct this with the Logical Volume active and mounted using chcon -v --reference /dev/mapper/VolGroup01-lv_student /dev/mapper/VolGroup01-lv_staff and while this command completes the context is not changed. Can someone confir...

Hi all, Over the last month or so I've installed FreeBSD 9 (-stable) on several Mac Minis via the memstick image; they seem to be pretty good little boxes for things like offsite secondary nameservers, for example, and they're easily replaced in case of problems. However, the newest minis have slightly different hardware, and FreeBSD can't find the built-in NIC. pciconf -lv on the

These patches update the example FLASK policy shipped with Xen and enable its build if the required tools are present. The third patch requires rerunning autoconf to update tools/configure. [PATCH 1/3] flask/policy: sort dom0 accesses [PATCH 2/3] flask/policy: rework policy build system [PATCH 3/3] tools/flask: add FLASK policy to build

when booting stable/9 under a debug kernel with WITNESS enabled and verbose I get the following panic.. It seems very much like the discussion from a year back on current: http://lists.freebsd.org/pipermail/freebsd-current/2012-January/031375.html Any ideas? uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1 uhub0: 2 ports with 2 removable, self powered uhub1: 2

Hi. I experimented a bit with collecting entropy from the time it takes for device_attach() to run (in CPU cycles). It seems that those times have enough variation that we can use it for entropy harvesting. It happens even before root is mounted, so pretty early. On the machine I'm testing it, which has minimal kernel plus NIC driver I see 75 device_attach() calls. I'm being very careful

This patch set adds basic supports for amd next generation iommu (IOMMUv2) hardware. IOMMUv2 supports various new features advertised by iommu extended feature register. It introduces guest level IO translation and supports state-of-the-art ATS/ATC devices with demand paging capability. Please refer to AMD IOMMU Architectural Specification [1] for more details. Thanks, Wei [1]

Hi, I have been trying out a nice new tws controller and decided to enable debugging in the kernel and run some stress tests. With a regular GENERIC kernel, it boots up fine. But with debugging, it panics on boot. Anyone know whats up ? Is this something that should be sent directly to LSI ? pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0