1. Stir it with a wooden spoon.
2. Biological evolution is a change in the genetic characteristics of a population over time. That this occurs is a fact.
3. The fact that there are 16 fluid ounces (oz.) in a pint (8 oz. to the cup) and 16 dry oz. to the pound leads to all sorts of confusion and mistakes in recipes. Further, it is quite common for recipes to specify an amount of a dry substance in liquid units: a cup of chopped onions, a half cup of diced celery, etc. This is done because we typically don't keep scales in our kitchens, but we do have measuring cups.
Where this really becomes problematic is with measuring flour. The actual amount of flour in a measuring vessel will vary widely depending upon how loose or compact it is.
4. Irish Soda Bread is a classic quick bread from Ireland, which takes its name from the fact that it uses baking soda for leavening. The whole reason bread soda was used in the first place was to replace using yeast as the rising agent.
It is usually made with buttermilk, baked on the griddle or in the oven. It didn’t keep well and was made every 2-3 days and eaten as a part of the mean, not a desert.
Before baking, a cross is cut on the top with a knife, supposedly to ward off the devil. It shocks some people to learn that Irish Soda Bread hasn't been around for thousands of years. It wasn't until around the 1840's that bicarbonate of soda (Bread soda) as a leavening agent was introduced to Ireland. The basic soda bread is made with flour, baking soda, salt, and soured milk (or buttermilk).
Irish soda bread. Real soda bread, the traditional type our Irish ancestors have baked and eaten for well over 100 years. It is tender and dense with a slight sour tang and a hard crust. A nutritious staple that is real “Staff of Life” stuff.
As befitting a traditional product of a poor country, it was made with only the most basic of ingredients: flour to form a dough, bread soda to leaven the dough, soured milk to moisten and activate the soda, and salt for seasoning. It is a traditional food, worth preserving and passing on to our grandchildren and great grandchildren.
5. In OpenBSD, interfaces are named for the type of card, not for the type of connection. You can see your network card get initialized during the booting process, or after the booting process using the dmesg(8) command. You also have the chance of seeing your network interface using the ifconfig(8) command. For example, here is the output of dmesg for a Intel Fast Ethernet network card, which uses the device name fxp.
code:fxp0 at pci0 dev 10 function 0 "Intel 82557" rev 0x0c: irq 5, address 00:02:b3:2b:10:f7
inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
If you don't know what your device name is, please look at the supported hardware list for your platform. You will find a list of many common card names and their OpenBSD device names here. Combine the short alphabetical device name (such as fxp) with a number assigned by the kernel and you have an interface name (such as fxp0). The number is assigned based on various criteria, depending upon the card and other details of the system. Some cards are assigned by the order they are found during bus probing. Others may be by hardware resource settings or MAC address.
You can find out what network interfaces have been identified by using the ifconfig(8) utility. The following command will show all network interfaces on a system. This sample output shows us only one physical Ethernet interface, an fxp(4).
code:$ ifconfig
lo0: flags=8049 mtu 33224
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
lo1: flags=8008 mtu 33224
fxp0: flags=8843 mtu 1500
address: 00:04:ac:dd:39:6a
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 10.0.0.38 netmask 0xffffff00 broadcast 10.0.0.255
inet6 fe80::204:acff:fedd:396a%fxp0 prefixlen 64 scopeid 0x1
pflog0: flags=0<> mtu 33224
pfsync0: flags=0<> mtu 2020
sl0: flags=c010 mtu 296
sl1: flags=c010 mtu 296
ppp0: flags=8010 mtu 1500
ppp1: flags=8010 mtu 1500
tun0: flags=10 mtu 3000
tun1: flags=10 mtu 3000
enc0: flags=0<> mtu 1536
bridge0: flags=0<> mtu 1500
bridge1: flags=0<> mtu 1500
vlan0: flags=0<> mtu 1500
address: 00:00:00:00:00:00
vlan1: flags=0<> mtu 1500
address: 00:00:00:00:00:00
gre0: flags=9010 mtu 1450
carp0: flags=0<> mtu 1500
carp1: flags=0<> mtu 1500
gif0: flags=8010 mtu 1280
gif1: flags=8010 mtu 1280
gif2: flags=8010 mtu 1280
gif3: flags=8010 mtu 1280
As you can see here, ifconfig(8) gives us a lot more information than we need at this point. But, it still allows us to see our interface. In the above example, the interface card is already configured. This is obvious because an IP network is already configured on fxp0, hence the values "inet 10.0.0.38 netmask 0xffffff00 broadcast 10.0.0.255". Also, the UP and RUNNING flags are set.
Finally, you will notice several other interfaces come enabled by default. These are virtual interfaces that serve various functions. The following manual pages describe them:
* lo - Loopback Interface
* pflog - Packet Filter Logging Interface
* sl - SLIP Network Interface
* ppp - Point to Point Protocol
* tun - Tunnel Network Interface
* enc - Encapsulating Interface
* bridge - Ethernet Bridge Interface
* vlan - IEEE 802.1Q Encapsulation Interface
* gre - GRE/MobileIP Encapsulation Interface
* gif - Generic IPv4/IPv6 Tunnel Interface
* carp - Common Address Redundancy Protocol Interface
The interface is configured at boot time using the /etc/hostname.if(5) files, where if will be replaced by the full name of your interface, for the example above, /etc/hostname.fxp0.
The layout of this file is simple:
code:address_family address netmask broadcast [other options]
Much more detail about the format of this file can be found in the hostname.if(5) man page. You will need to read this for less trivial configurations.
A typical interface configuration file, configured for an IPv4 address, would look like this:
code:$ cat /etc/hostname.fxp0
inet 10.0.0.38 255.255.255.0 NONE
In this case, we have defined an IPv4 (inet) address, with an IP address of 10.0.0.38, a subnet mask of 255.255.255.0 and no specific broadcast address (which will default to 10.0.0.255 in this case).
You could also specify media types for Ethernet, say, if you wanted to force 100baseTX full-duplex mode.
code:inet 10.0.0.38 255.255.255.0 NONE media 100baseTX mediaopt full-duplex
(Of course, you should never force full duplex mode unless both sides of the connection are set to do this! In the absence of special needs, media settings should be excluded. A more likely case might be to force 10base-T or half duplex when your infrastructure requires it.)
Or, you may want to use special flags specific to a certain interface. The format of the hostname file doesn't change much!
code:$ cat /etc/hostname.vlan0
Inet 172.21.0.31 255.255.255.0 NONE vlan 2 vlandev fxp1
6. I can't count :(