Update of /cvsroot/leaf/src/bering-uclibc4/source/mdadm
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv24446/mdadm
Added Files:
buildtool.cfg buildtool.mk md-syslog-events mdadm-2.5.6.tgz
mdadm-raid.init mdadm-uClibc.patch mdadm.conf mdadm.init
Log Message:
added -fno-strict-aliasing for gcc 4.4.4
--- NEW FILE: mdadm-uClibc.patch ---
diff -urN mdadm-2.5.2.orig/util.c mdadm-2.5.2/util.c
--- mdadm-2.5.2.orig/util.c 2006-06-26 07:10:45.000000000 +0200
+++ mdadm-2.5.2/util.c 2006-07-27 18:24:36.000000000 +0200
@@ -389,7 +389,7 @@
return ftw(path, add_dev_1, nopenfd);
}
#else
-int add_dev(const char *name, const struct stat *stb, int flag, struct FTW *s)
+int add_dev_1(const char *name, const struct stat *stb, int flag, struct FTW
*s)
{
return 0;
}
--- NEW FILE: mdadm.conf ---
# mdadm configuration file
#
# mdadm will function properly without the use of a configuration file,
# but this file is useful for keeping track of arrays and member disks.
# In general, a mdadm.conf file is created, and updated, after arrays
# are created. This is the opposite behavior of /etc/raidtab which is
# created prior to array construction.
#
#
# the config file takes two types of lines:
#
# DEVICE lines specify a list of devices of where to look for
# potential member disks
#
# ARRAY lines specify information about how to identify arrays so
# so that they can be activated
#
# You can have more than one device line and use wild cards. The first
# example includes SCSI the first partition of SCSI disks /dev/sdb,
# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second
# line looks for array slices on IDE disks.
#
#DEVICE /dev/sd[bcdjkl]1
#DEVICE /dev/hda1 /dev/hdb1
#
# If you mount devfs on /dev, then a suitable way to list all devices is:
#DEVICE /dev/discs/*/*
#
#
#
# ARRAY lines specify an array to assemble and a method of identification.
# Arrays can currently be identified by using a UUID, superblock minor number,
# or a listing of devices.
#
# super-minor is usually the minor number of the metadevice
# UUID is the Universally Unique Identifier for the array
# Each can be obtained using
#
# mdadm -D <md>
#
#ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
#ARRAY /dev/md1 super-minor=1
#ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1
#
# ARRAY lines can also specify a "spare-group" for each array. mdadm --monitor
# will then move a spare between arrays in a spare-group if one array has a
failed
# drive but no spare
#ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1
#ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1
#
# When used in --follow (aka --monitor) mode, mdadm needs a
# mail address and/or a program. This can be given with "mailaddr"
# and "program" lines to that monitoring can be started using
# mdadm --follow --scan & echo $! > /var/run/mdadm
# If the lines are not found, mdadm will exit quietly
#MAILADDR [email protected]
PROGRAM /sbin/md-syslog-events
--- NEW FILE: mdadm-2.5.6.tgz ---
(This appears to be a binary file; contents omitted.)
--- NEW FILE: mdadm.init ---
#!/bin/sh
#
# Start the RAID monitor daemon for all active md arrays if desired.
#
# Copyright (c) 2001-2004 Mario Jou/3en <[email protected]>
# Distributable under the terms of the GNU GPL version 2.
RCDLINKS="2,S25 3,S25 4,S25 5,S25 0,K25 1,K25 6,K25"
MDADM=/sbin/mdadm
DEBIANCONFIG=/etc/default/mdadm
PIDFILE=/var/run/mdadm.pid
test -x $MDADM || exit 0
test -f /proc/mdstat || exit 0
START_DAEMON=true
test -f $DEBIANCONFIG && . $DEBIANCONFIG
case "$1" in
start)
if [ "x$START_DAEMON" = "xtrue" ] ; then
echo -n "Starting RAID monitor daemon: mdadm --monitor"
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $MDADM
-- \
--monitor --pid-file $PIDFILE --daemonise --scan
echo "."
fi
;;
stop)
if [ -f $PIDFILE ] ; then
echo -n "Stopping RAID monitor daemon: mdadm --monitor"
start-stop-daemon --stop --quiet --pidfile $PIDFILE --exec $MDADM
rm -f $PIDFILE
echo "."
fi
;;
restart|reload|force-reload)
$0 stop
$0 start
;;
*)
echo "Usage: $0 {start|stop|restart|reload|force-reload}"
exit 1
;;
esac
exit 0
--- NEW FILE: buildtool.mk ---
# makefile for mdadm
include $(MASTERMAKEFILE)
MDADM_DIR:=mdadm-2.5.6
MDADM_TARGET_DIR:=$(BT_BUILD_DIR)/mdadm
$(MDADM_DIR)/.source:
zcat $(MDADM_SOURCE) | tar -xvf -
cat $(MDADM_PATCH1) | patch -d $(MDADM_DIR) -p1
touch $(MDADM_DIR)/.source
source: $(MDADM_DIR)/.source
$(MDADM_DIR)/.build:
mkdir -p $(MDADM_TARGET_DIR)
mkdir -p $(MDADM_TARGET_DIR)/sbin
mkdir -p $(MDADM_TARGET_DIR)/etc/init.d
$(MAKE) CC=$(TARGET_CC) CXFLAGS="$(BT_COPT_FLAGS) -DUCLIBC
-fno-strict-aliasing" -C $(MDADM_DIR)
$(BT_STRIP) $(BT_STRIP_BINOPTS) $(MDADM_DIR)/mdadm
cp -a $(MDADM_DIR)/mdadm $(MDADM_TARGET_DIR)/sbin
cp -a mdadm.init $(MDADM_TARGET_DIR)/etc/init.d/mdadm
cp -a mdadm-raid.init $(MDADM_TARGET_DIR)/etc/init.d/mdadm-raid
cp -a mdadm.conf $(MDADM_TARGET_DIR)/etc
cp -a md-syslog-events $(MDADM_TARGET_DIR)/sbin
cp -a $(MDADM_TARGET_DIR)/* $(BT_STAGING_DIR)
touch $(MDADM_DIR)/.build
build: $(MDADM_DIR)/.build
clean:
make -C $(MDADM_DIR) clean
rm -rf $(MDADM_TARGET_DIR)
rm -f $(MDADM_DIR)/.build
srcclean: clean
rm -rf $(MDADM_DIR)
rm -f $(MDADM_DIR)/.source
--- NEW FILE: md-syslog-events ---
#!/bin/sh
#
# sample event handling script for mdadm
# e.g. mdadm --follow --program=/sbin/syslog-events --scan
#
# License: GPL ver.2
# Copyright (C) 2004 SEKINE Tatsuo <[email protected]>
event="$1"
dev="$2"
disc="$3"
facility="kern"
tag="mdmonitor"
case x"${event}" in
xFail*) priority="error" ;;
xTest*) priority="debug" ;;
x*) priority="info" ;;
esac
msg="${event} event on ${dev}"
if [ x"${disc}" != x ]; then
msg="${msg}, related to disc ${disc}"
fi
exec logger -t "${tag}" -p "${facility}.${priority}" -- "${msg}"
--- NEW FILE: mdadm-raid.init ---
#!/bin/sh
#
# Start any arrays which are described in /etc/mdadm.conf and which are
# not running already.
#
# Copyright (c) 2001-2004 Mario Jou/3en <[email protected]>
# Distributable under the terms of the GNU GPL version 2.
RCDLINKS="S,S25"
MDADM=/sbin/mdadm
CONFIG=/etc/mdadm.conf
DEBIANCONFIG=/etc/default/mdadm
test -x $MDADM || exit 0
AUTOSTART=true
test -f $DEBIANCONFIG && . $DEBIANCONFIG
case "$1" in
start)
if [ "x$AUTOSTART" = "xtrue" ] ; then
test -f /proc/mdstat || exit 0
echo -n "Starting raid devices: "
if [ -f $CONFIG ] && [ -x $MDADM ] ; then
$MDADM --assemble --scan --auto=yes
fi
echo "done."
fi
;;
stop|restart|reload|force-reload)
;;
*)
echo "Usage: $0 {start|stop|restart|reload|force-reload}"
exit 1
;;
esac
exit 0
--- NEW FILE: buildtool.cfg ---
<File buildtool.mk>
Server = cvs4-sourceforge
Revision = HEAD
Directory = mdadm
</File>
<File mdadm-2.5.6.tgz>
Server = cvs4-sourceforge
Revision = HEAD
envname = MDADM_SOURCE
Directory = mdadm
</File>
<File mdadm-uClibc.patch>
Server = cvs4-sourceforge
Revision = HEAD
envname = MDADM_PATCH1
Directory = mdadm
</File>
<File mdadm.init>
Server = cvs4-sourceforge
Revision = HEAD
envname = MDADM_INIT
Directory = mdadm
</File>
<File mdadm-raid.init>
Server = cvs4-sourceforge
Revision = HEAD
envname = MDADM_RAID
Directory = mdadm
</File>
<File mdadm.conf>
Server = cvs4-sourceforge
Revision = HEAD
envname = MDADM_CONF
Directory = mdadm
</File>
<File md-syslog-events>
Server = cvs4-sourceforge
Revision = HEAD
envname = MDADM_LOG
Directory = mdadm
</File>
<Package>
<mdadm>
Version = 2.5.6
Revision = 3
Help <<EOF
mdadm RAID tools
Homepage: http://neil.brown.name/blog/mdadm
LEAF package by __PACKAGER__, __BUILDDATE__
EOF
<Permissions>
Files = 644
Directories = 755
</Permissions>
<Owner>
Files = root:root
Directories = root:root
</Owner>
<Contents>
<File>
Filename = sbin/mdadm
Source = sbin/mdadm
Type = binary
Permissions = 755
</File>
<File>
Filename = sbin/md-syslog-events
Source = sbin/md-syslog-events
Type = binary
Permissions = 755
</File>
<File>
Filename = etc/init.d/mdadm
Source = etc/init.d/mdadm
Description = mdadm init file
Type = binary
Permissions = 755
</File>
<File>
Filename = etc/init.d/mdadm-raid
Source = etc/init.d/mdadm-raid
Description = mdadm-raid init file
Type = binary
Permissions = 755
</File>
<File>
Filename = etc/mdadm.conf
Source = etc/mdadm.conf
Description = mdadm configuration
Type = conf
Type = local
Type = binary
</File>
</Contents>
</mdadm>
</Package>
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
leaf-cvs-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits
