text:
LPI Linux Certification/LPIC2 Exam 202/Network Client Management

Section Overview

 * DHCP configuration
 * NIS configuration
 * LDAP configuration
 * PAM authentication
 * DHCP configuration

Overview
Description: ''The candidate should be able to configure a DHCP server and set default options, create a subnet, and create a dynamically-allocated range. This objective includes adding a static host, setting options for a single host, and adding bootp hosts. Also included is to configure a DHCP relay agent, and reload the DHCP server after making changes.''

Key files, terms, and utilities include:

dhcpd.conf dhcpd.leases

DHCP?
Most people reading this will already know the DHCP protocol. Just as a quick reminder. DHCP stands for Dynamic Host Configuration Protocol and is commonly used to distribute specific network settings in networks. Settings such as the default gateway, nameservers, IP addresses and much more.

As for a small illustration of the protocol itself.

Configuring dhcpd
After the installation of dhcpd the main configuration file can be found at /etc/dhcpd.conf. For Debian installations, one should edit /etc/default/dhcp as soon as the installation is finished and change the following line according to your setup.

INTERFACES="eth1" # or "eth1 eth2", whatever interfaces you wish to serve ip's.

The dhcpd.conf file is divided in global parameters and subnet specific parameters. Each subnet can override the global parameters. The most commonly used parameters are the following.

option domain-name "example.com"; option domain-name-servers "<IP_ADDRESS>, <IP_ADDRESS>" option subnet-mask <IP_ADDRESS>; # global Subnet mask default-lease-time 600; # Seconds each DHCP lease is granted and after which a request for the same ip is launched. max-lease-time 7200; # If DHCP server does not respond, keep IP till 7200 seconds are passed. subnet <IP_ADDRESS> netmask <IP_ADDRESS> { # Subnet for first 13 devices, 10 of which are servers, 3 printers range <IP_ADDRESS> <IP_ADDRESS>; # Range of IP's for our printers option subnet-mask <IP_ADDRESS>; option broadcast-address <IP_ADDRESS>; # This is the subnets broadcast address option routers <IP_ADDRESS>; # The gateway of this subnet option time-servers <IP_ADDRESS>; # Gateway is running a timeserver option ntp-servers <IP_ADDRESS>; # Gateway running a timeserver } subnet <IP_ADDRESS> netmask <IP_ADDRESS> { # Subnet for 29 computers range <IP_ADDRESS> <IP_ADDRESS>; option subnet-mask <IP_ADDRESS>; option broadcast-address <IP_ADDRESS>; option routers <IP_ADDRESS>; } group { host server1 { # the first fixed server for subnet <IP_ADDRESS>/28 server-name server1; hardware ethernet 0f:45:d3:23:11:90; fixed-address <IP_ADDRESS>; } host server2 { server-name server2; hardware ethernet 0f:45:d3:23:11:91; fixed-address <IP_ADDRESS>; } }

This example is just providing a hint about possible options and overrides.

More info can be found on dhcpd.conf and dhcp-options in man pages. Look in those pages too for information about using the DHCP server to serve BOOTP as well, useful for diskless clients..

Overview
Description: ''The candidate should be able to configure an NIS server and create NIS maps for major configuration files. This objective includes configuring a system as a NIS client, setting up an NIS slave server, and configuring ability to search local files, DNS, NIS, etc. in nsswitch.conf.''

Key files, terms, and utilities include:

nisupdate, ypbind, ypcat, ypmatch, ypserv, ypswitch, yppasswd, yppoll, yppush, ypwhich, rpcinfo nis.conf, nsswitch.conf, ypserv.conf /etc/nis/netgroup /etc/nis/nicknames /etc/nis/securenets

NIS
NIS stands for Network Information Service. Its purpose is to provide information, that has to be known throughout the network, to all machines on the network. Information likely to be distributed by NIS is login names/passwords/home directories (/etc/passwd) and group information (/etc/group)

If, for example, your password entry is recorded in the NIS passwd database, you will be able to login on all machines on the network which have the NIS client programs running.

Within a network there must be at least one machine acting as a NIS server. You can have multiple NIS servers, each serving different NIS "domains" - or you can have cooperating NIS servers, where one is the master NIS server, and all the other are so-called slave NIS servers (for a certain NIS "domain", that is!) - or you can have a mix of them...

Slave servers only have copies of the NIS databases and receive these copies from the master NIS server whenever changes are made to the master's databases. Depending on the number of machines in your network and the reliability of your network, you might decide to install one or more slave servers. Whenever a NIS server goes down or is too slow in responding to requests, a NIS client connected to that server will try to find one that is up or faster.

NIS databases are in so-called DBM format, derived from ASCII databases. For example, the files /etc/passwd and /etc/group can be directly converted to DBM format using ASCII-to-DBM translation software ("makedbm", included with the server software). The master NIS server should have both, the ASCII databases and the DBM databases.

Slave servers will be notified of any change to the NIS maps, (via the "yppush" program), and automatically retrieve the necessary changes in order to synchronize their databases. NIS clients do not need to do this since they always talk to the NIS server to read the information stored in it's DBM databases.

To run any of the software mentioned below you will need to run the program /usr/sbin/portmap. The RPC portmapper (portmap(8)) is a server that converts RPC program numbers into TCP/IP (or UDP/IP) protocol port numbers. It must be running in order to make RPC calls (which is what the NIS/NIS+ client software does) to RPC servers (like a NIS or NIS+ server) on that machine. When an RPC server is started, it will tell portmap what port number it is listening to, and what RPC program numbers it is prepared to serve. When a client wishes to make an RPC call to a given program number, it will first contact portmap on the server machine to determine the port number where RPC packets should be sent.

Since RPC servers could be started by inetd(8), portmap should be running before inetd is started. For secure RPC, the portmapper needs the Time service. Make sure, that the Time service is enabled in /etc/inetd.conf on all hosts:

# time   stream  tcp     nowait  root    internal time   dgram   udp     wait    root    internal
 * 1) Time service is used for clock synchronization.

IMPORTANT: Don't forget to restart inetd after changes on its configuration file !

What do you need to set up NIS?

Determine whether you are a Server, Slave or Client : Your machine is going to be part of a network with existing NIS servers You do not have any NIS servers in the network yet

In the first case, you only need the client programs (ypbind, ypwhich, ypcat, yppoll, ypmatch). The most important program is ypbind. This program must be running at all times, which means, it should always appear in the list of processes. It is a daemon process and needs to be started from the system's startup file (eg. /etc/init.d/nis, /sbin/init.d/ypclient, /etc/rc.d/init.d/ypbind, /etc/rc.local). As soon as ypbind is running your system has become a NIS client.

In the second case, if you don't have NIS servers, then you will also need a NIS server program (usually called ypserv). Section 9 describes how to set up a NIS server on your Linux machine using the "ypserv" daemon.

Setting Up the NIS Client
The ypbind daemon

Newer ypbind versions have a configuration file called /etc/yp.conf. You can hard code a NIS server there - for more info see the manual page for ypbind(8). You also need this file for NYS. An example:

ypserver <IP_ADDRESS> ypserver <IP_ADDRESS> ypserver <IP_ADDRESS>

If the system cam resolv the hostnames without NIS, you may use the name, otherwise you have to use the IP address. ypbind 3.3 has a bug and will only use the last entry (ypserver <IP_ADDRESS> in the example). All other entries are ignored. ypbind-mt handle this correct and uses that one, which answered at first.

It might be a good idea to test ypbind before incorporating it in the startup files. To test ypbind do the following:

Make sure you have your YP-domain name set. If it is not set then issue the command: /bin/domainname nis.domain

where nis.domain should be some string _NOT_ normally associated with the DNS-domain name of your machine! The reason for this is that it makes it a little harder for external crackers to retrieve the password database from your NIS servers. If you don't know what the NIS domain name is on your network, ask your system/network administrator.

Start up "/usr/sbin/portmap" if it is not already running. Create the directory "/var/yp" if it does not exist. Start up "/usr/sbin/ypbind"

Use the command "rpcinfo -p localhost" to check if ypbind was able to register its service with the portmapper. The output should look like:

program vers proto  port 100000   2   tcp    111  portmapper 100000   2   udp    111  portmapper 100007   2   udp    637  ypbind 100007   2   tcp    639  ypbind

Or like this (depending on the version of ypbind you are using) :

program vers proto  port 100000   2   tcp    111  portmapper 100000   2   udp    111  portmapper 100007   2   udp    758  ypbind 100007   1   udp    758  ypbind 100007   2   tcp    761  ypbind 100007   1   tcp    761  ypbind

You may also run "rpcinfo -u localhost ypbind". This command should produce something like:

program 100007 version 1 ready and waiting program 100007 version 2 ready and waiting

The output depends on the ypbind version you have installed. Important is only the "version 2" message. At this point you should be able to use NIS client programs like ypcat, etc... For example, "ypcat passwd.byname" will give you the entire NIS password database.

IMPORTANT: If you skipped the test procedure then make sure you have set the domain name, and created the directory /var/yp. This directory MUST exist for ypbind to start up successfully. To check if the domainname is set correct, use the /bin/ypdomainname from yp-tools 2.2. It uses the yp_get_default_domain function which is more restrict. It doesn't allow for example the "(none)" domainname, which is the default under Linux and makes a lot of problems.

If the test worked you may now want to change your startupd files so that ypbind will be started at boot time and your system will act as a NIS client. Make sure that the domainname will be set before you start ypbind. Well, that's it. Reboot the machine and watch the boot messages to see if ypbind is actually started. For host lookups you must set (or add) "nis" to the lookup order line in your /etc/host.conf file. Please read the manpage "resolv+.8" for more details. Add the following line to /etc/passwd on your NIS clients:

+::::::

You can also use the + and - characters to include/exclude or change users. If you want to exclude the user guest just add -guest to your /etc/passwd file. You want to use a different shell (e.g. ksh) for the user "linux"? No problem, just add "+linux::::::/bin/ksh" (without the quotes) to your /etc/passwd. Fields that you don't want to change have to be left empty. You could also use Netgroups for user control.

