Linux Solutions

The article will educate a user on how to make a USB Boot CD for Ubuntu 11.10.Please note that creating a USB Boot CD that can be used to boot the Ubuntu Live 11.10 USB Flash Drive from a PC or Mac with a BIOS that doesn’t natively support booting from a USB device (USB drivers are loaded from CD).

A boot menu option has been included for booting from a Macbook (forcing bypass of the Nouveau nVidia drivers, which do not play well with a Macbook.).
Boot CD for Ubuntu 11.10 USB Prerequisites
• PC or Macbook that can Boot from a Live CD
• USB flash drive with Ubuntu preinstalled
• Working CD Burner and USB Port
• Active Internet Connection
Making a USB Boot CD to Boot Ubuntu 11.10 from a Flash Drive
A user can prefer to perform the following steps by booting from a prebuilt Live Ubuntu Flash Drive created using UUI, using a machine that does support booting from USB. This allows us to free up the CD Burner and use it to burn the final ISO.
1. Insert the Ubuntu Live USB (or Ubuntu CD) and restart your computer, booting from the CD or USB
2. Open a Terminal
3. Type sudo apt-get update
4. Type sudo apt-get install –reinstall nvidia-current grub
5. Type mkdir -p ubcd/boot/grub
6. Type cp /usr/lib/grub/i386-pc/stage2_eltorito ubcd/boot/grub
7. Type gedit ubcd/boot/grub/menu.lst
Add the following information to your menu.lst file and click save:
title Start Ubuntu from USB DISK (MACBOOK)
root (cd)
kernel /boot/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper noprompt cdrom-detect/try-usb=true persistent nouveau.noaccel=1 blacklist=vga16fb
initrd /boot/initrd.lz
boot
title Start Ubuntu from USB DISK (PC)
root (cd)
kernel /boot/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper noprompt cdrom-detect/try-usb=true persistent
initrd /boot/initrd.lz
boot
1. Type cp /cdrom/casper/vmlinuz ~/ubcd/boot
2. Type sudo gedit /etc/initramfs-tools/modules
Add the following lines to the modules file and click save:
usbcore
usb-storage
uhci_hcd
ohci_hcd
ehci_hcd
sd_mod
scsi_mod
3. Type sudo gedit /etc/initramfs-tools/initramfs.conf
Add the following line to the bottom of the file and click save:
WAIT=8
4. Type sudo mkinitramfs -o ubcd/boot/initrd.lz
5. Type mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot -boot-load-size 4 -boot-info-table -o usbcd.iso ubcd
6. Insert a blank CD and type brasero -i usbcd.iso (to burn the usbcd.iso to a CD)

The article will provide a reader with information on the development of Linux. 1986 Linus (Benedict) Torvalds programmed its own driver for its floppy controller. He learned intensively hardware programming and became better knowledge about his Sinclair computer with Q-DOS.

Additionally he provided his own programmer Tools. When 1991 the 386-Intel PC became modern, he got one PC to learn about the programming of 386 CPUs. As operating system the Unix derivate MINIX was used, he has know Unix already since 1990 from its university. Minix was developed by Andrew Tanenbaum as learning system and was particularly used at universities. The written book from A. Tanenbaum “Operating Systems: Design and Implementation” is about operating system concepts and Minix, which became the favourite book from Torvalds. The source code of Minix is open source, any modifications are bound to the license conditions.

Because he did not find the provided terminal emulator program in Minix acceptable, he began his project to code his own and better terminal emulator with more functions on hardware level. In addition he programmed his own drivers for the data medium access and the file system and others in assembler. With these functions the software becames the ability to upload and download from the Internet. In the line of the development terminal program got more and more functions so he made the decision to enhance it to a operating system. Its operating system was derivated from concepts of Minix but completely written from scratch beginning at the Kernel.

After long programming evenings it was so far. On 17th September 1991 the operating system Freax version 0.01 was finished, as development environment was used still the MINIX for 386 CPUs. It contained already the GNU Shell bash and the GNU C-compiler GCC from Richard Stallman, which counts to the standard programs for the meantime named operating system Linux. Because Linux profits particularly from the GNU software pool, it is generally called GNU/Linux.

