GRUB stands for GRand Unified Boot loader.
GRUB Boot loader is an important part for multi booting PC that eans when more than one option is available for booting a PC. Now-a-days, most of the computer users keep at least two operating system for their PC. It helps a lot to them. When any one try to black mail the user, user don't be worry about that as there is an another option for him to complete his task at that moment.
i.e I use Ubuntu for using Internet and for developing windows based software I use Xp. If both the option can not be displayed at the start up of the pc, we have to need two PC for two different requirements.
GRUB Boot-loader is one of this solution provider. we can use the GRUB boot-loader according to our needs. But we have to be more cautions when we will try to work with GRUB Boot loader.GRUB is an excellent and highly flexible boot loader. It's designed to boot a wide range of operating systems from a wide range of file systems.GRUB is now pretty much the standard used in the very many variations of Linux available today.
Before doing any work on GRUB, we need to back up a copy of that file which will help us for any problem in future. Recently, I have tried to change some option in my GRUB file. And then I accessed many website for getting some help. And some website helps me a lot. These are as
Website 1
Website 2
Website 3
Remember, before doing any work with GRUB, you must know the version of your GRUB and then follow according to that. And then take a backup of that GRUB file before any modification. Lets try and enjoy..
Tuesday, September 14, 2010
Monday, September 13, 2010
Tips on Database Design
1.Develop A Prototype
Significant time can be saved by creating the structure in a simple desktop database (such as Microsoft Access) before finalising the design in one of the enterprise databases. The developer will be able to recognise simple faults and makes changes more rapidly than would be possible at a later date.
2.Split database structure into multiple tables
Unlike paper-based structures, databases do not require the storage of all fields in a single table. For large databases it is useful to split essential information into multiple tables. Before creating a database, ensure that the data has been normalised to avoid duplication.
3.Use understandable field names
The developer should avoid field names that are not instantly recognisable. Acronyms or internal references will confuse users and future developers who are not completely familiar with the database.
4.Avoid illegal file names
It is considered good practice to avoid exotic characters in file or field names. Exotic characters would include ampersands, percentages, asterisks, brackets and quotation marks. You should also avoid spaces in field and table names.
5.Ensure Consistency
Remain consistent with data entry. If including title (Mr, Miss, etc.) include it for all records. Similarly, if you have established that house number and address belong in different fields, always split them.
6.Avoid blank fields
Blank fields can cause problems when interpreting the data at a later date. Does it mean that you have no information, or you have forgotten to enter the information? If information is unavailable it is better to provide a standard response (e.g. unknown).
7.Use standard descriptors for date and time
Date and time can be easily confused when exporting database fields in a text file. A date that reads ‘12/04/2003’ can have two meanings, referring to April 12th or December 4th, 2003. To avoid ambiguity always enter and store dates with a four-digit century and times of day using the 24 hour clock. The ISO format (yyyy-mm-dd) is useful for absolute clarity, particularly when mixing databases at a later date.
8.Use currency fields if appropriate
Currency data types are designed for modern decimal currencies and can cause problems when handling old style currency systems, such as Britain’s currency system prior to 1971 that divided currency into pounds, shillings and pence.
9.Avoid proprietary extensions
Care should be taken when using proprietary extensions, as their use will tie your database to a particular software package. Examples of proprietary extensions include the user interface and application-specific commands.
10.Avoid the use of field dividers
Commas, quotation marks and semi-colons are all used as methods of separating fields when databases are exported to a plain text file and subsequently re-imported into another database. When entering data into a database you should choose an alternative character that represents these characters.
Collected From:Website
Significant time can be saved by creating the structure in a simple desktop database (such as Microsoft Access) before finalising the design in one of the enterprise databases. The developer will be able to recognise simple faults and makes changes more rapidly than would be possible at a later date.
2.Split database structure into multiple tables
Unlike paper-based structures, databases do not require the storage of all fields in a single table. For large databases it is useful to split essential information into multiple tables. Before creating a database, ensure that the data has been normalised to avoid duplication.
3.Use understandable field names
The developer should avoid field names that are not instantly recognisable. Acronyms or internal references will confuse users and future developers who are not completely familiar with the database.
4.Avoid illegal file names
It is considered good practice to avoid exotic characters in file or field names. Exotic characters would include ampersands, percentages, asterisks, brackets and quotation marks. You should also avoid spaces in field and table names.
5.Ensure Consistency
Remain consistent with data entry. If including title (Mr, Miss, etc.) include it for all records. Similarly, if you have established that house number and address belong in different fields, always split them.
6.Avoid blank fields
Blank fields can cause problems when interpreting the data at a later date. Does it mean that you have no information, or you have forgotten to enter the information? If information is unavailable it is better to provide a standard response (e.g. unknown).
7.Use standard descriptors for date and time
Date and time can be easily confused when exporting database fields in a text file. A date that reads ‘12/04/2003’ can have two meanings, referring to April 12th or December 4th, 2003. To avoid ambiguity always enter and store dates with a four-digit century and times of day using the 24 hour clock. The ISO format (yyyy-mm-dd) is useful for absolute clarity, particularly when mixing databases at a later date.
8.Use currency fields if appropriate
Currency data types are designed for modern decimal currencies and can cause problems when handling old style currency systems, such as Britain’s currency system prior to 1971 that divided currency into pounds, shillings and pence.
9.Avoid proprietary extensions
Care should be taken when using proprietary extensions, as their use will tie your database to a particular software package. Examples of proprietary extensions include the user interface and application-specific commands.
10.Avoid the use of field dividers
Commas, quotation marks and semi-colons are all used as methods of separating fields when databases are exported to a plain text file and subsequently re-imported into another database. When entering data into a database you should choose an alternative character that represents these characters.
Collected From:Website
Subscribe to:
Posts (Atom)