Home » Interclypse Blog
Red Hat Magic Sysrq Key Sequence (Stop-A for Red Hat Linux)
In the case when a system is inoperable or hung and needs to be rebooted you can use the Magic Sysrq key sequence from the system console. The only downside of this is that it must be activated before it can be accessed. To activate sysrq run the following command and add kernel.sysrq = 1 to /etc/sysctl.conf.
# sysctl -w kernel.sysrq=0
Now you can force a reboot using Sysrq:
- NOTE: The Sysrq key is the Prt Scr key
- Hit alt-sysrq-s. This will attempt to sync your mounted file systems so that changes to files get flushed to disk. You may hear or see disk activity. If you are looking at the console, the system should print the devices which were flushed.
- A few seconds later, hit alt-Sysrq-u. This will attempt to remount all your mounted file systems as read-only. You may hear or see disk activity. If you are looking at the console, the system should print the devices which were remounted.
- A few seconds later, use the alt-Sysrq-b to reboot the system
Are You Really Following an Agile Methodology?
I recently came across a project that stated they were following an agile methodology, specifically Scrum; however they had not delivered any usable software since the projects inception (over 18 months). In addition, they required a detailed specification prior to the start of development. The specification took over 6 months to produce by a separate team and required several review approval meetings before approval was given to begin development. Are they really following an Scrum? ABSOLUTELY NOT!
What is Scrum?
Scrum is the most popular agile methodology in use today. It was first introduced by Dr. Jeff Sutherland and Ken Schwaber in 1995 at OOPSLA. According to the Agile Alliance, Scrum is an agile, lightweight process that can be used to manage and control software and product development using iterative, incremental practices. Scrum, when used properly, significantly increases productivity and reduces time to market while facilitating adaptive, empirical systems development.
Scrum adheres to the values as defined in the Agile Manifesto: “Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
Twelve principles underlie the Agile Manifesto, including:
- Customer satisfaction by rapid delivery of useful software
- Working software is delivered frequently (weeks rather than months)
- Working software is the principal measure of progress
- Even late changes in requirements are welcome
- Close, daily cooperation between businesspeople and developers
- Face-to-face conversation is the best form of communication (co-location)
- Projects are built around motivated individuals, who should be trusted
- Continuous attention to technical excellence and good design
- Simplicity
- Self-organizing teams
- Regular adaptation to changing circumstances
Scrum practices:
- Three basic roles: Product Owner, ScrumMaster, and Project Team
- Product Backlog
- Sprint Backlog
- Sprint Planning Meeting
- Daily Scrum Meeting
- Thirty-day iterations, delivering increments of potentially shippable functionality at the end of each iteration
- Retrospectives
Simple questions to determine if you are following Scrum; if you answer no to any of the below then you are not adhering to Scrum.
- Do you have fixed/time boxed iterative development; typically 2-4 week sprints?
- Do you have working software at the end of each iteration or sprint?
- Do you have testing as part of the iteration or sprint?
- Do you have an integrated team that consists of the people formulating the product, the people building the product, the people testing the product, and the people that will use the product?
- Do you require a complete specification before you start development? If you do you are not following Scrum.
- Do you have daily meetings?
- Do you have product backlog?
- Do you have a product owner?
How to Flash the BIOS using a USB Stick
Flashing a computers BIOS is a task most have little experience in doing. Although, the steps outlined here are quite simple one must still be cautious so that your computer is not left in an unusable state. This article focuses on the basic steps and explains why it is necessary to flash the BIOS, precautions, and how to recover in case of a bad flash.
What is the BIOS and why do you need to flash it?
BIOS stands for Basic Input/Output System. It is the most basic component in your computer and determines what your computer can do without accessing any other files or programs from the hard drive. The BIOS contains all the information needed for your computer to Power on Self Test (POST), which is needed in order for the computer to boot. The BIOS also includes how to control your keyboard, communicate with your CPU, send/receive video signals to/from your monitor, and recognize your components (hard drives, optical drives, USB devices, serial ports).
Why should we flash the BIOS?
Flashing your BIOS to the latest release is crucial because it enhances your system's capabilities, helps it to detect newer devices and components (newer hard drivers, newer CPUs, etc), and improves stability through the introduction of patches by the manufacturer.
Steps
- Make sure you have a USB stick. Since the original method to flash the BIOS was using a 1.44MB floppy USB size is not important - they are all greater than 1.44MB
- Download the BIOS version appropriate for your motherboard.
NOTE: BE SURE TO READ THE DOCUMENTATION TO MAKE SURE YOU HAVE PICKED THE CORRECT VERSION.
- Download HP USB Disk Storage Utility used to format and make your USB stick bootable
- Download the DOS bootable files
- Install the HP USB Disk Storage Utility
- Unzip the DOS bootable files to your C: drive
- Insert your USB stick in your computer
- Run the HP USB Disk Storage Utility software. NOTE: With Microsoft Vista you need to start the software as an administrator by right clicking on the icon and selecting "Run as Administrator".
- Select your USB as the “Device”, FAT as the “File system”, BOOTDISK as the “Volume label”, select “Quick Format”, Select “Create a DOS startup disk”, and enter C:\win98boot (or the path where you downloaded the DOS bootable files. Then select the “Start” button. This process only takes a few seconds.
- (Optional) Check the USB stick; there should be 3 files installed on it: command.com, io.sys and msdos.sys. If you do not see them you may have to unhide them by selecting Tools->Folder Options->View unselect the ”Hide protected operating system files (Recommended)”.
- Next copy the exploded BIOS upgrade files you already downloaded to the USB stick
- You are now ready to flash
- Reboot your system and enter BIOS setup (usually by selecting the F2 key during initial boot)
- Move to the Boot tab
- Change your USB stick to be the first on the list
- Save and exist the BIOS setup
- A reboot will occur; this time booting from your USB stick
- Once booted you will be left at a DOS prompt
- Change directory to where the updated BIOS files were saved
- Execute the program (typically you just type "flash" at the prompt) as indicated in the BIOS flash update documentation
- Remove the USN stick
- Reboot the system
Precautions
- Flashing the BIOS can be dangerous if the flashing process isn't finished successfully or if the newly flashed file doesn't match your system or is incorrect
- Never flash if there is possibility of losing electricity
- Before proceeding to flash don't forget to go into your BIOS and write down all of your settings. This is crucial because the "default" settings may not be the best option for your system, especially if you've tweaked BIOS
- Do NOT reboot and/or shut down your system while flashing
Page 1 of 1 pages