After approximately 6 months Freax was renamed in Linux. Already on 3th July 1991 he had asked for the POSIX standards in the minix-newsgroup, he presented on 25th August 1991 his project in public and asked for suggestions for further functions and extensions. The source code was made freely accessible by ftp. To communicate with other programmers and interested people he used the Maylinglist “Linux-activists@niksula.hut.fi” and the newsgroup “comp.os.minix” for contact and progress messages. Later its own Maylinglist and forums were created.

In the line of the development he received wished postcards from all over the world with thankfully words. The project has got a strong self-dynamic in the InterNet and was maintained by the community. The rights at the brand name Linux was transferred after a legal incident to Linus Torvalds and later distributed on several persons to ensure the further development and to avoid a “takeover by enemys”. The symbol figure “Tux the penguin” was selected because Torvalds was bitten by a penguin in a Finnish zoo. The self-willed animal had impressed him in such a way, which it gave to its operating system this guidance figure. At the beginning Linux doesn`t contain any installation script or graphical installation menu. To make the installation from Linux easier and automated Owen LeBlanc from the Manchester Computing Centre published the MCC Interim release, this was the key for the automated installation of today’s distributions.

Virtualisation helps business generate value from IT by becoming more flexible to the evolutionary needs of customers, staff and markets. Yet as IT transcends all levels of business, how do organisations incorporate usability with collaboration and compliance if the only virtual environments available are too expensive for them to implement?

The problem has long been that leading virtualisation platforms have been built almost exclusively for public consumption on Windows. Not a problem at all you may say! But whilst delivering supreme performance and security, migrating to such a solution has been too expensive for many organisations to justify.

Today however, there are many options such as those provided by Peer 1 Hosting that offer cost effective solutions that can be optimised with speed and agility around virtual infrastructure that doesn’t break the bank. Driving application delivery, performance optimisation and flexible working practice for a growing user community, we also can see that Linux has now become a viable alternative to Windows virtualisation.

Where previously, Linux virtualisation was too complex to use without considerable technical acumen and offered limited ease of use, it is now fast becoming the platform of choice for many businesses, for two primary reasons.

1. Customised Usability
Our ability to adapt to changing market conditions and capture customer insights requires IT that delivers speed and agility in real-time. Early forms of virtualisation environment, such as off-the-shelf offerings for a Windows OS, delivered regimented (boxed) functionality. While they still provide many benefits, we are increasingly challenged, and somewhat threatened, by the need to use IT in unique ways. How else can you be first to market, offer competitive prices, facilitate bespoke roles and responsibilities, and secure so much data?

Using an off-the-shelf virtualisation platform creates limited opportunities to customise. This is so crucial in getting the most out of server capacity, network bandwidth and the data you process. The open source flexibility of Linux virtualisation offers endless opportunities for customisation of a virtual IT infrastructure. While Linux server virtualisation still plays catch-up to Windows for pure usability, having such a flexible environment creates tremendous advantages as a scalable virtualised IT model, at low cost. It is significantly lower than a ‘paid for’ Windows virtualisation platform that may provide optimum speed, but for how long when your business needs to expand capacity based on changing industry trends and opportunities in the market?

2. Scalable Usability
Virtualisation is renowned for the highest levels of resilience. It offers the flexibility to dynamically reallocate server resources where they are needed most. In direct competition, Windows and Linux virtualisation both offer substantial upfront cost savings to rolling out IT as a physical footprint on-site. Yet Windows, as a subscription or paid-for service, has long been seen as the best choice because it is easier to manage and crucially provides a better end user experience.
However, this is rapidly becoming a thing of the past as major developments in usability make Linux virtualisation a genuine alternative. Graphical interfacing capabilities now make Linux virtualisation an extremely intuitive platform of choice for many.

For server, desktop, storage, network and middleware maintenance at scale, a business needs to utilise the most lightweight virtualisation platform it can. As such, pressures are mounting to implement virtualisation with extreme scalability. Many SMBs cannot justify the upfront or residual costs of running a Windows virtualisation environment, yet in a business world dictated by mobile and BYOD trends, it is virtually impossible for anyone to scale operations with physical IT run in-house.

Linux virtualisation offers much greater levels of usability and support than ever before. As storage, network bandwidth and desktop virtualisation become major components of IT going forward, Linux virtualisation offers the best low cost option.

 

The article will provide a reader with information on programming and use of Linux.

Most Linux distributions support dozens of programming languages. The original development tools used for building both Linux applications and operating system programs are found within the GNU toolchain, which includes the GNU Compiler Collection (GCC) and the GNU build system. Amongst others, GCC provides compilers for Ada, C, C++, Java, and Fortran. First released in 2003, the Low Level Virtual Machine project provides an alternative open-source compiler for many languages. Proprietary compilers for Linux include the Intel C++ Compiler, Sun Studio, and IBM XL C/C++ Compiler. BASIC in the form of Visual Basic is supported in such forms as Gambas, FreeBASIC, and XBasic, and in terms of terminal programming or QuickBASIC or Turbo BASIC programming in the form of QB64.

A common feature of Unix-like systems, Linux includes traditional specific-purpose programming languages targeted at scripting, text processing and system configuration and management in general. Linux distributions support shell scripts, awk, sed and make. Many programs also have an embedded programming language to support configuring or programming themselves. For example, regular expressions are supported in programs like grep, or locate, while advanced text editors, like GNU Emacs have a complete Lisp interpreter built-in.
Most distributions also include support for PHP, Perl, Ruby, Python and other dynamic languages. While not as common, Linux also supports C# (via Mono), Vala, and Scheme. A number of Java Virtual Machines and development kits run on Linux, including the original Sun Microsystems JVM (HotSpot), and IBM’s J2SE RE, as well as many open-source projects like Kaffe and JikesRVM.

GNOME and KDE are popular desktop environments and provide a framework for developing applications. These projects are based on the GTK+ and Qt widget toolkits, respectively, which can also be used independently of the larger framework. Both support a wide variety of languages. There are a number of Integrated development environments available including Anjuta, Code::Blocks, CodeLite, Eclipse, Geany, ActiveState Komodo, KDevelop, Lazarus, MonoDevelop, NetBeans, Qt Creator and Omnis Studio, while the long-established editors Vim, nano and Emacs remain popular.
Uses
As well as those designed for general purpose use on desktops and servers, distributions may be specialized for different purposes including: computer architecture support, embedded systems, stability, security, localization to a specific region or language, targeting of specific user groups, support for real-time applications, or commitment to a given desktop environment. Furthermore, some distributions deliberately include only free software. Currently, over three hundred distributions are actively developed, with about a dozen distributions being most popular for general-purpose use.

Linux is a widely ported operating system kernel. The Linux kernel runs on a highly diverse range of computer architectures: in the hand-held ARM-based iPAQ and the mainframe IBM System z9, System z10; in devices ranging from mobile phones to supercomputers. Specialized distributions exist for less mainstream architectures. The ELKS kernel fork can run on Intel 8086 or Intel 80286 16-bit microprocessors, while the µClinux kernel fork may run on systems without a memory management unit. The kernel also runs on architectures that were only ever intended to use a manufacturer-created operating system, such as Macintosh computers (with both PowerPC and Intel processors), PDAs, video game consoles, portable music players, and mobile phones. See List of Linux supported architectures.

There are several industry associations and hardware conferences devoted to maintaining and improving support for diverse hardware under Linux, such as FreedomHEC.

The article will provide a reader with information on YUMI – Multiboot USB Creator (Windows).

YUMI (Your Universal Multiboot Installer), is the successor to MultibootISOs. It can be used to create a Multiboot USB Flash Drive containing multiple operating systems, antivirus utilities, disc cloning, diagnostic tools, and more. Contrary to MultiBootISO’s which used grub to boot ISO files directly from USB, YUMI uses syslinux to boot extracted distributions stored on the USB device, and reverts to using grub to Boot Multiple ISO files from USB, if necessary.

Aside from a few distributions, all files are stored within the Multiboot folder, making for a nicely organized Multiboot Drive that can still be used for other storage purposes.
Creating a YUMI Multiboot MultiSystem Bootable USB Flash Drive
YUMI works much like Universal USB Installer, except it can be used to install more than one distribution to run from the USB. Distributions can also be uninstalled using the same tool.
Fixed broken LMDE 201204 Install options. Update to support HDT 5.2, and Debian Live 6.0.6. Correct several dead links.

How to Create a MultiBoot USB Flash Drive
1. Run* YUMI-0.0.8.4.exe following the onscreen instructions
2. Run the tool again to Add More ISOs/Distributions to your Drive
3. Restart your PC setting it to boot from the USB device
4. Select a distribution to Boot from the Menu and enjoy!

A user should now be booting the favourite distributions from the custom Multi-Boot USB device. How It Works: YUMI (Your Universal Multiboot Installer) enables each user to create their own custom Multiboot UFD containing only the distributions they want, in the order by which they are installed. A new distribution can be added to the UFD each time the tool is run. If a user runs YUMI from the same location store ISO files, they should be auto-detected, eliminating the need to browse for each ISO.

If MultibootISOs was previously used, a user must reformat the drive and start over. YUMI uses Syslinux directly, and chainloads to grub only if necessary, so it is not compatible with the older Multiboot ISO tool.

The distro uninstaller works great, but unlisted ISO’s that have been added must currently be manually removed. Please note that not all Unlisted ISO’s can be booted (thus adding unlisted ISO’s is an unsupported option).

The article will provide a reader with the spam forward script.

All the spam that has come through the RBLs and Spamassassin into the “Spam” folder where the spams are actually put into the subfolder “cur”.
What is required now is setting up a script that loops through the folder and forwards the emails to spamcop.
Here it is:
fe.sh (forward email script)
#!/bin/bash

# ENTER PATH OF THE EMAILS THAT ARE TO BE SUBMITTED TO SPAMCOP
FPATH=”/home/mail/web4p1/Maildir/.Spam/cur”

# ENTER YOUR SPAMCOP EMAIL ADDRESS
EMAIL=”…….. a.t. spam.spamcop.net”

#################################################################
#################################################################

cd $FPATH

for FILENAME in *
do

# Create email and submit it to the supplied spamcop address
/usr/bin/mime-construct \
–subject “Forwarded spam (MIME encoded)” \
–attachment “Original message” \
–type message/rfc822 \
–encoding base64 \
–file $FILENAME \
–to “$EMAIL”

# Train this email to be spam to the bayesian SA filters
/usr/bin/sa-learn –spam $FILENAME

# Delete email
/bin/rm $FILENAME

done
All in all, this is a very simple script and just two things need to be adjusted:
1.) The PATH variable needs to point to your spam/cur folder
2.) The EMAIL variable needs to be set to the one you have received upon signing up at spamcop
Spam verification script
As said in the prerequisites we also need a folder where the verification emails from spamcop go to. This can be either a complete new email account or some folder combined with some email filtering. I have opted for the second option and I use procmail to filter my incoming email:
:0:
* ^To: spamcop a.t. roleplayer.org

Maildir/.Spamcop-Reply/
Now that we have another folder for the verification emails we need to filter out the unique ID that is contained in them. I have created this little script to get the whole url:
vs.sh (verify spam script)
#!/bin/bash

# ENTER PATH OF THE VERIFICATION EMAILS FROM SPAMCOP
FPATH=”/home/mail/web4p1/Maildir/.Spamcop-Reply/cur”

# ENTER WEBPATH TO PHP SCRIPT
URL=”http://www.domain.com/spamcop/index.php”

#################################################################
#################################################################

cd $FPATH

for FILENAME in *
do

# Get the supplied URL from the spamcop email
DATA=`/bin/grep -F http://www.spamcop.net/sc?id= $FILENAME`
echo $DATA

