CSPICE_LSPCN computes L_s, the planetocentric longitude of the sun,
as seen from a specified body.
Given:
body is the name of the central body, typically a planet.
[1,c1] = size(body); char = class(body)
or
[1,1] = size(body); cell = class(body)
et is the epoch at which the longitude of the sun (L_s) is
to be computed. 'et' is expressed as seconds past J2000
TDB (Barycentric Dynamical Time).
[1,n] = size(et); double = class(et)
abcorr indicates the aberration corrections to be applied
when computing the longitude of the sun.
[1,c2] = size(abcorr); char = class(abcorr)
or
[1,1] = size(abcorr); cell = class(abcorr)
'abcorr' may be any of the following.
'NONE' Apply no correction.
'LT' Correct the position of the sun,
relative to the central body, for
planetary (light time) aberration.
'LT+S' Correct the position of the sun,
relative to the central body, for
planetary and stellar aberrations.
the call:
lspcn = cspice_lspcn( body, et, abcorr )
returns:
lspcn the planetocentric longitude of the sun, often called
"L_s," for the specified body at the specified time.
[1,n] = size(et); double = class(et)
The longitude is defined in a right-handed frame whose
basis vectors are defined as follows:
- The positive Z direction is given by the instantaneous
angular velocity vector of the orbit of the body about
the sun.
- The positive X direction is that of the cross product
of the instantaneous north spin axis of the body with
the positive Z direction.
- The positive Y direction is Z x X.
Units are radians; the range is 0 to 2*pi. Longitudes are
positive to the east.
'lspcn' returns with the same vectorization measure (N) as 'et'.
Any numerical results shown for this example may differ between
platforms as the results depend on the SPICE kernels used as input
and the machine specific arithmetic implementation.
Use the meta-kernel shown below to load the required SPICE
kernels.
KPL/MK
File name: standard.tm
This meta-kernel is intended to support operation of SPICE
example programs. The kernels shown here should not be
assumed to contain adequate or correct versions of data
required by SPICE-based user applications.
In order for an application to use this meta-kernel, the
kernels referenced here must be present in the user's
current working directory.
The names and contents of the kernels referenced
by this meta-kernel are as follows:
File name Contents
--------- --------
de421.bsp Planetary ephemeris
pck00010.tpc Planet orientation and
radii
naif0011.tls Leapseconds
\begindata
KERNELS_TO_LOAD = ( 'de421.bsp',
'pck00010.tpc',
'naif0011.tls' )
\begintext
Example(1):
Scalar
cspice_furnsh( 'standard.tm' )
et = cspice_str2et('21 march 2006')
lspcn = cspice_lspcn( 'earth', et, 'none' ) * cspice_dpr
MATLAB outputs:
lspcn =
0.2365
Example(2):
Vector
et = cspice_str2et('21 march 2005') + [0:1000000.:10000000.];
lspcn = cspice_lspcn( 'earth', et, 'none' ) * cspice_dpr
MATLAB outputs:
lspcn =
0.4815 11.9353 23.3193 34.6294 45.8611 57.0476 68.1626
79.2509 90.3058 101.3366 112.3833
None.
For important details concerning this module's function, please refer to
the CSPICE routine lspcn_c.c.
MICE.REQ
ABCORR.REQ
-Mice Version 1.0.0, 10-NOV-2015, EDW (JPL)
Script rewritten to call CSPICE interface.
-Mice Version 0.9.0, 23-OCT-2015, EDW (JPL)
Pure Matlab script.
planetocentric longitude of sun
compute L_s
compute Ls
compute L_sub_s
|


The saxon:script
element is a top-level element.
It is used to define an implementation
for an extension function that will be used by Saxon. With
other processors, a different implementation of the same function can be selected,
using mechanisms defined by that processor (for example, xalan:script
).
The attributes for saxon:script
are the same as the attributes
of the xsl:script
element defined in the (now withdrawn) XSLT 1.1
working draft.
The language
attribute is mandatory, and must take the value "java".
The values "javascript", "ecmascript", or a QName are also permitted, but in this
case Saxon ignores the saxon:script
element.
The implements-prefix
attribute is mandatory, its value must be a namespace
prefix that maps to the same namespace URI as the prefix used in the extension function
call.
The src
attribute is mandatory for language="java", its value must take the
form "java:fully.qualified.class.Name", for example "java:java.util.Date". It defines
the class containing the implementation of extension functions that use this prefix.
The archive
attribute is optional, its value is a space-separated list of URLs
of folders or JAR files that will be searched to find the named class. If the attribute
is omitted, the class is sought on the classpath.


| dbGetConnectArgs {DBI} | R Documentation |
Returns the arguments stored in a DBIConnector object for inspection,
optionally evaluating them.
This function is called by dbConnect()
and usually does not need to be called directly.
dbGetConnectArgs(drv, eval = TRUE, ...)
drv |
A object inheriting from DBIConnector. |
eval |
Set to |
... |
Other arguments passed on to methods. Not otherwise used. |
Other DBIConnector generics:
DBIConnector-class
,
dbConnect()
,
dbDataType()
,
dbIsReadOnly()
cnr <- new("DBIConnector", .drv = RSQLite::SQLite(), .conn_args = list(dbname = ":memory:", password = function() "supersecret") ) dbGetConnectArgs(cnr) dbGetConnectArgs(cnr, eval = FALSE)


In this article we will be learning the basics of JavaScriptMVC and
the Model-View-Controller pattern by installing
and walking through a simple Todo list manager. The separation of the
application's core logic from its user interface behavior is the hallmark of MVC. By
working through this exercise you will understand how JavaScriptMVC's particular flavor of this pattern
enables you to create more flexible and maintainable browser-based applications.
Let's get started!
Setup
First, clone the application from our repository at GitHub,
and initialize all the necessary submodules. The following commands will get you up and running:
The can folder is where the CanJS library lives. JavaScriptMVC consists of powerful abstractions like Construct, Model, Control, and view. The jquerypp folder contains the jQuery++, which provides numerous helpful jQuery plugins like resize, destroyed, fastfix, json, and hover -- all designed to enhance your life as a JavaScript developer.
The steal folder houses the Steal dependency management system, which is what makes it possible to keep your project organized during development, and compact and fast in production. Steal has two main responsibilities: As a JavaScript library, it facilitates on-demand loading of any resources (scripts, stylesheets, templates, or even user-defined content) your application requires. As a command line utility, it takes care of bundling, compressing, and optimizing your application for deployment.
The FuncUnit testing framework lives in the funcunit folder -- think jQuery's excellent Qunit framework plus Selenium and headless (Env.js) support. Basically, qUnit on steroids.
Lastly, our application files will live in the todo folder.
MVC in JavaScript
MVC is a well-established architectural pattern in software engineering. Without going into too much detail, it states that there should be a clear separation of concerns between the part of the system that represents the application's core logic and state (Model), the part that renders the user interface (View), and the part that coordinates between the two (Control). Since our application consists of only one model, one control, and a handful of templates, we're going to keep all our code in the todo.js, todo.html, and todo.ejs files. (Ordinarily in a JavaScriptMVC application, we'd keep a single component in each file for ease of navigation, but you'll forgive us this time for keeping it simple.)
The diagram below shows how we've broken our application out into model, view, and control layers:
Dependencies
If you look at todo.js the first thing you'll notice is that all the code is wrapped in a call to the steal function:
In fact, this is true of every JavaScript file in a JavaScriptMVC application: we use steal to state our dependencies up-front, which tells the framework what libraries, plugins, stylesheets, etc. we need to load before we can begin. Typically, the final argument to steal will be a callback function, which will be executed when all the other dependencies (and their dependencies, and so on...) have been loaded and executed as well. No more worrying whether you forgot any


---
layout: page
title: "My Talks"
description: "Videos and slides from my conference talks"
header-img: "img/talks-bg.jpg"
---
Public speaking at conferences/events:
-
"High Tech-Low Test or Problems of Modern Testing" - Ministry of Testing Abu Dhabi, Virtual, 2022.
Video (EN).
-
"Practical Contract Testing with Spring Cloud Contract" - Ministry of Testing Abu Dhabi, Virtual, 2020.
Video (EN).
Slides.
-
"Ups and downs of contract testing in real life" - Selenium Camp, Kyiv, UA, 2020.
Video (RU).
Slides.
-
"Practical Contract Testing with Spring Cloud Contract" - TestCon Europe, Vilnius, LT, 2019.
Video (EN).
Slides.
-
"Turning automation education upside-down" - QA Fest, Kyiv, UA, 2019.
Video (RU).
Slides.
-
"Testing challenges at microservices world" - Test Fest, Wroclaw, PL, 2019.
Video (EN).
Slides.
-
"Hidden complexities in microservices testing" - ITEM conference, Dnipro, UA, 2018.
Slides.
-
"Automating microservices: what, where and when" - IT Weekend, Dnipro, UA, 2018.
Slides.
-
"Integration testing for microservices with Spring Boot" - Selenium Camp, Kyiv, UA, 2018.
Video (RU).
Slides.
-
"Testing for Java Developers" - IT Weekend, Dnipro, UA, 2017.
-
"The One where Cucumber meets Scala" - IT Weekend, Lviv, UA, 2017.


Simple Get - Options
Download Manager
Path:
Parameters:
e.g. /usr/bin/wget "http://foo.com/foo.txt" -P "/home/user/downloads"
Parameters should be:
[SG_URL] -P [SG_DESTINATION]
Destination:
Restore to Defaults
Save
SimpleGet 2.3 - Copyright © 2011 Roque Pinel
Licensed under the Apache License, Version 2.0


We will install all the server side development tools.
They include:
These steps will be performed on the vagrant machine
$ vagrant up
$ vagrant ssh
$ sudo apt-get install default-jdk mysql-server
$ javac -version # This tests the java installation
javac 1.7.0_65
$ mysql --version # This tests the mysql intallation
mysql Ver 14.14 Distrib 5.5.38, for debian-linux-gnu (i686) using readline 6.3
IntelliJ IDEA (Community Edition) is one of the best (imho) open source Java IDE.
Go to http://www.jetbrains.com/idea/download/ and download the last version for your operating system.
Mac OS X Installation
Windows Installation
Windows Installation
Windows Installation
Windows Installation
Windows Installation
Windows Installation
Linux Installation
$ wget http://download-cf.jetbrains.com/idea/ideaIC-13.1.4b.tar.gz
$ tar xzvf ideaIC-13.1.4b.tar.gz


Download Pext
GNU/Linux
AppImage
Stable - Development
Arch Linux
Stable - Development
PyPI
Stable - Development
Alternatively, you may Install from source.
Windows
Currently, we only support installing from source.
AppImage
Stable - Development
Arch Linux
Stable - Development
PyPI
Stable - Development
Alternatively, you may Install from source.
Currently, we only support installing from source.


Puneri Paltan
Owned and managed by Insurekot Sports Pvt. Ltd.,
Puneri Paltan is one of two Pro kabaddi league
franchiese from Maharashtra. The team represents
the city of pune, comining the magnificence of
Maharashtra's cultural capital with the true flavours
of this indigenous sports. Insurekot Sports Pvt. Ltd.
is passionate about Kabaddi and committed to
promoting the sports and works with an aim to
create awerness around kabaddi's rich heritage in
the country. The team masterminded by Ashok
Shinde is lead by Wazir Singh.
Recreating the glory of the game's rich history in
India, Puneri Paltan unleshes the energy and
fortitude of kabaddi in it's morden day version
|


