Puppy Linux Manual in English. Manual- English. How to Use the Manual and Download Puppy . Hanbala in Arabic.

English or Bahasa. Note that the installation method is very similar among Puppy Linux distros. There is a book by Grant Wilson about Puppy 4.

PDF. click here. Pay attention to the NOTE below about version numbering. You should replace this with the latest. Use the number with filenames, like pup.

Starting April 2. Puppy Linux, and there is a file /etc/DISTRO. This manual. summarizes the most important information for Puppy beginners and. Puppy. Sub- menus are separated by.

How to get Puppy. You can get Puppy Linux from. The filesize is about 1.

MB. To make sure that you downloaded a genuine original file, you can. ISO file with the associated file.

HOWTO Introduction. OpenVPN is a full-featured SSL VPN which implements OSI layer 2 or 3 secure network extension using the industry standard SSL/TLS protocol. 2 thoughts on “ 11gR2 rac installation on 64 bit Linux step by step ” Nafey March 11, 2010 at 12:03 pm. Very nice post. I was able to complete the 11gR2 Rac. Guide: Installing Oracle Enterprise Manager 10g Grid Control Rel 5 on Oracle Database 11g and Linux by Mike Revitt. Install Oracle Database 11g R2 on Linux - (RHEL 6) by Jeff Hunter, Sr. Database Administrator Contents. Introduction; Example Configuration.

3 Configuring Storage for Oracle Grid Infrastructure for a Cluster and Oracle RAC. This chapter describes the storage configuration tasks that you must complete. 24 x 7 for a month. And much more. Learn more.

You should get an OK. If not you need to download the iso again. To open. a DOS- Box click on . This opens an input window, into which you enter. Now you get a DOS- Box. Change into the directory in which you stored the two files. Enter these commands: c: cd pup.

Now you should see the Puppy- files (make sure. Next, enter the command. You should get an . To burn an ISO file on CD, consult the. CD- burning software. Beginners sometimes copy the ISO. CD, which doesn’t work.

Usually the. CD- burning software has a special menu option for burning an ISO file. CD. You can verify whether you burned the CD correctly by looking at. CD with the file manager (e. Windows Explorer). If you see files.

If you see the file. You can run Puppy directly from the CD, without affecting. Alternatively you can install Puppy on a. USB stick. How to run Puppy the very first time.

First you must set up the boot sequence in the BIOS. If you do not know. BIOS- setup, consult the computers manual. Usually. you press one of the following keys immediately after switching on the. PC: ESC, one of the function keys F1 to F1. At the. BIOS- setup you change the boot sequence so that the CD- ROM drive is. Close the BIOS- setup and store the.

Immediately insert the Puppy CD into. CD- ROM drive. If you are too slow your old operating system starts. During the starting procedure you are. For other questions, navigate with the cursor keys. Then strike the return- key.

Thereafter a. further window (Puppy video Wizard) appears, . Press the return- key. Wait some seconds till the next.

Puppy video Wizard) appears. There you navigate with the cursor. LCD panel = flat screen, CRT = standard monitor). Then strike the return- key. After some seconds the. Puppy desktop appears.

A few seconds. later, the Puppy desktop will be displayed using a resolution of 6. If you wish to use an even higher resolution choose e. Click on the OK- button. Your old operating system is.

Puppy Linux. Now you can. CD out of the CD drive, unless you do not have enough ram, in. Puppy will not allow the CD to be ejected. If saving to pup. If you do not. enter anything, Puppy is loaded after some seconds into RAM.

When. starting, Puppy automatically looks for a previously stored. If this file doesn't exist yet, you will be asked again the same boot- up questions.

This boot option is very useful and. The other boot options are normally. Back to Top. Saving and Installing to Hard Disk. Back to Top. How to save the settings and your personal files. So that Puppy can store all settings and your personal data, a file. I recommend a size of 5.

MB for this. file. This is big enough for further programs and can be backed- up on.

CD- ROM (note: if you want to backup the file on a USB stick, it must. GB). Puppy can store the pup. Windows XP- users normally have a NTFS- filesystem only. There. are two options for you to store the pup.

How to install Puppy. If you prefer not to keep booting Puppy from CD- ROM, you can install.

Puppy to a hard disk drive. This requires some preparation. Hard drives, partitions and filesystems. A hard drive can be divided in one or more partitions. If you create. several partitions on a harddrive, each partition appears like a hard. In other words: although you have only. PC, you will see several (virtual) hard- drives.

Windows or Linux. Windows designates the harddrives (as well as. CD/DVD drive). In Windows they will be. Usually A designates the floppy disk drive, C.

D the CD- ROM drive, E the harddrive. F the harddrive (third partition) and so on.

