search for: last_rule

...pplied and the permissions are then correct but why is it not doing so at boot? The file in questions I've called /etc/udev/rules.d/49-udev-override.rules and it contains KERNEL=="tty[A-Z]*", NAME="%k", GROUP="rcl", MODE="0660", OPTIONS="last_rule" the default 50-udev.rules file has been left untouched. SELinux is in permissive mode and so I can't find a reason why it is happening. Anyone have any ideas? -- James A. Peltier IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fa...

...ap.c 2005-03-16 16:22:49.000000000 -0500 @@ -275,6 +275,7 @@ int lineno = 0; int err = 0; + memset(this_rule, '\0', sizeof(struct rule)); while ( lineno++, fgets(line, MAXLINE, f) ) { rv = parseline(line, this_rule, lineno); if ( rv < 0 ) @@ -283,6 +284,7 @@ *last_rule = this_rule; last_rule = &this_rule->next; this_rule = tfmalloc(sizeof(struct rule)); + memset(this_rule, '\0', sizeof(struct rule)); } } -- Peter

hi everyone I've been playing and trying to tell udev to ignore and not create symlinks in /dev but I fail. Hoping this is the one: ENV{ID_SERIAL}== I've tried: ENV{SYSTEMD_READY}:="0" OPTIONS+="last_rule" even ENV{UDISKS_IGNORE}="1" but udev tests would still show: ACTION=add and symlinks created. Would share an advice? many thanks, L.

I''ve the same error: http://serverfault.com/questions/222390/xen-4-0-1-on-ubuntu-10-10-not-booting I add this line: +KERNEL=="gntdev", NAME="xen/%k" +KERNELS=="xen", KERNEL=="xvd*", SUBSYSTEM=="block", OPTIONS+="last_rule" to /tools/hotplug/Linux/xen-backend.rule, but nothing. I need to re-compile xen? Or i need to enabled some kernel modules? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...udevinfo -a -p /sys/block/sdb and I try to use them to write /etc/udev/rules.d/10-custom.rules ID=="?:0:1:0", BUS=="scsi", DRIVER=="sd", SYSFS{model}=="DDYS-T36950N ", SYSFS{vendor}=="IBM ", OPTIONS="ignore_device", OPTIONS+="last_rule" I put the "?" on the ID field because I know that the order of the controller can change (a kernel update could trigger the switch); also I tried with and without the spaces at the end of vendor and model: no change Where am I wrong? It is a different way of doing this? TIA Ciao...

it looks like one of the recent updates will sometimes chmod /dev/null to 600. out of 20 machines i've updated, 3 of them had the odd /dev/null perms afterwards. i haven't tried to identify what it doing it yet, but wanted to give a heads up to others that might start seeing weird behavior.

After upgrade via http://download.opensuse.org/repositories/Virtualization:/openSUSE11.3/openSUSE_11.3/src/xen-4.0.1_21326_01-1.1.src.rpm with any "kotd" or 2.6.34.4-2.2-xen VFB gets broken . It worked with original  Xen 4.0, no matter of  some additional patching to support ZFS 24 has been done and 4.0 src.rpm has been rebuilt to reinstall 4.0   In particular,  virt-install fails to