# Submit the URL to the PHP script
/usr/bin/lynx -dump $URL?data=$DATA

# Remove that file
/bin/rm $FILENAME

done

Again, quite a simple script. All it does is go to the path given, loop through all the emails contained there, filtering out the line with the ID and passing that information to a PHP script (which will then do the actual form submission).
1.) The PATH variable needs to point to the spam/cur folder.
2.) The URL variable needs to be set to the weblocation of the script.
Spamcop form submission script
index.php (form submission script)
0)) {
print(“

“);
print(“

“);
foreach ($aArray as $aKey => $aValue) {
print(“

“);
if (!is_array($aValue)) {
if (empty($aValue)) {
print(“

“);
} else {
print(“

“);
}
} else {
print(“

“);
}
print(“

“);
}
print(“

Key	Value
$aKey	$aValue	$aKey	$aValue	$aKey(array)	“); displayArray($aValue); print(“

“);
} else {
print(“empty or invalid“);
}
}

The article will provide a reader with information on BIOS settings using USB tricks and settings. The system BIOS can be complicated to someone who is not yet familiar with all of the settings. Here are a few tips to help increase the chances of successfully booting a USB Linux system.

If the flash memory stick fails to boot, go back into the system BIOS and try changing some of the following settings (Be sure to take note on any changes that a user has made). In addition, we have included some other tips to help achieve a successful boot.
BIOS setup tips for USB Boot:
• Switch on or off USB keyboard support
• Turn off Fast Boot
• Disable USB 2.0 support (last resort, this will default to USB 1.1)
Other tips to help a user to Boot from USB:
These are some other suggestions to help ensure a successful USB Linux Boot:
• Unplug USB hubs and extensions (these may draw from the current needed to wake the USB device)
• Try using a different USB port. (some frontal ports may not be fully supportive)
• Unplug additional USB devices. (I’ve seen something as simple as an IPod halt a system boot)
• Sometimes a USB drive may go undetected at startup. If a user’s drive has an LED, ensure that it either flashes or remains solid during system post. If the drive does not respond, remove the drive, then power the system completely down for 15 seconds, reinsert the drive and try again.
• Some laptops using a PCMCIA slot may have troubles booting. A user may have to tell Linux to ignore PCMCIA during boot. A user can do this in the syslinux.cfg file by simply adding “nopcmcia” to the default boot options or by using a cheatcode before boot.
Common USB BIOS boot options
The following list of USB BIOS boot options have been thoroughly tested with various Linux USB installs. There may be others but this is meant to be a simple checklist to familiarize a user with the boot options and which ones to use. Be sure to check back often as we will be constantly adding new information to this list over time.
Newer BIOS Boot Menu:
Many newer computers detect the USB device as a hard drive (USB-HDD0). In which case, a user can press a specific key (F2, F10, F11 or ESC) during system post to access the “Boot Menu”. Select the USB DISK from the Boot Menu and resume startup.
Older BIOS Setup method:
If a user’s system is a bit older or uses a simplified BIOS, a user may not have a Boot Menu option. In this case a user will need to make the system detect and boot the USB device by changing the settings in the BIOS.
Older BIOS Boot Options:
1. USB-HDD ” Preferred boot method”
2. USB-ZIP “May or may not work”
3. USB-FDD “Unsupported”
Summary:
Generally speaking, if a users system BIOS supports the USB-HDD boot option, it should boot Linux from a large capacity USB flash drive. (a BIOS that supports USB-HDD automatically detects the geometry of the USB Flash drive)
The USB-ZIP option is typically used on older systems that do not support USB-HDD boot. Using this boot option might require modifying the drive geometry to match how the BIOS has been hard-coded to see the device.
Exception: The USB-ZIP boot option may allow a user to boot some larger capacity flash drives without drive geometry modification, if a users BIOS also lists the flash drive as a selectable hard drive under boot priority. (Typical of the Award-Phoenix BIOS)
If a user’s BIOS lists the USB memory stick as a hard drive, a user should select it as the 1st boot device.
A user should always remove other USB boot options from the boot priority list when attempting to boot from USB-ZIP or USB-HDD to avoid conflicting startup Cues.
The file-system used may also affect the BIOS’s ability to detect and boot the drive. If a Fat file-system doesn’t work, try Fat32. The partition must also be active or the device will not boot.

The article will provide a user with information on open SUSE 12.3 Milestone 2.
In a change to policy, KDE 4.10 Beta 2 has been added to Factory already. Usually only finished KDE releases are added, but since more KDE team developers are working on Factory, it made sense to perform early integration and testing in Factory now. So, if everything goes as planned, the final version of openSUSE will arrive in March including KDE 4.10.0 or 4.10.1. This new version of KDE increases the Qt Quick usage in Plasma Workspaces. In 4.10, additional desktop components are implemented using this declarative technology instead of C++ for greater stability and easier theming. Okular now uses less memory when zooming in on big PDFs, and a new indexer replaces the last Strigi components, allows faster and more reliable indexing of documents.
Other KDE changes include kwebkitpart 1.3, which adds Access Key support, automatic scrolling and manual spell checking support for forms, as well as on demand plugin loading; and appmenu-qt joins the standard installation, allowing application menus to be shown at the top of the screen or in a menu button on the window border.
After a period of stabilization work, GNOME 3.6.3 found its way into this milestone. The GNOME interface for PackageKit is at version 3.6.1, which fixes a segfault error when a distribution upgrade is available. This GNOME version is better integrated with systemd, and has a new “Airplane Mode”, that switches off all radios, including Bluetooth.
Claws Mail has been updated to 3.9. This little GTK email client and news reader is known for being fast, extensible and easy to configure. It adds IMAP server side search, has several speed-ups and optimizations, a better GnuPG integration and more than thirty bug fixes.
The GNU C library was updated. glibc 2.17 improves ARM and multi-arch subsystems, and adds fixes for crypto bugs. DBUS 1.6.8 includes new service ownership rule possibilities, and many security, bugs, and performance fixes.
Another updated package is QEMU, which goes from 1.2.0 to 1.3.0. With QEMU we can easily create and run virtual machines. This new version improves live migrations of virtual machines. That means that we can now stop a virtual machine and continue the execution in another place without noticeable problems. QEMU 1.3.0 adds many newly virtualized devices and chipsets.
LLVM is one of those cool projects that everyone knows, but few can exactly say what it is. Fascinate Xmas parties with the knowledge that LLVM is a set of libraries that allow aggressive optimizations of an intermediate ad-hoc language (known as LLVM IR) and the compilation of this language to a specific architecture and processor. Clang is a C / C++ / Objective-C compiler that translate the high level language to this IR language, and is a really fast compiler. If this description interests a user then a user will be pleased to know that M2 updates LLVM/Clang to 3.2rc2. This version of LLVM improves the Clang diagnostics, this means that we will have better error messages that explain more clearly what mistakes we are making. LLDB is the new command line debugger for LLVM/Clang. It uses the Clang parser for the C++ debugger. And there is a lot of new functionality in the optimizer, like a new high-level loop optimizer and the automatic parallelizer.
libzypp 12.5 includes new package management transaction logging features.
As part of the SuSEconfig removal work, permissions now applies changes following installation or upgrade, to ensure new permissions are effective regardless of package installation order.