For example, to allow login-access only to miquels, dth and ed, and all members of the sysadmin netgroup, but to have the account data of all other users available use:

+miquels::::::: +ed::::::: +dth::::::: +@sysadmins::::::: -ftp +:*::::::/etc/NoShell

Note that in Linux you can also override the password field, as we did in this example. We also remove the login "ftp", so it isn't known any longer, and anonymous ftp will not work. The netgroup would look like :

sysadmins (-,software,) (-,kukuk,)

The nsswitch.conf File
The Network Services switch file /etc/nsswitch.conf determines the order of lookups performed when a certain piece of information is requested, just like the /etc/host.conf file which determines the way host lookups are performed. For example, the line :

hosts: files nis dns

specifies that host lookup functions should first look in the local /etc/hosts file, followed by a NIS lookup and finally through the domain name service (/etc/resolv.conf and named), at which point if no match is found an error is returned. This file must be readable for every user! You can find more information in the man-page nsswitch.5 or nsswitch.conf.5.

A good /etc/nsswitch.conf file for NIS is:

passwd:    compat group:     compat
 * 1) /etc/nsswitch.conf

shadow:    compat passwd_compat: nis group_compat: nis shadow_compat: nis hosts:     nis files dns services:  nis [NOTFOUND=return] files networks:  nis [NOTFOUND=return] files protocols: nis [NOTFOUND=return] files rpc:       nis [NOTFOUND=return] files ethers:    nis [NOTFOUND=return] files netmasks:  nis [NOTFOUND=return] files netgroup:  nis bootparams: nis [NOTFOUND=return] files publickey: nis [NOTFOUND=return] files automount: files aliases:   nis [NOTFOUND=return] files
 * 1) For libc5, you must use shadow: files nis

Setting up a NIS Server
The Server Program ypserv

If you run your server as master, determine what files you require to be available via NIS and then add or remove the appropriate entries to the "all" rule in /var/yp/Makefile. You always should look at the Makefile and edit the Options at the beginning of the file.

There was one big change between ypserv 1.1 and ypserv 1.2. Since version 1.2, the file handles are cached. This means you have to call makedbm always with the -c option if you create new maps. Make sure, you are using the new /var/yp/Makefile from ypserv 1.2 or later, or add the -c flag to makedbm in the Makefile. If you don't do that, ypserv will continue to use the old maps, and not the updated one.

Now edit /var/yp/securenets and /etc/ypserv.conf. For more information, read the ypserv(8) and ypserv.conf(5) manual pages.

Make sure the portmapper (portmap(8)) is running, and start the server ypserv. The command « rpcinfo -u localhost ypserv » should output something like :

program 100004 version 1 ready and waiting program 100004 version 2 ready and waiting

The "version 1" line could be missing, depending on the ypserv version and configuration you are using. It is only necessary if you have old SunOS 4.x clients.

Now generate the NIS (YP) database. On the master, run :

% /usr/lib/yp/ypinit -m

On a slave make sure that ypwhich -m works. This means, that your slave must be configured as NIS client before you could run « /usr/lib/yp/ypinit -s masterhost » to install the host as NIS slave. That's it, your server is up and running.

If you have bigger problems, you could start ypserv and ypbind in debug mode on different xterms. The debug output should show you what goes wrong.

If you need to update a map, run make in the /var/yp directory on the NIS master. This will update a map if the source file is newer, and push the files to the slave servers. Please don't use ypinit for updating a map. You might want to edit root's crontab *on the slave* server and add the following lines:

20 *   * * *    /usr/lib/yp/ypxfr_1perhour 40 6   * * *    /usr/lib/yp/ypxfr_1perday 55 6,18 * * *   /usr/lib/yp/ypxfr_2perday

This will ensure that most NIS maps are kept up-to-date, even if an update is missed because the slave was down at the time the update was done on the master.

You can add a slave at every time later. At first, make sure that the new slave server has permissions to contact the NIS master. Then run :

% /usr/lib/yp/ypinit -s masterhost

on the new slave. On the master server, add the new slave server name to /var/yp/ypservers and run make in /var/yp to update the map.

The Program rpc.ypxfrd
rpc.ypxfrd is used for speed up the transfer of very large NIS maps from a NIS master to NIS slave servers. If a NIS slave server receives a message that there is a new map, it will start ypxfr for transfering the new map. ypxfr will read the contents of a map from the master server using the yp_all function. This process can take several minutes when there are very large maps which have to store by the database library.

The rpc.ypxfrd server speeds up the transfer process by allowing NIS slave servers to simply copy the master server's map files rather than building their own from scratch. rpc.ypxfrd uses an RPC-based file transfer protocol, so that there is no need for building a new map.

rpc.ypxfrd can be started by inetd. But since it starts very slow, it should be started with ypserv. You need to start rpc.ypxfrd only on the NIS master server.

The Program rpc.yppasswdd
Whenever users change their passwords, the NIS password database and probably other NIS databases, which depend on the NIS password database, should be updated. The program "rpc.yppasswdd" is a server that handles password changes and makes sure that the NIS information will be updated accordingly. rpc.yppasswdd is now integrated in ypserv. You don't need the older, separate yppasswd-0.9.tar.gz or yppasswd-0.10.tar.gz, and you shouldn't use them any longer. The rpc.yppasswdd in ypserv 1.3.2 has full shadow support. yppasswd is now part of yp-tools-2.2.tar.gz.

You need to start rpc.yppasswdd only on the NIS master server. By default, users are not allowed to change their full name or the login shell. You can allow this with the -e chfn or -e chsh option. If your passwd and shadow files are not in another directory then /etc, you need to add the -D option. For example, if you have put all source files in /etc/yp and wish to allow the user to change his shell, you need to start rpc.yppasswdd with the following parameters:

rpc.yppasswdd -D /etc/yp -e chsh or rpc.yppasswdd -s /etc/yp/shadow -p /etc/yp/passwd -e chsh

There is nothing more to do. You just need to make sure, that rpc.yppasswdd uses the same files as /var/yp/Makefile. Errors will be logged using syslog.

If everything is fine (as it should be), you should be able to verify your installation with a few simple commands. Assuming, for example, your passwd file is being supplied by NIS, the command :

% ypcat passwd

should give you the contents of your NIS passwd file. The command :

% ypmatch userid passwd

(where userid is the login name of an arbitrary user) should give you the user's entry in the NIS passwd file. The "ypcat" and "ypmatch" programs should be included with your distribution of traditional NIS or NYS. Once you have NIS correctly configured on the server and client, you do need to be sure that the configuration will survive a reboot. On RedHat, create or modify the variable NISDOMAIN in the file /etc/sysconfig/network.

Exercises
.

Overview
Key terms, files and utilities : Slapd slapd.conf

PAM authentication
test

PAM (Pluggable Authentication Modules) is a flexible mechanism for authenticating users. Since the beginnings of UNIX, authenticating a user has been accomplished via the user entering a password and the system checking if the entered password corresponds to the encrypted official password that is stored in /etc/passwd. The idea being that the user *is* really that user if and only if they can correctly enter their secret password. That was in the beginning. Since then, a number of new ways of authenticating users have become popular. Including more complicated replacements for the /etc/passwd file, and hardware devices Smart cards etc.. The problem is that each time a new authentication scheme is developed, it requires all the necessary programs (login, ftpd etc...) to be rewritten to support it. PAM provides a way to develop programs that are independent of authentication scheme. These programs need "authentication modules" to be attatched to them at run-time in order to work. Which authentication module is to be attatched is dependent upon the local system setup and is at the discretion of the local system administrator. PAM authentication Linux-PAM (Pluggable Authentication Modules for Linux) is a suite of shared libraries that enable the local system administrator to choose how applications authenticate users. In other words, without (rewriting and) recompiling a PAM-aware application, it is possible to switch between the authentication mechanism(s) it uses. Indeed, one may entirely upgrade the local authentication system without touching the applications themselves. Historically an application that has required a given user to be authenticated, has had to be compiled to use a specific authentication mechanism. For example, in the case of traditional UN*X systems, the identity of the user is verified by the user entering a correct password. This password, after being prefixed by a two character ``salt'', is encrypted (with crypt(3)). The user is then authenticated if this encrypted password is identical to the second field of the user's entry in the system password database (the /etc/passwd file). On such systems, most if not all forms of privileges are granted based on this single authentication scheme. Privilege comes in the form of a personal user-identifier (uid) and membership of various groups. Services and applications are available based on the personal and group identity of the user. Traditionally, group membership has been assigned based on entries in the /etc/group file. PAM authentication Unfortunately, increases in the speed of computers and the widespread introduction of network based computing, have made once secure authentication mechanisms, such as this, vulnerable to attack. In the light of such realities, new methods of authentication are continuously being developed. It is the purpose of the Linux-PAM project to separate the development of privilege granting software from the development of secure and appropriate authentication schemes. This is accomplished by providing a library of functions that an application may use to request that a user be authenticated. This PAM library is configured locally with a system file, /etc/pam.conf (or a series of configuration files located in /etc/pam.d/) to authenticate a user request via the locally available authentication modules. The modules themselves will usually be located in the directory /lib/security and take the form of dynamically loadable object files (see dlopen(3)). PAM authentication Overview For the uninitiated, we begin by considering an example. We take an application that grants some service to users; login is one such program. Login does two things, it first establishes that the requesting user is whom they claim to be and second provides them with the requested service: in the case of login the service is a command shell (bash, tcsh, zsh, etc.) running with the identity of the user. Traditionally, the former step is achieved by the login application prompting the user for a password and then verifying that it agrees with that located on the system; hence verifying that as far as the system is concerned the user is who they claim to be. This is the task that is delegated to Linux-PAM. From the perspective of the application programmer (in this case the person that wrote the login application), Linux-PAM takes care of this authentication task -- verifying the identity of the user. PAM authentication The flexibility of Linux-PAM is that you, the system administrator, have the freedom to stipulate which authentication scheme is to be used. You have the freedom to set the scheme for any/all PAM-aware applications on your Linux system. That is, you can authenticate from anything as naive as simple trust (pam_permit) to something as paranoid as a combination of a retinal scan, a voice print and a one-time password! To illustrate the flexibility you face, consider the following situation: a system administrator (parent) wishes to improve the mathematical ability of her users (children). She can configure their favorite ``Shoot 'em up game'' (PAM-aware of course) to authenticate them with a request for the product of a couple of random numbers less than 12. It is clear that if the game is any good they will soon learn their multiplication tables. As they mature, the authentication can be upgraded to include (long) division! PAM authentication Linux-PAM deals with four separate types of (management) task. These are: authentication management; account management; session management; and password management. The association of the preferred management scheme with the behavior of an application is made with entries in the relevant Linux-PAM configuration file. The management functions are performed by modules specified in the configuration file. The Linux-PAM library consults the contents of the PAM configuration file and loads the modules that are appropriate for an application. These modules fall into one of four management groups and are stacked in the order they appear in the configuration file. These modules, when called by Linux-PAM, perform the various authentication tasks for the application. Textual information, required from/or offered to the user, can be exchanged through the use of the application-supplied conversation function. PAM authentication Linux-PAM is designed to provide the system administrator with a great deal of flexibility in configuring the privilege granting applications of their system. The local configuration of those aspects of system security controlled by Linux-PAM is contained in one of two places: either the single system file, /etc/pam.conf; or the /etc/pam.d/ directory. Linux-PAM specific tokens in this file are case insensitive. The module paths, however, are case sensitive since they indicate a file's name and reflect the case dependence of typical Linux file-systems. The case-sensitivity of the arguments to any given module is defined for each module in turn. In addition to the lines described below, there are two special characters provided for the convenience of the system administrator: comments are preceded by a `#' and extend to the next end-of-line; also, module specification lines may be extended with a `\' escaped newline. A general configuration line of the /etc/pam.conf file has the following form: : service-name  module-type   control-flag   module-path   args PAM authentication Below, we explain the meaning of each of these tokens. The second (and more recently adopted) way of configuring Linux-PAM is via the contents of the /etc/pam.d/ directory. Once we have explained the meaning of the above tokens, we will describe this method.

Service-name The name of the service associated with this entry. Frequently the service name is the conventional name of the given application. For example, `ftpd', `rlogind' and `su', etc.. There is a special service-name, reserved for defining a default authentication mechanism. It has the name `OTHER' and may be specified in either lower or upper case characters. Note, when there is a module specified for a named service, the `OTHER' entries are ignored.

