August 17

Linux: Installing VMWARE Horizons on Ubuntu 14.04 64bit

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

Category: Linux | Comments Off on Linux: Installing VMWARE Horizons on Ubuntu 14.04 64bit
August 4

Linux: Centos/Redhat Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

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.

Category: Linux | Comments Off on Linux: Centos/Redhat Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
April 14

Linux: Remount as read write or read only – ro rw

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

Category: Linux | Comments Off on Linux: Remount as read write or read only – ro rw
April 14

Linux: How to access Time Machine

Recently after switching from Mac OS X to Debian, I found I needed to restore a couple files from the Time Machine backup that I kept. The drive works just fine as an HFS+ mount, but I couldn’t figure out how to retrieve anything within. When Google didn’t yield the answer, I began to explore on my own.

It turns out Apple does a couple slick things with the file system to make incremental backups work, including hard linking to directories, which isn’t allowed in Linux. So for anyone that needs to access their Time Machine from something other than its associated Mac, here’s how you do it…

  1. Mount the drive. On linux, it should automount if you have gnome-volume-manager installed. If you don’t see it in /media, then run nautilus and check the desktop. Still don’t see it? Read man mount. And then don’t forget the -t hfsplus flag.
  2. Change directory. My mount point is /media/Time Machine/. Within that path, I find the directory Backups.backupdb. This represents the directory layout of your backup system. Inside that directory is the name of your disk. Inside that are folders labeled with dates corresponding to each incremental backup that was made. Pick the one you want, or choose the Latest symlink. For example, my path is now: 
    /media/Time Machine/Backups.backupdb/Drive 1/2008-06-05-073745
  3. Find your file’s folder. Within that path is a complete representation of your filesystem. Navigate to the location of your file. If it’s not too big or nested too deep, it may be plainly visible. However, there’s a good chance that its parent directory doesn’t exist. Instead you’ll see a zero-byte file for the parent that takes its name and acts as a pointer. Run ls -l and take note of the first numbered column. Example: 
    ...
-r--r--r-- 2155704 root 5791966       0 2007-06-25 02:54 Wallpaper
-r--r--r-- 2155725 root 5791967       0 2007-06-25 02:54 Web-Identity
-r--r--r-- 5441953 root 5791968       0 2007-06-25 02:54 Windows
-r--r--r-- 5511926 root 5791969       0 2007-06-25 02:54 Work

    After the permissions, you’ll see the directory number that typically refers to the number of directories within that folder. For a file, it should always be 1, but here it is not. What Apple has done is adjust the information in this file’s inode to use it as a pointer to the directory that contains the actual file. That way, multiple revisions of the same drive can coexist without duplicating data.

  4. Find the data. In my case, I want to grab something out of the Wallpaper folder. First I made a note of the directory number, 2155704, and then did cd /media/Time Machine/.HFS+ Private Directory Data — this is where the data really lives. From there, I just did cd dir_2155704, and voilà!

By: CBaker

Category: Linux | Comments Off on Linux: How to access Time Machine