search for: start_udev

Howdy. I have an appliance in which /sbin/start_udev exists but does not run successfully: /sbin/start_udev: line 36: /etc/init.d/functions: No such file or directory This prevents the "modprobe virtio_net" line (among other things) from being invoked. The attached patch is what I'm applying locally to libguestfs-1.0.74 to work aro...

...oup1 group2 Also, something else that's interesting. If I do this: passwd: files [!NOTFOUND=return] ldap shadow: files [!NOTFOUND=return] ldap group: ldap [NOTFOUND=continue] files and reboot, udev segfaults and the system freezes up after a few more seconds. Starting udev: /sbin/start_udev: line 43: 519 Segmentation fault "$@" $ARGS /sbin/start_udev: line 201: 523 Segmentation fault /sbin/udevd -d Wait timeout. Will continue in the background.[FAILED] Any advice?

...e of rebooting. Of course, a single removable device will camp at sdb, which is out of reach of udev so the whole hotplug thing is broken until someone removes all of the devices at site, allowing a clean boot. mapper correctly places the / filesystem higher in position in rc.sysinit, followed by start_udev (where the damage gets done) and finally fstab evaluation way down the line. I suppose i could just hardwire the array mount into rc.sysint to engage after modules get loaded and hopefully before start_udev, unless there is a better way to enforce it. I'm not sure at this stage (need to analy...

...or directory /bin/mknod: `/dev/lp3': Operation not permitted /bin/chown: cannot access `/dev/lp3': No such file or directory /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...

Hello list! I''ve noticed this problem a couple of times now.. so I''m wondering if it''s a known bug? Symptoms: After "long" dom0 uptime (174 days when it happened now, was something similar on previous times too) cannot start new pv domUs anymore.. pygrub runs and boots the kernel, but kernel newer gets to actually running initrd and the console output

...ree yet. You can apply the following patch manually to the kernel: https://lkml.org/lkml/2011/6/7/554 Note that this bug likely affects any distributions that enable ftrace and use kernels built during May. * udevadm settle timeout too short Since udev ~170, Fedora Rawhide no longer uses /sbin/start_udev, but uses a systemd script instead. We don't use systemd in the libguestfs appliance, and this change caused a different path to be taken through the 'init' script which uncovered a bug in how long we wait for the udev daemon to initially process requests. The setting (10 seconds) was...

...`/dev/lp3': Operation not permitted > /bin/chown: cannot access `/dev/lp3': No such file or directory > /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]: matchp...

When my machine installs (CentOS 6.3) the two network cards are getting reversed. The PCI card is getting eth0 and the motherboard is getting eth1. I would like them in reverse order to keep things the same as they used to be. How can I easily tell these two to reverse? Generate the 70-persistent-net-rules with motherboard eth0 first then the PCI slot? Thanks, Jerry

...cified user 'vcsa' unknown udevd[108]: specified user 'vcsa' unknown udevd[108]: specified group 'cdrom' unknown udevd[108]: specified group 'cdrom' unknown udevd[108]: specified group 'tape' unknown udevd[108]: specified group 'tape' unknown /sbin/start_udev: line 299: /etc/sysconfig/network: No such file or directory [ 1.227490] udev: starting version 147 [ 1.342135] ACPI Exception: AE_BAD_PARAMETER, Thread ffff88001db36aa0 could not acquire Mutex [0x1] (20090903/utmutex-290) [ 1.343146] piix4_smbus 0000:00:01.3: SMBus Host Controller at 0xb1...

...ces/platform/i8042/serio1/input/input2 udevd[88]: specified group 'dialout' unknown udevd[88]: specified group 'floppy' unknown udevd[88]: specified user 'vcsa' unknown udevd[88]: specified group 'cdrom' unknown udevd[88]: specified group 'tape' unknown /sbin/start_udev: line 291: /etc/sysconfig/network: No such file or directory [ 0.952509] udev: starting version 147 [ OK ] SIOCSIFADDR: No such device eth0: unknown interface: No such device SIOCADDRT: No such process mdadm: No arrays found in config file or automatically [ 2.232739] device-mapper: uevent:...

Unfortunately, placing the link into the /boot does not work. libguestfs-test-tool failes with the same message: ************************************************************ * IMPORTANT NOTICE * * When reporting bugs, include the COMPLETE, UNEDITED * output below in your bug report. *