PAM authentication Module-type One of (currently) four types of module. The four types are as follows:

auth; this module type provides two aspects of authenticating the user. Firstly, it establishes that the user is who they claim to be, by instructing the application to prompt the user for a password or other means of identification. Secondly, the module can grant group membership (independently of the /etc/groups file discussed above) or other privileges through its credential granting properties.

account; this module performs non-authentication based account management. It is typically used to restrict/permit access to a service based on the time of day, currently available system resources (maximum number of users) or perhaps the location of the applicant user---`root' login only on the console.

session; primarily, this module is associated with doing things that need to be done for the user before/after they can be given service. Such things include the logging of information concerning the opening/closing of some data exchange with a user, mounting directories, etc..

password; this last module type is required for updating the authentication token associated with the user. Typically, there is one module for each `challenge/response' based authentication (auth) module-type. PAM authentication Control-flag The control-flag is used to indicate how the PAM library will react to the success or failure of the module it is associated with. Since modules can be stacked (modules of the same type execute in series, one after another), the control-flags determine the relative importance of each module. The application is not made aware of the individual success or failure of modules listed in the `/etc/pam.conf' file. Instead, it receives a summary success or fail response from the Linux-PAM library. The order of execution of these modules is that of the entries in the /etc/pam.conf file; earlier entries are executed before later ones. As of Linux-PAM v0.60, this control-flag can be defined with one of two syntaxes. The simpler (and historical) syntax for the control-flag is a single keyword defined to indicate the severity of concern associated with the success or failure of a specific module. There are four such keywords: required, requisite, sufficient and optional. PAM authentication Control-flag The Linux-PAM library interprets these keywords in the following manner: required; this indicates that the success of the module is required for the module-type facility to succeed. Failure of this module will not be apparent to the user until all of the remaining modules (of the same module-type) have been executed.

requisite; like required, however, in the case that such a module returns a failure, control is directly returned to the application. The return value is that associated with the first required or requisite module to fail. Note, this flag can be used to protect against the possibility of a user getting the opportunity to enter a password over an unsafe medium. It is conceivable that such behavior might inform an attacker of valid accounts on a system. This possibility should be weighed against the not insignificant concerns of exposing a sensitive password in a hostile environment.

sufficient; the success of this module is deemed `sufficient' to satisfy the Linux-PAM library that this module-type has succeeded in its purpose. In the event that no previous required module has failed, no more `stacked' modules of this type are invoked. (Note, in this case subsequent required modules are not invoked.). A failure of this module is not deemed as fatal to satisfying the application that this module-type has succeeded.

Optional; as its name suggests, this control-flag marks the module as not being critical to the success or failure of the user's application for service. In general, Linux-PAM ignores such a module when determining if the module stack will succeed or fail. However, in the absence of any definite successes or failures of previous or subsequent stacked modules this module will determine the nature of the response to the application. One example of this latter case, is when the other modules return something like PAM_IGNORE. PAM authentication Control-flag : The more elaborate (newer) syntax is much more specific and gives the administrator a great deal of control over how the user is authenticated. This form of the control flag is delimited with square brackets and consists of a series of value=action tokens: [value1=action1 value2=action2 ...] Here, valueI is one of the following return values: success; open_err; symbol_err; service_err; system_err; buf_err; perm_denied; auth_err; cred_insufficient; authinfo_unavail; user_unknown; maxtries; new_authtok_reqd; acct_expired; session_err; cred_unavail; cred_expired; cred_err; no_module_data; conv_err; authtok_err; authtok_recover_err; authtok_lock_busy; authtok_disable_aging; try_again; ignore; abort; authtok_expired; module_unknown; bad_item; and default. The last of these (default) can be used to set the action for those return values that are not explicitly defined. The actionI can be a positive integer or one of the following tokens: ignore; ok; done; bad; die; and reset. A positive integer, J, when specified as the action, can be used to indicate that the next J modules of the current module-type will be skipped. In this way, the administrator can develop a moderately sophisticated stack of modules with a number of different paths of execution. Which path is taken can be determined by the reactions of individual modules. PAM authentication

ignore - when used with a stack of modules, the module's return status will not contribute to the return code the application obtains.

bad - this action indicates that the return code should be thought of as indicative of the module failing. If this module is the first in the stack to fail, its status value will be used for that of the whole stack.

die - equivalent to bad with the side effect of terminating the module stack and PAM immediately returning to the application.

ok - this tells PAM that the administrator thinks this return code should contribute directly to the return code of the full stack of modules. In other words, if the former state of the stack would lead to a return of PAM_SUCCESS, the module's return code will override this value. Note, if the former state of the stack holds some value that is indicative of a modules failure, this 'ok' value will not be used to override that value.

done - equivalent to ok with the side effect of terminating the module stack and PAM immediately returning to the application.

reset - clear all memory of the state of the module stack and start again with the next stacked module. PAM authentication Each of the four keywords: required; requisite; sufficient; and optional, have an equivalent expression in terms of the [...] syntax. They are as follows:

required is equivalent to [success=ok new_authtok_reqd=ok ignore=ignore default=bad]

requisite is equivalent to [success=ok new_authtok_reqd=ok ignore=ignore default=die]

sufficient is equivalent to [success=done new_authtok_reqd=done default=ignore]

optional is equivalent to [success=ok new_authtok_reqd=ok default=ignore]

Just to get a feel for the power of this new syntax, here is a taste of what you can do with it. With Linux-PAM-0.63, the notion of client plug-in agents was introduced. This is something that makes it possible for PAM to support machine-machine authentication using the transport protocol inherent to the client/server application. With the ``[ ... value=action ... ]'' control syntax, it is possible for an application to be configured to support binary prompts with compliant clients, but to gracefully fall over into an alternative authentication mode for older, legacy, applications. PAM authentication Module-path The path-name of the dynamically loadable object file; the pluggable module itself. If the first character of the module path is `/', it is assumed to be a complete path. If this is not the case, the given module path is appended to the default module path: /lib/security

Args The args are a list of tokens that are passed to the module when it is invoked. Much like arguments to a typical Linux shell command. Generally, valid arguments are optional and are specific to any given module. Invalid arguments are ignored by a module, however, when encountering an invalid argument, the module is required to write an error to syslog(3). For a list of generic options see the next section.

Any line in (one of) the configuration file(s), that is not formatted correctly, will generally tend (erring on the side of caution) to make the authentication process fail. A corresponding error is written to the system log files with a call to syslog(3). PAM authentication Directory based configuration More flexible than the single configuration file, as of version 0.56, it is possible to configure libpam via the contents of the /etc/pam.d/ directory. In this case the directory is filled with files each of which has a filename equal to a service-name (in lower-case): it is the personal configuration file for the named service. Linux-PAM can be compiled in one of two modes. The preferred mode uses either /etc/pam.d/ or /etc/pam.conf configuration but not both. That is to say, if there is a /etc/pam.d/ directory then libpam only uses the files contained in this directory. However, in the absence of the /etc/pam.d/ directory the /etc/pam.conf file is used (this is likely to be the mode your preferred distribution uses). The other mode is to use both /etc/pam.d/ and /etc/pam.conf in sequence. In this mode, entries in /etc/pam.d/ override those of /etc/pam.conf. The syntax of each file in /etc/pam.d/ is similar to that of the /etc/pam.conf file and is made up of lines of the following form: module-type  control-flag   module-path   arguments The only difference being that the service-name is not present. The service-name is of course the name of the given configuration file. For example, /etc/pam.d/login contains the configuration for the login service. PAM authentication This method of configuration has a number of advantages over the single file approach. We list them here to assist the reader in deciding which scheme to adopt: A lower chance of misconfiguring an application. There is one less field to mis-type when editing the configuration files by hand. Easier to maintain. One application may be reconfigured without risk of interfering with other applications on the system. It is possible to symbolically link different services configuration files to a single file. This makes it easier to keep the system policy for access consistent across different applications. (It should be noted, to conserve space, it is equally possible to hard link a number of configuration files. However, care should be taken when administering this arrangement as editing a hard linked file is likely to break the link.) A potential for quicker configuration file parsing. Only the relevant entries are parsed when a service gets bound to its modules. It is possible to limit read access to individual Linux-PAM configuration files using the file protections of the filesystem. Package management becomes simpler. Every time a new application is installed, it can be accompanied by an /etc/pam.d/xxxxxx file. PAM authentication The following are optional arguments which are likely to be understood by any module. Arguments (including these) are in general optional. Debug : Use the syslog(3) call to log debugging information to the system log files. no_warn : Instruct module to not give warning messages to the application. use_first_pass : The module should not prompt the user for a password. Instead, it should obtain the previously typed password (from the preceding auth module), and use that. If that doesn't work, then the user will not be authenticated. (This option is intended for auth and password modules only). try_first_pass : The module should attempt authentication with the previously typed password (from the preceding auth module). If that doesn't work, then the user is prompted for a password. (This option is intended for auth modules only). use_mapped_pass : This argument is not currently supported by any of the modules in the Linux-PAM distribution because of possible consequences associated with U.S. encryption exporting restrictions. Within the U.S., module developers are, of course, free to implement it (as are developers in other countries). expose_account : In general the leakage of some information about user accounts is not a secure policy for modules to adopt. Sometimes information such as users names or home directories, or preferred shell, can be used to attack a user's account. In some circumstances, however, this sort of information is not deemed a threat: displaying a user's full name when asking them for a password in a secured environment could also be called being 'friendly'. The expose_account argument is a standard module argument to encourage a module to be less discrete about account information as it is deemed appropriate by the local administrator. PAM authentication Example configuration file entries Default policy : If a system is to be considered secure, it had better have a reasonably secure `OTHER' entry. The following is a paranoid setting (which is not a bad place to start!): OTHER  auth     required       pam_deny.so OTHER   account  required       pam_deny.so OTHER   password required       pam_deny.so OTHER   session  required       pam_deny.so
 * 1) default; deny access
 * 1) default; deny access

Whilst fundamentally a secure default, this is not very sympathetic to a misconfigured system. For example, such a system is vulnerable to locking everyone out should the rest of the file become badly written. The module pam_deny is not very sophisticated. For example, it logs no information when it is invoked so unless the users of a system contact the administrator when failing to execute a service application, the administrator may go for a long while in ignorance of the fact that his system is misconfigured. PAM authentication The addition of the following line before those in the above example would provide a suitable warning to the administrator. OTHER  auth     required       pam_warn.so OTHER   password required       pam_warn.so
 * 1) default; wake up! This application is not configured
 * 1) default; wake up! This application is not configured

Having two ``OTHER auth'' lines is an example of stacking. On a system that uses the /etc/pam.d/ configuration, the corresponding default setup would be achieved with the following file: auth    required       pam_warn.so auth     required       pam_deny.so account  required       pam_deny.so password required       pam_warn.so password required       pam_deny.so session  required       pam_deny.so PAM authentication On a less sensitive computer, one on which the system administrator wishes to remain ignorant of much of the power of Linux-PAM, the following selection of lines (in /etc/pam.conf) is likely to mimic the historically familiar Linux setup.
 * 1) default configuration: /etc/pam.d/other
 * 1) default configuration: /etc/pam.d/other

OTHER  auth     required       pam_unix.so OTHER   account  required       pam_unix.so OTHER   password required       pam_unix.so OTHER   session  required       pam_unix.so
 * 1) default; standard UN*X access
 * 1) default; standard UN*X access

PAM authentication Key terms, files and utilities : /etc/pam.d /etc/pam.conf /lib/libpam.so.*


text:
User:Ran Feldesh

Hi all,

I would like to check the option of uploading wikiversity lecture notes of a physics course given at Ben Gurion University, Israel, by my professor. I created the below link at my UserAccount page as a preliminary pilot. I'll link it to with its appropriate place at the phyiscs portal in case that the pilot would come out good. '''Therefore please do not alter this for the coming week. For any suggestions please write me on my talk page.'''

--Ran Feldesh 19:40, 8 April 2007 (UTC)

Thermodynamics Lecture Notes, BGU

source: wikimedia

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: User:Ran Feldesh


text:
Cookbook:Bengali Five-Spice Mix (Panch Puran)

| Cuisine of India | Spices and herbs

Panch Puran (also called Panch Phoran, Panch Phoron, or Bengali Five-Spice Mix) is a spice mixture used in Indian cuisine. It is made of equal parts of five spices:

 * fenugreek seed (methi)
 * nigella seed (kalo jira)
 * mustard seed (rai or shorshe)
 * fennel seed (mouri)
 * cumin seed (jeera)

In some variations, wild onion is used in place of cumin. In other variations, radhuni seed is added to the mixture.

The name simply means "five spices" in Bengali.

In Bengali cuisine, the seeds are usually fried in oil (or ghee), which causes them to start crackling immediately. Vegetables (especially potatoes), dal, or fish are then added. It is not used with meat.


text:
User:Rodasmith/lexeme data

Purpose and scope
This initiative attempts to maximize the effectiveness of contributions for lexicological details that apply to multiple entries. It does not seek to prohibit efforts to build synchronization systems across various inflections.

Lexicological details
Many of the lexicological details in any dictionary apply to a specific headword, i.e. in sequence of characters (e.g. words) in a specific language (e.g. English) with a specific part of speech (e.g. Noun) and a specific grammatical form (e.g. plural). For example, below are a pronunciation and citation, two lexicological details that apply to the specific headword, which is a plural English noun:
 * Pronunciation
 * Noun
 * [definition]
 * Common English translation of a quote from Pindar,
 * Words have a longer life than deeds.
 * Common English translation of a quote from Pindar,
 * Words have a longer life than deeds.

In our dictionay (and in every good dictionary that describes English or any other inflected language), some lexicological details (e.g. a definition for a verb) apply more broadly to an entire lexeme (i.e. to all of the inflections of a given headword). To illustrate, consider the English word, which functions as several specific grammatical forms of the lexeme to talk/talk/talks/talking/talked. Following are a few of its specific grammatical functions:
 * is the bare infinitive:
 * (To) communicate to someone else by means of voice.
 * I did not talk to him.
 * is the first person singular present tense indicative mood:
 * (I) communicate to someone else by means of voice.
 * I talk to him every day.
 * is the imperative:
 * Communicate to someone else by means of voice!
 * Talk!

Although the word talk functions as several grammatical forms, no dictionary gives separate definitions for each of those grammatical forms. Rather, each definition explains only the meaning of the lexeme to talk/talk/talks/talking/talked, using a grammar-neutral verb phrase:
 * 1) To communicate to someone else by means of voice.
 * ... but not also...
 * 1) (I) communicate to someone else by means of voice.
 * 2) Communicate to someone else by means of voice!

The senses struck from above are unnecessary because each dictionary definition only describes the meaning of the lexeme and its part of speech without attempting describe the grammar details of any particular verb form. So, each dictionary definition applies to all forms of the lexeme (e.g. for to talk, talk, talks, talking, and talked). Thus, readers who see “To communicate to someone else by means of voice” know that they can use the word in places where an infinitive is not grammatically correct. (I.e., it's OK to say I talk to him every day, even though it is grammatically incorrect to say, *I to communicate... to him every day.)

So, we can classify each lexicological detail according to the type of entity to which it applies:
 * 1) Details that apply to a headword (a specific grammatical form of a specific word), e.g.:
 * 2) * citations for the English word
 * 3) * grammar categories of the Spanish word
 * 4) Details that apply to an entire lexeme, e.g.:
 * 5) * definitions of the English lexeme
 * 6) * translations of the English lexeme
 * 7) * conjugation of the Spanish lexeme
 * 8) Details that apply to a large set of words, e.g.:
 * 9) * Appendix:Spanish conjugation, which applies to all Spanish verbs

This initiative seeks to determine where best to put lexicological details that apply to an entire lexeme. Three alternatives follow:
 * Repeat lexeme details in every entry for its various forms.
 * Consolidate lexeme details in its “main” entry.
 * Consolidate lexeme details in templates.

Repeat lexeme details in every entry for its various forms
In this approach, there would be no single place for details that apply to the whole lexeme. Instead, an editor who wants to correct a translation of the lexeme must edit the 60+ pages of various verb forms to ensure that subsequent readers find corrected the definition.

Consolidate lexeme details in its “main” entry
In this traditional dictionary approach, a “secondary” entry like would show details for that specific word along with an abbreviated version of the details that apply to the lexeme hablar/hablo/hablas/habla/hablamos/... and a notice that more details for the lexeme may be found in the “main” (lemma/citation form) entry. The disadvantage to this approach is that readers must click the “main entry” link for more details.

Consolidate lexeme details in templates
In this approach, we would transclude lexeme details into the entries for each of its forms. This gives readers “zero-click” access to the details that apply to all of its forms from entries for every form of a lexeme. For example, readers would find a complete, up-to-date set of definitions and translations that contributors have supplied for the lexeme immediately whenever a reader looks up  without forcing the reader to click through to. One disadvantage of this approach is the apparent mismatch of the grammatical form of with a definition like “to communicate by...”. Another disadvantage is that several applications today depend on definitions appearing in a numbered list in the core article, and not transcluded from a template. Also, given how MediaWiki handles section editing, this approach creates certain editorial hurdles.

Benefits of consolidation
The latter two approaches would create a single consistent place (1) for contributors to furnish such details, (2) for readers to read about such details, and (3) for bots and other applications (e.g. Ninjawords) to consume such details. Either alternative would provide the following benefits:
 * For definitions of English lexemes: A contributor would be able to add and edit definitions in our project for the English lexeme talk/talks/talking/talked by editing the numbered list at talk without also having to edit the entries for, , and . A reader who wants to know whether “they talk” can refer to non-verbal communication would be able to check talk without having also to check definitions in our entries for , , and .  External applications would be able to consume synonyms and antonyms for each lexeme from a single source.
 * For translations from English lexemes: A contributor would be able to add a new translation in a single edit that is seen by all future readers who want to translate . A reader who wants to translate "he will talk" into Spanish would find all such translations by reading the Spanish entries linked from the translations table in talk without also having to check, , or.
 * Inflections of a lexeme: A contributor who wants to supply the conjugation of a French verb would be able to do so in a single edit for all future readers who seek that conjugation. A reader who wants to know how to conjugate that French verb would be able to look in one consistent place.  A bot writer who wants to add entries for inflections of that lexeme would be able to read just that one resource.

Some policy document should define where to house lexicological details that apply to entire lexemes.

title: User:Rodasmith/lexeme data


text:
toissapäiväinen

Adjective

 * 1) of the day before yesterday; nudiustertian

Usage notes
The adjective is a single word, although the noun, which it is derived from, consists of two words.

title: toissapäiväinen


text:
Chapin School (New Jersey)

 * See also The Chapin School for the school in Manhattan with the same name.

Chapin School is a private coeducational day school located in Lawrence Township, New Jersey, United States, serving students in pre-kindergarten through eighth grade situated on a 13 acre campus located 2 miles outside of Princeton (which is the school's mailing address).

As of the 2022 school year, the school had an enrollment of 228 students and 42.1 classroom teachers (on an FTE basis), for a student–teacher ratio of 6:1

Chapin School in Princeton, New Jersey, is accredited by the Middle States Association of Colleges and Schools. The school is a member of the National Association of Independent Schools and the New Jersey Association of Independent Schools.

History

Chapin School was founded in Princeton in 1931 by Frances Jordan Chapin. The school acquired its first permanent location in April 1951. In 1958, the school moved to its current site, having purchased the 5 acre Edgar S. Smith estate, which included the pre-American Revolutionary War Henry D. Phillips House.

The first decade of the "new" Chapin, incorporated in April 1951, saw a growing student body, administrative stability and the acquisition of a permanent site for the school. Following Mrs. Chapin's death, classes were held for three years in a rented house at 11 Mercer Street. In 1954, the school moved to "Snowden," which it leased from Bernard Kilgore, publisher of The Wall Street Journal and The Princeton Packet. In 1958, Chapin moved to its present location in northern Lawrence Township, having purchased the five-acre Edgar S. Smith estate, the centerpiece of which was the pre-Revolutionary War Henry D. Phillips House.

As the school "grew up," curriculum and institutional procedures matured. In 1991 Chapin received accreditation from the Middle States Association of Colleges and Schools, and in 2002, the school achieved dual accreditation from Middle States and the New Jersey Association of Independent Schools.

Facilities

 * Over 50 classrooms
 * 2 technology centers
 * 1 design lab
 * 3 science labs
 * 1 music lab
 * 2 libraries/media centers with 12,000 books and online resources
 * Auditorium
 * Full size gymnasium
 * 3 athletic fields
 * 1 business office with conference room
 * 1 dining pavilion

Recent history
Chapin School launched its most ambitious capital campaign in history in 2012. This consisted of a number of Lower School and Upper School renovations and new facilities including classrooms, science labs, library/media centers and the commons area. By 2015, the capital campaign topped $8 million.

Chapin School built a new pre-school and kindergarten building, the Margaret Wilby Primary Building, replacing the old Pre-K building during the 2006-2007 school year.

Notable alumni

 * Bebe Neuwirth - Star of Cheers and television, movies, and Broadway.

title: Chapin School (New Jersey)


text:
Latin/Stylistic Features of Latin Verse and Prose

=Stylistic Features of Latin Verse and Prose=

This is a brief glossary of stylistic features often found in Latin especially in rhetoric and poetry.

Alliteration
Alliteration is a common poetic technique used in Latin from the earliest surviving fragments to the latest literary age. In alliteration there is a repetition of the initial consonantal letter.

Hyperbaton
Hyperbaton is the arranging of words in a particular manner to produce an effect. Hyperbaton is used often in Latin literature because Latin syntax is far more flexible than English.

Example 2
Analysis: The word 'periculo' separates the words 'magnae' and 'opes' even if it should be used before magnae opes.

Hendiadys
Hendiadys is a rhetorical and poetic technique that uses the juxtaposition of two or more words with a similar meaning to reinforce an idea.

Parallelism
Parallelism is a stylistic device common in Latin in which two sentences have similar syntax.

Example 3
Analysis: In both sentences the nominative is placed first and the principal verb is last.

Chiasmus
Chiasmus is the reverse of parallelism, because syntactic structures are inverted. The name is from the Greek letter Chi which resembles an X and illustrates symmetrical crossing. A good example is the aphorism quod cibus est aliis, aliis est venenum, "What is food to some, to others is poison." The pattern is: noun, verb, pronoun; pronoun, verb, noun.

Litotes
The negation of a verb instead of using an antonym is a poetical device known as litotes. Litotes is much weaker than simply using an antonym. Litotes is often used as underestimation.

Anaphora
The rhetorical figure called anaphora is often used in conjunction with parallelism where the first word in the first sentence of a paragraph or stanza is repeated in the following sentences. It is sometimes used where the initial word in a sentence must be understood in the clauses or sentences that follow.

Example 6
Analysis: timeo is repeated in the sentence, although not strictly necessary

Epistrophe
An epistrophe is a rhetorical device like anaphora except at the end of a sentence.

Asyndeton
As you can see, an asyndeton is a multiple numeration without the "et (and)"

Polysyndeton
This is a numeration with et:

Veni et vidi et vici.

Polysyndeton is marked by the repeated use of the same conjunction (et...et...et) or (neque...neque...neque). It is the direct opposite of asyndeton (listing with no conjunctions).

Pluralis modestiae
This is an advanced technique, often used in ancient fabulae, by Aesop and others.

It means that the Plural is used to show "modestia", for example

"officium magnum e nostro est."


text:
National Register of Historic Places listings in Lancaster County, Pennsylvania

This is a list of the National Register of Historic Places listings in Lancaster County, Pennsylvania.

This is intended to be a complete list of the properties and districts on the National Register of Historic Places in Lancaster County, Pennsylvania, United States. The locations of National Register properties and districts for which the latitude and longitude coordinates are included below, may be seen in a map.

There are 209 properties and districts listed on the National Register in the county. The city of Lancaster is the location of 57 of these properties and districts; they are listed separately, while the 153 properties and districts in the other parts of the county are listed here. One property straddles the Lancaster city limits and appears on both lists. Another three sites are further designated as National Historic Landmarks. Yet another property was once listed but has been removed.

Exclusive of Lancaster

 * }

Former listings

 * }


text:
Spy (1781 ship)

Spy was built in France in 1780, almost surely under another name, and taken in prize. The British East India Company (EIC) purchased her in 1781 and used her for almost two years as a fast packet vessel and cruiser based in St Helena. It then sold her and she became a London-based slave ship, making two voyages in the triangular trade carrying enslaved people from West Africa to the West Indies. She then became a whaler, making seven whaling voyages between 1786 and 1795. She was probably wrecked in August 1795 on a voyage as a government transport.

EIC packet
One source states that Spy was built in the Thames for the EIC, but that appears to be a mistake. The EIC had her surveyed before purchasing her. The same source states that she sailed to Bombay and Bengal. Actually, she never sailed east of the Cape of Good Hope (the Cape). The EIC stationed her at St Helena and had her patrol in nearby waters.

Spy, John Sherwood, master, sailed from Gravesend on 13 December 1781, and Portsmouth on 6 February 1782 and arrived at St Helena on 13 June. She sailed from there on 18 August and returned on 7 September. She sailed from St Helena on 23 September and returned on 11 October. She sailed from St Helena on 16 November and returned on 6 December. She sailed from St Helena on 10 March 1783 and returned on 1 April. She sailed on 17 May and returned on 1 June. On 8 September she was at the Cape and she returned on 7 October. She returned to the Downs on 8 December. She was back at London by 16 December.

One source states that in 1784 the EIC sent Spy out to St. Helena and stationed her there permanently as a guard ship. It did not. Instead, it sold her to Camden and Calvert, who went on to employ Spy as a slave ship.

Transporting enslaved people
The preeminent database on the trans-Atlantic slave trade confuses two vessels. It gives Spy the origins and dimensions of Stag, of 337 tons (bm). Stag was launched in 1774 in France and captured circa 1779. It then attributes to Stag the burthen (200 tons), of Spy. The probable source of the confusion is that in 1786 Captain Thomas Wilson transferred from Spy to Stag, which had been renamed Spy in 1784, with the change of name not making it into Lloyd's Register until 1787.

1st voyage transporting enslaved people (1784-1785): Captain Thomas Wilson sailed from London on 12 August 1784. Spy started acquiring captives on 1 December at Cape Coast Castle. She sailed from Africa on 1 March 1785 and arrived at Montego Bay, Jamaica on 4 May with 350 captives. She sailed from Jamaica on 24 June and arrived back at London on 23 August.

2nd voyage transporting enslaved people (1785–1786): Captain Thomas Wilson sailed from London on 28 September 1785. Spy acquired captives at Cape Coast Castle and then at Anomabu. She embarked 450 in all and left Africa on 26 March 1786. She arrived at Grenada with on 20 May with 430 captives, having lost 20 on the voyage. She disembarked 424. She arrived back at London on 1 August.

On her return her owners, Camden & Calvert, decided to try whaling instead of continuing transporting enslaved people. Captain Wilson transferred to another Spy, the former Stag, and continued transporting enslaved people.

Whaler
1st whaling voyage (1786–1787): Captain J. Brown sailed from London on 31 August 1786, bound for the Brazil Banks. Spy returned on 22 June 1787 with 10 tuns of sperm oil, 55 tuns of whale oil, and 38 cwt of whale bone.

Calvert & Camden sold Spy to King & Co.

2nd whaling voyage (1787–1788): Captain Thomas Wyer (or Wier) sailed from London on 4 December 1787, bound for the Brazil Banks. Spy returned on 19 August 1788 with 50 tuns of sperm oil.

3rd whaling voyage (1788–1789): Captain William Fitch sailed from London in 1788, bound for the coast of Africa. In January 1789 she and several other whalers, including Lord Hawkesbury, were "all well" off the coast of Guinea. In June she had 240 barrels of spermaceti oil. Spy returned on 25 August 1789 with 56 tuns of sperm oil. In 1789 she underwent repairs.

4th whaling voyage (1789-1791): Captain Fitch sailed from London on 12 November 1789. Spy returned on 10 January 1791.

5th whaling voyage (1791-1792): Captain Fitch sailed in 1791. On 3 February 1792, Spy, Fitch, master, was at the Cape of Good Hope, together with Lucy,  Chaser, and several other whalers. Spy returned to England on 25 June 1792.

Apparently Calvert & Co. were once again owners of Spy.

6th whaling voyage (1792-1793): Captain Fitch sailed in 1792, bound for Brazil. Spy returned on 5 April 1793 with 105 tuns of whale oil and 75 cwt of whale bone.

7th whaling voyage (1793-1795): Captain Fitch sailed from London on 17 October 1793, bound for the coast of Peru. Spy returned on 26 July 1795.

Fate
LR continued to carry Spy through 1797, but with stale data. However, a Spy, Howard, master, was lost in the last week of August near Dungeness. She was outbound as a government transport; her crew were rescued. A second report had her running on shore at Dymchurch. She had been carrying men from the 3rd Regiment (The Old Buffs), who were safely landed.

title: Spy (1781 ship)


text:
puhdistaa

Verb

 * 1)  To clean (up), clear (up), cleanse, purge, scour.
 * 2)  To refine, purify.
 * 3)  To purify air, water.

title: puhdistaa


text:
Vendlincourt

Vendlincourt is a municipality in the district of Porrentruy in the canton of Jura in Switzerland.

History
Vendlincourt is first mentioned in 1136 as Uuandeleincurt.

Geography
Vendlincourt has an area of. Of this area, 5.12 km2 or 55.8% is used for agricultural purposes, while 3.45 km2 or 37.6% is forested. Of the rest of the land, 0.59 km2 or 6.4% is settled (buildings or roads), 0.02 km2 or 0.2% is either rivers or lakes.

Of the built up area, housing and buildings made up 3.1% and transportation infrastructure made up 2.1%. Out of the forested land, all of the forested land area is covered with heavy forests. Of the agricultural land, 46.1% is used for growing crops and 8.8% is pastures. All the water in the municipality is in lakes.

The municipality is located in the Porrentruy district.

Coat of arms
The blazon of the municipal coat of arms is Azure, a Fleur-de-lis in chief between a Saltire Or.

Demographics
Vendlincourt has a population of. , 7.6% of the population are resident foreign nationals. Over the last 10 years (2000–2010) the population has changed at a rate of -6%. Migration accounted for -6.9%, while births and deaths accounted for 1.7%.

Most of the population speaks French (566 or 91.7%) as their first language, German is the second most common (28 or 4.5%) and Italian is the third (10 or 1.6%).

, the population was 51.1% male and 48.9% female. The population was made up of 249 Swiss men (45.8% of the population) and 29 (5.3%) non-Swiss men. There were 249 Swiss women (45.8%) and 17 (3.1%) non-Swiss women. Of the population in the municipality, 269 or about 43.6% were born in Vendlincourt and lived there in 2000. There were 122 or 19.8% who were born in the same canton, while 54 or 8.8% were born somewhere else in Switzerland, and 74 or 12.0% were born outside of Switzerland.

, children and teenagers (0–19 years old) make up 25.3% of the population, while adults (20–64 years old) make up 54% and seniors (over 64 years old) make up 20.7%.

, there were 241 people who were single and never married in the municipality. There were 309 married individuals, 39 widows or widowers and 28 individuals who are divorced.

, there were 214 private households in the municipality, and an average of 2.5 persons per household. There were 67 households that consist of only one person and 23 households with five or more people. , a total of 207 apartments (80.5% of the total) were permanently occupied, while 29 apartments (11.3%) were seasonally occupied and 21 apartments (8.2%) were empty. , the construction rate of new housing units was 3.7 new units per 1000 residents. The vacancy rate for the municipality,, was 6.3%.

The historical population is given in the following chart:

Politics
In the 2007 federal election the most popular party was the CVP which received 31.86% of the vote. The next three most popular parties were the SVP (22.71%), the SPS (21.53%) and the FDP (18.29%). In the federal election, a total of 172 votes were cast, and the voter turnout was 39.5%.

Economy
, Vendlincourt had an unemployment rate of 2.8%. , there were 30 people employed in the primary economic sector and about 11 businesses involved in this sector. 139 people were employed in the secondary sector and there were 10 businesses in this sector. 35 people were employed in the tertiary sector, with 16 businesses in this sector. There were 280 residents of the municipality who were employed in some capacity, of which females made up 45.0% of the workforce.

the total number of full-time equivalent jobs was 181. The number of jobs in the primary sector was 25, of which 22 were in agriculture and 3 were in forestry or lumber production. The number of jobs in the secondary sector was 132 of which 109 or (82.6%) were in manufacturing and 23 (17.4%) were in construction. The number of jobs in the tertiary sector was 24. In the tertiary sector; 5 or 20.8% were in wholesale or retail sales or the repair of motor vehicles, 2 or 8.3% were in the movement and storage of goods, 8 or 33.3% were in a hotel or restaurant, 1 was in the information industry, and 1 was a technical professional or scientist.

, there were 140 workers who commuted into the municipality and 154 workers who commuted away. The municipality is a net exporter of workers, with about 1.1 workers leaving the municipality for every one entering. About 26.4% of the workforce coming into Vendlincourt are coming from outside Switzerland. Of the working population, 7.1% used public transportation to get to work, and 57.5% used a private car.

Religion
From the, 369 or 59.8% were Roman Catholic, while 64 or 10.4% belonged to the Swiss Reformed Church. Of the rest of the population, there were 8 members of an Orthodox church (or about 1.30% of the population), and there were 55 individuals (or about 8.91% of the population) who belonged to another Christian church. There were 4 (or about 0.65% of the population) who were Islamic. 11 (or about 1.78% of the population) belonged to no church, are agnostic or atheist, and 133 individuals (or about 21.56% of the population) did not answer the question.

Education
In Vendlincourt about 155 or (25.1%) of the population have completed non-mandatory upper secondary education, and 33 or (5.3%) have completed additional higher education (either university or a Fachhochschule). Of the 33 who completed tertiary schooling, 54.5% were Swiss men, 27.3% were Swiss women.

The Canton of Jura school system provides two year of non-obligatory Kindergarten, followed by six years of Primary school. This is followed by three years of obligatory lower Secondary school where the students are separated according to ability and aptitude. Following the lower Secondary students may attend a three or four year optional upper Secondary school followed by some form of Tertiary school or they may enter an apprenticeship.

During the 2009–10 school year, there were a total of 44 students attending 3 classes in Vendlincourt. There were no kindergarten classes in the municipality. The municipality had 3 primary classes and 44 students. There are only nine Secondary schools in the canton, so all the students from Vendlincourt attend their secondary school in another municipality.

, there were 7 students in Vendlincourt who came from another municipality, while 34 residents attended schools outside the municipality.

Transportation
Vendlincourt is located on the Porrentruy–Bonfol railway line and has regular service at the Vendlincourt railway station.

title: Vendlincourt


text:
Neal Dodson

Neal Dodson (born May 17, 1978) is an Independent Spirit Award-winning film producer. His producer credits include the Academy Award-nominated Margin Call, the Golden Globe Award-winning and Academy Award-nominated All Is Lost starring Robert Redford, the comedy Breakup at a Wedding, the dramas Aardvark and Viper Club, and the film A Most Violent Year starring Oscar Isaac and Jessica Chastain, which won Best Picture from the National Board of Review. Dodson executive produced Another Cinderella Story starring Selena Gomez and Jane Lynch, Banshee Chapter starring Katia Winter, Hollidaysburg starring Rachel Keller, Jonathan starring Ansel Elgort, Love On A Limb starring Ashley Williams and Marilu Henner, Never Here starring Mireille Enos and Sam Shepard, and Periods as well as co-producing Hateship, Loveship starring Kristen Wiig. Dodson also produced and appeared in the Starz documentary filmmaking television series The Chair, which followed two filmmakers making the same film, and was created by producer Chris Moore.

Dodson frequently collaborates with the filmmaker J.C. Chandor through their CounterNarrative Films production company, as well as with actor and producer Zachary Quinto through their Before the Door Pictures production company, founded in 2008 with longtime friends Quinto and Corey Moosa.

Dodson was born and raised in York, Pennsylvania, where he attended Central York High School. He went to college in Pittsburgh at the Carnegie Mellon School of Drama. After working as an actor in regional theatre and on Broadway in Tom Stoppard's Tony Award-winning production of The Invention of Love, he became a feature film producer.

He is married to actress Ashley Williams and they have two sons: Gus and Odie. They split their time between New York and Los Angeles. Dodson is the brother-in-law of country music star Brad Paisley and Ashley's sister, actress Kimberly Williams-Paisley.

Filmography

 * Another Cinderella Story (2008)
 * Margin Call (2011)
 * Breakup at a Wedding (2012)
 * All Is Lost (2013)
 * The Banshee Chapter (2014)
 * A Most Violent Year (2014)
 * The Chair (2015) (documentary TV series)
 * Hateship, Loveship (2015)
 * Aardvark (2017)
 * Never Here (2017)
 * Jonathan (2018)
 * Viper Club (2018)
 * Triple Frontier (2019)

title: Neal Dodson


text:
Talk:HTML/Basic formatting

Headline text
saramas page link title$$Insert formula here$$ Insert non-formatted text here --<IP_ADDRESS> 11:58, 10 April 2007 (UTC)#REDIRECT Insert text

When to use emphasisxitalics and when strongxbold
In the previous lesson is explained how to empasise text by or strong emphasis. So what is the difference to italics tag ' and bold tag '''? When to use emphasis and when italics?--Juan 08:30, 24 October 2008 (UTC)

and tags deprected
These two tags were deprected, so I think the activity should be removed.--Juan 08:33, 24 October 2008 (UTC)

title: Talk:HTML/Basic formatting


text:
Solberge Hall Hotel

Solberge Hall near Northallerton, North Yorkshire, England, is a wedding and events venue offering exclusive use to couples. The house is a Georgian house of historical significance. It was built in 1824 by John Hutton, a local landowner. It remained in the Hutton family for about one hundred years and was then purchased by Benjamin Talbot the inventor. After an extensive multi-million pound refurbishment and restoration programme, Solberge Hall is now a wedding and events venue set in a private estate in North Yorkshire.

The Hutton family
John Hutton (1794–1857) built Solberge Hall in 1824. He was born in 1794 in Newby Wiske. His father was Robert Hutton and his mother was Margaret Squire. The Huttons purchased Sober Gate adjacent to Solberge Hall in 1684. In 1812 when John was eight years old, his father died, leaving him and his sister Margaret in the care of their mother at Sober Gate. John inherited the property when he came of age, and in 1821 he bought Solberge Manor from George Osbaldeston, the cricketer. In 1824, he built Solberge Hall, which for many years was called Sowber Hill. John lived with his sister Margaret until her death in 1833 at the age of 36. He erected an elaborate memorial to her in St Michael’s and All Angels Church in North Otterington. It was considered to be an artistic work and the British Museum holds an illustration of the monument.

