Translate

Image of Android Wireless Application Development
Image of Linux Kernel Development (3rd Edition)
Image of RHCE Red Hat Certified Engineer Linux Study Guide (Exam RH302) (Certification Press)
Image of Advanced Programming in the UNIX Environment, Second Edition (Addison-Wesley Professional Computing Series)

UEFI-based Windows 10 Platform - Failure to Boot Due to Missing or Corrupt BCD

I was prompted to write this post as a result of Windows 10 Professional recently attempting to do a silent update while I was waiting in an airport which I unknowingly interrupted when I powered down my UEFI-based laptop prior to boarding the plane. When I later powered on the laptop, it failed to boot and simply displayed the following message: A Boot Configuration Data (BCD) store (there can be more than one) contains boot configuration parameters which control how the operating system is started in Windows 10. First introduced in Windows Vista, these parameters were previously stored in the

Korn Shell Launcher for Windows Subsystem for Linux

According to Microsoft, the Windows Subsystem for Linux (WSL) is a new Windows 10 feature that is essentially a compatibility layer which enables you to run native Linux command-line tools and utilities directly on Windows 10, alongside your traditional Windows desktop applications. Currently a beta feature, it is scheduled to be officially released in the Windows 10 Anniversary Update which is due CY2016Q3. There is no support for Linux GUI-based or TUI-based tools, utilities or applications not is any planned. When WSL is enabled, a Canonical-created Ubuntu user-mode image (currently named trusty-server-cloudimg-amd64-root.tar.gz and based on Ubuntu 14.04 Long-Term Support) is

Creating a UEFI Rescue DVD

Developing a UEFI rescue DVD containing a set of useful UEFI-related utilities is a personal project that I work on from time to time. I own a number of laptops with UEFI firmware and have encountered a myriad of strange UEFI-related booting issues on these laptops over the last few years. In fairness, some of these issues were due to early versions of UEFI firmware but a lot are not. Here is my current build script for creating a UEFI-bootable ISO: #!/bin/bash ISONAME="urd-dvd.iso" TOPDIR=$(pwd) # preparation [[ -d ./build ]] && rm -rf ./build [[ -f ${ISONAME} ]] && rm

GNS3 Cloud and VMware Host-Only Adapter

When you research how to connect a VMware guest to GNS3, you will find many articles advocating the use of a Microsoft loopback adapter. Here is one such example from Intense School. Equally you will find many requests for help from people who ran into trouble setting up such such a configuration. Reasons for loopback connectivity failure include Microsoft firewall issues, MAC address issues and IPv4 configuration issues. I typically create a host-only network when I am testing or using VMs as I do not have a need for external connectivity for such VMs. I prefer not to use the

Installing Oracle 11g Release 2 on Fedora 14

This post will show you how to install Oracle Database 11g Release 2 on Fedora 14 (Laughlin), configure Oracle Enterprise Manager to access the database and how to access the database from a Window platform using Oracle SQLPlus Instant Client. Note, however, that Oracle Database 11g R2 is not certified by Oracle to run on Fedora 14 so you will not get support from Oracle if you have any questions. The following steps should be done as root. First add a number of kernel parameters to /etc/sysctl.conf if they do not already exist in this file or have values less