I recently installed redhawk on RHEL 5.8 using the instructions found here http://redhawksdr.github.io/Documentation/mainch2.html#x4-60002
I was installing from the redhawk-yum-1.10.0-10-el5-x86_64.tar.gz file.
After the installation and a reboot I found that all the files in /dev/ on the system had been changed to be owned by usrp:usrp and permissions were changed so that other users could not write to those files.
This created a lot of problems as many user scripts on the system write things to /dev/null which became unavailable.
Has anyone seen this before?
I also noticed that all the directories like /usr/local/redhawk were owned by root:root instead of redhawk:redhawk.
UPDATE:
I found that even after restoring the correct ownership and permissions to /dev/* files a reboot reverted those changes. Then I removed the file /etc/udev/rules.d/10-usrp-udh.rules and restored the correct permissions once more. After a reboot this time, the correct permissions persisted and the problem ended. Something must be up with the USRP-UDH rules installed by the UDH RPM with redhawk in EL5 series installer.
You're correct that the problem is being caused by the udev rules file installed by the UHD RPM. Specifically, The udev system within CentOS5 (14.32.el5) does not support the SUBSYSTEMS and ATTRS tags, which are included in the udev rules file created using the official UHD driver and fedora spec file. Since the current version of REDHAWK (1.10.1) does not support CentOS5, the recommended solution is to upgrade to CentOS6. If this is not a viable option for you, you'll need to obtain a CentOS5-compatible build of the UHD drivers.
Related
Using a virgin (but updated) version of Rocky Linux 8.5, I am trying to install VMware Workstation 16.2.1 (and others), but get compile errors during the first attempt to run, when vmmon and vmnet are being built.
All the proper, current headers from kernel-devel and kernel-headers are installed.
I tried upgrading to the 5.16.4 kernal at kernel.org, with all associated headers, and basically get the same errors.
"Unable to install all modules." i.e., vmmon and vmnet
Posts i have found with searching the net seem to indicate that there was a "back-port" of an upstream fix to Rocky that has affected the ability to build the loadable kernel modules necessary to run vmware - but i cannot confirm this is actually the problem that I am experiencing.
So i simply ask these questions: Can anyone (today) install VMware Workstation 16.2.1 (or any version), on a fresh install of Rocky Linux 8.5?
If so, would you please point me at your installation instructions, because I am unable to build "vmmon" and "vmnet" modules today (2022-01-04), that allow me to actually run virtual machines with vmware? (The kernel modules fail to compile and build.)
(and after 15 years of using stackoverflow i do not have the reputation to create a "rocky-linux" question tag...)
See https://unix.stackexchange.com/questions/689436/the-vmmon-and-vmnet-vmware-workstation-kernel-modules-fail-to-build-on-rocky-lin
mbubecek's instructions work for a variety of releases and should compile perfectly and run without issue, if you follow his instructions.
I have successfully used these methods at least a half dozen times with Rocky 8.5 and 8.6 with vmware workstation 16.1 up to version 16.2.1
NOTE: This error is NOT Rocky Linux specific. Also happens on some versions of RHEL 8 and CentOS 8.x I would also expect this "fix" to work on all of the other linux versions that are RHEL 8-derived.
I've been having difficulty with the same issue, and a colleague pointed me to check my kernel. This is our "official" resolution. See if the below works for you.
This is due to differences between the kernel and the source code for the VMWare modules, see here for more information. You can get the correct kernel modules, and build them by executing the following commands
wget https://github.com/mkubecek/vmware-host-modules/archive/workstation-16.1.0.tar.gz
tar -xf workstation-16.1.0.tar.gz
cd vmware-host-modules-workstation-16.1.0/
make
sudo make install
If you get the error,
crosspage.c:53:16: fatal error: linux/frame.h: No such file or directory
The error is described here. The solution is to remove (i.e. comment out) the offending include file in crosspage.c After doing the sudo make install, it is a very good idea to restart you host.
You may need to manually insert the modules into the kernel the first time after running make install'. The kernel modules (vmmon.ko and vmnet.ko) will be found at /lib/modules//misc. The following set of command will do this:
cd /lib/modules/$(uname -r)/misc
sudo insmod vmmon.ko
sudo insmod vmnet.ko
The modules should be load automatically after a restart/reboot.
If you update vmware to a different version (say 16.2.1) you may need to this again. Just change the versions in the above commands. If you hit the update button on the splash-screen and failed to notice the version you are updating to, you can run `vmware -v' at a command prompt to get the version you updated to.
I have gone through the JBoss FUSE guide in official guide but I could not see any details regarding capabilities of install FUSE in Linux server. Have any one try this before? I have not seen any document regarding this, Appropriate if some experienced person provide feedback about this.
Is it possible to install the FUSE in Linux server for example Ubuntu 16.04.1 LTS ? If it's possible is there any reference document guideline ?
Yes it's possible to run the FUSE on linux without any issue. Only thing is it is required to install JDK and its better to have maven installed in your PC as well.(Note that path variable needed to be updated after install JDK and maven). If you haven't install please go through following guide lines.
01) Install JDK in linux
02) Install maven in linux
After you installed those two then you need to download the relevant zip file from JBoss Fuse official site. Then extract the zip file in to desired location. (This location can be any place you want to install in folder structure)
Open the command line and go to bin folder on extracted folder.
then Type following command and press enter
./fuse
As show on below image
Then you will see similar interface to below(Usual fuse loading interface ).
Since there is not much dificulties on this I don't think there will be any documentation regarding this. I believe this steps will help you to setup JBoss Fuse in linux environment.
I am using Fedora 20 and somehow it boots to an older version of the kernel: 3.11, instead of 3.14. uname -r shows 3.11.10-301.fc20.x86_64 and rpm -qa kernel shows kernel-3.11.10-301.fc20.x86_64, kernel-3.13.10-200.fc20.x86_64, kernel-3.14.4-200.fc20.x86_64
I am curious why this is caused.
How I can make it to boot to 3.14 (the updated version.)
Would it cause trouble if I remove the older versions?
If not, how can I remove the older version, just for the record.
A user from another thread suggested me to hold 'Ctrl' key to change this, but this didn't quite work out and I wish to have more permanent solution to this.
All other thread only mentions how to install and boot to older versions, not the other way around. Any help would be appreciated!
Are you getting all the kernel version in GRUB Screen. if not then update GRUB then it will display all the kernel version and then you can select as per your choice.
grub2-mkconfig -o /boot/grub2/grub.cfg
try above using super user mode.
You should not delete the older kernels as i tried in Debian it made me to format the HD so better keep all versions. You can remove the kernel package but due to dependency and other reasons it may create problems. Still you want to remove the kernels then you can follow the link.
I've installed a RPM (MySQL Shared glibc Library). After that I couldn't boot my fedora Linux box (Because of some crash with kernel glibc). I boot via LiveDVD and renamed the RPM's copied files, but it can't solved.
How can I uninstall my RPM (not only files) through other Linux or Live CD?
If you boot from a live cd you can remove rpm packages from the installed system by running
rpm --erase --root /mnt/your_system_mount_point the-package-you-want-to-remove
Another alternatively is boot the system by editing the boot loader kernel command line to contain init=/bin/bash and try to run rpm --erase the-package-you-want-to-remove from there. If the problem is with glibc you might have trouble getting bash executed (as well as rpm), but you might want to try this option as well just to see how far the startup is progressing without problems. Thinking of it, busybox usually comes with a statically linked binary that could be used as init shell, you might have better success using that.
I have a server currently running RHEL 5.1, and I would like to upgrade it to RHEL 5.4. The server is not connected to the Internet, so I don't think I can use "yum update".
How would I be able to upgrade my server, and is it just a small-scale upgrade, like Windows patches, leaving everything on the server intact, or would it delete everything that was on the server?
Thank you.
Regards,
Rayne
I haven't actually tried this myself, but you should be able to use an installation disc for RHEL 5.4 to upgrade even if you are off-line (although you'll need to get on-line somewhere to download the disk image). Once you have the RHEL 5.4 disc, you should be able to follow the instructions here:
How do I use yum to update or install packages for Red Hat Enterprise Linux 5 from a customized repository?
to update your system. Basically, you create a custom repository on you hard drive with the rpm files from the disk and point yum at it or use the disc directly.
Good luck.
Of course if you can put the server temporarily on-line and just use the on-line repositories, after updating all the packages in your 5.1 distribution, you'll have all the same files as if you installed 5.4. At least that's what I remember happening. I had a 5.0 installation that I kept updated and when I compared them they seemed to be the same as the 5.3 version (current at the time) although during boot, my system said it was still 5.0
Rayne,
I used to work on DOE classified systems that could never touch the public internet. There is a very easy way to do this as mentioned. Just use the ISO as a repo, and for my example to work, it needs to be a DVD image. (The way around that using disk {1,2,3} is to copy the files from each disk onto the local disk or a storage device)
You will need to install createrepo which for me involved two dependencies.
createrepo
deltarpm
python-deltarpm
mkdir -p /mnt/iso/rhel54
mount -o loop /path/to/rhel5.4.iso /mnt/iso/rhel54
cd /mnt/iso
createrepo .
It will look like this:
[root#hostname iso]# createrepo .
44/20586 - rhel54/HighAvailability/Packages/PyQt4-4.6.2-8.el6.x86_64.rpm
Create /etc/yum.repos.d/rayne.repo and add
[Rayne-repo]
baseurl=file:///mnt/iso/
enabled=1
gpgcheck=0
Then run yum update
The update from RHEL 5.1 to RHEL 5.4 is not a small one, not like Windows patches. You can read the release notes, but you will end up with a newer kernel in the end and a ton of updates to the packages. I have not upgraded from 5.X to 5.Y+3 before, it's always been incremental (5.1 to 5.2). At any rate, this should work for you.