In 1845 at the age of 50, Hutton married Caroline Robson, the daughter of Thomas Robson of Holtby Hall. The couple had two sons. When John died in 1857, he was described in the York Herald as being "in all respects a real English country gentleman. He was applauded for his innovative agricultural activities, as some of his experiments in crop growing and animal feeding were adopted by others and assisted in production.

The eldest son, John Hutton (1847–1921), inherited Solberge Hall. He was educated at Eton and Oxford University. In 1870, he married Caroline Shore, the daughter of Charles John Shore, 2nd Baron Teignmouth. They had a son, John, who became a Member of Parliament. He also served on North Riding County Council.

In 1913 John put Solberge Hall on the market and Benjamin Talbot bought the property

Benjamin Talbot
Benjamin Talbot, inventor and steel company manager, moved into Solberge Hall in about 1913. The following year he became a magistrate for the North Riding. Talbot (1864–1947) was born in 1864 at Hadley in Shropshire. He was the second son of Benjamin Talbot who owned the Castle Ironworks in Wellington. After he finished school he worked in his father’s ironworks. In 1884 he married Frances Ann Chapman and moved to USA for ten years where he invented new techniques in the production of steel. Talbot returned to England in 1900 and his new inventions were introduced into some of the English Steel Companies. In 1907 he became managing director of Cargo Fleet Iron Company and transformed it into a profitable firm. He was a director of several other steel companies. For his inventions he was awarded the Bessemer gold medal of the Iron and Steel Institute, the Elliott Cresson gold medal, and the John Scott medal of the Franklin Institute. In 1928 he was elected president of the Iron and Steel Institute and served as president of the National Federation of Iron and Steel Manufacturers.

Talbot had four children one of whom was Viva Talbot. She was 13 when she came to Solberge Hall where she lived with her parents until she married in 1941 at the age of 41. She was a notable artist and was given an exhibition of her woodcuts depicting her father's steelworks.

Benjamin Talbot died in 1947 and the following year Solberge Hall was sold. It is now owned and operated by the Wharfedale Group.

title: Solberge Hall Hotel


text:
Third Munda ministry

This is a list of minister from Arjun Munda cabinets starting from 11 September 2010 to 18 January 2013. Arjun Munda is the leader of Bharatiya Janata Party was sworn in the Chief Ministers of Jharkhand on 11 September 2010. Here is the list of the ministers of his ministry.

Arjun Munda along with two minister, took oath of office on 11 September, one minister from Jharkhand Mukti Morcha and one from minister from All Jharkhand Students Union.

On 8 October 2010 the cabinet was expanded with introduction of three ministers from the Bharatiya Janata Party, four ministers from Jharkhand Mukti Morcha and one minister each from All Jharkhand Students Union and Janata Dal (United).

title: Third Munda ministry


text:
User:Sanokharbazar

About Sanokhar

Sanokhar is a Village in Sonhaula Block in Bhagalpur District of Bihar State, India. It belongs to Bhagalpur Division. It is located 36 KM towards East from District head quarters Bhagalpur. 8 KM from Sonhaula. 259 KM from State capital Patna

Sanokhar Pin code is 813204 and postal head office is Ekchari.

Madarganj ( 5 KM ), Arar ( 6 KM ) , Amdanda ( 6 KM ) , Bansi Pur ( 7 KM ) , Ekchari ( 9 KM ) are the nearby Villages to Sanokhar. Sanokhar is surrounded by Mehrma Block towards East, Colgong Block towards North , Mahagama Block towards South , Thakurgangti Block towards East.

Colgong, Bhagalpur , Naugachhia , Godda are the near by Cities to Sanokhar.

This Place is in the border of the Bhagalpur District and Godda District. Godda District Mehrma is East towards this place. It is near to the Jharkhand State Border.

Demographics of Sanokhar

Maithili is the Local Language here.

Politics in Sanokhar

Bharatiya Janata Party, INC , BJP , JD(U) , RJD , LJP are the major political parties in this area.

Polling Stations /Booths near Sanokhar

1)Uchcha Vidyalay Sanokhar Pashchim Bhag

2)Urdu Prathamik Vidyalay Lakshmipur Chache

3)Prathamik Vidyalay Urdu Maheshamunda Uttari Bhag

4)Utkrmit Madhya Vidyalay Sonudih

5)Madhya Vidyalay Madadanda

HOW TO REACH Sanokhar

By Rail

Ekchari Rail Way Station is the very nearby railway stations to Sanokhar. Nathnagar Rail Way Station (near to Bhagalpur), Kahalgaon Rail Way Station (near to Colgong) , Ekchari Rail Way Station (near to Colgong) , Bhagalpur Rail Way Station (near to Bhagalpur) are the Rail way stations reachable from near by towns.

By Road

Colgong, Bhagalpur are the nearby by towns to Sanokhar having road connectivity to Sanokhar

Colleges near Sanokhar

Tarar Mahavidyalaya Tarar
 * Locality Name : Sanokhar (	सनोखर )  Block Name : Sonhaula District : Bhagalpur   State : Bihar   Division : Bhagalpur   Language : Maithili and Hindi, Urdu   Current Time 10:58 AM	  Date: Tuesday, Aug 01,2017 (IST)	  Time zone: IST (UTC+5:30)   Elevation / Altitude: 41 meters. Above Seal level   Telephone Code / Std Code: 06429   Assembly constituency : Kahalgaon assembly constituency   Assembly MLA : Sadanand Singh   Lok Sabha constituency : Bhagalpur parliamentary constituency   Parliament MP : Shailesh Kumar Urph Bulo Mandal   Pin Code : 813204   Post Office Name : Ekchari

title: User:Sanokharbazar


text:
Pramod Jain Bhaya

Pramod Jain Bhaya is an Indian National Congress politician from the state of Rajasthan. He Is Former Cabinet Minister for Mines and Cow Rearing in the Third Ashok Gehlot ministry. He is a three-time MLA, having previously served as an MLA from 2003 to 2008 and as a minister from 2008 to 2011 during the 2008 to 2013 term.

Constituency
He represents the Anta Assembly constituency from Rajasthan.

title: Pramod Jain Bhaya


text:
Petros Bourdoulis

Petros Bourdoulis (born 13 September 1970 in Georgian SSR) is a Greek former wrestler who competed in the 1992 Summer Olympics and in the 1996 Summer Olympics.

title: Petros Bourdoulis


text:
Eye-talian

Adjective

 * 1)  Italian, usually in reference to an Italian American or Italian American culture.

Usage notes
The spelling represents a pronunciation of Italian with rather than  or.

title: Eye-talian


text:
User:Comeez

Pierce Wong

Pierce Wong, a Change Management Guru, academician and Social Media Specialist, born in Sibu in 1973, the youngest among three siblings, a faithful christian, the owner of a blog Significant Blogging.

Elected as the Pro Tem Deputy Chairman of TM Net Sarawak User Group on 21 March 2006.

Secretary General of Sarawak Social Media Association

title: User:Comeez


text:
whitten

Etymology
English, used in mid-16th century; variant of.

Noun

 * 1) Any of several small trees having leaves that are white and downy underneath.

title: whitten


text:
Japanese/Kana/Lessons/Hiragana/Lesson 2

In this lesson you are going to learn how to read and write か, き, く, け, こ. Adding two small lines called dakuten, but commonly known simply as  tenten, meaning "two marks", causes clear sounds to change to their voiced sound. Thus, adding the tenten marks will cause か, き, く, け, and こ to produce が, ぎ, ぐ, げ, ご.

Clear Sounds
日语/假名/平假名/第二課

title: Japanese/Kana/Lessons/Hiragana/Lesson 2


text:
Plato/Apology

Whether or not to abide by the laws and decrees of one's own country is the question addressed by Plato's "Apology." Socrates was accused and found guilty of "corrupting the youth." For this he was sentenced to death. With hindsight, and based on what we have remaining written by Socrates' friends and supporters, it appears that Socrates was unjustly accused, tried, and condemned.

Socrates points out that he voluntarily remained in his country. He participated in government appropriately. For these reasons (and others) he felt he was rationally obliged to abide by the laws and decrees.

Was Socrates right? How does this message apply to us today?

For people living in a free and open society, Socrates' argument may well be every bit as applicable today as it was 2500 years ago in Athens.

One should note that Socrates might well have saved his own life had he tempered his thoughts with a more remorseful tone. Socrates refused to compromise his principles -- i.e., that he should say precisely what he thought -- and thus he forfeited his life. In this, Socrates poses an enduring example of authenticity and integrity.

We should also note that Socrates never failed to challenge the worldview of his listeners. The Apologia, in which he suggests that, rather than killing him, the State should sustain him as a pensioner, is an example of his bold but internally-consistent style of argument. For this alone, even if his logical and philosophical contributions are ignored, Socrates' greatness should be recognized and respected.

