centOS: Installed programs are gone after reboot - centos

Hi I downloaded CentOS 6 live cd and installed the iso into a VM. When I install applications:
yum install git
The program git is installed, but after reboot the system no longer has git.
Am I installing the OS wrong? Do I need to burn it to a disk?

My guess is that you're still booting from the live cd image, thus your changes have only been saved in your system memory, and not actually written to disk.
If you've actually installed it detach the .iso from the virtual machine and give booting it another shot.

Related

I installed CentOS to VM but it doesn't work

I installed CentOs to VirtualBox. However, after installation finishes, i reboot the system but i get black screen again installation.There is no CentOS start command/button. All are about installation again. How can i fix this situation ?
You have installation media (CD/USB drive) before HDD in boot order. Just remove/unmount ISO and let VM to boot from HDD.

Migration from Fedora to CentOS

I did go through some articles about migrating to CentOS but not specifically from Fedora to CentOS. I'd like to know the steps and measures to follow
I don't think there is a migration path from CentOS to Fedora or vise versa. even though both systems share the same codebase CentOS is way older than Fedora. I used to be a distro hopper way back, but I kept the /home directory in a different drive so I could install any distro I wanted and keep my data and configuration files intact. You should consider doing the same.

Provision windows machine with vagrant to install github desktop

I try to install github desktop via chocolatey (vagrant provisioning) on my windows virtual machine. The installation process runs until the actual github installation. The error message looks like this:
Download of GitHubSetup.exe (663.49 KB) completed
WARNING: Ignoring checksums due to feature checksumFiles turned off or option --ignore-checksums set.
Installing github...
github has been installed.
Microsoft's ClickOnce framework is downloading and extracting the ~110
MB install files.
This may take several minutes or longer. Please wait...
The installation hangs at this point. I read about this issue at the official chocolatey webpage . How can I workaround this problem?

How to 'factory reset'/reinstall OS on the Intel Edison

I've filled up my Intel Edison 100% and have no room for anything more. I've emptied all logs and am still at 100%. I decided I want to factory reset and reorganize next time with the SD card better. Unfortunately I cannot find out how to reinstall completely the OS.
I've tried downloding the Yocto linux image off the intel downloads page, and uploading that to the Edison. However, it still is running the same as before...
For some reason I distinctly remember (pretty sure anyway...) reading a command to 'reset' everything. I just can't find any documentation now that I need it. Does anyone know how to do this?
Found the command, it's reboot ota
This is my checklist
Install dfu-util (on Linux: sudo apt-get install dfu-util)
Download Release 3.0 Yocto* complete image and unzip it
Connect the module using both USB connectors.
Run sudo ./flashall.sh --recovery
Wait for the script to finish and then a few extra minutes for the module to boot.
I've found one USB hub that didn't work, I had to connect directly to the USB port on the computer.
I'm not sure if you need both usb connectors but at least the one for main power is needed.
flashall.sh is found in the unzipped directory.

VMware Fusion and CentOS black screen

Just installed CentOS 5.8 on a VM using VMware Fusion 3.1.4 on my MB Mac OS X 10.7.4 and have the following problem. CentOS finished to install and re-start. The result, a nice black screen. I rebooted CentOS (on the VM) no success. I rebooted VMware Fusion, no success. I rebooted the whole machine (physical machine) no success.
Is there anywhere VMware Fusion log booting errors I can investigate why I have this annoying black screen?
VMware Fusion logs errors in the virtual machine's bundle.
So, for example, if your virtual machine appears on your hard disk on the desktop as:
myvm
you will find it in Terminal at:
cd ~/Desktop
ls -1 myvm*
... myvm.vmwarevm
then:
cd myvm.vmwarevm
you will see:
vmware.log
(and maybe vmware-0.log, etc, which will be older logs; vmware-0 being second most recent, vmware-1 being third most recent.)
A very late answer, but hope that is some help.