Specifications
Table Of Contents
- Quartus II Installation & Licensing for Linux Workstations
- Contents
- Documentation Conventions
- Installing the Quartus II Software
- Introduction
- Quartus II Software System Requirements
- Uninstalling Previously Installed Versions of Altera Software
- Altera.com Download Center
- Installing Downloaded Altera Software
- Altera Complete Design Suite
- The Altera Complete Design Suite Installation Script
- Installing the Altera Complete Design Suite
- Using the 64-bit Version of the Quartus II Software
- Licensing the Quartus II Software
- More Configuration Information
- Documentation and Technical Support
- Quartus II Software File Organization
- Mounting and Unmounting DVD-ROMs
- Index

CHAPTER 2: LICENSING THE QUARTUS II SOFTWARE
CONFIGURING EACH USER ENVIRONMENT
ALTERA CORPORATION INSTALLATION & LICENSING FOR LINUX WORKSTATIONS ■ 22
2. If the parameters do not have the recommended values, change the
values to the recommended values by adding one or more of the
following lines to the limits.conf file:
3. Type the following command at the command prompt:
echo 356 40000 32 32000 > /proc/sys/kernel/sem r
Configuring Each User Environment
Ensure that you perform the following steps for each Quartus II software
user before starting the Quartus II software for the first time:
1. Update each user’s PATH environment variable in the .cshrc file, which
is located in the home directory, to include the bin directory in the
Quartus II system directory, which is usually the /opt/altera<version
number>/bin directory. To update the PATH environment variable, type
the following command at a command prompt:
Table 3. Configuration Parameters
Parameter Recommended Value
hard nofile 32768
soft nofile 32768
!
Asterisks (*) in limits.conf File
The asterisks (*) in the previous lines are part of the code and must be
included in the limits.conf file.
!
Adding Kernel Configuration Command to Linux Workstation
Startup Scripts
The previous command takes effect immediately; however, Altera
recommends that your system administrator also add the commands to the
workstation’s startup scripts, because the command is reset whenever you
restart the workstation.