title: Plato/Apology


text:
Hernando de Santana

Hernando de Santana (born in the 1510s, Zafra, Badajoz Province, Spain - year of death unknown) was a Spanish conquistador, founder of the city of Valledupar on January 6, 1550, and conqueror in what is now northern Colombia.

title: Hernando de Santana


text:
Category:St. Boniface Saints (baseball) players

This is for players of the St. Boniface Saints minor league baseball team, who played in the Northern League in 1915.


text:
Talk:C Programming/Basics of compilation

Does anyone else think this page should go away or at least be moved? Thunderbunny 21:55, 11 Dec 2004 (UTC)

What more content is required for it to be complete? Its completion status is 25% since ages. Anuvrat (discuss • contribs) 18:33, 5 September 2011 (UTC)
 * Agreed. The completeness status is now 75% --Strange quark (discuss • contribs) 02:50, 26 May 2017 (UTC)

define the term "header" before using it.
for the chapters "Preprocessor" and "Automation". Utonsal (discuss • contribs) 22:57, 31 December 2018 (UTC)

section "Automation": "Makefiles" -- a program or some files?
… I first understood it being a program, but in the next paragraph it appears in plural, so that I then had to assume, that these are files. so: what is it?


text:
Emma Ekwall

Emma Amalia Ekwall (18 January 1838 – 1 February 1925) was a Swedish painter.

Life and career
Born in Gransbo, Småland, she was the daughter of the official Nils Fredrik Ekvall and Emelie Bernhardina Carolina Djurström and the sister of Knut, Gustaf, and Hugo Ekwall.

Ekwall studied at the Royal Swedish Academy of Fine Arts, Stockholm between 1865 and 1871. The latter year also saw her become the first woman to receive a royal medal. After her studies, she went abroad, spending time in Munich and Leipzig. She most notably painted portraits, as well as flowers and children, some of which are on display at Nationalmuseum.

In 1925, Ekwall died in Stockholm, at the age of 87.

title: Emma Ekwall


text:
gereja

Etymology
From. , from, from , from.

Noun

 * 1) A Christian house of worship; a building where Christian religious services take place.
 * 2) A particular denomination of Christianity.
 * 1) A particular denomination of Christianity.

Etymology
, from, from , from.

Noun

 * 1)  church a house of worship

title: gereja


text:
Cookbook:Albanian Fried Meatballs

| Cuisine of Albania | Meat Recipes

Fried meatballs (qofte të fërguara) is an Albanian dish.

Ingredients

 * 1 slice stale bread
 * 1 lb ground meat
 * 1 small onion, finely-grated
 * 2 tablespoons chopped feta cheese
 * 2 tablespoons bread crumbs
 * 2 tablespoons oil or melted butter
 * 1 tablespoon chopped parsley
 * Salt
 * Pepper
 * Mint
 * Oregano
 * 1 cup flour
 * 1 cup oil (olive oil recommended)

Procedure

 * 1) Soak bread in water and squeeze hard to drain.
 * 2) Combine soaked bread, ground meat, bread crumbs, oil or melted butter, onion, cheese, parsley, salt, pepper, and mint, and mix thoroughly.
 * 3) Form mixture into 1 inch-thick patties, then sprinkle with salt, pepper, and oregano.
 * 4) Roll in flour and fry in hot oil.
 * 5) Serve hot with French fries or mashed potatoes.

title: Cookbook:Albanian Fried Meatballs


text:
User:Gatoclass/SB/Continental Iron Works

new

 * nanking frame

refs

 * - align="left"
 * align="center" |
 * align="right" |
 * - align="left"
 * align="center" |
 * align="right" |
 * - align="left"
 * align="center" |
 * align="right" |
 * - align="left"
 * align="center" |
 * align="right" |
 * - align="left"
 * align="center" |
 * align="right" |
 * - align="left"
 * align="center" |
 * align="right" |
 * - align="left"
 * align="center" |
 * align="right" |
 * - align="left"
 * align="center" |
 * align="right" |
 * - align="left"
 * align="center" |
 * align="right" |
 * - align="left"
 * align="center" |
 * align="right" |
 * align="center" |
 * align="right" |
 * - align="left"
 * align="center" |
 * align="right" |
 * - align="left"
 * align="center" |
 * align="right" |
 * align="center" |
 * align="right" |
 * align="right" |

 * 1200 men
 * lathe
 * day dream, works description etc cozzens mystic nyherald engine engine, works description etc

 * nuevo cubano launch
 * nanking frame
 * american welding co buys machine tools 1927 taken over by aw co

 * photo battle of hampton roads

 * extent of works 1903

 * shells for spanish-american 1898 torpedo shells
 * torpedoes 1898
 * 1500 under harrison 1896
 * boiler furnaces of maine
 * lucious a smith
 * worden image
 * union gas light 1890

 * incorporation details 1887

 * monadnock frame 1886

 * minelayer david bushnell 1885
 * atlantic first steel hulled ferry in us and brooklyn

 * 200 cf gasometer 1880

 * fulton gas works 1880
 * complete gas works
 * tanks for wood treatment 1877
 * activities june 1874 inc. pittsburgh gas works
 * catskill montauk 1874?

 * nassau 1872
 * various gasworks 1871
 * new foundry 1870, biggest gasworks in US ny gas works
 * bridge? 1869 looks like it yep

 * comm officers monitor book
 * suspension furnaces ad 1907
 * welded seam pioneer
 * muscoota contracted 1863
 * world's largest gasometer 1888
 * still at west and calyer 1918

 * warren e. hill president after rowland

 * products 1911 with photos - buoys, wood digesters, boilers, pipes, water drums
 * 175 employess 1927

 * later history, depth charge casings, munitions, gas pipes and water mains
 * james fisk jr?
 * boilers for 2 cruisers by columbian iron works, patapsco river 1890
 * first us thorneycroft boilers for USS Cushing 1889
 * world's largest gasometer 1888
 * cauldrons, vat cars 1875
 * lifecars, torpedoes 1874 more lifecars
 * farragut fulton quintard engines
 * atlantic brooklyn quintard?
 * reason for corrugations in boiler furnaces (more further in)
 * monitor builders neptune version
 * us navy ship sponsors
 * pioneer in welding 1874
 * image 1898
 * 1901 advert
 * monitor correspondence
 * "brief sketch of monitor and its inventor"
 * bushnell's account
 * cohoes engine
 * weiss 1920
 * wooden tanks for monitor
 * tin can on a shingle


text:
Barrington Hall, Essex

Barrington Hall is a Grade II* listed 18th-century English country house in Hatfield Broad Oak, Essex, England. Barrington Hall is built in red brick, in both two and three storeys, with a balustraded parapet and a number of ornamentally shaped Dutch gables. The south front of the house has a central block centrepiece with carved figures. It was Grade II* listed in 1975, its listing stating: "c.1734 and mid C19. Of red brick with stone dressings and rusticated stone quoins."

History
The original manor of Hatfield Broad Oak was bought by Sir Francis Barrington in 1612. The Barringtons were the hereditary woodwards (foresters) of Hatfield Forest. Prior to 1600 the family seat was an earlier Barrington Hall, which once stood on a moated site north of the village of Hatfield Broad Oak. In 1735, John Shales Barrington succeeded his cousin the 5th Baronet Barrington to the estate. He began to build a new Georgian manor but the plan was not concluded until after his death and the house was not occupied on a permanent basis until 1863. After his death, the house was owned by Sir Fitzwilliam Barrington. The Barrington family sold their interest in Hatfield Forest in 1832 to John Archer Houblon after the death of Sir Fitzwilliam Barrington.

In 1863, the Hall was still not occupied; it was inherited by George Alan Lowndes, a distant relative of the Barringtons. Lowndes adopted the surname after inheriting the estate; previously, his patronymic was Clayton. He arranged to have it remodeled in a neo-Jacobean style to the design of Edward Browning and lived at Barrington until his death in 1904. The property was then sold in 1908 to Alfred Gosling, whose family held it until selling it to the British Livestock Company in 1977 for use as offices. Following this, in 1980 the hall was sold to Contemporary Perfumers Ltd. In 2012 the property was offered for sale for £5,000,000, and in 2014 it was purchased by the developer Silvertown Properties. After an extensive restoration it was listed for sale in 2019 with a guide price of £15,000,000 including 41.25 acres of grounds.

title: Barrington Hall, Essex


text:
User:Eligio Budde

Sign below if you watched this. :^) —————————————————————————————

 * Wei4Green | 唯绿远大 (talk) 19:25, 28 March 2019 (UTC)

title: User:Eligio Budde


text:
Wikipedia:Sockpuppet investigations/Slade121/Archive

Suspected sockpuppets

Grosseteste is a sock created by the person also editing as Slade121. In short, both profiles have: I would add more, but I still haven't shaken the headache from the deafening quacks.... Guliolopez (talk) 01:05, 17 September 2019 (UTC)
 * been blocked for socking. While Slade121 is still blocked, Grosseteste is not. I'd advocate that the latter block be restored.
 * identical userpages. Compare Grosseteste's to Slade121's
 * identical circles of interest. Effectively Grosseteste's entire edit history overlaps with that of Slade121
 * made materially the same edits months/years apart. Compare Grosseteste's edit here with Slade121's here and here.

 * Update It has been pointed out to me (by the unblocking admin and editor him/herself) that the editor has "never once denied" using multiple profiles. But has not done so consecutively. And has not done so illegitimately. In a way that would contravene WP:SOCKLEGIT. However, given that the very first thing this latest profile was used for was a less than constructive/collegiate talkpage attack (which, effectively, led to a block), and the most recent thing the profile was used for was to reopen a long-closed editwar, I'm less than convinced that SOCKLEGIT applies. And, perhaps, that there may be an issue with misuse of a clean start. Anyway, I am leaving this SPI thread open. And will let the closing admin make a determination. Guliolopez (talk) 10:54, 17 September 2019 (UTC)

Comments by other users

Clerk, CheckUser, and/or patrolling admin comments

 * Closing based on administrative history. Bbb23 (talk) 14:38, 20 September 2019 (UTC)