Each. partition has its own file system, Windows normally uses NTFS (Windows. XP) or FAT3. 2 (Win. Win. 95). The partitions are sequentially numbered, starting with one. Linux can work with different file. Reiser. FS. These file systems are not.

Windows. In addition Linux can work with Windows. Back to Top. Preparing the Hard Disk. Back to Top. Defragment your hard disk. Before creating new partitions on your hard drive, you should. Here is how to do it: Start up Windows. First, backup your files to CD- ROM, DVD, or an external hard drive. If your data is encrypted, it is advisable to decrypt it.

This protects you from data loss because. Next, start the Disk Defragmenter program under Windows. The program. is located at . Select hard drive c: \ and click the . Depending on the size of the.

If you have very large amounts of data, you can. In this case, please make sure beforehand. Click the . I recommend creating three or four. Windows partition. The following example. Windows partition (drive letter C). Your. hard disk would then look like this: First partition: NTFS or FAT3.

Windows)Second partition: ext. Puppy will be installied to)Third partition: Linux swap (for page files)Fourth partition: FAT3. Windows and Linux)Optionally, a fifth partition: ext. Linux)Windows will continue to reside on your first partition with all its. The second partition (recommended size about 1- 2 GB). Linux file system (ext. Cd Lex Skate Rock Download Blogspot. This is the partition Puppy.

The third partition (exactly as large as your. Linux swap partition that Linux can .. The fourth partition has a FAT3. Windows and Linux. This partition. (recommended size about 5 GB) is used for files that you want to access. Windows and Linux. If you want to manage large amounts of.

Puppy (e. g. This file system. Windows and is meant for Linux only.

To create the partitions, proceed as follows: Start Puppy Linux from CD with the . To do this, select the Windows partition /dev/hda. Click the . My test.

I am using half of that for. You probably have a much larger hard drive so your.

Then press the . You now have an . This. is where Puppy Linux will be installed to. I recommend a size of 1 to 2. MB). Select ext. 2 from the . This. partition is to hold Linux's swap files as a Linux swap partition. You. should make it as large as your computer's memory (RAM). With my test. computer, this amounts to 1.

MB). Select linux- swap from. MB). Since my test computer. I am using 3. 96 megabytes (MB). Select FAT3. 2 from the . In this case, you may have to create so- called logical. Please consult additional sources if you are unsure about.

To actually write the changes to disk, select . If. you have less than 2.

MB RAM you should choose Full Installation. Frugal Installation using Puppy Universal Installer. A Frugal Installation copies the image from the Puppy CD to the hard. At bootup, Puppy is loaded into your computer's memory (RAM).

Puppy from CD, however, loading it from a. This way, Frugal Installation combines the. CD- ROM (protection from malware) and a hard. Moreover, upgrading to a new Puppy version is.

Choose which. medium Puppy should be installed to. In this example, I chose the. In our example, click on the . Just click on the . In the next two dialogue boxes, click . The boot loader is the first.

It enables you to. If Windows was the. Start the installation of the boot loader GRUB with .

These can only be written to a Linux file system partition. If you do not have a. Linux file system partition yet, you need to create one. Select the Master Boot Record . What remains to be done is to. GRUB boot loader so that Puppy Linux can be booted.