YUMI (Your Universal Multiboot Installer), is the successor to MultibootISOs. It can be used to create a Multiboot USB Flash Drive containing multiple operating systems, antivirus utilities, disc

cloning, diagnostic tools, and more. Contrary to MultiBootISO’s which used grub to boot ISO files directly from USB, YUMI uses syslinux to boot extracted distributions stored on the USB device, and reverts to using grub to Boot Multiple ISO files from USB, if necessary.

Aside from a few distributions, all files are stored within the Multiboot folder, making for a nicely organized Multiboot Drive that can still be used for other storage purposes.

Creating a YUMI Multiboot MultiSystem Bootable USB Flash Drive
YUMI works much like Universal USB Installer, except it can be used to install more than one distribution to run from a userr USB. Distributions can also be uninstalled using the same tool.

How to Create a MultiBoot USB Flash Drive?
1. Run* YUMI-0.0.8.1.exe following the onscreen instructions
2. Run the tool again to Add More ISOs/Distributions to a userr Drive
3. Restart a userr PC setting it to boot from the USB device
4. Select a distribution to Boot from the Menu and enjoy!

A user should now be booting a userr favorite distributions from a userr custom Multi-Boot USB device.

How It Works:
YUMI (A userr Universal Multiboot Installer) enables each user to create their own custom Multiboot UFD containing only the distributions they want, in the order by which they are installed. A new distribution can be added to the UFD each time the tool is run.
If a user run YUMI from the same location a user store ISO downloads, they should be auto-detected, eliminating the need to browse for each ISO.

