Nagios (rpmbuild) Enterprise Linux

error(s):

1) /var/tmp/rpm-tmp.4HW54O: line 38: cd: nagios-3.5.0: No such file or directory
2) configure: error: unrecognized option: --datarootdir=/usr/share/nagios

Nagios Tracker – 0000468: redhat – I’m unable to use rpmbuild to build nagios-3.5.0 RPM @RHEL6 – Mantis

workaround:

tar -zxf nagios-3.5.0.tar.gz
rm nagios-3.5.0.tar.gz
mv nagios nagios-3.5.0
sed -i 's/datarootdir/datadir/' nagios-3.5.0/nagios.spec
tar -czf nagios-3.5.0.tar.gz nagios-3.5.0
rpmbuild -tb nagios-3.5.0.tar.gz
ls rpmbuild/RPMS/*/nagios-3.5.0*rpm

Samsung / Verizon Galaxy Nexus OTA UPDATE

Factory Images for Nexus Phones – Android — Google Developers

  • Settings -> Apps -> ALL -> Google Service Framework -> Clear data & Force stop
  • Settings -> About phone -> System updates -> Check now
  • IMM76K
  • JRO03O (WiFi only)

I/SystemUpdateService(11239): starting download of http://android.clients.google.com/packages/ota/verizon_prime/60fc80848c8e.signed-mysid-JRO03O-from-IMM76K.60fc8084.zip

I/SystemUpdate.Download(11239): Started a new update download: http://android.clients.google.com/packages/ota/verizon_prime/60fc80848c8e.signed-mysid-JRO03O-from-IMM76K.60fc8084.zip (id 3677; allowMobile=false)

 

I/SystemUpdateService( 9856): starting download of http://android.clients.google.com/packages/ota/verizon_prime/5939ff985946.signed-mysid-JDQ39-from-JRO03O.5939ff98.zip

I/SystemUpdate.Download( 9856): Started a new update download: http://android.clients.google.com/packages/ota/verizon_prime/5939ff985946.signed-mysid-JDQ39-from-JRO03O.5939ff98.zip (id 7675; allowMobile=true)

Apple iOS (iP*_Restore.ipsw) – iPhone iPad iPod (direct download links)

Kernel panic – not syncing: VFS: Unable to mount root fs on known-block(0,0)

Kernel panic - not syncing: VFS: Unable to mount root fs on known-block(0,0)

assuming your GRUB (/boot/grub/grub.conf) have something like this:

# grep -E "^hiddenmenu|^timeout" /boot/grub/grub.conf
timeout=0
hiddenmenu
#

Try holding “Ctrl” at GRUB splash/menu screen and then select previously working kernel. If that won’t help then boot into a rescue mode and do following:

# yum remove kernel-VERSION
# yum update kernel

reboot your system and you _SHOULD_ be OK)

alexus' blog is Stephen Fry proof thanks to caching by WP Super Cache

%d bloggers like this: