--- title: "SPRING POETRY RECEPTION" date: "2000-01-01 19:04:11 -06:00" categories: - events - spring subtitle: "" layout: "events" event-image: "poetry-walk.jpg" event-dates: "THURSDAY, APRIL 9 @ 5:30-6:30PM" event-location: "Red Butte Garden Visitor Center" button-type: "register" tickets-link: "https://55218.blackbaudhosting.com/55218/Spring-Poetry-Reception" registration-info: "N/A" instructor-info: "N/A" member-cost: "Free" public-cost: "Garden Admission" event-notes: "cancelled" tickets-button: "#" published: false ---
And don't forget to visit the Garden to see all of the winning poems on display as part of our Garden Poetry Walk during the month of April and May to celebrate National Poetry Month!
Poets in attendance:
And don't forget to visit the Garden to see all the winning poems on display as part of our Garden Poetry Walk during the month of April to celebrate National Poetry Month!
REGISTRATION REQUIRED


THE BIG LEBOWSKI (1998) Reviewed by Chuck Dowling Copyright 1998 - The Jacksonville Film Journal URL:http://users.southeast.net/~chuckd21/
Cast: Jeff Bridges, John Goodman, Julianne Moore, Steve Buscemi, David Huddleston, John Turturro, Sam Elliott, Peter Stormare, Flea, Ben Gazarra, Phillip Seymore Hoffman, Tara Reid Written by: Joel and Ethan Coen Directed by: Joel Coen Running Time: 119 minutes My Rating: ***** out of *****
After critic Gene Siskel saw the Coen brothers' 1996 film "Fargo" he remarked that he would not see a better picture that year. I thought that was a pretty bold statement considering how early in the year the film was released. Well, here it is the first week of March, the Coen brothers have released their latest film "The Big Lebowski," and I have to say, in the words of Gene Siskel: I will not see a better film this year.
To describe the plot of "The Big Lebowski" would be pointless, as it's just not something able to be described. Jeff Bridges plays Jeff Lebowski aka "The Dude," a hippie who gets mixed up in a case of mistaken identity with a millionaire (David Huddleston), also named Jeff Lebowski. What follows includes kidnapping, ransom, auto theft, bowling, musical dance numbers, former german rock stars, bad pornography, and more comedy than ten movies usually have.
The Coen brothers, responsible for such wondeful motion pictures as "Fargo," "The Hudsucker Proxy," "Raising Arizona," "Barton Fink," and "Blood Simple" always succeed in creating their own little universe on the movie screen, and with "The Big Lebowski" they certainly succeed again. How they have managed to maintain their creative filmmaking and storytelling abilities, and now manage to TOP all their previous works is beyond me. But I am so glad that they have.
I usually try to avoid grand, sweeping statements when I write reviews, but in the case of "The Big Lebowski" I just can't help it.  For the entire running time of the film, I was constantly laughing. Yes, that's right. I laughed for 119 minutes. Never once during the 1am screening I attended did I glance at my watch, and not once did I yawn or take my eyes off the screen. While the film ran I never wanted it to end, and when it was over I wanted them to run it again. If I was to give out the Oscars, acting awards would go to all involved (particularly Bridges, Goodman, and Buscemi, who's dialogue and chemistry with one another is fantastic), along with awards for writing, directing, production design, music... everything. And a note to the Coen brothers: I want a sequel. I want more of these characters, and I want it as soon as possible.
Now I realize that comedy is a tricky thing, and that everyone has a slightly different sense of humor. And the comedy in "The Big Lebowski" isn't necessarily jokes, set-ups, and punch lines. It's dialogue and attitudes, much like the comedic elements of "Pulp Fiction".
Certainly some of you will see the film and afterwards think that I am completely insane. So here's a little test to help you see if you'll go along with the comedy of the film. In the early seconds of the film, The Dude writes a check for a ridiculously low amount of money, something like $.68. I found that to be absolutely hilarious. If you would too, then "The Big Lebowski" is right up your alley. It's the best film of the year so far, and I seriously doubt there will be anything better. [R]
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


The Mechanics of Nomenclators
Number of ways a message can be enciphered: Infinite
Ease of encryption: Low, almost to the point of unfeasability
Security: High
Nomenclators worked on the same basic principle as monosubstitution ciphers. However, rather than acting upon letters, nomenclators act on words and even phrases. For instance, the message "Attack at dawn" could be enciphered as "λ ζ ψ".
As might be expected, keys for nomenclators were nearly impossible to memorize, and thus nomenclators often necessitated the use of physical dictionaries which were at risk of being captured by the enemy.


I am...
A software developer passionate about modern technologies and standards. I proudly work at Koombea. I'm a cat-loving engineer and have many hobbies.
I like...
- Drones (I like to build them)
- DIY Electronics
- Fixing stuff with software
- Gaming
- Engineering
- Sporty Cars
Feel free to reach out:


{% extends "base.html" %} {% block extra_head %}
The idea behind linkypedia is to help cultural heritage institutions that are putting content online to see how wikipedians are citing and annotating their stuff. Many libraries, museums and archives have embraced the new publishing medium of the Web by digitizing items and putting them online. Traditionally these items have been organized and annotated by catalogers, archivists and curators around the world.
linkypedia aims to help reveal and foster the connections between these digital curation communities. The idea being that if organizations can see how their web content is being used in Wikipedia, they will be encouraged and emboldened to do more. In addition linkypedia can also help cultural heritage institutions get involved in content creation on Wikipedia itself. Wikipedia encourages the participation of librarians, archivists and museum curators--and linkypedia can help those working at cultural heritage institutions get to work.
If you are interested in the technical details, linkypedia is a Python/Django application that uses the External Links Search built into Wikipedia to get a list of wikipedia pages and the relevant links. The project also uses the lovely Wikipedia API to fetch relevant details about the wikipedia page. The source code is available on GitHub.


Form Wizard
Nostrud exercitation commodo consequat.
1
2
Choose A Location
United States
United Kingdom
Viet Nam
7:00am - 18:00pm
9:00am - 21:00pm
10:00am - 22:00pm
12:00am - 24:00pm
3
Full Name:
Benjamin Harrison
Phone:
+1<PHONE_NUMBER>
Email:
<EMAIL_ADDRESS>Travel Location:
Tokyo Japan
Date:
15 Jan, 2018
Time:
7:00am - 18:00pm


The congress.datalog.builtin
Module¶
-
class
congress.datalog.builtin.
CongressBuiltinCategoryMap
(start_builtin_map)¶ Bases:
object
-
add_map
(newmap)¶
-
builtin
(table)¶ Return a CongressBuiltinPred for given Tablename or None.
-
builtin_is_registered
(predtotest)¶ Given a CongressBuiltinPred, check if it has been registered.
-
delete_all_in_category
(category)¶
-
delete_builtin
(category, name, inputs)¶
-
delete_category
(category)¶
-
delete_from_category
(category, pred)¶
-
delete_map
(newmap)¶
-
dict_predtriple_to_pred
(predtriple)¶
-
exists_category
(category)¶
-
get_category_name
(predname, predinputs)¶
-
insert_category
(category)¶
-
insert_to_category
(category, pred)¶
-
is_builtin
(table, arity=None)¶ Given a Tablename and arity, check if it is a builtin.
-
list_available_builtins
()¶ Print out the list of builtins, by category.
-
mapequal
(othercbc)¶
-
sync_with_predlist
(predname, pred, category, operation)¶
-
-
class
congress.datalog.builtin.
CongressBuiltinPred
(name, arglist, num_inputs, code)¶ Bases:
object
-
string_to_pred
(predstring)¶
-
-
class
congress.datalog.builtin.
DatetimeBuiltins
¶ Bases:
object
-
classmethod
datetime_equal
(x, y)¶
-
classmethod
datetime_greaterthan
(x, y)¶
-
classmethod
datetime_greaterthanequal
(x, y)¶
-
classmethod
datetime_lessthan
(x, y)¶
-
classmethod
datetime_lessthanequal
(x, y)¶
-
classmethod
datetime_minus
(x, y)¶
-
classmethod
datetime_plus
(x, y)¶
-
classmethod
datetime_to_seconds
(x)¶
-
classmethod
extract_date
(x)¶
-
classmethod
extract_time
(x)¶
-
classmethod
now
()¶
-
classmethod
pack_date
(year, month, day)¶
-
classmethod
pack_datetime
(year, month, day, hour, minute, second)¶
-
classmethod
pack_time
(hour, minute, second)¶
-
classmethod
to_datetime
(x)¶
-
classmethod
to_timedelta
(x)¶
-
classmethod
unpack_date
(x)¶
-
classmethod
unpack_datetime
(x)¶
-
classmethod
unpack_time
(x)¶
-
classmethod
-
class
congress.datalog.builtin.
NetworkAddressBuiltins
¶ Bases:
object
-
classmethod
ip_in_network
(ip, cidr)¶
-
classmethod
ips_equal
(ip1, ip2)¶
-
classmethod
ips_greaterthan
(ip1, ip2)¶
-
classmethod
ips_greaterthan_equal
(ip1, ip2)¶
-
classmethod
ips_lessthan
(ip1, ip2)¶
-
classmethod
ips_lessthan_equal
(ip1, ip2)¶
-
classmethod
networks_equal
(cidr1, cidr2)¶
-
classmethod
networks_overlap
(cidr1, cidr2)¶
-
classmethod


Chapter 21 A Mini-Exam Example
A common regret of students who failed exam PA is that they did not start doing practice exams soon enough. Here is a simple practice exam to help you to understand what concepts that you should focus on learning, to become familiar with the format, and to test your technical skills with R, RStudio, and MS Word.
21.1 Project Statement
ABC Health Insurance company is building a model to predict medical claims. Using only age
and sex
information from the prior year, build a model to predict claims for the next year.
21.1.1 Describe the data (1 point)
library(tidyverse)
data <- read_csv("C:/Users/sam.castillo/Desktop/R Manual Data/health_insurance.csv") %>%
select(age, sex, charges) %>% #put this into an r library
rename(claims = charges)
data %>% summary()
## age sex claims
## Min. :18.00 Length:1338 Min. : 1122
## 1st Qu.:27.00 Class :character 1st Qu.: 4740
## Median :39.00 Mode :character Median : 9382
## Mean :39.21 Mean :13270
## 3rd Qu.:51.00 3rd Qu.:16640
## Max. :64.00 Max. :63770
## [1] 1338 3
The data consists of 1,338 policies with age and sex information. The objective is to predict future claims.
21.1.2 Create a histogram of the claims and comment on the shape (1 point)
The distribution of claims is strictly positive and right skewed.
## `stat_bin()` using `bins = 30`. Pick better value with `binwidth`.
21.1.3 Fit a linear model (1 point)
21.1.4 Describe the relationship between age, sex, and claim costs (1 point)
We fit a linear model to the claim costs using age and sex as predictor variables. The coefficient of
age
is 258, indicating that the claim costs increase by $258 for every one-unit increase in the policyholder’s age. The cofficient of 1538 onsexmale
indicates that on average, men have $1538 higher claims than women do.
## (Intercept) age sexmale
## 2343.6249 258.8651 1538.8314
21.1.5 Write a summary of steps 1-4 in non-technical language (1 point)
ABC Health is interested in predicting the future claims for a group of policyholders. We began by collecting data on 1,538 policy holders which recorded their age, sex, and annual claims. We then created a histogram of the claim costs. A linear model which shows that claim costs increase as age increases, and are higher for men on average.


Edit/Update title
Some quick example text to build on the card title and make up the bulk of the card's content.
Card link Another link{% extends "base_generic.html" %} {% block title %}{% endblock %} {% block context %} {% load static %}
Some quick example text to build on the card title and make up the bulk of the card's content.
Card link Another link


Note
Click here to download the full example code
Variable Properties¶
This example shows step by step how to set up and run a model of a cooling planetesimal without using a parameters file. This example uses temperature dependent material properties in the mantle and reproduces the results of Murphy Quinlan et al. (2021).
As we’re setting this up step-by-step instead of using the pytesimal.quick_workflow module, we need to import a selection of modules:
import pytesimal.setup_functions
import pytesimal.load_plot_save
import pytesimal.numerical_methods
import pytesimal.analysis
import pytesimal.core_function
import pytesimal.mantle_properties
Instead of creating and loading a parameter file, we’re going to define variables here. The values match those of the constant thermal properties case in Murphy Quinlan et al. (2021):
timestep = 1E11 # s
r_planet = 250_000.0 # m
core_size_factor = 0.5 # fraction of r_planet
reg_fraction = 0.032 # fraction of r_planet
max_time = 400 # Myr
temp_core_melting = 1200.0 # K
core_cp = 850.0 # J/(kg K)
core_density = 7800.0 # kg/m^3
temp_init = 1600.0 # K
temp_surface = 250.0 # K
core_temp_init = 1600.0 # K
core_latent_heat = 270_000.0 # J/kg
kappa_reg = 5e-8 # m^2/s
dr = 1000.0 # m
The setup_functions.set_up() function creates empty arrays to be filled with resulting temperatures:
(r_core,
radii,
core_radii,
reg_thickness,
where_regolith,
times,
mantle_temperature_array,
core_temperature_array) = pytesimal.setup_functions.set_up(timestep,
r_planet,
core_size_factor,
reg_fraction,
max_time,
dr)
# We define an empty list of latent heat that will
# be filled as the core freezes
latent = []
Next, we instantiate the core object. This will keep track of the temperature of the core as the model runs, cooling as heat is extracted across the core-mantle boundary. This simple eutectic core model doesn’t track inner core growth, but this is still a required argument to allow for future incorporation of more complex core objects:
core_values = pytesimal.core_function.IsothermalEutecticCore(
initial_temperature=core_temp_init,
melting_temperature=temp_core_melting,
outer_r=r_core,
inner_r=0,
rho=core_density,
cp=core_cp,
core_latent_heat=core_latent_heat)
Then we define the mantle properties. We want to use temperature-dependent properties, so we need to specify this:
(mantle_conductivity,
mantle_heatcap,
mantle_density) = pytesimal.mantle_properties.set_up_mantle_properties(
cond_constant='n',
density_constant='n',
heat_cap_constant='n'
)
You can check (or change) the value of these properties after they’ve been set up using one of the MantleProperties methods:
print(f' Mantle conductivity {mantle_conductivity.getk()} W/(m K)')
Out:
Mantle conductivity 3.411005666195278 W/(m K)
When temperature dependent properties are used, temperature can be passed in as an argument to return the value at that temperature. The default temperature is 295 K, so if no temperature argument is passed, the function is evaluated at T=295.
We need to set up the boundary conditions for the mantle. For this example, we’re using fixed temperature boundary conditions at both the surface and the core-mantle boundary.
top_mantle_bc = pytesimal.numerical_methods.surface_dirichlet_bc
bottom_mantle_bc = pytesimal.numerical_methods.cmb_dirichlet_bc
# Now we let the temperature inside the planestesimal evolve. This is the
# slowest part of the code, because it has to iterate over all radii and
# time.
# This will take a minute or two!
# The mantle property objects are passed in in the same way as in the
# example with constant thermal properties.
(mantle_temperature_array,
core_temperature_array,
latent,
) = pytesimal.numerical_methods.discretisation(
core_values,
latent,
temp_init,
core_temp_init,
top_mantle_bc,
bottom_mantle_bc,
temp_surface,
mantle_temperature_array,
dr,
core_temperature_array,
timestep,
r_core,
radii,
times,
where_regolith,
kappa_reg,
mantle_conductivity,
mantle_heatcap,
mantle_density)
This function fills the empty arrays produced by setup_functions.set_up() with calculated temperatures for the mantle and core.
Now we can use the pytesimal.analysis module to find out more about the model run. We can check when the core was freezing, so we can compare this to the cooling history of meteorites and see whether they can be expected to record magnetic remnants of a core dynamo:
(core_frozen,
times_frozen,
time_core_frozen,
fully_frozen) = pytesimal.analysis.core_freezing(core_temperature_array,
max_time,
times,
latent,
temp_core_melting,
timestep)
Then, we can calculate arrays of cooling rates from the temperature arrays:
mantle_cooling_rates = pytesimal.analysis.cooling_rate(mantle_temperature_array,
timestep)
core_cooling_rates = pytesimal.analysis.cooling_rate(core_temperature_array,
timestep)
Meteorite data (the diameter of ‘cloudy-zone particles’) can be used to estimate the rate at which the meteorites cooled through a specific temperature (C. W. Yang et al., 1997). The analysis.cooling_rate_cloudyzone_diameter function calculates the cooling rate in K/Myr, while the analysis.cooling_rate_to_seconds function converts this to K/s which allows comparison to our result arrays.
d_im = 147 # cz diameter in nm
d_esq = 158 # cz diameter in nm
imilac_cooling_rate = pytesimal.analysis.cooling_rate_to_seconds(
pytesimal.analysis.cooling_rate_cloudyzone_diameter(d_im))
esquel_cooling_rate = pytesimal.analysis.cooling_rate_to_seconds(
pytesimal.analysis.cooling_rate_cloudyzone_diameter(d_esq))
We can use this cooling rate information to find out how deep within their parent bodies these meteorites originally formed, and when they passed through the temperature of tetrataenite formation (when magnetism can be recorded). The analysis.meteorite_depth_and_timing() function returns the source depth of the meteorite material in the parent body based on the metal cooling rates at 800 K (as a depth from surface in km and as a radial value from the center of the planet in m), the time that the meteorite cools through the tetrataenite formation temperature in comparison to the core crystallisation period, and a string defining this relation between paleomagnetism recording and dynamo activity:
(im_depth,
im_string_result,
im_time_core_frozen,
im_Time_of_Crossing,
im_Critical_Radius) = pytesimal.analysis.meteorite_depth_and_timing(
imilac_cooling_rate,
mantle_temperature_array,
mantle_cooling_rates,
radii,
r_planet,
core_size_factor,
time_core_frozen,
fully_frozen,
dr=1000,
)
(esq_depth,
esq_string_result,
esq_time_core_frozen,
esq_Time_of_Crossing,
esq_Critical_Radius) = pytesimal.analysis.meteorite_depth_and_timing(
esquel_cooling_rate,
mantle_temperature_array,
mantle_cooling_rates,
radii,
r_planet,
core_size_factor,
time_core_frozen,
fully_frozen,
dr=1000,
)
print(f"Imilac depth: {im_depth}; Imilac timing: {im_string_result}")
print(f"Esquel depth: {esq_depth}; Esquel timing: {esq_string_result}")
Out:
Imilac depth: 61.0; Imilac timing: Core has not started solidifying yet
Esquel depth: 68.0; Esquel timing: Core has started solidifying
If you need to save the meteorite results, they can be saved to a dictionary which can then be passed to the load_plot_save.save_params_and_results. This allows for any number of meteorites to be analysed and only the relevant data stored:
meteorite_results_dict = {'Esq results':
{'depth': esq_depth,
'text result': esq_string_result},
'Im results':
{'depth': im_depth,
'text result': im_string_result,
'critical radius': im_Critical_Radius}}
To get an overview of the cooling history of the body, it’s very useful to plot the temperatures and cooling rates as a heatmap through time. In order to plot the results, we need to define a figure height and width, then call load_plot_save.plot_temperature_history(), load_plot_save.plot_coolingrate_history() or load_plot_save.two_in_one(). These functions convert the cooling rate from K/timestep to K/Myr to make the results more human-readable.
fig_w = 6
fig_h = 9
pytesimal.load_plot_save.two_in_one(
fig_w,
fig_h,
mantle_temperature_array,
core_temperature_array,
mantle_cooling_rates,
core_cooling_rates, )
There are a few formats or ways to save the results. The temperature and cooling rate arrays can be saved as compressed .npz arrays, to be loaded at a later time and replotted/new meteorite formation depths calculated etc. The input parameters can be saved as a .json file, which allows the run to be documented and provides all the metadata needed to reproduce the results. For either of these, a results folder and results filename is needed. The folder can be defined relative to the working directory, or with an absolute path. An absolute path usually results in less confusion!
# define folder and check it exists:
folder = 'workflow'
pytesimal.load_plot_save.check_folder_exists(folder)
# define a results filename prefix:
result_filename = 'variable_workflow_results'
The result arrays can now be saved:
pytesimal.load_plot_save.save_result_arrays(result_filename,
folder,
mantle_temperature_array,
core_temperature_array,
mantle_cooling_rates,
core_cooling_rates)
In order to save the result parameter file, we also need to define a run_ID, a descriptive string to identify the model run, and clarify whether we used constant or variable thermal properties:
run_ID = 'Example run with default variable properties'
cond_constant = 'n'
density_constant = 'n'
heat_cap_constant = 'n'
pytesimal.load_plot_save.save_params_and_results(
result_filename, run_ID, folder, timestep, r_planet, core_size_factor,
reg_fraction, max_time, temp_core_melting, mantle_heatcap.getcp(),
mantle_density.getrho(), mantle_conductivity.getk(), core_cp, core_density,
temp_init, temp_surface, core_temp_init, core_latent_heat,
kappa_reg, dr, cond_constant, density_constant,
heat_cap_constant, time_core_frozen, fully_frozen,
meteorite_results=meteorite_results_dict)
This results file can then be loaded as a parameter file if you want to repeat the same set up.
Total running time of the script: ( 3 minutes 37.785 seconds)


OpenSolaris
Collectives
Discussions
Documentation
Download
Source Browser
Free CD
Log-in
|
en
Community Group arc
:
ARC Policies
>
Recommended Installation Locations for Solaris-compatible Software Components
Top Menu
Show
:
Comments
Attachments
History
Information
Print
:
Print
Print preview
Export as PDF
Export as RTF
Export as HTML
Export as XAR
Wiki code for
Recommended Installation Locations for Solaris-compatible Software Components
Hide Line numbers
1: ||**Table of Contents**|**Overview**|**BestPractice Synopsis** 2: | 3: [[Applicability>>#Applicability]] 4: [[Background>>#Background]] 5: [[Policy>>#Policy]] 6: [[Exemptions>>#Exemptions]] 7: [[Appeals>>#Appeals]] 8: [[Interface>>#Interface]] 9: [[CaseHistory>>#CaseHistory]] 10: [[ManPages>>#ManPages]] 11: [[References>>#References]] 12: ||Category|Software 13: |Owner|SAC 14: |Author|PSARC 15: |Changes|PSARC 16: |Authority|SAC 17: |Policy Version|1.2 18: |Status|Approved March 23, 1999 19: |Last Reviewed|March, 1999 20: |Effective|Solaris 2.x 21: | This document is a summary of recommendations for installation locations of package objects on Foundation Solaris 2.x. 22: | | 23: ---- 24: == Applicability 25: ---- 26: == Background 27: ---- 28: == BestPractice 29: * **Applies to** All software installed on Solaris 30: * **Authority** SAC 31: * **Approval** PSARC 1998/374 1998/09/30 32: * **Effective** Solaris 2.x 33: * **Policy** This project documents what the ARCs have approved for standard directories in the Solaris Foundation filesystems and what can be found in the System V ABI documentation. It is assumed that the information this project provides will be publically posted (perhaps to enhance the filesystem(5) manpage) and used by the ARCs and SCs in guiding project teams. 34: * **Details** The following table is a summary of recommendations for installation locations of package objects on //Foundation Solaris 2.x//. 35: The //Installation Location for Bundled Foundation Solaris software// column contains the locations by which Solaris diversity can be delivered either as add-on application software or as add-on system modules. 36: //Platform// in the definitions below refers to the Instruction Set Architecture (ISA) or processor type (uname -p). 37: //Platform-specific// in the definitions below generally refers to the specific hardware implementation (uname -i). 38: // System Software// is defined to be software required for initial installation and/or booting of a system and to provide a sufficient execution environment for additional software. 39: // Add On Software// is all other software not required at initial system installation or boot to provide a fully operational system environment. For additional details on Solaris directory structure and filesystem organization, see filesystem(5). 40: |= Type of File |= Installation Location for 41: |= Bundled Foundation Solaris software|= Add-on system software or applications 42: | Platform dependent [[[1]>>#f1]] modules required for boot. (see kernel(1M)) |/kernel/|/kernel/ 43: (system software only) 44: | SPARC 64-bit 45: Platform dependent 46: modules required for boot 47: [Solaris 2.7 and beyond] |/kernel///subsystem///sparcv9/|/kernel///subsystem///sparcv9/ 48: (system software only) 49: | Intel IA64 64-bit 50: Platform dependent 51: modules required for boot 52: [Solaris future] |/kernel///subsystem///ia64/ 53: (NOTE: "ia64" is an example; 54: the actual name may be different) |/kernel///subsystem///ia64/ (system software only) 55: (NOTE: "ia64" is an example; 56: the actual name may be different) 57: | Platform dependent 58: configuration files for 59: the system node and 60: not shared between 61: systems |/etc/|/etc/opt/$PKG/ 62: | Platform dependent 63: subsystem configuration 64: files for the system node 65: and not shared between 66: systems |/etc///subsystem///|/etc/opt/$PKG/ 67: | non-permanent temporary 68: files created by the system |/etc/volatile/|/etc/volatile/ (system software only) 69: | Essential executables used 70: in the booting process and 71: in manual system recovery. 72: The full complement of 73: utilities is available only 74: after /usr is mounted. |/sbin/|/opt/$PKG/sbin/ 75: Not Applicable since one 76: cannot assume that /opt 77: is part of the root 78: filesystem. 79: | non-permanent (contents 80: cleared during system 81: boot) temporary files 82: created by applications |/tmp/|/tmp/ 83: | This directory contains 84: files installed by 85: add-on software 86: application packages | Should not be Applicable |/opt/ 87: | system or node specific changing files (logs, databases) |/var/|/var/opt/$PKG/ 88: | status log files produced by 89: software management 90: functions and/or 91: applications. E.g., log files 92: produced for product installation. |/var/sadm/system/logs/|/var/sadm/system/logs/ 93: | files that vary in size or 94: presence during normal 95: system operations created 96: by application packages | Not Applicable |/var/opt/ 97: | files that vary in size or 98: presence during normal 99: system operations created 100: by applications. Contents 101: are preserved across the 102: system boot operation. |/var/tmp/|/var/tmp/ 103: | Platform-specific[[[2]>>#f2]] modules required for boot |/platform/`uname -i`/kernel/[[[3]>>#f3]]|/platform/`uname -i`/kernel/ 104: (system software only) 105: | SPARC 64-bit 106: Platform-specific 107: modules required for boot 108: [Solaris 2.7 and beyond] |/platform/`uname -i`/kernel///subsystem///sparcv9/| Not Applicable 109: | Intel IA64 64-bit 110: Platform dependent 111: modules required for boot 112: [Solaris future] |/platform/`uname -i`/kernel///subsystem///ia64/ 113: (NOTE: "ia64" is an example; 114: the actual name may be different) | Not Applicable 115: | Hardware class specific 116: modules required for boot |/platform/`uname -m`/kernel/|/platform/`uname -m`/kernel/ 117: (system software only) 118: | Platform-specific shared 119: objects required for boot |/platform/`uname -i`/lib/|/platform/`uname -i`/lib/ 120: (system software only) 121: | Platform-specific 122: administrative utilities 123: required for boot 124: |/platform/`uname -i`/sbin/|/platform/`uname -i`/sbin/ 125: (system software only) 126: | usr platform dependent 127: loadable modules |/usr/kernel/| Not Applicable 128: | usr platform-specific 129: modules |/usr/platform/`uname -i`/kernel/|/usr/platform/`uname -i`/kernel/ 130: (system software only) 131: | Platform-specific 132: daemon and shared 133: objects |/usr/platform/`uname -i`/lib/|/usr/platform/`uname -i`/lib/ 134: (system software only) 135: | SPARC 64-bit 136: Platform-specific 137: daemon and shared 138: objects 139: [Solaris 2.7 and beyond] |/usr/platform/`uname -i`/lib/sparcv9/|/usr/platform/`uname -i`/lib/sparcv9/ 140: (system software only) 141: | Intel IA64 64-bit 142: Platform-specific 143: daemon and shared 144: objects 145: [Solaris future] |/usr/platform/`uname -i`/lib/ia64/ (NOTE: "ia64" is an example; 146: the actual name may be different) |/usr/platform/`uname -i`/lib/ia64 147: (system software only) 148: (NOTE: "ia64" is an example; 149: the actual name may be different) 150: | Platform-specific System 151: administration utilities |/usr/platform/`uname -i`/sbin/|/usr/platform/`uname -i`/sbin/ 152: (system software only) 153: | Platform-specific System 154: (sys, vm) header files |/usr/platform/`uname -i`/include/|/usr/platform/`uname -i`/include/ 155: (system software only) 156: | Platform-specific System 157: manual pages for 158: documenting platform- 159: specific shared objects, 160: administration utilities, 161: configuration files, 162: special files/modules, 163: and header files |/usr/platform/`uname -i`/[s]man/ 164: /usr/platform/`uname -i`/[s]man/[s]man3x/ 165: /usr/platform/`uname -i`/[s]man/[s]man1m/ 166: /usr/platform/`uname -i`/[s]man/[s]man4/ 167: /usr/platform/`uname -i`/[s]man/[s]man7d/ 168: /usr/platform/`uname -i`/[s]man/[s]man9e/|/usr/platform/`uname -i`/[s]man 169: (system software only) 170: platform-specific shared objects 171: platform-specific utilities 172: platform-specific file formats 173: platform-specific special files 174: platform-specific device headers 175: | Platform dependent 176: user-invoked executables; 177: commands expected to be 178: run users as part of their 179: normal PATH. |/usr/bin/ 180: All user-level commands should be run out 181: of this directory. For executable that have to 182: be different on a 64-bit system than on a 183: 32-bit system, a wrapper that selects the 184: appropriate executable is placed here. 185: See isaexec(3C). |/opt/$PKG/bin/ 186: | SPARC 64-bit Platform 187: dependent user-invoked 188: executables that have to be 189: different on a 64-bit 190: system. 191: [Solaris 2.7 and beyond] |/usr/bin/sparcv9/ 192: see isaexec(3C). 193: Note that this directory shall not be part 194: of the user’s PATH, as the user should never 195: directly invoke an executable in this 196: directory; rather the identically-named 197: wrapper in /usr/bin is invoked and 198: that in turn invokes the executable in this 199: directory, when appropriate. |/opt/$PKG/bin/sparcv9/ 200: | Intel IA64 64-bit Platform 201: dependent user-invoked 202: executables that have to be 203: different on a 64-bit 204: system. 205: [Solaris future] |/usr/bin/ia64/ 206: see isaexec(3C) 207: (NOTE: "ia64" is an example; 208: the actual name may be different) 209: Note that this directory shall not be part 210: of the user’s PATH, as the user should never 211: directly invoke an executable in this 212: directory; rather the identically-named 213: wrapper in /usr/bin is invoked and 214: that in turn invokes the executable in this 215: directory, when appropriate. |/opt/$PKG/bin/ia64/ 216: (NOTE: "ia64" is an example; 217: the actual name may be different) 218: | Platform dependent 219: subsystem user-invoked 220: executables; commands 221: expected to be run users as 222: part of their normal PATH |/usr/bin///subsystem[[[4]>>#f4]]/// 223: see isaexec(3C). | /opt/$PKG/bin/ 224: | SPARC 64-bit Platform 225: dependent user-invoked 226: executables that have to be 227: different on a 64-bit 228: system. 229: [Solaris 2.7 and beyond] |/usr/bin///subsystem[[[4]>>#f4]]///sparcv9/ 230: see isaexec(3C) 231: Note that this directory shall not be part 232: of the user’s PATH, as the user should never 233: directly invoke an executable in this 234: directory; rather the identically-named 235: wrapper in /usr/bin is invoked and 236: that in turn invokes the executable in this 237: directory, when appropriate. |/opt/$PKG/bin/sparcv9/ 238: | Intel IA64 64-bit Platform 239: dependent user-invoked 240: executables that have to be 241: different on a 64-bit 242: system. 243: [Solaris future] | /usr/bin///subsystem[[[4]>>#f4]]///ia64/ 244: see isaexec(3C) 245: (NOTE: "ia64" is an example; 246: the actual name may be different) 247: Note that this directory shall not be part 248: of the user’s PATH, as the user should never 249: directly invoke an executable in this 250: directory; rather the identically-named 251: wrapper in /usr/bin is invoked and 252: that in turn invokes the executable in this 253: directory, when appropriate | /opt/$PKG/bin/ia64/ 254: (NOTE: "ia64" is an example; 255: the actual name may be different) 256: | Platform dependent 257: subsystem user-invoked 258: executables; commands 259: expected to be run users as 260: part of their normal PATH 261: |/usr///subsystem[[[4]>>#f4]]///bin/ 262: see isaexec(3C)|/opt/$PKG/bin/ 263: | SPARC 64-bit Platform 264: dependent user-invoked 265: executables that have to be 266: different on a 64-bit 267: system. 268: [Solaris 2.7 and beyond] | /usr///subsystem[[[4]>>#f4]]///bin/sparcv9/ 269: see isaexec(3C) 270: Note that this directory shall not be part 271: of the user’s PATH, as the user should never 272: directly invoke an executable in this 273: directory; rather the identically-named 274: wrapper in /usr/bin is invoked and 275: that in turn invokes the executable in this 276: directory, when appropriate |/opt/$PKG/bin/sparcv9/ 277: | Intel IA64 64-bit Platform 278: dependent user-invoked 279: executables that have to be 280: different on a 64-bit 281: system. 282: [Solaris future] | /usr///subsystem[[[4]>>#f4]]///bin/ia64/ 283: see isaexec(3C) 284: (NOTE: "ia64" is an example; 285: the actual name may be different) 286: Note that this directory shall not be part 287: of the user’s PATH, as the user should never 288: directly invoke an executable in this 289: directory; rather the identically-named 290: wrapper in /usr/bin is invoked and 291: that in turn invokes the executable in this 292: directory, when appropriate |/opt/$PKG/bin/ia64/ 293: (NOTE: "ia64" is an example; 294: the actual name may be different) 295: | Platform dependent 296: libraries, commands, 297: daemons, never directly 298: executed by a human |/usr/lib/|/opt/$PKG/lib/ 299: | SPARC 64-bit 300: Platform dependent 301: libraries, commands, 302: daemons, never 303: directly executed by a 304: human |/usr/lib/sparcv9/|/opt/$PKG/lib/sparcv9/ 305: | Intel IA64 64-bit Platform 306: dependent libraries, 307: commands, daemons, never 308: directly executed by a 309: human |/usr/lib/ia64/ 310: (NOTE: "ia64" is an example; 311: the actual name may be different) |/opt/$PKG/lib/ia64/ 312: (NOTE: "ia64" is an example; 313: the actual name may be different) 314: | Platform dependent 315: subsystem extensions; 316: libraries, commands, 317: daemons, never directly 318: executed by a human | /usr/lib///subsystem[[[4]>>#f4]]/// |/opt/$PKG/lib/ 319: | SPARC 64-bit 320: Platform dependent 321: libraries, commands, 322: daemons, never 323: directly executed by a 324: human | /usr/lib///subsystem[[[4]>>#f4]]///sparcv9/|/opt/$PKG/lib/sparcv9/ 325: | Intel IA64 64-bit Platform 326: dependent libraries, 327: commands, daemons, never 328: directly executed by a 329: human | /usr/lib///subsystem[[[4]>>#f4]]///ia64/ 330: (NOTE: "ia64" is an example; 331: the actual name may be different) |/opt/$PKG/lib/ia64/ 332: (NOTE: "ia64" is an example; 333: the actual name may be different) 334: | Platform dependent 335: subsystem extensions; 336: libraries, commands, 337: daemons, never directly 338: executed by a human | /usr///subsystem[[[4]>>#f4]]///lib/|/opt/$PKG/lib/ 339: | SPARC 64-bit 340: Platform dependent 341: libraries, commands, 342: daemons, never 343: directly executed by a 344: human | /usr///subsystem[[[4]>>#f4]]///lib/sparcv9/|/opt/$PKG/lib/sparcv9/ 345: | Intel IA64 64-bit Platform 346: dependent libraries, 347: commands, daemons, never 348: directly executed by a 349: human | /usr///subsystem[[[4]>>#f4]]///lib/ia64/ 350: (NOTE: "ia64" is an example; 351: the actual name may be 352: different) |/opt/$PKG/lib/ia64/ 353: (NOTE: "ia64" is an example; 354: the actual name may be different) 355: | Platform dependent 356: system administration 357: utilities expected to be 358: run only by administrators |/usr/sbin/| /opt/$PKG/sbin/ 359: | Platform dependent 360: system administration 361: subsystem utilities 362: expected to be run only 363: by administrators | /usr/sbin///subsystem[[[4]>>#f4]]///|/opt/$PKG/sbin/ 364: | Platform dependent 365: system administration 366: subsystem utilities 367: expected to be run only 368: by administrators | /usr///subsystem[[[4]>>#f4]]///sbin/|/opt/$PKG/sbin/ 369: | platform independent[[[5]>>#f5]] 370: sharable files | /usr/share/| Not Applicable 371: | platform independent 372: sharable databases | /usr/share/lib/| Not Applicable 373: | platform independent 374: sharable manual pages | /usr/share/[s]man/| /opt/$PKG/[s]man/ 375: 376: ---- 377: 378: 1. A //platform dependent// file is one that is installed on all platforms, but whose contents vary depending on the platform in question. 379: Executable files are the classic // platform dependent// file, but there can also be // platform dependent// shell scripts or configuration files. 380: One example is ///kernel/genunix//. 381: 382: 2. A // platform specific// file is one that is only installed on a subset of the supported platforms. // Platform specific// files can be further sub-divided into // platform dependent// and // platform independent//. A // platform specific platform independent// file is one that is only present on some platforms, but is always the same (if it is present). 383: A // platform specific platform dependent// file is only present on some platforms, and its contents differ on different platforms. 384: 385: 3. The minimal default kernel search path is 386: ///platform/`uname -i`/kernel:/kernel:/usr/kernel//, 387: but some systems may have a search path of 388: ///platform/`uname -i`/kernel:/platform/`uname -m`/kernel:/kernel:/usr/kernel//. 389: See kernel(1M) for details. 390: 391: 4. There is no recommended convention to use for a given //subsystem//, but a single //subsystem// should not mix conventions of ///usr/*///subsystem//// and ///usr///subsystem///*//. 392: 393: 5. A //platform independent// file is one that is installed on all platforms, and whose contents are the same on all platforms. Portable shell scripts, standard configuration files, and manual page sources are common examples of // platform independent// files. 394: 395: ---- 396: 397: == Exemptions 398: 399: ---- 400: 401: == Appeals 402: 403: ---- 404: 405: == Interface 406: 407: |Exported Interface Name |Stability Classification |ARC Case |Comments 408: |filesystem locations|Evolving|PSARC/1998/374|SUN NON-PROPRIETARY INFORMATION 409: 410: ---- 411: 412: == CaseHistory 413: 414: |=Case|=Type|=Name 415: |PSARC/1998/374|OnePager| Solaris Platform Installed Object Paths 416: |LSARC/1992/011|OnePager| Name Changes for SunPro Packages and Install Directory 417: |PSARC/1992/169|Unknown| /kernel/unix dependencies 418: |PSARC/1992/170|Unknown| /kernel directory layout 419: |PSARC/1992/171|Unknown| userland machine dependencies 420: |PSARC/1993/242|FastTrack| KBI Implementation (Phase 2) 421: |PSARC/1993/271|OnePager| PKG REORG: Footprint Reduction 422: |PSARC/1993/321|OnePager| KBI (Kernel Binary Interface) 423: |PSARC/1993/636|OnePager| SHWP Certified CD install 424: |PSARC/1993/638|OnePager| SHWP Certified CD /platform support 425: |PSARC/1994/291|OnePager| KBI Versioning 426: |PSARC/1994/331|FastTrack| Restructuring /var/sadm 427: |PSARC/1994/400|FastTrack| Changes to KBI VM interfaces 428: |PSARC/1994/440|FastTrack| Platform Definition File 429: |PSARC/1994/441|OnePager| PSMI for PowerPC 430: |PSARC/1995/028|FastTrack| Maintain Namespace for eeprom(1M) 431: |PSARC/1995/029|FastTrack| Modified Implementation of Platform Dependent Executables 432: |PSARC/1995/109|FastTrack| /usr/openwin/platform 433: |PSARC/1995/422|OnePager| PSMI Extensions 434: |PSARC/1996/039|OnePager| Solaris Packaging Requirements 435: |PSARC/1997/310|FastTrack| PSMI Version 1.2 436: |PSARC/1997/386|FastTrack| Platform Names for Solaris x86 437: |PSARC/1998/231|FastTrack| New Algorithm for x86 Platform Name 438: 439: ---- 440: 441: == ManPages 442: 443: |=Document|=Description 444: |filesystem.5| 445: |kernel.1M | 446: |isaexec.3C | 447: 448: ---- 449: 450: == References 451: 452: |
Search
Collectives
Community Group
Academic and Research
Accessibility
Advocacy
Appliances
Approachability
Architecture Process and Tools
BrandZ
Chinese Users
Community Advisory Board
Databases
Desktop
Device Drivers
Distribution
Documentation
DTrace
Emerging Platforms
Fault Management
Games on OpenSolaris
HA Clusters
HPC Developer
Installation and Packaging
Internationalization and Localization
Laptop
Logical Domains
Modular Debugger (MDB)
Networking
NFS
Observability
OpenSolaris Governing Board (OGB)
OpenSolaris Printing
OS/Net (ON)
Performance
Power Management
PowerPC
Security
Service Management Facility (smf(5))
Software Porters
Solaris Volume Manager
Storage
Systems Administration Community Group
Testing
Tools Home
Unix File Systems (UFS)
Website Community
X Window System
Xen
ZFS
Zones
Project
ADSL Modem Enhancement
ARC Process Definition
ARM Platform Port
Automatic Data Migration
BIND Update
Bluetooth Stack & Drivers
Brocade FC HBA - Initiator
Brocade FC HBA - Target
Brussels - unified network link configuration
Caiman, Solaris Install Revisited
Celeste
Český portál
Chime Visualization Tool for DTrace
CIFS client for Solaris
CIFS Server
Clearview: Network Interface Coherence
Cluster Agent: Informix Dynamic Server
Cluster Agent: OpenSolaris Container
Cluster Agent: OpenSolaris xVM
Cluster Agent: Oracle E-Business Suite
Cluster agent: PostgreSQL
Cluster Agent: Samba
Cluster Agent: Tomcat
CMT
Coarse Data Flow Parallelism
Colorado: Open HA Cluster on OpenSolaris
Command Assistant
Common Array Manager
Companion - /opt/sfw: Free and Open Source software
COMSTAR: Common Multiprotocol SCSI Target
Content
Contest
CPU Observability
Credentials Process Groups
Crossbow: Network Virtualization and Resource Control
Crypto KMS Agent Toolkit
Cryptographic Framework
Data Migration Manager
Data Tethers
Deutsches Portal
Device Detection Tool
Device Driver Utility
Device Manager
Device Mapper
Direct Rendering Infrastructure & 3D drivers
DTrace Guide
Duckwater: Simplified name services management
Easy Tools
Emancipation
Emulex Fibre Channel Device Driver
Emulex Advanced Ethernet Device Driver
Enable/Enhance Solaris support for Intel Platform
Enhance the support of USB webcams
Enhanced SMF Profiles
Enhancements for AMD-based Platforms
Erlang DTrace Integration
Ethernet bridge module for Solaris
Evaluate Conary
Events Registry
Ext3 file system support
F/OSS Package Base
Facilitation
Fibre Channel over Ethernet
Fine Grained Access Policy (FGAP)
Fingerprint Authentication
Flexible Mandatory Access Control
Forensic Tools
Fully Open X Project
Fuse on Solaris
gcore
Generic Machine Check Architecture Improvements
Google SOC
HA-JBoss
HA-MySQL
Hadoop Live CD
Hitachi
HoneyComb Fixed Content Storage
HPC Stack
Image Packaging System
Improved Performance MIB
Indiana
Innovation Awards
Input Method
Intel Graphics
Internet Key Exchange, version 2
Interrupt Resource Management
IP Datapath Refactoring
IP over Infiniband
IPsec Tunnel Reform
iSCSI Extensions for Remote DMA (iSER)
iSNS Server
JeOS - Just enough Operating System
JKstat - a java binding for libkstat
Journaled File System (JFS)
K Desktop Environment
Kerberos
Kernel Sockets
Kernel SSL Enhancements
Key Management Framework
Korn Shell 93 integration/migration project
Labeled IPsec
LatencyTOP
Layer 2 Filtering
LDoms Manager
Lending
libMicro - portable microbenchmarks
Link Layer Discovery
Live Media: Technologies for distributions running from CD and other media
Locale Data
lofi compression and cryptography support
lx64 brand
Media Management System
Mega_sas
Mexico
MilaX minimal Live Distribution
MIPS Platform Port
Mozilla DTrace
MRSL.NONsharedDevice
Multi-lingual Glossary
Multi-pathing software (MPxIO)
Multiple disk sector size support
Multiple DOI
Muskoka: An open repository for OpenSolaris technical content
Navigator
Nemo: A Framework for High-Performance Networking
Network Auto-Magic
Network Data Management Protocol
Network MIBs
Network Performance Projects
Network Storage
Network Time Protocol (NTP)
Nevada Globalization
New Design of 4over6 Mechanism Based on OpenSolaris
NFS RDMA transport update and performance analysis
NFS Server in non-Global Zones
NFS version 4.1 pNFS
NFSv4 namespace extensions
Nightingale: Port Songbird to OpenSolaris
NPort ID Virtualization (NPIV)
NUMA
Object Storage Device (OSD) support for Solaris
OHACGE Script Based Plug-in
ON/Nevada (ONNV) Project
Open Development Infrastructure
Open HA Cluster Utilities
Open Sound System
OpenGrok
OpenPegasus CIM Server
OpenRTI
OpenSolaris Busybox
OpenSolaris Desktop
OpenSolaris Hispano
OpenSolaris Security Audit
OpenSolaris support for the QEMU processor emulator: host and guest
PEF: Packet Event Framework
Performance Wrappers
Pkgfactory
Polski Portal
Portail Francophone
Portal Brasil
Portals
Power Management Usability Interfaces
Presto: Automatic Printing Configuration
Printable Many Page Solaris Manuals
Promise SuperTrak RAID HBA Driver
QLogic Converged Network Adapter GLDv3 NIC Driver
Quagga Routing Protocol Suite Integration
RAID Configuration Utility
RBridge (IETF TRILL) support
RDMA Offload Framework
Reno: Login Process Enhancements for Interop
Resource Management
s10brand
SAM/QFS
SCM Migration Project
SCSI RDMA Protocol
SDcard Drivers
Sensor Abstraction Layer
Session Initiation Protocol
SFW
Shell: bourne shell, korn shell, C shell, etc.
Sierra: Intel WiFi Chipsets Support
Simple Panels
SM-HBA Based SAS HBA Management
SMF Documentation
Solaris iSCSI Target
Solaris PowerPC Port
SourceJuicer
Sparks: name service switch/nscd enhancements
Squashfs
Star integration/migration project
Starfish
Starter Kit
Storage Power Management
Sun Security Toolkit
Sun StorageTek Availability Suite
Support for OpenFabrics User Verbs / API on OpenSolaris OS
Support gcc4/GCCfss in Solaris
Suspend/Resume
SVR4 Packaging
Systemz
Tamarack: Removable Media Enhancements in Solaris
Tesla: OpenSolaris Enhanced Power Management
Test Development
Tickless Kernel Architecture
TIPC
Trademarks
Trusted networking interface policy database for Trusted Extensions
Trusted Platform Module support
Use Case
Validated Execution Project
Virtual Console
Virtual Network Machines
Visual Panels
Visualization for HPC
Volo
VRRP: Virtual Router Redundancy Protocol Implementation
VSCAN service
Web Stack
Website
Winchester: Schema mapping and ID mapping for AD Interoperability
Wireless USB Support
Wireless Wide Area Network
X Consolidation
x86 Generic FMA Topology Enumerator
Xen Gate
Xfce: A lightweight desktop environment
ZFS Boot and Install
ZFS on disk encryption support
Zone Manager
Zone Statistics
Русский портал
البوابة العربية
भारतीय पोर्टल
中国门户
日本ポータル
한국 포탈
User Group
Adelaide
Argentina
Arizona
Atlanta
Baltimore-Washington
Bangalore
Bangkok
Bangladesh
Beijing
Bélem
Berlin
Bhimavaram
Bloomington
Campus Ambassadors
Capital Region
Cardiff
Ceara
Charlotte
Chengdu
Chennai
Chihuahua
Chile
Cleveland
Colombia
Columbus
Connecticut
Cracow
Czech
Dallas/Ft. Worth
Danish
Delaware
Edinburgh
Egypt
Finland
Florida
Front Range
FuZhou
Great Lakes
Greece
Hangzhou
Hawaii
HeFei
Houston
Hong Kong
Hyderabad
Indonesia
Irish
Israel
Italian
Jinan
Jogja
Kabul
Kansas City
Latvia
London
Madurai
Manchester
Mato Grosso
Melbourne
Minas Gerais
Minnesota
Montreal
Moscow
Mumbai
Munich
NEA
Netherlands
New England
New York City
New Zealand
NIT Hamirpur
Noroeste
Nuremberg-Erlangen
Oklahoma City
Osnabrück
Peru
Philadelphia
Piaski
Pittsburgh
Porto Alegre
Puget Sound
Pune
Queensland
Rio de Janeiro
Research Triangle Park
Romania
Russia
San Antonio
San Diego
San Francisco
São Paulo
Scottish
Serbia
Shanghai
Shenzhen
Silicon Valley
Singapore
Slovak
South African
Southern Connecticut
St. Louis
Sweden
Switzerland
Sydney
Szczecin
Taiwan
Tecum
Thames Valley
Tokyo
Toronto
Trondheim
Tulsa
Turkey
Ukraine
University of Melbourne
Vale do Paraíba
Vancouver
Venezuela
Welsh - Cymru
Wisconsin
Xi'an
Subsites
Code Reviews
Code Repositories
Package Search
Bugster
Bugzilla
Test Machines
Planet
Mailing Lists
Elections & Polls
ARC Case Logs
Source Juicer
Package Factory
User Authentication
Community Group arc Pages
ARCAgenda
FAQ
Use of the OpenSolaris aliases
ARC Fasttrack Handbook
When should developers interact with the ARC?
What sort of changes need ARC approval?
How do I publish/request an existing Sun ARC Case?
How to succeed with an Architectural review
What is an ARC Review?
Planning for the Architectural Review
ARC Fast-Track Sponsor Duties
General Principles for Requiring Changes to Projects
Announcing the Systems Architecture Process
Glossary
ARC Best Practices
ARC Alias Usage Guidelines
Architecture = Components + Interfaces
Command Lines and arguments
Configuration Files
Device Drivers
Environment Variables
Hardware Platform Dependencies
Internationalization (I18n)
Changes to interfaces
Inter-Project Compatibility
Libraries
Namespace Management and Conventions
Operating System Compatibility
Performance
Signals
Standards Conformance
Administrative and Security Precedents and Policies
Reusable Passwords In Command Line Arguments and Environment Variables
Storing Reusable Passwords on a Filesystem
Adding RBAC Authorizations
When to use setuid -vs- RBAC roles and profiles
Building RBAC Rights Profiles
Security Questions
Caselog
Files
ARC Handbook
ARC Process Proposal
Goals
Introduction to the ARC message for project teams
Responsibilities
Case Publishing Tool Information
Chartering a Consolidation
Template for interface "contract"
Template for ARC Project creation
Template for ARC Opinion
10 Questions
Reference: Sun's current internal ARC process
ARC Policies
Install Time Security
Network Install-Time Security
Plugable Authentication Modules
Service Management Facility (SMF) usage
Audit Policy
FMA Event Protocol
Recommended Installation Locations for Solaris-compatible Software Components
Interface Taxonomy
Library and Shared Object Requirements
Obsolete and the EOF process
Release Taxonomy
Secure - By Default
Packaging rules for system extensions (Shared and sharable components)
Projects
Testing area for automated scripts
OpenSolaris Developers
OpenSolaris Distros
OpenSolaris Users


Sites
Get Help
Licenses
Profile
Logout
Sites
Manage your
WordPress Sites
or add new ones.
Add Site
Govoid.es
edit
URL:
https://www.govoid.es
Site ID:
AS1231XOY74
Last modified: 11:09 PM - 1 Jan 2016
Blog Worona
edit
URL:
https://blog.worona.org
Site ID:
WQ5230I9Z2
Last modified: 06:09 AM - 3 Aug 2016