search for: nodevice

Hi, Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled This is stripped down kernel with everything possible loaded from modules. Any ideas? Did not see any warnings in UPDATING... ./danfe

...talled as kernel module by using the Ports Collection (emulators/virtio-kmod). To use it on 8.4-RELEASE, the GENERIC kernel has to be recompiled by removing all of the virtio(4) drivers before installing emulators/virtio-kmod. The following lines in kernel configuration file disable the drivers: nodevice virtio nodevice virtio_pci nodevice vtnet nodevice virtio_blk nodevice virtio_scsi nodevice virtio_balloon After recompilation and installing the new kernel and emulators/virtio-kmod, add the following lines to /boot/loader.conf. This enab...

...s") : ... these options can be set on a per-mount basis using the -o option, without affecting the property that is stored on disk. The values specified on the command line will override the values stored in the dataset. The -nosuid option is an alias for "nodevices,nosetuid". These proper- ties are reported as "temporary" by the "zfs get" command. TEST 26.07.2007 Forensic mounting of ZFS File Systems. Loopback device does not seem to work with ZFS using "zfs mount" or legacy "mount". However, tempora...

...s") : ... these options can be set on a per-mount basis using the -o option, without affecting the property that is stored on disk. The values specified on the command line will override the values stored in the dataset. The -nosuid option is an alias for "nodevices,nosetuid". These proper- ties are reported as "temporary" by the "zfs get" command. TEST 26.07.2007 Forensic mounting of ZFS File Systems. Loopback device does not seem to work with ZFS using "zfs mount" or legacy "mount". However, tempora...

...to send logs via UDP directly to a syslog server. It seems to me that the benefits of this approach include: 1. No need to setup /dev/log in every chroot. This is a huge plus for anyone dealing with a large number of chrooted users or in environments where the underlying filesystem has the "nodevices" flag set (I have both). 2. The logs are sent directly from the application, with no reliance on the syslogd of the host OS. For users that have separation of responsibilities, having logs go directly to a syslog server maintained by a separate group is a plus since it's more difficult...

...SEXP args, SEXP env) > { > checkArity(op, args); > ! inhibitDisplayList(CurrentDevice()); > return R_NilValue; > } > > --- 52,60 ---- > SEXP do_devcontrol(SEXP call, SEXP op, SEXP args, SEXP env) > { > checkArity(op, args); > ! if(!NoDevices()){ > ! inhibitDisplayList(CurrentDevice()); > ! } > return R_NilValue; > } > > > PATCH END > > --please do not edit the information below-- > > Version: > platform = i386-pc-sco3.2v4.2 > arch = i386 > os = sco3.2v4.2 > system = i386, s...

...... OK 376) QEMU XML-2-ARGV disk-geometry ... OK 377) QEMU XML-2-ARGV disk-blockio ... OK 378) QEMU XML-2-ARGV video-device-pciaddr-default ... OK 379) QEMU XML-2-ARGV video-vga-nodevice ... OK 380) QEMU XML-2-ARGV video-vga-device ... OK 381) QEMU XML-2-ARGV video-vga-device-vgamem ... OK 382) QEMU XML-2-ARGV video-qxl-nodevice ... OK 383) QEMU XML-2-ARGV video-...

Hi Rowland, Just a quick summary, we had to roll back the AD migration due to some users having issues accessing the shares post the migration. They were getting server couldn't not be found , using both hostname and IP. It won't even show the shares available in the server. Some users had no issues, which is the puzzling bit Re the OS and file system: I had a look at the following