If MultibootISOs was previously used, a user must reformat the drive and start over. YUMI uses Syslinux directly, and chainloads to grub only if necessary, so it is not compatible with the older Multiboot ISO tool. Although I do plan to add back most of the capabilities of MultibootISOs as time permits.

The distro uninstaller works great, but unlisted ISO’s that have been added must currently be manually removed! Also note that not all Unlisted ISO’s can be booted (thus adding unlisted ISO’s is an unsupported option).

Basic Essentials to create a MultiSystem Bootable USB Drive
• Fat32 or *NTFS Formatted USB Flash or USB Hard Drive
• PC that can boot from USB
• Windows XP/Vista/7 or WINE to create the Bootable USB
• YUMI-0.0.8.1.exe
• A userr selection of ISO Files

The Windows XP Installation from USB option currently works by booting directly from a userr XP ISO, hence the YUMI menu entry is created under “Directly Bootable ISOs”. In order for the Windows XP installation to succeed, a user must perform the following steps;

1.) To begin an install, select (Stage 1)
2.) Upon first reboot, a user must select (Stage 2)
3.) Finally, after (Stage 2) is complete – upon the second reboot, select (Stage 3) to boot the drive where a user installed Windows XP. If this option fails, simply remove the USB and reboot!
When using the “Try an Unlisted ISO option”, the ISO file name must contain no spaces.
* YUMI does support NTFS, however not all distributions will boot from an NTFS formatted device.
* When installing Windows 8, 7, or Vista from USB, a user must unplug the USB device before the first restart, otherwise a user will receive an error stating:
“windows setup could not configure windows to run on this computer’s hardware”.

