Re: [gentoo-user] udevd boot messages
On 2012-05-26 01:52, Peter Humphrey wrote: $ elogviewer --help File /usr/local/bin/elogviewer, line 11 ^ SyntaxError: invalid syntax Huh? Mine (latest stable 0.5.2-r2, official Gentoo portage - not some overlay) is installed in /usr/bin/... Have you changed the install path or installed it through some other means? Best regards Peter K
Re: [gentoo-user] udevd boot messages
On Saturday 26 May 2012 09:36:50 pk wrote: On 2012-05-26 01:52, Peter Humphrey wrote: $ elogviewer --help File /usr/local/bin/elogviewer, line 11 ^ SyntaxError: invalid syntax Huh? Mine (latest stable 0.5.2-r2, official Gentoo portage - not some overlay) is installed in /usr/bin/... So is mine (same version), so I don't know why it's looking in /usr/local/bin. I have no alias mentioning elogviewer. $ find /usr -name elogviewer 2 /dev/null /usr/portage/app-portage/elogviewer /usr/bin/elogviewer $ $ grep /local/ /usr/bin/elogviewer $ Have you changed the install path or installed it through some other means? Nope. Unless I did something odd in 2007, I suppose. I don't like mysteries :-( -- Rgds Peter Portage 2.1.10.49 (default/linux/amd64/10.0, gcc-4.5.3, glibc-2.14.1-r3, 3.2.12-gentoo x86_64) = System uname: Linux-3.2.12-gentoo-x86_64-Intel-R-_Core-TM-_i5_CPU_750_@_2.67GHz-with-gentoo-2.1 Timestamp of tree: Fri, 25 May 2012 08:15:01 + app-shells/bash: 4.2_p20 dev-java/java-config: 2.1.11-r3 dev-lang/python: 2.7.3-r1, 3.2.3 dev-util/cmake: 2.8.7-r5 dev-util/pkgconfig: 0.26 sys-apps/baselayout: 2.1-r1 sys-apps/openrc: 0.9.8.4 sys-apps/sandbox: 2.5 sys-devel/autoconf: 2.13, 2.68 sys-devel/automake: 1.10.3, 1.11.1 sys-devel/binutils: 2.21.1-r1 sys-devel/gcc:4.5.3-r2 sys-devel/gcc-config: 1.5-r2 sys-devel/libtool:2.4-r1 sys-devel/make: 3.82-r1 sys-kernel/linux-headers: 3.1 (virtual/os-headers) sys-libs/glibc: 2.14.1-r3 Repositories: gentoo ACCEPT_KEYWORDS=amd64 ACCEPT_LICENSE=* -@EULA dlj-1.1 sun-bcla-java-vm PUEL AdobeFlash-10.3 googleearth CBUILD=x86_64-pc-linux-gnu CFLAGS=-O2 -march=core2 -pipe CHOST=x86_64-pc-linux-gnu CONFIG_PROTECT=/etc /usr/share/config /usr/share/gnupg/qualified.txt CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/init.d /etc/pam.d /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo CXXFLAGS=-O2 -march=core2 -pipe DISTDIR=/usr/portage/distfiles EMERGE_DEFAULT_OPTS=--with-bdeps=y --autounmask=n --nospinner --keep-going --load-average=8 FEATURES=assume-digests binpkg-logs buildpkg buildsyspkg distlocks ebuild-locks fixlafiles news parallel-fetch protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox FFLAGS= GENTOO_MIRRORS=http://distfiles.gentoo.org; LANG=en_GB.UTF-8 LDFLAGS=-Wl,-O1 -Wl,--as-needed LINGUAS=en_GB en MAKEOPTS=-j8 -l8 PKGDIR=/usr/portage/packages PORTAGE_COMPRESS= PORTAGE_CONFIGROOT=/ PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages PORTAGE_TMPDIR=/tmp PORTDIR=/usr/portage PORTDIR_OVERLAY= SYNC=rsync://serv.prhnet/gentoo-portage USE=X acl acpi alsa amd64 bash-completion bzip2 cli cracklib crypt cups cxx dbus dri dts dvd exif ffmpeg flac fxsr gdbm gpm iconv ipv6 jpeg jpeg2k kde mad mmx mng modules mp3 mp4 mudflap multilib ncurses nls nptl opengl openmp pae pam pcre pdf png policykit pppd pulseaudio readline sdl semantic-desktop session smp sse sse2 ssl ssse3 svg symlink tcpd theora tidy tiff truetype udev unicode vorbis wmf xorg zlib ALSA_CARDS=hda-intel ALSA_PCM_PLUGINS=adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol APACHE2_MODULES=actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias APACHE2_MPMS=prefork CALLIGRA_FEATURES=kexi words flow plan sheets stage tables krita karbon braindump CAMERAS=fuji COLLECTD_PLUGINS=df interface irq load memory rrdtool swap syslog ELIBC=glibc GPSD_PROTOCOLS=ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx INPUT_DEVICES=evdev KERNEL=linux LCD_DEVICES=bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text LIBREOFFICE_EXTENSIONS=presenter-console presenter-minimizer LINGUAS=en_GB en PHP_TARGETS=php5-3 PYTHON_TARGETS=python3_2 python2_7 RUBY_TARGETS=ruby18 USERLAND=GNU VIDEO_CARDS=nouveau XTABLES_ADDONS=quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account Unset:
Re: [gentoo-user] udevd boot messages
On 05/26/2012 10:34 AM, Peter Humphrey wrote: On Saturday 26 May 2012 09:36:50 pk wrote: On 2012-05-26 01:52, Peter Humphrey wrote: $ elogviewer --help File /usr/local/bin/elogviewer, line 11 ^ SyntaxError: invalid syntax Huh? Mine (latest stable 0.5.2-r2, official Gentoo portage - not some overlay) is installed in /usr/bin/... So is mine (same version), so I don't know why it's looking in /usr/local/bin. I have no alias mentioning elogviewer. $ find /usr -name elogviewer 2 /dev/null /usr/portage/app-portage/elogviewer /usr/bin/elogviewer $ $ grep /local/ /usr/bin/elogviewer $ Have you changed the install path or installed it through some other means? Nope. Unless I did something odd in 2007, I suppose. I don't like mysteries :-( Portage *never* installs anything in /usr/local. My best bet is that you have been experimenting back in 2007 and probably copied the original file in /usr/local. Remove it and then emerge elogviewer again ;) -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
Re: [gentoo-user] udevd boot messages
On Saturday 26 May 2012 10:37:38 Markos Chandras wrote: Portage *never* installs anything in /usr/local. Indeed so. My best bet is that you have been experimenting back in 2007 and probably copied the original file in /usr/local. Remove it and then emerge elogviewer again ;) As I said before, I've already done that - twice or three times now. I get the same result. Something is apparently causing bash to seek the file in /usr/local/bin/ instead of in /usr/bin/ . [OT] I have a more pressing problem now - someone has hacked into a supposedly protected part of my website, so I must find what's failed and fix it, or else find another package. No sleep for the wicked... [/OT] -- Rgds Peter
Re: [gentoo-user] udevd boot messages
On 2012-05-24 7:24 PM, Michael Mol mike...@gmail.com wrote: I just now started going through /var/log/portage/messages, and was reminded of this thread. It is much easier if you set up portage to email you these individually...
Re: [gentoo-user] udevd boot messages
On 2012-05-25 13:17, Tanstaafl wrote: On 2012-05-24 7:24 PM, Michael Mol mike...@gmail.com wrote: I just now started going through /var/log/portage/messages, and was reminded of this thread. It is much easier if you set up portage to email you these individually... app-portage/elogviewer is also nice... :-) Best regards Peter K
Re: [gentoo-user] udevd boot messages
On Friday 25 May 2012 21:13:14 pk wrote: app-portage/elogviewer is also nice... :-) I thought I'd give this a try, but after installing it and its two dependencies (pygtk and libglade - this is a KDE box) I get this: $ elogviewer --help File /usr/local/bin/elogviewer, line 11 ^ SyntaxError: invalid syntax I messed about with that file but couldn't make the syntax work, so I ran emerge -Cav elogviewer and the file was left behind. Qfile and equery b /usr/local/bin/elogviewer turned nothing up so I deleted the file. Now, after remerging elogviewer and the two dependencies I get this: $ elogviewer --help bash: /usr/local/bin/elogviewer: No such file or directory What's going on here? Where did that file come from originally, and why is it not being installed now? I've retrieved it from a backup, but how did it get in there? It dates from 2007! Maybe it's just too late at night. -- Rgds Peter
Re: [gentoo-user] udevd boot messages
On Fri, May 25, 2012 at 7:17 AM, Tanstaafl tansta...@libertytrek.org wrote: On 2012-05-24 7:24 PM, Michael Mol mike...@gmail.com wrote: I just now started going through /var/log/portage/messages, and was reminded of this thread. It is much easier if you set up portage to email you these individually... The file isn't that difficult. Also, this is a laptop whose only working network connection is its wifi NIC. -- :wq
Re: [gentoo-user] udevd boot messages
On 2012-05-23 5:25 PM, Markos Chandras hwoar...@gentoo.org wrote: On 05/23/2012 05:24 PM, Tanstaafl wrote: *Especially* for servers, there really, REALLY needs to be a way to see this kind of warning BEFORE updating... ie, the warning should be printed to the screen during an 'emerge -pvuDN world' or something, so I know that a reboot will be required for this update. /pet-peeve This kind of messages are also printed at the end of -uDNav world so if you scroll your screen up you can see all the warning/log messages from every package that you have updated. Also, these kind of messages are logged in/var/log/portage/ Ummm... yes, I know that, I get my elogs via email... You must have missed the words 'BEFORE updating' above... I put BEFORE in caps, not sure what else I could have done to make it more plain... ;)
Re: [gentoo-user] udevd boot messages
On 2012-05-23 5:54 PM, Markos Chandras hwoar...@gentoo.org wrote: On 05/23/2012 10:47 PM, Alan McKinnon wrote: Tanstaafl wants to know if a reboot*will* be required*before* he does the update. What you are describing tells him that after the update completes when it is already too late. I face the same issue at work. We have a change policy requiring 14 days advance notice of any change affecting service. If I do a routine world update then have to log an emergency change for an unexpected reboot, the change manager will have my nuts for breakfast. If it happens more than once, I'd be having a really unusual conversation with the CTO which probably ends with him standing behind me watching while I migrate every single box that isn't RHEL6 (all 200 of them) over to RHEL6 where I*do* have exact knowledge in advance of the impact of a change. Did either of you ever open a bug about this or even discuss it in the gentoo-dev mailing list? What you say sounds like a valid concern to me but unless you express your needs to maintainers, nothing is ever going to happen. However, in this particular case, yes a news item would be the ideal solution. I didn't discuss it on the dev list (I'm not a dev), but I did ask a question about this, but it was more general in nature (how to get ewarn/einfo during --pretend): http://forums.gentoo.org/viewtopic.php?p=5930125#5930125 As a result of that thread, I then opened this bug which was subsequently closed: https://bugs.gentoo.org/show_bug.cgi?id=281248
Re: [gentoo-user] udevd boot messages
On Mon, May 21, 2012 at 5:00 PM, Markos Chandras hwoar...@gentoo.org wrote: On 05/21/2012 03:27 PM, Michael Hampicke wrote: I updated udev from 171-r5 to 171-r6 and now i get several udevd boot message as : udevd[1389]: can not find '/lib/udev/rules.d/90-network.rules': No such file or directory udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No such file or directory .. and so on. /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok with all the rules that udevd does not find at boot. No I would guess it was because of the upgrade of sys-apps/baselayout to 2.1-r1. Things got crazy here with that upgrade. I had to re-merge every package with files under /lib/ In your case re-merging udev should to the trick. The package clearly informed you that you need to reboot for things to work properly You should reboot the system now to get /run mounted with tmpfs! Have a look on pkg_postinst() function in that ebuild. You chose to ignore it and this is why you had these problems after the update. Ok, now I'm coming up on a bind. I've spent the last few days trying to get my laptop back up to snuff, cycling emerge updates, revdep-rebuilds and eix-syncs. That particular warning, for me, was buried in a mountain of ruby and libicu build failures. I just now started going through /var/log/portage/messages, and was reminded of this thread. I just wanted to note that deleting the rules.d directory, and then only re-emerging udev, strikes me as setting oneself up for more problems in the future. Turns out, there are a lot of packages on my system I might want to look at re-emerging. A lot of it belongs to udev, but a lot of it...doesn't. I'm going to try Jacques's method of removing the old rules.d folder, and re-emerging the packages equery identified. Hopefully, I won't see the same boot messages that hit other people. saffron rules.d # for pkg in $(ls); do equery b $pkg; done * Searching for 10-dm.rules ... sys-fs/lvm2-2.02.88 (/lib/udev/rules.d/10-dm.rules) * Searching for 11-dm-lvm.rules ... sys-fs/lvm2-2.02.88 (/lib/udev/rules.d/11-dm-lvm.rules) * Searching for 13-dm-disk.rules ... sys-fs/lvm2-2.02.88 (/lib/udev/rules.d/13-dm-disk.rules) * Searching for 30-kernel-compat.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/30-kernel-compat.rules) * Searching for 40-gentoo.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/40-gentoo.rules) * Searching for 42-qemu-usb.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/42-qemu-usb.rules) * Searching for 50-firmware.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/50-firmware.rules) * Searching for 50-udev-default.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/50-udev-default.rules) * Searching for 60-cdrom_id.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/60-cdrom_id.rules) * Searching for 60-persistent-alsa.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/60-persistent-alsa.rules) * Searching for 60-persistent-input.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/60-persistent-input.rules) * Searching for 60-persistent-serial.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/60-persistent-serial.rules) * Searching for 60-persistent-storage.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/60-persistent-storage.rules) * Searching for 60-persistent-storage-tape.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/60-persistent-storage-tape.rules) * Searching for 60-persistent-v4l.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/60-persistent-v4l.rules) * Searching for 70-libgphoto2.rules ... media-libs/libgphoto2-2.4.12 (/lib/udev/rules.d/70-libgphoto2.rules) * Searching for 70-udev-acl.rules ... sys-auth/consolekit-0.4.5_p20120320 (/lib/udev/rules.d/70-udev-acl.rules) * Searching for 75-cd-aliases-generator.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/75-cd-aliases-generator.rules) * Searching for 75-persistent-net-generator.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/75-persistent-net-generator.rules) * Searching for 75-probe_mtd.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/75-probe_mtd.rules) * Searching for 77-nm-olpc-mesh.rules ... net-misc/networkmanager-0.8.4.0-r2 (/lib/udev/rules.d/77-nm-olpc-mesh.rules) * Searching for 80-drivers.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/80-drivers.rules) * Searching for 80-udisks.rules ... sys-fs/udisks-1.0.4-r1 (/lib/udev/rules.d/80-udisks.rules) * Searching for 90-alsa-restore.rules ... media-sound/alsa-utils-1.0.25-r1 (/lib/udev/rules.d/90-alsa-restore.rules) * Searching for 90-network.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/90-network.rules) * Searching for 95-dm-notify.rules ... sys-fs/lvm2-2.02.88 (/lib/udev/rules.d/95-dm-notify.rules) * Searching for 95-udev-late.rules ... sys-fs/udev-171-r6 (/lib/udev/rules.d/95-udev-late.rules) * Searching for 95-upower-battery-recall-dell.rules ... sys-power/upower-0.9.16 (/lib/udev/rules.d/95-upower-battery-recall-dell.rules) * Searching for
Re: [gentoo-user] udevd boot messages
On 2012-05-21 5:00 PM, Markos Chandras hwoar...@gentoo.org wrote: On 05/21/2012 03:27 PM, Michael Hampicke wrote: I updated udev from 171-r5 to 171-r6 and now i get several udevd boot message as : udevd[1389]: can not find '/lib/udev/rules.d/90-network.rules': No such file or directory udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No such file or directory .. and so on. /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok with all the rules that udevd does not find at boot. No I would guess it was because of the upgrade of sys-apps/baselayout to 2.1-r1. Things got crazy here with that upgrade. I had to re-merge every package with files under /lib/ In your case re-merging udev should to the trick. The package clearly informed you that you need to reboot for things to work properly You should reboot the system now to get /run mounted with tmpfs! Have a look on pkg_postinst() function in that ebuild. You chose to ignore it and this is why you had these problems after the update. pet-peeve I asked about this a while back but never got a decent answer... *Especially* for servers, there really, REALLY needs to be a way to see this kind of warning BEFORE updating... ie, the warning should be printed to the screen during an 'emerge -pvuDN world' or something, so I know that a reboot will be required for this update. /pet-peeve
Re: [gentoo-user] udevd boot messages
Tanstaafl writes: *Especially* for servers, there really, REALLY needs to be a way to see this kind of warning BEFORE updating... ie, the warning should be printed to the screen during an 'emerge -pvuDN world' or something, so I know that a reboot will be required for this update. /pet-peeve Indeed! I think eselect news read should show this, at least. Wonko
Re: [gentoo-user] udevd boot messages
On 2012-05-23 12:49 PM, Alex Schuster wo...@wonkology.org wrote: Tanstaafl writes: *Especially* for servers, there really, REALLY needs to be a way to see this kind of warning BEFORE updating... ie, the warning should be printed to the screen during an 'emerge -pvuDN world' or something, so I know that a reboot will be required for this update. /pet-peeve Indeed! I think eselect news read should show this, at least. That would work for me... anytime I saw an update for system critical stuff (like baselayout or udev or openrc) I'd be sure to check things... As it stands, I'm now very glad for my self imposed policy of waiting a few days for critical things like this...
Re: [gentoo-user] udevd boot messages
On 05/23/2012 05:24 PM, Tanstaafl wrote: On 2012-05-21 5:00 PM, Markos Chandras hwoar...@gentoo.org wrote: On 05/21/2012 03:27 PM, Michael Hampicke wrote: I updated udev from 171-r5 to 171-r6 and now i get several udevd boot message as : udevd[1389]: can not find '/lib/udev/rules.d/90-network.rules': No such file or directory udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No such file or directory .. and so on. /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok with all the rules that udevd does not find at boot. No I would guess it was because of the upgrade of sys-apps/baselayout to 2.1-r1. Things got crazy here with that upgrade. I had to re-merge every package with files under /lib/ In your case re-merging udev should to the trick. The package clearly informed you that you need to reboot for things to work properly You should reboot the system now to get /run mounted with tmpfs! Have a look on pkg_postinst() function in that ebuild. You chose to ignore it and this is why you had these problems after the update. pet-peeve I asked about this a while back but never got a decent answer... *Especially* for servers, there really, REALLY needs to be a way to see this kind of warning BEFORE updating... ie, the warning should be printed to the screen during an 'emerge -pvuDN world' or something, so I know that a reboot will be required for this update. /pet-peeve This kind of messages are also printed at the end of -uDNav world so if you scroll your screen up you can see all the warning/log messages from every package that you have updated. Also, these kind of messages are logged in /var/log/portage/ -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
Re: [gentoo-user] udevd boot messages
On Wed, 23 May 2012 22:25:37 +0100 Markos Chandras hwoar...@gentoo.org wrote: On 05/23/2012 05:24 PM, Tanstaafl wrote: On 2012-05-21 5:00 PM, Markos Chandras hwoar...@gentoo.org wrote: On 05/21/2012 03:27 PM, Michael Hampicke wrote: I updated udev from 171-r5 to 171-r6 and now i get several udevd boot message as : udevd[1389]: can not find '/lib/udev/rules.d/90-network.rules': No such file or directory udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No such file or directory .. and so on. /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok with all the rules that udevd does not find at boot. No I would guess it was because of the upgrade of sys-apps/baselayout to 2.1-r1. Things got crazy here with that upgrade. I had to re-merge every package with files under /lib/ In your case re-merging udev should to the trick. The package clearly informed you that you need to reboot for things to work properly You should reboot the system now to get /run mounted with tmpfs! Have a look on pkg_postinst() function in that ebuild. You chose to ignore it and this is why you had these problems after the update. pet-peeve I asked about this a while back but never got a decent answer... *Especially* for servers, there really, REALLY needs to be a way to see this kind of warning BEFORE updating... ie, the warning should be printed to the screen during an 'emerge -pvuDN world' or something, so I know that a reboot will be required for this update. /pet-peeve This kind of messages are also printed at the end of -uDNav world so if you scroll your screen up you can see all the warning/log messages from every package that you have updated. Also, these kind of messages are logged in /var/log/portage/ You are missing the point. Tanstaafl wants to know if a reboot *will* be required *before* he does the update. What you are describing tells him that after the update completes when it is already too late. I face the same issue at work. We have a change policy requiring 14 days advance notice of any change affecting service. If I do a routine world update then have to log an emergency change for an unexpected reboot, the change manager will have my nuts for breakfast. If it happens more than once, I'd be having a really unusual conversation with the CTO which probably ends with him standing behind me watching while I migrate every single box that isn't RHEL6 (all 200 of them) over to RHEL6 where I *do* have exact knowledge in advance of the impact of a change. -- Alan McKinnnon alan.mckin...@gmail.com
Re: [gentoo-user] udevd boot messages
On 05/23/2012 10:47 PM, Alan McKinnon wrote: On Wed, 23 May 2012 22:25:37 +0100 Markos Chandras hwoar...@gentoo.org wrote: On 05/23/2012 05:24 PM, Tanstaafl wrote: On 2012-05-21 5:00 PM, Markos Chandras hwoar...@gentoo.org wrote: On 05/21/2012 03:27 PM, Michael Hampicke wrote: I updated udev from 171-r5 to 171-r6 and now i get several udevd boot message as : udevd[1389]: can not find '/lib/udev/rules.d/90-network.rules': No such file or directory udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No such file or directory .. and so on. /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok with all the rules that udevd does not find at boot. No I would guess it was because of the upgrade of sys-apps/baselayout to 2.1-r1. Things got crazy here with that upgrade. I had to re-merge every package with files under /lib/ In your case re-merging udev should to the trick. The package clearly informed you that you need to reboot for things to work properly You should reboot the system now to get /run mounted with tmpfs! Have a look on pkg_postinst() function in that ebuild. You chose to ignore it and this is why you had these problems after the update. pet-peeve I asked about this a while back but never got a decent answer... *Especially* for servers, there really, REALLY needs to be a way to see this kind of warning BEFORE updating... ie, the warning should be printed to the screen during an 'emerge -pvuDN world' or something, so I know that a reboot will be required for this update. /pet-peeve This kind of messages are also printed at the end of -uDNav world so if you scroll your screen up you can see all the warning/log messages from every package that you have updated. Also, these kind of messages are logged in /var/log/portage/ You are missing the point. Tanstaafl wants to know if a reboot *will* be required *before* he does the update. What you are describing tells him that after the update completes when it is already too late. I face the same issue at work. We have a change policy requiring 14 days advance notice of any change affecting service. If I do a routine world update then have to log an emergency change for an unexpected reboot, the change manager will have my nuts for breakfast. If it happens more than once, I'd be having a really unusual conversation with the CTO which probably ends with him standing behind me watching while I migrate every single box that isn't RHEL6 (all 200 of them) over to RHEL6 where I *do* have exact knowledge in advance of the impact of a change. Did either of you ever open a bug about this or even discuss it in the gentoo-dev mailing list? What you say sounds like a valid concern to me but unless you express your needs to maintainers, nothing is ever going to happen. However, in this particular case, yes a news item would be the ideal solution. -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
Re: [gentoo-user] udevd boot messages
On Wed, 23 May 2012 22:54:23 +0100 Markos Chandras hwoar...@gentoo.org wrote: On 05/23/2012 10:47 PM, Alan McKinnon wrote: On Wed, 23 May 2012 22:25:37 +0100 Markos Chandras hwoar...@gentoo.org wrote: On 05/23/2012 05:24 PM, Tanstaafl wrote: On 2012-05-21 5:00 PM, Markos Chandras hwoar...@gentoo.org wrote: On 05/21/2012 03:27 PM, Michael Hampicke wrote: I updated udev from 171-r5 to 171-r6 and now i get several udevd boot message as : udevd[1389]: can not find '/lib/udev/rules.d/90-network.rules': No such file or directory udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No such file or directory .. and so on. /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok with all the rules that udevd does not find at boot. No I would guess it was because of the upgrade of sys-apps/baselayout to 2.1-r1. Things got crazy here with that upgrade. I had to re-merge every package with files under /lib/ In your case re-merging udev should to the trick. The package clearly informed you that you need to reboot for things to work properly You should reboot the system now to get /run mounted with tmpfs! Have a look on pkg_postinst() function in that ebuild. You chose to ignore it and this is why you had these problems after the update. pet-peeve I asked about this a while back but never got a decent answer... *Especially* for servers, there really, REALLY needs to be a way to see this kind of warning BEFORE updating... ie, the warning should be printed to the screen during an 'emerge -pvuDN world' or something, so I know that a reboot will be required for this update. /pet-peeve This kind of messages are also printed at the end of -uDNav world so if you scroll your screen up you can see all the warning/log messages from every package that you have updated. Also, these kind of messages are logged in /var/log/portage/ You are missing the point. Tanstaafl wants to know if a reboot *will* be required *before* he does the update. What you are describing tells him that after the update completes when it is already too late. I face the same issue at work. We have a change policy requiring 14 days advance notice of any change affecting service. If I do a routine world update then have to log an emergency change for an unexpected reboot, the change manager will have my nuts for breakfast. If it happens more than once, I'd be having a really unusual conversation with the CTO which probably ends with him standing behind me watching while I migrate every single box that isn't RHEL6 (all 200 of them) over to RHEL6 where I *do* have exact knowledge in advance of the impact of a change. Did either of you ever open a bug about this or even discuss it in the gentoo-dev mailing list? What you say sounds like a valid concern to me but unless you express your needs to maintainers, nothing is ever going to happen. However, in this particular case, yes a news item would be the ideal solution. I haven't opened a bug myself, mostly because I've never been bitten by this. My Gentoo servers run stable so I've always known from this list and other places when something requiring a reboot is coming down the line. I agree, a news item is the perfect solution. Having portage do it will be highly cumbersome, it will require some kind of new magic flag in ebuilds that portage must parse. All that work for something that doesn't happen often? Nah, it'll never fly. -- Alan McKinnnon alan.mckin...@gmail.com
Re: [gentoo-user] udevd boot messages
On May 24, 2012 5:19 AM, Alan McKinnon alan.mckin...@gmail.com wrote: On Wed, 23 May 2012 22:54:23 +0100 Markos Chandras hwoar...@gentoo.org wrote: [znip] Did either of you ever open a bug about this or even discuss it in the gentoo-dev mailing list? What you say sounds like a valid concern to me but unless you express your needs to maintainers, nothing is ever going to happen. However, in this particular case, yes a news item would be the ideal solution. I haven't opened a bug myself, mostly because I've never been bitten by this. My Gentoo servers run stable so I've always known from this list and other places when something requiring a reboot is coming down the line. +1 I love this list :-) In my previous place, I have one 'experimental' server which gets updated before all others. It's the 'designated fall guy'. Which reminds me of Project Management 101: What's the first thing you must do before embarking on a project? Answer: Designate a fall guy and prepare implicating evidences. ;-) I agree, a news item is the perfect solution. Having portage do it will be highly cumbersome, it will require some kind of new magic flag in ebuilds that portage must parse. All that work for something that doesn't happen often? Nah, it'll never fly. Also a heartfelt +1 for this. That said, I'm going to repost this 'news' to the Gentoo-server list, unless someone beats me to it. Rgds,
Re: [gentoo-user] udevd boot messages
I updated udev from 171-r5 to 171-r6 and now i get several udevd boot message as : udevd[1389]: can not find '/lib/udev/rules.d/90-network.rules': No such file or directory udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No such file or directory .. and so on. /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok with all the rules that udevd does not find at boot. No I would guess it was because of the upgrade of sys-apps/baselayout to 2.1-r1. Things got crazy here with that upgrade. I had to re-merge every package with files under /lib/ In your case re-merging udev should to the trick.
[solved] Re: [gentoo-user] udevd boot messages
Le 21/05/2012 16:27, Michael Hampicke a écrit : I updated udev from 171-r5 to 171-r6 and now i get several udevd boot message as : udevd[1389]: can not find '/lib/udev/rules.d/90-network.rules': No such file or directory udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No such file or directory .. and so on. /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok with all the rules that udevd does not find at boot. No I would guess it was because of the upgrade of sys-apps/baselayout to 2.1-r1. Things got crazy here with that upgrade. I had to re-merge every package with files under /lib/ In your case re-merging udev should to the trick. I re-emerged udev, but i still got error messages. So i deleted (backup) my old /lib64/udev/rules.d directory and re-emerged udev. Then no more messages with the new rules.d directory. Thank you for your reply. Best regards, -- Jacques
Re: [gentoo-user] udevd boot messages
On 05/21/2012 03:27 PM, Michael Hampicke wrote: I updated udev from 171-r5 to 171-r6 and now i get several udevd boot message as : udevd[1389]: can not find '/lib/udev/rules.d/90-network.rules': No such file or directory udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules': No such file or directory .. and so on. /lib is a symlink pointing to /lib64. /lib64/udev/rules.d is ok with all the rules that udevd does not find at boot. No I would guess it was because of the upgrade of sys-apps/baselayout to 2.1-r1. Things got crazy here with that upgrade. I had to re-merge every package with files under /lib/ In your case re-merging udev should to the trick. The package clearly informed you that you need to reboot for things to work properly You should reboot the system now to get /run mounted with tmpfs! Have a look on pkg_postinst() function in that ebuild. You chose to ignore it and this is why you had these problems after the update. -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
