Author: jhuntwork
Date: 2005-05-14 08:49:55 -0600 (Sat, 14 May 2005)
New Revision: 156
Added:
trunk/packages/raidtools/
trunk/packages/raidtools/Makefile
trunk/packages/raidtools/raidtools-1.00.3-gcc-3.3_fix-1.patch
Modified:
trunk/Makefile
trunk/TODO
trunk/packages/distcc/Makefile
Log:
Added raidtools
Modified: trunk/Makefile
===================================================================
--- trunk/Makefile 2005-05-14 14:37:40 UTC (rev 155)
+++ trunk/Makefile 2005-05-14 14:49:55 UTC (rev 156)
@@ -178,7 +178,7 @@
ch-libungif ch-imlib2 ch-pango ch-atk ch-gtk2 ch-cvs ch-libIDL
ch-firefox ch-startup-notification \
ch-xfce ch-lua ch-ion ch-irssi ch-xchat ch-samba ch-tcpwrappers
ch-portmap ch-nfs-utils ch-traceroute \
ch-ncftp ch-pciutils ch-nALFS ch-device-mapper ch-LVM2 ch-dhcpcd
ch-distcc ch-ppp ch-rp-pppoe ch-libaal \
- ch-reiser4progs ch-squashfs ch-cpio ch-db ch-postfix ch-mutt ch-slrn
ch-linux ch-klibc ch-unionfs \
+ ch-reiser4progs ch-squashfs ch-cpio ch-db ch-postfix ch-mutt ch-slrn
ch-raidtools ch-linux ch-klibc ch-unionfs \
ch-initramfs ch-cdrtools ch-blfs-bootscripts ch-syslinux
# Rules for building tools/stage1
@@ -850,6 +850,10 @@
make -C $(PKG)/$@ chroot
make unmount
+raidtools: prep-chroot
+ make -C $(PKG)/$@ chroot
+ make unmount
+
linux: prep-chroot
make -C $(PKG)/$@ chroot
make unmount
@@ -1366,6 +1370,9 @@
ch-slrn: popdev
make -C $(PKG)/slrn stage2
+ch-raidtools: popdev
+ make -C $(PKG)/raidtools stage2
+
ch-linux: popdev
make -C $(PKG)/linux stage2
Modified: trunk/TODO
===================================================================
--- trunk/TODO 2005-05-14 14:37:40 UTC (rev 155)
+++ trunk/TODO 2005-05-14 14:49:55 UTC (rev 156)
@@ -10,6 +10,5 @@
* Ask someone how to use USB to serial converters. Add support to the kernel.
* Find out exact requirements for Intel framebuffer
* Reduce dhcpcd timeout. The boot process appears to hang when there is no
DHCP server in the network.
-* Add raid-tools
* Change /etc/issue information to acknowledge work done by the new livecd
team as well.
Should we list team members?
Modified: trunk/packages/distcc/Makefile
===================================================================
--- trunk/packages/distcc/Makefile 2005-05-14 14:37:40 UTC (rev 155)
+++ trunk/packages/distcc/Makefile 2005-05-14 14:49:55 UTC (rev 156)
@@ -19,7 +19,7 @@
@echo "=====> Building $(NM) in chroot"
@echo ""
@if [ ! -f $(SRC)/$(FILE) ] ; then $(WGET) $(URL) ; fi
- @if [ ! -f /bin/ls ] ; then tar xjvf $(SRC)/$(FILE) && cd $(DIR) && \
+ @if [ ! -f /usr/bin/distcc ] ; then tar xjvf $(SRC)/$(FILE) && cd
$(DIR) && \
./configure --prefix=/usr && \
make -j3 && make install ; fi
@make clean
Added: trunk/packages/raidtools/Makefile
===================================================================
--- trunk/packages/raidtools/Makefile 2005-05-14 14:37:40 UTC (rev 155)
+++ trunk/packages/raidtools/Makefile 2005-05-14 14:49:55 UTC (rev 156)
@@ -0,0 +1,30 @@
+# raidtools Makefile
+
+# Package versions
+NM= raidtools
+VRS= 1.00.3
+DIR= $(NM)-$(VRS)
+FILE= $(DIR).tar.gz
+PATCH1= $(DIR)-gcc-3.3_fix-1.patch
+URL= $(FTP)/$(NM)/$(FILE)
+
+# RULES
+
+.PHONY: clean stage2 chroot
+
+chroot:
+ @chroot "$(MP)" $(chenv1) 'cd $(ROOT) && make ch-$(NM) $(chbash1)'
+
+stage2:
+ @echo ""
+ @echo "=====> Building $(NM) in chroot"
+ @echo ""
+ @if [ ! -f $(SRC)/$(FILE) ] ; then $(WGET) $(URL) ; fi
+ @if [ ! -f /usr/sbin/mkraid ] ; then tar xzvf $(SRC)/$(FILE) && cd
$(DIR) && \
+ patch -Np1 -i ../$(PATCH1) && \
+ ./configure --prefix=/usr --sysconfdir=/etc && \
+ make -j3 && make install ; fi
+ @make clean
+
+clean:
+ @-rm -rf $(DIR)
Added: trunk/packages/raidtools/raidtools-1.00.3-gcc-3.3_fix-1.patch
===================================================================
--- trunk/packages/raidtools/raidtools-1.00.3-gcc-3.3_fix-1.patch
2005-05-14 14:37:40 UTC (rev 155)
+++ trunk/packages/raidtools/raidtools-1.00.3-gcc-3.3_fix-1.patch
2005-05-14 14:49:55 UTC (rev 156)
@@ -0,0 +1,62 @@
+--- raidtools-1.00.3/mkraid.c~ 2003-07-23 18:57:58.000000000 +0200
++++ raidtools-1.00.3/mkraid.c 2003-07-23 18:56:59.000000000 +0200
+@@ -170,33 +170,32 @@
+
+ if (old_force_flag && (func == mkraid)) {
+ fprintf(stderr,
+-
+-"
+- WARNING!
+-
+- NOTE: if you are recovering a double-disk error or some other failure mode
+- that made your array unrunnable but data is still intact then it's strongly
+- recommended to use the lsraid utility and to read the lsraid HOWTO.
+-
+- If your RAID array holds useful and not yet backed up data then --force
+- and the hot-add/hot-remove functionality should be used with extreme care!
+- If your /etc/raidtab file is not in sync with the real array configuration,
+- then --force might DESTROY ALL YOUR DATA. It's especially dangerous to use
+- -f if the array is in degraded mode.
+-
+- If your /etc/raidtab file matches the real layout of on-disk data then
+- recreating the array will not hurt your data, but be aware of the risks
+- of doing this anyway: freshly created RAID1 and RAID5 arrays do a full
+- resync of their mirror/parity blocks, which, if the raidtab is incorrect,
+- the resync will wipe out data irrecoverably. Also, if your array is in
+- degraded mode then the raidtab must match the degraded config exactly,
+- otherwise you'll get the same kind of data destruction during resync.
+- (see the failed-disk raidtab option.) You have been warned!
+-
+- [ If your array holds no data, or you have it all backed up, or if you
+- know precisely what you are doing and you still want to proceed then use
+- the --really-force (or -R) flag. ]
+-");
++"\n"
++" WARNING!\n"
++"\n"
++" NOTE: if you are recovering a double-disk error or some other failure
mode\n"
++" that made your array unrunnable but data is still intact then it's
strongly\n"
++" recommended to use the lsraid utility and to read the lsraid HOWTO.\n"
++"\n"
++" If your RAID array holds useful and not yet backed up data then --force\n"
++" and the hot-add/hot-remove functionality should be used with extreme
care!\n"
++" If your /etc/raidtab file is not in sync with the real array
configuration,\n"
++" then --force might DESTROY ALL YOUR DATA. It's especially dangerous to
use\n"
++" -f if the array is in degraded mode.\n"
++"\n"
++" If your /etc/raidtab file matches the real layout of on-disk data then\n"
++" recreating the array will not hurt your data, but be aware of the risks\n"
++" of doing this anyway: freshly created RAID1 and RAID5 arrays do a full\n"
++" resync of their mirror/parity blocks, which, if the raidtab is incorrect,\n"
++" the resync will wipe out data irrecoverably. Also, if your array is in\n"
++" degraded mode then the raidtab must match the degraded config exactly,\n"
++" otherwise you'll get the same kind of data destruction during resync.\n"
++" (see the failed-disk raidtab option.) You have been warned!\n"
++"\n"
++" [ If your array holds no data, or you have it all backed up, or if you\n"
++" know precisely what you are doing and you still want to proceed then use\n"
++" the --really-force (or -R) flag. ]\n"
++);
+ return EXIT_FAILURE;
+ }
+
--
http://linuxfromscratch.org/mailman/listinfo/livecd
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