The article will provide a user with information on system requirements for the Server.SUSE Linux Enterprise Server helps you save money, deliver mission-critical data center services reliably and securely and get the most out of your mixed IT environment.

• Reliability, Availability and Serviceability

• Advanced Security

• Cross-Platform Virtualization

• Simplified Administration, Development and Systems Management

• Interoperability with Other platforms

System Requirements • Minimum Linux server system requirements for installation • Local Installation: 512 MB RAM • Secure Shell (SSH)-based network install, graphical: 512 MB RAM • Virtual Network Computing (VNC)-based network install using File Transfer Protocol (FTP): 512 MB RAM  Minimum Linux server system requirements for operation • 512 MB RAM • 750 MB hard disk space for software • 750 MB hard disk space for user data  Recommendations for specific uses • 512 MB to 4 GB RAM, at least 256 MB per CPU • 4 GB hard-disk space • Network interface (Ethernet, wireless or modem) • For Xen virtual host server—at least 512 MB RAM for each virtual host server • For KVM virtual host server—the limits are equal to those of SUSE Linux Enterprise Server • For Xen or KVM virtual machines—at least an additional 256 MB RAM for each virtual machine • For print servers—a relatively faster processor or additional processors to improve server-based printing • For web servers—additional RAM to improve caching, and additional processors to improve web application performance • For database servers—additional RAM to improve caching, and using multiple disks for parallel I/O • For file servers—additional memory and disks, or a Redundant Array of Inexpensive Disks (RAID) system to improve I/O throughput

Supported processor platforms

x86 (32-bit) x86_64 (64-bit) Itanium* (Itanium II or newer) IBM* POWER* IBM z/Architecture* (64-bit)

After reading the article, a user would have gained knowledge and understanding of the Servier’s requirements.