KELP 세미나 소식이군요.
http://kelp.or.kr/korweblog/pages.php?page=03/10/27/3640332
당일 낮에 할 일이 없을듯 보이니... 저는 놀러갈 듯 하군요. ^^;; 밤에는 여행가기로 했고... -ㅅ-
다행히도 세미나가 집 앞(이라기에는 좀 멀지만... ^^;; ) 이니 츄리닝입고 가도 될듯하군요 ㅎㅎ
|
SELECT
*
FROM
ADM.DBCFG
WHERE
DBNAME = ?
AND INPUT_DATE IN ( ? , ?, ?, ? )
<select id="dbm.selectDBCfgByDBNameAndInputDate" parameterClass="java.util.HashMap" resultMap="retmapDBCfgVo">
SELECT
*
FROM
ADM.DBCFG
WHERE
DBNAME = #dbname#
<iterate property="input_date" prepend ="AND INPUT_DATE IN " open="(" close=")" conjunction="," >
#input_date[]#
</iterate>
</select>
public List<DBCfgVo> getDBCfgList(String dbname, List<String> date) {
SqlMapClient sqlMapper = SqlMapperMgr.getSqlMapClient(MAPPERTYPE.DBMDB);
List<DBCfgVo> list = null;
Map<String, Object> map = new HashMap<String, Object>();
map.put("dbname", dbname);
map.put("input_date", date);
try {
list = (List<DBCfgVo>)sqlMapper.queryForList("dbm.selectDBCfgByDBNameAndInputDate",map);
} catch (SQLException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
return list;
}
wine_opengl.reg |
To start, NAT is by far the easiest way to get your guests connected to the interweb, but you may want to use the guests as servers. For this you need Host Networking.
You will need to install bridge-utils and uml-utilities so that you can make a tap device and add it to a bridge.
sudo apt-get install bridge-utils uml-utilities
To configure bridging, you basically go through three steps on the host machine. First you need to create a bridge. Next you create virtual interface(s). Then you add a real interface and virtual interface(s) to the bridge. Because of the scripts available on the distribution which take care of all the details, all of this sums up to two steps:
On the host machine:
$ sudo gedit /etc/network/interfaces
auto eth0
iface eth0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0
# The loopback network interface
auto lo
iface lo inet loopback
"br0" is an arbitrary name. To take the modifications into account, restart the network:
$sudo /etc/init.d/networking restart
From now on, your system will always set up the bridge on boot. Note that this could slow down the boot time a little bit, because of the bridge coming up.
On the host machine:
$ sudo gedit /etc/vbox/interfaces
# Each line should be of the format :
# <interface name> <user name> [<bridge>]
vbox0 <your user name> br0
vbox1 <your user name> br0
...
"vbox#" is an arbitrary name. You may declare here as many virtual interfaces as you wish, and add it to a bridge.
Later when you will configure the network of your virtual machine you will use the virtual adapter name "vbox#" for host networking. For example if you use the VirtualBox Qt graphical interface, enter "vbox#" in the "Interface Name" field, when choosing "Host interface".
To take the modifications into account, restart the VirtualBox host networking script:
$sudo /etc/init.d/virtualbox-ose restart
The virtual interfaces are now created and added to the bridge.
That's it! Now the different scripts will take care of cleanly create/configure/remove bridges and virtual interfaces when you boot and shut your system down.