uname -r - shows running kernel version

dpkg -l | grep linux-image-.*-generic - shows installed kernel versions

Look for the kernel version you want to reinstall then run:

sudo apt-get install --reinstall linux-image-3.X.Y-ZZ-generic

By: E Carvalho

Add support for 32-bit applications

dpkg –add-architecture i386

apt-get update

apt-get install libxml2:i386 libssl1.0.0:i386 libXtst6:i386 libudev1:i386 libpcsclite1:i386 libtheora0:i386 libv4l-0:i386 libpulse0:i386 freerdp-x11 libatk1.0-0:i386 libgdk-pixbuf2.0-0:i386 libgtk2.0-0:i386 libxss1:i386 lib32stdc++6 lib32z1 lib32z1-dev

Fix some dependencies

ln -sf /lib/i386-linux-gnu/libudev.so.1 /lib/i386-linux-gnu/libudev.so.0

ln -sf /lib/i386-linux-gnu/libssl.so.1.0.0 /lib/i386-linux-gnu/libssl.so.1.0.1

ln -sf /lib/i386-linux-gnu/libcrypto.so.1.0.0 /lib/i386-linux-gnu/libcrypto.so.1.0.1

Install VMware Client

wget https://download3.vmware.com/software/view/viewclients/CART14Q4/VMware-Horizon-Client-3.2.0-2331566.x86.bundle

chmod +x VMware-Horizon-Client-3.2.0-2331566.x86.bundle

./VMware-Horizon-Client-3.2.0-2331566.x86.bundle

By: Camne

After a Kernel upgrade and a reboot on our CENTOS 6 server, it tried to boot with the following error: Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

After a ton of research we concluded that the initramfs was not created correctly during the kernel upgrade.

To fix this issue do the following:

1.  Boot into a live same version of Centos. Choose the recovery options.
2. Go through all of the default prompts, then drop down to shell.
3. Type: chroot /mnt/sysimage
4. Type: cd /boot
5. Type: ls -l initramfs*
6. Look at the version numbers and determine the last version that was installed.  Eg. initramfs-2.6.32-358.el6.x86_64.img
7. Type: dracut -f /boot/initramfs-2.6.32-358.el6.x86_64.img 2.6.32-358.el6.x86_64

This will rebuild the initramfs.  On reboot your system should come back up.

When in the directory you want to copy to do the following:

find /root-path-to-source-files-and-directories/ -name *2014*.mp4 -exec cp {} . ;

The . can be replaced with an actual target directory

Imagine this:
You stuck in a USB drive, you go in to try and write something or delete something and it says its read only filesystem. You type mount and notice the “ro” directive. Do you go and unmount and mount again? Nah.. Just remount.

There are 2 ways.
1) Remount all of the mounts of that device
2) Remount a specific mount of that device

To remount as readonly or readwrite every mount of the device

SYNTAX:
mount -o ro,remount [device]
mount -o rw,remount [device]

To remount a mounted partition as readonly

mount -o ro,remount /dev/sdb1
mount -o rw,remount /dev/sdb1

Even if you have several mounts of the same thing, they will all remount as readonly or readwrite

Also note that you dont have to specify the target only the device

———————-

To remount as readonly or readwrite only one mount of a device

SYNTAX:
mount -o ro,remount [destination folder]
mount -o rw,remount [destination folder]

To remount a specific mount folder and not every mount do this

mount -o rw,remount /media/USB_FLASH_1

Complications (METHOD UNSTABLE):

When you do the above method to only remount as readwrite or readonly a specific destination folder, well every mount that happened after the specified mount will get changed as well.

After doing some test this proved to be unstable… Sometimes only the destination folder would remount properly, and other times all of the destination folders would remount the same way

———————-

EXAMPLE:

I put in a usb sdcard and it was mounted like this

# mount
..snip..
/dev/sdb1 on /media/USB_FLASH_1 type vfat (ro,noatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=winnt,utf8,flush,errors=remount-ro)
/dev/sdb1 on /run/nfs4/media/USB_FLASH_1 type vfat (ro,noatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=winnt,utf8,flush,errors=remount-ro)

So I made it readwrite like this

# mount -o rw,remount /dev/sdb1

Now look at what mount says

# mount
..snip..
/dev/sdb1 on /media/USB_FLASH_1 type vfat (rw,noatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=winnt,utf8,flush,errors=remount-ro)
/dev/sdb1 on /run/nfs4/media/USB_FLASH_1 type vfat (rw,noatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=winnt,utf8,flush,errors=remount-ro)

Now lets make the /media/USB_FLASH_1 readonly (this is where the complication comes in, well hopefully it doesnt)

# mount -o ro,remount /run/nfs4/media/USB_FLASH_1

Verify

# mount
..snip..
/dev/sdb1 on /media/USB_FLASH_1 type vfat (rw,noatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=winnt,utf8,flush,errors=remount-ro)
/dev/sdb1 on /run/nfs4/media/USB_FLASH_1 type vfat (ro,noatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=winnt,utf8,flush,errors=remount-ro)

—-

(so here looks like it worked, and the complication didn’t happen)

What is this complication?
So in the previous command if the result of this command:
# mount -o ro,remount /run/nfs4/media/USB_FLASH_1
would of been (notice how both changed to ro, instead of just one… hence the complication)
# mount
..snip..
/dev/sdb1 on /media/USB_FLASH_1 type vfat (ro,noatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=winnt,utf8,flush,errors=remount-ro)
/dev/sdb1 on /run/nfs4/media/USB_FLASH_1 type vfat (ro,noatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=winnt,utf8,

By: KBoss