This. is how to do it. Open the file . You will find this file in the /boot/grub. GRUB files to (/dev/hda.

For Linux newbies, I include detailed instructions on. More advanced users can skip ahead to.

ZFS - Wikipedia. ZFSDeveloper(s)Oracle Corporation. Full name. ZFSIntroduced. November 2. 00. 5 with Open. Solaris. Structures. Directory contents. Extensible hash table. Limits. Max. The features of ZFS include protection against data corruption, support for high storage capacities, efficient data compression, integration of the concepts of filesystem and volume management, snapshots and copy- on- write clones, continuous integrity checking and automatic repair, RAID- Z and native NFSv.

ACLs. The ZFS name is registered as a trademark of Oracle Corporation. ZFS became a standard feature of Solaris 1. June 2. 00. 6. In 2. Oracle stopped the releasing of source code for new Open. Solaris and ZFS development, effectively forking their closed- source development from the open- source branch. In response, Open. ZFS was created as a new open- source development umbrella project.

The user sees this as a single volume, containing an NTFS- formatted drive of their data, and NTFS is not necessarily aware of the manipulations that may be required (such as rebuilding the RAID array if a disk fails). The management of the individual devices and their presentation as a single device, is distinct from the management of the files held on that apparent device. ZFS is unusual, because unlike most other storage systems, it unifies both of these roles and acts as both the volume manager and the file system.

Therefore, it has complete knowledge of both the physical disks and volumes (including their condition, status, their logical arrangement into volumes, and also of all the files stored on them). ZFS is designed to ensure (subject to suitable hardware) that data stored on disks cannot be lost due to physical error or misprocessing by the hardware or operating system, or bit rot events and data corruption which may happen over time, and its complete control of the storage system is used to ensure that every step, whether related to file management or disk management, is verified, confirmed, corrected if needed, and optimized, in a way that storage controller cards, and separate volume and file managers cannot achieve.

ZFS also includes a mechanism for snapshots and replication, including snapshot cloning; the former is described by the Free. BSD documentation as one of its . Snapshots can be rolled back . Checksums are stored with a block's parent block, rather than with the block itself. This contrasts with many file systems where checksums (if held) are stored with the data so that if the data is lost or corrupt, the checksum is also likely to be lost or incorrect.

Can store a user- specified number of copies of data or metadata, or selected types of data, to improve the ability to recover from data corruption of important files and structures. Automatic rollback of recent changes to the file system and data, in some circumstances, in the event of an error or inconsistency.

Automated and (usually) silent self- healing of data inconsistencies and write failure when detected, for all errors where the data is capable of reconstruction. Data can be reconstructed using all of the following: error detection and correction checksums stored in each block's parent block; multiple copies of data (including checksums) held on the disk; write intentions logged on the SLOG (ZIL) for writes that should have occurred but did not occur (after a power failure); parity data from RAID/RAIDZ disks and volumes; copies of data from mirrored disks and volumes. Native handling of standard RAID levels and additional ZFS RAID layouts (.

The RAIDZ levels stripe data across only the disks required, for efficiency (many RAID systems stripe indiscriminately across all devices), and checksumming allows rebuilding of inconsistent or corrupted data to be minimised to those blocks with defects; Native handling of tiered storage and caching devices, which is usually a volume related task. Because it also understands the file system, it can use file- related knowledge to inform, integrate and optimize its tiered storage handling which a separate device cannot; Native handling of snapshots and backup/replication which can be made efficient by integrating the volume and file handling. ZFS can routinely take snapshots several times an hour of the data system, efficiently and quickly. For example, synchronous writes which are capable of slowing down the storage system can be converted to asynchronous writes by being written to a fast separate caching device, known as the SLOG (sometimes called the ZIL - ZFS Intent Log). Highly tunable - many internal parameters can be configured for optimal functionality. Can be used for high availability clusters and computing, although not fully designed for this use.

Inappropriately specified systems. It expects or is designed with the assumption of a specific kind of hardware environment. If the system is not suitable for ZFS, then ZFS may underperform significantly. Common system design failures: Inadequate RAM — ZFS may use a large amount of memory in many scenarios; Inadequate disk free space — ZFS uses copy on write for data storage; its performance may suffer if the disk pool gets too close to full; No efficient dedicated SLOG device, when synchronous writing is prominent — this is notably the case for NFS and ESXi; even SSD based systems may need a separate SLOG device for expected performance. The SLOG device is only used for writing apart from when recovering from a system error. It can often be small (for example, in Free. NAS, the SLOG device only needs to store the largest amount of data likely to be written in about 1.

SLOG is therefore unusual in that its main criteria are pure write functionality, low latency, and loss protection - usually little else matters. Lack of suitable caches, or misdesigned caches — for example, ZFS can cache read data in RAM (.

While routine for other filing systems, ZFS handles RAID natively, and is designed to work with a raw and unmodified low level view of storage devices, so it can fully use its functionality. A separate RAID card may leave ZFS less efficient and reliable. For example ZFS checksums all data, but most RAID cards will not do this as effectively, or for cached data.

Separate cards can also mislead ZFS about the state of data, for example after a crash, or by mis- signalling exactly when data has safely been written, and in some cases this can lead to issues and data loss. Separate cards can also slow down the system, sometimes greatly, by adding latency to every data read/write operation, or by undertaking full rebuilds of damaged arrays where ZFS would have only needed to do minor repairs of a few seconds.

ZFS terminology and storage structure. The vdev is an essential part of ZFS resilience, since it provides redundancy. Therefore, it is easiest to describe ZFS physical storage by first looking at vdevs.

Each vdev can be one of: a single device, ormultiple devices in a mirrored configuration, ormultiple devices in a ZFS RAID (. Devices might not be in a vdev if they are unused spare disks, offline disks, or cache devices. Each vdev that the user defines, is completely independent from every other vdev, so different types of vdev can be mixed arbitrarily in a single ZFS system. If data redundancy is required (so that data is protected against physical device failure), then this is ensured by the user when they organize devices into vdevs, either by using a mirrored vdev or a Raid. Z vdev. Data on a single device vdev may be lost if the device develops a fault. Data on a mirrored or Raid. Z vdev will only be lost if enough disks fail at the same time (or before the system has resilvered any replacements due to recent disk failures).

A ZFS vdev will continue to function in service if it is capable of providing at least one copy of the data stored on it, although it may become slower due to error fixing and resilvering, as part of its self- repair and data integrity processes.