Status:
Version:1.0.0-B
A silent, tiny and effective CSS framework + HTML5 ready choice to CSS.
If you've installed a package before, you can install it again without any internet connection.
It downloads so it never needs to downloaded again.
Modular
Modern art mode
Free and Open Source
Morphological design
Supports:All recent versions of Chrome, Firefox, Edge, Safari, Opera and Internet Explorer 11.


| Package | Description |
|---|---|
| org.cooperari.core |
Cooperari engine.
|
| org.cooperari.core.aspectj |
Package for interface with the AspectJ compiler and LTW agent.
|
| org.cooperari.errors |
Cooperari error classes, related to aspects like
runtime execution events (e.g., deadlock or race detection),
invalid configuration options, internal errors, etc.
|
| org.cooperari.feature |
Root package for feature implementations.
|
| org.cooperari.feature.atomic |
Yields points for methods in
java.util.concurrent.AtomicXXX
classes. |
| org.cooperari.feature.data |
Support for data access yield points and race detection.
|
| org.cooperari.feature.hotspots |
Hotspot reachability feature.
|
| org.cooperari.feature.monitor |
Yield point support for Java monitor operations and related
deadlock detection.
|
| org.cooperari.feature.thread |
Yield point support
Thread life-cycle methods. |
| org.cooperari.feature.threadrunner |
Support for the "fork-and-join" thread runner.
|
| org.cooperari.feature.unsafe |
Support for yield points in calls to methods to
sun.misc.Unsafe . |
| Class and Description |
|---|
| CBlockingOperationEvent
An enumeration of common operation outcomes used by several primitives.
|
| CConfiguration
Configuration object defined by annotations.
|
| CCoverageLog
Coverage log.
|
| CEngine
Cooperative execution engine.
|
| COperation
Base class for cooperative operations.
|
| CRuntime
Cooperari runtime.
|
| CThread
Cooperative thread.
|
| CThreadState
Cooperative thread state.
|
| CTrace.EventType
Event types.
|
| CUncaughtExceptionHandler
Handler for uncaught thread exceptions.
|
| CWorkspace
Keeps a record of the Cooperari workspace directory and
global configurations, and provides associated utility methods.
|
| CWorkspace.Option
Workspace options.
|
| Class and Description |
|---|
| CCoverageLog
Coverage log.
|
| Class and Description |
|---|
| CThread
Cooperative thread.
|
| Class and Description |
|---|
| CRuntime
Cooperari runtime.
|
| CustomYieldPoint
Custom yield point definition.
|
| Class and Description |
|---|
| CustomYieldPoint
Custom yield point definition.
|
| Class and Description |
|---|
| COperation
Base class for cooperative operations.
|
| CRuntime
Cooperari runtime.
|
| CThread
Cooperative thread.
|
| Class and Description |
|---|
| COperation
Base class for cooperative operations.
|
| CRuntime
Cooperari runtime.
|
| Class and Description |
|---|
| COperation
Base class for cooperative operations.
|
| CRuntime
Cooperari runtime.
|
| CThread
Cooperative thread.
|
| CThreadState
Cooperative thread state.
|
| Class and Description |
|---|
| COperation
Base class for cooperative operations.
|
| CThread
Cooperative thread.
|
| CThreadState
Cooperative thread state.
|
| Class and Description |
|---|
| COperation
Base class for cooperative operations.
|
| CThread
Cooperative thread.
|
| CThreadState
Cooperative thread state.
|
| Class and Description |
|---|
| CustomYieldPoint
Custom yield point definition.
|
Copyright © 2021 Cooperari. All rights reserved.


This directory used to contain the editor's extensions for PRADO.
They have been moved elsewhere; we suggest you to download the most up-to-date versions from the project's repository
Currently we provide extensions for the following editors:


Pyjamas is a simple library that provides basic version management for
persisting reflections JavaScript code as JSON.
- Version:
- 0.0.3
- Source:
- To Do:
-
- Improve this description!
Classes
Methods
(static) construct(constructor, target) → {object}
Reconstructs a persisted object as an instance of the given constructor.
If the given target is not at the current version of the constructor then
upgraders will be successively applied until the highest version is
achieved.
Parameters:
| Name | Type | Description |
|---|---|---|
constructor |
function | Object constructor |
target |
object | Raw instance to use to populate a new instance of the constructor |
- Source:
Returns:
A new instance of the constructor
- Type
- object
(static) manifest(target) → {object}
Manifests an instance of a class as a bare-bones object that confirms
to JavaScript Object Notation. The resulting object will have no
undefined fields, functions or a constructor. There are no references
to the original constructor stored. It is up to the user to keep the
association of the return the type class definition of the manifested
object.
Parameters:
| Name | Type | Description |
|---|---|---|
target |
object | Target object to manifest |
- Source:
Returns:
Versioned persistable representation of target
- Type
- object
(static) register(constructor, version, defines) → {Pyjamas.Pyjamas}
Registers a class into the PyjamasDB and returns a new Pyjamas instance
Parameters:
| Name | Type | Description |
|---|---|---|
constructor |
function | Object constructor to register |
version |
string | Current version of object constructor |
defines |
object | Definitions of instance variables to persist when given an instance of the constructor's class |
- Source:
Returns:
A new Pyjamas instance
- Type
- Pyjamas.Pyjamas
Example
Pyjamas.register(MyClass, '0.1.2', {
foo : Number,
bar : String,
baz : MyOtherClass
});
(static) toJSON(target) → {string}
Returns a JSON string representation of a target instance
Parameters:
| Name | Type | Description |
|---|---|---|
target |
object | Target object to serialized |
- Source:
- See:
Returns:
JSON string representation of target
- Type
- string
(static) unregister(constructor) → {Pyjamas.Pyjamas|null}
Removes a class from the PyjamasDB if it exists, otherwise return null
Parameters:
| Name | Type | Description |
|---|---|---|
constructor |
function | Object constructor to unregister |
- Source:
Returns:
Removed Pyjamas instance or null if the
constructor was not registered
- Type
- Pyjamas.Pyjamas | null


A very important concept introduced by the LAR package is the definition of the model of a cell complex, as a pair made by a list of vertices, given as lists of coordinates, and a topological relation.
Definition (LAR model). A LAR model is a pair, e.g. a Python tuple (V, FV), where:
Examples Some very simple examples of 0D, 1D, and 2D models follows. They are displayed in Figure 1.
V = [[0.,0.],[1.,0.],[0.,1.],[1.,1.],[0.5,0.5]]
VV = [[0],[1],[2],[3],[4]]
EV = [[0,1],[0,2],[0,4],[1,3],[1,4],[2,3],[2,4],[3,4]]
FV = [[0,1,4],[1,3,4],[2,3,4],[0,2,4]]
model0d, model1d, model2d = (V,VV), (V,EV), (V,FV)
◇
Macro referenced in 6d.


What is the viewport used in the graphics display below?
Left = 0, Bottom = 0, Width = 150, Height = 150
- Left = 0, Bottom = 0, Width = 150, Height = 150
- Left = 0, Bottom = 50, Width = 150, Height = 150
- Left = 50, Bottom = 0, Width = 150, Height = 150
- Left = 50, Bottom = 50, Width = 150, Height = 150
Take into consideration the position of the white rectangle.


Starship Troopers
Dir: Paul Verhoeven Starring: Casper Van Dien, Dina Meyer, Patrick Muldoon, Denise Richards Neil Patrick Harris, Clancy Brown & Michael Ironside
Only for Real "Troopers" (A film review of "Starship Troopers") by Timothy Scott
Okay, so I admit maybe I'm getting old, but the best advice I can give for anyone thinking of seeing "Starship Troopers" can be summed in two words - Ear Plugs.
Normally, IUm a tireless advocate of THX quality theaters with state-of -the-art digital sound. But this film had me wishing I had my remote control. You don't so much watch "Starship Troopers" as survive it. By the end, youUll likely feel as battered and bombarded as the wounded troopers themselves.
Somewhere amidst the carnage is a message from director Paul Verhoeven that we are a society addicted to violence, as capable of inhumanity as the creatures we so gleefully destroy. But you'll probably miss that as you dodge the endless bullets, razor claws and dismembered body parts hurling at you from every direction.
Verhoeven has made another in the long line of technically brilliant "theme park" films we've come to expect BEFORE Labor Day. I suppose by turning up the camp factor Verhoeven has convinced himself that this is social commentary. Sure, if you look hard enough you can find meaning watching the Coyote trying new ways to kill the Road Runner. Sorry Paul, I'm not impressed.  Of course, I mention video games on purpose because I know this film is coming to a Nintendo near you. Frankly, that might be more fun.
Of course, such video game graphics won't compare to the computer generated images seen in this film. As supervised by Phil Tippet of Jurassic Park fame, Industrial Light & Magic do their usual first rate job with the effects. Visually, I haven't seen a film with this many eye-popping wonders since "The Fifth Element." Interestingly, both these films only make me wonder how incredible it would be to see effects like these attached to a real story. Let's just hope George "Skywalker" Lucas knows what I'm talking about.
So, what about the story, you ask?  Succeeding as a trooper is basically advancement by attrition. If you stick around long enough for the commanding officers to die, sooner or later they put you in charge.
 What's most remarkable about the actors is what perfect physical specimens they are. Their performances are so stiff you'd think the tongue that supposed to be in cheek got sucked out by aliens too. Although, in fairness, straight is exactly how this material should be played. If anyone of these characers winked at the audience at all, the whole premise would collapse.
The film is certainly not as derivative as say, "Independence Day." Verhoeven seems to prefer borrowing from himself. The clever news sequences for example are very reminiscent of "RoboCop" (not to mention the incessant bloodshed). The best moments occur when the film is clearly not taking itself seriously as it parodies the WWII newsreels and propaganda films trying to recruit young men and women to sign up for Federal (read: Military) Service.
By joining up, they can become "citizens" - valued members of society honored for their commitment to protecting the human race above all else.  These parodies of fascism arenUt new, but in this kind of film it comes across as rather witty.
Unlike "RoboCop" "Total Recall" or even "Showgirls", "Starship Troopers" will not be remembered years from now. Despite its bludgeon-like impact, none of the perfomances stand out. In fact, even the big, nasty bugs seem bland. In it's attempt to satirize overkill, thatUs exactly what it becomes. The Audience is Listening...just not as well as we used to.
Grade: C+
reply to<EMAIL_ADDRESS>The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Advice From the Trenches
Chris Oakman
January 2014
Chris Oakman
January 2014
"Their [software developers] principal work is human communication to organize the user's expressions of needs into formal procedure."
"Working on the wrong thing for a month is equivalent to not showing up to work for a month at all."
Work somewhere where the quality of the software effects the bottom line.
Chris Oakman
chris@oakmac.com


QA Engineer / Developer in Training
I have over 25 years of experience working in software development mainly as a quality assurance engineer with some experience as a business analyst as well. For the majority of that time I tested on property casualty and life insurance as well as healthcare related systems.
I have a bachelors of arts degree plus technical coursework undertaken after graduating from college.


