text:
Linux in a Windows World/Sharing Files and Printers/Basic Samba Configuration
From WikiContent
(Initial conversion from Docbook)
Current revision (23:06, 11 March 2008) (edit) (undo)
(Initial conversion from Docbook)
Current revision
All major Linux distributions ship with Samba, the Server Message Block/Common Internet File System (SMB/CIFS) server for Unix-like systems. This server package enables Linux to serve files and printers to Windows clients, providing a reliable and low-cost platform to fill this role. In fact, despite some fundamental differences between the Linux/Unix and Windows platforms, Samba handles its duties so well that Samba servers are often more trouble-free than their Windows counterparts, so network administrators have sometimes gone to great lengths to deploy Linux running Samba rather than Windows in this role.
This chapter describes basic Samba configuration, starting with installing the server. Other topics include the configuration file format, how you identify the server to other computers on the network, minimal options to help Samba get along with other systems in terms of its browsing features, and setting password options. You must set these basic features before you can move on to the next topic, configuring file and printer shares; that topic is covered in Chapter 4.
An experienced Samba administrator who's familiar with the local network can set all the options described in this chapter in just a minute or two. Many of these options require some time to fully describe because of changes in SMB/CIFS over time and because of peculiarities of integrating SMB/CIFS with Linux's traditional networking tools, but you'll change only a handful of Samba configuration file options. If you're impatient to get started, pay particular attention to Section 3.3.2 and Section 3.5.
Installing Samba
Samba isn't a single server; rather, it's a family of servers that together provide the full functionality of the package. (Nonetheless, references to "the Samba server" or similar phrases are common.) Four daemons provide the most important Samba features.
- smbd
- This daemon handles the file- and printer-serving functions per se. Clients connect to it using TCP port 139 or 445 to request the transfer of files.
- nmbd
- This daemon handles most of the SMB/CIFS functionality not provided by smbd, including NetBIOS name resolution (as described in Section 3.3) and browsing features (as described briefly in the Section 3.4 and in more detail in Chapter 5). Iff you run smbd, chances are you'll also run nmbd. This server binds to UDP ports 137 and 138.
- The Samba Web Administration Tool (SWAT) provides a web-based GUI administration tool for Samba. Running it isn't necessary, and I don't describe it further in this book. It can be a handy tool for new Samba administrators, though, and it provides some functions that can help ordinary users, such as an interface to change their passwords. It usually runs on TCP port 901.
- Winbind
- This daemon, which is also known as winbindd, provides a way for Linux to access NetBIOS name and Windows NT domain information. The main upshot is that a system that runs Winbind can authenticate its local users against the Windows domain's user database, as described in Chapter 7. Although Winbind is a daemon, it isn't a server for other computers; it enables extra functionality solely for the computer on which it runs.
In addition to these daemons, Samba provides a number of support utilities and client programs. These include the smbclient client program, which provides FTP-like access to SMB/CIFS shares; the smbmount utilities, which helps you mount SMB/CIFS shares in Linux; and the smbpasswd utility for handling Samba passwords. Some of these tools are described in this chapter, but others are covered elsewhere in this book.
Most Linux distributions deliver these programs in one or more packages. Typically, a base package is called samba or samba-common. Additional functionality often ships in other packages, such as samba-clients or swat. Consult your distribution's package list and descriptions to learn what you need to install for the functionality you require. Alternatively, you can download and install Samba from its own web site, http://www.samba.org. This site's download area provides links to binaries for many distributions and to a source code tarball that should compile on any Linux distribution. (Just one source tarball contains all the major Samba components described here.)
Samba (or at least the smbd and nmbd daemons) is typically launched through SysV startup scripts, and these usually install from the distribution's main Samba package. If you installed Samba from a source tarball, though, you'll need to create your own SysV startup script, run Samba from a local startup script, or launch Samba manually on an as-needed basis. (The packaging subdirectory of the Samba source package includes sample SysV startup scripts for several distributions.) Although it's possible to run Samba from a super server such as inetd or xinetd, doing so is uncommon and isn't recommended. In fact, nmbd tends to be a bit difficult to run in this way.
A few features related to SMB/CIFS aren't part of the main Samba package. Most notably, the ability to mount SMB/CIFS shares on a Linux system is built into the Linux kernel, although it relies on the external smbmount command, which is part of the Samba package. Some GUI SMB/CIFS network browsers are also available separately. Many of these tools nonetheless rely on the basic Samba configuration described in this chapter for certain default values.
The Samba Configuration File Format
Before delving into Samba configuration, you should understand the Samba configuration file format. This file is called smb.conf , and it's typically located in /etc/samba, although a few distributions (particularly old ones) place it in some variant location, such as /etc/samba.d or /etc. When you compile from source code, it goes in /usr/local/samba/lib unless you change a configuration option.
Wherever it's located, the smb.conf file is broken into several distinct sections, each of which has its purposes. Within each section, lines have a simple structure consisting of a parameter that's to be set and one or more values to be assigned to the parameter, or they may be comment lines. You should also understand the use of Samba variables, which enable you to set a parameter to a value you may not know when creating the configuration file.
Configuration File Sections
Example 3-1 shows a short but complete smb.conf configuration file. In this file, the section names appear between square brackets ([ ]). In this example, the section names are [global], [homes], and [freefiles].
Example 3-1. A short smb.conf file
[global] workgroup = GREENHOUSE netbios name = MANDRAKE server string = Free files for all encrypt passwords = Yes security = User os level = 2 domain master = No preferred master = No domain logons = No [homes] browseable = No writeable = Yes # Put all our public files in a logical place.... [freefiles] path = /usr/share/samba/public browseable = Yes writeable = No
The [global] section of smb.conf is the only section that's really required. It sets global-level parameters that affect the operation of the server as a whole, such as setting its NetBIOS name and password encryption settings. In addition, you can place most share-level parameters in the [global] section, in which case the parameter effectively changes the default behavior. For instance, the writeable parameter is share-level, meaning that you can set it differently for each share. If placed in the [global] section, though, this parameter sets the default for the rest of the shares. This can be handy if you have many shares that use similar options; rather than set the same parameter in all the shares, you can set it just once, in the [global] section.
Sections after the [global] section—the [homes] and [freefiles] sections in Example 3-1—all define individual Samba shares. Each share definition begins with its name and ends with the next share definition or the end of the file. All the parameters in a share definition must be share-level parameters.
Frequently, the share names are not indented, while parameters belonging to a share are indented. This practice makes it easy to locate the parameters you want to adjust, but it's not required; Samba ignores most whitespace in smb.conf, including indentation of configuration lines.
Parameters, Values, and Comments
If you examine Example 3-1, you'll quickly discern the basic form of an smb.conf parameter line:
parameter = Value
The parameter is a keyword that holds particular meaning to Samba. Some Samba functions can be accessed through multiple parameter names; for instance, writeable is synonymous with writable and write ok, and read only is an antonym for these. In other words, writeable = Yes has the same effect as read only = No.
The Value is the value that's assigned to the parameter. Several different types of values exist:
- Boolean values
- Many Samba parameters require Boolean options. For these, Yes, True, and 1 are all synonymous, while No, False, and 0 are their opposites. A few Booleans also accept other options to set a feature automatically or have some other parameter-specific effect.
- Numeric values
- Some parameters take numeric values, such as a time in seconds or a file size in bytes or kilobytes. Both integral and real numeric values are possible, although some parameters expect one type or the other. Some parameters take values that are special numbers or sets of numbers, such as IP addresses.
- String values
- You can provide strings to some parameters, such as the values of the workgroup, netbios name, server string, and path parameters in Example 3-1. Sometimes these strings can be almost anything you like, as in server string. Other strings must be constrained in some way, though; for instance, path is a local Linux pathname. When a string value contains spaces, you do not normally need to enclose it in quotes, although you can do so if you prefer. Quotes may also be necessary with lists of string items that contain spaces.
- Delimited values
- Some parameters accept a limited range of strings as values. For instance, Example 3-1 shows the security parameter, which accepts just a handful of values.
- Lists
- Many parameters accept multiple values as options, such as several IP addresses or hostnames. Lists are normally delimited by commas or spaces, although a few parameters use other characters as delimiters.
For the most part, Samba doesn't care about the case of its parameters or values; domain master = No has the same effect as DOMAIN MASTER = no or any other variant. Some values, though, are case-sensitive for reasons other than Samba. For instance, a Linux filename provided as a value is case-sensitive because the underlying Linux filesystem is case-sensitive.
Similarly, parameters aren't sensitive to whitespace; you can insert or remote spaces from parameters without causing problems. For instance, server string = Free files for all is identical to serverstring = Free files for all. Whitespace may be important to parameters' values, though.
If a configuration line is very long, you can break it across multiple lines by ending the first line (and any subsequent nonterminal lines) with a backslash (\):
hosts allow = daisy.greenhouse.example.com, 172.24.21.27, \ 192.168.7.107
This example sets the hosts allow parameter to three values—a hostname and two IP addresses.
Instead of or in addition to a parameter and value, an smb.conf line may hold a comment. These are denoted by a hash mark (#) or a semicolon (;); Samba ignores lines that begin with one of these characters. (Whitespace before comments is ignored.) Many sample smb.conf files contain numerous comments describing the function of each configuration line in the file.
Samba provides a parameter called comment. This is not to be confused with a comment! The comment parameter sets a free-form string that's associated with a share for the benefit of users.
Variables and Their Uses
In most cases, you can set a Samba parameter to a constant value. All the parameters in Example 3-1 do this. Samba also supports variables as parameter values. A variable is a placeholder, denoted by a leading percent symbol (%), that can take on a particular value depending upon the machine on which Samba is running, the Samba version, the username of the person accessing the share, and so on. Table 3-1 summarizes Samba's variables. Note that variable identifiers are case-sensitive; for instance, %d and %D are distinct variables.
Table 3-1. Samba variables
|The client's OS. Possible values are OS2 (OS/2), Samba, UNKNOWN, WfWg (DOS or Windows for Workgroups), Win2K (Windows 2000), Win95 (Windows 9x/Me), or WinNT (Windows NT).
|A print job's length in pages, if known.
|The daemon's process ID number.
|The client's workgroup or NT domain name, if known.
|The sender of a WinPopUp message.
|The primary group of %u.
|The primary group of %U.
|The server's DNS hostname, if known.
|The home directory of %u
|The client's IP address.
|A print job's name.
|The server's NetBIOS name.
|The client's NetBIOS name, if known.
|The client's DNS hostname, if known.
|The NIS home directory server.
|The path to an automounted share's root directory.
|The path to the share's root directory.
|The level of the SMB protocol in use. Legal values are CORE, COREPLUS, LANMAN1, LANMAN2, and NT1.
|A filename. In printer shares, this identifies the file passed by the client to be printed. It can also refer to a file that holds a WinPopUp message.
|The share's name.
|A WinPopUp message's destination.
|The current date and time.
|The effective Linux username. This may not be the same as %U.
|The username sent by the client.
|Samba's version number.
|A print job's size in bytes.
|The value of the environment variable envvar.
You can use a variable much as you'd use any other value in a parameter. It will be expanded to its full replacement value when Samba needs to do so. You can even combine variables with regular text or with other variables. For instance, consider the following parameter:
log file = /var/log/samba/log.%m
A line like this is a common sight in the global sections of smb.conf files. If the client's NetBIOS name is DAISY, Samba logs information on accesses by this client in /var/log/samba/log.daisy. (Samba usually converts NetBIOS names to lowercase.) If Samba doesn't know the client's NetBIOS name, the IP address is substituted for the NetBIOS name. Separating logfiles in this way can be handy when debugging problems or tracing usage patterns for the server.
Some environment variables aren't guaranteed to be available. For instance, %L is only available if the client uses the NetBIOS over TCP/IP (NBT) method of connecting to the server, using TCP port 139. This variable is meaningless or will return an IP address for a client that uses the newer "raw" SMB/CIFS over on TCP port 445. Similarly, %h and %M work correctly only if your network's DNS server is working correctly. Variables that convert IP addresses to DNS names also require you to set the hostname lookups = Yes parameter to work correctly. Some parameters have meaning only in particular contexts; for instance, %S is meaningless when used with global parameters because a share name can apply only to an individual share and not to the system as a whole.
The include Parameter
Normally, a Samba server uses a single smb.conf configuration file; however, you can use the include parameter to merge in multiple files. This parameter takes a filename as an option. Samba reads the specified file and uses its contents as if they were part of the main smb.conf file, at the location of the include parameter.
Typically, you pass a variable as part of the filename that you give to include. You can use this ability to provide customized configurations for different client computers, client OSs, users, and so on. For instance, you can set options that adjust the server's delivery of filenames to clients (as described in Chapter 4) based on the client OS:
include = /etc/samba/smb-%a.conf
You then create files called smb-Win95.conf, smb-Samba.conf, or other appropriate values, and place OS-specific options in each file. You can place such a call in the [global] section or in a share definition. In fact, you can even place entire share definitions in an included configuration file. This type of configuration can be useful when one OS works better with one set of options than another. For instance, you might want to set different case-sensitivity options depending on the client OS's capabilities.
Identifying the Server
The first task you must undertake when configuring a Samba server is setting various identification options. SMB/CIFS was designed for non-TCP/IP networks and includes server identification tools that are independent of common TCP/IP naming systems, such as DNS hostnames. SMB/CIFS machines are identified by NetBIOS names, and computers belong to workgroups or NT domains (an NT domain is simply a workgroup with some extra features). Although most recent SMB/CIFS clients can contact servers using DNS hostnames or raw IP addresses rather than NetBIOS names, you must give your Samba server a NetBIOS name and a workgroup (or NT domain) name for interaction with older clients, such as DOS and Windows 9x systems. You may also want to adjust a few additional identification options, which tell the system what operating system to pretend to be, among other things.
NetBIOS Name Options
A NetBIOS name is similar to a computer's DNS hostname (without the domain name component). It's a string of up to 15 characters that can contain letters, numbers, and various punctuation marks. (Using punctuation can be confusing, though, and so is usually best avoided.) NetBIOS names are case-insensitive, although I generally present them in all-uppercase in this book to distinguish them from DNS hostnames, which I present in lowercase.
Technically, the NetBIOS name as just described is only the base of the NetBIOS name. The full NetBIOS name includes a one-byte code that identifies the type of service available under the name; for instance, a NetBIOS name might end with a hexadecimal 0x20 to signify a file or print service. A single computer is likely to register several NetBIOS names using a single NetBIOS base name and different type codes. Samba handles this automatically; you just give it the NetBIOS base name, and it registers the names required based on other smb.conf options.
You set your computer's NetBIOS name with the global netbios name parameter:
netbios name = MANDRAKE
If you don't include this parameter in the smb.conf file, the default is to use your computer's DNS hostname, minus the domain component. For instance, if your computer is called mandrake.greenhouse.example.com, Samba registers the NetBIOS name MANDRAKE. This default is usually reasonable, assuming your DNS hostname is set correctly; however, you may want to set the NetBIOS name explicitly just to be sure. (When you do so, this setting overrides the DNS hostname for NetBIOS purposes but not for other TCP/IP protocols.) In most cases, you shouldn't try to use different NetBIOS and DNS names on a single computer because it will most likely confuse your users.
Occasionally, you may want to give a computer multiple NetBIOS names. Samba supports this option via the global netbios aliases parameter, which enables you to specify names to be registered in addition to the name provided with netbios name (or the DNS hostname, if you omit netbios name from your smb.conf file). For instance, suppose that MANDRAKE should also be known as MANDRAGORA and MANDRAGORIN>. You can do so by using the following line in addition to the netbios name line shown earlier:
netbios aliases = MANDRAGORA MANDRAGORIN
You can use this parameter to give a system multiple NetBIOS names if it also has multiple DNS hostnames. You can also use it to consolidate several servers in one. For instance, if you replace two old file server computers with one new server, you can have the new server appear under both names by assigning one name with netbios name and the second with netbios aliases. You'll need to define file or printer shares to match those found on both original servers, though.
If you use the %L variable as part of a filename in an include parameter, you can load different shares depending on which NetBIOS name a client uses to address the server. This can help minimize user confusion should you want to consolidate many servers into one; to users, your single server can look like the two old ones, complete with different shares available under each name. Be aware, though, that many newer clients, including Windows 2000 and XP, no longer use NetBIOS names by default, so this trick may not be useful on all networks. Specifying smb ports = 139 limits Samba to using port 139, and hence NetBIOS and its naming conventions. This forces the desired behavior even with most newer clients.
NetBIOS name resolution can work in any of several ways. The most common methods are broadcast name resolution and a NetBIOS Name Server (NBNS) computer, a.k.a. a Windows Internet Name Service (WINS) system. In broadcast name resolution, a client sends a broadcast that contains the name of the system it wants to contact, and that system responds to the broadcasts. Broadcast name resolution is easy to configure (no special Samba parameters are required), but it doesn't work well in networks with multiple subnets.
If your network includes an NBNS system, you should point Samba at it with the global wins server parameter, which requires the IP address (or DNS hostname, if you also set hostname lookups = Yes) of the NBNS system:
wins server = 172.24.21.1
Samba 3.0 and later supports multiple NBNS systems (separated by spaces or commas on the wins server line).
Conceptually, you can consider an NBNS system to be much like a DNS server; clients contact it to turn names into IP addresses. Unlike a DNS server, though, an NBNS system requires no explicit configuration to add hostnames to it. Instead, clients contact the NBNS system when they start up and at various times thereafter in order to register their configured names. The wins server parameter has the dual effect of telling Samba (or nmbd, to be more precise) to register with the NBNS system and to use that system for NBNS lookups, when they're required.
While you're setting the wins server option, you should check to be sure that wins support is set to No. If this value is Yes, Samba attempts to operate as an NBNS system. This is likely to cause confusion if your network has an existing NBNS system. Of course, if you really want your computer to take on these duties, you should set wins support = Yes, but, in this case, you should omit the wins server parameter; Samba knows to refer to itself for this function when it's configured as an NBNS system.
You can tell Samba which name lookup methods to use with the name resolve order parameter, which takes an ordered list of one to four values:
- lmhosts
- This option tells Samba to use an lmhosts file, which is conceptually and structurally similar to an /etc/hosts file: it's a list of IP addresses and associated NetBIOS names, one per line. The file is typically stored in the same directory as smb.conf.
- host
- This option refers to lookups using the computer's normal TCP/IP hostname lookup mechanisms—typically /etc/hosts and DNS. This lookup method doesn't work for some service types, so you shouldn't rely on it exclusively.
- wins
- This option refers to NBNS-based lookups; it requires that you set wins server (or wins support = Yes).
- bcast
- You can have Samba perform broadcast name resolution with this option.
The default name resolution order is lmhosts host wins bcast, but you can remove options or change their order by specifying them with name resolve order:
name resolve order = wins bcast lmhosts
This example causes NBNS lookups to be tried first, followed by broadcasts, followed by lmhosts lookups. In this example, ordinary TCP/IP hostname lookups are not attempted by Samba.
Workgroup Name Options
The NetBIOS naming system is basically flat; all computers on a network have names in the same namespace, with no hierarchical structure. This contrasts with DNS names, which provide for an arbitrary number of domains and subdomains. NetBIOS avoids name conflicts primarily by restricting the scope of the network; NetBIOS name broadcasts don't normally pass over routers, and NBNS computers typically serve just one organization's computers.
NetBIOS does provide the illusion of a two-tiered structure, though, through the use of workgroups and NT domains. On a conceptual level, a workgroup is a collection of computers that are related in some way, such as those in a single department. On a technical level, workgroups are implemented by having members of the workgroup register NetBIOS names based on the workgroup name and using particular service type codes.
In any event, you must tell Samba the name of the workgroup to which it belongs. You do this with the global workgroup parameter, which takes a workgroup name as its value. These names follow the same naming rules as NetBIOS machine names, but because the computer's DNS domain name is less likely to be a suitable substitute, it's not used as the default value. Instead, the default if you omit the workgroup parameter is a compile-time option, but it's usually WORKGROUP.
If you fail to set the computer's workgroup correctly, you may not be able to browse to the server from Windows clients, or the server may appear under its own unique workgroup in the clients' browsers. Thus, it's important that you set this option appropriately for your network. If you're configuring a new network, select a workgroup name as you see fit. Perhaps your organization's domain name will work, or maybe a subdomain name will be more appropriate. In some cases, you might even use something unrelated, but to avoid confusion, it's usually best to employ a DNS domain or subdomain name as the workgroup name.
Windows NT domains are just workgroups with a special server, the domain controller, which handles centralized logons and typically some other tasks. If you use a domain configuration, you set the NT domain name using the workgroup parameter.
Miscellaneous Identification Options
In addition to setting the NetBIOS name, workgroup name, and related options, you may need to attend to a few miscellaneous identification parameters. These can affect how other systems interact with your Samba server:
- server string
- This parameter sets a free-form string that appears along with the NetBIOS name in many operating systems' network browsers. In fact, in Windows XP, this string is more prominent than the NetBIOS name.
- protocol
- This parameter sets the maximum protocol level that Samba uses. (The %R entry in Table 3-1 describes the values that this parameter accepts.) Chances are you won't need to change this value, but it's conceivable that downgrading will help when dealing with very old clients.
- announce as
- You can tell Samba to announce itself as any number of different Windows OSs with this parameter. Legal values are NT Server (the default), NT (a synonym for NT Server), NT Workstation, Win95, and WfW. As with protocol, chances are you won't need to adjust this parameter except perhaps with some very old clients, which might not be able to cope with newer settings.
- announce version
- This parameter sets an OS version number that goes along with the announce as value. The default value for recent versions of Samba is 4.9, and this should almost never be changed.
Chances are you'll only want to set the server string parameter, which has a direct effect on clients. This is shown in Figure 3-1, which depicts a Windows XP computer's view of the servers on a network using the My Network Places browsing tool. In most cases, the NetBIOS name appears in parentheses after the value of the server string variable. (HALRLOPRILLALAR Figure 3-1 is an exception because it lacks the server string value, or rather, it lacks its equivalent because this computer is the Windows computer used to take the screen shot.) Many default smb.conf files place the %v variable in the server string parameter, which has the effect of displaying the Samba version number to clients, as in the TEELA server in Figure 3-1. This information, though, can be useful to miscreants wanting to break into the computer. To be sure, they can discover the version in some other way, but there's no point in making it easy for them; I recommend not using %v in your server string parameter.
Figure 3-1. Windows displays the value of the server string variable alongside the NetBIOS name in its network browser
Setting Master Browser Options
In order to handle local network browsers like the one shown in Figure 3-1, SMB/CIFS requires one computer to be designated a master browser . This computer collects data on the computers on the network and provides it to any computer that asks for the information. The clients then present the data to users in one form or another (Figure 3-1 being one example).
In the context of SMB/CIFS, a network browser is a tool that provides information about, and typically a way to access, SMB/CIFS file and printer shares. Typically, it's integrated into the OS's local file manager. In Windows, it's called either My Network Places or Network Neighborhood, depending on the version of Windows. SMB/CIFS browsers use different protocols from web browsers. Although some programs, such as the K Desktop Environment's (KDE's) Konqueror, can serve as both SMB/CIFS and web browsers, the two protocols are entirely unrelated.
In fact, two types of SMB/CIFS master browsers exist. A local master browser handles browsing tasks on a single subnet. A domain master browser helps integrate multiple subnets. The local master browser is selected automatically by the computers on a network using a process known as an election . Samba provides options that influence how it participates in elections; you can "rig" an election so that Samba wins or loses it, as you see fit. Domain master browser status is acquired based on server configuration, and Samba provides options to control this process, as well. Chapter 5 describes these parameters in more detail. For the moment, though, if you don't want Samba to acquire either type of master browser status, you should add the following parameters to your smb.conf file's [global] section:
domain master = No local master = No os level = 0 preferred master = No
In fact, the first two options should be sufficient to keep Samba from acquiring master browser status; the last two options simply provide added insurance, should you accidentally mis-set the local master parameter. Of course, on some networks you might want Samba to acquire local master browser status; to do so, set the following options:
local master = Yes os level = 33 preferred master = Yes
Configuring Samba to become a local master browser on a network on which browsing works fine may cause problems. If Samba acquires master browser duties over a working master browser, the result can be disruptions should that old system try to reacquire master browser status periodically. Each such attempt to reacquire master browser status will result in a temporary browsing outage. Likewise, network topology and other issues can cause problems when changing a master browser. If in doubt, configure Samba to not try to take on these duties.
Setting Password Options
New Samba installations are frequently plagued by two problems: incorrectly set workgroup names and password encryption difficulties. The first problem is easily corrected by changing the workgroup parameter, as described earlier. Password problems are harder to overcome because they may require changing more than just one or two Samba parameters. To address these issues, you must first understand them. You must then decide whether to use unencrypted or encrypted passwords. On some networks, you may need to decide whether to use a password server for authentication, as well.
Password Issues
Samba password issues can be complicated. SMB/CIFS provides several different ways to encode passwords, to authenticate clients using passwords, and to store them. In fact, some of these issues are negotiated between client and server, with no need for explicit configuration, but others require your attention.
The simplest case of Samba password handling, at least from the point of view of Samba administration, is to have Samba accept unencrypted (or cleartext) passwords from clients and authenticate users against the local Linux account database. Conceptually, this works much like Linux authentication for FTP, Telnet, SSH, or other servers that use the Linux account database. Unfortunately, this approach has some problems. Most importantly, exchanging passwords in cleartext makes them vulnerable to sniffing—interception by unauthorized third parties who have physical access to your network wires. (In an Internet exchange, sniffing can also occur on intervening routers or their networks.) Thus, unencrypted passwords are undesirable from a security point of view. (On the other hand, the password encryption systems used by some versions of SMB/CIFS are not much better than cleartext, so you shouldn't consider encrypted passwords to be proof against sniffing.) In terms of practicality, cleartext passwords are also a problem because recent versions of Windows use encrypted passwords by default and don't drop back to cleartext passwords. Although you can reconfigure Windows clients to use cleartext passwords, doing so on a large network can be tedious.
So, what about encrypted passwords? Unfortunately, the password encryption systems used by SMB/CIFS aren't compatible with the encrypted form of Linux passwords used in a standard Linux password database (/etc/passwd or, more commonly, /etc/shadow). Therefore, in order to support SMB/CIFS encrypted passwords, Samba must maintain its own password database. Typically, this database is stored in a file called smbpasswd and is located in the same directory as smb.conf or a subdirectory of that directory. Other methods of storing this database exist but are beyond the scope of this book. If you want to use encrypted passwords, you must not only configure Samba to use them but create the encrypted password file, populate it with account information, and assign passwords to users. Because the Linux passwords are stored in a hash (basically, a one-way encryption system), they can't be decrypted, and you'll need to either assign random Samba passwords to users or have them enter passwords in some way. This task can be tedious on a large network.
A third approach to handling passwords is to defer to another computer. For instance, if your network is configured as a Windows NT domain or an AD domain, you can have Samba defer to the domain controller. This approach greatly simplifies Samba setup because you don't need to configure a local password database. Samba provides several options for how to defer to a remote system.
No matter what method you use, each user of your system must have a local account. (Using guest accounts can relax this restriction, but this topic is beyond the scope of this book.) Thus, you must still create local Linux accounts even if you use a Windows domain controller for authentication. If this task is tedious because you have many users, you may want to consult Chapter 7, which describes joining a Linux system to an NT domain in a way that enables the underlying Linux accounts to mirror the NT domain's accounts. Although this configuration can be a bit tricky to set up, it can greatly simplify account maintenance on a large network that has an NT domain controller (either a Windows system or a Samba server).
Using Cleartext Passwords
From a Samba configuration perspective, the simplest authentication method is to use cleartext passwords. You can do so by setting encrypt passwords = No in the [global] section of smb.conf. This configuration is the default in Samba versions prior to 3.0; however, with Version 3.0, the default setting changed to Yes. To avoid confusion, I recommend setting the value explicitly, whatever version of Samba you're using. When configured to use cleartext passwords, Samba doesn't attempt to negotiate an encrypted password exchange with clients; it does attempt to authenticate users against the passwords stored in the local Linux password database. Thus, users must have valid local Linux passwords, not just valid accounts. (With encrypted passwords, Samba users' accounts could conceivably exist but have disabled local passwords.)
Windows versions since Windows 95 OEM Service Release 2 (OSR2) and Windows NT 4.0 Service Pack 3 (SP3) require the use of encrypted passwords by default. Thus, these OSs will not work with a Samba server configured to use cleartext passwords unless you change a Windows Registry entry. One relatively painless way to do so is to use a .reg file that ships with Samba. In fact, several such files exist, one for each version of Windows. The filename takes the form Win Ver_PlanPassword.reg, where Ver is the Windows version. For instance, Win2000_PlainPassword.reg is the file for Windows 2000, and WinXP_PlainPassword.reg does the job for Windows XP. Some distributions deliver these files in compressed form, so .gz may be tacked onto the end; if so, you'll need to uncompress the file with gunzip before you use it. Precisely where you can find these files also varies. Most place them in the Registry subdirectory of the Samba documentation directory, as in /usr/share/doc/samba-3.0.2a/full_docs/Registry, but the precise path varies.
Try using your distribution's package management tools to locate these files. For instance, on a computer that uses the RPM Package Manager (RPM), you could type rpm -ql samba | grep PlainPassword to locate the files in the samba package that contain the string PlainPassword in their names.
Once you've located these files, copy the ones you need to a floppy disk, put them on an FTP site, send them via email, or otherwise make them accessible to clients. On a Windows system, double-click the file from the file manager to install the changes in the Registry. You then need to reboot the computer for the changes to take effect. In a small office, you should be able to apply the patch to all the Windows clients in a few minutes by walking from one system to another with a floppy disk in your hand. Alternatively, you can make the changes manually using a Windows Registry editor; however, applying the changes automatically is almost certain to be both faster and more reliable.
Once you've configured the Samba server and your clients to use cleartext passwords, the clients should be able to access the server, assuming appropriate accounts with valid passwords exist on the server. However, a few additional parameters can affect access:
- password level
- Linux's local passwords are case-sensitive, but many SMB/CIFS clients assume passwords will be treated in a case-insensitive way. For instance, Windows 9x/Me converts all passwords to uppercase when using certain SMB/CIFS protocol levels. In order to work around this problem, the global password level parameter tells Samba to try case variants. The default value for this parameter is 0, which causes Samba to try the password as delivered and the password converted to all-lowercase if it was sent in all-uppercase. Higher values cause Samba to convert the password to lowercase and then to convert the specified number of letters to uppercase. For instance, if password level = 1 and if a client gives RHUMBA as the password, Samba tries to authenticate the user with passwords of RHUMBA, rhumba, Rhumba, rHumba, and so on. Using high numbers as the password level parameter can therefore improve the odds of a successful login using a valid password that's been corrupted by the client. These attempts increase the time for Samba to confirm that a password is invalid, though, and, in some cases, to verify a valid password. They also increase the odds of a successful break-in by effectively eliminating case as a security feature in your local passwords.
- username level
- This global parameter is similar to password level, but it applies to usernames rather than passwords. One other minor difference is that when this parameter is set to its default value of 0, Samba tests the username converted to lowercase followed by the username converted to lowercase but with an initial capital letter. If you give higher values, Samba tries up to the number of letters converted to uppercase that you specify, just as with password level.
- username
- This share-level parameter specifies a list of usernames against which to test a password. This is necessary when using some very old clients (such as some antiquated DOS clients) that don't send usernames, just passwords. Samba tries the password with each of the usernames specified. Ordinarily, this parameter isn't needed because all modern clients deliver usernames by default. This parameter can be used with encrypted passwords as well as with cleartext ones, but because the clients most likely to force its use employ unencrypted passwords, I've described it here.
On the whole, using cleartext passwords is normally undesirable on modern networks. Between the increased risks of password sniffing with cleartext passwords, and the fact that most modern SMB/CIFS clients don't use them by default, you're usually better off switching to an encrypted password system or to a password server. Encrypted passwords can be more of a hassle to configure on the Samba server, but they're easier to configure on the clients.
Using Encrypted Passwords
Because all modern versions of Windows use encrypted passwords by default, this approach is the easiest one from a client configuration point of view. You will, though, need to take some steps to get encrypted passwords working on the server.
From a client perspective, the difference between using encrypted passwords on the file or print server and using a password server is nil. In both cases, the client engages in a challenge-response authentication exchange with the file or print server; only the configuration of that file or print server differs.
Only one smb.conf entry needs changing to use encrypted passwords: encrypt passwords = Yes. This is the default value for Samba 3.0 and later, but earlier versions used No as the default, so I recommend setting it explicitly to avoid confusion. A few other parameters can influence how Samba treats encrypted passwords, but they probably don't need adjustment:
- smb passwd file
- You can tell Samba what file to use for holding encrypted passwords with this global parameter. Ordinarily, Samba uses a file called smbpasswd, which is usually located in the same directory as smb.conf or a subdirectory thereof.
- passdb backend
- This parameter tells Samba how to store its password database. The usual value, smbpasswd, specifies that the smbpasswd file (or another file specified by smb passwd file) be used. Other options tell Samba to use more specialized types of databases, such as an LDAP directory. Fully describing these alternatives is beyond the scope of this book.
- lanman auth
- The LANMAN hashing scheme is one of several SMB/CIFS encrypted authentication systems. This global Boolean parameter enables or disables support for this protocol. The default value is Yes, and the parameter must be set to this value to support Windows 9x/Me systems.
- ntlm auth
- The NT LANMAN (NTLM) hash is an improvement on LANMAN authentication, and this parameter controls whether Samba accepts this authentication method. The default value is Yes. If this option and lanman auth are both set to No, only the newest NTLMv2 protocol will work; however, this protocol was added only to Windows NT 4.0 SP4; older clients (and many non-Microsoft clients) don't support NTLMv2.
In addition to setting encrypt passwords = Yes and, if desired, any ancillary password-related parameters, you must prepare a local Samba password database. This database is maintained using the smbpasswd command. In particular, you add users to the database using the -a parameter (which can only be used as root):
# smbpasswd -a linnaeus New SMB password: Retype new SMB password: Added user linnaeus
This command adds a Samba password entry for the user linnaeus. If your system lacks a current smbpasswd file or its equivalent, you'll see an error message to the effect that it doesn't exist; but don't fear, the smbpasswd utility creates the file and adds the user to it. In any event, you should repeat this command for every user on your system. Note that Samba requires the username to match an existing Linux account, so if you're configuring a new system, you should create a Linux account first, and then create a Samba password database entry for it.
Running smbpasswd in this way isn't very difficult for a network with just a few users, but on a larger network, it can be quite tedious. If you want to script the operation, you can deliver a password to the utility within a script by appending the password to the username, separated by a percent symbol (%):
smbpasswd -a linnaeus%apassword
Of course, your script will need to generate passwords in some (preferably random) way. You'll then need to either communicate this information to your users or help them enter their passwords later. Another option is to use a script called mksmbpasswd, mksmbpasswd.sh, or something similar. These scripts create a new smbpasswd file from your regular Linux passwd database. Such scripts used to ship with Samba packages, but they're less common today, perhaps because they save very little time. The scripts can't convert Linux passwords to a form that SMB/CIFS can use, so they deliberately generate accounts with invalid passwords. Thus, you must still help users enter their encrypted passwords manually.
In theory, the global update encrypted parameter can help you enter encrypted passwords. When set to Yes, this parameter causes Samba to set a user's encrypted password to the value of an unencrypted password that a client computer sends when the user logs on. Unfortunately, this requires you to configure your clients to send unencrypted passwords. Thus, although update encrypted might help you convert a network from cleartext to encrypted passwords, it won't be of much help when adding a new Linux system to an existing network that already uses encrypted passwords.
The case options described earlier, in Section 3.5.2, are inapplicable to encrypted passwords. Depending on the hash chosen by the client, passwords may be case-sensitive or -insensitive, and Samba provides the same case sensitivity as clients. Thus, in this respect encrypted passwords are simpler than unencrypted passwords.
The smbpasswd command can be used to change passwords for existing accounts, as well as create new ones. Type smbpasswd username, where username is the username whose password you want to change, to do the job. Individual users can also use this utility to change their passwords, but they must have shell access to the server to do so.
If users don't need shell access to the server, you can set their login shells to /usr/bin/smbpasswd. When users log in using Telnet or SSH, they'll enter their Linux passwords and then be prompted to change their Samba passwords. Once this is done, they're immediately logged out.
Using a Password Server
Instead of using a local password database, you can defer authentication to another computer—typically a domain controller, but perhaps some other system. In fact, Samba provides three different ways to do this. You choose the method using the security parameter, but depending upon the method you choose, you may need to perform some additional configuration steps.
All these methods of authentication require you to set encrypt passwords = Yes. Instead of maintaining the account database locally, though, you point Samba at an external server.
Setting the security mode
The security parameter tells Samba what security mode to use—that is, what rules to apply for authenticating users. This parameter takes one of five possible values:
- Share
- When using this security level, Samba attempts to emulate the default access control method of Windows 9x/Me, which is to assign passwords to individual shares and not use usernames. To do this, Samba tries to authenticate using the password that the client sends and a series of different accounts, such as an account used by a previous logon from the client or the name of the share itself. Share-level security is a poor match to Linux's underlying security model, though, and so it's seldom used.
- User
- This security model is the default, and it corresponds to the use of a local account database—either a cleartext Linux account database or an encrypted Samba account database, depending on the value of encrypt passwords.
- Server
- When using server-level security, Samba authenticates users against a remote server in much the way that Windows 9x/Me servers do. On a technical level, this authentication method is similar to a man-in-the-middle attack; the Samba server essentially passes the data on from the client as if it were making the logon request, then honors the reply from the server. This approach is easy to configure but occasionally doesn't work correctly. It can be used to authenticate against a server that's not a domain controller, but the remote server must be configured to enable remote authentication. This option is being deprecated in Samba 3.0 and later; it still works, but is likely to eventually vanish.
- Domain
- In a domain-level configuration, the Samba server fully joins an NT domain, much as Windows NT/200x/XP systems do. Samba can then exchange credentials with the domain controller and use the full NT domain authentication system for its users.
- This is the latest authentication method. It links Samba to a Windows 200x Active Directory (AD) controller and uses native AD protocols for authentication. This system is also the most difficult to configure and isn't fully described in this book.
If you use server-, domain-, or ADS-level security, you must tell Samba where to find the password server. This task can be accomplished with the global password server parameter, which accepts a list of one or more names or IP addresses. If you specify a name, it's looked up in the order specified by the name resolve order parameter. If you use domain- or ADS-level security, the remote servers must be domain controllers. Alternatively, you can specify an asterisk (*) to have Samba attempt to locate its domain controller automatically.
Don't use the password server parameter or domain- or ADS-level security on a system that you configure as a domain controller. Such systems should use user-level security and should omit the password server parameter.
Using server-level security
Server-level security can be a quick way to use a remote password server. This configuration requires you to enter options like this:
security = Server password server = 172.24.21.98
Of course, you'd adjust the IP address for your own network. Little else is required for this configuration, at least on the Samba server that users access directly. You must ensure that appropriate user accounts exist on the password server system, though. Those accounts must also match the local Linux user accounts on the Samba server you're configuring; using a remote password server doesn't obviate the need to provide local Linux accounts for Samba's use.
Windows networks frequently employ longer usernames than do Linux systems; for instance, CarlLinnaeus rather than linnaeus. If your password server uses such usernames, you can map them to conventional Linux usernames with the username map parameter. This parameter accepts a filename that contains mappings of Linux to Windows usernames, as in linnaeus = "Carl Linnaeus". When Samba receives a logon request from CarlLinnaeus, it authenticates against the password server using that name but uses the local linnaeus account. Although you can use this parameter with user-level security, it's most frequently employed with server-, domain-, or ADS-level security.
Using domain-level security
A more complex configuration than server-level security looks nearly identical to it in smb.conf:
security = Domain password server = 172.24.21.98
However, this configuration requires joining the Samba server to the domain using the net command. You can accomplish this task by passing the join subcommand to net:
# net join member -U adminuser
In this example, the system is joined as a member of the domain specified by the workgroup parameter in smb.conf and controlled by the domain controller pointed to by password server. You must specify an account to use on the domain controller for this operation with the -U parameter. This account must have administrative access to the domain controller's account database, because it must add a machine trust account for your Samba server. This machine trust account is used in the authentication process for individual user logons.
As a practical matter, domain-level security is a bit tougher to configure than is server-level security, but it's more reliable in some situations. If necessary, you can use the username map parameter, as described in Section 220.127.116.11, to associate Linux usernames with Windows usernames.
Chapter 5 describes configuring a Samba server as a domain controller, including the domain controller configuration options required to enable joining other Samba servers as full domain members.
If you've been making changes to your Samba server's configuration as you've read this chapter, it should now be functioning in a rather minimal way on your network. You should understand the basics of the Samba configuration file format, and you should be able to make your server appear in clients' SMB/CIFS browsers. If at least one share is defined (as is common in sample smb.conf files), you should also be able to log on to the Samba server from clients, thanks to appropriate settings for the password options on both client and server. Of course, these tasks aren't enough; in most cases, you run a Samba server in order to share files or printers, which means you need to be able to define appropriate shares. This task is the topic of Chapter 4.


text:
|Home Software category Just in softwares Submit a program Contact us
Home > Servers::FTP Servers > Wing FTP Server Pro 3.6.6
Wing FTP Server Pro 3.6.6
The most simple and powerful FTP server software for Windows,Linux and MacCompany: FTP
Platform: WinXP,WinVista,WinVista x64,Win7 x32,Win7 x64,Win2000,Windows2000,Windows2003,Wi
Size: 6422 KB
Price: USD $139.00
Release Date: 2010-08-23
Screenshot URL: http://www.wftpserver.com/screenshots/screen1.jpg
Category: Servers::FTP Servers
Wing FTP server is a multi-protocol file server(FTP, HTTP, FTPS, HTTPS, SFTP) for Windows, Linux, Mac, freeBSD and Solaris. It includes a new set of advanced tools (web based remote control, web based client, administrator console, task scheduler). It provides event manager for the program to respond to different events, scripts support let users extend the server by Lua language.
Related keywords:
ftp server ftp server software windows ftp server
Wing FTP Server Pro Related Titles:VShell Server for UNIX 4.3.3 - SSH server providing fine tune control over access and file transfer privileges
VShell Server for Windows 4.3.3 - SSH server providing fine tune control over access and file transfer privileges
icipici FTP server 1.0 - The most powerfull and easy to use FTP Server
Best Used Cars 1.0 - Not too long ago one would not have been so stressed about buying home audio. Ba
Sysax Multi Server 6.19 - Secure FTP Server and SSH2 Secure Shell Server with web based administration
Serv-U FTP Server 126.96.36.199 - Serv-U FTP server includes web, SFTP & FTPS file transfer plus file sharing
TurboFTP Server 1.30.850 - High performance, secure, scalable and management friendly FTP/SFTP server.
FTPshell Server 6.12 - SSH2 Secure Shell Server and Secure FTP Server
Web File Transfer 6.1 - Web file manager to transfer large files
Vision Without Glasses Review 1.0 - Vision Without Glasses Review, proper formation of both internal and external bo
Serv-U 126.96.36.199 - Serv-U FTP server includes web, SFTP & FTPS file transfer. OS: Windows or Linux.
NSF to PSTConversion Tool 4 - Technical expertise not required to run the migration tool to move NSF to PST
Audio & Multimedia Business Communications Desktop Development Education Dwg Converter Games & Entertainment Graphic Apps Home & Hobby Network & Internet News Security & Privacy Servers System Utilities Web Development Others
Copyright © 2000 - 2018 FreeSharewareCenter.com - Freeware and Shareware Download Center.
All Rights Reserved.

subset: commoncrawl


text:
So of course, the last bolt I need to remove is rounded. I figure I have one shot to get it right with a good 6 point socket but accessibility is next to nothing.
So I'd like to hear from all you auto trans removers. This is my first time pulling an auto trans so I don't know any tricks.
What tool configuration do you typically use?
is there anyway to get on this thing good without pulling friggin intake?
Edited by lostinthe202, 30 December 2009 - 03:54 PM.


text:
Attorney Anne Mead is not in Kansas anymore. Recently named partner with the firm of Butler Sevier Hinsley & Reid PLLC, a family law practice, she said, "We have some pretty incredible people working for us, I'm really, really lucky."
The Kansas native attended Washburn University there and moved to Memphis to attend the University of Memphis Cecil C. Humphries School of Law after she and husband, Jay, considered living in other places such as Georgia, South Carolina and Kansas. Her family had moved to Memphis during her time in college, though, and it just felt right to be near them again.
Though she's ended up in the legal profession, her undergraduate degree is in English literature. She says she thought at the time that she wanted to work in the media but, "realized pretty quickly that I probably wouldn't be satisfied either simply writing an article for a newspaper or being on a television broadcast or something like that."
She began thinking realistically about her career options, about how to continue writing yet pay the bills, when a friend suggested she explore the moot court and mock trial team. "I absolutely loved it, loved every single part of it," she said. "To this day I love litigation and I love trial. When I'm litigating something, it's the only time that I ever forget I am something other than a lawyer."
She took the LSAT, what she calls a "horribly scary experience," and then took two years to make sure the decision was the right one. During that time, Mead traveled across the country managing different chapters of her sorority to help them improve, and worked for a law firm as a legal assistant.
She graduated from law school in 2004, was awarded an internship with the Department of Justice and clerked in Division 7 for Judge Robert Lanier. After his retirement, she clerked for several different judges in that division.
"It was such a wonderful experience to get to see how each judge handled their cases differently," she said. "As a lawyer, you will never ever get to see what goes on in chambers and the thought process a judge goes through unless you clerk for a judge."
Eventually the governor appointed Judge Donna Fields to Division 7 and it was a prescient remark by her that would set Mead on the course she's been on ever since. Fields suggested family law, but Mead balked saying, "I don't know if I could do that, to see people divorcing and the impact that would have on children. It would probably be really upsetting and I don't know if I could live with that on a day-to-day basis. She (Fields) said, 'Well that's really why you should do it then.'"
By her estimation, Mead says she sent resumes out to just about everyone in the Memphis Bar Association directory, finally going to work with the firm of Pounders Coleman.
"I couldn't have asked for better teachers than Ms. Pounders and her partner, Ms. Coleman," Mead said.
She worked for the firm for five years before going out on her own for the flexibility that it offered. With new daughter, Madeline, she says, "I didn't want to miss any more of her life."
Mead shared office space with attorneys Bill Burns and Frank Watson, but working on her own presented challenges in itself, from handling the billing to cultivating her own client base.
"It's really interesting when you think about where your clients come from and how you portray yourself to just about everyone you deal with," Mead said, "people at my daughter's school, friends of friends, my dentist, my eye doctor, because as long as they all know what you do, and they like you, they'll refer clients to you. That was honestly how I got a lot of my referrals in the beginning."
In 2011, after a year-and-a-half of this and wanting to spend more time on clients' cases instead of paperwork, she accepted a position with Butler Sevier. It was the same year she completed training to be a Rule 31 Listed Family Mediator, of which the firm has seven in house.
Though she still searches for the time to write just for herself, Mead doesn't feel she's left anything behind and, just as Fields predicted, she loves the work she does despite the heartache.
The reward is "to know that you potentially had a hand in making sure that child is better off despite their circumstances. I am not the architect of the facts, but I can help create a different situation, and a different reality for my clients, going forward."


text:
David Beckham has moved back to London as he looks for his next club, but the son of the former Manchester United and Real Madrid star could yet join a club before his illustrious father.
According to the Daily Mail, 14-year-old Brooklyn Beckham could follow in the footsteps of David Beckham by becoming a professional after it was revealed the youngster is on trial with Chelsea.
Beckham Snr was spotted at Chelsea's Cobham training ground on Tuesday, sparking speculation that the 37-year-old could move to Stamford Bridge, but the ex-England captain was in attendance to watch Brooklyn in an academy game for the Blues.
The presence of the Manchester United legend created a mini Twitter frenzy, with parents watching their children in Chelsea training shocked to see Beckham doing the same in the wintery conditions at the Surrey base.
"Brooklyn is like any teenager with an ambition to be a footballer. He has just returned to England and wanted to see how he fared," an insider is reported to have told the Daily Mail.
"Chelsea are one of the strongest academies in the country. The difference is that he is the son of the former England captain and this will draw attention."
Brooklyn's trial with Chelsea comes on the 20th anniversary of David signing his first professional deal with Manchester United along with the likes of Gary Neville and Paul Scholes.
Two decades later and Beckham is chasing one final contract before retirement, and has been linked with a free transfer to Paris Saint-Germain after leaving LA Galaxy late last year.
Do YOU want to write for GiveMeSport? Get started today by signing-up and submitting an article HERE: https://www.givemesport.com/writeforgms


text:
Classic Blueberry Buckle Recipe
Popular Videos
- 1/4 cup butter, softened
- 3/4 cup sugar
- 1 egg
- 2 cups all-purpose flour
- 2 teaspoons baking powder
- 1/4 teaspoon salt
- 1/2 cup milk
- 2 cups fresh blueberries
- 2/3 cup sugar
- 1/2 cup all-purpose flour
- 1/2 teaspoon ground cinnamon
- 1/3 cup cold butter, cubed
- In a small bowl, cream butter and sugar until light and fluffy. Beat in egg. Combine the flour, baking powder and salt; add to creamed mixture alternately with milk, beating well after each addition. Fold in blueberries. Pour into greased 9-in. square baking pan.
- For topping, in a small bowl, combine the sugar, flour and cinnamon; cut in butter until crumbly. Sprinkle over blueberry mixture.
- Bake at 375° for 40-45 minutes or until a toothpick inserted in the center comes out clean. Cool on a wire rack. Yield: 4-6 servings.
Reviews forClassic Blueberry Buckle
My Review
Average Rating
"Made this for the first time and it was very good, husband liked it also and he is very picky."
"Can this be made with frozen blueberries with similar results. Blueberry season is over."
"I Love it, but I make some changes: black sugar, oatmeal instead of half of the flour, and the result is a delicious and health recipe. many thanks, Ana Lucia"
"This was very good. I added 1 tsp vanilla."
"I just finished making this recipe for the umpteenth time, and It continues to be an all-time family favorite, for sure. It is easy to make, so moist, and delicious. We like to eat it for breakfast with coffee. Today, I made a dozen muffins from the recipe- instead of baking it in a pan- just bake for 18 minutes. I have made this many times to gift to others."
"My husband loves Blueberry Buckle and this is a good recipe."
"This is amazing! So easy, too! My 11 yo daughter and I made it, following the directions exactly, and it came out perfectly and sooooo delicious!!!"
"I liked everything about this recipe except I would definitely cut down on the sugar in the topping to 1/2 cup - I just felt it was a bit too sweet."
"I doubled this recipe and put it in a 13 x 9" pan. This is by far the best buckle recipe I've ever tried! It is now my go-to during blueberry season. The top is super crunchy, and the cake light and delicious. Lots of compliments from my co-workers! My image stays strong--thanks Taste of home!!"


text:
2011/12 model - Worn twice. I think they're a wee bit small for me (I'm usually 8.5). My old Inifiniy (9) boots a a bit loose but seem more comfortable.
Maybe willing to swap or make me a sensible offer - currently RRP is £60
PS. NEVER pee'd in - besides, they're Drylock - wouldn't get in anyway


text:
Spandex Tights - Bad Hair Day (1/7/1996)
Robert Dix is a Philadelphia-based graphic designer and illustrator. He was the illustrator of the comic book 'Spandex Tights', that was written by Bryan Glass and published by Lost Cause between 1994 and 1996. He also drew the 'American Pie' back-up feature with Ray Ramos. In 2004, he contributed to the comic book 'A Bunch of Baboons' by Baboon Books.


text:
Eczema Pictures
Have Eczema? Read more about our eczema product - H-Eczema
Free Shipping over $49
Free Shipping over $99
All products are shipped in a plain envelope with no description of what is inside.
All products come with an Unconditional 90 Day Money Back Guarantee. If you are unhappy for any reason, simply return the bottles for a full refund of your product purchase. No questions asked!
1 866 445 5433 (office hours - Monday to Friday, 9am-8pm EST)
+1 858 794 8474 (office hours - Monday to Friday, 9am-8pm EST)
For customers outside the USA, alternatively email your telephone number and best time to call, and we will get back to you.
General enquires and sales - click here to email us
Live Chat is available during normal business hours (Monday to Friday, 9am-8pm EST) An icon will be available at the bottom of your screen when live chat is online. - Chat with us!


text:
Search our database of handpicked sites
Looking for a great physics site? We've tracked down the very best and checked them for accuracy. Just fill out the fields below and we'll do the rest.
You searched for "heat transfer"
We found 16 results on physics.org and 71 results in our database of sites
(of which 69 are Websites, 0 are Videos, and 2 are Experiments)
Search results on physics.org
How do you induction cookers work?
How is energy transfered?
How does a fridge work?
How do brewers control temperature to make beer?
Can we control lightning?
Hyperthermia - Cancer therapy hots up
SODIS - A place in the sun
Where is that draught coming from?
All about... supernovae
How do solar cells work?
Could your phone harm your health?
How does an artificial heart work?
The Herschel Space Observatory
Cutting the cord - Wireless electricity
How does sunscreen work?
What is a mirage?
Specific Heat
The specific heat is the amount of heat per unit mass required to raise the temperature by one degree Celsius.
How Thermoses (Vacuum Flasks) Work
An excellent description of how Thermoses (Vacuum Flasks) work using heat transfer principles. From HowStuffWorks.com. An extremely good, informative site.
Calorimetry - Measuring Heats of Reactions
Description of some calorimetry methods and calculation examples.
Heat Of Vaporization
Equation for determining the latent heat of fusion. Grams and calories used.
What is heat?
An introductory level definition of heat, with lots of extra information.
A definition of the term heat with links to related topics such as the first law of thermodynamics. Includes examples and questions.
Energy transfer and storage
An activity to explore energy transfer and storage
Wilhelm Rontgen
Wilhelm Rontgen (1845 - 1913) first work was on the specific heats of gases and the thermal conductivity of crystals.
Heat and Thermodynamics
Introductory page leading to many other pages on hyperphysics, each dealing with an aspect of heat and thermodynamics
This site gives details of a series of demonstrations on illustrating heat, giving details of the set-up used and the safety hazards


text:
From Genea-Musings. This week's challenge is:
Provide a list of your paternal grandmother's patrilineal line. Answer these questions:
* What was your father's mother's maiden name? Britt (Sarah Britt, 1925 Emanuel Co, GA - 23 Feb 2008, Stone Mountain, Gwinnett, GA)
* What was your father's mother's father's name? Nathan(iel) Britt (1901, Emanuel Co, GA - 1965, Fulton Co, GA)
* What is your father's mother's father's patrilineal line? That is, his father's father's father's ... back to the most distant male ancestor in that line? I can just go back one more generation to William Britt (1818, Edgefield Co, SC - aft 1901, Emanuel OR Burke Co, GA)
* Can you identify male sibling(s) of your father's mother, and any living male descendants from those male sibling(s)? If so, you have a candidate to do a Y-DNA test on that patrilineal line. If not, you may have to find male siblings, and their descendants, of the next generation back, or even further. My father's mother had one brother, James Evoid Britt. He had a son, J.E.B. Jr. I know he married, but I'm not sure if he has children.


text:
Your horse has neck and/or back pain. The signs are obvious: sensitivity when grooming and saddling, resistance to rider weight, stiffness and pain when manipulating the neck and back, and a notable decrease in performance. But what is causing the pain, and what can you do about it?
"Despite being common and obvious in many cases, identifying the exact source of the neck or back pain can be complex," said Richard Mitchell, DVM, a private practitioner in Newtown, Conn., at the 12th Congress of The World Equine Veterinary Association, held Nov. 2-6, 2011, in Hyderabad, India.
According to Mitchell, "A thorough physical examination coupled with a complete therapeutic approach can frequently identify, then relieve symptoms of neck and back pain."
Lower limb problems that cause the horse to carry himself differently can lead to muscle stiffness and soreness. Thus, identifying and correcting lower limb problems could resolve neck and back issues.
Once lower limb problems are ruled out the veterinarian should perform palpation, passive and active flexion tests, jogging, longeing, and watching the horse move under saddle in a systematic fashion. If he or she identifies a "sore spot," radiographs (X ray), ultrasound, thermography (measuring body surface temperature and depicting inflammation by detecting and displaying heat), and possibly nuclear scintigraphy (bone scans) can be used to better characterize the underlying problem.
"This type of thorough physical exam and careful observation of the horse in motion can enable the practitioner to accurately assess the horse and address problems in an effective manner," relayed Mitchell. "A variety of techniques are currently available for horses with neck and back pain."
Examples of various treatments include:
- Injecting corticosteroids into painful joints such as the temporomandibular joint (jaw) or the joints between the individual vertebrae in the spinal column;
- Non-steroidal anti-inflammatory drugs (NSAID) to decrease inflammation;
- Muscle relaxants;
- Mesotherapy (injecting small volumes of corticosteroids and local anesthetics into the mesodermal tissue under the skin) to reduce discomfort and improve range of motion in cases of neck pain;
- Chiropractics, acupuncture, and therapeutic ultrasound to improve range of motion and comfort;
- Ensuring proper saddle fit;
- Estrone sulfate to help improve muscle tone;
- Extracorporeal shock wave therapy (ESWT); and
- Time off from performance in the case of trauma (e.g., fracture or severe ligamentous strain).
The exact treatment will depend on the underlying cause and must be determined by a veterinarian, potentially in concert with a qualified equine physical therapist.
Disclaimer: Seek the advice of a qualified veterinarian before proceeding with any diagnosis, treatment, or therapy.


text:
Review: Speck CandyShell Card for iPhone 5
Company: Speck Products
Website: http://www.speckproducts.com/
Model: CandyShell Card
Price: $40
Compatible: iPhone 5
Although it didn't launch alongside Speck's original batch of iPhone 5 cases, CandyShell Card ($40) has returned to the company's lineup. First made available for the iPhone 4/4S, the case combines elements of the standard CandyShell with those of the subsequently-released SmartFlex Card. The result is a co-molded rubber and glossy plastic shell with room for up to three credit cards in the back; it's an amalgamation of features from a pair of great cases.
At its core, CandyShell Card is almost identical to a standard CandyShell, except it's a bit thicker due to the card holder. It uses the same rubber inside, plastic outside design, including extending the rubber out to the corners, buttons, and front edge. The bottom is the same too, with full openings for the headphone and Lightning ports, and small dots exposing the speaker and microphone. As we'd expect, button coverage is executed just how it should be, with full protection, but without dampening button sensitivity. This design continues to offer one of the best tradeoffs of size and drop protection we've seen.
Along the case's rear left edge is a 3.5" long slot cut into the plastic. Underneath, it's lined with rubber, and although you can't see it while the case is installed, there's a bump that prevents your cards from sliding around, even if there's just one. Thankfully, this works; even with extreme shaking, a single card will stay securely in place. Despite this impressive grip, card removal is easy. You can simply push your card or cards out, using the thumb hole on the right side of the case.
The only reason that CandyShell Card earns a B+, and not the same high recommendation as SmartFlex Card, is its slightly higher price. The look and functionality are almost the same; it's really just the plastic that sets them apart. At $35, this case would easily be worth an A-. Regardless, it's a very good option, and worth checking out if you're looking to replace your old-fashioned wallet with something smaller.
Editors' Note: iLounge only reviews products in "final" form, but many companies now change their offerings - sometimes several times - after our reviews have been published. This iLounge article provides more information on this practice, known as revving.


text:
Difference between revisions of "Rancher"
m (→Variants)
m (→GTA IV)
|Line 28:
|Line 28:
The Rancher, now manufactured by [[Declasse]],
The Rancher , now manufactured by [[Declasse]], resembles a [[:wp:Chevrolet K5 Blazer#1973-1991|Cheyenne Trim 1989-1991 K5 Blazer]]; the taillights and the slight lean of the rear of the cab resemble [[:wp:Ford Bronco|1980-1996 Ford Broncos]]. The GTA IV rendition, also features variants of the Rancher with or without a camper shell. Pickup variants of the Rancher may also include a roll bar with top-mounted offroad lights, a brush guard, or a bull bar. All variants of GTA IV's Rancher also feature nerf bars. The rear bed-lids of pre-GTA IV Ranchers are hinged to the top, while those of the GTA IV rendition are hinged at the bottom on the truck bed, with an additional glass lid hinged to the top for the camper shell variant, similar to its real-life counterpart. Also, the pickup variants may or may not come with boxes loaded.
<gallery width="auto" perrow="2" style="font-size:95%; padding:0; text-align:left" widths="180">
<gallery width="auto" perrow="2" style="font-size:95%; padding:0; text-align:left" widths="180">
Revision as of 04:55, 10 October 2012
Rear quarter view)
A Rancher in GTA Vice City.
GTA Vice City
GTA San Andreas
|Vehicle type
|Civilian 4x4
|Body style
2-door SUV
2-door pickup (GTA IV)
|2 (driver and passenger)
|Declasse (GTA IV)
{{Infobox vehicle
| name = Rancher
| front_image = Rancher-GTAVC-front.jpg
| image_size = 300
| caption = A Rancher in GTA Vice City
| rear_image = Rancher-GTAVC-rear.jpg
| vehicle_type = Civilian 4x4
| body_style = 2-door SUV
The Rancher is an SUV/pickup truck that appears in Grand Theft Auto: Vice City, Grand Theft Auto: San Andreas, Grand Theft Auto IV. Unlike most vehicles from GTA Vice City, the Rancher is absent from Grand Theft Auto: Vice City Stories.
GTA Vice City — GTA San Andreas
"What kind of moron would drive this car? Hey, my wife drives one of these.
Oh, sorry man."
- Official Vice City Bureau of Investigation file description, GTA Vice City.
The Rancher is a medium-sized SUV designed with off-road capabilities in mind, featuring large tires, soft suspensions and a high ground clearance. Despite its size, the two-door Rancher is only capable of holding two occupants, as it rear compartment is not capable of carrying passengers, similar to two-door pickup trucks in the series. In general, the Rancher resembles a 1981-1988 Chevrolet K5 Blazer (but with added turning signals and different taillights). The camper shell is permanently placed over the bed, and cannot be removed unless a modification is used.
GTA Vice City (Rear quarter view).
GTA San Andreas (Rear quarter view).
The Rancher in GTA IV, now manufactured by Declasse, resembles a Cheyenne Trim 1989-1991 K5 Blazer; the taillights and the slight lean of the rear of the cab resemble 1980-1996 Ford Broncos. The GTA IV rendition, also features variants of the Rancher with or without a camper shell. Pickup variants of the Rancher may also include a roll bar with top-mounted offroad lights, a brush guard, or a bull bar. All variants of GTA IV's Rancher also feature nerf bars. The rear bed-lids of pre-GTA IV Ranchers are hinged to the top, while those of the GTA IV rendition are hinged at the bottom on the truck bed, with an additional glass lid hinged to the top for the camper shell variant, similar to its real-life counterpart. Also, the pickup variants may or may not come with boxes loaded.
GTA IV (Rear quarter view).
GTA Vice City — GTA San Andreas
The Rancher is one of the better SUVs in both GTA Vice City and GTA San andreas. Performance is only average, but its chassis is better. Its handling is above average. The suspension is soft, which makes the car quite comfortable, even on broken surfaces such as railroad tracks.
In Grand Theft Auto IV, the Rancher is not a on-road performance oriented vehicle. It's suspension consists of solid axles front and rear, as opposed to the independent suspension on more refined SUVs and pick-ups. This layout, coupled with a powerful V8 engine, means that on-road cornering is an erratic affair, with plenty of sliding and body roll.
However, the old-fashioned suspension, together with 4WD and a easily controlled engine, starts to pay off when the vehicle is taken off-road. In the hands of a skillful driver, the Rancher is an excellent off-roader. The high ground clearance means boulders are negotiated with ease. The solid axles keep the vehicle planted, although the driver must always be wary of the risk of a roll-over (due to the high center of gravity).
- FBI Rancher (GTA Vice City and GTA San Andreas, GTA Chinatown Wars as the "FIB Rancher" and GTA Vice City Stories by using CheatDevices)
- A unique black Rancher can be obtained in GTA Vice City after "Test Track" is completed three times, each time beating your previous record. On the next attempt, a PIG driving a black Rancher will appear and start driving around the track as well. The player is free to steal it from him and save the car in a garage.
- Police Ranger (GTA San Andreas)
- A unique Rancher (internal name "rnchlure") is spawned with the spawn a Rancher cheat in GTA San Andreas. The vehicle's internal name suggests that it was intended for use in the mission "Lure", however a regular Rancher is used in that mission. The only distinction of this variant from the normal Rancher are its black-tinted windows (which obscure the occupants of the vehicle, a central element of the Lure mission). Unlike the normal Rancher, the "rnchlure" version cannot be exported or modded at mod garages. (GTA San Andreas)
- Gang Rancher (GTA Vice City Stories)
- A Rancher in GTA IV is among a range of cars requested in Stevie's Car Thefts, featuring a unique blood red and light gray body color. The Rancher may come with or without a camper shell, as well as one of a range of accessories, much like a regular Rancher.
- Rancher-GTAVC-black.jpg
The black Rancher available in GTA Vice City.
The Rancher requested in Stevie's Car Thefts in GTA IV.
The Rancher in GTA San Andreas can be modified at a TransFender mod garage, which offers a wide range of customizations for the vehicle:
Italicized pricing denotes prices at the Las Venturas TransFender, which charges 20% more except Colors.
- In its appearances in GTA San Andreas and GTA IV, the Rancher plays the following radio stations by default when entered:
- K-DST in GTA San Andreas.
- Liberty Rock Radio 97.8 in GTA IV.
- Rusting wrecks of Ranchers can also be found in various dilapidated areas and junkyards in GTA IV.
- In perfect condition the Rancher can be sold in the S&M Auto Sales for $2,500 after completing Stevie's Car Thefts in GTA IV.
- The Rancher and Police Rancher appear in Bully. It is however undrivable because the protagonist Jimmy Hopkins is only fifteen years old. He can also hold onto the backs of vehicles while on his skateboard.
- Bullworth Acedemy's maths teacher Mr. Hattrick owns a light blue and grey Rancher.
- GTA San Andreas
- Spawns regularly in the desert and countryside.
- Parked by a garage to the south west of the form at Blueberry Acres, Red County (only when wanted for export).
- At the Import/Export Ship at Easter Basin, San Fierro for $40,000.
- Parked next to a building northwest of Hunter Quarry and east of Cluckin' Bell in Bone County.
- Parked between trailers north of Ammu-Nation in eastern Bone County.
- Northernmost trailer in Las Payasadas.
- Parked beside The Triangle Club in Bohan (multiplayer only).
- Common around Chinatown.
- Common on Frankfort Ave, in Middle Park, Varsity Heights and North Holland.
- Bully
- Driving all around Bullworth.


text: add to multibuy What is a Multi-Buy? Free delivery on this item Please call our sales team for delivery dates Trustpilot The Quooker Fusion provides hot, cold and 100°C filtered boiling water from a single spout. Its high-vacuum insulation means that it only costs 3 pence a day to have boiling water at hand exactly when you want. This is the Fusion Square model finished in brushed chrome with a three litre water tank and it can be converted to a 4-in-1 model with the addition of the optional Cold Water Filter kit. 2 yearwarranty Features Colour: BRUSHED CHROME Dispenses hot, cold and 100°C purified water from a single spoutCan be converted to a 4-in-1 model with the addition of the optional Cold Water Filter kitChildproof double-push-and-turn textured handle with light ringHighly energy efficientHiTAC water filterStainless steel 3 litre tankVacuum insulationStandby power consumption 10wPower 1600wHeat up time from cold 10 minutes 10 bar maximum pressurePressure relief valveCeramic water shut off valveHigh temperature activated carbon water filter with 5 year lifespanPlease note:This model requires connection to your existing hot and cold water supplyOptional cold water filter and Scale control filter available at an extra cost


text: UMW News BureauThe University of Montana Western men and women's rodeo team are in Casper, Wyo. for the 61st College National Finals Rodeo. By Wally Feldt The University of Montana Western men's rodeo team rides into Casper, Wyo. for the 61st College National Finals Rodeo (CNFR) June 14-20, 2009 as champions of the Big Sky Region. More than 400 cowboys and cowgirls from over 100 colleges and universities will compete in college rodeo's premier event. The CNFR begins on Sunday, June 14 with Bulls, Broncs and Breakaway at 1 and 4 p.m. There are slack performances Monday, June 15 and Tuesday, June 16 beginning at 7 a.m. "This is the Super Bowl of college rodeo," Montana Western rodeo coach Olie Else said. "The best of the best will be showing their talent in one of the premier rodeo events." Evening performances begin at 7 p.m. Tuesday through Saturday. All qualifiers compete in three rounds with the top 12 in each event advancing to the Saturday night championship finals. Led by four individual champions, the Bulldog men's team won the regional title by nearly 2000 points and will send eight cowboys to the CNFR. Wyatt Smith, a junior from Rexburg, Idaho was the regional champ in saddle bronc, steer wrestling and all-around. Smith will compete in saddle bronc and steer wrestling. Brett Heggie, a junior from Roundup, Mont., was the regional champion in tie down roping. Heggie, a transfer from Norwest College of Powell, Wyo., competed at CNFR last year. Brian Dawson, a senior from Boulder, Mont., finished second in the region in saddle bronc riding. Dawson is making his first appearance at the CNFR. Ace Mills, junior from Augusta, Mont., will compete in saddle bronc riding in his first trip to the College National Finals. Kent Mueller, a senior from Belgrade, Mont., will compete in team roping. It's Mueller's first appearance at the CNFR. Parker Murnion, a junior from Jordan, Mont., makes his first appearance in Casper competing in team roping. Taylor Nahrgang, a senior from Buckeye, Ariz., makes his third trip to the CNFR. He will compete in steer wrestling. Nahrgang is the newly elected student director of the Big Sky Region and is a candidate for the Walt Garrison award. Stetson Wilson, a senior from Pocatello, Idaho, finished second in the region in steer wrestling. This is Wilson's second trip to the CNFR. The Bulldog women's team finished second in the region and qualified four cowgirls to the College National Finals. Shaylee French, a senior from Pincher Creek, Alberta, Canada is making her third straight trip to the CNFR. She will compete in goat tying in Casper. She finished third in the region. Brandy Pedersen, a junior from Great Falls, Mont. is making her second trip to the CNFR. She qualified in breakaway roping after finishing fourth in the region. Lexi Archibek, a senior from Sun City, Calif. is making her first trip to the CNFR. She qualified for the CNFR after a fourth place regional finish in barrel racing. Rose Fields, a junior from Salmon, Idaho is making her first trip to the CNFR. She qualified for the CNFR after a seventh place regional finish in barrel racing.


text:
Hartford - BENEATH the stained-glass windows and stenciled walls of the Charter Oak Cultural Center, dancers from the Judy Dworin Performance Ensemble and the singers of Women of the Cross, a spiritual trio, acted out the lives of inmates from the York Correctional Institution, a women's prison in Niantic.
In their rehearsal last month for the upcoming performance of "Time In," an exploration of time spent behind bars, the performers spoke of waiting for the hours to pass, of how they came to be inmates and of how they supported one another.
The performance was an outgrowth of the writing workshop given for York inmates by Wally Lamb, the Connecticut author of the novels "She's Come Undone" and "I Know This Much Is True." Mr. Lamb has been working with the women's stories for many years and has published a nonfiction anthology, "Couldn't Keep It to Myself: Wally Lamb and the Women of York Correctional Institution: Testimonies of Our Imprisoned Sisters." The inmates' pieces were edited and reshaped into dialogue during a six-month arts residency by Prof. Judy Dworin, chairwoman of the dance department at Trinity College in Hartford, who choreographed the show.
"One of the things I've learned in my seven years at York is that the equation by which women land in prison is complex and multifaceted, not at all a matter, as some people assume, of 'we're good people, they're bad people,' " Mr. Lamb wrote in an e-mail message.
"When the women not only write, but then share their writing with folks beyond the prison walls, it helps to dispel stereotypes and gets the public thinking about them as human beings first, inmates second," he wrote. "That's where Judy's mission and mine intersect."Continue reading the main story
More than 30 inmates danced and sang with the ensemble in a performance of "Time In" at the prison in June. In August, the inmate performers sat in the audience at the prison and watched the ensemble perform.
"Time is a loaded topic for women who are serving time," Ms. Dworin said. "There were tears, joy, women standing up and singing louder than the performers. At the end of it, there was this enormous standing ovation, and hugs and thanks. These kinds of moments in performance are the reason we do this. It's certainly the reason I do it."
The inmates were not permitted to perform outside the prison, so the ensemble will be performing "Time In" without them at the Charter Oak Cultural Center Nov. 2 to 4. Mr. Lamb will introduce the first day's performance.
Laresse Harvey of New Britain, a former inmate at York who saw the performance recently at a school in Southbury, said it captured the essence of the five and a half years she had served at the prison.
"Time is valuable," she said. "I choose to live life and have experiences now, and I never take a beautiful blue sky for granted."Continue reading the main story


text:
Wonderful changes have come to this land and people since the arrival of the pioneers. And I want to say that the changes, the progress and increase will be just as great during the next 51 years as during a similar period that has just closed. The destiny of this people is before heaven and earth and nothing can stay it. —Wilford Woodruff
SALT LAKE CITY — About 2,000 people gathered to hear the president of The Church of Jesus Christ of Latter-day Saints speak on a sunny Monday morning, July 25, 1898. Wilford Woodruff stood, the stars and stripes serving as a backdrop, and addressed the crowd at the original camping spot of the Utah settlers.
"Wonderful changes have come to this land and people since the arrival of the pioneers," he said as he dedicated Pioneer Park, with fellow pioneers seated behind him. "And I want to say that the changes, the progress and increase will be just as great during the next 51 years as during a similar period that has just closed. The destiny of this people is before heaven and earth and nothing can stay it."
Those were the words spoken to the crowd as recorded in the July 25, 1898 evening edition of the Deseret News. It would be one of his final addresses as the man who served with Joseph Smith and the founding members of the LDS Church would die only weeks later on Sept. 2.
An original glass negative, recently discovered and sold to the LDS church, shows the president addressing the crowd as those enjoying the dedication donned heavy clothes, but also hats, flowers and umbrellas for the event.
Richard E. Turley, Jr., assistant historian and recorder for the LDS church, said the images are in the possession of the church and they are in the process of cataloguing them. He said the church plans on making the images available to the public.
"They're a wonderful addition to our collection," Turley said.
A print says July 24th, but the image President Woodruff is of the next day at the park, one of 624 original glass negatives in a collection taken by Charles Ellis Johnson from as early as 1892 to as late as 1912. Glen Beckstead sold the negatives to the church after purchasing them from a bookstore.
"They were the kind of thing that needed to be with a big institution," Beckstead said. "There were a lot of them that needed to be fixed, that needed some tender loving care, so it was easy to decide to sell."
Ron Fox, photo historian and author, helped broker the deal and said the image depicts a festive celebration.
"It's all about the great love for the heritage, for the struggle for statehood," Fox said. "And the struggle to take the desert and make it bloom like a rose."
He said the LDS church is in the process of conserving the images and preparing them for a longer life, a process that may take up to a year. But Fox said the images are great quality and have thousands of mega pixels.
"You could blow this original picture up to the size of a billboard and still have the quality," he said.
Other images in the collection include a photo of a group of young girls at the dedication, and images of the Buffalo Soldiers marching down Main Street and at the train station. There are action shots of a busy Main Street, photos from President Woodruff's funeral, and images showing Utah's first state governor, Heber Manning Wells. There are images of Emmeline B. Wells, Fifth general president of the LDS Relief Society and for decades a voice for Utah women, including in the fight for the vote.
In the Pioneer Park photo, those in attendance and sitting on the stage behind President Woodruff were city council members, George Q. Cannon, First Counselor to President Woodruff in the church's First Presidency; Congressman William Henry King, judge William Cochran Adkinson Smoot, Zina D.H. Young, the third general president of the Relief Society and others.
Mayor John Clark said although they weren't formally celebrating the 51st anniversary of the pioneers into Salt Lake Valley that day (it was the day before), there was no better way to honor them than by dedicating the historic ground as a public park, "for the benefit of the inhabitants of this city, founded by the pioneers."
The dedication closed with a dedicatory prayer given by President Cannon, followed by three cheers for the pioneers, and the mayor and city council for having the park dedicated for residents.
"Let us never forget those noble pioneers who opened up these valleys for us and our posterity and made it possible for us to enjoy this rich heritage," Clark said. "Hail to the Pioneers of '47, joy and peace to their posterity and to all the dwellers in the pleasant vales of Utah!"
Email: [email protected]
Twitte: EmileeEagar


text:
We cut briars and weeds around the stones and made them look much better.
~ The pieces are all sewn together, stitched with love.........and a quilt tells a story and the story is our past ~
The Arrowood family immigrated from England to Maryland in the 1700's. They went south, eventually settling in the mountains of North Carolina. Later , some went further south, into the Piedmont of North Carolina, in search of work and a better way of life.
I am in search of my family.
I search for those that came before me, and lived their lives as best they could. I am in search of their stories, how they lived, and how they loved.
I shared this love of seeking the past with my Dad, sharing each new finding with him, the thrill in his heart intermingling with mine. I continue this search in his honor, and hope to know these people of ours when I join up with them all in heaven.
~ Steve Lewis Arrowood 1932-2008 ~
Come with me, back to a simpler time and place. A place far removed from the hectic pace of today. To a time when life was hard, but the rewards were great. When your quality of life was determined by your own sweat, your own toil, and your own ingenuity.
Would you like a glass of sweet tea? Let's sit out on the porch where we will catch the sweetly scented breeze of summertime. Maybe Grandma will fry up some of her wonderful chicken... Time slows here.
"We shape our lives not by what we carry with us, but what we leave behind."
~You live as long as you are remembered.~
"Our most treasured family heirlooms are our sweet family memories. " Author: Unknown
"But those who came before us will teach you. They will teach you from the wisdom of former generations."
Tuesday, March 13, 2012
In Search of William Winters ~ Quaker Meadows ~ Canoe Creek NC
We cut briars and weeds around the stones and made them look much better.
2 comments:
This is the most amazing work of art and kindness I have found anywhere on the internet, especially facebook. I really injoy the post and plan to bookmark so as to come back and finish what I started today. I am working on several pages on facebook https://www.facebook.com/home.php which is some history of Avery County and alsohttps://www.facebook.com/buckmtman?v=photos not sure these links will work but please visit my facebook page Donald Leonard Johnson.ReplyDelete
Thank you so much, Donald, for your kind words. This search is so very important to me. It keeps blessing me over and over again. I must admit a tear fell (once again!) while reading your sweet note. Blessings to you, kind sir. Martha JaneReplyDelete