I'm getting the following error:
install-reddit.sh: line 79: /etc/lsb-release: No such file or
directory
cat /etc/issue
gives me
CentOS release 6.6 (Final)
I know the script is for ubuntu: https://github.com/reddit/reddit/wiki/reddit-install-script-for-Ubuntu but I was wondering if there is a way to make the script run on centOS? When I try to install normally it fails
In the end I did not find a solution to running the easy install from reddit. Instead I used vagrant to create a virtual Ubuntu Linux 12.04 (Precise Pangolin) which with a little fiddling worked fine for me.
The one issue is that you have to preallocate space for it (unlike if it were local (clearly)). I had to increase the size 4x to get it working for me.
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 am trying to build this project using Rust on WSL. However, after running npm run build:program-rust my computer crashed and showed a BSD (I caused the crash twice to make sure this command was the actual cause).
What is the workaround for this issue?
Thanks to the discussion on this issue I realized I was on WSL 1 (you can check with wsl -l -v)
I tried migrating my Ubuntu 20.04 instance to WSL 2 by running wsl --set-version <my_distro_name> 2 and it appears to have resolved the Blue Screen issue.
I'm really new to Ubuntu and WSL.
My problem is simple: I want to access from Ubuntu which I have installed in my computer (dual boot alongside with Windows) to my WSL2 filesystem that I have in Windows. I located a file named ext4.vhdx which I suppose is my entire wsl drive, but I'm not really sure, it is in
c:\Users\USER\Appdata\Local\Packages\CanonicalGroupLimited.Ubuntu20.04o...\LocalState\
I'm currently into web development and I want to share that environment within WSL2 and Ubuntu, I noticed that using the linux fs is way faster than windows fs and it works better with things like watchers. So, is it possible?
I'm currently running Windows 10 19041 (2004), Ubuntu LTS 20.04
I've also encountered similar issues when doing this WSL Ubuntu sharing thing, and I've finally found a solution on the internet that works out perfectly.
Reference Link:
https://www.nicholasmelnick.com/2020/07/sharing-your-wsl2-environment-with-linux/
So basically these are the steps,
First of all, the WSL's "ext4.vhdx" file should be accessible inside your Ubuntu system (So you must mount your windows drive inside your linux OS)
Install libguestfs-tools package with APT
And finally just create a folder and guestmount the drive with following commands.
$ sudo mkdir -p /mnt/wsl
$ sudo guestmount -o allow_other \
--add /mnt/c/Users/username/AppData/Local/Packages/CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc/LocalState/ext4.vhdx \
-i /mnt/wsl
And done! Hope this would solve your problem. :)
I have prepared executable from my perl code for distribution
It works fine on my own ubuntu 12.04 where it was created
It should work without perl on any system
But After execution of executable on Ubuntu 14.04 LTS, (64 bit) it gives
Error:
Can't load '/home/osboxes/Version-1/lib/vrt/16e8aba612e215bf6a5195289f1a16d8/Prima.so' for module Prima: libgif.so.4: cannot open shared object file: No such file or directory at <content>/DynaLoader.pm line 157.
After installing libgif4 it gave error
libtiff.so.4: cannot open shared object file: No such file or directory
What may be the cause for this and solution for this.
Ubuntu 14.04 LTS includes libtiff5 by default. Versions up to 13.04 had libtiff4. I made the executable compatible with libtiff4. also just installing libtiff4 by Ubuntu Software Center did not help so I installed it manually.
Downloaded it from here and installed by command:
sudo dpkg -i ./libtiff4_3.9.7-2ubuntu1_amd64.deb
I'm trying to follow this guide. I'm running both Ubuntu 12.04.5 LTS (GNU/Linux 3.13.0-74-generic x86_64) on "real" hardware and 14.04.1 via VirtualBox on my Mac. The problem is that I don't even get past Step 1:
hoffmann#angl99:~$ export CCPREFIX=/home/hoffmann/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-
hoffmann#angl99:~$ ${CCPREFIX}gcc -v
I'm then getting the following error:
-bash: /home/hoffmann/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: No such file or directory
However, the file that I'm told is missing is certainly there:
hoffmann#angl99:~$ less /home/hoffmann/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc
"/home/hoffmann/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc" may be a binary file. See it anyway?
This is probably the result of a basic error/misconception. Could anybody suggest a solution?
Thanks!
Sebastian
OK - I've worked it out (with the help of the person who posted the guide I'm trying to follow). It was indeed a basic issue...
The cross compiler binaries I was going to use are 32-bit and I was running a 64-bit system. I've now installed a 32-bit Ubuntu on VirtualBox and everything is running smoothly.