Sign Up
The Trusted Leader in Text Marketing.
Drive traffic to your business by sending text messages to your customers.
Login


|
|
{{adv.title}} |
{{adv.price| currency:"€"}}
|
| Area: |
{{adv.area}} m2
|
Created on: |
{{adv.CreateDateWithTime}}
|
Visited |
{{adv.visited}} |
| Storey height: |
{{adv.storey_height}} |
Ends on: |
{{adv.DisableDateWithTime}} |
|
|
| Floors: |
{{adv.floors ? adv.floors : '-'}}
|
Deletion on: |
{{adv.DeleteDateWithTime}}
|
On watchlist: |
{{adv.favorite}} |
| {{adv.StatusStr}} |
{{adv.StatusMessage}}
|


Press Spacebar for next slide
Esc or 'o' for overview
Programming is a way to instruct the computer to perform various tasks
| How normal people see it | How Geeks see it |
|---|---|
| Hindi | Python |
| English | C++ |
| Spanish | Java |
| Tamil | Ruby |
(press SPACE to navigate down)
Dennis Ritchie
He also helped in developing UNIX.
(with the help of C++)
#include<stdio.h>
int main()
{
printf("Hello World!");
return 0;
}
#include<stdio.h>
To teach C, how to take input and display output
int main{
main() is the door through which compiler enters your program
printf("Hello World");
This tells C to show output
return 0;
}
The program ended
‘Never forget the’
| Char |
|---|
| takes in character like alphabets |
| int |
|---|
| takes in Integer values |
| Float |
|---|
| stores decimal number with single precision |
| Double |
|---|
| stores decimal number with double precision |
printf(“format specifier”, variable_name);
scanf(“format specifier”, variable_address);
| Format Specifier | Datatype |
|---|---|
| %c | Character |
| %f | Float |
| %d | Integer |
| Unary | + - ! ~ ++ -- (type) * & sizeof | Right to Left |
| Multiplicative | * / % | Left to Right |
| Additive | + - | Left to Right |
| Shift | << >> | Left to Right |
| Relational | < <= > >= | Left to Right |
| Equity | == != | Left to Right |
| Bitwise AND | & | Left to Right |
| Bitwise XOR | ^ | Left to Right |
Table Continued...
| Bitwise OR | | | Left to Right |
| Logical AND | && | Left to Right |
| Logical OR | || | Left to Right |
| Conditional | ? : | Right to Left |
Condition block need to be executed or not is decided by the condition.
If the condition is "true" statement block will be executed, if condition is "false" then statement block will not be executed.
If (condition 1 )
{
Executed if condition is true
}
Examples:
if(3 + 2 % 5)
printf("It works");
if(a=10)
printf("Even this works");
if(-5)
printf("Suprisingly even this works");
Note: In C programming, Any non-zero value is considered to be true, Whereas 0 is considered to be false.
if (condition)
{
Executes this block if condition is true
}
else
{
Executes this block if condition is false
}
(as a substitute for if-else statement)
condition ? expression 1 : expression 2;
int x,y;
scanf("%d",&x);
y=(x > 5 ? 3 : 4);
This statement will store 3 in y if x is greater than 5, otherwise it will store 4 in y.
The equivalent if statement will be
if( x > 5 )
y = 3;
else
y = 4;
Switch (n) {
case 1 :
Executed when n = 1
break;
case 2:
Executed when n = 2
break;
default :
Executed when none of the cases are true
Question time?
Question: Take values of length and breadth of a rectangle from user and check if it is square or not.
Input:
5 3
4 4
Output:No
Yes
#include<stdio.h>
int main() {
int x, y;
scanf("%d %d", &x,&y);
if(x==y)
printf("Yes");
else
printf("No");
return 0;
}
Loops in programming comes into use when we need to repeatedly execute a block of statements.
Until the statement turns False.
for ( initialisation ; termination condition ; upgradation)
{
body of Loop
}
main()
{
int i;
for( i=0 ; i <= 10 ; i++ )
printf("%d",i);
}
Output: 1 2 3 4 5 6 7 8 9 10
initialise loop counter;
while( test loop counter using a condition )
{
Do this;
And this;
Update loop counter;
}
do
{
this;
and this;
and this;
}
while(this condition is true);
Note: This loop executes for at least once irrespective of the test condition due to the “do” block.
Moving on to some
topics
Collection of items of the same datatype stored at contiguous memory locations
In C, we can declare an array by specifying its type and size or by initializing it or by both.
Array indices starts at zero and go to one less than the size of the array
Example : int arr[9] = {10, 20, 30, 40, 50, 60, 70, 80, 90}
It is a VARIABLE
which holds
address of another variable of same data type
THE '&' OPERATOR <--access Memory from Variable
THE '*' OPERATOR <--access Variable from Memory
To access address of a variable to a pointer, we use the unary operator & (Ampersand) that returns the address of that variable. For example &x gives us address of variable x.
One more operator is unary * (Asterisk) which is used for two things: To declare a pointer variable. When a pointer variable is declared in C/C++, there must be an * before its name. And to access the value stored in the address we use this unary operator that eventually returns the value of the variable located at the address specified by its operand.
void main(){
int var = 10, *ptr;
ptr = &var;
printf("%d\n", var);
printf("%p\n", ptr);
printf("%d\n", *ptr);
}
10
0x7fff84ef7e7c
10
(In simplest words)
| Pass by Value | Pass by Reference |
|---|---|
| We pass variable as function arguments | We pass value address as function arguments |
| void swap(int x, int y) | void swap(int *x, int*y) |
The process in which a function calls itself directly or indirectly
Example: A function to return factorial of a number
int fact(int n)
{
if (n <= 1) // base case
return 1;
else
return n*fact(n-1);
}
Time Complexity of push (), pop(), peek (), isEmpty() the functions :O(1)
Time Complexity enqueue(), dequeue(), isFull(), isEmpty(), front() and rear() is O(1).
For Any Queries


Reach
Username/Sign Out
×
Search
Create Event
Profile
☰
Edit Event
Location
Select your option
0.5
1
5
10
15
20
Unlimited
Range (km)
Event Name
Start Date & Time
End Date & Time
Capacity
Event Description
Event Type
Select your option
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Post for (days)
Submit
About
Terms
Contact Us
Privacy


{% extends 'authdash.html' %} {% block body %}
System Dashboard
Manage your Virtual Machines by selecting the VM from the ownership list below. Jira tickets can also be created if problems arise
| Hostname | CPU Count | RAM (GB) | Disk Size (GB) | Power Status | ||
|---|---|---|---|---|---|---|
| {{vm.hostname}} | {{vm.cpu}} | {{vm.ram}} | {{vm.disk}} | {{vm.power}} |
|


James Galantino
Portfolio
About
Portfolio
1. Rec app repo
2. Pipe Cleaner app repo
3. Work Day Scheduler repo
4. Eat Da Burger app repo


Natural ability
Ultrasonic waves of the Golbat help him not only to move without eyes, but also to hunt. The waves stun the prey, and the Pokemon catches it easily.


23 November 1998
Disease Outbreak Reported
Based on reports from the Pan American Health Organization (PAHO), Regional Office for the Americas, WHO
Local WHO offices in the affected countries have been reinforced by technical personnel with a range of specialities, including environmental sanitation, epidemiological surveillance, food hygiene and vaccination. 31 experts have been sent to Honduras, 19 to Nicaragua, 4 to Guatemala, 3 to Belize and 2 to El Salvador.
Nicaragua. The areas most damaged are along the Pacific coast and in the northern part of the country. Until now, 2 362 deaths have been confirmed, 970 persons have disappeared and over 55 000 have been displaced. Major damage has been sustained by the infrastructure (roads, water supply and sanitation systems) and by agricultural production.
Reports of suspected cases of cholera in Matalgalpa and Esteli reflect high levels of water contamination and the difficulties associated with chlorine distribution. In accessible areas, suspected cases of cholera have been managed in a timely fashion by health personnel. Although there is a risk of an epidemic outbreak, the situation has so far been under control. Reports on dengue from Leon, Boaco and Rivas do not differ from the annual averages, however there is probably underreporting of cases in the affected areas.
On 13 November 1998, 16 suspected cases of leptospirosis were reported in Chinandega, in the community of El Viejo: 8 were hospitalized, 5 have died and 3 have received laboratory confirmation. In addition, 1 suspected case has been reported in Matagalpa, 1 in Managua and 1 in Esteli.
Of the 8 areas suffering the greatest problems, communication has been reestablished by road in 5. The 3 others can only be reached by air, thus the quantity of drugs, food and fuel that can be transported there is limited. Many communities remain isolated in all of the affected areas.
Honduras. The country has been severely affected and losses in human lives, infrastructure and agriculture continue to rise. Earlier estimates of deaths and of populations at risk have been exceeded as health teams reach previously isolated areas. Currently 7 000 deaths have been confirmed, 12 000 people have disappeared and over 500 000 were estimated to be living in 938 shelters as of 13 November (down from 800 000 in the first 24 hours after the passage of the hurricane).


Next: defun, Previous: Data and Control Flow Dictionary, Up: Data and Control Flow Dictionary
apply
function &rest args^+ ⇒ {result}*
function—a function designator.
args—a spreadable argument list designator.
results—the values returned by function.
Applies the function to the args.
When the function receives its arguments via &rest, it is permissible (but not required) for the implementation to bind the rest parameter to an object that shares structure with the last argument to apply. Because a function can neither detect whether it was called via apply nor whether (if so) the last argument to apply was a constant, conforming programs must neither rely on the list structure of a rest list to be freshly consed, nor modify that list structure.
setf can be used with apply in certain circumstances; see APPLY Forms as Places.
(setq f '+) ⇒ + (apply f '(1 2)) ⇒ 3 (setq f #'-) ⇒ #<FUNCTION -> (apply f '(1 2)) ⇒ -1 (apply #'max 3 5 '(2 7 3)) ⇒ 7 (apply 'cons '((+ 2 3) 4)) ⇒ ((+ 2 3) . 4) (apply #'+ '()) ⇒ 0 (defparameter *some-list* '(a b c)) (defun strange-test (&rest x) (eq x *some-list*)) (apply #'strange-test *some-list*) ⇒ implementation-dependent (defun bad-boy (&rest x) (rplacd x 'y)) (bad-boy 'a 'b 'c) has undefined consequences. (apply #'bad-boy *some-list*) has undefined consequences.
(defun foo (size &rest keys &key double &allow-other-keys) (let ((v (apply #'make-array size :allow-other-keys t keys))) (if double (concatenate (type-of v) v v) v))) (foo 4 :initial-contents '(a b c d) :double t) ⇒ #(A B C D A B C D)
funcall, fdefinition, function, Evaluation, APPLY Forms as Places
Next: defun, Previous: Data and Control Flow Dictionary, Up: Data and Control Flow Dictionary


This document describes Flink’s fault tolerance mechanism for streaming data flows.
Apache Flink offers a fault tolerance mechanism to consistently recover the state of data streaming applications. The mechanism ensures that even in the presence of failures, the program’s state will eventually reflect every record from the data stream exactly once. Note that there is a switch to downgrade the guarantees to at least once (described below).
The fault tolerance mechanism continuously draws snapshots of the distributed streaming data flow. For streaming applications with small state, these snapshots are very light-weight and can be drawn frequently without impacting the performance much. The state of the streaming applications is stored at a configurable place (such as the master node, or HDFS).
In case of a program failure (due to machine-, network-, or software failure), Flink stops the distributed streaming dataflow. The system then restarts the operators and resets them to the latest successful checkpoint. The input streams are reset to the point of the state snapshot. Any records that are processed as part of the restarted parallel dataflow are guaranteed to not have been part of the checkpointed state before.
Note: For this mechanism to realize its full guarantees, the data stream source (such as message queue or broker) needs to be able to rewind the stream to a defined recent point. Apache Kafka has this ability and Flink’s connector to Kafka exploits this ability.
Note: Because Flink’s checkpoints are realized through distributed snapshots, we use the words snapshot and checkpoint interchangeably.
The central part of Flink’s fault tolerance mechanism is drawing consistent snapshots of the distributed data stream and operator state. These snapshots act as consistent checkpoints to which the system can fall back in case of a failure. Flink’s mechanism for drawing these snapshots is described in “Lightweight Asynchronous Snapshots for Distributed Dataflows”. It is inspired by the standard Chandy-Lamport algorithm for distributed snapshots and is specifically tailored to Flink’s execution model.
A core element in Flink’s distributed snapshotting are the stream barriers. These barriers are injected into the data stream and flow with the records as part of the data stream. Barriers never overtake records, the flow strictly in line. A barrier separates the records in the data stream into the set of records that goes into the current snapshot, and the records that go into the next snapshot. Each barrier carries the ID of the snapshot whose records it pushed in front of it. Barriers do not interrupt the flow of the stream and are hence very lightweight. Multiple barriers from different snapshots can be in the stream at the same time, which means that various snapshots may happen concurrently.
Stream barriers are injected into the parallel data flow at the stream sources. The point where the barriers for snapshot n are injected (let’s call it Sn) is the position in the source stream up to which the snapshot covers the data. For example, in Apache Kafka, this position would be the last record’s offset in the partition. This position Sn is reported to the checkpoint coordinator (Flink’s JobManager).
The barriers then flow downstream. When an intermediate operator has received a barrier for snapshot n from all of its input streams, it emits itself a barrier for snapshot n into all of its outgoing streams. Once a sink operator (the end of a streaming DAG) has received the barrier n from all of its input streams, it acknowledges that snapshot n to the checkpoint coordinator. After all sinks acknowledged a snapshot, it is considered completed.
When snapshot n is completed, it is certain that no records from before Sn will be needed any more from the source, because these records (and their descendant records) have passed through the entire data flow topology.
Operators that receive more than one input stream need to align the input streams on the snapshot barriers. The figure above illustrates this:
When operators contain any form of state, this state must be part of the snapshots as well. Operator state comes in different forms:
map()
or filter()
). User-defined state can either be a simple variable in the function’s java object, or the associated key/value state of a function (see State in Streaming Applications for details).Operators snapshot their state at the point in time when they received all snapshot barriers from their input streams, before emitting the barriers to their output streams. At that point, all updates to the state from records before the barriers will have been made, and no updates that depend on records from after the barriers have been applied. Because the state of a snapshot may be potentially large, it is stored in a configurable state backend. By default, this is the JobManager’s memory, but for serious setups, a distributed reliable storage should be configured (such as HDFS). After the state has been stored, the operator acknowledges the checkpoint, emits the snapshot barrier into the output streams, and proceeds.
The resulting snapshot now contains:
The alignment step may add latency to the streaming program. Usually, this extra latency is in the order of a few milliseconds, but we have seen cases where the latency of some outliers increased noticeably. For applications that require consistently super low latencies (few milliseconds) for all records, Flink has a switch to skip the stream alignment during a checkpoint. Checkpoint snapshots are still drawn as soon as an operator has seen the checkpoint barrier from each input.
When the alignment is skipped, an operator keeps processing all inputs, even after some checkpoint barriers for checkpoint n arrived. That way, the operator also processes elements that belong to checkpoint n+1 before the state snapshot for checkpoint n was taken. On a restore, these records will occur as duplicates, because they are both included in the state snapshot of checkpoint n, and will be replayed as part of the data after checkpoint n.
NOTE: Alignment happens only for operators with multiple predecessors (joins) as well as operators with multiple senders (after a stream repartitioning/shuffle).
Because of that, dataflows with only embarrassingly parallel streaming operations (map()
, flatMap()
, filter()
, …) actually give exactly once guarantees even
in at least once mode.
Recovery under this mechanism is straightforward: Upon a failure, Flink selects the latest completed checkpoint k. The system then re-deploys the entire distributed dataflow, and gives each operator the state that was snapshotted as part of checkpoint k. The sources are set to start reading the stream from position Sk. For example in Apache Kafka, that means telling the consumer to start fetching from offset Sk.
If state was snapshotted incrementally, the operators start with the state of the latest full snapshot and then apply a series of incremental snapshot updates to that state.


Horizontal Nav
We can use
display: flex;
to replace
float
to create a horizontal navigations.
display: flex;
Home
News
Contact
About
flex-direction
Home
News
Contact
About
justify-content
Home
News
Contact
About
align-items
Home
News
Contact
About
flex-grow
Home
News
Contact
About


Orzo with Parmesan and Basil
Allrecipes
Ingredients
-
-
2
tablespoons butter
-
1
cup uncooked orzo pasta
-
1
(14.5 ounce) can chicken broth
-
1/2
cup grated Parmesan cheese
-
1/4
cup chopped fresh basil
-
salt and pepper to taste
-
2
tablespoons chopped fresh basil
Instructions
-
-
Melt butter in heavy skillet over medium-high heat. Stir in orzo and saute until lightly browned.
-
Stir in chicken stock and bring to boil. Cover. Reduce heat and simmer until orzo is tender and liquid is absorbed, about 15 - 20 minutes.
-
Mix in Parmesan cheese and basil. Season with salt and pepper. Transfer to shallow bowl. Garnish with basil sprigs.
Notes


Booking Confirmation
Booking For
Date: {{booking.date}}
Name: {{booking.name}}
Email: {{booking.email}}
{% if booking.company %}Company: {{booking.company}}
{% endif %}
{% if booking.rego %}Rego(s): {{booking.rego}}
{% endif %}
{% if booking.phone %}Phone: {{booking.phone}}
{% endif %}
Booking Made by
Name: {{user.username}}
Email: {{user.email}}
Hub: {{user.hub}}
Carpark
Carpark: {{carpark.name}}
Description: {{carpark.description}}
Google maps Link: Carpark
Bays
{% for bay in bays %}
---
Bay Number: {{bay.bay.bay_number}}
Time: {{bay.start_time|date:"f a"}} - {{bay.end_time|date:"f a"}}
{% if bay.bay.description %}Description: {{bay.bay.description}}
{% endif %}
{% endfor %}
Thanks for booking with UniPark


We are a retailer of stationery and books (fiction and non-fiction), and we hope that you will find our web-site useful.
Before The Frost
Going Postal
Runaway
The Lighthouse
Dark Star Safari
Self-made Man
The Promise
Us And Them
Erasers
Pencil sets
Customer Service
About Us
Community Site!


Pick-Up Student
Sign Up
Sign In
×
Username
Password
Sign In
Remember me
Cancel
Forgot password?
×
Email
Username
Password
Sign Up
Cancel


The btOverlappingPairCallback class is an additional optional broadphase user callback for adding/removing overlapping pairs, similar interface to btOverlappingPairCache.
More...
#include <btOverlappingPairCallback.h>
The btOverlappingPairCallback class is an additional optional broadphase user callback for adding/removing overlapping pairs, similar interface to btOverlappingPairCache.
Definition at line 24 of file btOverlappingPairCallback.h.
◆ btOverlappingPairCallback()
| btOverlappingPairCallback::btOverlappingPairCallback |
( |
| ) |
|
|
inlineprotected |
◆ ~btOverlappingPairCallback()
| virtual btOverlappingPairCallback::~btOverlappingPairCallback |
( |
| ) |
|
|
inlinevirtual |
◆ addOverlappingPair()
◆ removeOverlappingPair()
◆ removeOverlappingPairsContainingProxy()
The documentation for this class was generated from the following file:


IC 50 and EC 50 Values Were Determined for Inhibition of NS3-4A Protease Activity and HCV RNA Replication, Respectively
Notes: NS3-4A protease activity was determined with recombinant genotype 1b enzyme and IC 50 values calculated with regression analyses on plots of activity vs [inhibitor] as shown in Figure 2. All compounds were tested along with a known antagonist Anaspec 25346 as a positive control to ensure enzyme performance as stated by the manufacturer. For EC 50 determinations, log-phase replicon cells were incubated with porphyrin or control vehicle 48 hr and the relative amount of HCV RNA then determined by the comparative cycle threshold level (ΔCΤ) as described in methods. EC 50 was then extrapolated by regression on plots of HCV RNA vs [Inhibitor] curves as shown in Figure 2. All compounds were tested along with a known positive control, danoprevir 30 as described in methods to ensure replicon and assay performance. Each IC 50 or EC 50 value is the mean of at least two separate experiments with 3–5 determinations per point and variances were pooled using analysis of variance. Statistical values were determined using Fisher’s Least Significant Difference (LSD) test for multiple comparisons.


Game.System.EnemyControlSystem Class
EnemyControlSystem
Constructor
Game.System.EnemyControlSystem
()
Item Index
Methods
Methods
init
-
nodeType
The initialization method is called when the object is constructor.
Parameters:
-
nodeType
StringThe type of the node. See Core.Node.TYPE.
onEngineAdd
-
engine
Callback method when this system is added to the engine.
Parameters:
-
engine
Core.Enginereference to the Core.Engine object.
onEngineRemove
-
engine
Callback method when this system is removed from the engine.
Parameters:
-
engine
Core.Enginereference to the Core.Engine object.
update
()
The update loop of this system, as called by a given Core.Engine's update loop. All related Core.Node objects are updated. Handling of each node individually can be performed by overriding the updateNode method.
Properties
enabled
Boolean
Indicates if the system is currently enabled or not. If not enabled, no system or node updates will be performed.
Default: true
priority
Integer
The priority of the current system. This is used by the Core.Engine to order the sequence of systems that it processes. Lower priority numbers are executed first.
Default: 0


context deadline exceeded
error occurs when using context.WithDeadline()
and the deadline has expired.
package main
import (
"context"
"log"
"time"
)
func main() {
var ctx context.Context
var ctxCancelFunc context.CancelFunc
var timeTillContextDeadline = time.Now().Add(3 * time.Second)
ctx, ctxCancelFunc = context.WithDeadline(context.Background(), timeTillContextDeadline)
defer ctxCancelFunc()
time.Sleep(5 * time.Second) //Sleep simulates time your program was doing something
//Check context for error, If ctx.Err() != nil gracefully exit the current execution
if ctx.Err() != nil {
log.Println(ctx.Err())
}
}
In most cases this isn’t an error you would fix. This is simple a signal that your code should stop and gracefully exit what its doing.
Created by Jon Calhoun, but you can check out the source and contribute on GitHub


The jQuery Cycle Plugin is a lightweight slideshow plugin. Its implementation is based on the InnerFade Plugin by Torsten Baldes, the Slideshow Plugin by Matt Oakes, and the jqShuffle Plugin by Benjamin Sterling. It supports pause-on-hover, auto-stop, auto-fit, before/after callbacks, click triggers and many transition effects. It also supports, but does not require, the Metadata Plugin and the Easing Plugin.
The plugin provides a method called cycle which is invoked on a container element. Each child element of the container becomes a "slide". Options control how and when the slides are transitioned.
shuffle
|
zoom
|
fade
|
turnDown
|
curtainX
|
scrollRight (click)
|


Project Manager | Web Developer | UI Designer
Tell Me More
I'm a tenacious developer with a passion for continuous learning and powerful design.
From my academic background in Business & Information Systems to my experience as a Technical Project Manager in Healthcare IT, I've always been fascinated with tech. After learning JavaScript, I quickly fell in love with web development and haven't looked back since.
When I'm not coding you can find me climbing at Boulder Canyon or trail running at Marshall Mesa.
Enough said, time to get to the good stuff!
Software Implementations
Integration Projects
Agile & Scrum
Git Workflow
HTML5 | CSS
JavaScript | ES6 | jQuery
React.js
React Native
Node.js
Express.js
Knex.js
SQL
PostgreSQL
Chai
Mocha
Supertest
click images to see more
Ⓒ 2019 Encep Nurdin


Good, reliable, bookkeepers can be hard to find. The Bounty Bookkeeping team has the expertise to keep your books up-to-date and accurate.
At Bounty Bookkeeping we do the bookkeeping so you can focus on building a great business!
Based in the northern suburbs of Melbourne, we are a boutique bookkeeping practice servicing clients from all around Australia.
Not sure where to start? We are offering every business owner a free 30 minute financial health check. No catches...just solid advice.
Book FREE Health Check NowHere are just a few of the industries we work with...
The healthcare industry, has many challenges and requirements other industries don't have. A healthcare business needs to be setup with the right software and procedures, and thats where Bounty Bookkeeping can help.
Here are just a few ways we can help your healthcare practice:
If you’re like a lot construction businesses, you might still do your books by hand. Problem is, the combination of human error and time constraints of a busy business can lead to errors and unpaid accounts.
Poor bookkeeping can lead to all sorted of challenges, here are a few we hear about quite a lot:
Starting and running a retail business is both exciting and demanding. You will need to be considering trading hours, rents, seasonal trade and the challenge of casual and part time staff. In addition, you have all the usual small business compliance issues of GST, BAS and PAYG.
Bounty Bookkeeping can help take the stress and headaches out of running a business. Here's just a few of the ways we can help:
We proudly work with, and are endorsed by:
No pressure sales, no jargon...just honest advice


BOOTPARAM
Section: Linux Programmer's Manual (7)
Updated: 2014-06-13
Index
Return to Main Contents
NAME
bootparam - introduction to boot time parameters of the Linux kernel
DESCRIPTION
The Linux kernel accepts certain 'command-line options' or 'boot time
parameters' at the moment it is started.
In general this is used to
supply the kernel with information about hardware parameters that
the kernel would not be able to determine on its own, or to avoid/override
the values that the kernel would otherwise detect.
When the kernel is booted directly by the BIOS (say from a floppy to
which you copied a kernel using 'cp zImage /dev/fd0'),
you have no opportunity to specify any parameters.
So, in order to take advantage of this possibility you have to
use a boot loader that is able to pass parameters, such as GRUB.
The argument list
The kernel command line is parsed into a list of strings
(boot arguments) separated by spaces.
Most of the boot arguments take have the form:
name[=value_1][,value_2]...[,value_10]
where 'name' is a unique keyword that is used to identify what part of
the kernel the associated values (if any) are to be given to.
Note the limit of 10 is real, as the present code handles only 10 comma
separated parameters per keyword.
(However, you can reuse the same
keyword with up to an additional 10 parameters in unusually
complicated situations, assuming the setup function supports it.)
Most of the sorting is coded in the kernel source file
init/main.c.
First, the kernel
checks to see if the argument is any of the special arguments 'root=',
'nfsroot=', 'nfsaddrs=', 'ro', 'rw', 'debug' or 'init'.
The meaning of these special arguments is described below.
Then it walks a list of setup functions (contained in the bootsetups
array) to see if the specified argument string (such as 'foo') has
been associated with a setup function ('foo_setup()') for a particular
device or part of the kernel.
If you passed the kernel the line
foo=3,4,5,6 then the kernel would search the bootsetups array to see
if 'foo' was registered.
If it was, then it would call the setup
function associated with 'foo' (foo_setup()) and hand it the arguments
3, 4, 5, and 6 as given on the kernel command line.
Anything of the form 'foo=bar' that is not accepted as a setup function
as described above is then interpreted as an environment variable to
be set.
A (useless?) example would be to use 'TERM=vt100' as a boot
argument.
Any remaining arguments that were not picked up by the kernel and were
not interpreted as environment variables are then passed onto process
one, which is usually the
init(1)
program.
The most common argument that
is passed to the
init
process is the word 'single' which instructs it
to boot the computer in single user mode, and not launch all the usual
daemons.
Check the manual page for the version of
init(1)
installed on
your system to see what arguments it accepts.
General non-device-specific boot arguments
- 'init=...'
-
This sets the initial command to be executed by the kernel.
If this is not set, or cannot be found, the kernel will try
/sbin/init,
then
/etc/init,
then
/bin/init,
then
/bin/sh
and panic if all of this fails.
- 'nfsaddrs=...'
-
This sets the nfs boot address to the given string.
This boot address is used in case of a net boot.
- 'nfsroot=...'
-
This sets the nfs root name to the given string.
If this string
does not begin with '/' or ',' or a digit, then it is prefixed by
'/tftpboot/'.
This root name is used in case of a net boot.
- 'no387'
-
(Only when
CONFIG_BUGi386
is defined.)
Some i387 coprocessor chips have bugs that show up when used in 32 bit
protected mode.
For example, some of the early ULSI-387 chips would
cause solid lockups while performing floating-point calculations.
Using the 'no387' boot argument causes Linux to ignore the maths
coprocessor even if you have one.
Of course you must then have your
kernel compiled with math emulation support!
- 'no-hlt'
-
(Only when
CONFIG_BUGi386
is defined.)
Some of the early i486DX-100 chips have a problem with the 'hlt'
instruction, in that they can't reliably return to operating mode
after this instruction is used.
Using the 'no-hlt' instruction tells
Linux to just run an infinite loop when there is nothing else to do,
and to not halt the CPU.
This allows people with these broken chips
to use Linux.
- 'root=...'
-
This argument tells the kernel what device is to be used as the root
filesystem while booting.
The default of this setting is determined
at compile time, and usually is the value of the root device of the
system that the kernel was built on.
To override this value, and
select the second floppy drive as the root device, one would
use 'root=/dev/fd1'.
The root device can be specified symbolically or numerically.
A symbolic specification has the form
/dev/XXYN,
where XX designates
the device type ('hd' for ST-506 compatible hard disk, with Y in
'a'-'d'; 'sd' for SCSI compatible disk, with Y in 'a'-'e';
'ad' for Atari ACSI disk, with Y in 'a'-'e',
'ez' for a Syquest EZ135 parallel port removable drive, with Y='a',
'xd' for XT compatible disk, with Y either 'a' or 'b'; 'fd' for
floppy disk, with Y the floppy drive number---fd0 would be
the DOS 'A:' drive, and fd1 would be 'B:'), Y the driver letter or
number, and N the number (in decimal) of the partition on this device
(absent in the case of floppies).
Recent kernels allow many other
types, mostly for CD-ROMs: nfs, ram, scd, mcd, cdu535, aztcd, cm206cd,
gscd, sbpcd, sonycd, bpcd.
(The type nfs specifies a net boot; ram refers to a ram disk.)
Note that this has nothing to do with the designation of these
devices on your filesystem.
The '/dev/' part is purely conventional.
The more awkward and less portable numeric specification of the above
possible root devices in major/minor format is also accepted.
(For example,
/dev/sda3
is major 8, minor 3, so you could use 'root=0x803' as an
alternative.)
- 'rootdelay='
-
This parameter sets the delay (in seconds) to pause before attempting
to mount the root filesystem.
- 'rootflags=...'
-
This parameter sets the mount option string for the root filesystem
(see also
fstab(5)).
- 'rootfstype=...'
-
The 'rootfstype' option tells the kernel to mount the root filesystem as
if it where of the type specified.
This can be useful (for example) to
mount an ext3 filesystem as ext2 and then remove the journal in the root
filesystem, in fact reverting its format from ext3 to ext2 without the
need to boot the box from alternate media.
- 'ro' and 'rw'
-
The 'ro' option tells the kernel to mount the root filesystem
as 'read-only' so that filesystem consistency check programs (fsck)
can do their work on a quiescent filesystem.
No processes can
write to files on the filesystem in question until it is 'remounted'
as read/write capable, for example, by 'mount -w -n -o remount /'.
(See also
mount(8).)
The 'rw' option tells the kernel to mount the root filesystem read/write.
This is the default.
- 'resume=...'
-
This tells the kernel the location of the suspend-to-disk data that you want the machine to resume from after hibernation.
Usually, it is the same as your swap partition or file. Example:
resume=/dev/hda2
- 'reserve=...'
-
This is used to protect I/O port regions from probes.
The form of the command is:
reserve=iobase,extent[,iobase,extent]...
In some machines it may be necessary to prevent device drivers from
checking for devices (auto-probing) in a specific region.
This may be
because of hardware that reacts badly to the probing, or hardware
that would be mistakenly identified, or merely
hardware you don't want the kernel to initialize.
The reserve boot-time argument specifies an I/O port region that
shouldn't be probed.
A device driver will not probe a reserved region,
unless another boot argument explicitly specifies that it do so.
For example, the boot line
reserve=0x300,32 blah=0x300
-
keeps all device drivers except the driver for 'blah' from probing
0x300-0x31f.
- 'mem=...'
-
The BIOS call defined in the PC specification that returns
the amount of installed memory was designed only to be able
to report up to 64MB.
Linux uses this BIOS call at boot to
determine how much memory is installed.
If you have more than 64MB of
RAM installed, you can use this boot argument to tell Linux how much memory
you have.
The value is in decimal or hexadecimal (prefix 0x),
and the suffixes 'k' (times 1024) or 'M' (times 1048576) can be used.
Here is a quote from Linus on usage of the 'mem=' parameter.
The kernel will accept any 'mem=xx' parameter you give it, and if it
turns out that you lied to it, it will crash horribly sooner or later.
The parameter indicates the highest addressable RAM address, so
'mem=0x1000000' means you have 16MB of memory, for example.
For a 96MB machine this would be 'mem=0x6000000'.
NOTE:
some machines might use the top of memory for BIOS
caching or whatever, so you might not actually have up to the full
96MB addressable.
The reverse is also true: some chipsets will map
the physical memory that is covered by the BIOS area into the area
just past the top of memory, so the top-of-mem might actually be 96MB
+ 384kB for example.
If you tell linux that it has more memory than
it actually does have, bad things will happen: maybe not at once, but
surely eventually.
You can also use the boot argument 'mem=nopentium' to turn off 4 MB
page tables on kernels configured for IA32 systems with a pentium or newer
CPU.
- 'panic=N'
-
By default the kernel will not reboot after a panic, but this option
will cause a kernel reboot after N seconds (if N is greater than zero).
This panic timeout can also be set by
echo N > /proc/sys/kernel/panic
- 'reboot=[warm|cold][,[bios|hard]]'
-
(Only when
CONFIG_BUGi386
is defined.)
Since 2.0.22 a reboot is by default a cold reboot.
One asks for the old default with 'reboot=warm'.
(A cold reboot may be required to reset certain hardware,
but might destroy not yet written data in a disk cache.
A warm reboot may be faster.)
By default a reboot is hard, by asking the keyboard controller
to pulse the reset line low, but there is at least one type
of motherboard where that doesn't work.
The option 'reboot=bios' will
instead jump through the BIOS.
- 'nosmp' and 'maxcpus=N'
-
(Only when __SMP__ is defined.)
A command-line option of 'nosmp' or 'maxcpus=0' will disable SMP
activation entirely; an option 'maxcpus=N' limits the maximum number
of CPUs activated in SMP mode to N.
Boot arguments for use by kernel developers
- 'debug'
-
Kernel messages are handed off to the kernel log daemon klogd so that they
may be logged to disk.
Messages with a priority above
console_loglevel
are also printed on the console.
(For these levels, see
<linux/kernel.h>.)
By default this variable is set to log anything more important than
debug messages.
This boot argument will cause the kernel to also
print the messages of DEBUG priority.
The console loglevel can also be set at run time via an option
to klogd.
See
klogd(8).
- 'profile=N'
-
It is possible to enable a kernel profiling function,
if one wishes to find out where the kernel is spending its CPU cycles.
Profiling is enabled by setting the variable
prof_shift
to a nonzero value.
This is done either by specifying
CONFIG_PROFILE
at compile time, or by giving the 'profile=' option.
Now the value that
prof_shift
gets will be N, when given, or
CONFIG_PROFILE_SHIFT,
when that is given, or 2, the default.
The significance of this variable is that it
gives the granularity of the profiling: each clock tick, if the
system was executing kernel code, a counter is incremented:
profile[address >> prof_shift]++;
The raw profiling information can be read from
/proc/profile.
Probably you'll want to use a tool such as readprofile.c to digest it.
Writing to
/proc/profile
will clear the counters.
- 'swap=N1,N2,N3,N4,N5,N6,N7,N8'
-
Set the eight parameters max_page_age, page_advance, page_decline,
page_initial_age, age_cluster_fract, age_cluster_min, pageout_weight,
bufferout_weight that control the kernel swap algorithm.
For kernel tuners only.
- 'buff=N1,N2,N3,N4,N5,N6'
-
Set the six parameters max_buff_age, buff_advance, buff_decline,
buff_initial_age, bufferout_weight, buffermem_grace that control
kernel buffer memory management.
For kernel tuners only.
Boot arguments for ramdisk use
(Only if the kernel was compiled with
CONFIG_BLK_DEV_RAM.)
In general it is a bad idea to use a ramdisk under Linux---the
system will use available memory more efficiently itself.
But while booting (or while constructing boot floppies)
it is often useful to load the floppy contents into a
ramdisk.
One might also have a system in which first
some modules (for filesystem or hardware) must be loaded
before the main disk can be accessed.
In Linux 1.3.48, ramdisk handling was changed drastically.
Earlier, the memory was allocated statically, and there was
a 'ramdisk=N' parameter to tell its size.
(This could also be set in the kernel image at compile time.)
These days ram disks use the buffer cache, and grow dynamically.
For a lot of information in conjunction with the new ramdisk
setup, see the kernel source file
Documentation/blockdev/ramdisk.txt
(Documentation/ramdisk.txt
in older kernels).
There are four parameters, two boolean and two integral.
- 'load_ramdisk=N'
-
If N=1, do load a ramdisk.
If N=0, do not load a ramdisk.
(This is the default.)
- 'prompt_ramdisk=N'
-
If N=1, do prompt for insertion of the floppy.
(This is the default.)
If N=0, do not prompt.
(Thus, this parameter is never needed.)
- 'ramdisk_size=N' or (obsolete) 'ramdisk=N'
-
Set the maximal size of the ramdisk(s) to N kB.
The default is 4096 (4 MB).
- 'ramdisk_start=N'
-
Sets the starting block number (the offset on the floppy where
the ramdisk starts) to N.
This is needed in case the ramdisk follows a kernel image.
- 'noinitrd'
-
(Only if the kernel was compiled with
CONFIG_BLK_DEV_RAM
and
CONFIG_BLK_DEV_INITRD.)
These days it is possible to compile the kernel to use initrd.
When this feature is enabled, the boot process will load the kernel
and an initial ramdisk; then the kernel converts initrd into
a "normal" ramdisk, which is mounted read-write as root device;
then
/linuxrc
is executed; afterward the "real" root filesystem is mounted,
and the initrd filesystem is moved over to
/initrd;
finally
the usual boot sequence (e.g., invocation of
/sbin/init)
is performed.
For a detailed description of the initrd feature, see the kernel source file
Documentation/initrd.txt.
The 'noinitrd' option tells the kernel that although it was compiled for
operation with initrd, it should not go through the above steps, but
leave the initrd data under
/dev/initrd.
(This device can be used only once: the data is freed as soon as
the last process that used it has closed
/dev/initrd.)
Boot arguments for SCSI devices
General notation for this section:
iobase
-- the first I/O port that the SCSI host occupies.
These are specified in hexadecimal notation,
and usually lie in the range from 0x200 to 0x3ff.
irq
-- the hardware interrupt that the card is configured to use.
Valid values will be dependent on the card in question, but will
usually be 5, 7, 9, 10, 11, 12, and 15.
The other values are usually
used for common peripherals like IDE hard disks, floppies, serial
ports, and so on.
scsi-id
-- the ID that the host adapter uses to identify itself on the
SCSI bus.
Only some host adapters allow you to change this value, as
most have it permanently specified internally.
The usual default value
is 7, but the Seagate and Future Domain TMC-950 boards use 6.
parity
-- whether the SCSI host adapter expects the attached devices
to supply a parity value with all information exchanges.
Specifying a one indicates parity checking is enabled,
and a zero disables parity checking.
Again, not all adapters will support selection of parity
behavior as a boot argument.
- 'max_scsi_luns=...'
-
A SCSI device can have a number of 'subdevices' contained within
itself.
The most common example is one of the new SCSI CD-ROMs that
handle more than one disk at a time.
Each CD is addressed as a
'Logical Unit Number' (LUN) of that particular device.
But most
devices, such as hard disks, tape drives and such are only one device,
and will be assigned to LUN zero.
Some poorly designed SCSI devices cannot handle being probed for
LUNs not equal to zero.
Therefore, if the compile-time flag
CONFIG_SCSI_MULTI_LUN
is not set, newer kernels will by default only probe LUN zero.
To specify the number of probed LUNs at boot, one enters
'max_scsi_luns=n' as a boot arg, where n is a number between one and
eight.
To avoid problems as described above, one would use n=1 to
avoid upsetting such broken devices.
- SCSI tape configuration
-
Some boot time configuration of the SCSI tape driver can be achieved
by using the following:
st=buf_size[,write_threshold[,max_bufs]]
The first two numbers are specified in units of kB.
The default
buf_size
is 32kB, and the maximum size that can be specified is a
ridiculous 16384kB.
The
write_threshold
is the value at which the buffer is committed to tape, with a
default value of 30kB.
The maximum number of buffers varies
with the number of drives detected, and has a default of two.
An example usage would be:
st=32,30,2
-
Full details can be found in the file
Documentation/scsi/st.txt
(or
drivers/scsi/README.st
for older kernels) in the Linux kernel source.
- Adaptec aha151x, aha152x, aic6260, aic6360, SB16-SCSI configuration
-
The aha numbers refer to cards and the aic numbers refer to the actual
SCSI chip on these type of cards, including the Soundblaster-16 SCSI.
The probe code for these SCSI hosts looks for an installed BIOS, and
if none is present, the probe will not find your card.
Then you will
have to use a boot argument of the form:
aha152x=iobase[,irq[,scsi-id[,reconnect[,parity]]]]
-
If the driver was compiled with debugging enabled, a sixth
value can be specified to set the debug level.
All the parameters are as described at the top of this section, and the
reconnect
value will allow device disconnect/reconnect if a nonzero value
is used.
An example usage is as follows:
aha152x=0x340,11,7,1
-
Note that the parameters must be specified in order, meaning that if
you want to specify a parity setting, then you will have to specify an
iobase, irq, scsi-id and reconnect value as well.
- Adaptec aha154x configuration
-
The aha1542 series cards have an i82077 floppy controller onboard,
while the aha1540 series cards do not.
These are busmastering cards,
and have parameters to set the "fairness" that is used to share
the bus with other devices.
The boot argument looks like the following.
aha1542=iobase[,buson,busoff[,dmaspeed]]
-
Valid iobase values are usually one of: 0x130, 0x134, 0x230, 0x234,
0x330, 0x334.
Clone cards may permit other values.
The
buson, busoff
values refer to the number of microseconds that the
card dominates the ISA bus.
The defaults are 11us on, and 4us off, so
that other cards (such as an ISA LANCE Ethernet card) have a chance to
get access to the ISA bus.
The
dmaspeed
value refers to the rate (in MB/s) at which the DMA
(Direct Memory Access) transfers proceed.
The default is 5MB/s.
Newer revision cards allow you to select this value as part of the
soft-configuration, older cards use jumpers.
You can use values up to
10MB/s assuming that your motherboard is capable of handling it.
Experiment with caution if using values over 5MB/s.
- Adaptec aha274x, aha284x, aic7xxx configuration
-
These boards can accept an argument of the form:
aic7xxx=extended,no_reset
-
The
extended
value, if nonzero, indicates that extended translation for large
disks is enabled.
The
no_reset
value, if nonzero, tells the driver not to reset the SCSI bus when
setting up the host adapter at boot.
- AdvanSys SCSI Hosts configuration ('advansys=')
-
The AdvanSys driver can accept up to four I/O addresses that will be
probed for an AdvanSys SCSI card.
Note that these values (if used) do
not effect EISA or PCI probing in any way.
They are used only for
probing ISA and VLB cards.
In addition, if the driver has been
compiled with debugging enabled, the level of debugging output can be
set by adding an 0xdeb[0-f] parameter.
The 0-f allows setting the
level of the debugging messages to any of 16 levels of verbosity.
- AM53C974
-
Syntax:
AM53C974=host-scsi-id,target-scsi-id,max-rate,max-offset
- BusLogic SCSI Hosts configuration ('BusLogic=')
-
Syntax:
BusLogic=N1,N2,N3,N4,N5,S1,S2,...
-
For an extensive discussion of the BusLogic command line parameters,
see the kernel source file
drivers/scsi/BusLogic.c.
The text
below is a very much abbreviated extract.
The parameters N1-N5 are integers.
The parameters S1,... are strings.
N1 is the I/O Address at which the Host Adapter is located.
N2 is the Tagged Queue Depth to use for Target Devices that support
Tagged Queuing.
N3 is the Bus Settle Time in seconds.
This is the amount of time
to wait between a Host Adapter Hard Reset which
initiates a SCSI Bus Reset and issuing any SCSI Commands.
N4 is the Local Options (for one Host Adapter).
N5 is the Global Options (for all Host Adapters).
The string options are used to provide control over Tagged Queuing
(TQ:Default, TQ:Enable, TQ:Disable, TQ:<Per-Target-Spec>), over
Error Recovery (ER:Default, ER:HardReset, ER:BusDeviceReset,
ER:None, ER:<Per-Target-Spec>), and over Host Adapter Probing
(NoProbe, NoProbeISA, NoSortPCI).
- EATA/DMA configuration
-
The default list of I/O ports to be probed can be changed by
eata=iobase,iobase,....
- Future Domain TMC-16x0 configuration
-
Syntax:
fdomain=iobase,irq[,adapter_id]
- Great Valley Products (GVP) SCSI controller configuration
-
Syntax:
gvp11=dma_transfer_bitmask
- Future Domain TMC-8xx, TMC-950 configuration
-
Syntax:
tmc8xx=mem_base,irq
-
The
mem_base
value is the value of the memory-mapped I/O region that
the card uses.
This will usually be one of the following values:
0xc8000, 0xca000, 0xcc000, 0xce000, 0xdc000, 0xde000.
- IN2000 configuration
-
Syntax:
in2000=S
-
where S is a comma-separated string of items keyword[:value].
Recognized keywords (possibly with value) are:
ioport:addr, noreset, nosync:x, period:ns, disconnect:x,
debug:x, proc:x.
For the function of these parameters, see the kernel source file
drivers/scsi/in2000.c.
- NCR5380 and NCR53C400 configuration
-
The boot argument is of the form
ncr5380=iobase,irq,dma
-
or
ncr53c400=iobase,irq
-
If the card doesn't use interrupts, then an IRQ value of 255 (0xff) will
disable interrupts.
An IRQ value of 254 means to autoprobe.
More details can be found in the file
Documentation/scsi/g_NCR5380.txt
(or
drivers/scsi/README.g_NCR5380
for older kernels) in the Linux kernel source.
- NCR53C8xx configuration
-
Syntax:
ncr53c8xx=S
-
where S is a comma-separated string of items keyword:value.
Recognized keywords are: mpar (master_parity), spar (scsi_parity),
disc (disconnection), specf (special_features), ultra (ultra_scsi),
fsn (force_sync_nego), tags (default_tags), sync (default_sync),
verb (verbose), debug (debug), burst (burst_max).
For the function of the assigned values, see the kernel source file
drivers/scsi/ncr53c8xx.c.
- NCR53c406a configuration
-
Syntax:
ncr53c406a=iobase[,irq[,fastpio]]
-
Specify irq = 0 for noninterrupt driven mode.
Set fastpio = 1 for fast pio mode, 0 for slow mode.
- Pro Audio Spectrum configuration
-
The PAS16 uses a NC5380 SCSI chip, and newer models support
jumperless configuration.
The boot argument is of the form:
pas16=iobase,irq
-
The only difference is that you can specify an IRQ value of 255, which
will tell the driver to work without using interrupts, albeit at a
performance loss.
The iobase is usually 0x388.
- Seagate ST-0x configuration
-
If your card is not detected at boot time,
you will then have to use a boot argument of the form:
st0x=mem_base,irq
-
The
mem_base
value is the value of the memory-mapped I/O region that
the card uses.
This will usually be one of the following values:
0xc8000, 0xca000, 0xcc000, 0xce000, 0xdc000, 0xde000.
- Trantor T128 configuration
-
These cards are also based on the NCR5380 chip, and accept the
following options:
t128=mem_base,irq
-
The valid values for
mem_base
are as follows: 0xcc000, 0xc8000, 0xdc000, 0xd8000.
- UltraStor 14F/34F configuration
-
The default list of I/O ports to be probed can be changed by
eata=iobase,iobase,....
- WD7000 configuration
-
Syntax:
wd7000=irq,dma,iobase
- Commodore Amiga A2091/590 SCSI controller configuration
-
Syntax:
wd33c93=S
-
where S is a comma-separated string of options.
Recognized options are
nosync:bitmask, nodma:x, period:ns, disconnect:x, debug:x,
clock:x, next.
For details, see the kernel source file
drivers/scsi/wd33c93.c.
Hard disks
- IDE Disk/CD-ROM Driver Parameters
-
The IDE driver accepts a number of parameters, which range from disk
geometry specifications, to support for broken controller chips.
Drive-specific options are specified by using 'hdX=' with X in 'a'-'h'.
Non-drive-specific options are specified with the prefix 'hd='.
Note that using a drive-specific prefix for a non-drive-specific option
will still work, and the option will just be applied as expected.
Also note that 'hd=' can be used to refer to the next unspecified
drive in the (a, ..., h) sequence.
For the following discussions,
the 'hd=' option will be cited for brevity.
See the file
Documentation/ide.txt
(or
drivers/block/README.ide
for older kernels) in the Linux kernel source for more details.
- The 'hd=cyls,heads,sects[,wpcom[,irq]]' options
-
These options are used to specify the physical geometry of the disk.
Only the first three values are required.
The cylinder/head/sectors
values will be those used by fdisk.
The write precompensation value
is ignored for IDE disks.
The IRQ value specified will be the IRQ
used for the interface that the drive resides on, and is not really a
drive-specific parameter.
- The 'hd=serialize' option
-
The dual IDE interface CMD-640 chip is broken as designed such that
when drives on the secondary interface are used at the same time as
drives on the primary interface, it will corrupt your data.
Using this
option tells the driver to make sure that both interfaces are never
used at the same time.
- The 'hd=dtc2278' option
-
This option tells the driver that you have a DTC-2278D IDE interface.
The driver then tries to do DTC-specific operations to enable the
second interface and to enable faster transfer modes.
- The 'hd=noprobe' option
-
Do not probe for this drive.
For example,
hdb=noprobe hdb=1166,7,17
-
would disable the probe, but still specify the drive geometry so
that it would be registered as a valid block device, and hence
usable.
- The 'hd=nowerr' option
-
Some drives apparently have the
WRERR_STAT
bit stuck on permanently.
This enables a work-around for these broken devices.
- The 'hd=cdrom' option
-
This tells the IDE driver that there is an ATAPI compatible CD-ROM
attached in place of a normal IDE hard disk.
In most cases the CD-ROM
is identified automatically, but if it isn't then this may help.
- Standard ST-506 Disk Driver Options ('hd=')
-
The standard disk driver can accept geometry arguments for the disks
similar to the IDE driver.
Note however that it expects only three
values (C/H/S); any more or any less and it will silently ignore you.
Also, it accepts only 'hd=' as an argument, that is, 'hda='
and so on are not valid here.
The format is as follows:
hd=cyls,heads,sects
-
If there are two disks installed, the above is repeated with the
geometry parameters of the second disk.
- XT Disk Driver Options ('xd=')
-
If you are unfortunate enough to be using one of these old 8-bit cards
that move data at a whopping 125kB/s, then here is the scoop.
If the card is not recognized,
you will have to use a boot argument of the form:
xd=type,irq,iobase,dma_chan
-
The type value specifies the particular manufacturer of the card,
overriding autodetection.
For the types to use, consult the
drivers/block/xd.c
source file of the kernel you are using.
The type is an index in the list
xd_sigs
and in the course of time
types have been added to or deleted from the middle of the list,
changing all type numbers.
Today (Linux 2.5.0) the types are
0=generic; 1=DTC 5150cx; 2,3=DTC 5150x; 4,5=Western Digital;
6,7,8=Seagate; 9=Omti; 10=XEBEC, and where here several types are
given with the same designation, they are equivalent.
The xd_setup() function does no checking on the values, and assumes
that you entered all four values.
Don't disappoint it.
Here is an
example usage for a WD1002 controller with the BIOS disabled/removed,
using the 'default' XT controller parameters:
xd=2,5,0x320,3
- Syquest's EZ* removable disks
-
Syntax:
ez=iobase[,irq[,rep[,nybble]]]
IBM MCA bus devices
See also the kernel source file
Documentation/mca.txt.
- PS/2 ESDI hard disks
-
It is possible to specify the desired geometry at boot time:
ed=cyls,heads,sectors.
-
For a ThinkPad-720, add the option
tp720=1.
- IBM Microchannel SCSI Subsystem configuration
-
Syntax:
ibmmcascsi=N
-
where N is the
pun
(SCSI ID) of the subsystem.
- The Aztech Interface
-
The syntax for this type of card is:
aztcd=iobase[,magic_number]
-
If you set the magic_number to 0x79, then the driver will try and run
anyway in the event of an unknown firmware version.
All other values
are ignored.
- Parallel port CD-ROM drives
-
Syntax:
pcd.driveN=prt,pro,uni,mod,slv,dly
pcd.nice=nice
-
where 'port' is the base address, 'pro' is the protocol number, 'uni'
is the unit selector (for chained devices), 'mod' is the mode (or -1
to choose the best automatically), 'slv' is 1 if it should be a slave,
and 'dly' is a small integer for slowing down port accesses.
The 'nice' parameter controls the driver's use of idle CPU time, at the
expense of some speed.
- The CDU-31A and CDU-33A Sony Interface
-
This CD-ROM interface is found on some of the Pro Audio Spectrum sound
cards, and other Sony supplied interface cards.
The syntax is as follows:
cdu31a=iobase,[irq[,is_pas_card]]
-
Specifying an IRQ value of zero tells the driver that hardware
interrupts aren't supported (as on some PAS cards).
If your card
supports interrupts, you should use them as it cuts down on the CPU
usage of the driver.
The
is_pas_card
should be entered as 'PAS' if using a Pro Audio Spectrum card,
and otherwise it should not be specified at all.
- The CDU-535 Sony Interface
-
The syntax for this CD-ROM interface is:
sonycd535=iobase[,irq]
-
A zero can be used for the I/O base as a 'placeholder' if one wishes
to specify an IRQ value.
- The GoldStar Interface
-
The syntax for this CD-ROM interface is:
gscd=iobase
- The ISP16 CD-ROM Interface
-
Syntax:
isp16=[iobase[,irq[,dma[,type]]]]
-
(Three integers and a string.)
If the type is given as 'noisp16',
the interface will not be configured.
Other recognized types
are: 'Sanyo", 'Sony', 'Panasonic' and 'Mitsumi'.
- The Mitsumi Standard Interface
-
The syntax for this CD-ROM interface is:
mcd=iobase,[irq[,wait_value]]
-
The
wait_value
is used as an internal timeout value for people who are
having problems with their drive, and may or may not be implemented
depending on a compile-time #define.
The Mitsumi FX400 is an IDE/ATAPI CD-ROM player and does not use
the mcd driver.
- The Mitsumi XA/MultiSession Interface
-
This is for the same hardware as above, but the driver has extended features.
Syntax:
mcdx=iobase[,irq]
- The Optics Storage Interface
-
The syntax for this type of card is:
optcd=iobase
- The Phillips CM206 Interface
-
The syntax for this type of card is:
cm206=[iobase][,irq]
-
The driver assumes numbers between 3 and 11 are IRQ values, and
numbers between 0x300 and 0x370 are I/O ports, so you can specify one,
or both numbers, in any order.
It also accepts 'cm206=auto' to enable
autoprobing.
- The Sanyo Interface
-
The syntax for this type of card is:
sjcd=iobase[,irq[,dma_channel]]
- The SoundBlaster Pro Interface
-
The syntax for this type of card is:
sbpcd=iobase,type
-
where type is one of the following (case sensitive) strings:
'SoundBlaster', 'LaserMate', or 'SPEA'.
The I/O base is that of the
CD-ROM interface, and not that of the sound portion of the card.
Ethernet devices
Different drivers make use of different parameters, but they all at
least share having an IRQ, an I/O port base value, and a name.
In its most generic form, it looks something like this:
ether=irq,iobase[,param_1[,...param_8]],name
The first nonnumeric argument is taken as the name.
The param_n values (if applicable) usually have different meanings for each
different card/driver.
Typical param_n values are used to specify
things like shared memory address, interface selection, DMA channel
and the like.
The most common use of this parameter is to force probing for a second
ethercard, as the default is to probe only for one.
This can be accomplished with a simple:
ether=0,0,eth1
Note that the values of zero for the IRQ and I/O base in the above
example tell the driver(s) to autoprobe.
The Ethernet-HowTo has extensive documentation on using multiple
cards and on the card/driver-specific implementation
of the param_n values where used.
Interested readers should refer to
the section in that document on their particular card.
The floppy disk driver
There are many floppy driver options, and they are all listed in
Documentation/floppy.txt
(or
drivers/block/README.fd
for older kernels) in the Linux kernel source.
This information is taken directly
from that file.
- floppy=mask,allowed_drive_mask
-
Sets the bit mask of allowed drives to mask.
By default, only units 0
and 1 of each floppy controller are allowed.
This is done because
certain nonstandard hardware (ASUS PCI motherboards) mess up the
keyboard when accessing units 2 or 3.
This option is somewhat
obsoleted by the cmos option.
- floppy=all_drives
-
Sets the bit mask of allowed drives to all drives.
Use this if you have
more than two drives connected to a floppy controller.
- floppy=asus_pci
-
Sets the bit mask to allow only units 0 and 1.
(The default)
- floppy=daring
-
Tells the floppy driver that you have a well behaved floppy
controller.
This allows more efficient and smoother operation, but
may fail on certain controllers.
This may speed up certain operations.
- floppy=0,daring
-
Tells the floppy driver that your floppy controller should be used
with caution.
- floppy=one_fdc
-
Tells the floppy driver that you have only floppy controller (default)
- floppy=two_fdc or floppy=address,two_fdc
-
Tells the floppy driver that you have two floppy controllers.
The second floppy controller is assumed to be at address.
If address is
not given, 0x370 is assumed.
- floppy=thinkpad
-
Tells the floppy driver that you have a Thinkpad.
Thinkpads use an
inverted convention for the disk change line.
- floppy=0,thinkpad
-
Tells the floppy driver that you don't have a Thinkpad.
- floppy=drive,type,cmos
-
Sets the cmos type of drive to type.
Additionally, this drive is
allowed in the bit mask.
This is useful if you have more than two
floppy drives (only two can be described in the physical cmos), or if
your BIOS uses nonstandard CMOS types.
Setting the CMOS to 0 for the
first two drives (default) makes the floppy driver read the physical
cmos for those drives.
- floppy=unexpected_interrupts
-
Print a warning message when an unexpected interrupt is received
(default behavior)
- floppy=no_unexpected_interrupts or floppy=L40SX
-
Don't print a message when an unexpected interrupt is received.
This is needed on IBM L40SX laptops in certain video modes.
(There seems to
be an interaction between video and floppy.
The unexpected interrupts
only affect performance, and can safely be ignored.)
The sound driver
The sound driver can also accept boot arguments to override the compiled in
values.
This is not recommended, as it is rather complex.
It is described in the Linux kernel source file
Documentation/sound/oss/README.OSS
(drivers/sound/Readme.linux
in older kernel versions).
It accepts
a boot argument of the form:
sound=device1[,device2[,device3...[,device10]]]
-
where each deviceN value is of the following format 0xTaaaId and the
bytes are used as follows:
T - device type: 1=FM, 2=SB, 3=PAS, 4=GUS, 5=MPU401, 6=SB16,
7=SB16-MPU401
aaa - I/O address in hex.
I - interrupt line in hex (i.e 10=a, 11=b, ...)
d - DMA channel.
As you can see it gets pretty messy, and you are better off to compile
in your own personal values as recommended.
Using a boot argument of
'sound=0' will disable the sound driver entirely.
ISDN drivers
- The ICN ISDN driver
-
Syntax:
icn=iobase,membase,icn_id1,icn_id2
-
where icn_id1,icn_id2 are two strings used to identify the
card in kernel messages.
- The PCBIT ISDN driver
-
Syntax:
pcbit=membase1,irq1[,membase2,irq2]
-
where membaseN is the shared memory base of the N'th card, and irqN is
the interrupt setting of the N'th card.
The default is IRQ 5 and
membase 0xD0000.
- The Teles ISDN driver
-
Syntax:
teles=iobase,irq,membase,protocol,teles_id
-
where iobase is the I/O port address of the card, membase is the
shared memory base address of the card, irq is the interrupt channel
the card uses, and teles_id is the unique ASCII string identifier.
Serial port drivers
- The RISCom/8 Multiport Serial Driver ('riscom8=')
-
Syntax:
riscom=iobase1[,iobase2[,iobase3[,iobase4]]]
-
More details can be found in the kernel source file
Documentation/riscom8.txt.
- The DigiBoard Driver ('digi=')
-
If this option is used, it should have precisely six parameters.
Syntax:
digi=status,type,altpin,numports,iobase,membase
-
The parameters maybe given as integers, or as strings.
If strings are used, then iobase and membase should be given
in hexadecimal.
The integer arguments (fewer may be given) are in order:
status (Enable(1) or Disable(0) this card),
type (PC/Xi(0), PC/Xe(1), PC/Xeve(2), PC/Xem(3)),
altpin (Enable(1) or Disable(0) alternate pin arrangement),
numports (number of ports on this card),
iobase (I/O Port where card is configured (in HEX)),
membase (base of memory window (in HEX)).
Thus, the following two boot prompt arguments are equivalent:
digi=E,PC/Xi,D,16,200,D0000
digi=1,0,0,16,0x200,851968
-
More details can be found in the kernel source file
Documentation/digiboard.txt.
- The Baycom Serial/Parallel Radio Modem
-
Syntax:
baycom=iobase,irq,modem
-
There are precisely 3 parameters; for several cards, give
several 'baycom=' commands.
The modem parameter is a string
that can take one of the values ser12, ser12*, par96, par96*.
Here the * denotes that software DCD is to be used, and
ser12/par96 chooses between the supported modem types.
For more details, see the file
Documentation/networking/baycom.txt
(or
drivers/net/README.baycom
for older kernels) in the Linux kernel source.
- Soundcard radio modem driver
-
Syntax:
soundmodem=iobase,irq,dma[,dma2[,serio[,pario]]],0,mode
-
All parameters except the last are integers;
the dummy 0 is required because of a bug in the setup code.
The mode parameter is a string with syntax hw:modem,
where hw is one of sbc, wss, or wssfdx, and modem is one of
afsk1200 or fsk9600.
The line printer driver
- 'lp='
-
Syntax:
lp=0
lp=auto
lp=reset
lp=port[,port...]
-
You can tell the printer driver what ports to use and what ports not
to use.
The latter comes in handy if you don't want the printer driver
to claim all available parallel ports, so that other drivers
(e.g., PLIP, PPA) can use them instead.
The format of the argument is multiple port names.
For example,
lp=none,parport0 would use the first parallel port for lp1, and
disable lp0.
To disable the printer driver entirely, one can use
lp=0.
- WDT500/501 driver
-
Syntax:
wdt=io,irq
Mouse drivers
- 'bmouse=irq'
-
The busmouse driver accepts only one parameter, that being the
hardware IRQ value to be used.
- 'msmouse=irq'
-
And precisely the same is true for the msmouse driver.
- ATARI mouse setup
-
Syntax:
atamouse=threshold[,y-threshold]
-
If only one argument is given, it is used for both
x-threshold and y-threshold.
Otherwise, the first argument
is the x-threshold, and the second the y-threshold.
These values must lie between 1 and 20 (inclusive); the default is 2.
Video hardware
- 'no-scroll'
-
This option tells the console driver not to use hardware scroll
(where a scroll is effected by moving the screen origin in video
memory, instead of moving the data).
It is required by certain
Braille machines.
SEE ALSO
klogd(8),
mount(8)
Large parts of this man page have been derived from the
Boot Parameter HOWTO (version 1.0.1) written by Paul Gortmaker.
More information may be found in this (or a more recent) HOWTO.
An up-to-date source of information is the kernel source file
Documentation/kernel-parameters.txt.
Index
- NAME
-
- DESCRIPTION
-
- The argument list
-
- General non-device-specific boot arguments
-
- Boot arguments for use by kernel developers
-
- Boot arguments for ramdisk use
-
- Boot arguments for SCSI devices
-
- Hard disks
-
- IBM MCA bus devices
-
- Ethernet devices
-
- The floppy disk driver
-
- The sound driver
-
- ISDN drivers
-
- Serial port drivers
-
- The line printer driver
-
- Mouse drivers
-
- Video hardware
-
- SEE ALSO
-
This document was created by
man2html,
using the manual pages.
Time: 02:55:20 GMT, September 18, 2014


Far far away, behind the word mountains, far from the countries Vokalia and Consonantia, there live the blind texts. Separated they live in Bookmarksgrove right at the coast of the Semantics, a large language ocean.
Far far away, behind the word mountains, far from the countries Vokalia and Consonantia, there live the blind texts. Separated they live in Bookmarksgrove right at the coast of the Semantics, a large language ocean.
Far far away, behind the word mountains, far from the countries Vokalia and Consonantia, there live the blind texts. Separated they live in Bookmarksgrove right at the coast of the Semantics, a large language ocean.
People Says
Address: 98 West 21th Street, Suite 721 New York NY 10016


four drinks, a million
reasons
"just love yourself and you're set." - lady gaga
lady gaga and starbucks share a mission:to build a kinder,braver world.through the born this way foundation,
lady gaga has inspired hers fans to embrace kindness in theirs communities-online and
in the world.with your help,we can empower young people to spread more kindness.
learn more


About
BiwaScheme is a Scheme interpreter written in JavaScript.
Example
<script src="lib/biwascheme.js"> (display "hello, world!") </script>
Try it now: BiwaScheme REPL
Demo
Features
- Most syntax/base library of R6RS (see Status)
- Functions for web application (Ajax, DOM manipulation, etc.)
- Calling JavaScript functions from Scheme
- Comprehensive unit test
- Tiny interpreter debugger
Links
Licence
- BiwaScheme: MIT License
- BiwaScheme Logo (by Jakub Jankiewicz): Creative Commons Attribution 3.0
Contact
see Development for ITS and mailing lists.
Yutaka HARA (yutaka.hara.gmail.com)
http://route477.net/